Re: [fpc-devel] Re: Unicode and Lazarus
On Thu, Nov 20, 2008 at 9:09 AM, Mattias Gärtner <[EMAIL PROTECTED]> wrote: > So the roadmap from LCL pov is: > - a RTL using unicode strings > - changing the string types in the lazarus code > - a fpc release with the unicode RTL >From what I've heard about the Unicode RTL fpc developers recomend that we build our own set of routines/classes using UTF8String. Later they could be added to Free Pascal. This is more or less what we are doing at the moment, so we should just continue in the same direction. -- Felipe Monteiro de Carvalho ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Re: Unicode and Lazarus
On Thu, Nov 20, 2008 at 1:50 PM, Michael Schnell <[EMAIL PROTECTED]> wrote: > >> Compiler support for a unicode string is not enough for the LCL. >> As long as base classes like TStrings uses ansistrings, the LCL must use a >> string type, that does no conversion. > > Of course you are right that the RTL needs to be made up accordingly. Maybe > TStrings and friends are needed in multiple versions. Yes, I would have thought that's a given. All base classes need unicode support where appropriate - that includes TStrings. > Using a string type that dynamically can be used top hold multiple encodings > (as discussed here, too) sounds nice, if it does not result in too slow code > (due to the necessity of checking for the coding with any operation). At the moment, I think first supporting Unicode is the most important step. Performance tuning comes afterwards. That how it seems to work now and I don't see a problem with that. FPC generates assembler code, and it's still an ongoing process in tuning the performance of the assembler code. I remember how things where tweaked a while back with all the language shootout tests. We can implement Unicode shootout tests later. ;-) Regards, - Graeme - ___ fpGUI - a cross-platform Free Pascal GUI toolkit http://opensoft.homeip.net/fpgui/ ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Re: Unicode and Lazarus
Compiler support for a unicode string is not enough for the LCL. As long as base classes like TStrings uses ansistrings, the LCL must use a string type, that does no conversion. Of course you are right that the RTL needs to be made up accordingly. Maybe TStrings and friends are needed in multiple versions. Using a string type that dynamically can be used top hold multiple encodings (as discussed here, too) sounds nice, if it does not result in too slow code (due to the necessity of checking for the coding with any operation). -Michael ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Re: Unicode and Lazarus
Zitat von Felipe Monteiro de Carvalho <[EMAIL PROTECTED]>: > if a real utf8string would be a solution for Lazarus (I am not saying > it is, but it could be), we need to have a directive to change the > default string into utf8string. To avoid a huge amount of code to need > to be suddenly changed. Then only "ansistring" needs to be changed. Compiler support for a unicode string is not enough for the LCL. As long as base classes like TStrings uses ansistrings, the LCL must use a string type, that does no conversion. For example: Items[i]:=Caption; As long as Items[i] is treated as ansi, any automatic conversion can loose unicode characters. So the roadmap from LCL pov is: - compiler support for some unicode string on every platform: done in fpc 2.3, thanks to Florian - a RTL using unicode strings - changing the string types in the lazarus code - a fpc release with the unicode RTL Mattias ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
[fpc-devel] Re: Unicode and Lazarus
if a real utf8string would be a solution for Lazarus (I am not saying it is, but it could be), we need to have a directive to change the default string into utf8string. To avoid a huge amount of code to need to be suddenly changed. Then only "ansistring" needs to be changed. -- Felipe Monteiro de Carvalho ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
