> <[EMAIL PROTECTED]> wrote: > > As a workaround, it can be converted into a normal breaking space. There is > > no proper solution, MBCS requires it to be a string rather than a char, but > > compatibility requires it to be a char. Which means you are limited to SBCS > > compatible thousand separators. > > This is what the Russian user had to revert to, using a normal $20 > (space) character. But seeing that Delphi is now going to be fully > Unicode compliant, surely we need to attend to these issues as well in > FPC - being fully Unicode compliant.
And just like Delphi, I think it is better to wait to a major version with proper unicode string support, and do it (mostly) right in one go, instead of little ad-hoc changes to support workarounds. _______________________________________________ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
