Issue 120409 - RTF Large Fields not Rendering in RTF or PDF
Summary: RTF Large Fields not Rendering in RTF or PDF
Status: CONFIRMED
Alias: None
Product: Writer
Classification: Application
Component: formatting (show other issues)
Version: 3.4.0
Hardware: All All
: P3 Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact: Alex
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-30 13:38 UTC by ej197us
Modified: 2014-03-31 19:12 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: 4.1.0-dev
Developer Difficulty: ---


Attachments
Text file showing the fields not working (20.28 KB, application/octet-stream)
2012-07-30 13:38 UTC, ej197us
no flags Details
RTF Document with large fields starts at page 6 (118.31 KB, application/msword)
2012-07-30 13:43 UTC, ej197us
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description ej197us 2012-07-30 13:38:31 UTC
Created attachment 78782 [details]
Text file showing the fields not working

RTF does not render large fields.  All of the data is present in the RTF file.  When the file is opened, partial contents are displayed on the first page, however subsequent pages are rendered with blanks.
Comment 1 ej197us 2012-07-30 13:43:49 UTC
Created attachment 78783 [details]
RTF Document with large fields starts at page 6

This is an rtf document which contains the bug.  I am viewing using 3.41 build 9592 - rev 1366353
Comment 2 ej197us 2012-07-30 13:47:14 UTC
The work flow for this project is that an xml file is merged into the the rtf which is then converted to a pdf using uno all running on a server.  The merged fields are present in the rtf to be converted to pdf.  When I open the RTF using latest build the large fields are text truncated but the space is reserved with what looks like blanks.
Comment 3 ej197us 2012-08-15 13:10:39 UTC
Any dev going to pick this up
Comment 4 ej197us 2012-09-05 11:47:46 UTC
Have I missed the answer for this. ARe there any work arounds?
Comment 5 zhengfan 2013-05-10 07:22:29 UTC
Can be reproduced in my local env.
But personally, I think this issue should be considered as an enhancement one, for:
1. Such long contents inside a field is not so common;
2. In general the issue based on the design and implementation of 'Field' in SWriter: in-edit-able (in text line), in-break-able,in-split-able. Which means, if the content of a field is longer than formatted inside 1 page, the rest part that should be assigned into the second page will be invisible.
3. In some special cases, even MS word do not support the long content field so well, for example, the long content field inside a table cell, which exist in the sample file page 6 - page 7. Open the sample file inside MS Word 2010, also partially invisible contents exist in page 7.
Comment 6 Edwin Sharp 2014-03-31 19:12:53 UTC
Confirmed with
AOO410m14(Build:9760)  -  Rev. 1582709
2014-03-30_04:11:07 - Rev. 1583103
abiword 3.0.0
Debian