My personal summary on the practical aspect is: * in some cases best readability is the target * in some cases exact string representation is the target * in some other cases you simply want to be fast
in the first case you are probably targetting for best user expirience. in the second case you are targetting for e.g. debugging or copy&past on the shell. in the third case you are probably listing a text or binary file on the console. for exact representations any sort of escaped character sequences might be used. readability instead requires different substitution rules. for this its possible but not in all cases equally desirable to change character sets and fonts of the displaying console. and probably the most determining factor: the reversal of the substitution rules will have much of ambiguities in most cases - only a few cases (e.g. the german char set with only some 7 extra characters) have no ambiguities. so you should save you a brainer never doing backwards translations. for the fast case you dont care about accuracy but only send e.g. a dot to the console for anything not simply convertible - thats how hex editors do it for ages. regards, Alex. ------------------------------------------------------------------------------ Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
