Hi all, >> Still I think UTF-8 aware KEYB and DISPLAY together with old apps >> are still a lot more useful than any "you always have to use 16 bit >> wide characters" method which would only work with new apps at all. > KEYB would need no changes, 2-char wide characters would be a String. > True that not too comfortable to write the corresponding KL layouts, > but still feasible. It means I can use !1, !2, etc... on KEY files and create strings. I see, according to documentation, that I can prepare up to 79 strings. I'd like to prepare a prototype brazilian keyboard layout and try it with Mined.
I have just a question, Aitor - how to deal with dead keys and strings? Can the resulting combination point to a string? Just an example: 26 !C1 (...) <-- !C1 Pointing to acute-accent combinations in this case (brazilian keyboard) (...) [Diacritics...] ´ aá <-- Here is my doubt - Could I make "a!1"? [Strings...] !1 Bytes_related_to_á_in_UTF-8 Cheers, Henrique ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
