translations January 2008

translations@drupal.org

16 participants
21 discussions

update for l10n_server users
by Gábor Hojtsy 31 Jan '08

31 Jan '08

Hey, I just managed to level the differences between the 4 branches of potx module, so now potx 5.x-1.2 contains the best code for you to translate Drupal 6. Please do the following to continue Drupal 6 translation: - update to potx 5.x-1.2 (the latest stable version in the 1.x series) - update to the latest l10n_server development version (there were some fixes related to export file placement, see http://drupal.org/node/212594#comment-712331) - grab Drupal 6 RC3 and parse it in You will notice that there are a small number of new strings to translate due to potx finding stuff better and RC3 contains some translatability fixes for strings which were not translated before. Note that Drupal 6 final is expected for early next week. Use the flat export format to export files and commit to drupal.org CVS, so your translation will be available on launch. Happy translating! Gabor

1 0

Drupal 6.0 RC3 is out
by Gábor Hojtsy 31 Jan '08

31 Jan '08

Hey, Drupal 6.0 RC3 is out and it means a small amount of work for you. We noticed some string which were not translatable and needed to modify one or two strings as well. It should be quick to adapt to this version. Note that Drupal 6 final is expected to be out sometime next week, unless something wrong happens, so if you can get your work out to be committed to Drupal.org, then all our users could use the translations. Drupal 6 itself includes instructions on how one can download translation packages from Drupal.org, so it would be important to have the packages sitting there. A note to l10n_server users: upgrade to the latest version and use the flat export format to export files for CVS commits. Let me know if there are any problems / questions. Gabor

1 0

Localization Server status
by Drupal Norge 28 Jan '08

28 Jan '08

I am just wondering on the status of the localization server. It seems that there are numerous translation teams who have installed the localization server on their own websites and Gabor mentioned on his e-mail regarding D6 packaging that: "The latest version of localization server also includes a flat export format, which exports files as you need to commit them to Drupal.org CVS. So get those translations flowing!" Should we install our own localization server or should we just wait for it to be installed in a drupal.org subdomain? Either of the two is okay...I am just wondering what our course of action will be. ****Gabor, what do you recommend? Best regards, John (JohnNoc) -------------------------------------- http://drupalnorge.no http://drupal.org/project/nb http://drupal.org/project/nn

2 1

Translations for 6.0
by Miguel Duarte 28 Jan '08

28 Jan '08

Hi, Is there already a timing regarding when we will be able to start translating for the 6.0 using the web interface? -- Mobile: +351.966075978 Office: +351.217242590 Fax: +351.210125718 Skype: mcduarte2000

2 1

FYI: update_status and user_status official release warning
by Derek Wright 27 Jan '08

27 Jan '08

Greetings, Drupal translator community. I'm about to create official releases for 2 of my contribs, and I thought I'd give interested parties a chance to update their translations since there have been some string changes: 1) [Important] update_status 5.x-2.1 (http://drupal.org/project/ update_status) This is the highly popular D5 contrib module that tells you when your site is missing updated releases from drupal.org. Already in core for D6, and mostly the same strings, so if you've been working on your D6 core translation, you can probably re-use the vast majority of strings for this (or, working on this translation for 5.x-2.1 will be a healthy start for your core translations). 2) [Low prio] user_status 5.x-1.2 (http://drupal.org/project/ user_status) This is a small module that gives admins a way to send notification emails when users are approved, blocked or removed. Again, this functionality is now in core, but the strings are probably more different. This is a handy module if your site requires admin approval for accounts, but doesn't seem to be particularly popular or widely used. Both are in a complete code/string freeze, and have updated .pot files in their po subdirectories. If anyone wants to update a translation for either one, please open a new task about it in the respective issue queue, so I know to hold off on tagging the release until I see you commit or post the new .po files. http://drupal.org/node/add/project-issue/update_status/task http://drupal.org/node/add/project-issue/user_status/task I'm aiming to release both by Tuesday or Wednesday at the latest, so please at least let me know sooner than that if you're interested but need more time. Thanks, -Derek (dww)

1 0

Drupal 6 packaging works
by Gábor Hojtsy 25 Jan '08

25 Jan '08

Hey, Although we forgot to send a note here, Drupal 6 translation packaging works for a few days now, so feel free to tag your translations for Drupal 6, and please follow the naming guide (ie. use the same name as in drupal-pot but with .po extensions not .pot). The latest version of localization server also includes a flat export format, which exports files as you need to commit them to Drupal.org CVS. So get those translations flowing! Gabor

1 0

Problems with translations (beginner)
by Dalia Kumpiluvelil 24 Jan '08

24 Jan '08

Hello all, I am trying to translate phrases from English into German, but I have some problems with particular strings. There are two major problems: 1. Strings are already translated into German but not displayed on the website in spite of correct language settings or 2. I cannot find them at all in Poedit. Furthermore I have a question regarding the strings attached with "@"; can you just overwrite them or should variables like @buddy stay out of other reasons? And what should I do with variables with "%" and "!"? Also, It would be helpful to know where a string is being used. The "reference node/add/page" doesn't help too much tp find out where the translation appears (especially, if there are two locations of a string), and there are lots of double entries like "buddy of/Buddy of" etc. Any hints and tipps are highly appreciated! best regards, Dalia Already translated in Poedit, but not shown on the site: ----------------------------------------------------- -Invite your friends and colleagues. -Points -Enter the URL to use for this view in the form of 'dir/dir'. Do not begin or end the URL with a /. Example: 'view/tracker'. This is required if providing a page view. You can also add $arg as a placeholder for arguments passed in the URL, for example 'user/$arg/tracker' or 'view/taxonomy/$arg'. Note that any arguments listed here will be required, even if they are listed as optional below. You do not need to list arguments at the end of the path -Description -Subscribers -Subscribe -Recent posts -user points Not found in Poedit: ------------------- -You currently do not have any pending Freund requests from other users. -You do not have any pending Freund requests that you have made. -To organize your Freunde into groups, visit the edit < <http://iik-forum.de/buddylist/6/buddies/groups/edit> http://iik-forum.de/buddylist/6/buddies/groups/edit> groups page -You don't have any groups defined. -No groups found -Groups are a way to keep your Freunde organized. Groups can be named whatever you like -Add new groups -authentical user -Groups are a way to keep your Freunde organized. Groups can be named whatever you like. -Search for a group by name. -No subscribed groups -There are no new posts in your subscribed groups. -Unread posts in my groups -my recent -my unread

2 1

Re: [translations] translations Digest, Vol 27, Issue 12
by Amed Çeko Jiyan 20 Jan '08

20 Jan '08

Hi again, - As Frederik says, we use "kmr" for Kurmanji and "ckb" for Sorani. We use these codes in GNOME and some other projects. - you are right, "ku" is not a country code. We can not ku_KU in any projects. SO we use ku_TR for some projects. Why projects need country code? Do countries support projects? No. It would be great to use only language codes for all projects. As you see from Kurdish Google, iso639 2 makes problems for us. It would be better to use "kmr" and "ckb" That is good Drupal will use iso639 3. Amed On Jan 19, 2008 2:00 PM, <translations-request(a)drupal.org> wrote: > 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. Re: language code problem (for kurdish) ( G?bor Hojtsy ) > 2. Re: language code problem (for kurdish) > (Frederik 'Freso' S. Olesen) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 18 Jan 2008 14:52:15 +0100 > From: " G?bor Hojtsy " <gabor(a)hojtsy.hu> > Subject: Re: [translations] language code problem (for kurdish) > To: "A list for translators" <translations(a)drupal.org> > Message-ID: > <86ca3ccb0801180552u381bdd54v557cf8fc2f722da1(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Hey Amed, > > On Jan 18, 2008 2:00 AM, Amed ?eko Jiyan <amedcj(a)gmail.com> wrote: > > I would translate Drupal into Kurdish (Kurmanc?). I got cvs account and > i > > created a project named Kurdish Kurmanc?. I would use ku_KU as language > code > > for Kurmanc?, but i got that message "- We normally use iso639 2 letter > > language codes for Drupal, ie for Kurdish it is ku" all of otehr > projects > > -like Mozilla Firefox, Google- would we use ku as language code. That is > > because they don't know any thing about Kurdish language(s). Kurdish is > a > > languages family as Scandinavian. > > After i start to translate Drupal into Kurdish Kurmanc?, some other > friends > > started to translate into Kurdish Soran?. We are translating Drupal into > two > > languages but we have one language code (ku). will one of us stop to > > translating Drupal because that problem? No, i don't think so. I have > > allready created ku, ku_KU, so_KU in CVS directory. > > I would Drupal will let us to use ku_KU and so_Ku as languages codes. > > > > *Maybe you would see that big mistake : http://www.google.com/intl/ku/ > > That is Kurdish page of Google. When you open that page, you will some > some > > thing in latin letters (Kurmanc?) and some other things in arabic > letters > > (Soran?). I hope Drupal will not fall in same mistake. > > Well, Drupal 5 and before uses the ISO 639 language codes. With Drupal > 6, we are migrating to the RFC 4646 codes, which supersede the ISO 639 > codes as far as W3C directions go. > (http://www.ietf.org/rfc/rfc4646.txt) It is important to choose > interoperable language codes, because when browsers send what is their > preferred language, Drupal can only choose the right one for display, > if the browser and Drupal use the same format. So we try to follow > standards. > > I looked into the registry for information on how this is handled > there: http://www.iana.org/assignments/language-subtag-registry. Looks > like the IANA does not "know about" (to borrow your words) Kurmanc? or > Soran? either. May it be that there are some other / alternate names > for these variants, which are registered there? > > It would be great to do this to the letter of the standards, so I'd > ask you to collaborate and think this through first :) > > Gabor > > > ------------------------------ > > Message: 2 > Date: Fri, 18 Jan 2008 21:34:20 +0100 > From: "Frederik 'Freso' S. Olesen" <freso.dk(a)gmail.com> > Subject: Re: [translations] language code problem (for kurdish) > To: "A list for translators" <translations(a)drupal.org> > Message-ID: > <5ac9cdd10801181234o4aac30edtfe4c46665a0c0a73(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > 2008/1/18, Amed ?eko Jiyan <amedcj(a)gmail.com>: > >[...] That is > >because they don't know any thing about Kurdish language(s). Kurdish is a > >languages family as Scandinavian. > >After i start to translate Drupal into Kurdish Kurmanc?, some other > friends > >started to translate into Kurdish Soran?. We are translating Drupal into > two > >languages but we have one language code (ku). [...] > > So there is no language "Kurdish"? According to Wikipedia, Kurdish is > considered by some to be in three parts (Northern (Kurmanji), Central > (Sorani), and Southern (Zaza-Gorani)), although this is also a topic > of linguistic debate.[1] However, as I'm very much *for* spreading > both languages and dialects, I'd say: Just use the ISO 639-3 codes! > "kmr" for Kurmanji and "ckb" for Sorani. > > (By the way, I only investigated this as I am Scandinavian meself > (Danish, to be exact)... >_>) > > >[...] I have > >allready created ku, ku_KU, so_KU in CVS directory. > >I would Drupal will let us to use ku_KU and so_Ku as languages codes. > > so_KU would mean "Somali, as spoken in KU" (apparently, there's no > "ku" country code[2]). I'm pretty sure this is not your intention. :) > Again, I'd say: Go with the ISO 639-3 codes I listed above. > > [1] http://en.wikipedia.org/wiki/Kurdish_language#Dialects > [2] http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2 > -- > Frederik 'Freso' S. Olesen <http://freso.dk/> > > > ------------------------------ > > _______________________________________________ > translations mailing list > translations(a)drupal.org > http://lists.drupal.org/mailman/listinfo/translations > > > End of translations Digest, Vol 27, Issue 12 > ******************************************** >

4 4

language code problem (for kurdish)
by Amed Çeko Jiyan 20 Jan '08

20 Jan '08

Hi all, I would translate Drupal into Kurdish (Kurmancî). I got cvs account and i created a project named Kurdish Kurmancî. I would use ku_KU as language code for Kurmancî, but i got that message "- We normally use iso639 2 letter language codes for Drupal, ie for Kurdish it is ku" all of otehr projects -like Mozilla Firefox, Google- would we use ku as language code. That is because they don't know any thing about Kurdish language(s). Kurdish is a languages family as Scandinavian. After i start to translate Drupal into Kurdish Kurmancî, some other friends started to translate into Kurdish Soranî. We are translating Drupal into two languages but we have one language code (ku). will one of us stop to translating Drupal because that problem? No, i don't think so. I have allready created ku, ku_KU, so_KU in CVS directory. I would Drupal will let us to use ku_KU and so_Ku as languages codes. *Maybe you would see that big mistake : http://www.google.com/intl/ku/ That is Kurdish page of Google. When you open that page, you will some some thing in latin letters (Kurmancî) and some other things in arabic letters (Soranî). I hope Drupal will not fall in same mistake. Best regards, Amed Çeko Jiyan

3 3

localization server files v.s. translation templates
by Erik Stielstra 13 Jan '08

13 Jan '08

Using Gábor's excelent localization server we have completed the Dutch translation of Drupal 6. The filenames of the exported translations do not match the translation templates. For example: Exported from localization server: aggregator-admin-inc.nl.po and aggregator-module.nl.po In translation templates: modules-aggregator.pot Can someone confirm that drupal-6 translations must only be uploaded to cvs matching (the file names and source strings of) the translation templates. And therefore we need to transfer the translations to the template files structure. Regards, Erik Stielstra

3 4

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

translations January 2008