updates in .pot files of system-config-language package
by pravin.d.s@gmail.com
Dear All,
Due to some problems of system-config-language package i have
regenerated .pot file, so i request all the localization team member please
update the corresponding .po files.
Let me know if anything to do from my side.
Thanks & Regards,
------------------
Pravin Satpute
14 years, 7 months
Re: Installation Guide .pot strings out of order
by Ruediger Landmann
On 09/17/2009 01:34 AM, John J. McDonough wrote:
> ----- Original Message ----- From: "Tomek Chrzczonowicz"
> <chrzczonowicz(a)gmail.com>
> To: <fedora-docs-list(a)redhat.com>
> Sent: Wednesday, September 16, 2009 10:56 AM
> Subject: Installation Guide .pot strings out of order
>> the order of strings in .pot files (translation templates)
>> doesn't match the one in the source text
> The current version of Transifex requires us to jump through all sorts
> of hoops to create the pot files. It is unlikely that we can maintain
> the order, even if it were a permanent fix. The problem should be
> corrected with the updated tfx. We had hoped to see the updated
> version in time for F12 but I guess that isn't going to happen.
Hi Tomek,
What John says is correct, but I'll try to explain with slightly more
detail. (I'll explain from first principles, so please be patient if
you already know some of this!)
All of our longer texts are made up of multiple XML files. This makes
them easier to write and to maintain, especially when more than one
person works together on a text. In the case of the Installation Guide,
this amounts to around 700 separate files.[1]
Our publication tool, Publican,[2] then transforms each of these XML
files into a POT file, and then into PO files for each language. The
order of the strings in the POT files and PO files matches the order of
the strings in the original English XML files. You can see Publican's
set of POT files for the Installation Guide here [3] and Publican's set
of Polish PO files here [4].
Normally, these files are what translators of Publican documents should
be working with. However, the version of Transifex in Fedora (version
0.5) does not support more than *one* POT file for the document, and
*one* PO file per language.
To work around this limitation, we have used msgcat[5] to merge all the
POT files into one giant POT file (nearly 4,000 strings!) and merge all
the PO files for each language into one giant PO file for each language.
Msgcat groups the strings from the individual POT/PO files primarily in
*alphabetical order of the name of the original POT/PO file* (which of
course, is the same as the name of the XML file from which each POT/PO
file was generated originally). This is why you are seeing strings in an
order different from how they appear in the published book. However,
/within/ each of those groups, the strings do actually occur in the same
order as they do in the source text.
To finish the story, once translators have finished their work, we must
then split up the giant PO files into the individual, small PO files
again so that we can publish the translated book. Unfortunately, the
whole process is not 100% reliable, and occasionally, a few translated
strings get lost in the process of merging all the PO files together and
splitting them apart again.
Sometime after the release of Fedora 12, the Fedora Project is due to
upgrade to Transifex 0.7. This supports multiple POT files and multiple
PO files per language, meaning that translators will have access to the
PO files generated by Publican itself. Note that this doesn't completely
solve your problem if you want to work on a book in exactly the same
order as the text will appear in the finished book, because if you want
to work that way, you will need to identify which of the 700 PO files
contains the text that you want to work on. The easiest solution would
be to grep through the directory until you find the file that you want
(this is also how we writers find sections that we need to correct or
update). Of course, you can also use Gtranslator or Lokalize to search
for the string in the huge PO files that we have now.
Hope this helps, and as always, thank you! for the hard work and
dedication that you put into translating our docs.
Cheers
Ruediger
[1]
http://git.fedorahosted.org/git/docs/install-guide.git?p=docs/install-gui...
[2] https://fedorahosted.org/publican/
[3]
http://git.fedorahosted.org/git/docs/install-guide.git?p=docs/install-gui...
[4]
http://git.fedorahosted.org/git/docs/install-guide.git?p=docs/install-gui...
[5] http://www.gnu.org/software/hello/manual/gettext/msgcat-Invocation.html
14 years, 7 months
Self-Introduction: Filip Slunecko
by Filip Slunecko
Hi,
My name is Filip Slunecko, and I'm from Brno, Czech Republic..
My FAS name is slune and I'd like to help with translation into
Czech. I work as IT professional.
I've been using Fedora for a 4 years now, and I'd like to give
something back to community.
I've never worked for Fedora project.
I have programming experience in Python.
GPG fingerprint:
pub 1024D/04672CB8 2009-09-01
Key fingerprint = 62BB D686 5C03 133B 79D0 BB29 7016 FB25 0467 2CB8
uid Filip Slunecko <filip.slunecko(a)gmail.com>
sub 2048g/5181900C 2009-09-01
Best regards
14 years, 7 months
Re: transifex committing wrong translations to elfutils
by Noriko Mizumoto
Roland McGrath さんは書きました:
>> msgid: '%' is only meaningful with the 'x' option
>>
>
> That was indeed a typo in our format string (meant to be %c).
> Thanks for catching that! I've fixed it in the latest git tree
> on our fedorahosted repo.
>
Thanks! I see now fixed PO.
> It would be nice if the canonical po/Makefile's "make check"
> would do something that would catch those msgfmt errors in the
> package build before it gets to the translators.
>
I am not sure, but l10n infra team (Dimitris, Asgeir, etc) may be able
to have some idea on this?
noriko
14 years, 7 months
system-config-kdump translation in new branch
by Ankit Patel
Hi all,
There is a new branch called 'new' created for system-config-kdump for
Fedora 12. However, there are no changes with respect to translation.
So, I have updated the transifex component to accept the translations to
'new' branch.
I can only notice "Danish" translation being pushed in the 'master'
branch recently. So, if "Danish" team would like to take a moment to
merge the translations from 'master' branch to 'new' branch would be
great. Would like to request other language teams to verify whether
their translation files are showing correct status. Let me know, if you
want me to merge it for you.
Thanks!
--
Regards,
Ankit Patel
http://www.indianoss.org/
http://www.ankit644.com/
14 years, 7 months
Fedora Translation Schedule - Action Items (Trans, Devel, Rel-eng).
by Ankit Patel
Hi all,
As you might have already noticed an email from John Poelstra regarding Fedora
12 Translation Schedule, there are couple of changes introduced for the first
time in the schedule to help FLP translators.
Earlier schedule tasks (related to translations) used to be:
- Software string freeze (For Developers, changes to the translatable messages
file will require FLP's approval)
- Software Translation Period (For Translators, to complete the translation of
Fedora packages)
- Software rebuild packages (For Packagers, to rebuild packages with latest
submitted translations).
Now, it is changed to,
- Software string freeze (For Developers, changes to the translatable messages
file will require FLP's approval)
- Software Translation Period (For Translators, to translate Fedora packages)
- Software rebuild packages (For Packagers, to rebuild packages with latest
submitted translations - For Translators' review).
- Software Translation Review Period (For Translators, to review translation of
Fedora packages)
- Software rebuild packages (For Packagers, to rebuild packages with latest
submitted translations - Final rebuild).
Schedule in detail:
http://poelstra.fedorapeople.org/schedules/f-12/f-12-trans-tasks.html
These changes were basically introduced to overcome issues like,
- translators are not able to review their translations
- translators are most of the time clueless on whether their translations will
be included in the latest package or not.
More details: https://fedorahosted.org/fesco/ticket/243
Since these changes are introduced for the first time in Fedora schedule, it
needs to be communicated to all affected groups. I had a discussion with noriko
and mishti today morning and we listed down major actions as mentioned below.
Let's know if you find any modification to it or you would like to help with any
of it.
*List of action items:*
1. Request John Poelstra to update the schedule with correct entry - "Build
packages for which Fedora is upstream for all language translators' review &
correction"
2. Request John Poelstra to communicate to devel-list about this newly added entry
3. File Tracker Bug and bugs against respective packages (will start from 10th Sept)
-> Make sure you mark the bugs as "High Priority" bugs
-> Make sure you explain the reason to the package maintainer properly that the
rebuilt package should reach to end users and should be released under Fedora.
4. Request developers individually to help with the bugs, since they might not
be aware of this new change
5. Once Package Maintainers rebuild the packages by due date (14th Sept),
request Release Engineering to release those rebuilt packages.
6. Get in touch with any of the release engineers to ensure they help us with this.
7. Closely monitor whether the packages are actually rebuilt & released or not.
8. Inform FLP (translation) team again after the package rebuilds.
9. FLP members will do 'yum update' on their rawhide machines to review their
translation and submit updated translation through transifex by 22nd September.
Thanks!
--
Regards,
Ankit Patel
http://www.indianoss.org/
http://www.ankit644.com/
14 years, 7 months
Fedora 12 Translation Schedule Reminder
by John Poelstra
Name Start End
Translate Beta Release Notes Tue 2009-09-08 Thu
2009-09-17
Build F-12 collection packages for all language translators Thu
2009-09-10 Mon 2009-09-14
Review and correct software translation in built UI Tue 2009-09-15 Tue
2009-09-22
Software: Start Rebuild all translated packages Tue 2009-09-22 Tue
2009-09-22
Software: Translation Deadline (PO Files complete) Tue 2009-09-22 Tue
2009-09-22
Software: Rebuild all translated packages Tue 2009-09-22 Tue
2009-09-29
Review and correct Beta Release Notes (daily buids html) Wed 2009-09-23
Mon 2009-10-05
Final (Beta) Freeze: Development Code Complete Tue 2009-09-29 Tue
2009-09-29
14 years, 7 months