Compose mode to imput UTF-8
Pages: 1 2
Colin Ferris (399) 1814 posts |
Have you a place where the mods could be downloaded from? |
Clive Semmens (2335) 3276 posts |
I have now! https://clive.semmens.org.uk/RISCOS/KeyBds.zip – that’s the whole miniapps containing them, but the modules are easily found within. Sadly I’ve still not found a copy of IKHG – I suspect I don’t have one any longer. Someone somewhere probably does… |
Steve Pampling (1551) 8170 posts |
Well, about 20 years ago Theo was looking for a modernised one, and did get a reply from both Castle and ROL. Whether the replies were positive, and he has a 32 bit version, is a question only he can answer. |
Clive Semmens (2335) 3276 posts |
I would be very interested in a 32-bit version!! |
Paul Sprangers (346) 524 posts |
And so would i! |
Herbert Doerfler (8783) 5 posts |
I’ve played with unicode characters and compose systems. AltKeys and MoreKeys look cool, but no source code is a bummer. Check GitHub for similar tools or hit up Stack Overflow for advice. |
adr (12133) 23 posts |
AltKeys and MoreKeys look cool, but no source code is a bummer. Check GitHub for similar tools or hit up Stack Overflow for advice. I’ve already wrote a compose system before to be used independently of the X environment for a system The problem is that I wanted to ignore the system alphabet, but by the way keys and chars are related and how the wimp uses alphabets, applications should I’ve been thinking about it and I can’t help saying to myself: what are you doing?, what the “*” are you doing? I need UTF-8 so I’m afraid riscos is not for me as things are right now. |
Rick Murray (539) 13840 posts |
The correct way is to write a keyboard handler. That way lies the path of madness…
Or within the Wimp environment, using the Wimp_ProcessKey call.
That’s exactly it. If you pass ASCII 233, is that an ‘é’ or is it part of a UTF-8 code? Literally the only way to tell is to look at the codes sent at the same(ish) time to see if it’s a valid UTF-8 sequence, which isn’t much help for those apps that don’t understand that byte != character. Sadly, there is still no built in support for falling back to Latin1 (or whatever) for bogus high bit set characters. Granted, the people that say this isn’t the job of FontManager and/or the purists that say “UTF-8 is UTF-8, end of” may be correct in their assertions, but if there’s no simple sensible way to get old 8 bit characterset apps working under UTF-8, there will not be any compelling reason to ever switch the desktop/system alphabet to UTF-8. [this, by the way, is why I don’t have much interest in 64 bit anything, there’s still plenty that can be done with the 32 bit software that exists]
I think you mean Ovation. ;) That’s just an epic cheat really. The reason you must hold down Alt when starting the app is in order for it to load its default fonts either with or without specifying the UTF-8 encoding. The only other thing I did was to teach the cursor handler about how UTF-8 sequences are constructed, so when you press the left or right keys, it’ll skip over the correct number of bytes to position the caret at the appropriate place. It’s really simple, and sadly I’ve not figured out the file format enough to know where to poke a flag to say “this file is UTF-8” to get it to load correctly. |
adr (12133) 23 posts |
I think you mean Ovation. ;) I also have tried, and like, Ovation. I thought that would be The only other thing I did was to teach the cursor handler about how UTF-8 sequences are constructed, so when you press the left or right keys, it’ll skip over the correct number of bytes to position the caret at the appropriate place. Yes, It’s not so hard, that’s the beauty of UTF-8. The balance between size, ASCII compatibility, error handling and the range of characters is fantastic. Ken Thomson and Rob Pike don’t fool around. |
Pages: 1 2