I am +1 to Option 2, which allows a domain-driven placement, even if some files are going to have very few messages.
PS I left some review comments regarding location comments in translation source files in one of your pull request. Great initiative :) Regards, Maciej pon., 18.02.2019, 16:21 użytkownik Tobias McNulty <tob...@caktusgroup.com> napisał: > Claude, I'm in -- many thanks! > > I have a project started here: > https://www.transifex.com/django/djangoproject-dot-com/ > > That said, I have a question about how to best set this up. > > djangoproject.com is unique: It houses strings that apply to a number of > different sites, some of which have a single Django app and others of which > rely on multiple Django apps. One of those sites (and apps) is > docs.djangoproject.com, which puts us in the potentially confusing spot > of having two different projects in Transifex that handle translation for > what is a single website: https://docs.djangoproject.com. > > I was originally leaning towards having a single project-level locale > directory <https://github.com/django/djangoproject.com/pull/865> to > handle all the translations for strings in the "djangoproject.com" repo > ("Option 1"), but having seen how we have Transifex set up, I'm wondering > if that's a less-than-optimal approach. > > *I believe* that we could instead keep one locale directory per app > <https://github.com/django/djangoproject.com/pull/864> ("Option 2"), and > then in our Transifex config decide *on a per-app *basis what project in > Transifex should house the translations. For now, that would likely mean > that the "docs" app in the dp.com repo would go to "django-docs" in > transifex (to a "static-website-strings" or similarly named resource) and > everything else would go to the "djangoproject.com" project I set up and > linked above, with resources named for the app. If/when we get to this > point, we could potentially split off 'dashboard.djangoproject.com' to > its own Transifex project. This option does have the unfortunate > consequence of needing to move app-specific HTML templates into their > respective app directories, but if it helps simplify the translation > process I think it would be well worth the effort (and is mostly done, I > think, as part of this proof-of-concept PR). > > Does Option 2 sound like a reasonable approach? What do others think? > > On Mon, Feb 18, 2019 at 9:16 AM Claude Paroz <cla...@2xlibre.net> wrote: > >> Le 18.02.19 à 01:55, Tobias McNulty a écrit : >> (...) >> > Is there someone on this list who could make me an Admin (or Project >> > Coordinator for such a project) in our Transifex account? My username >> is >> > tobias_dsf. >> >> Done. Thanks for pushing this forward! >> >> Claude >> -- >> www.2xlibre.net >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django internationalization and localization" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to django-i18n+unsubscr...@googlegroups.com. >> To post to this group, send email to django-i18n@googlegroups.com. >> Visit this group at https://groups.google.com/group/django-i18n. >> For more options, visit https://groups.google.com/d/optout. >> > -- > You received this message because you are subscribed to the Google Groups > "Django internationalization and localization" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-i18n+unsubscr...@googlegroups.com. > To post to this group, send email to django-i18n@googlegroups.com. > Visit this group at https://groups.google.com/group/django-i18n. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django internationalization and localization" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-i18n+unsubscr...@googlegroups.com. To post to this group, send email to django-i18n@googlegroups.com. Visit this group at https://groups.google.com/group/django-i18n. For more options, visit https://groups.google.com/d/optout.
