Zinn wrote:Ok, it is a problem of the used operationg system and its fonts. The translation is corrent an can be moved with cut and paste to another program.
One other topic: You change the output to ? when you can't translate. In my opnion it is better to change it back to equal the input ch as it was before we starting this issue. You may have a change to correct the untranslated part. With question mark all information are lost.
- Helmut
This change was done deliberately after a lot of experiments with code page conversions.
Here is the rational behind it:
1. A code page conversion error should not appear at all. Actually,
it is hard to produce one. Most cases are returned by WinApi as "success" but with "?" as the result.
For example, when you convert a single byte of a multi-byte encoding, WinApi returns a ? and success.
There is no way to detect such cases. Outputting ? in case of an error simply
sticks to a convention that is already in place.
2. If the code page conversion fails, you get an incorrect result because the character codes
of some encoding X are treated as Unicode. Pretty much like random results.
The problem is that it may look like a valid result at first glance.
You may not notice that there has been a conversion error.
3. It is hard to imagine that something useful could be done by the user in case of a
code page conversion error. And I think about end users here.
For debugging such situations a developer will need more information anyway.
- Josef
