Date: prev next · Thread: first prev next last
2022 Archives by date, by thread · List index

/* Font Definitions */
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
        panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
a:link, span.MsoHyperlink
@page WordSection1
        {size:612.0pt 792.0pt;
        margin:72.0pt 72.0pt 72.0pt 72.0pt;}
I don’t think this is an old version of LO. I suspect it was written in word, then the pdf 
produced, then the Open Document version created from the PDF. I have both the PDF and the ODT 
versions. There is no HTML version. 

I can’t use the PERL script. I don’t know PERL and I suspect by the time I was confident enough to 
try I could have cut and pasted everything I need manually!

I put the PDF through an online converter and got a very clean DOCX version, so that at least is a 
start. The document uses page styles. What I find confusing is that the original ODT version has 91 
custom page styles for 47 pages. The DOCX version has only 39 page styles, which still seems a lot. 
It isn’t something I use a lot though, so I don’t know if this is normal or an artefact of the 
conversion. It doesn’t appear to use footers, but text in a frame fixed to the bottom by inserting 
enough line breaks. Again this may be from the conversion.

To put this in context, this is a policy document from a public body, originally issued for 
information in PDF and ODT formats. Both versions use columns, which makes reading onscreen a bit 
of a nightmare. It also includes tables split across columns and also across pages, without 
repeating headers.  All in all I get the impression that the original document layout is a bit 
kludged together. While that may be a feature of the conversion, given the mess the ODT file is in, 
I can’t see any benefit from providing it, other than ticking an accessibility box and if tested 
would probably fail. I can’t see a screen reader making much sense of it.


Side topic from my original problem but the UK government guidance on accessible formats is 


Sent fromMailfor Windows

From:Steve EdmondsSent:04 July 2022 20:50To:users@global.libreoffice.orgSubject:Re: 
[libreoffice-users] Badly formatted document

Is it possible it is an old document from an earlier version of LO.

A while back the way LO anchored images (and frames) was changed, images
<p class=MsoNormal>in tables were particularly affected throwing out text positioning also

and I had to go through all my manuals and change my image anchoring to

"as character".

On 05/07/2022 04:59, Ian Bertram wrote:

I have been sent a graphic heavy document in ODT format. However it looks as if it has been badly 
converted from a pdf file. The layout is scrambled, headers don’t align properly and there are a 
host of other issues. It is also in columns. Is there a simple way to strip out everything bar 
the words? I have tried saving it as a txt file, but this loses a lot of the paragraph numbering 
and introduces other layout issues. Saving in rtf format is even worse.


The best I have managed so far has been by converting all the text to a single style and removing 
the columns. All the graphics however overlap text and it is often very difficult to find the 
anchor point.


Sent fromMailfor Windows



To unsubscribe e-mail to:


Posting guidelines + more:

List archive:

Privacy Policy:

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
Privacy Policy:


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.