While translating docbook-locales, a few entries are bugging me a bit. I am
writing in here in an attempt to understand how the other teams have tackled
these strings. These are here:
msgid "Set Index"
#. Tag: para
I have currently translated this (and the lowercase version of the same string)
as "an index of sets" where "set" refers to "groups" (as per the translation
note in string number 94). Is this context correct?
#. Tag: para
#. LOCALIZATION NOTE: attribution of authorship: 'Romeo and Juliet' by William
This is the tricky one. From the translators note it seems that the translated
version of "by" would be used in a format like '<name-of-book> by
<name-of-writer>'. Now this would have been quite easy to write if the
construction of the sentence in my language follows the same structure as in
English. Unfortunately, this is not the case and a literal representation of the
'<name-of-book> by <name-of-writer>' structure would be extremely incorrect
We would probably follow a structure like: <name-of-book> <name-of-writer>
<translation for 'written by'> (a simple 'by' would not be a perfect fit)
I am curious to know how the other languages with a similar problem have handled
Btw, in case this needs to be put in a bug, I would be happy to do so.
Thanks in advance
mishti or runa_b on Freenode, Gimpnet, Mozilla, LinuxChix
On 08/07/2009 07:03 AM, Eric Christensen wrote:
> I've added a column to the Guide Table that shows the priority that
> we give to translations. This was a request from L10N so they would
> know what guides to work on when manpower was limited. Here's my
> 1 Release Notes
> 2 Installation Guide
> 3 Installation Quick Start Guide
> 4 user Guide
I think that the Installation Quick Start Guide should be above the full
Installation Guide for two reasons:
* the IQSG is likely to be of greater benefit to a greater number of users
* when a translator has finished with the IQSG, they can re-use many of
the strings to get a head start on the full Installation Guide
I would also like to add two items as 0 on the list (0.1 and 0.2?) :
* The docbook locales list (I guess this fills the same place in the
L10N workflow as the old docs-common-entities module) -- this is
available in Transifex here:
* The Publican "Common_Content" sections -- not currently available in
Transifex, but will become so soon
Should I add these to the top of the Guides table? Although they're not
"guides" themselves, localizations of the guides will not work unless
these items are completed first.
----- "Orcan Ogetbil" <oget.fedora(a)gmail.com> wrote:
> On Sun, Aug 9, 2009 at 10:11 PM, Dimitris Glezos wrote:
> > On Sun, Aug 9, 2009 at 11:46 PM, Orcan Ogetbil wrote:
> >> Hello list,
> >> The new FedoraStudio feature we will have with F-12 comes with an
> >> optional multimedia-menus package. By installing this package,
> >> will have a categorized Sound&Video/Multimedia menu in their
> >> menu.
> >> The names of these submenus are defined in .desktop files. It
> >> to be that the Name and Comment keys in these .desktop files need
> >> translations. We have about 20-22 strings waiting for translation.
> >> couldn't find a way to make Transifex talk to .desktop files maybe
> >> because I am not much familiar with it. I was advised on IRC to
> >> on this list.
> > If there's a tool to convert a .desktop file into a POT file, and
> > host this on fedorahosted, we could set it up pretty easily.
> Alright. I believe that I can produce a .pot file from the .desktop
> files via xgettext. How about the other way around? Is there a .po
> file parser that I can use to put the translated strings back into
> .desktop files?
> For instance, assume that we have a .desktop file with the line:
> Now, after the translations are done, (.desktop -> .pot -> .po ->
> .desktop) I want these lines added to the .desktop file:
> If there's such a parser, I can write a simple Makefile to generate
> the final .desktop files. Otherwise I'll write my own parser.
You can do this extraction/merging easily with intltool, and let translators work with PO files.
You might find a better reference to this in the Gnome or Intltool documentation, but here's a 1-minute overview:
1) In your ./my.desktop.in file, prepend localizable entries with '_'
_Name=Name of Application
2) Create a ./po directory and create a POTFILES.in file where you add 'my.desktop.in' to the list of source-files
3) Now you can run in your ./po directory
You will now have a POT file in you ./po directory for translators to translate
4) After translation, you can merge changes back into your my.desktop file doing something like:
intltool-merge -d po my.desktop.in my.desktop
Feel free to catch me on IRC if you need any clarification.
Russian, German, Hungarian, Japanese and Polish translation have been
completed 100%. Thank you!!
Those now have been pushed to Web. It should be available within 6 hours.
For Russian, there were two tag errors preventing build and they have
been fixed. The fixed PO file has been committed in the repo, so for
next time please remember to checkout the file before working.
-------- Original Message --------
Subject: [Fwd: Re: Question on translation-quick-start-guide]
Date: Fri, 07 Aug 2009 16:37:09 +0200
From: Piotr Drąg <piotrdrag(a)gmail.com>
To: Noriko Mizumoto <noriko(a)redhat.com>
Noriko, would you take care of this? Updated translations are already split.
------ Wiadomość oryginalna ------
Temat: Re: Question on translation-quick-start-guide
Data: Fri, 07 Aug 2009 16:35:05 +0200
Nadawca: Piotr Drąg <piotrdrag(a)gmail.com>
Adresat: lerkru(a)gmail.com <lerkru(a)gmail.com>
W dniu 07.08.2009 16:22, lerkru(a)gmail.com pisze:
> 2 days ago, i upload russian translation of
> --translation-quick-start-guide--, but some line in this text is not
> translated (on web). Why?
That's because it's not an automatic process, and Noriko (TQSG
maintainer) did not publish it yet. I'll let her know you finished your
The new FedoraStudio feature we will have with F-12 comes with an
optional multimedia-menus package. By installing this package, users
will have a categorized Sound&Video/Multimedia menu in their desktop
The names of these submenus are defined in .desktop files. It appears
to be that the Name and Comment keys in these .desktop files need
translations. We have about 20-22 strings waiting for translation. I
couldn't find a way to make Transifex talk to .desktop files maybe
because I am not much familiar with it. I was advised on IRC to write
on this list.
You can find the source tarball for the multimedia-menus package in
. So, what would be the best way to proceed?
When: 2009-08-12 at 17:00 UTC (1 PM EDT/10 AM PDT)
Next Wednesday we are scheduled to have the Release Readiness meeting
for the Fedora 12 Alpha. I'm hoping representatives from each of the
teams will be able to attend. Please discuss with your teams to see if
there are any issues they would like to bring forward. This cross team
meeting is held to coordinate and discuss release day issues in real
time and to make sure we are ready for a smooth release day.
The following list shows the people that represented these teams in past
releases. If you cannot attend or no longer wish to represent your team
please coordinate and alternate and let me know.
>> I still need to know who is representing the translation team <<
Ambassadors -- David Nalley
Design -- Máirín Duffy
Documentation -- Eric Christensen
FESCo -- Jon Stanley
Fedora Engineering Manager -- Tom "Spot" Callaway
Fedora Project Leader -- Paul Frields
Infrastructure -- Mike McGrath
Marketing -- Mel Chua
Quality -- James Laska
Release Engineering -- Jesse Keating
Translation -- ??
Websites -- Ricky Zhou
I will send conference call information privately next week. A recap of
this meeting will appear on this list.
My name is Javier. I am from Spain and I'd like to help translating Fedora to spanish. I am System and Network admin at Public University of Navarre at Pamplona where we are using linux since 1995. May FAS username is jfdezl.
My GPG key and fingerprint:
pub 1024D/827FD232 2009-06-12
Key fingerprint = DA95 8948 897B 22B7 97F3 03D8 7FD3 9B0C 827F D232
uid Javier Fernandez Landa <jfdezl(a)gmail.com>
sub 2048g/5716A07E 2009-06-12