Hi *,
On Wed, Jul 11, 2012 at 1:34 PM, Rob Weir <[email protected]> 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
