Please also give us the pdf so that we can compare easily. Thanks.

Marking as NEEDINFO, once you attach the PDF please reopen as UNCONFIRMED and I'll take a look at it.

Also changing version as you say it's been at least since 3.6 that you've seen this issue. Version refers to the oldest version that we see the issue, not the latest that it's been tested.

Thanks!

Created attachment 73417 [details]
January 2013 Ski Perfect Newsletter PDF

This bug is one of several issues that LO has displaying document files.  I had been trying to address it on the opensuse mailing list  opensuse@opensuse.org under two threads.

The first thread was specifically to deal with text not showing up at random on any document, .doc or .odt.

http://lists.opensuse.org/opensuse/2013-01/msg00193.html

The second thread deals with pictures not displaying properly, and again the subject of the text not showing up at random on any document, but using the newsletter as an example.

http://lists.opensuse.org/opensuse/2013-01/msg00351.html

I have already opened a bug at opensuse bugzilla on this subject.  You can see that the picture problem is only partially resolved, and the problem of the text not showing up is not resolved at all.  It will inform you of what has already been done to bring about some improvement.

https://bugzilla.novell.com/show_bug.cgi?id=798789

Have fun!

I had the same problem (with libreoffice 1:3.5.4+dfsg-4) after the recent upgrade of my system (to debian wheezy).

The solution was to remove:
  ~/.fontconfig
  ~/.fonts.conf

Hope that helps.

Hi. I am not able to reproduce this bug with the latest version of LibreOffice. When I open the .doc, it looks the same as the .pdf. 

Would you let me know if you still experience this issue? If not, I will close this as WorksForMe.

Thank you.

- Brenda


Version: 4.0.3.1 (Build ID: a67943cd4d125208f4ea7fa29439551825cfb39)
Platform: Ubuntu 13.04 

-------------------------------

LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage
There are also other ways to get involved including with marketing, UX, documentation, and of course developing -  http://www.libreoffice.org/get-help/mailing-lists

(In reply to comment #5)
> Hi. I am not able to reproduce this bug with the latest version of
> LibreOffice. When I open the .doc, it looks the same as the .pdf. 
> 
> Would you let me know if you still experience this issue? If not, I will
> close this as WorksForMe.
> 
> Thank you.
> 
> - Brenda
> 
> 
> Version: 4.0.3.1 (Build ID: a67943cd4d125208f4ea7fa29439551825cfb39)
> Platform: Ubuntu 13.04 
> 
> -------------------------------
> 
> LibreOffice is powered by a team of volunteers, every bug is confirmed
> (triaged) by human beings who mostly give their time for free. We invite you
> to join our triaging by checking out this link:
> https://wiki.documentfoundation.org/QA/BugTriage
> There are also other ways to get involved including with marketing, UX,
> documentation, and of course developing - 
> http://www.libreoffice.org/get-help/mailing-lists

Hi Brenda,
the doc file still doesn't render correctly on my laptop using openSUSE 12.3 and LibreOffice 4.0 Build 302.  Most of the problems have been resolved with the addition of additional fonts, as detailed in the opensuse mailing list referenced above.

However, the problem of the picture on the second page not being in the correct position remains.  Specifically, the picture is moved up about 3/4 of an inch on the second page.  The top of the picture is clipped or maybe it is hidden under the cover page picture?  The bottom of the second page picture shows a white band at the bottom, because nothing is displayed there.  Its blank, because the picture on that page isn't displayed correctly.  It should be obvious what I am trying to convey to you if you display the pdf file and the doc file side by side.

Good luck figuring out the bug!

Hi Munguanaweza - when replying please reply directly to FDO instead of via email as we get a lot of extra text that makes it harder to follow comments :)

Adding Need_Advice to ensure that we get an additional expert to look at this before marking as WFM.

I replied by hitting the reply button on the previous comment on FDO instead of hitting the comment link at the bottom of the page.  My mistake, this should work better.

Are you seeing the blank space at the bottom of the page that I described?  Here is a link to a picture that shows what is happening.

http://img849.imageshack.us/img849/2766/janskiperfect2.png

In case you aren't able to follow my textual description, this picture will make it clear.  There is a white band at the bottom of the page that shouldn't be there.  If you compare the pdf file with the doc file as it renders in LO, you will see the difference.

I can confirm it's partly reproducible on LO 4.0.3.3 (Win7 32bit), picture on page 2 not truncated but resized sot it leaves blank space on the bottom of page 2.

Don't think it's a bug with Win7 because it seems picture on page 1 & page 2 has different size, so it's resized to fit page width/height.
Saw the screenshot with Opensuse, picture on page 2 seems truncated on the bottom.

Opening this file in Word 2010 on a Win 7 64-bit machine the picture on page to is displayed in the same way as in LibreOffice 4.0.3.3 (see picture from comment 9). Opening the file in Word 2003 also displays the picture in the same way.

The document displayed in Word 2003:
http://imageshack.us/a/img707/1821/zf.png

Is this the original file, or has it been saved in LibreOffice (or other program than Word) at any point in time? 
In my tests I downloaded a new copy for each test just to be sure i did not mess up the file at any step.

The files that are attached are the original files.  The .doc file was produced in Word 2000.  The pdf file was produced by converting the Word 2000 .doc file with Adobe Acrobat 6.

Created attachment 80812 [details]
Screenshot on LO 4.0.4.2

Attached file is result from LO 4.0.4.2 (Win7 32bit). That image looks like comment 11.

Hi munguanaweza,

Thanks for the report!

I change the summary to make it more clear.
And at the sime time, I resolve this issue as invalid.

Not to be unfriendly. But the only way to make this work, is provide an issue with (ideally) one well described problem. With a sample file.
That is easier to triage, point and to reproduce and finally to fix :)

So pls see this as an invitation to cut down the "Writer doesn't display documents correctly." in well digestiable pieces.
Would be lovely if you can help with that!

Kind regards,
Cor

Hi,
I have read and reread your last comment several times and am not sure what you really want.  Do you wish that I should open a new bug with a different title, using the same attachments so you can fix the problem?  

There were several problems involved in this bug, all but the last has been fixed and documented in the bug.  It has been substantiated by others seeking to troubleshoot the bug.  Perhaps you can suggest a new title of your liking that will allow a speedy resolution to the problem, after reviewing the last few posts in the bug.

Thanks

Hi !
(In reply to comment #15)

> I have read and reread your last comment several times and am not sure what
> you really want.

Sorry for no being clear enough!
It's by far easiest for developers, when different problems have a separate issue. When the document has various issues, it is well possible that completely different pieces of code are involved, with various developers having experience with that.
Then when there is one issue 'does not display correctly' that is not as helpful as we, mere users, could make it :)


> Do you wish that I should open a new bug with a different
> title, using the same attachments so you can fix the problem?  

Various possibilities, but sort of logic is:
 - change the title of this issue for one bug, and reopen;
 - create new issue(s) for other bug(s);
   you may refer to the same attachment, but pls mention page of problem
   you may also refer to new issues in this start issue.

> [...]  Perhaps you can suggest a new title of
> your liking that will allow a speedy resolution to the problem, 

speady resolution is hard to guarantee, but the clearer one singel bug, the easier for the busy devs to pick it out!

(Of course, what I kindly aks you to do with description, splitting could be done by many, e.g. by me too. But failing enough spare time .. ;) )

Hope this is clear enough now.
Kind regards,

I believe that this is a duplicate of a long standing issue which is a nightmare to fix. @Cor - if you happen to know of the original bug report # I think we can close this as a duplicate. I know Michael has more than once told me these kinds of bugs all fall under the same category of another bug and he has repetitively said it's weeks of work to fix it correctly :-/

Status should be UNCONFIRMED not REOPENED as QA needs to first confirm the particular issue, setting status now

Hi Cor,and all others,

I have reopened the bug since one remaining problem mentioned in the original bug was never resolved.  

I have changed the name of the bug at your request to try and pinpoint the problem remaining.  

If the title of the bug doesn't allow developers to figure out what is the problem now, please reply with a suggestion of a better title that pinpoints the problem, and I will be happy to change the title again.

Created attachment 85513 [details]
screen shot in 4.1.1.2 on Ubuntu

Hi,

I think page 2 looks fine - at least for me.
Or can you explain waht is wrong?

Hi,
it is very easy to explain the problem.  

Please read the black color text beginning with "Hi Brenda" in comment 6 (six) above for a description of the problem.

For a picture of the problem, kindly click on the link I provided in comment 9 (nine) above, or just take another look at your screenshots from Ubuntu.  It shows the same problem, you just overlooked it.

Also, kindly note that this problem has already been verified by reading comments 10, 11, and 13.  Would these comments, and the statement in comment 17 qualify to make this bug as confirmed already?

Hi Cors,
I just took a second look at the screenshots you took in Ubuntu.  I noticed that the first page is also not displaying the graphic picture correctly.  

It should extend clear across the page without any border on the right hand side.  But there is a white band on the right hand side of page one in your screenshots.

I don't see this in LO in opensuse, but in your Ubuntu it displays incorrectly.  Could this be caused by the same issue that is causing the page two picture to be incorrectly displayed in both Linux and Windows versions of LibreOffice?

the problem is that the picture(s) at page (1 and) 2 are not covering the full sheet?

Hi Cors,
Its very easy to answer the question you asked in your last comment.

Please read the black color text beginning with "Hi Brenda" in comment 6 (six) above for a description of the problem.

For a picture of the problem, kindly click on the link I provided in comment 9 (nine) above, or just take another look at your screenshots from Ubuntu.  It shows the same problem, you just overlooked it.

Please also read the entire text in my reply in comment 22 (twenty two).

If you compare how the pictures render in LibreOffice to how they render in the pdf version of the document, which I have attached to the bug, you may see the problem.

I'm really unsure what to make of this. The doc file seems broken in itself. When opening the "Ski Perfect Newsletter" doc file in Word 2010 on OS X the image on page 2 is missing completely (that is the image which shows in LO but on page two a white bar at the bottom of the page remains).

The white bar existis on page two in LO 4.1.3.2 & 4.2a1 on OS X 10.9. Since there are more visible issue when opening the test doc in Word I have doubts if this is actually a bug with LO or if the file is just broken or badly designed.

Per several comments I am closing this as INVALID. We need a much simpler test case that demonstrates a single issue. Please provide us a 1 page (the simpler the better) document that shows a single issue. While I can confirm there is white space on the bottom of the image - I'm not convinced that it's LibreOffice's bug until I can get a much better test case. What's particularly troubling is that multiple people have reported it's broken in MSO 2007 or 2010.


Once/if you provide a simpler test case, mark as UNCONFIRMED and we'll go from there.