August 2007 - translations - lists.drupal.org

A couple of untranslated strings in 5.x core
by Vasileios Lourdas 09 Aug '07

09 Aug '07

Hello people, I've noticed a couple of untranslated strings in Drupal 5.1. Here's the procedure I've followed: 1) Installed a fresh Drupal 5.1. 2) Enabled all modules. 3) Added the greek language as a secondary language in Localization settings page. 4) Imported the translated .po file for greek [the translation is 100% complete, the Localization settings page reports 2431/2431 (100%)]. 5) Changed the site's default language to greek. In the navigation menu in left, under Create content, the names and the descriptions for the Page and Story content types are untranslated and remain in English. Is this a bug? Should I open an issue about this? -- # Vasileios Lourdas, # Informatics Engineer, Thessaloniki (Greece) # http://www.lourdas.name

4 23

FYI: update_status 5.x-2.0 final out soon - please translate now if you want
by Derek Wright 09 Aug '07

09 Aug '07

Over at http://drupal.org/node/155878 I was asked to give translators some time to update their translations for the official 5.x-2.0 release of the update_status module. The 5.x-2.0-rc2 release[1] is now out, a string freeze is in place, the translation templates are up to date, and the official release should be out in about 2 or 3 days. So, if you want to get your translation of this "must-have" D5 contrib module into the official 5.x-2.0 release, please act quickly. If you're planning to do this, you can reply to the issue [2] to indicate your interest, and I'll try to hold off on tagging the release until I see your commit or .po file attached there. Thanks, -Derek (dww) [1] http://drupal.org/node/165312 [2] http://drupal.org/project/comments/add/155878

4 5

central space for contrib pos
by Alaa Abd El Fattah 05 Aug '07

05 Aug '07

Hi, working on the Arabic translation, we have a small team of translators being paid by different projects to translate drupal. we are trying to do quality control and unify the vocabulary as much as possible (not a simple task considering how many different people's and nations speak arabic). however the requirement to store contrib po's in the contrib module's CVS directory makes it very difficult to track which modules are translated and and the whole quality control process becomes very tedious. for 4.7 translation we just dumped contrib module POs in the translations/ar directory but I'm not sure that's a good idea, I thought about having a translations/ar/contrib subdirectory or even starting a new project for Arabic contrib translations (translations/ar_contrib). so what about you? how do you organize translation of contrib modules? cheers, Alaa -- Alaa: Husband of the Grand Waragi Master http://www.manalaa.net

3 4

Empty Strings
by Martin Stadler 04 Aug '07

04 Aug '07

So empty strings in a .po file override already translated strings if I import them... I know the current system of contrib translation is far from good and people are working on it (d6, SoC...). Anyways, here's my scenario: I started translating some contrib modules I use (into German). Of course I want my work to be commited to the drupal CVS. I read the translations handbook and got used to some gettext tools, merging etc. What I did was extracting a fresh .pot file, merging it with the core de.po into the module's de.po and started translating the still empty strings. Sometimes it's too much work and it seems to be enough to only translate the strings that will be visible to the end-user leaving the rest of the strings empty. After importing and testing I filed issues in the respective projects attaching my de.po files. Now I found out that empty translation strings will override already translated strings in the override mode of the import feature of drupal. As I merged the core .po file with my .pot this is only a problem if the string doesn't exist in core but does in another contrib module with an existing translation which is already imported. I cannot merge all module's translations with the one I'm about to create. So it may happen that I override an existing translation of a contrib module with an empty string of another's module's translation. To me it makes sense to keep empty string in my translation file as I or someone else will propably continue to work on that file. But as these empty strings are soon part of the official stable modules they can override other's translations too. Of course I could import them without overriding existing strings but sometimes I want to update my translation... Is there any solution to this problem? A tool to delete the empty strings as a workaround? What kind of .po files should I commit in the future? Sorry for the long text and repetitions... Cheers, Standart

2 3