> So if I were to translate the necessary files, someone could at
> me a screenshot of it running on RO5?
I expect so, yes.
> That would be satisfying! I'll have to try to get R05 running
> emulation on Windows at least, so I can see my translation in action!
There's not yet a complete RO5 ROM image for emulation.
No, I tried RPCEmu
yesterday with the ROOL IOMD RO5.15 image. I was quite impressed, actually! But it's a
fair way off being usable, you're right.
It occurs to me that it's likely that the Wimp doesn't even
strings to be drawn -- it just throws them at the Font Manager, having
opened the desktop font without an explicit encoding specifier, so it'll
use whatever the system alphabet is set to. Perhaps, therefore, the Font
Manager should attempt to fix this case up.
It does seem like the Font Manager
would be the place to tackle this. Perhaps it could have a sort of 'intelligent'
mode where it tries to detect if strings being sent to it are properly encoded, and alter
the encoding if it detects otherwise. I suppose it would have to be quite simple logic,
though, or the overheads would be too great. Hmm...another tricky situation arising to try
to keep legacy code running as the OS moves forward!
> Any pointers as to where to start with the translation files?
Copy !NetSurf.Resources.en.Messages to !NetSurf.Resources.ja.Messages,
translate the strings, and send use the resulting file. That's about it.
The text at the top of the Messages file describes what the format is.
Modern Zap can edit UTF-8 encoded files quite happily -- you may have to
tell it that a file is UTF-8 encoded; I can't remember, off hand.
the pointers (and thanks Michael for the Zap version info). I'm running Zap 1.47 at
the moment, and have a bitmap font containing a good deal of the glyphs necessary for
Japanese. Sadly, I think I'll be doing this on Windows though, as without an input
engine, Zap can't help me much ;-)
I'll get back to you once I have something useful.