Re: Binary vs. text

[flash flash@xxxxxxxx]

Thank you , Carl

≪Xy uses several control
characters -- Ascii 0, 26, 27, 174, 175, 253, 254 and 255 spring to
mind -- but the two that work the most mischief vis-a-vis binary
files are Ascii 0 and 26. These occur plentifully in binary files
but MUST BE ABSENT, save for a single terminating Ascii-26 at
End_of_File, from any XyWrite file if the file is to maintain its
integrity once displayed in XyWrite. The mischief arises because
when XyWrite displays a file, it strips out all occurrences of
Ascii-0 and truncates the file contents after the first occurrence
of Ascii-26, discarding the balance of the file. If you SAve this
defective and incomplete version of the file to disk, all of the
stripped-out and truncated information is permanently LOST, and the
file is thus irretrievably corrupted.≫

Is it correct to conclude that the reason why SAving the .dct file (as
if it were displayable text) corrupts it is that there is an instance of
a saccrosanct character in the middle of it, thereby truncating much of
the dictionary?