On Mon, 24 Nov 2014 16:40:06 +
Graeme Geldenhuys wrote:
>[...]
> Where should we report this? Mantis or Unicode page of the Wiki?
On a second thought, a programmer need to know what might fail and the
alternative/workaround. The latter depends on settings.
In case of the new LCL mode we can
On Mon, 24 Nov 2014 22:53:44 +0100
Hans-Peter Diettrich wrote:
> Graeme Geldenhuys schrieb:
>
> > How is ThousandSeparator and DecimalSeparator supposed to work it
> > TFormatSettings? If you switched the RTL to UTF-8 or UTF-16 a Russian
> > thousand separator (4-byte non-breaking white space ch
On Mon, 24 Nov 2014 22:15:29 +0100
Hans-Peter Diettrich wrote:
>[...]
> The Delphi (and FPC) encoding model allows for strings of different
> static (declared) and dynamic (true content) encoding, see the special
> handling of RawByteString (Wiki).
>
> So far it's not a good idea to simply *as
Graeme Geldenhuys schrieb:
How is ThousandSeparator and DecimalSeparator supposed to work it
TFormatSettings? If you switched the RTL to UTF-8 or UTF-16 a Russian
thousand separator (4-byte non-breaking white space character) for
example will not fit into a Char type.
The Char type is quite us
luiz americo pereira camara schrieb:
When DefaultSystemCodePage is CP_ACP the variable S will have the
content of UTF8 but the encoding will be ACP (in my case 1252), just
like is today.
With DefaultSystemCodePage as CP_UTF8 both content and code page will match
The Delphi (and FPC) encoding
On 24/11/14 10:46, Joost van der Sluis wrote:
On 11/22/2014 12:45 PM, C Western wrote:
I have been switching back and forth between gdb and the new one - both
have some issues. The one I noticed most recently with the new one is
with a multi threaded application - a break set in the thread seem
On 2014-11-24 16:36, Mattias Gaertner wrote:
> It has not yet been converted.
Many thanks for confirming that.
> We can help the FPC team by collecting all places.
Where should we report this? Mantis or Unicode page of the Wiki?
Regards,
- Graeme -
--
fpGUI Toolkit - a cross-platform GUI
On Mon, 24 Nov 2014 16:25:15 +
Graeme Geldenhuys wrote:
>[...]
> Or is TFormatSettings just something that hasn't yet been converted to
> be Unicode friendly?
It has not yet been converted.
We can help the FPC team by collecting all places.
Mattias
--
On 2014-11-22 16:38, Michael Van Canneyt wrote:
> The exact behaviour of the RTL is controlled by a couple of variables:
> DefaultSystemCodePage, DefaultFileSystemCodePage ,
> DefaultRTLFileSystemCodePage.
I've read the updated wiki page, but still confused about something...
TFormatSettings =
On Mon, 24 Nov 2014 12:45:54 -0300
luiz americo pereira camara wrote:
> 2014-11-24 8:15 GMT-03:00 Mattias Gaertner :
>[...]
> > This works with or without {$codepage utf8}:
> >
> > S := 'João'; // constant to (Ansi or Short)string
> >
>
> Without {$codepage utf8}
> When DefaultSystemCodePage is
2014-11-24 8:15 GMT-03:00 Mattias Gaertner :
> On Sun, 23 Nov 2014 21:37:56 -0300
> luiz americo pereira camara wrote:
>
> > The attached program show how data loss can occur
>
> The program uses writeln, which converts to console CP.
> When you save the strings to a file you can see what they co
On 2014-11-24 10:52, Michael Schnell wrote:
> I don't know the internals of the program(s). It's a huge system and
> does anything that somehow might be possible :-) .
Luckily you have everything unit tested right. So it would simply be a
case of running the test suite to see what works and what
Please don't start an UTF war again.
This has been discussed in length and a zillion times.
Mattias
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
On 11/24/2014 02:50 PM, Hans-Peter Diettrich wrote:
code, the user should be allowed to use the string encoding (and byte
cont per character), he finds the most convenient for his application.
I'm not sure what exactly you mean here.
Here I menat that for a *new project* the user might be wil
Am 24.11.2014 14:55 schrieb "Hans-Peter Diettrich" :
> Please note that until now Windows did the Ansi to UTF conversions
itself, in every API call with strings involved. If this was not noticed
before, the conversions won't be noticeable afterwards as well.
This is something that one definitely s
On 11/24/2014 02:19 PM, Hans-Peter Diettrich wrote:
A move to UTF-16 instead will only favor Windows,
Regarding the RTL interface, you of course are right.
Doing the user software with UTF-16 instead of RTZF-8 strings, in many
cases (but of course not perfectly) allows for keeping old-style 1
Michael Schnell schrieb:
On 11/23/2014 07:52 PM, Felipe Monteiro de Carvalho wrote:
Well, the first reports of how the unicode rtl would look like were
pretty scary: Total break of the string part of millions of lines of
code that people wrote with Lazarus since years.
That is why I stopped re
On Sun, 23 Nov 2014 18:27:12 -0300
luiz americo pereira camara wrote:
> 2014-11-20 13:21 GMT-03:00 Mattias Gaertner :
>[...]
> Please test and tell what you find out.
> >
> >
> The FormatSettings fields are still encoded with System Code Page
> regardless of DefaultSystemCodePage value.
>
> Whil
On Mon, 24 Nov 2014 13:12:04 +0100
Michael Schnell wrote:
> On 11/24/2014 12:01 PM, Juha Manninen wrote:
> > See the request from Mattias : "Please test and tell what you find out."
>
> I have not enough knowledge to be able to patch the compiler :-(
I asked for testing compiling with -dEnableU
On 11/24/2014 12:01 PM, Juha Manninen wrote:
See the request from Mattias : "Please test and tell what you find out."
I have not enough knowledge to be able to patch the compiler :-(
let's keep this thread in a more congrete level.
Agreed (even if I don't think that will lead to anything fai
On Mon, 24 Nov 2014 12:15:03 +0100
Mattias Gaertner wrote:
>[...]
> I guess it would be a good idea to pass -Fcutf8 with FPC 2.7.1. For
> both modes.
On second thought: only for new mode.
Passing it in the old mode will make the wide/unicode/utf8string work,
but the Ansi/Shortstring will be wro
On Sun, 23 Nov 2014 21:37:56 -0300
luiz americo pereira camara wrote:
> 2014-11-20 13:21 GMT-03:00 Mattias Gaertner :
>[...]
First of all: Thanks for testing.
> Without {$codepage utf8} directive String constants will get Code Page 0
> (CP_ACP) and not the 1200 (UTF16 - UnicodeString).
Beware:
On Mon, Nov 24, 2014 at 11:33 AM, Michael Schnell wrote:
> IMHO that would be just GREAT to allow for doing portable software. The RTL
> and LCL interface should be OS ignorant for portability. In user code, the
> user should be allowed to use the string encoding (and byte cont per
> character), h
On 11/24/2014 11:44 AM, luiz americo pereira camara wrote:
If the program does not explicitely assumesa specific encoding, i.e.
use only String type and do not do low level string handling, there
will be no need to change.
I don't know the internals of the program(s). It's a huge system and
On 11/22/2014 12:18 AM, Mattias Gaertner wrote:
On Fri, 21 Nov 2014 23:08:00 +
Martin Frb wrote:
[...]
So as far as the debugger goes, this would then be correctly following
the debug info.
Funny fpc. Thanks for checking.
BTW, the default TGDBMIDebugger jumps even worse. Begin, End, Beg
On 11/22/2014 12:45 PM, C Western wrote:
I have been switching back and forth between gdb and the new one - both
have some issues. The one I noticed most recently with the new one is
with a multi threaded application - a break set in the thread seem to
cause the debugger to become "lost". Is the
2014-11-24 6:29 GMT-03:00 Michael Schnell :
> On 11/23/2014 07:52 PM, Felipe Monteiro de Carvalho wrote:
>
>>
>> Well, the first reports of how the unicode rtl would look like were
>> pretty scary: Total break of the string part of millions of lines of
>> code that people wrote with Lazarus since
Am 24.11.2014 10:20 schrieb "Joost van der Sluis" :
>
> On 11/23/2014 09:09 PM, waldo kitty wrote:
>>
>> On 11/22/2014 6:45 PM, Mattias Gaertner wrote:
>>>
>>> On Sat, 22 Nov 2014 23:27:30 +0100
>>> Bart wrote:
>>>
On 11/22/14, Joost van der Sluis wrote:
> Add the windows-unit to th
On 11/22/2014 05:18 PM, Hans-Peter Diettrich wrote:
Does this mean that Lazarus (new mode) ignores the OS system codepage
setting?
IMHO that would be just GREAT to allow for doing portable software. The
RTL and LCL interface should be OS ignorant for portability. In user
code, the user should
On 11/23/2014 07:52 PM, Felipe Monteiro de Carvalho wrote:
Well, the first reports of how the unicode rtl would look like were
pretty scary: Total break of the string part of millions of lines of
code that people wrote with Lazarus since years.
That is why I stopped recommending Lazarus to my c
On 11/23/2014 09:09 PM, waldo kitty wrote:
On 11/22/2014 6:45 PM, Mattias Gaertner wrote:
On Sat, 22 Nov 2014 23:27:30 +0100
Bart wrote:
On 11/22/14, Joost van der Sluis wrote:
Add the windows-unit to the uses section of lresources as a quick fix.
Done.
i pulled your update last evenin
31 matches
Mail list logo
