translations May 2007

translations@drupal.org

11 participants
8 discussions

xxx-module.hu files
by Bèr Kessels 29 May '07

29 May '07

Hello, In the contribs I just found a few xxx-module.hu po files. According to the handbook[1] they should have been named 'hu.po'. Did I miss a change in policy, and if so, can someone explain the new policy so that I can update the handbook page? If I did not miss omething, is it okay if I rename the files when I encounter them to the proper naming scheme? Bèr [1] http://drupal.org/node/11396 -- Drupal, Ruby on Rails and Joomla! development: webschuur.com | Drupal hosting: www.sympal.nl

3 5

Re: [translations] [Translations] Language
by Gabor Hojtsy 27 May '07

27 May '07

Dear Ozono, We are open to publish the Azerbaijan translation (or any other translation) if someone send it to us. Drupal works with an open community, so if someone would like to see the Azerbaijan translation, he can do it. Gabor tuncay(a)eco.gov.az wrote: > Dear Drupal administrations, > > I think its time to have Drupal in Azerbaijan language. Here in Azerbaijan > everyone likes your CMS, but the main problem is translations. All of us > are waiting for Azerbaijan Drupal CMS. We ded more projects in Drupal. But > our clients want to have Drupal in their own language. We recomend this CMS > to all of our friends. Tell us please when we could see the translations in > Azerbaijan version? > > Truly yours, > Ozono. >

2 1

updating translations: how valuable is user data after all?
by Gabor Hojtsy 24 May '07

24 May '07

Hi guys, Now Drupal 6.x-dev includes cool features to import PO files automatically at every logical step: - you can install Drupal in your foreign language, and have PO files for all enabled modules imported along automatically - when you add a new language, all translation files for enabled modules get imported automatically for that language - when you install new modules or enable themes, the translation files for these components get imported for all enabled languages This is all great and automated, contrib modules already have their PO files at the right place, and we will update the packaging scripts for Drupal 6 to package core translations properly. You might notice a pattern in the above features though: they IMPORT stuff into the database. Unfortunately we have no way in Drupal 6 to remove translations when you disable a theme or uninstall a module. We don't know what strings appeared in *only* that component, and not elsewhere in Drupal, so we can remove them without problems. For that, we would need the extractor script built into Drupal core to look through all source files of enabled components and identify the unused strings in the database. Fortunately this is doable in contrib, now that extractor has it's own Drupal module. (Of course it is doable in Drupal core my deleting all strings from the database and reimporting files for only the enabled components, but read on about the value of user data). BTW Drupal 6 core still need upgrade support for translations. So when you update a module or Drupal itself, new and corrected translations get into your database. New translations are easy again, they are just importing new stuff, which we are very good at :) Updating translations already in the DB threatens user data though. In Drupal 5 and before, we have no information about what translations a user modified on the web interface, so we don't know what was imported from available PO files and what was user defined. We can reimport stuff from the files, but can easily loose/overwrite user defined/updated strings. What can we do about not to loose user defined strings? We can easily introduce a 'modified' bit into the locale translations (target) table, just as it was in menu module in Drupal 5. That would help us from Drupal 6 onward, but it does not help us loosing user defined strings when a Drupal 5 to Drupal 6 upgrade happens. So how cautious should we be there? 1. Do not overwrite any existing translation, risking that we leave incorrect and fixed translations in the database. 2. Do overwrite existing translations on an update, risking that we overwrite user modified translations. Note that an update will not *remove* anything from the DB because we don't know what we can remove as explained above. It can *overwrite* stuff though, and problems are around these overwrites. So how should the update paths work for Drupal and for modules/themes? Gabor

3 6

Re: [translations] translations Digest, Vol 19, Issue 5
by Miguel Duarte 22 May '07

22 May '07

Hi, My 2 cents is that you should overwrite everything. At leat the pt-pt translation is still evolving and there are many old translation we updated through the time. Of course, before, you should always tell the user about that. ;) Regards, Miguel Duarte 2007/5/22, translations-request(a)drupal.org <translations-request(a)drupal.org>: > Send translations mailing list submissions to > translations(a)drupal.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.drupal.org/mailman/listinfo/translations > or, via email, send a message with subject or body 'help' to > translations-request(a)drupal.org > > You can reach the person managing the list at > translations-owner(a)drupal.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of translations digest..." > > > Today's Topics: > > 1. updating translations: how valuable is user data after all? > (Gabor Hojtsy) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 22 May 2007 11:53:19 +0200 > From: Gabor Hojtsy <gabor(a)hojtsy.hu> > Subject: [translations] updating translations: how valuable is user > data after all? > To: development(a)drupal.org, A list for translators > <translations(a)drupal.org> > Message-ID: <4652BD8F.9000801(a)hojtsy.hu> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Hi guys, > > Now Drupal 6.x-dev includes cool features to import PO files > automatically at every logical step: > > - you can install Drupal in your foreign language, and have > PO files for all enabled modules imported along automatically > > - when you add a new language, all translation files for > enabled modules get imported automatically for that language > > - when you install new modules or enable themes, the translation > files for these components get imported for all enabled > languages > > This is all great and automated, contrib modules already have their PO > files at the right place, and we will update the packaging scripts for > Drupal 6 to package core translations properly. > > You might notice a pattern in the above features though: they IMPORT > stuff into the database. Unfortunately we have no way in Drupal 6 to > remove translations when you disable a theme or uninstall a module. We > don't know what strings appeared in *only* that component, and not > elsewhere in Drupal, so we can remove them without problems. For that, > we would need the extractor script built into Drupal core to look > through all source files of enabled components and identify the unused > strings in the database. Fortunately this is doable in contrib, now that > extractor has it's own Drupal module. (Of course it is doable in Drupal > core my deleting all strings from the database and reimporting files for > only the enabled components, but read on about the value of user data). > > BTW Drupal 6 core still need upgrade support for translations. So when > you update a module or Drupal itself, new and corrected translations get > into your database. New translations are easy again, they are just > importing new stuff, which we are very good at :) Updating translations > already in the DB threatens user data though. In Drupal 5 and before, we > have no information about what translations a user modified on the web > interface, so we don't know what was imported from available PO files > and what was user defined. We can reimport stuff from the files, but can > easily loose/overwrite user defined/updated strings. > > What can we do about not to loose user defined strings? We can easily > introduce a 'modified' bit into the locale translations (target) table, > just as it was in menu module in Drupal 5. That would help us from > Drupal 6 onward, but it does not help us loosing user defined strings > when a Drupal 5 to Drupal 6 upgrade happens. So how cautious should we > be there? > > 1. Do not overwrite any existing translation, risking that we leave > incorrect and fixed translations in the database. > > 2. Do overwrite existing translations on an update, risking that > we overwrite user modified translations. > > Note that an update will not *remove* anything from the DB because we > don't know what we can remove as explained above. It can *overwrite* > stuff though, and problems are around these overwrites. > > So how should the update paths work for Drupal and for modules/themes? > > Gabor > > > ------------------------------ > > _______________________________________________ > translations mailing list > translations(a)drupal.org > http://lists.drupal.org/mailman/listinfo/translations > > > End of translations Digest, Vol 19, Issue 5 > ******************************************* > -- Mobile: +351.966075978 Office: +351.217242590 Fax: +351.210125718 Skype: mcduarte2000

1 0

FYI: New way to classify releases on drupal.org
by Derek Wright 08 May '07

08 May '07

All project maintainers are encouraged to read: http://drupal.org/node/142344 thanks, -derek (dww)

1 0

Anybody I could ask general questions about Spanish translations?
by Gustavo Sánchez Muñoz 06 May '07

06 May '07

Good morning, I have just applied to the CVS to be able to submit translations for some of the contributed modules. I am posting this because I have some doubts about the workflow. I would like to know if there is something similar to a style book, translation guidelines, etc... so as to keep some consistency with the general "translation into Spanish" consensus. I don't know if there is some type of 'super translator' that reviews the translations submited, etc... Thank you Gustavo Sánchez :)

2 3

Estimate required
by Nadir Durrani 04 May '07

04 May '07

Dear All My name is Nadir Durrani. I am leading an Open Source Localization Project @CRULP (Center for Research in Urdu Language Processing) here in Pakistan. We want to localize Drupal. I need to have a rough estimate of total number of translation messages (i.e. total number of strings) that we need to localize drupal. Best Regards Nadir Durrani Team Lead OSL-CRULP

2 2

Help make decisions about Drupal 6 translation template standards! Just two questions!
by Gabor Hojtsy 02 May '07

02 May '07

Hi, Let me point you in this discussion. These are very important questions to answer for Drupal 6 to be as translation and foreign language friendly as possible. The main reason I put up these questions is to make *YOUR* life easier when translating Drupal 6 stuff (core or contrib). Now is the time to step up and have your voice heard! http://groups.drupal.org/node/3907 Gabor

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

translations May 2007