Re: [libreoffice-l10n] Bugs to fix in translations

2013-08-26 Thread Rimas Kudelis
Hi, 2013-08-20 00:27, Andras Timar rašė: Pootle has many checks, but there are cases which are not covered. You may remember the style name localization issue from last month. Therefore I wrote a tool which checked three types of translation errors: 1. Unique style names. 2. Unique spreadsheet

Re: [libreoffice-l10n] Bugs to fix in translations

2013-08-26 Thread Mihovil Stanic
I agree with that, but some locales got their users used to localised function names. MS Office function names are not localized for croatian, nor we localise it. It's hard to find function examples and descriptions online if you use localised names and it's even harder for those transfering fro

Re: [libreoffice-l10n] Bugs to fix in translations

2013-08-26 Thread Sophie
Hi all, Le 26/08/2013 09:52, Mihovil Stanic a écrit : I agree with that, but some locales got their users used to localised function names. MS Office function names are not localized for croatian, nor we localise it. It's hard to find function examples and descriptions online if you use localised

Re: [libreoffice-l10n] Re: Bugs to fix in translations

2013-08-26 Thread Andras Timar
Hi Zeki, On Sun, Aug 25, 2013 at 10:48 AM, Zeki Bildirici wrote: > 2013/8/22 Andras Timar : > http://dev-www.libreoffice.org/l10n/error-report/report-4.0.txt http://dev-www.libreoffice.org/l10n/error-report/report-4.1.txt > > Hi Andras, > > Is it possible to have this fixes in upcoming

Re: [libreoffice-l10n] Bugs to fix in translations

2013-08-26 Thread Andras Timar
On Mon, Aug 26, 2013 at 10:09 AM, Sophie wrote: > Hi all, > Le 26/08/2013 09:52, Mihovil Stanic a écrit : > >> I agree with that, but some locales got their users used to localised >> function names. >> MS Office function names are not localized for croatian, nor we localise >> it. >> It's hard to

Re: [libreoffice-l10n] Bugs to fix in translations

2013-08-26 Thread Andras Timar
Hi Rimas, On Mon, Aug 26, 2013 at 8:33 AM, Rimas Kudelis wrote: > Furthermore, perhaps locales should at least be preseeded with the original > function names? Because its a bit dumb when our machinery "localizes" SUMIFS > as SUMIF, just because SUMIF was already "localized" as SUMIF (surprise!)

Re: [libreoffice-l10n] Bugs to fix in translations

2013-08-26 Thread Tom Davies
Hi :) Are there potential copyright issues with using their stuff?  Any idea what licensing they use?  It's possible they might use a fairly permissive license but it might be good to know if we are walking into a trap with this. Regards from Tom :)  From: A

[libreoffice-l10n] Re: Bugs to fix in translations

2013-08-26 Thread Thomas Hackert
Hello Tom, *, On Montag, 26. August 2013 13:00 Tom Davies wrote: > Are there potential copyright issues with using their stuff? Any > idea what licensing they use? It's possible they might use a > fairly permissive license but it might be good to know if we are > walking into a trap with this. Re

Re: [libreoffice-l10n] Bugs to fix in translations

2013-08-26 Thread Valter Mura
In data lunedì 26 agosto 2013 10:09:58, Sophie ha scritto: > Hi all, > > Le 26/08/2013 09:52, Mihovil Stanic a écrit : > > I agree with that, but some locales got their users used to localised > > function names. > > MS Office function names are not localized for croatian, nor we localise > > it.

Re: [libreoffice-l10n] Re: Bugs to fix in translations

2013-08-26 Thread Tom Davies
Hi :) Thanks for the links! :)  I think the page qualifies as a certain persons "personal web-page" so from what i have read so far it should be fine to use.  I'm not a legal expert either but i am a native-English reader so i can possibly read these links slightly faster than you.  So far its

Re: [libreoffice-l10n] Re: Bugs to fix in translations

2013-08-26 Thread Zeki Bildirici
2013/8/26 Andras Timar : > Hi Zeki, >> Is it possible to have this fixes in upcoming release 4.1.1? > > I pushed the fixes just in case. I don't know about another release > candidate (rc3) for 4.1.1. Your fixes will be in 4.1.2 for sure. I wish there will be a RC3, because these are serious error