[fpc-pascal] Unicode file routines proposal
Felipe Monteiro de Carvalho
felipemonteiro.carvalho at gmail.com
Mon Jun 30 15:49:41 CEST 2008
On Mon, Jun 30, 2008 at 10:32 AM, Marco van de Voort <marcov at stack.nl> wrote:
> It should be possible to work in the native encoding. One doesn't want to
> wrap _every_ function in _every_ header with conversions procs.
It is not possible to work with a ever changing encoding.
MyLabel.Caption := 'Lição';
How would that ever work with a ever changing encoding? It would not.
If you go to the real implementation level a changing encoding quickly
becomes unmanagable.
And what about the LFM files? In which encoding will they be? What if
you develop a software in one system and tryes to build it in another?
Ok, to go one step further: Has anyone ever seen a fully unicode
system which works with changing encodings? I beliave there exists
none, because this is not a good solution.
> Well, they will have to do that with one string type too, at every external
> barrier.
This is already necessary.
> That also kills the benefit of choosing UTF-16 in the first place, since
> Delphi code won't work on Unix without manually inserting a lot of
> conversion code.
Delphi code can use the ansi routines, which could just call the
utf-16 routines with a string conversion, or you can implement every
routine twice to maximize speed.
--
Felipe Monteiro de Carvalho
More information about the fpc-pascal
mailing list