On 12/21/2011 09:53 PM, Frank Erlbacher wrote:
>
> yes, in a rtf-viewer the generated rtf-File looks good. But is isn't a
> arial-bullet. It is a symbol-middlepoint, If you open the rtf-file as
> plain text you can see it.
> The workflow I have to realize:
>
> 1. creating a rtf-template with substitution fields by customer
> 2. transforming the template to xsl-fo and substitute the fields with
> values by a third party tool
> 3. rendering to rtf with XSL-FO Converter
> 4. editing the rtf-file by customer
> 5. transforming the rtf-file to xsl-fo by a third party tool
Upcast? If this is the case, then it should be possible to parametrize
the conversion step #5 to workaround your problem.
> 6. rendering to pdf with apache fop
>
>
> The rtf-file looks (step 4) looks good. But the rtf-file generated by
> XSL-FO Converter (step 5) contains the following:
You mean step #3.
> {\*\listtable
> {\list\listid664038103\listsimple
> {\listlevel\levelnfc23\leveljc0\levelstartat1\levelfollow0
> *{\leveltext\'02\'00ยท;}*
> {\levelnumbers\'01;}
> \plain\f3\fs22\cf2
> }
The above specification (generated by our product XMLmind XSL-FO
Converter) is correct. It seems that your step #5 (the third party tool)
does not correctly interpret \levelnfc23:
Excerpts from Rich Text Format (RTF) Specification, version 1.6:
---
\levelnfcN Specifies the number type for the level:
...
23 Bullet (no number at all)
---
>
> The result of step 6 is a numbered and bulleted list:
>
> Rendering the xsl-fo (step 6) to rtf by XSL-FO Converter the result
> looks like this:
>
We are sorry but we cannot help you. Our product has not been designed
to support a workflow (i.e. step #5) like yours, that is, adapt its
output to anything other than MS-Word.
--
XMLmind FO Converter Support List
[email protected]
http://www.xmlmind.com/mailman/listinfo/xfc-support
