When there are Chinese characters in the output, the console will       display messy code.I change the encoding of the source file into       UTF-8 or UTF-16,but the messy code is still there...
       I use the dmd 2.065,Visual Studio 2013 with VisualD.
       How to solve this problem?
       Thank you!

On 05/10/2014 07:19 PM, IceNature via Digitalmars-d-learn wrote:
> When there are Chinese characters in the output, the console will       display messy code.I change the encoding of the source file into       UTF-8 or UTF-16,but the messy code is still there...
>         I use the dmd 2.065,Visual Studio 2013 with VisualD.
>         How to solve this problem?
>         Thank you!
>

If this is on Windows, you must

1) Set the console code page to 65001 e.g. by the command

  chcp 65001

(It is possible to make it the default through a Windows registry setting.)

2) Set the font to a unicode one e.g. Lucida

Ali

On Sunday, 11 May 2014 at 02:38:44 UTC, IceNature via Digitalmars-d-learn wrote:
> When there are Chinese characters in the output, the console will       display messy code.I change the encoding of the source file into       UTF-8 or UTF-16,but the messy code is still there...
>        I use the dmd 2.065,Visual Studio 2013 with VisualD.
>        How to solve this problem?
>        Thank you
You can get answer from here:
http://forum.dlang.org/thread/ucfpqgzzxcacqxkdrkmj@forum.dlang.org

Thank you for your help. But if I change the default console encoding,will it affect other programs,making other console program show messy code?

On 2014年5月11日 格林尼治标准时间+0800下午1时18分42秒, FrankLike via Digitalmars-d-learn <digitalmars-d-learn@puremagic.com> wrote:
>On Sunday, 11 May 2014 at 02:38:44 UTC, IceNature via Digitalmars-d-learn wrote:
>> When there are Chinese characters in the output, the console
>> will       display messy code.I change the encoding of the
>> source file into       UTF-8 or UTF-16,but the messy code is
>> still there...
>>        I use the dmd 2.065,Visual Studio 2013 with VisualD.
>>        How to solve this problem?
>>        Thank you
>You can get answer from here: http://forum.dlang.org/thread/ucfpqgzzxcacqxkdrkmj@forum.dlang.org
>
>.

Thank you for your help. But if I change the default setting,will it affect other programs,making other console program show messy code?

On 2014年5月11日 格林尼治标准时间+0800下午12时30分40秒, "Ali Çehreli via Digitalmars-d-learn" <digitalmars-d-learn@puremagic.com> wrote:
>On 05/10/2014 07:19 PM, IceNature via Digitalmars-d-learn wrote:
>> When there are Chinese characters in the output, the console will
>display messy code.I change the encoding of the source file into UTF-8 or UTF-16,but the messy code is still there...
>>         I use the dmd 2.065,Visual Studio 2013 with VisualD.
>>         How to solve this problem?
>>         Thank you!
>>
>
>If this is on Windows, you must
>
>1) Set the console code page to 65001 e.g. by the command
>
>   chcp 65001
>
>(It is possible to make it the default through a Windows registry
>setting.)
>
>2) Set the font to a unicode one e.g. Lucida
>
>Ali
>
>.

Known bug https://issues.dlang.org/show_bug.cgi?id=2742

On Sunday, 11 May 2014 at 06:35:26 UTC, IceNature via Digitalmars-d-learn wrote:
> Thank you for your help. But if I change the default console encoding,will it affect other programs,making other console program show messy code?

Don't  affect,and you must set the font to  a  unicode font ,such as Lucida.

The problem has been solved with your help. Thank you very much.

On 2014年5月11日 格林尼治标准时间+0800下午3时43分41秒, FrankLike via Digitalmars-d-learn <digitalmars-d-learn@puremagic.com> wrote:
>On Sunday, 11 May 2014 at 06:35:26 UTC, IceNature via Digitalmars-d-learn wrote:
>> Thank you for your help. But if I change the default console encoding,will it affect other programs,making other console program show messy code?
>
>Don't  affect,and you must set the font to  a  unicode font ,such as Lucida.
>
>
>.

On Sunday, 11 May 2014 at 07:43:07 UTC, Kagamin wrote:
> Known bug https://issues.dlang.org/show_bug.cgi?id=2742

It's not bug. Write-functions are designed to output text to stdout, and it's issue of programmer to make sure that expected "acceptor" can interpret them properly. Note that stdout may be redirected to file or be part of pipe, that does nothing with cmd console.

On Sunday, 11 May 2014 at 08:48:43 UTC, FreeSlave wrote:
> On Sunday, 11 May 2014 at 07:43:07 UTC, Kagamin wrote:
>> Known bug https://issues.dlang.org/show_bug.cgi?id=2742
>
> It's not bug. Write-functions are designed to output text to stdout, and it's issue of programmer to make sure that expected "acceptor" can interpret them properly. Note that stdout may be redirected to file or be part of pipe, that does nothing with cmd console.

OK, just tested it: after a program calls SetConsoleOutputCP(CP_UTF8); it's able to print utf-8 text correctly, but if it fails to reset the codepage back, the console remains in utf-8, so other programs will fail to print text in oem encoding in such console. If this program runs other programs, they fail to print oem text to this console, because the console expects utf-8.