Mail Archives: djgpp/2000/01/19/10:54:13
Manni Heumann writes:
> You pointed me in the right direction and now I've got a working
> "DE.CFG". I also noticed some other codes being incorrect. Fixed
> them to.
Excellent. It's possible that some of the mappings might be wrong if
people made them for character encodings other than Latin-1 or Unicode
(I doubt that anyone did since keyconf has always used Latin-1 in
the display code, but it's always possible). Also the keyboard scancode
numbers were reassigned in the transition from 3.12 to 3.9.x, as part
of the portability work. Although that doesn't change the output
character codes (because the new Unicode format is upwardly compatible
with the old Latin-1), it now uses different values for the KEY_*
constants, which involves some changes to the mapping tables. I wrote
a script to convert old to new format mappings, so all the old locale
tables should in theory be ok, but obviously it's hard for me to test
anything other than the UK layout as I don't know what other countries
are supposed to do, so it's great if you can help to find/fix any
problems. Many thanks!
> Just give me a last hint and tell me what to do with the
> new file. Import it into keyboard.dat and mail that to you?
Just mailing me the de.cfg would be great (keyboard.dat is only used
to avoid cluttering the disk with many files, and the individual .cfg
versions will be used in preference to it if both exist). This is my
work address, so it would be best to send it to my home email:
shawn AT talula DOT demon DOT co DOT uk.
>> Actually tabs have never been supported
>
> This really comes as a surprise. I had some code in my program that
> textprintfed "%s\t%d" and the numbers came out neatly aligned. This
> was compiled with version 3.11.
Strange indeed! I'd expect the \t to be printed the same as a space,
ie. without any alignment behaviour (although I suppose this could
have done the same thing if your strings all happened to be the same
length).
Shawn Hargreaves.
- Raw text -