Bug 50509 - Wrong rtf list label without auto increment generated by fop revision 1036000
Summary: Wrong rtf list label without auto increment generated by fop revision 1036000
Status: CLOSED WONTFIX
Alias: None
Product: Fop - Now in Jira
Classification: Unclassified
Component: rtf (show other bugs)
Version: trunk
Hardware: PC All
: P3 normal
Target Milestone: ---
Assignee: fop-dev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-21 22:27 UTC by Jerry Fan
Modified: 2012-04-30 00:17 UTC (History)
0 users



Attachments
The original fo file (3.41 KB, application/octet-stream)
2010-12-21 22:27 UTC, Jerry Fan
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jerry Fan 2010-12-21 22:27:26 UTC
Created attachment 26436 [details]
The original fo file

I am trying to generate the rtf file with the attached fo file:

Correct content of the generated rtf should be as followed:


  a.      nested list item

  b.      nested list item with more text. nested list item with more text.

          nested list item with more text. nested list item with more text.

          nested list item with more text. nested list item with more text.

 c.       nested list item


But the result is not correct. 


 a.       nested list item

 a.       nested list item with more text. nested list item with more text.

          nested list item with more text. nested list item with more text.

          nested list item with more text. nested list item with more text.

 a.       nested list item

Lists with the roman list label has the same problem.

It seems that FOP treat these labels as bullet labels or it cannot deal with the auto increment of the alpha and roman labels.
Comment 1 Glenn Adams 2012-04-07 01:44:34 UTC
resetting P2 open bugs to P3 pending further review
Comment 2 Glenn Adams 2012-04-07 09:43:23 UTC
rtf is no longer actively maintained; if a patch is provided, it will be considered for application
Comment 3 Glenn Adams 2012-04-30 00:14:40 UTC
batch transition resolved+wontfix to closed+wontfix
Comment 4 Glenn Adams 2012-04-30 00:17:09 UTC
batch transition resolved+wontfix to closed+wontfix; if you believe this remains a bug and can demonstrate it with appropriate input FO file and output PDF file (as applicable), then you may reopen