Thanks Ken,

I figured that the msg stack might be using a different font and attempted to use a script to get access to the font being used, but always came back with an error message. I have played with a ton of different fonts trying to figure out which one it could be if it is font related.

try something like
answer the effective textfont of fld 1 of stack "message box"

I have used the numToChar in this instance, but but for readability issues, to save on typing numToChar (12) , numToChar (14) over and over again, The chars as displayed in the msg box would be great for proof reading scripts. I use these Chars because they are used in MS Word for Page Break and Column Break (makes it easy to proof read, spell check and grammar check vast libraries of text that I use to generate reports.) etc. I thought it would be nice to insert one char in a script rather than the 14 or so chars I now use and have to covert to use in MS word for proofing text.. MS.doc files are cross compatible so I thought I should be alright using these in cross compatible apps. I have thought about using the File separator, Group separator, Record separator, and Unit separator numToChar 28 - 31 as well.

Would you please elaborate on your thoughts as to why I might have problems with using some of these in a cross platform application.

Thanks,

Dave Calkins

What about using a local or global array for those special characters that you use regularly? For example

c[pagebreak] or c[pb] = numToChar(12)
c[columnbreak] or c[cb] = numToChar (14)
c[fileseparator] or c[fs] = ...

Yes, still more typing than a single character but it is readable and cross-platform compatible.

MS doc files are cross-compatible but only because all special characters are encoded. Create an RTF file of a Word doc with u-umlaut for example. You won't see this character in that file.

Robert
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution

Reply via email to