Re: OpenJade behaves differently than Jade

[Alexander Sieb <alex@xxxxxxx>]

Matthias Clasen wrote:
> 
> >
> > Hi!
> >
> > As a poor Win95 user, I just came to test OpenJade 1.3. I found a different
> > behavior towards Jade 1.2, which I think is a little weird:
> >
> > Before all real numbers were using a dot as a delimiter, e.g. (* 1.2 14pt)
> > Now, OpenJade issues errors saying "this is not a number", and I must use a
> > comma, such as (* 1,2 14pt)
> >
> > But for length-specs, this is not the case; OpenJade issues an error if I
> > state (* 1,2 13,5pt), and the correct spelling is (weird enough:)
> >
> > (* 1,2 13.5pt)
> >
> > Bug or feature? Or configurable?
> >
> 
> Bug. Sounds as if OpenJade is using the wrong locale when reading the specs.
> 
IIRC that is related to SP_HAVE_LOCALE strod, right?
I compiled using SP_HAVE_LOCALE=1, should I undefine SP_HAVE_LOCALE?

-- 
cu Alex
alex@xxxxxxx


 DSSSList info and archive:  http://www.mulberrytech.com/dsssl/dssslist