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] Bugs to fix in translations

2013-08-26 Thread Tom Davies
From: Andras Timar To: Sophie Cc: LibreOffice-l10n Sent: Monday, 26 August 2013, 9:19 Subject: Re: [libreoffice-l10n] Bugs to fix in translations 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,

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 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 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] 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 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-21 Thread Xuacu
Fixed in ast for 4.1 & 4.0 by changing function name from TIME>HORA to TIME>TIEMPU (conflict with HOUR>HORA) I also changed related translations, but still have to do a second pass to make sure I didn't miss something. Regards -- Xuacu On Mon, Aug 19, 2013 at 11:27 PM, Andras Timar wrote: > Hi,

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

2013-08-20 Thread Andras Timar
Hi Chris, On Tue, Aug 20, 2013 at 3:46 PM, Chris Leonard wrote: > Consider adding a check for mismatched terminal newlines. In other software > builds, this type of error can be fatal, not sure about LO. "newlines" and > "endwhitespace" pofilters can catch this, but as a build killer, a special

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

2013-08-20 Thread Donald
On 20/08/13 20:27, Andras Timar wrote: > Hi, > > On Tue, Aug 20, 2013 at 10:06 AM, Donald wrote: >> Thanks for doing that. >> You reported that in EO, NESIMETRIECO is duplicated, but Pootle did not >> find it (I presume it is the UI of 4.1) >> I have grep-ed my local copy of the files for it and

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

2013-08-20 Thread Chris Leonard
Consider adding a check for mismatched terminal newlines. In other software builds, this type of error can be fatal, not sure about LO. "newlines" and "endwhitespace" pofilters can catch this, but as a build killer, a special check might be useful. On Mon, Aug 19, 2013 at 5:27 PM, Andras Timar

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

2013-08-20 Thread Andras Timar
Hi, On Tue, Aug 20, 2013 at 5:49 AM, Christian Kühl wrote: > In German you searched out, that two Calc function names are translated > identically, although they are different in English: EFFECT and EFFECTIVE. > > In Calc the EFFECT function becomes EFFECT_ADD during the EFFECTIVE > function keep

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

2013-08-20 Thread Andras Timar
Hi, On Tue, Aug 20, 2013 at 10:06 AM, Donald wrote: > Thanks for doing that. > You reported that in EO, NESIMETRIECO is duplicated, but Pootle did not > find it (I presume it is the UI of 4.1) > I have grep-ed my local copy of the files for it and not found it. > Where I should look for it? http

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

2013-08-20 Thread Donald
On 20/08/13 09:27, Andras Timar wrote: > Hi, > > 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. Uni

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

2013-08-19 Thread Mihovil Stanic
Hi, You marked croatian HR locale as affected, but I don't see any strings in txt file. I'll correct 4.0 version, forgot to change Heading / Title problem there. Best regards, Mihovil Dana 19.8.2013. 23:27, Andras Timar je napisao: Hi, Pootle has many checks, but there are cases which are n

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

2013-08-19 Thread Christian Kühl
Hi Andras! Am 19.08.2013 23:27, schrieb Andras Timar: 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: 2. Unique spreadsheet function