Ouch! I feel sufficiently admonished! Well I learn something new every day. This still leaves the problem of using a font that does not contain the character code you are seeking. Encodings.WindowsLatin1.Chr(153) still does not produce the Trademark Symbol using the default System font on Windows.
Tom > > Ow! No, you don't. The global Chr() function is defined for > values 0 through 127 *only*. The above code is incorrect, > ill-advised, improper, and just plain a Bad Idea. Please > don't use it, nor advise others to use it. > > To answer the original question... ASCII values range from 0 > through 127. Anything else is not an ASCII value, but > something else. > Non-ASCII characters have different code points in different > encodings. If you're going to specify a non-ASCII character > by its code point, then you must have some encoding in mind. > Don't expect REALbasic to read your mind, though; be explicit. > > For example, if it's the Windows-Latin-1 encoding that you > have in mind, when you hold the belief that 153 is the > Trademark symbol (I have no idea whether this is the case, > but just suppose it for the sake of this example), then you > should use Encodings.WindowsLatin1.Chr(153). Do NOT use just > Chr(153), since > 153 is not in the defined range for Chr, and if you are > unlucky the result will happen to be what you expected on > your machine, only to generate the wrong result on some other machine. > > Best, > - Joe > > -- > > Joseph J. Strout > [EMAIL PROTECTED] _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
