[libreoffice-l10n] Quality in l10n

2013-12-02 Thread Olivier Hallot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello As translator for LibreOffice since 2003, I often see less than optimal english strings to translate and I believe other translators also has the perception that the original english can be improved (other than typos). Although the origin of

Re: [libreoffice-l10n] Quality in l10n

2013-12-02 Thread Tom Davies
Hi :) +1 It certainly seems that way. However it also seems that the number of troublesome strings is remarkably small. People do sometimes post such strings to this list and various people are here ready to discuss what they think it means. Although some it it might look quite rough it seems

Re: [libreoffice-l10n] Quality in l10n

2013-12-02 Thread Sophie
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Le 02/12/2013 12:39, Olivier Hallot a écrit : Hello As translator for LibreOffice since 2003, I often see less than optimal english strings to translate and I believe other translators also has the perception that the original english can be

Re: [libreoffice-l10n] Quality in l10n

2013-12-02 Thread Olivier Hallot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Sophie, Em 02-12-2013 10:21, Sophie escreveu: I thought that Glade would bring more quality but what is missing the most is maybe a referential glossary for developers (or they have one that should be updated maybe). Although a good idea in

Re: [libreoffice-l10n] Quality in l10n

2013-12-02 Thread Sophie
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Olivier, Le 02/12/2013 14:04, Olivier Hallot a écrit : Hi Sophie, Em 02-12-2013 10:21, Sophie escreveu: I thought that Glade would bring more quality but what is missing the most is maybe a referential glossary for developers (or they have

[libreoffice-l10n] Duplicated strings in Pootle

2013-12-02 Thread Baurzhan Muftakhidinov
Good day, I am working on Kazakh translation on Pootle, and I see that there are so many duplicated strings there. I understand that often they are from different modules, so they have to present in each module. I am curious whether it is planned to do something with these duplicated strings.

Re: [libreoffice-l10n] Duplicated strings in Pootle

2013-12-02 Thread Andras Timar
Hi, On Mon, Dec 2, 2013 at 5:23 PM, Baurzhan Muftakhidinov baurthefi...@gmail.com wrote: Good day, I am working on Kazakh translation on Pootle, and I see that there are so many duplicated strings there. I understand that often they are from different modules, so they have to present in

Re: [libreoffice-l10n] Duplicated strings in Pootle

2013-12-02 Thread Olivier Hallot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Em 02-12-2013 15:00, Andras Timar escreveu: For example with translation memory -- which in under development for Pootle -- you never need to translate the same string twice. Well sort of... You always need to check if the TM is guessing under

Re: [libreoffice-l10n] Quality in l10n

2013-12-02 Thread Mirosław Zalewski
Dnia 2013-12-02, o godz. 09:39:49 Olivier Hallot olivier.hal...@documentfoundation.org napisał(a): Although the origin of the english strings are from the developers, and they are focused in producing code and fixing bugs more than writing beautiful english, it may be necessary that we - the

Re: [libreoffice-l10n] Duplicated strings in Pootle

2013-12-02 Thread Stanić Mihovil
When it is about one word strings, they should be translate separately. In croatian and some other languages you can translate for example word new as novi, nova, novo etc. depending on gender. Dana 2. 12. 2013. 17:24 Baurzhan Muftakhidinov baurthefi...@gmail.com je napisao/la: Good day, I am

Re: [libreoffice-l10n] Quality in l10n

2013-12-02 Thread Sophie
Hi Mirosław, Le 02/12/2013 18:37, Mirosław Zalewski a écrit : Dnia 2013-12-02, o godz. 09:39:49 Olivier Hallot olivier.hal...@documentfoundation.org napisał(a): Although the origin of the english strings are from the developers, and they are focused in producing code and fixing bugs more

Re: [libreoffice-l10n] Quality in l10n

2013-12-02 Thread Robinson Tryon
On Mon, Dec 2, 2013 at 1:03 PM, Sophie gautier.sop...@gmail.com wrote: Although the origin of the english strings are from the developers, and they are focused in producing code and fixing bugs more than writing beautiful english, it may be necessary that we - the community and in a continuous

Re: [libreoffice-l10n] Quality in l10n

2013-12-02 Thread tk
Robinson Tryon wrote: the one responsible of the en_US version. And I don't think somebody is in fact. Hmm. Sophie - should we consider spinning-up a community for en_US? I'm not sure I have much time to spend on it right now, but I could a) Can somebody layout precisely what an en_US l10n

Re: [libreoffice-l10n] Quality in l10n

2013-12-02 Thread Sophie
Hi Jonathon, Le 02/12/2013 20:22, tk a écrit : Robinson Tryon wrote: the one responsible of the en_US version. And I don't think somebody is in fact. Hmm. Sophie - should we consider spinning-up a community for en_US? I'm not sure I have much time to spend on it right now, but I

Re: [libreoffice-l10n] Quality in l10n

2013-12-02 Thread tk
Sophie wrote: a) Can somebody layout precisely what an en_US l10n team/group/individual would do? as, I said, I think the first thing is to have an up to date glossary, then check for the consistency in the menus/dialogs/tabs, check for the Camel case use, check that the good terms are