You are viewing a plain text version of this content. The canonical link for it is here.
Posted to l10n@openoffice.apache.org by Dick Groskamp <th...@quicknet.nl> on 2012/07/11 17:29:36 UTC
[CORRECTION] Re: Error in Dutch version in CSV export from Calc
Op 11-7-2012 16:31, risto.i.j@saunalahti.fi schreef:
> Hello!
> I just subscribe this list.
> I made a proposal to Duch SCSTR_FIELDSEP text in Pootle. I reality
> there is two proposals, firs was not so good.
> I suppose there are some dead line for this change to have it in next
> version?
>
> Regards
> Risto
>
> Below is copy of original post:
>
> Hi,
>
> I have confirmed issue
> https://issues.apache.org/ooo/show_bug.cgi?id=120216. The problem is,
> that the export from Calc to csv does not work.
>
> I guess, that there is something wrong in the translation, therefore I
> write to ooo-l10n@incubator.apache.org.
>
> It is the string SCSTR_FIELDSEP.
>
> In nl I see
> ,\t\t44\t\t;\t\t59\t\t:\t\t58\t\t{Tab}\t\t9\t\t{spatie}\t\t32
>
> In de I see
> ,\t44\t;\t59\t:\t58\t{Tab}\t9\t{Leer}\t32
>
> There seems to be some additional \t in nl which should not be there.
> I'm not familiar with Pootle, but hope that you can find it with this
> information.
>
> Kind regards
> Regina
>
>
Regina / Ristoi,
thanks for stepping in.
I've fiound the conflicting string.
It is due to some superfluous tabs that got into the Dutch trabslation.
(As Regina saw correctly)
I noticed that tose appear when you copy the original English string to
the field for editing
I removed the superfluous tabs and adjusted the Dutch translation. I
can't check if the correction
stnds if the suggestion will be accepted, since I have no acces to Pootle.
As Ristoi did I entered a suggestion 2 (nobody)
In Ristoii's suggestions I see the removed tabs as strikethrough, which
is probably not the solution
@Juergen: please accept suggestiion #2 in segment 2609
(scstring.src#SCSTR_FIELDSEP.string.text)
to see if the suggestion stands. If not I will type
the text in the field for editing instead of copying it
from the original text
--
DiGro
Windows 7 and OpenOffice.org 3.3
Scanned with Ziggo uitgebreide Internetbeveiliging (F-Secure)
Re: [CORRECTION] Re: Error in Dutch version in CSV export from Calc
Posted by Ariel Constenla-Haile <ar...@apache.org>.
Hi Andrea,
On Sun, Jul 22, 2012 at 05:00:36PM +0200, Andrea Pescetti wrote:
> On 11/07/2012 Ariel Constenla-Haile wrote:
> >the whole concept/design is error prone there!
> >In main/sc/source/ui/src/scstring.src#483
> >483 String SCSTR_FIELDSEP ...
> >If someone files a new bug, I can take a look at it :)
>
> Thanks! Filed
> https://issues.apache.org/ooo/show_bug.cgi?id=120341
Thanks for the reminder, I completely forgot about this.
Regards
--
Ariel Constenla-Haile
La Plata, Argentina
Re: [CORRECTION] Re: Error in Dutch version in CSV export from Calc
Posted by Andrea Pescetti <pe...@apache.org>.
On 11/07/2012 Ariel Constenla-Haile wrote:
> the whole concept/design is error prone there!
> In main/sc/source/ui/src/scstring.src#483
> 483 String SCSTR_FIELDSEP ...
> If someone files a new bug, I can take a look at it :)
Thanks! Filed
https://issues.apache.org/ooo/show_bug.cgi?id=120341
Regards,
Andrea.
Re: [CORRECTION] Re: Error in Dutch version in CSV export from Calc
Posted by Ariel Constenla-Haile <ar...@apache.org>.
Hi *,
On Wed, Jul 11, 2012 at 1:34 PM, Rob Weir <ro...@apache.org> wrote:
>>> It is the string SCSTR_FIELDSEP.
>>>
>>> In nl I see
>>> ,\t\t44\t\t;\t\t59\t\t:\t\t58\t\t{Tab}\t\t9\t\t{spatie}\t\t32
>>>
>>> In de I see
>>> ,\t44\t;\t59\t:\t58\t{Tab}\t9\t{Leer}\t32
>>>
> Or is there any easy way to automate checking or preventing such errors?
the whole concept/design is error prone there!
In main/sc/source/ui/src/scstring.src#483
483 String SCSTR_FIELDSEP
484 {
485 Text [ en-US ] = ",\t44\t;\t59\t:\t58\t{Tab}\t9\t{space}\t32 " ;
486 };
It would be better to place markers, remove the localization, and
replace the markers (I guess "Tab" and "space" are already translated
somewhere else, or two new string can be created):
String SCSTR_FIELDSEP
{
Text = ",\t44\t;\t59\t:\t58\t{$1}\t9\t{$2}\t32 " ;
};
String SCSTR_FIELDSEP_TAB
{
Text [ en-US ] = "Tab" ;
};
String SCSTR_FIELDSEP_SPACE
{
Text [ en-US ] = "space" ;
};
If someone files a new bug, I can take a look at it :)
Regards
Re: [CORRECTION] Re: Error in Dutch version in CSV export from Calc
Posted by Rob Weir <ro...@apache.org>.
On Wed, Jul 11, 2012 at 11:29 AM, Dick Groskamp <th...@quicknet.nl> wrote:
> Op 11-7-2012 16:31, risto.i.j@saunalahti.fi schreef:
>
>> Hello!
>> I just subscribe this list.
>> I made a proposal to Duch SCSTR_FIELDSEP text in Pootle. I reality there
>> is two proposals, firs was not so good.
>> I suppose there are some dead line for this change to have it in next
>> version?
>>
>> Regards
>> Risto
>>
>> Below is copy of original post:
>>
>> Hi,
>>
>> I have confirmed issue
>> https://issues.apache.org/ooo/show_bug.cgi?id=120216. The problem is, that
>> the export from Calc to csv does not work.
>>
>> I guess, that there is something wrong in the translation, therefore I
>> write to ooo-l10n@incubator.apache.org.
>>
>> It is the string SCSTR_FIELDSEP.
>>
>> In nl I see
>> ,\t\t44\t\t;\t\t59\t\t:\t\t58\t\t{Tab}\t\t9\t\t{spatie}\t\t32
>>
>> In de I see
>> ,\t44\t;\t59\t:\t58\t{Tab}\t9\t{Leer}\t32
>>
>> There seems to be some additional \t in nl which should not be there. I'm
>> not familiar with Pootle, but hope that you can find it with this
>> information.
>>
>> Kind regards
>> Regina
>>
>>
> Regina / Ristoi,
>
> thanks for stepping in.
>
> I've fiound the conflicting string.
> It is due to some superfluous tabs that got into the Dutch trabslation. (As
> Regina saw correctly)
> I noticed that tose appear when you copy the original English string to the
> field for editing
>
> I removed the superfluous tabs and adjusted the Dutch translation. I can't
> check if the correction
> stnds if the suggestion will be accepted, since I have no acces to Pootle.
>
> As Ristoi did I entered a suggestion 2 (nobody)
> In Ristoii's suggestions I see the removed tabs as strikethrough, which is
> probably not the solution
>
> @Juergen: please accept suggestiion #2 in segment 2609
> (scstring.src#SCSTR_FIELDSEP.string.text)
> to see if the suggestion stands. If not I will type the
> text in the field for editing instead of copying it
> from the original text
>
Thanks. I wonder, since this is such an easy bug to make, whether we
should check the other translations as well?
Or is there any easy way to automate checking or preventing such errors?
-Rob
> --
> DiGro
>
> Windows 7 and OpenOffice.org 3.3
> Scanned with Ziggo uitgebreide Internetbeveiliging (F-Secure)
>