First off I want to thank everyone for their input, especially you Joe
for the guidelines on how to think about all this. Another misconception
I had was in thinking that at the very least, the system font for each
platform had a standardized character set or what you referred to as
unicode. And Will, thanks for giving me the proper term 'glyph' for what
I've been referring to as 'option key characters.' This issue of Getting
Started is a keeper.
I still need to learn how to use text encoding but a least now I have an
basic understanding as to why it is needed and that's a good start.
Once again, my problem is blocks of text that are taken from the net may
occasionally have glyphs in them. When these text blocks are placed in a
hidden listbox cells and then displayed in an edit field when a row is
clicked, there is no problem. If there are glyphs in the text, they
appear in the edit field as they should. The problem arises when I want
to save the text to a binary file, if there are glyphs in any one block
of text, it corrupts the file. So it would seem that I would first need
a way to detect if a block of text has a glyph in it, a way to determine
which text encoding it is in and finally to apply that text encoding to
it. Come to think of it, it would be nice if edit fields and listbox
cells had a method for extracting the text encoding information they use
which allows them to properly display these glyphs in the first place.
Just a thought.
Anyway, I wish I could continue this discussion, but I'm going away for
Thanksgiving. I'll see you when I get back in a couple of weeks. Till
then, have a terrific holiday.
Pete Gatti
- - -
Unsubscribe or switch delivery mode:
<http://support.realsoftware.com/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
|