Repository: cookiecutter/cookiecutter-django

Issue:
Offer translation to strings collected by makemessages
## Description

The newly created projects could have the translation to strings by default. 

## Rationale

I frequently create projects supporting multiple languages, and there's always the need to translate these strings manually. 

I'd happily provide the PT-BR (Brazillian Portuguese) translation if there is any interest in the proposal. I guess the user could choose which languages to include while creating a new project.


Discussion:
That's an interesting suggestion. I understand the problem you're describing, and appreciate the pain to translated the same strings over and over.

For context, by default, [we ship with American English only](https://github.com/cookiecutter/cookiecutter-django/blob/00b22bc02d6c1668972cf61a6632dbbb200b8a86/%7B%7Bcookiecutter.project_slug%7D%7D/config/settings/base.py#L28).

I assume your suggection is to add more `.po` files under the locale folder, without configuring the additional languages, right? I don't think we should add more languages to the `LANGUAGES` settings by default.

In terms of usability, it would be a massive boost I think. If you need some of the languages we provide, then it's much easier to get started, and if not, it's pretty simple to remove the translation files you don't need, or they can also stay around, I don't think there is any harm in that.

While I think the default `LANGUAGES` settings that we provide should stay minimal, we could add all the translations commented out, to make it easier to add them.

> I guess the user could choose which languages to include while creating a new project.

That would be ideal, although the user would typically give one or more (e.g. en-us and fr-fr), and it doesn't look supported by cookiecutter right now: https://github.com/cookiecutter/cookiecutter/issues/1002

PS: I started to provide more help around translations in #4363. This is to fix another issue, but we should build a potential fix for this on top of it.
Hello there!

Good to see you appreciated the idea. Just to make sure I got this:
- We'll create multiple .po folders, for each supported language
- All the supported languages will appear at `LANGUAGES`, but commented out by default
- The user can uncomment the desired languages at `LANGUAGES` or delete some folders

I'll start working on this subject, starting from your branch at #4363.

Glad to help.

Resolving patch:
diff --git a/{{cookiecutter.project_slug}}/config/settings/base.py b/{{cookiecutter.project_slug}}/config/settings/base.py
--- a/{{cookiecutter.project_slug}}/config/settings/base.py
+++ b/{{cookiecutter.project_slug}}/config/settings/base.py
@@ -26,6 +26,12 @@
 TIME_ZONE = "{{ cookiecutter.timezone }}"
 # https://docs.djangoproject.com/en/dev/ref/settings/#language-code
 LANGUAGE_CODE = "en-us"
+# https://docs.djangoproject.com/en/dev/ref/settings/#languages
+# from django.utils.translation import gettext_lazy as _
+# LANGUAGES = [
+#     ('en', _('English')),
+#     ('pt-br', _('Português')),
+# ]
 # https://docs.djangoproject.com/en/dev/ref/settings/#site-id
 SITE_ID = 1
 # https://docs.djangoproject.com/en/dev/ref/settings/#use-i18n


Test patch: