docs translation

[Tammy Fox]

On Sun, Sep 29, 2002 at 11:29:39PM -0300, Rodrigo Del C. Andrade wrote:
> 
> 	Hello Tammy, Paul and all doc writters and translators.
> 	First and foremost I wish to say that I'd never participated before 
> 	of any projects of this kind or even had any role on the RH community 
> whatsoever, but I am very willing to help and its never late to start, 
> so I'll add some cents in this to get the discussion going. Feel free to 
> hammer my feelings if you feel like it, I can bear it as long as its 
> good for the FC.
> 
> Tammy Fox wrote:
> >This would be the place. We currently don't have a process for it, but
> >I would love to hear your ideas for it such as:
> >
> >1. CVS location -- separate or in the same module as the original version
> 
>     The same location has its advantages, but as long as we're talking 
> about diferent trees, so no translator would have write access to a 
> writer's doc and accidentally do some nasty thing. I know the cvs can be 
> "rewinded", but taking vacines is better than antibiotics, isnt it?
> 
> 	Something like
> 	
> 	/
> 	/en_docs (original)
> 	/en_docs/burning_cds
> 	...
> 	/es_docs
> 	/es_docs/grabando_cds
> 	...
> 	/pt_br_docs
> 	/pt_br_dos/queimando_cds
> 
> 	Etc. or the code for each language.
> 	I am not a CVS expert, and my desk is buried in 3 feet of crap, so 
> 	what you think?
> 
> 

For the RHEL docs, for each English module, there is a corresponding
module for each language the English module is translated into. It
works out well. We also us po files. As files change, the po files in
the translation modules are updated so that the translators know to
translate the new or changed content. Maybe each writer should be
responsible for updating the po files like in software
translations. Each translator could monitor the commits to module
containing the po files she is responsible for. Of course, we need a
CVS server that allows non-RH people to commit first -- we are still
working on that.

> >2. Method -- there are tools to convert from XML to PO and back to XML -- 
> >probably the best choice
> 
> 	Posting these tools on Translations Project on fedora.redhat.com 
> 	with some, even if small, tutorial/quick guide/tips thingie would be a 
> start, I guess.....
> 

Sure. Paul and Sarah are the people for this. I just know generally
how it works.

> >3. Process for alert translators of new and changed content
> 
> 	hmm... The docs list?
> 	Something that bothers me a lil more than this is actually defining 
> who's onto what. It would be a waste if 2 ppl get the same doc to 
> translate to the same language, without knowing of each others effort. 
> We gotta define something about that.
> 

Yes. We need a way for people to volunteer for translations and a way
to clearly mark that doc as taken. Other projects do this with a
website that shows the progress and the owner.

> 	Well, lets evolve this into a nice organized multi-cultural project!
> 	Cheers!!!
> 
> 	Vantroy
> 
> 
> >
> >Cheers,
> >Tammy
> >
> >On Mon, Sep 29, 2003 at 01:59:13AM -0300, Luiz Rocha wrote:
> >
> >> Is here the best place to talk about translation of documentation 
> >>(developer's guide, documentor's guide) or is in the fedora-devel list?
> >>-- 
> >>Luiz Rocha <lsdr at lsdr.net>
> >>
> >>
> >>--
> >>fedora-docs-list mailing list
> >>fedora-docs-list at redhat.com
> >>http://www.redhat.com/mailman/listinfo/fedora-docs-list
> >
> >
> >
> >--
> >fedora-docs-list mailing list
> >fedora-docs-list at redhat.com
> >http://www.redhat.com/mailman/listinfo/fedora-docs-list
> >
> >
> 
> 
> --
> fedora-docs-list mailing list
> fedora-docs-list at redhat.com
> http://www.redhat.com/mailman/listinfo/fedora-docs-list

--