Re: rtf question
- From: John <jhy001@xxxxxxxxxxxxx>
- Date: Tue, 08 Sep 2009 12:48:14 -0400
Andreas Prilop wrote:
On Mon, 7 Sep 2009, John wrote:
{\u201}tat
Apparently it doesn't like the {\u201} somehow.
No curly brackets around \u201 .
When I code it in line simply as \u201tat , TextEdit eats the
character after the special character, even if I put a blank
after the unicode (as \u201 tat).
The next character is the replacement character for programs
that don't understand Unicode. You could write \u201Etat ,
or simply \u201_tat if you are lazy and know that all your
programs understand \u .
Once again: Read the RTF specification(s).
http://www.google.co.uk/search?q=RTF+specification
I missed a tree while looking at the forest. I didn't realize
that the next character was required and is what is printed if
unicode isn't understood. A good idea really.
It works in TextEdit, NeoOffice, and OpenOffice if I use
{\u201E}tat or \u201Etat . Indeed it now makes sense that
the curly brackets appeared unbalanced in Neo/OpenOffice
because it "ate" the rightmost one, unbalancing them. Somehow,
TextEdit recovers.
Thank you again!
.
- Follow-Ups:
- Re: rtf question
- From: Zedex Dragon
- Re: rtf question
- References:
- rtf question
- From: John
- Re: rtf question
- From: Andreas Prilop
- Re: rtf question
- From: John
- Re: rtf question
- From: Andreas Prilop
- rtf question
- Prev by Date: Re: rtf question
- Next by Date: Re: rtf question
- Previous by thread: Re: rtf question
- Next by thread: Re: rtf question
- Index(es):
Relevant Pages
|