July 22, 2009 [Issue 3193] Support Windows-1251 as a source encoding | ||||
---|---|---|---|---|
| ||||
Posted in reply to ok96@mail.ru | http://d.puremagic.com/issues/show_bug.cgi?id=3193 --- Comment #16 from Oleg Halzov <ok96@mail.ru> 2009-07-22 03:51:47 PDT --- Dear Walter, Please take a close look at my last 3 attachements having "edit in Notepad and compile result in Console" text in descriptions. Note that all Russians have 866 codepage by default in Windows Command Prompt. Nobody will be switching 866 to any other codepage for console application. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- |
July 22, 2009 [Issue 3193] Support Windows-1251 as a source encoding | ||||
---|---|---|---|---|
| ||||
Posted in reply to ok96@mail.ru | http://d.puremagic.com/issues/show_bug.cgi?id=3193 --- Comment #17 from Stewart Gordon <smjg@iname.com> 2009-07-22 04:32:31 PDT --- Going by your screenshots and their descriptions, DMD is behaving correctly. I do, however, feel that D's stdio ought to support codepages(In reply to comment #16) > Dear Walter, > Please take a close look at my last 3 attachements having "edit in Notepad and > compile result in Console" text in descriptions. Going by your screenshots and their descriptions, DMD is behaving correctly. > Note that all Russians have 866 codepage by default in Windows Command Prompt. You mean it's hard-coded for each language's edition of Windows? That's something else that ought to change. > Nobody will be switching 866 to any other codepage for console application. Console output is an entirely separate issue from source encoding. I feel that D's stdio ought to support codepages, but it doesn't (aside from the fact that printf isn't part of D's stdio). Meanwhile, please check out my utility library http://pr.stewartsplace.org.uk/d/sutil/ -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- |
July 25, 2009 [Issue 3193] Support Windows-1251 as a source encoding | ||||
---|---|---|---|---|
| ||||
Posted in reply to ok96@mail.ru | http://d.puremagic.com/issues/show_bug.cgi?id=3193 Andrei Alexandrescu <andrei@metalanguage.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andrei@metalanguage.com --- Comment #18 from Andrei Alexandrescu <andrei@metalanguage.com> 2009-07-24 18:10:55 PDT --- I think support for codepages and other character types could be implemented in a library. That was the ambitious purpose behind std.encoding. Yet another great project for someone interested. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- |
July 27, 2009 [Issue 3193] Support Windows-1251 as a source encoding | ||||
---|---|---|---|---|
| ||||
Posted in reply to ok96@mail.ru | http://d.puremagic.com/issues/show_bug.cgi?id=3193 --- Comment #19 from Sobirari Muhomori <maxmo@pochta.ru> 2009-07-27 02:39:21 PDT --- As to console output, it's a duplicate of (runtime) bug 2742 or bug 1448. Tango and C API work correctly, phobos doesn't. As to cp1251, this ice age technology is definitely not a way to go, unicode is a future. No, it's the present. Windows works in unicode and you should use it. As to convertion of source from ANSI to OEM codepage, it's valid RFE, but hardly one will implement it. You can try yourself. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- |
July 27, 2009 [Issue 3193] Support Windows-1251 as a source encoding | ||||
---|---|---|---|---|
| ||||
Posted in reply to ok96@mail.ru | http://d.puremagic.com/issues/show_bug.cgi?id=3193 --- Comment #20 from Stewart Gordon <smjg@iname.com> 2009-07-27 03:34:29 PDT --- (In reply to comment #19) > As to console output, it's a duplicate of (runtime) bug 2742 or bug 1448. This is getting OT for this bug report, but it's 2742 to which what this conversation has drifted into is related. 1448 is a separate issue. > As to convertion of source from ANSI to OEM codepage, it's valid RFE, but hardly one will implement it. You can try yourself. I already have. See comment 17. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- |
July 28, 2009 [Issue 3193] Support Windows-1251 as a source encoding | ||||
---|---|---|---|---|
| ||||
Posted in reply to ok96@mail.ru | http://d.puremagic.com/issues/show_bug.cgi?id=3193 --- Comment #21 from Sobirari Muhomori <maxmo@pochta.ru> 2009-07-28 02:37:01 PDT --- Hmm... your library is just an API, it has nothing to do with source encoding and as far as I see it accepts utf8 text, not ANSI. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- |
July 28, 2009 [Issue 3193] Support Windows-1251 as a source encoding | ||||
---|---|---|---|---|
| ||||
Posted in reply to ok96@mail.ru | http://d.puremagic.com/issues/show_bug.cgi?id=3193 --- Comment #22 from Stewart Gordon <smjg@iname.com> 2009-07-28 03:30:01 PDT --- (In reply to comment #21) > Hmm... your library is just an API, it has nothing to do with source encoding As has a lot of the discussion here from comment 13 onwards. Maybe, to avoid confusion, we should continue this conversation at bug 2742. Or perhaps even better, on the newsgroup. > and as far as I see it accepts utf8 text, not ANSI. Not quite. It communicates with the console in the console codepage. Application code communicates with it in UTF-8. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- |
Copyright © 1999-2021 by the D Language Foundation