> Yes and sometimes also translating off line. The offline translating is another bit of fun :-) This process (as it evolves) done by those of us in the Doc Project and the L10N project is nto as much of an immediate issue. It does need work and a lot of refining but the people working on this side of things are not replacing text in the original pages with translated content :-)
> What we (l10n teams) would like to have his a conversion to .po or xliff > so that we can work with our translation tools and most important our > translation memory. This ensure consistency between the UI, help files > and the documentation because we use the same glossary/terminology for > them. > We have discuss this during OOoCon. But the export/import filters are > not going very well from what Rafaella told us. > It seems to be possible to export wiki content to .po, this is used for > translating offline mediawiki extensions. See the page here : > http://translatewiki.net/wiki/Translating:Offline > but I don't know how it would be manageable for us. If there is anything that we need to try out to possibly make the more formal translation process move along move efficiently, we should look into it. Installing an extension for testing is not hard... I just need to know which one, and have someone available to test it (particularly in the case of translations). C. -- Clayton Cornell ccorn...@openoffice.org OpenOffice.org Documentation Project co-lead StarOffice - Sun Microsystems, Inc. - Hamburg, Germany --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@documentation.openoffice.org For additional commands, e-mail: dev-h...@documentation.openoffice.org
