Thread overview | |||||||||
---|---|---|---|---|---|---|---|---|---|
|
October 25, 2014 [Issue 2742] std.stdio assumes console works in utf-8 | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=2742 Vladimir Panteleev <thecybershadow@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://issues.dlang.org/sh | |ow_bug.cgi?id=1448 -- |
June 09, 2015 [Issue 2742] std.stdio assumes console works in utf-8 | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=2742 Andrei Alexandrescu <andrei@erdani.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|2.025 |D2 -- |
October 14, 2016 [Issue 2742] std.stdio assumes console works in utf-8 | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=2742 Andrei Alexandrescu <andrei@erdani.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |bootcamp Assignee|andrei@erdani.com |nobody@puremagic.com -- |
October 14, 2016 [Issue 2742] std.stdio assumes console works in utf-8 | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=2742 Vladimir Panteleev <thecybershadow@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |WONTFIX --- Comment #14 from Vladimir Panteleev <thecybershadow@gmail.com> --- I think we should let this one go. 1. To see international characters in the first place, you have to change the console font from a raster one. 2. Setting the output console CP to 65001 is not an option because it breaks spawned programs. In particular, batch files stop working. Problems also occur if the console isn't changed back. 3. Changing the data's output encoding according to the user's locale cannot be done if the output is a file or pipe, as it would be a breaking change. 4. As a result, the only way to do this is to check if the output is the console. However, because we do output via the C standard library, whatever stdout points to may change at any moment, so we cannot cache the check. 5. Since all output is done via the C standard library, it is its responsibility to handle this, however it does not. We do not have control over the MS standard C library, which does not implement this check. I think this is unactionable unless either we move away from using C for input/output (see: std.io), or someone presents a C example program that produces correct Unicode output to both console and file and which works with all C runtimes that D uses (AFAIU, this is impossible). > If this is not going to be fixed, it should be documented. The problem is with Windows and the C libraries, not D. -- |
October 14, 2016 [Issue 2742] std.stdio assumes console works in utf-8 | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=2742 --- Comment #15 from Walter Bright <bugzilla@digitalmars.com> --- When I start a command prompt in Windows, I run the command: chcp 65001 which sets it to Unicode. -- |
October 17, 2016 [Issue 2742] std.stdio assumes console works in utf-8 | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=2742 anonymous4 <dfj1esp02@sneakemail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://issues.dlang.org/sh | |ow_bug.cgi?id=7084 -- |
November 02, 2016 [Issue 2742] std.stdio assumes console works in utf-8 | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=2742 Martin Krejcirik <mk@krej.cz> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mk@krej.cz See Also| |https://issues.dlang.org/sh | |ow_bug.cgi?id=15761 -- |
Copyright © 1999-2021 by the D Language Foundation