Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to firstname.lastname@example.org.
> Then I read this in msdn: > > "A carriage return (character value 13) or linefeed (character value > 10) will be treated as a \par control if the character is preceded by > a backslash. You must include the backslash; otherwise, RTF ignores > the control word. (You may also want to insert a > carriage-return/linefeed pair without backslashes at least every 255 > characters for better text transmission over communication lines.)" This makes it resistant to the CR/LF/CRLF conversion. > "Unicode RTF > > Word 2000 is a Unicode-enabled application. Text is handled using the > 16-bit Unicode character encoding scheme. Expressing this text in RTF > requires a new mechanism, because until this release (version 1.6), > RTF has only handled 7-bit characters directly and 8-bit characters > encoded as hexadecimal. The Unicode mechanism described here can be > applied to any RTF destination or body text." "The Unicode mechanism described here" is representing Unicode characters that are not part of one of the supported ANSI code pages with "\uN" where "N represents the Unicode character value expressed as a decimal number." > Are you sure Word isn't saving the file with 16-bit chars (UTF-16, > UCS-2, whatever). So even though RTF supports Unicode, it doesn't seem to support any Unicode encoding like utf-16. An example from the spec: "For example, the text Lab<Gamma>Value (Unicode characters 0x004c, 0x0061, 0x0062, 0x0393, 0x0056, 0x0061, 0x006c, 0x0075, 0x0065) should be represented as follows (assuming a previous \ucl): Lab\u915GValue." Gerhard