Closed eloraburns closed 11 years ago
I think I understand how to do this now -- will test it out a bit more and commit tomorrow!
Update: Managed to consolidate all translations to PROJECT_ROOT/local/
. Reference changesets: e5c2e50ad2c5d180fc8ecc564a7328c4dca6aa12 and 2599e5db3d9acbb7045bc59d539c2f2f50040b0d
I am however, in favor of keeping separate translations for each, that way, it is a lot easier to push upstream, assuming they welcome translation works done on the core.
Yeah, if you can split them out I think that's reasonable.
They obviously have the {% trans %}
stuff set up on their side, but I don't know if the have existing .po files that we could feed back.
I've split the translation to two locations:
symposion/
is now at symposion/locale
symposion_project
is now at symposion_project/locale/
I don't think they have any .po
file yet for the core, so only i18n is mostly done, but not l10n..
The existing infrastructure only translates things from
symposion_project
as far as I can tell. It looks like a bunch of{% trans %}
tags already exist forsymposion
, so I suspect it will look easy in hindsight. ;)I am curious to see if we end up with a single .mo file for
symposion_project
+symposion
, or separate translations for each…