Currently the 6.x branch has a po folder and a translations folder. According to this comment there should only be a translations folder.
I was considering removing the po folder along with the (outdated) translations within and accepting updated translations with a newer POT file to put into the translations folder. A newer POT file than what exists currently may need to be generated in response to this.
I don't have any experience with internationalization, so let me know what works best for you all.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | taxonomy_access_admin.inc_.patch | 1.33 KB | magnus |
Comments
Comment #1
keve commentedI did not know about 'translation' folder. It worth to clean up directory structure. :)
'po' folder seems more standard in drupal. Please do not delete it, move 'translation' folder's content to po folder. (with latest pot file).
I do not know what are the best practices to update translation 'po' files, as i do not know who were the translators.
Comment #2
magnus commentedFrom Drupal 6 translations goes into /translations and the /po is no longer used and could be removed in the D6 branch. Copy the /po from D5 to /translations in D6 if you want to save the old work.
I'm not sure, but I think you can grant a translator access to CVS for this project. I have a translator account to update translations in contrib modules so that's how I was able to update the Swedish translation and also update the POT.
Usually there aren't that many translators on contrib modules so maybe it is easier to update the translations yourself it there is a new translator. It can be a little bit confusing about branches and tags and the files could end up everywhere =)
There are four strings that cannot be translated in the dev. I made a patch to fix this.
I have updated the POT and Swedish translation in CVS for 6.x-1.x (with the fix above), I also included the German translation found in http://drupal.org/node/166080#comment-851952.
Comment #3
cpugeniusmv commentedPatch committed.
I'll probably just copy the old translations from po into an "old" subdirectory in translations.
Comment #4
keve commentedSorry, i misunderstood the new concept. You are right: all translations better go to tranlations folder. :)
Thanks for both of you for the efforts.
It would be nice to collect contact details of translators, who submitted translations, so that when t() changes, we can call for help and update translations easier.
Comment #5
cpugeniusmv commentedComment #6
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #7
lourenzo commentedHello,
I already have a CVS account, how can I get a translator account in order to add pt_BR translations to contrib modules?
Thanks
--
Lourenzo Ferreira
http://lourenzo.blog.br