Hi Adam
When you say "This issue is introduced" are you talking about my reference to the underline or the rtf spec?
When you say as soon as possible, does that mean soon, in the next week, the next month, etc. should I roll back to v6? There are also some other issues with the rtf conversion not being the same as the standard 1.5 spec, for instance bullets and numbering lose their tab position, in other words there is no paragraph indenting like so "pard"fi-284"li852" and the bullet is reduced to a full stop, plus if a point needs to wrap the first line is pushed back to the margin. I have applied a number of fixes to the rtf converted like so
'Replaces the built in cute editor font face and size
strRTF = strRTF.Replace("Times New Roman;}", "Arial;}")
'Removes the empty paragraph at the top of a ul or ol list which is added by cute rft conversion
strRTF = strRTF.Replace(""viewkind4"uc1"pard"cf1"f1"fs20"qj"b0"i0"ulnone "par", ""viewkind4")
'replaces the default full text justification setting
strRTF = strRTF.Replace(""qj"", ""ql"")
'replace CE's weird "b1" tag with b
'strRTF = strRTF.Replace(""b1"", ""b "")
'Add the correct bullet type with paragraph settings
strRTF = strRTF.Replace("{"pntext"'B7"tab}", ""pard"fi-284"li852"ql {"pntext"bullet"tab}")
'Gets a limited count of bullet and number points and sets the tab position
For n As Integer = 0 To 50
strRTF = strRTF.Replace("{"pntext " & n & ""tab}", ""pard"fi-284"li852"ql " & n & ". ")
Next
but as you can see ,
1.) I shouldn't have to
2). I have limited the numbering to 50, hopefully clients won't use more than 50, but this is patchy programming for a silly work around. I need an rtf converter that conforms to a standard spec, or at least show me the specification cute rtf converter works to, or better please expose the rtf stylesheet for customer editing.
Thank you
Mark