Re: [xsl] cursed RTF outputs

["Jean-Paul Rehr rehrjb@xxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>]

Martin Honnen, your analyze-string solution worked perfectly. Thank you!

Michael Kay, you are very right about needing to look at the bytes. In the
case of RTF I wasn't grocking that this actually needed character map
translations - it wasn't enough to simply declare an encoding and process
it. A good lesson today.

On Sat, Jan 28, 2023 at 6:08 PM Jean-Paul Rehr rehrjb@xxxxxxxxx <
xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:

> >The answer in
>
https://stackoverflow.com/questions/55439948/xslt-convert-specific-characters
-of-a-string-individually-to-a-string-includin using
> a character map or a function to convert e.g. C$ to \'E4 might help.
>
> Indeed it seems I will have to do character mapping. Thanks for your very
> useful stackoverflow response.
>
> On Sat, Jan 28, 2023 at 5:59 PM Martin Honnen martin.honnen@xxxxxx <
> xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:
>
>>
>> Am 1/28/2023 um 5:43 PM schrieb Jean-Paul Rehr rehrjb@xxxxxxxxx:
>>
>> Sorry, I confused Windows-1250 and Windows-1252. Windows-1252 does work
>> for my character set (French). Notwithstanding that, the output results
>> when opened in rtf do not show up correctly.
>>
>>
>>
>> The answer in
>>
https://stackoverflow.com/questions/55439948/xslt-convert-specific-characters
-of-a-string-individually-to-a-string-includin
>> using a character map or a function to convert e.g. C$ to \'E4 might help.
>> XSL-List info and archive <http://www.mulberrytech.com/xsl/xsl-list>
>> EasyUnsubscribe <http://lists.mulberrytech.com/unsub/xsl-list/3377836> (by
>> email)
>>
> XSL-List info and archive <http://www.mulberrytech.com/xsl/xsl-list>
> EasyUnsubscribe <http://lists.mulberrytech.com/unsub/xsl-list/3377836> (by
> email <>)