Recent

Author Topic: Unicode resourcestring  (Read 2137 times)

winni

  • Hero Member
  • *****
  • Posts: 3197
Re: Unicode resourcestring
« Reply #15 on: February 03, 2023, 11:40:17 pm »
Please share me your wisdom.


UTF8 <> UTF16

KodeZwerg

  • Hero Member
  • *****
  • Posts: 2269
  • Fifty shades of code.
    • Delphi & FreePascal
Re: Unicode resourcestring
« Reply #16 on: February 04, 2023, 12:08:28 am »
@KodeZwerg
It was just an example against your wrong statement
"Unicode is Unicode, nothing more nothing less."
What else is Unicode when not Unicode?
UTF8 <> UTF16
Since you do not use words to answer a normal question but character encoding standards, I have absolute no Idea why you quoted me at all.
That answer makes no sense and my statement is still the same.
Unicode is Unicode, nothing more nothing less - period.
( but I am still open to be convinced by something different  :-* )

Excuse me moderators for this kinda offtopic argue.
« Last Edit: Tomorrow at 31:76:97 xm by KodeZwerg »

PascalDragon

  • Hero Member
  • *****
  • Posts: 5589
  • Compiler Developer
Re: Unicode resourcestring
« Reply #17 on: February 06, 2023, 11:01:55 pm »
Unicode string means generally UTF-16. UTF-16 could be Le or Be.

And FPC always uses the endianess of the target, so it makes no sense to talk about UTF-16BE vs. UTF-16LE in the general sense in the context of FPC.

Some people speaks, wrong, Unicode string for UTF-8. Please, use the exact denomination...  ;D ;D

We are on a FPC/Lazarus forum here, so I can assume that the users know when I write “UnicodeString” that I mean UnicodeString which in turn means UTF-16 (no matter if BE or LE) and not “Unicode string” which might mean any string with a Unicode encoding.

Unicode string means generally UTF-16. UTF-16 could be Le or Be.
Some people speaks, wrong, Unicode string for UTF-8. Please, use the exact denomination...  ;D ;D
It is the other way around. MS uses unicode 16 (based on UCS) and the rest of the world uses UTF8.

Qt uses UTF-16, JavaScript uses UTF-16, Java uses UTF-16. And on non-Windows wchar_t is even four Byte and thus uses UTF-32.

 

TinyPortal © 2005-2018