In message <Pine.LNX.4.44.0506290050070.28254-100000(a)tarrant.ecs.soton.ac.uk>
John-Mark Bell <jmb202(a)ecs.soton.ac.uk> wrote:
Thus, when attempting to display textual data sourced from the
Messages file in the status bar, NetSurf attempts to convert it from
UTF-8 into the system local encoding. As the input data is not UTF-8
encoded, it gets this wrong (and strips top-bit-set characters in the
Yes, I forgot to say that char "ç" was lost too, so the subject of my
post was a bit misleading.
My initial intention was to provide a mechanism by which the Messages
file could specify the character set that its contents are in and then
have NetSurf convert the contents to UTF-8 on loading (or simply
dictate that Messages files should be UTF-8 encoded).
In that case, the translators need the tools to do that (note:I don't
have RO 5, if that matters). Also, there should be an easy way to update
the ressources in UTF-8 if Netsurf goes that way, since translating is
essentially an incremental process (ATM, the various internationalized
Messages contain a mix of english and other language, it's painless to
do, but it's not necessarily going to be the case with UTF-8).
Using UTF-8 would be ideal if RISC OS is to be introduced to countries
like China, Japanese, Korea :)
This fixes the status bar issue perfectly. However, it breaks the
text in the menus (specifically, the double up arrow representing the
Shift key is lost). I can't see any way around this situation
(actually, there is one, but it would only work on RISC OS 5, and it
would break the menus of every other application).