digitalmars.D.bugs - [Issue 2040] New: Add codepage handling to core library
- d-bugmail puremagic.com (22/22) Apr 26 2008 http://d.puremagic.com/issues/show_bug.cgi?id=2040
- Janice Caron (6/6) Apr 26 2008 Check out std.encoding.
http://d.puremagic.com/issues/show_bug.cgi?id=2040 Summary: Add codepage handling to core library Product: D Version: 2.012 Platform: PC OS/Version: Linux Status: NEW Severity: enhancement Priority: P2 Component: Phobos AssignedTo: bugzilla digitalmars.com ReportedBy: jlquinn optonline.net I need to deal with non-unicode docs a lot. The current D library makes this unpleasant; either I need to track down and use iconv + D wrapper or code up the conversions myself. While I applaud the choice to make everything in D unicode, the real world is still out there. As a systems language especially, D should have the facilities to handle other codepage input and output natively. Java includes these abilities well-integrated with the IO package. D should do this as well. Perhaps this code might belong to std.utf. Or perhaps there should be a deeper package hierarchy, like std.text.convert. --
Apr 26 2008
Check out std.encoding. Currently, support for specific codepages is not built in (apart from ASCII, Latin-1 and Windows-1252), but class EncodingScheme has a register mechanism which allows you to add any arbitrary encoding scheme. If you would like a /specific/ codepage built into the library, let us know.
Apr 26 2008