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.
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.
Addition to this, CJK (aka chinese, japanese and korean) may have more
convertion problem sometime apart from their translation. If we can have
separate files for each lang, it will be easier to fix this kind of problem.
I am an idiot.
Ich bin ein dumbkoff
le nulles, moi
Thanks for listening
Paul W. Frields wrote:
On Wed, 2005-08-24 at 13:58 -0500, Tommy Reynolds wrote:
>Uttered "Paul W. Frields" <stickster(a)gmail.com>, spake thus:
>>Just my $0.02 -- I think this is the best solution also technically, but
>>the only thing I would be worried about is contributors who
>>inadvertently screw up translated sections (errant keystrokes, etc.) and
>>don't know that they've done so since they can't read the text. Does
>>this approach gain us enough to balance out that risk? Otherwise, I
>>think it's a super idea.
>I think the "who touches last owns" rule applies. You break the
>build, you fix the build. Anyway, we've got CVS backup for the
Yeah, I figured as much. I can live with that if everyone else can. ;-)