Hello FPC-Pascal,
Friday, February 19, 2010, 3:22:15 AM, you wrote:
LFDAM> Ok,
LFDAM> The steps are :
LFDAM> 1) Change the Font Type at Lucida Console Font :
LFDAM> http://www.conoce3000.com/fig01.jpg
LFDAM> 2) Compile the program with fpc 2.4. :
LFDAM> 3) change to UTF8, with chcp 65001 command
I found some inconsistencies a couple of months ago, but never got to
creating a bug report:
http://www.mail-archive.com/fpc-pascal@lists.freepascal.org/msg17337.html
lists.freepascal.org seems down, so I found this link.
VIncent
___
fpc-pascal mail
On 19 Feb 10, at 17:27, JoshyFun wrote:
> Friday, February 19, 2010, 3:22:15 AM, you wrote:
>
> LFDAM> Ok,
> LFDAM> The steps are :
> LFDAM> 1) Change the Font Type at Lucida Console Font :
> LFDAM> http://www.conoce3000.com/fig01.jpg
> LFDAM> 2) Compile the program with fpc 2.4. :
> LFDAM> 3) cha
Hello Tomas,
Friday, February 19, 2010, 11:55:39 PM, you wrote:
TH> No, this can't work that way, otherwise output of any accented
TH> character in one of the Windows codepages would result in the same
TH> error.
Well I do not know the writeln internals, but if writeln writes 7
bytes and windows
Hello Tomas,
Friday, February 19, 2010, 11:55:39 PM, you wrote:
TH> No, this can't work that way, otherwise output of any accented
TH> character in one of the Windows codepages would result in the same
TH> error.
Tested the "wrong" return of stdout:
code page UTF8 - 65001 en Windows
Length of s
