trans February 2006

trans@lists.fedoraproject.org

10 participants
9 discussions

status on release notes translation freeze
by Karsten Wade 27 Feb '06

27 Feb '06

We are going to be one or two days late with the release notes translation freeze. The new freeze is 28 Feb. 23:59 UTC. I will send another message tomorrow night confirming this new freeze. I'm sorry about this delay. I forgot to ask for a review from a key group of Red Hat developers, and we need to give them an extra day or two to reply. Thanks for your patience, - Karsten -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Content Services Fedora Documentation Project http://www.redhat.com/docs http://fedoraproject.org/wiki/DocsProject

1 0

[RFC] Existing translations and .PO files
by Tommy Reynolds 14 Feb '06

14 Feb '06

Hello, Translators! (I've CC:'ed the F-D-L as well.) I'm reworking the I18N support in the Fedora Documentation Project tools, such as the CVS. Previously, each document has had a set of base DocBook XML files. As translations were produced, complete new sets of translated XML files were added to the CVS repository. Now, we are moving to the more familiar process of archiving only the original document XML files and the .POT/.PO files needed to produce the translated XML files using the "xml2po" and "po2xml" tools. The new make(1) infrastructure will be able to use the .PO files to create the translated XML files on-the-fly. For example, the files "en/example-tutorial.xml" and "po/de.po" will be archived but the derived "de/example-tutorial.xml" file will NOT be archived but will be considered as a temporary file. My question is this: Some FDP documents already have translated versions in CVS. Under the new process, these archived versions will be discarded in favor of the on-the-fly translation using .PO files. Q1) Have you translators kept your .PO files that were used for these translations? Q2) If .PO files are not available, is there a way to derive the .PO files from the translated files or must this be a manual process? If you have another suggestion to dealing with this, don't be shy; I may not be asking the right questions. Cheers

2 1

status of FC5 test3 release notes
by Karsten Wade 13 Feb '06

13 Feb '06

It looks as if there are no release notes ready in time to translate for test3. We have been completely restructuring the build environment for the release-notes module. This must be done by tomorrow for the ISO, and there is not going to be time to get the XML translated. The translatable XML files are not changing content, but the XML tags and build environment are changing. If you wish to attempt to translate these files anyway, we are going to include in the ISO every language that builds. Sorry about this situation. We should be fixed within a few days to allow for a smooth process for FC5 final release. - Karsten -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Content Services Fedora Documentation Project http://www.redhat.com/docs http://fedoraproject.org/wiki/DocsProject

2 3

.po files available from Fedora Documentation Project
by Karsten Wade 08 Feb '06

08 Feb '06

We have recently added a 'make po' target to the Makefile for Fedora Documentation. We don't understand enough about how you perform difference checking with .po files. Is there a step that we should be doing here? Or is it a manual diff the translator runs? <megacoder> Step 1: You have an XML file. <megacoder> Step 2: make po. <megacoder> Step 3: add translations to .po file. <megacoder> Step 4: touch the original XML file. <megacoder> Step 5: make po. <megacoder> Step 6: see all previous content to PO file replaced by blanks. <stickster> Right, you'd have to have an intermediate diff in there <megacoder> As long as they know to do this step manually. Thanks - Karsten -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Content Services Fedora Documentation Project http://www.redhat.com/docs http://fedoraproject.org/wiki/DocsProject

4 3

Linux In URDU.
by Nayyar Ahmad 06 Feb '06

06 Feb '06

Hi, I have started working on Linux URDU Translation, the translation team is: 1. Nayyar Ahmad (me) :) 2. Sohail Riaz we had started it as a part time activity, but after some days spending with translation, we have now decided to do it on full time bases, for the reason, i have requested one of my friend in Japan, and he have donated me a domain and web-hosting-space i.e. linuxinurdu.org I am now searching a few dollars donation to buy two PCs and for Pocket Money :). this will help me to give full concentration to translation project. if i could get some small donation, I hope we will succeed pretty soon. I personally request you all to find few dollars donation for this project. I am very much thank full to MR. ALAM , he really did help me. Thanks, -- Nayyar Ahmad

1 0

Just a thought...
by Richard Allen 06 Feb '06

06 Feb '06

When committing files to the CVS that are fully translated the system promptly sends me an email letting me know that my file is now in "QA" state. This functionality is just great but I usually know when I'm finished anyway :) What I'd like to see added here is a mail when my files are no longer "Finished". This way I (we) could jump on changes as soon as they happen and I'm sure that would benefit us all. -- Rikki. -- RHCE, RHCX, HP-UX Certified Administrator. -- Solaris 7 Certified Systems and Network Administrator. Bell Labs Unix -- Reach out and grep someone. Those who do not understand Unix are condemned to reinvent it, poorly.

1 0

Another question
by Paul W. Frields 05 Feb '06

05 Feb '06

Our documentation building process requires an additional file "rpm-info.xml" that contains metadata about the document, such as revision history, title, authors, etc. The way things stand now, translators should edit this file directly, adding translations like: <translation lang="en"> <title>Example Tutorial</title> <desc>How we do it</desc> </translation> <translation lang="de"> <title>Beispieltutorial</title> <desc>Data data data...</desc> </translation> I am just now learning how translation works, thanks to Manuel Ospina's Translation Quick Start Guide. Would it be easier for translators if we moved to using "rpm-info-en.xml", "rpm-info-de.xml", etc.? Comments welcome. -- Paul W. Frields, RHCE http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 Fedora Documentation Project: http://fedora.redhat.com/projects/docs/

3 8

Release Notes Translation Process
by Pawel Sadowski 05 Feb '06

05 Feb '06

Hi, I have a question connected with translating release notes. I want to make a Polish translation of relnotes and I don't particularly know how to do it. I've heard, that now the only right way to translate relnotes is via Wiki. Is it true? I started translating XML files from CVS. Will it possible to translate relnotes like in this way? Cheers, Pawel Sadowski (McGiwer)

1 0

trans freeze slips one week
by Karsten Wade 04 Feb '06

04 Feb '06

Because FC5 test3 is slipping one week ... and also because I don't have the new XML files from the Wiki yet ... New trans freeze for test3 relnotes is 6 February 2006, this coming Monday, at Midnight UTC. http://fedoraproject.org/wiki/DocsProject/Schedule#preview I will send out a status update announcement by 08.00 UTC on Monday (5 Feb.). - Karsten -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Content Services Fedora Documentation Project http://www.redhat.com/docs http://fedoraproject.org/wiki/DocsProject

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

trans February 2006