[fpc-devel] Russian locale information not compatible with FPC locale variables
Michael Van Canneyt
michael at freepascal.org
Tue Jul 29 12:20:25 CEST 2008
>
>
> On Tue, 29 Jul 2008, Graeme Geldenhuys wrote:
>
> > On Tue, Jul 29, 2008 at 10:27 AM, Graeme Geldenhuys
> <graemeg.lists at gmail.com> wrote:
> > On Tue, Jul 29, 2008 at 10:16 AM, Daniƫl Mantione
> > <daniel.mantione at freepascal.org> 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.
>
>
> So back to my original question.... :)
>
> Due to ThousandSeparator being a Char type, is using a normal space
> ($20) the only available option for Russian users, using the current
> RTL implementation? Though this might cause issues in text wrapping
> routines which can now not distinguish between breaking spaces and
> non-breaking spaces.
Yes, this is your only option.
>
> The only other alternative is writing my own string format functions
> like fpgFormatFloat() and hope the users of fpGUI use the custom
> written functions instead of the RTL ones. This also means I need to
> implement my own locale variables to be Unicode compatible. What a
> job, for something that seemed so small an issue in the beginning. :)
Let's not jump to conclusions too quickly.
Obviously, the FPC team will have to do something for Unicode support;
Tiburon compatibility plays a big role in that. Once this is done,
there should be no problem. For the time being, replacing the non-
breaking space with a breaking space is the best you can do. The chances
that you really need a non-breaking space somewhere in an amount are
infinitesimally small.
So, no need to make the issue bigger than it is, and start coding duplicates
of existing routines because of such a small issue. We'll fix it eventually,
this is the main message.
Michael.
More information about the fpc-devel
mailing list