On Wed, 1 Dec 2010, Eric Auer wrote: > Compatible apps would be apps which only display ASCII out > of themselves and which make no serious assumptions about > one byte being equal to one character. A good example are > MORE and TYPE: If you TYPE an UTF8 text with a special CON > driver which expects and renders UTF8, it will simply work > because TYPE passes the text file 1:1 and only uses plain > ASCII for built-in messages, if any. A good counter example > are PG and EDIT: They make the byte-is-character assumption > for scrolling (in particular horizontal scrolling) and EDIT > uses block graphics chars of codepages. So you have to put > your CON driver in NON-Unicode mode while using EDIT or PG.
Kind-of like "chev us" or "chev jp" in DOS/V. > Or is the idea to have "Unicode everywhere", even in the > PrintScreen hotkey, TREE, Undelete, the volume label for > SYS / FORMAT / VOL / LABEL, tools like FIND or DEBUG...? Prolly. Thought for PrtSc, isn't that what GRAPHICS is for? -uso. ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
