Re: organizing CVS for trans
by Noriko Mizumoto
Hi Karsten-san and docs team
Thanks for your decision of having separate xml files per language!
As quality wise, I think it would be better to have proofreader
(maintainer) for each translation same way with software translation.
To avoid confliction committing same document file in same time by more
than one translators (or maintainer), access right should be restricted
to the maintainer, I think.
Any thoughts? translators?
Btw, I discussed with Warren about this.
Ideally we'd better to have trans cvs repository apart from docs cvs.
There are several challenges to make this happen at the moment.
Cheers
Noriko
Karsten Wade wrote:
> On Thu, 2005-08-25 at 11:03 +1000, Noriko Mizumoto wrote:
>
>>Hi docs team
>>
>>I am coming from fedora-trans-list, Japanese translator, Noriko
>>Mizumoto. I am so excited hearing the news that docs team is preparing
>>to host translation. I would like to say thank you, and am looking for
>>something that I can help. Please let me know if it is recommended to
>>make self introduction as translator, I am most happy to do so.
>
>
> That would be great to do. If you have done it already, you could just
> send us a link to that self-intro.
>
>
>>To me it would be nice if translators can work on po files similar to
>>fedora software modules we are currently working, since this must be one
>>of safe way to minimize translator from messing up tags. However this
>>might be required more time of your side, I guess.
>>
>>When the format will go with inline, the file can only be translated by
>>one translator at the time and other translators have to wait for
>>her/his turn, if my understanding is correct.
>>Then it seems that this is not practical for release notes which has
>>strictly limited time-frame for both docs and trans.
>
>
> Yes, this is how the RHEL documentation is translated, with separate XML
> files per language.
>
> Despite our geekish preference for translations all in one file, it is
> clear we need to make them separate files.
>
> foo-en.xml
> foo-it.xml
> foo-ru.xml
> foo-jp.xml
> ...
>
> Should we want to combine then in the future, I bet there is some way to
> do it in Perl.[1]
>
> - Karsten
> [1] Isn't this true of everything?
>
17 years, 9 months
doc schedule for FC5
by Karsten Wade
Pardon the cross-post, this is important enough to deserve it. :)
This schedule has been discussed with translation, so should fit into
their needs.
This is more than a draft, but there is room for some change if you can
make a good case.
http://fedoraproject.org/wiki/DocsProject/Schedule
Here is the test1 excerpt for discussion:
Test1
24 Oct. Relnote content frozen for trans
28 Oct. Guides content frozen for trans
31 Oct. Relnotes freeze for trans
01 Nov. Relnotes freeze for release (ISO)
02 Nov. Final ISO spin.
04 Nov. Guides trans freeze
05 Nov. Guides frozen for release (Web)
07 Nov. Test1 release
Translation has asked for a week to do appropriate translation. This
will result in up-to-date content missing from the release notes.
Here is how we address that:
* Early requests for relnotes
* Publicize this schedule, no surprises
* First and most prominent link at the top of the relnotes points the
reader at the online version of the relnotes
* This online version will be updated the day of FC release
* Will be in CVS
* Will need translation ASAP
* This helps make the next trans cycle shorter
* Will be posted live in rolling releases
--
Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/
gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41
Red Hat SELinux Guide
http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/
17 years, 9 months
Lost of the SSH-KEY
by Eduardo dos Santos Ligieri
Hi all,
I lost my SSH-KEY, my login is eligieri.
Please help-me!
Thanks!
17 years, 9 months
INTEREST: Telugu (te)
by Muralidhar Kamidi
Actually I am a latecomer into the world of computers, and linux in
particular. But when I saw Open Source happening so happily on the Net,
I realised it is for people like me. So the basic tenets of democracy
(if it is for the people, then it must be by the people as well!)
demanded that I be a part of this moment. But I am not a programmer. So
the only way I can help this movement is either by writing
documentation, or by translating. While there are a lot of people doing
the documentation, I found nobody translating the project into my mother
tongue (telugu). So I take up the task myself.
I want to know, how to do it. Send me as many files and links as
required to learn the basics of translation procedure. I don't have a
Fedora Core distribution with me. If there are ways to do the
translation from Windows environment, tell me. Otherwise tell me where
to get the Fedora Core in India. Please don't tell me to download. My 56
kbps connection will spend years at a stretch doing that!
This is the essence of what I would like to tell you: I am interested
and enthusiastic to be the first to translate into my mother tongue.
Just tell me how!
Thank you.
17 years, 9 months
Explanation of the summary for "fence"
by Göran Uddeborg
I'm unsure of how to translate the summary for the package "fence":
fence - The cluster I/O fencing system
I'me aware of two basic meanings of "fence": a barrier around an area
and a sport involving a old style weapon I believe is called with the
French word épée. Neither quite seems to apply.
I looked at the longer description, but that didn't help me. And
there was no URL to follow.
I'm sure I just miss some nuances here. Could someone with a better
understanding explain to me what?
17 years, 9 months
Re: schedule for translating documentation
by A S Alam
Karsten Wade wrote:
> This is mainly for the release notes, but we can follow it for other
> documentation for FC5.
>
> 2 November - test1 documentation freeze
> 7 November - test1 release
> 7 December - test2 documentation freeze
> 12 December - test2 release
> 4 January - test3 documentation freeze
> 9 January - test3 release
> 1 February - FC5 documentation freeze (final)
> 13 February - FC5 release
>
> This based on the schedule found at:
>
> http://fedora.redhat.com/participate/schedule/
>
> You'll notice that the docs freeze is two days after the devel freeze.
>
> This is really only one additional day for writing beyond devel freeze,
> accounting for the dateline. This additional day gives us a chance to
> take urgent changes to the release notes right up to devel freeze, and
> have one more day to make changes.
>
> Most of the translation will be in test1. We plan to have rolling
> content available throughout the writing cycle. Following that, we
> don't expect the document to churn very much, perhaps 10% to 20% change
> (change, additions) between tests. Expect the changes between test3 and
> release to be very minimal.
>
> This schedule is subject to changes in the master schedule.
>
> What do you think? With your agreement, I'll share this with the docs
> project as our schedule.
>
> BTW, documents that you may want to translate in addition to the release
> notes, which are planned for FC5:
>
> * Installation Guide
> * Desktop User Guide
> * Managing Software with Yum
>
> thx - Karsten
>
>
>
>
Hello,
I m translating Fedora GUI (I have cvs account)
How can I start Translation for my Language?
can u please provide some Ideas about this?
thanks
AP Brar
Punjabi Translator
17 years, 9 months
schedule for translating documentation [draft]
by Karsten Wade
This is mainly for the release notes, but we can follow it for other
documentation for FC5.
2 November - test1 documentation freeze
7 November - test1 release
7 December - test2 documentation freeze
12 December - test2 release
4 January - test3 documentation freeze
9 January - test3 release
1 February - FC5 documentation freeze (final)
13 February - FC5 release
This based on the schedule found at:
http://fedora.redhat.com/participate/schedule/
You'll notice that the docs freeze is two days after the devel freeze.
This is really only one additional day for writing beyond devel freeze,
accounting for the dateline. This additional day gives us a chance to
take urgent changes to the release notes right up to devel freeze, and
have one more day to make changes.
Most of the translation will be in test1. We plan to have rolling
content available throughout the writing cycle. Following that, we
don't expect the document to churn very much, perhaps 10% to 20% change
(change, additions) between tests. Expect the changes between test3 and
release to be very minimal.
This schedule is subject to changes in the master schedule.
What do you think? With your agreement, I'll share this with the docs
project as our schedule.
BTW, documents that you may want to translate in addition to the release
notes, which are planned for FC5:
* Installation Guide
* Desktop User Guide
* Managing Software with Yum
thx - Karsten
--
Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/
gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41
Red Hat SELinux Guide
http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/
17 years, 9 months
specspo, desc, and summary
by Sarah Wang
Hi all,
As you may be all aware, specspo is being split into desc and summary.
Both set of files are being placed under "specspo/" directory. For the
languages that haven't added themselves, I have merged the existing
translations into desc and summary, and added the corresponding po
files. You should be able to see them when you do "cvs up".
For the languages that have already started translating from the
scratch, you can use the following steps to merge the existing specspo
translation into the new files (using fr.po as an example):
cd ~/translate/specspo/desc
msgcat ../fr.po fr.po > tmp1.po
msgmerge tmp1.po desc.pot > tmp2.po
mv tmp2.po fr.po
This will merge the old translations, at the same time preserve the
newly added translations into one file.
Cheers,
Sarah
17 years, 10 months
Re: Fedora-trans-list Digest, Vol 18, Issue 4
by Paul Gampe
Apologies for the delay Igor and Munzir. We would class "Red Hat Network" a
proper name and generally recommend not translating it.
I hope this helps, Paul
> > I don't know whether someone replied to your message but definitely this
> > question is worth to be considered so we have something official for
> > consistency, at least.]
>
> Nope, still waiting for an answer. Things are going rather slow in Red
> Hat's i18n department it seems.
17 years, 10 months
