http://bugs.winehq.org/show_bug.cgi?id=18192
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |patch
--- Comment #2 from Austin English austinenglish@gmail.com 2009-04-24 20:03:06 --- (In reply to comment #1)
Created an attachment (id=20687)
--> (http://bugs.winehq.org/attachment.cgi?id=20687) [details]
patch that implements opening/saving files as ACP, UTF8, UTF16-LE and UTF16-BE
This patch is far too messy to send in, as it does lots of random stuff. I wrote most of it last year.
Some questions:
- Should I add a specific "Unix codepage" (CP_UNIXCP) item? (the UTF-8 option
adds a non-standard byte-order mark.) This could even do LF <-> CRLF conversion...
- Should I use IsTextUnicode()? If so, Wine notepad may then suffer from the
"Bush hid the facts" bug.
- It could even enumerate all installed codepages (EnumSystemCodepages(), I
believe), and allow the user to pick any of them. Good idea?
Note that Wine notepad uses the active code page (CP_ACP) for saving/loading, which isn't latin1/ISO-8859/CP1252 in some locales (e.g Russian uses CP1251, Japanese uses CP932).
Those are all good questions for wine-devel.
PS: Wine notepad doesn't like NUL characters (they truncate the file). This is hard to fix. I think WinXP Notepad uses a custom edit control. I don't know, though.
Testcases are always helpful.