On Sun, Dec 26, 2010 at 12:20 AM, Sophie Gautier <[email protected]> wrote: > On 24/12/2010 16:36, Kinshuk Sunil wrote: >> I am interested in contributing documentation and Hindi (India) >> localisation > > Concerning localization, I'll answer your other mail on the l10n list. > Concerning the documentation, we do not have a translation process yet. You > can either create you own documentation in your language or translate the > documentation that is available. > > Next week I'll test a process that could allow us to convert and to upload > the documentation files (from .ods file format) to Pootle (in .xlf file > format) to be able to work with our translation tools or directly in Pootle > and make the conversion back in .ods when it's over.
Hi Kinshuk, We at the documentation team have not yet decided on the tooling or method for Documentation management. We are a very young community, and as such just starting to develop this infrastructure. If you wish to translate the existing English documentation into Hindi I am sure we will be able to integrate with the infrastructure when it has been commissioned. Our current workflow has only been established for the English documentation, however I am personally working on a proposal to truly internationalise the documentation development. If you wish to put in the effort to translate the documentation into Hindi prior to the LibreOffice 3.3 launch I would suggest downloading the ODT of the file you want to translate, then using Google Translate to create a first pass, very rough translation of the PDF file available on the wiki. You could then copy the translated text back into the English ODT file in order to maintain official formatting, tables, images and figures, from which you could modify the text to suit the Hindi user base. Although there has been no official decision, I would expect that the documentation team requires that formatting, layout, colours must remain the same across languages (Localised fonts excepted, but if substituted, an open font would be much preferred). An example of using Google Translate to create a first pass is: http://translate.google.com/translate?js=n&prev=_t&hl=en&ie=UTF-8&layout=2&eotf=1&sl=en&tl=hi&u=http://wiki.documentfoundation.org/cgi_img_auth.php/c/c2/0101GS3-IntroducingLibO.pdf Simply go to http://translate.google.com Paste the web address of the PDF file into the box and press translate. I would strongly advise against 'creating your own' documentation, as has been suggested, as this would most likely not integrate well with the official documentation workflow once established. Thanks for your interest, and we are working hard to get the infrastructure set up which properly reflects our multicultural, multilingual community. शुक्रिया Michael Wheatland -- Unsubscribe instructions: E-mail to [email protected] List archive: http://listarchives.libreoffice.org/www/documentation/ *** All posts to this list are publicly archived for eternity ***
