[Tilesathome] Windows Client on dual core / windows ", " problem

[Christian Ehrlicher]

Knut Arne Bjørndal schrieb:
> On Tue, Oct 07, 2008 at 07:00:54PM +0200, Christian Ehrlicher wrote:
>> Knut Arne Bjørndal schrieb:
>>> On Tue, Oct 07, 2008 at 06:39:10PM +0200, Christian Ehrlicher wrote:
>>>> Ed Loach schrieb:
>>>>>> Oh, and the code you have been working on, did you mean to look
>>>>>> at
>>>>>> unstable? In that case you should update since the command line
>>>>>> building has been moved and completely redesigned.
>>>>> I was trying to find out what the problem was in stable first. I'll
>>>>> try unstable now to see whether that is already fixed with respect
>>>>> to this problem.
>>>>>
>>>> This issue was brought up several times and I also posted a small hack 
>>>> until someone is willin gto port the correct patch back from unstable. 
>>>> But nobody really cares...
>>>>
>>>> Simply change line 813 of tilesgen.pl to
>>>>
>>>> setlocale(LC_ALL, 'C');
>>>>
>>>>
>>>> and all works fine.
>>> Uh, am I reading you correctly that this issue is in fact fixed in
>>> unstable? In that case there's not much point in spending time on this
>>> since unstable will be migrated to stable in a few days anyway.
>>>
>> I did not verify if it's really fixed in unstable.
>> and btw: I heard the same sentence two weeks ago while this problem was 
>> discussed. I really wonder what's the problem to add this small hack 
>> instead waiting until a new t at h user complains about this issue... !?
> 
> When you say that something is just a hack until somebody can backport
> something from unstable, and they are planning to copy unstable to
> stabel soon enough then of course they don't bother patching code that
> will be obsolete soon anyway.
> 
> I'll put it on my todo to figure out what this patch of yours does and
> how to apply something similar to unstable.
> 
> Just for the record, could you supply some context for your change
> just so I'm sure I get it in the right place when I start working on
> it? Line numbers are a really bad way to identify a position in a
> changing codebase.
> 
The problem is the faulty inkscape. It needs , as separator when used in 
a german locale. Therefore the hack with InkscapeLocale.
The problem seems to be that
$oldLocale=setlocale(LC_ALL, $locale);
returns 'German' although it wasn't set to anything before. The next 
call to setlocale() then sets it to German. A global setlocale(LC_ALL, 
'C') did not work (at least for me iirc).

Maybe alo search the archives :)

Christian