I understand that non-printing characters are escaped in
RTF documents with
\', and I am told that they are stored as Hex
numbers. However, there is no
tag that indicates the end of an escaped sequence.
What is it that you're trying to do? Would converting the RTF to plain
text first
\'18
may either be hex 1 (null) decimal 8 or it may be hex 18 (cancel).
No. The specification is pretty clear that hexadecimal encoding requires two
characters. So it must be hex 18:
\'hhA hexadecimal value, based on the specified character set (may be
used to identify 8-bit values).
What is it that you're trying to do? Would converting the RTF to plain text
first fix your problem?
--- On Wed, 12/17/08, Ken Dibble krdib...@frontiernet.net wrote:
From: Ken Dibble krdib...@frontiernet.net
Subject: [NF] Parsing Hex/ASCII out of RTF
To: profox@leafe.com
Date: Wednesday
Hi folks,
I understand that non-printing characters are escaped in RTF documents with
\', and I am told that they are stored as Hex numbers. However, there is no
tag that indicates the end of an escaped sequence.
So something like this:
\'18
may either be hex 1 (null) decimal 8 or it may be
\'18
may either be hex 1 (null) decimal 8 or it may be hex 18 (cancel).
No. The specification is pretty clear that hexadecimal encoding requires two
characters. So it must be hex 18:
\'hhA hexadecimal value, based on the specified character set (may be
used to identify 8-bit values).
You
5 matches
Mail list logo