Hi,
I deal with in Japanese (and sometimes other languages) in a lot of my
programs, and nothing I do seems to work consistently on Windows systems.
(OS X is no problem).
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.
On 09 Jul 2013, at 11:02, Noah Silva wrote:
1. What encoding "should" I be writing to the terminal?
The console code page. You can get it using the following function:
function GetConsoleOutputCP : UINT; stdcall; external 'kernel32'
name 'GetConsoleOutputCP';
from experimenting
with te
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
On Tue, July 9, 2013 11:13, Jonas Maebe wrote:
> On 09 Jul 2013, at 11:02, Noah Silva wrote:
.
.
>> 3. Is there a way to set the output to UTF8 so I can just write out
>> UTF8
>> and be done with it?
>
> I don't know.
There is code page 65001 for UTF-8, however I don't know since which
version o
On 07/09/2013 11:02 AM, Noah Silva wrote:
I convert it to UTF8 before displaying it
Not a good idea.
The FPC developers are right now busy implementing the new Delphi
Strings. This _could_ mean that the application programmer can use any
encoding (such as multiple different ANSI byte-c
In our previous episode, Tomas Hajny said:
> >> and be done with it?
> >
> > I don't know.
>
> There is code page 65001 for UTF-8, however I don't know since which
> version of MS Windows it is supported (and to which extent - e.g.
> including the console output).
Afaik Windows XP, but there migh
In our previous episode, Michael Schnell said:
> Not a good idea.
>
> The FPC developers are right now busy implementing the new Delphi
> Strings. This _could_ mean that the application programmer can use any
> encoding (such as multiple different ANSI byte-codes, UTF-8, UTF-16,
> ...), but in
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
seems that local ("ANSI") encoding shoul
On 07/09/2013 12:55 PM, Marco van de Voort wrote:
Well, the main reason is not FPC, but Windows. UTF8 in Windows on
_API_ level is simply not a good idea
You are absolutely right.
Here, in theory the Lazarus LCL and the FPC RTL could help by by
providing an application programmer API that doe
In our previous episode, Dennis Poon said:
> Please state the windows version you are using. XP or Windows 7?
In XP there were separate Far East versions of Windows. In Vista+ this
was wholly integrated and there is only one Vista base system with various
language packs.
It might be that some o
On Tue, July 9, 2013 12:40, Marco van de Voort wrote:
> In our previous episode, Tomas Hajny said:
>> >> and be done with it?
>> >
>> > I don't know.
>>
>> There is code page 65001 for UTF-8, however I don't know since which
>> version of MS Windows it is supported (and to which extent - e.g.
>> in
In our previous episode, Tomas Hajny said:
> >> is
> >> like this.
> >
> > Keep in mind he is talking powershell, not cmd.exe
>
> I have no experience with powershell yet, but as long as it uses a console
> window (albeit designed differently), the launched applications should
> behave the same wa
On Tue, July 9, 2013 14:38, Marco van de Voort wrote:
> In our previous episode, Tomas Hajny said:
>> >> is
>> >> like this.
>> >
>> > Keep in mind he is talking powershell, not cmd.exe
>>
>> I have no experience with powershell yet, but as long as it uses a
>> console
>> window (albeit designed di
13 matches
Mail list logo
