2016.01.18. 23:20 keltezéssel, Bart írta:
With or without -dDisableUTF8RTL ?
Checkout, make bigide. I did not change anything.
Gabor
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinf
On 1/18/16, Gabor Boros wrote:
> A complicated example:
>
> Label1.Caption:=WideChar($25BD);
>
> With fixes_1_4(and FPC 3.0.0) I see a question mark on the screen, with
> fixes_1_6 I see the wanted "WHITE DOWN-POINTING TRIANGLE".
> I am happy with fixes_1_6! :-)
With or without -dDisableUTF8RTL
2016.01.17. 12:34 keltezéssel, Juha Manninen írta:
Feedback please.
Hi,
A complicated example:
Label1.Caption:=WideChar($25BD);
With fixes_1_4(and FPC 3.0.0) I see a question mark on the screen, with
fixes_1_6 I see the wanted "WHITE DOWN-POINTING TRIANGLE".
I am happy with fixes_1_6! :-)
On 1/18/16, Jürgen Hestermann wrote:
> Now that is cynical!
No it is not.
Lazarus has taken the direction of using the new UTF8 system.
Most of us do not use the DisableUtf8 feature at all, since we don't need it.
Hence we have no experience.
Users who want that feature should test it.
Failures
On Mon, Jan 18, 2016 at 8:20 AM, Jürgen Hestermann
wrote:
> Now that is cynical!
> Telling those who do not know anything about what
> has been developed over the last years
> to write the documentation theirselfs.
No, my point is that I will not continue doing it. Somebody else must
take charge.
Am 2016-01-17 um 19:48 schrieb Juha Manninen:
> Jürgen and taazz,
...
> The wiki page explaining it
> should be improved and maintained by people who actually use the
> system which means Jürgen, taazz, michl and others.
Now that is cynical!
Telling those who do not know anything about what
has b
Jürgen and taazz,
The DisableUTF8RTL system indeed is a fall-back for people who cannot
use the new improved UTF-8 system.
The automatic encoding conversion may do tricks when you still must do
explicit conversion to/from UTF-8 using the old clumsy functions.
I don't know about all the issues invol
On 1/17/16, Jürgen Hestermann wrote:
> But as one example, since FPC 3.0 you cannot use UTF8Delete on UTF8Strings
> anymore.
Already fixed in trunk (r50850 and r50910) and merged into 1.6RC2.
Please stop complaing about things that were already fixed.
Bart.
--
_
Am 2016-01-17 um 15:19 schrieb Juha Manninen:
> I don't understand how DisableUTF8RTL bombs your system because it is
> the backwards compatible thing.
> If your system worked with FPC 2.6.4, it should work with FPC 3.0 +
> DisableUTF8RTL.
Yes, you are right.
DisableUTF8RTL resets *some* of the c
On Sun, Jan 17, 2016 at 2:54 PM, Jürgen Hestermann
wrote:
> You may have a false impression of how Free Pascal/Lazarus is used by most
> people.
> At least I did not wait until the current version to use Unicode (and long
> paths)
> for file names and others. I think many did so.
> Therefore we ha
Am 2016-01-17 um 12:34 schrieb Juha Manninen:
> LCL continues to work as before when you define "DisableUTF8RTL". Then
> AnsiString is coded with the system codepage by default. The UTF-8
> conversion functions still work.
You may have a false impression of how Free Pascal/Lazarus is used by most
The RC1 and RC2 versions have been tested for a while now but we have
not heard any complaints about the new improved Unicode support.
Does that mean it works perfectly?
Windows is of biggest interest. There the new UTF-8 support breaks
existing code when it depends on system codepage.
For that re
12 matches
Mail list logo
