Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Conversion Error in CONVERT_RTF_TO_ITF

Former Member
0 Likes
403

Dear all,

I´m using FM CONVERT_RTF_TO_ITF to convert contents of an .rtf document to SapScript format. This basically works fine. Since the customer is based in Austria, there is a need to convert german special characters in the text as well (ä, ö, ü, ß).

This works for some characters, but not for all. I do get some incorrect results, that actually look like chinese characters. Here´s an excerpt of the result of a conversion

<< looking good >>

Ich habe soeben erfahren, dass sich die Flughafensteuern für Ihr Ticket

nach ... erhöht haben.

<< /looking good >>

<< looking not so good >>

Die anfallenden Geb&#40680;ren (Flughafensteuern) werden von der jeweiligen

Fluglinie an die einnahmeberechtigte Stelle zB. Flughafen AG abgegeben.

F&#40693; die Berechnung ist der Kurswechsel am jeweiligen Tag

ausschlaggebend, da die Betr&#37585;e in der jeweiligen Landesw&#37586;rung

anfallen. Daher k&#39946;nen sich die Taxen ver&#37592;dern, wenn das Ticket nicht

am Tag der Buchung ausgestellt wird.

<< /looking not so good >>

I tried to debug into form import_rtf (subsequently called by FM CONVERT_RTF_TO_ITF) but didn´t get any hints on where the error occurs.

I kind of think that it may be a problem linked to our systems codepage, since we are running a unicode database and i found a line of coding, that looks suspicious to me in form import_rtf (include LSTXKFRI, line 19)

  ascii_codepage = 1133.           " empirisch, bis genau bekannt

Any ideas?

Thanks a lot & Regards

Christoph

1 REPLY 1
Read only

Former Member
0 Likes
316

Just in case somebody´s interested! I found that the source .rtf files we were trying to convert were not valid .rtf, at least in the way SAP sees it.

We removed some of the formating information, then the FUBA was able to parse the code directly.

Thanx anyway & Kind regards

Christoph