On 2011-08-24 08:47, Sveinn í Felli wrote:
Sorry if this is not the proper list to ask, but before filing a bug
I'd like to know if someone has seen this before:
The following .doc file does open correctly in OpenOffice.org 3.3.0
and OpenOffice.org 3.2.1 but neither in LibreOffice 3.4.2 nor in
LibreOffice 3.4.3 OOO340m1 (Build:301) - tested on Debian and LinuxMint:
http://www.tullverket.se/download/18.4ab1598c11632f3ba9280009674/enhetsdokument+anvands+vid+import+och+export+4+blad_tv718_3.doc
Seems like a problem with lookup in many fields (Error: Source
reference not found), also looks like cell formatting is separated
onto another page than the form tables.
Curiously in LibreOffice 3.4.3 OOO340m1 the file is always opened as
read-only, no matter which permissions or filesystem is used.
Of course this could simply be a corrupted file, still it opens
correctly in OOo.
Any ideas ?
I can confirm on Suse OOO3.2.1 opens it ok and in LO3.3.4 the layout is
wrecked.
steve
--
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.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.documentfoundation.org/www/discuss/
All messages sent to this list will be publicly archived and cannot be deleted
Context
- Re: [tdf-discuss] [QA] Opening a .doc file - Regression in Libreoffice 3.4 ??? · Steve Edmonds
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.