Re: organizing CVS for trans

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

I have prepared translation of FC4 Rel Notes into Russian.

And I saw that .po based translation does not works well because
some translations are context dependent. 

The second reason for pure XML translation: currently I can not
successfully convert FDP xml files into .pot and back without
some works by hand. 

But XML translation requires some additional steps like FC translation project do:
- pre commit check and XML validation
- some locking to prevent race conditions for translators

And one more question: how we will translate legal entities like copyright statements?

Regards,
Andrew Martynov
Inventa
Translator to Russian

On Thu, Aug 25, 2005 at 09:24:08AM +0800, Yuan Yijun wrote:
> 2005/8/25, Noriko Mizumoto <noriko@xxxxxxxxxx>:
> > Hi docs team
> > 
> > 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.
> > 
> 
> agreed. If you are using fedora then you have a common encoding UTF-8,
> no convertion is made or needed. But someone uses windows...
> 
> I prefer po and we have cvs repositories to store po files. Then we
> can just commit the xml files, as long as the tools that fedora-docs
> promised are good enough (e.g. if I changed po slightly, the result
> xml/HTML should not change tooo much).
> 
> -- 
> bbbush ^_^
> 
> -- 
> 
> fedora-docs-list@xxxxxxxxxx
> To unsubscribe: 
> http://www.redhat.com/mailman/listinfo/fedora-docs-list

-- 

fedora-docs-list@xxxxxxxxxx
To unsubscribe: 
http://www.redhat.com/mailman/listinfo/fedora-docs-list

[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Red Hat 9]     [Yosemite News]     [KDE Users]

  Powered by Linux