Jonathan de Boyne Pollard wrote in a message to Andrew Grillet:

 JdBP>   If your argument is based on the principle that OS/2 users
 JdBP> are generally   more astute than Windows users, then I can
 JdBP> very easily throw that right   back at you by saying that
 JdBP> binary INI files do *not* stop OS/2 users   from fixing INI
 JdBP> files, because OS/2 users are astute enough to be able   to
 JdBP> write 3-line REXX scripts to hand-modify INI files when they
 JdBP> need to. 

 JdBP>   Or use one of the 15 or so INI file editors Out There ...

The problem is what to do in the case of file corruption.  Many INI editors
and other programs assume that the file is in a valid form or they will not
work.  With text files, it is considerably easier to repair corruption by
hand, especially since most such problems are created by INI editor bugs in
the first place.  I also find that many INI editors let you see only one
thing at a time, and there is no equivalent functionality to what can be
achieved by dumping a text file to a printer.  Admittedly, many of these
things could be looked at deficiencies of INI file editor programs rather
than of the binary file format per se, but they seem equally annoying to
the user from a practical standpoint.
 
-- Mike


---