Issue 106082 - A paragraph inside a section is not printed directly after opening the text doc
Summary: A paragraph inside a section is not printed directly after opening the text doc
Status: CLOSED FIXED
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOO310m19
Hardware: All Unix, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: Oliver-Rainer Wittmann
QA Contact: issues@sw
URL:
Keywords:
Depends on:
Blocks: 99999
  Show dependency tree
 
Reported: 2009-10-20 11:49 UTC by Joost Andrae
Modified: 2013-08-07 14:44 UTC (History)
2 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Joost Andrae 2009-10-20 11:49:57 UTC 
All Documents mentioned within this issue have been directly sent to
Oliver-Rainer. I cannot attach them because they are confidential.


A certain paragraph in a document is not being printed.

To reproduce please follow these steps:

- open the attached document DocToPrintNew.odt
- open "Navigator" 
- click to  "SectionConsiderants"=> focus on "Considérant en droit" (see
ScreenShotNavigator.png)
- print only the pages 4-5 
- see the missing paragraph in result (same as in the attached file print_doc.pdf)

This behavior happens only once a time where the document is opened and
immediately printed.   
When the document is updated before printing, all the paragraphs will be printed.   

I also attached the template that has been used to create the sample document.
There it is visible that there are two sections that contain "Considérant en
droit". One of them is hidden in the sample document.
Comment 1 Oliver-Rainer Wittmann 2009-10-20 13:31:55 UTC 
fixed in cws c07v026 - changed file:
/sw/source/core/layout/sectfrm.cxx, rev. 276497
Comment 2 Joost Andrae 2009-10-22 09:48:27 UTC 
ja->hi: please verify
Comment 3 h.ilter 2009-10-22 10:01:44 UTC 
And it occurred only on Unix.
Already verified the fix
Comment 4 h.ilter 2009-10-22 10:02:15 UTC 
Closed