[fpc-pascal] Re: Console Encoding in Windows (Local VS. UTF8)

2013-07-28 Thread Noah Silva
Hello everyone! Success! Writeln was indeed the main culprit. The following works: WritelnUTF8(('あいうえお秋葉原')); (Where: 1. WritelnUTF8 is a procedure that uses the Win32 API WriteConsole directly, bypassing whatever writeln is doing. 2. Where the source code is saves as UTF8 with BOM 3. Where I

Re: [fpc-pascal] Re: Console Encoding in Windows (Local VS. UTF8)

2013-07-13 Thread Noah Silva
Hi, Thank you very much for the link. I think it will take some experimenting to get everything to work how it should on my systems. I am not using the {$codepage utf8} in my files, but I don't usually have any non-ASCII text in the programs. (The source files are in UTF8 though). The data I a

[fpc-pascal] Re: Console Encoding in Windows (Local VS. UTF8)

2013-07-11 Thread Lukasz Sokol
On 10/07/2013 13:38, Graeme Geldenhuys wrote: > On 2013-07-10 11:19, Tomas Hajny wrote: >> >> Sure, but you can't select just any True Type fonts for console windows >> (only Lucida is offered in WinXP; > > And is so since Win95. Just amazing that Windows Console is so far > behind other platforms

[fpc-pascal] Re: Console Encoding in Windows (Local VS. UTF8)

2013-07-09 Thread Reinier Olislagers
On 9-7-2013 11:02, Noah Silva wrote: > I have followed steps in the Wiki, etc., but to little avail, so I have > some questions for anyone who knows more than me: > 1. What encoding "should" I be writing to the terminal? from > experimenting with text files using the cat command in powershell, it