199
edits
Changes
Jump to navigation
Jump to search
Line 55:
Line 55: + +
→Q: Will the lack of UTF-8 support and inability to use windows-1252 encoding properly (http://tinyurl.com/6kl3d5 for details) be fixed in a future release?
::Yes, exactly. Here are three potential solutions: (1) support UTF-8 fully which, ideally, is what I would like (2) choose an alternate metadata format that doesn't have to go through an XML parser in the first place and is expected to be windows-1252 (3) use an XML parser that supports windows-1252 as a charset (not sure if one exists outside of Microsoft though).
::Yes, exactly. Here are three potential solutions: (1) support UTF-8 fully which, ideally, is what I would like (2) choose an alternate metadata format that doesn't have to go through an XML parser in the first place and is expected to be windows-1252 (3) use an XML parser that supports windows-1252 as a charset (not sure if one exists outside of Microsoft though).
:I'm not finding any non-English characters that are showing up correctly using UTF-8 encoding. UTF-8 is definitely not working as advertised.
==== Q: Is there any chance at all that Nintendo can/will brick a Wii that has the Homebrew Channel? ====
==== Q: Is there any chance at all that Nintendo can/will brick a Wii that has the Homebrew Channel? ====