id,summary,reporter,owner,description,type,status,component,version,severity,resolution,keywords,cc,stage,has_patch,needs_docs,needs_tests,needs_better_patch,easy,ui_ux 10260,i18n documentation refactoring,Ramiro Morales,Ramiro Morales,"The attached code reshuffles and modifies the internationalization docs in the following way: * Divided the documentation in: An introductory document (with links to the other docs and to a couple of external resources) plus thee documents describing different tasks: internationalization, localization and deployment. * i18n doc: Consolidated the sections that talk about ''lazy translations'' and put the ''Pluralization'' section before them. * Put the sections about !JavaScript on the i18n doc and at the same level as the Python and template translatable string marking up sections, only a section about how to extract and compile message catalogs from JS has been kept in the l10n doc. * Removed the content about translating Django itself that was scattered all over the document(s). Because of that it wasn't helpful to the minor audience interested in it and confused things for the major audience: people dealing with apps i18n. Moved the non-redundant text to the already existing relevant `internals/contributing.txt` section. * Moved text about how to create a minimal Django translation (to be able to activate an app translation to a given language) from the locale middleware notes (now in the deployment doc) to the l10n doc, leaving only a small note and a reference. The description of Django ''technical messages'' got moved to `internals/contributing.txt`. * Put the ''gettext on win32'' section on the l10n doc. * Small typo fixes. * Unfied treatment given to `.po` files. They are now refered to as ''message files'' in all documents. The section about creating/updating these files from !JavaScript code refered to them as ''message catalogs'', it wasn´t wrong but was inconsistent and could be confused with a different thing: the data served by the `javascript_catalog` (the section describing it does even calls it ''message catalogs'') '''Things for further thought:''' * What to do with the ''Using translations in your own projects'' section (now on the l10n doc)? Currently it's a mix of things (duplicate info, app architecture, integration and deployment advice). * Move some content to the ``howto/`` Django doc sub-tree? ",,closed,Documentation,dev,,fixed,l10n i18n translation message files localization intrnationalization,Malcolm Tredinnick Gonzalo Saavedra Jannis Leidel,Accepted,1,0,0,0,0,0