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


@Paul, 

Paul Carr wrote
I tried that, and loaded the odt file into LO, but the styles still do not
work.

I can see that they are “there” (in the list of styles).

Thanks for the suggestion.

LO isn’t much use to me if none of the styles that I carefully developed
in my Word template over the past 10 years will work in LO.

...

LibreOffice has to import and interpret the OOXML file using filters--some
of the filters are not 100%.

So, the other option is to save from Office 2011 Word as ODF formatted
.ODT
document--let Microsoft meet the ODF standard (I think MSO 2011 for Mac is
only mostly  ODF 1.1 compliant--not ODF 1.2)

Anyhow, open that first in Word  to get a baseline for what "styles"
survived the conversion, and then import the .ODT into LibreOffice. 
Compare
the result and let us know if you get better handling of the styles that
go
missing on import of OOXML.  Ultimately,  most issues are going to be on
the
Microsoft side, although our LibreOffice filter devs play whack-a-mole
with
the Microsoft generated documents.

Of course well documented and reproducible with test case examples of
failure of the import filters are always appropriate for submission via
our
Bugzilla instance.

OK, not unexpected. But don't give up on LibreOffice just yet.  As I
mentioned, the developers working on the OOXML import and export filters are
quite talented, as we all have a vested interest in having better
interoperability with  Microsoft's OOXML standards compliant documents.

If styles captured into your templates are not too weirdly structured there
is a good chance the LibreOffice import filters can accommodate them.  But
to achieve that you would need to extract the styles from your template(s) 
into a set of simpler templates, and write up issues against conversion
problems one-by-one, ideally with a sample OOXML document and and PDF or
screen capture of the resulting style as applied.  And then a corresponding
demonstration of what the result is when imported into LibreOffice
identifying the issues with screen clips (or the XML code samples).

A bit of work, but that is what goes on continually for the project.  Sorry
that it is not more functional for you now, but that is the effort that
would be required to make it so. Hope you can dive in...

Stuart




--
View this message in context: 
http://nabble.documentfoundation.org/Styles-not-working-tp4168713p4168776.html
Sent from the Users mailing list archive at Nabble.com.

-- 
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


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.