On Wed, May 3, 2017 at 9:37 AM, Mattias Gaertner via Lazarus
wrote:
>> Hmmm... why does FPC not understand the BOM?
>
> It does. And so does Delphi. But with and without BOM have different
> meanings.
>
>
>> > You are right, that using Unicode with Lazarus only needs a couple of
>> > rules to foll
On Wed, May 3, 2017 at 6:13 AM, Ondrej Pokorny via Lazarus
wrote:
> Not if you need pre-unicode Delphi support :)
>
> (Well, Marcos didn't specify what Delphi version he wants to target but he
> stated "If Delphi sources don't use UTF8 [...]", which applies to
> pre-unicode Delphi versions.)
Yeah
On 2017-05-03 20:47, Juha Manninen via Lazarus wrote:
> If you share and edit the sources between Delphi and Lazarus then you
> cannot use the full Unicode.
Quite comical considering that the FPC team always makes such a big fuss
about "we want Delphi compatibility", and now it seems to be worse
On 03.05.2017 21:47, Juha Manninen via Lazarus wrote:
> Why Delphi adds the BOM? Why can't it just read the file and
> understand it is UTF-8?
Probably for the same reason as FPC: the default code page if no BOM is
available and no command line option is set and no $codepage directive
is found is
On 03.05.2017 21:47, Juha Manninen via Lazarus wrote:
How many people are editing their sources in both Delphi and Lazarus?
Me, but I keep the files ASCII-only because I need to target all Delphi
versions down to D5 :/ My customers really demand it, unfortunately. I'd
like to kill these dinos
On Wed, May 3, 2017 at 12:03 PM, Juha Manninen
wrote:
> Marcos Douglas B. Santos wrote:
>> But if I put theses constants as resourcestrings, it's Ok as Mattias
>> told me, right?
>
> I don't think it makes any difference. You can use the full Unicode in
> both cases.
I stand corrected.
If you sha
Am 03.05.2017 14:37 schrieb "Tony Whyman via Lazarus" <
lazarus@lists.lazarus-ide.org>:
> On the other hand, AnsiString and UnicodeString are still separate types.
Why? Why should there not be a single unified string type with (e.g.)
ASCII, UTF8 and UTF-16 (or MS Unicode) being just another code pa
Am 03.05.2017 11:34 schrieb "Graeme Geldenhuys via Lazarus" <
lazarus@lists.lazarus-ide.org>:
> For example, take a look at ConEmu for Windows.
> * Tab support built-in
> * Resizeable console windows
While not point and click you can resize console windows (and the window
buffer) without probl
On 2017-05-03 13:37, Tony Whyman via Lazarus wrote:
> Is Delphi/FPC string handling that much worse than 'C'?
I can’t answer about C, but compared to Java and Qt’s solution, Delphi
and FPC’s solutions are terrible and very confusing.
Regards,
Graeme
--
Am 03.05.2017 um 11:03 schrieb Juha Manninen via Lazarus:
> How could this thing be communicated so that people understand?
It would probably help if there weren't three different pages about "Unicode
Support" on the wiki, all saying slightly different and conflicting things
(because they talk abou
On Wed, 3 May 2017 13:37:24 +0100
Tony Whyman via Lazarus wrote:
>[...]
> On the other hand, AnsiString and UnicodeString are still separate
> types. Why? Why should there not be a single unified string type with
> (e.g.) ASCII, UTF8 and UTF-16 (or MS Unicode) being just another code page?
Man
On 03/05/17 09:52, Graeme Geldenhuys via Lazarus wrote:
[rant]
ps:
Both FPC and Delphi is in such a messed up state when it comes to
string and character types. It is the laughing stock of programming
languages at the moment. At least EMBT is heading in the right
direction with their
On Wed, 3 May 2017 15:15:53 +0300
Juha Manninen via Lazarus wrote:
>[...]
> > Back in Lazarus compiling such a file gives the error:
> > LazUnicodeTest.lpr(28,10) Error: UTF-8 code greater than 65535 found
>
> Äh, I did not test moving it back to Lazarus.
Well, that's the point of sharing cod
On Wed, May 3, 2017 at 5:59 AM, Graeme Geldenhuys via Lazarus
wrote:
> On 2017-05-03 01:21, Marcos Douglas B. Santos via Lazarus wrote:
>> Sorry about that. I stopped using Delphi at version 7, that uses ANSI.
>> I thought that Delphi nowadays was using UTF16.
>
> They (Delphi) loves to follow Mic
On Wed, May 3, 2017 at 2:43 PM, Mattias Gaertner via Lazarus
wrote:
> First it did not compile in Delphi, because of an unsupported inline. I
> fix that with an IFDEF FPC.
Right, I had added that after testing with Delphi.
The inline looks good to me, don't know why Delphi does not like it.
> Th
On Wed, 3 May 2017 12:03:41 +0300
Juha Manninen via Lazarus wrote:
>[...]
> Please also look at program LazUnicodeTest in components/lazutils/test/.
> It does advanced Unicode stuff and works in both Delphi and Lazarus.
I tried it:
First it did not compile in Delphi, because of an unsupported i
On Wed, 3 May 2017 12:03:41 +0300
Juha Manninen via Lazarus wrote:
>[...]
> Mattias Gaertner wrote:
> > Option a) You can use English in sources and load all non ASCII
> > constants via resourcestrings or similar. Then the codepage is
> > irrelevant.
> > Option b) You can store all files as UTF-8
Am 2017-05-03 um 11:34 schrieb Graeme Geldenhuys via Lazarus:
> I don't know why anybody would still want to run the standard Windows
> console - it is 20 years behind everybody else.
The reason: It is available on every Windows machine.
The alternatives need to be installed first
so scripts desi
On Wed, May 3, 2017 at 12:13 PM, Ondrej Pokorny via Lazarus
wrote:
> Not if you need pre-unicode Delphi support :)
Ok, true. IMO such old Delphi versions should not be used any more for new code.
Maintenance tasks only I think.
Fortunately there is again a free Delphi Starter edition. It means
a
On 03.05.2017 11:21, Juha Manninen via Lazarus wrote:
Windows already supports Unicode in everything ... except for console
output! Why is that?
You can start the console with UTF-8 codepage:
http://stackoverflow.com/questions/14109024/how-to-make-unicode-charset-in-cmd-exe-by-default
Then y
On 2017-05-03 10:25, Ondrej Pokorny via Lazarus wrote:
> You can start the console with UTF-8 codepage:
> http://stackoverflow.com/questions/14109024/how-to-make-unicode-charset-in-cmd-exe-by-default
>
> Then you have full unicode (utf-8) support.
Or use the much better console alternatives. The
On Wed, May 3, 2017 at 11:52 AM, Graeme Geldenhuys via Lazarus
wrote:
> At least EMBT is heading in the right direction with their
> Linux Delphi compiler - they completely removed AnsiString.
I must agree with you. I hope it will be removed in (far) future when
nobody uses the old Windows system
On 03.05.2017 11:03, Juha Manninen via Lazarus wrote:
I am puzzled why there were so many misleading and confusing replies,
also from knowledgeable Lazarus developers.
Remember, the question was about making sources compatible with Delphi.
The person (Marcos Douglas) did not know details of how s
Marcos Douglas B. Santos wrote:
> I am develop on Windows. What problems do you mean?
Unicode is recommended also on Windows. No worries. You don't need to
use the old system codepages.
People who need them must convert them explicitly because the Unicode
system of Lazarus does not support them di
On 2017-05-03 01:21, Marcos Douglas B. Santos via Lazarus wrote:
> Sorry about that. I stopped using Delphi at version 7, that uses ANSI.
> I thought that Delphi nowadays was using UTF16.
They (Delphi) loves to follow Microsoft. Files are stored in UTF-8 (this
is the norm), but they use UTF-16 int
On 2017-05-02 09:30, Juha Manninen via Lazarus wrote:
> From FPC's point of view our UTF-8 solution is a hack.
FPC's point of view or Marco's point of view? Just curious - so what is
FPC’s “correct” solution then for using UTF-8 and the preferred
encoding? What's the alternative they offer?
[ra
26 matches
Mail list logo
