http://bugs.winehq.org/show_bug.cgi?id=16204
Summary: Registry: Missing MIME character set encoding Product: Wine Version: 1.1.9 Platform: PC-x86-64 OS/Version: Windows Vista Status: UNCONFIRMED Severity: enhancement Priority: P5 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: winehq.5.tahtu@spamgourmet.com
The Windows API does not offer a way to figure out the code page of a know character set name, used in MIME enviroment.
The MSDN suggest to use this hard coded table: http://msdn.microsoft.com/en-us/library/ms776446(VS.85).aspx
But inside Windows there is a way to figure out the translation by using the Registry. For example the code page of the "big5" character set can be taken by the following Registry Key:
[HKEY_CLASSES_ROOT\MIME\Database\Charset\Big5] "Codepage"=dword:000003b6 "InternetEncoding"=dword:000003b6
Unfortunately this Keys are not present in the Wine Registry.
Since there is no Windows API call to figure out this I suggest to add the related values into the Wine Registry.
http://bugs.winehq.org/show_bug.cgi?id=16204
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- OS/Version|Windows Vista |other
http://bugs.winehq.org/show_bug.cgi?id=16204
--- Comment #1 from Lei Zhang thestig@google.com 2008-11-26 16:26:56 --- What application(s) depend on this?
http://bugs.winehq.org/show_bug.cgi?id=16204
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #2 from Dmitry Timoshkov dmitry@codeweavers.com 2008-11-26 22:42:42 --- Have a look at the mlang.dll APIs.
http://bugs.winehq.org/show_bug.cgi?id=16204
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #3 from Dmitry Timoshkov dmitry@codeweavers.com 2008-11-26 22:42:53 --- Closing.
http://bugs.winehq.org/show_bug.cgi?id=16204
--- Comment #4 from Tahtu winehq.5.tahtu@spamgourmet.com 2008-11-27 01:21:23 --- Idepended what I could do with the mlang.dll API - this is an incompatibility to the Windows system.
I accept that you think you should not handle my report more respectfull - so I think think I do not need to report further bugs I found.
Good luck with whatever your intension is...
http://bugs.winehq.org/show_bug.cgi?id=16204
--- Comment #5 from Dmitry Timoshkov dmitry@codeweavers.com 2008-11-27 01:27:58 --- You haven't unswered the question in the Comment #1. If there is no real world application that uses that then there is no problem to report.
http://bugs.winehq.org/show_bug.cgi?id=16204
--- Comment #6 from Dmitry Timoshkov dmitry@codeweavers.com 2008-11-27 01:29:09 --- My comment addressed the following claim in your report:
The Windows API does not offer a way to figure out the code page of a know character set name, used in MIME enviroment.
Obviously that's not true.
http://bugs.winehq.org/show_bug.cgi?id=16204
--- Comment #7 from Dmitry Timoshkov dmitry@codeweavers.com 2008-11-27 01:35:06 --- Read http://msdn.microsoft.com/en-us/library/aa741220(VS.85).aspx about the MIME database. The MIME database in the registry is obsolete, and might be incomplete or missing completely.
http://bugs.winehq.org/show_bug.cgi?id=16204
--- Comment #8 from Tahtu winehq.5.tahtu@spamgourmet.com 2008-11-27 02:30:19 --- You are the greatest man! You know everthing!(In reply to comment #7)
and might be incomplete or missing completely.
... but it's still an incompatibility... ;-)
Once again: You are the greatest man on earth. How can I serve you?
http://bugs.winehq.org/show_bug.cgi?id=16204
--- Comment #9 from Dmitry Timoshkov dmitry@codeweavers.com 2008-11-27 02:48:57 --- (In reply to comment #8)
... but it's still an incompatibility... ;-)
Well, if you have an app that uses that, you can always reopen this bug.
Once again: You are the greatest man on earth. How can I serve you?
Send a patch for the bug 16195? :-)