Hi. I think I have used it back in the days where sun made a PC version of unix, if that could be made available it could really enhance quality of the translation.
I am right now looking into making a small program that checks for this kind of translation mishaps. I have tried POconsistency which is nice, but does not control glossary strongly enough. The one I worked with, had a lot of languages (at least all the western ones). rgds Jan I On 11 October 2012 15:54, Alexandro Colorado <[email protected]> wrote: > Back in the Sun days we used to have a Glossary that spread throughout > all products explaining the terminology on different language. It was > like an OpenGrok for terms. > > Also a style guide, which I guess we still do, is only a matter of > making available to translators. > > On 10/11/12, jan iversen <[email protected]> wrote: > > HI. > > > > I would be a good idea to have a glossary.po file for each language, even > > though the program does not use it. It is important that the translations > > are consistent (e.g. edit is translated identically throughout all > files). > > > > I would also like to have a consistency check, that automatically checks > > accelerators and words are translated identically. I have been playing > with > > poconsistency which does quite a nice work. > > > > The idea of having spreadsheets to control sorting etc. is brillant. I > used > > to have documents as well to check the functionality of the dictionary. > > > > have a nice day > > rgds > > Jan > > > > On 10 October 2012 23:57, Rob Weir <[email protected]> wrote: > > > >> Does this make sense as a general list of tasks for fully localizing > >> OpenOffice for a language? > >> > >> 1. Translate UI strings in Pootle > >> > >> 2. Verify translations in a snapshot build of OpenOffice > >> > >> 3. Verify bundling of correct dictionaries > >> > >> 4. Verify other areas of localization: sorting, number formatting, > >> date formatting, string comparisons. Anything else? Should we have > >> some standard test spreadsheets and other documents to help verify > >> these areas? > >> > >> 5. Translate help strings. > >> > >> 6. Help update/maintain native language website, e.g., > >> www.openoffice.org/de, etc. > >> > >> 7. Help translate release announcements, release notes and other > >> materials that help promote the new release > >> > >> Any thing else? > >> > >> Some languages do only 1-4, which is probably the minimum that will > >> give a good user experience. Some languages are enabled for 5-7 as > >> well. In areas where we have multiple volunteers this might be one > >> way of splitting up the effort. > >> > >> Regards, > >> > >> -Rob > >> > > > > > > > > -- > > Jan Iversen > > ________________________________________________ > > Tel. no. +34 622 87 66 19 > > jandorte.wordpress.com > > > > > -- > Alexandro Colorado > PPMC Apache OpenOffice > http://es.openoffice.org > -- Jan Iversen ________________________________________________ Tel. no. +34 622 87 66 19 jandorte.wordpress.com
