Re: [Zope] locale and Splitter.c on FreeBSD - where is the bug ?

2000-09-11 Thread Aleksander Salwa
On Sun, 10 Sep 2000, Dieter Maurer wrote: > Nevertheless, you patch to "splitter" should be welcome > as it solves a usability problem on FreeBSD systems. > Put it into the collector (URL:http://classic.zope.org/Collector). Done. > You may file a problem report to the FreeBSD maintainers in >

Re: [Zope] locale and Splitter.c on FreeBSD - where is the bug ?

2000-09-11 Thread Aleksander Salwa
On Sun, 10 Sep 2000, Dieter Maurer wrote: > Put it into the collector (URL:http://classic.zope.org/Collector). 8080 Anyway, Collector doesn't work :( - "Temporarily Unavailable".

Re: [Zope] locale and Splitter.c on FreeBSD - where is the bug ?

2000-09-10 Thread Dieter Maurer
Aleksander Salwa writes: > > Some time ago I had a problem with locales on FreeBSD. > > On all machines I'm working on, 'char' is signed. > On Linux/x86, isalpha and others works fine with positive and negative > values of national characters. (For example, one polish character is > '

Re: [Zope] locale and Splitter.c on FreeBSD - where is the bug ?

2000-09-09 Thread Oleg Broytmann
On Sat, 9 Sep 2000, Aleksander Salwa wrote: > Some time ago I had a problem with locales on FreeBSD. > Finally, I solved it by patching Splitter.c. > > I added casting of values passed to funtions isalpha, isalnum to > type 'unsigned char'. They are declared in Splitter.c as 'char'. > > On all m

[Zope] locale and Splitter.c on FreeBSD - where is the bug ?

2000-09-09 Thread Aleksander Salwa
Some time ago I had a problem with locales on FreeBSD. Finally, I solved it by patching Splitter.c. I added casting of values passed to funtions isalpha, isalnum to type 'unsigned char'. They are declared in Splitter.c as 'char'. On all machines I'm working on, 'char' is signed. On Linux/x86, i