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. >> including the console output). > > Afaik Windows XP, but there might be font problems on console.
I also thought about mentioning True Type fonts (like Lucida) being a better option in this case, but then I assumed that with Japanese, this might be necessary anyway. >> console using the Windows API call SetConsoleOutputCP, but e.g. our unit >> Crt currently resets the code page used for output to console to the >> "main" process code page (as returned by GetACP) on each write and thus >> ignores the user selection - this will probably change in trunk in the >> future as part of the Unicode support activities, but the current state >> 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 way, shouldn't they? Tomas _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
