Re: [NF] Parsing Hex/ASCII out of RTF

2009-01-01 Thread Ken Dibble
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

RE: [NF] Parsing Hex/ASCII out of RTF

2008-12-18 Thread Ken Dibble
\'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).

Re: [NF] Parsing Hex/ASCII out of RTF

2008-12-18 Thread Michael Madigan
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

[NF] Parsing Hex/ASCII out of RTF

2008-12-17 Thread Ken Dibble
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

RE: [NF] Parsing Hex/ASCII out of RTF

2008-12-17 Thread Christof Wollenhaupt
\'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