Make front-end getext catalog available as JSON

[ian.morrison.a@…]

This is a question related to #22403.

It seems like it would be nice if the front-end gettext catalogs were simply available as JSON (and not as a custom js function, injected into the global namespace). This would allow the community to use (or build) separate client libraries for handing these translation strings.

Does that seem like a feature that others would be interested in?

[Aymeric Augustin]

Yes, that should be possible somehow.

[manologab]

Hi, I've been working with Django for the last few months and I will like to contribute with this feature.

What I propose is a javascript view json_catalog that returns the language settings as a json object like this:

{catalog:{
    'translate this':'traduce esto',
    'one plural sample': [
        'un ejemplo de plural',
        'muchos ejemplos de plural'
    ]
},
plural: null,
formats: {
    "DATETIME_FORMAT": "N j, Y, P",
    "DATE_FORMAT": "N j, Y",
    "DECIMAL_SEPARATOR": ".",
    ...
}}

Here is the code:
​https://github.com/manologab/django/tree/ticket_22404

Please let me know if you agree with this approach before going any further.

[Sergey Kolosov]

Working on that during DjangoCon Europe 2015 sprints.

[Sergey Kolosov]

PR: ​https://github.com/django/django/pull/4808

[Moritz Sichert]

Looks good!

[Tim Graham]

Reviewed the PR a bit more.

[Sergey Kolosov]

PR updated ​https://github.com/django/django/pull/4808

[Tim Graham <timograham@…>]

In 24440422:

Fixed #22404 -- Added a view that exposes i18n catalog as a JSON

Added django.views.i18n.json_catalog() view, which returns a JSON
response containing translations, formats, and a plural expression
for the specified language.