Re: [l10n-dev] OpenOffice.org 3.0 - Translation Schedule
Op Dinsdag 2008-02-05 skryf Reiko Saito: Hi Aijin, Thank you so much for your information and update to the user guide. I realized you added the section Localized Documents for me. -- I had added link JapaneseTranslation for JA community :-) Let me translate the additional part and ask you if I have any question. Regards, -Reiko Hallo Reiko, and thank you for your contribution to the documentation. I wanted to suggest a different name for the article though, since the name doesn't suggest that it has something to do with the Pootle user guide :-) Perhaps something like [[Pootle User Guide/ja]] or [[あてもなくユーザー ガイド]] (from Google machine translation :-) Or is there already a policy on the wiki for handling translations? The translations linked to from the front page does not seem to use a consistent way of naming the translated articles, but I guess the native name is good. If it is moved, I'll also link to it from the Pootle wiki site, for the benefit of all Japanese Pootle users. http://translate.sourceforge.net/wiki/pootle/index Keep well Friedel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] Make wiki information more accessible
Hello! I was trying to figure out how to localise OO to Kannada(kn) and I feel that it will be good if the information regarding access to POT files is put somewhere on the main page itself. I have spent nearly 2 weeks and quite a bit of download only to realise that you can get the files here - ftp://ftp.linux.cz/pub/localization/OpenOffice.org/devel/ Of course, a general re-organisation of information may also be necessary. Thank you. Regards, -- Vikram Vincent +919448810822 http://www.swatantra.org/ http://translate.swatantra.org/
[l10n-dev] Re: Make wiki information more accessible
Hello again, Is there any info on which files could be translated first in order to get some quick results? Thanks again. Regards -- Vikram Vincent +919448810822 http://www.swatantra.org/ http://translate.swatantra.org/
Re: [l10n-dev] Make wiki information more accessible
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sankarshan Mukhopadhyay wrote: | It is a wiki at the end of the day - why don't you add the relevant | information into an existing page or create a new page so as to help | others who might face the same issue ? :) and do check up the Native Language Team Lead from http://l10n.openoffice.org/languages.html and coordinate with them towards translations ~sankarshan -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFHqaNU+g4kmZ76nyERAnA6AJ4yOk5rOiptDj+uueiEjfD480qmtQCdGtTq +ROvgqZPwfUaks9CS8Uy9k0= =mr5x -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Re: Make wiki information more accessible
Op Woensdag 2008-02-06 skryf Vikram Vincent: Hello again, Is there any info on which files could be translated first in order to get some quick results? Thanks again. Regards There are a few tricks that you can try. When you have your tree of PO files, you can prioritise the modules/directories. Remember that you can use pocount to give you a good idea of the number of words and units in a set of files. http://translate.sourceforge.net/wiki/toolkit/pocount As a start, you probably want to skip the help files (helpcontent2) entirely at the start. Identify some programs in OpenOffice.org that you want to do first. You might (for example) prioritise Writer over the other programs. Things like the macro editor is probably the last priority. With some help from people in the know, you should be able to compile a list of modules/directories that are necessary for the translation of your chosen tool(s). You might also want to do the short strings first: http://translate.sourceforge.net/wiki/guide/short_strings_first You also want to make sure you gain as much as possible from translation memory to reuse the things that you have done in the project (or other previous projects). This can save some time, but also helps with consistency. Another time saver is terminology like Pootle does during translation. It makes it easier for inexperienced people to contribute without knowing all terminology before they start. I hope this is of some help. Keep well Friedel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Re: Make wiki information more accessible
Hello Friedal, F Wolff wrote: big snip I hope this is of some help. Thanks a lot. It has definitely been helpful. Regards, -- Vikram Vincent +91 9448810822 http://www.swatantra.org http://translate.swatantra.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Pootle: L10n Meeting on IRC - 5-02-2008
done :-) . You can find the log at: http://wiki.services.openoffice.org/wiki/IRC_Meetings - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Make wiki information more accessible
Hi, I saw you already receive some good information on how to proceed ... but just in case, here is a wiki page which has been set up exactly for the ones who are new to the project at: http://wiki.services.openoffice.org/wiki/NLC:New_Translators_Start_here Also, various information on l10n can be found at: http://wiki.services.openoffice.org/wiki/Category:Localisation Regarding a reorganisation of l10n inforamtion ... yes you are perfectly right and we will be working on that in the next weeks. Regards, Rafaella Vikram Vincent ha scritto: Hello! I was trying to figure out how to localise OO to Kannada(kn) and I feel that it will be good if the information regarding access to POT files is put somewhere on the main page itself. I have spent nearly 2 weeks and quite a bit of download only to realise that you can get the files here - ftp://ftp.linux.cz/pub/localization/OpenOffice.org/devel/ Of course, a general re-organisation of information may also be necessary. Thank you. Regards, - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
