-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I've run into two issues with LibO.
First, the character spacing seems to be different than in OOo. My
company letterhead prints fine in OOo (3.1 through 3.3 RC9), but when
I open the same document in LibO, the names in the masthead wrap to
the next line. I can only fix this by moving the tab points left a
good quarter-inch or so. I've noticed this spacing anomaly in several
other documents, as well. Anyone know why this is happening, if it's a
bug, and if so where to report it?
Second: when I open a self-contained database (i.e., a single ODB file
containing all of the data inside, instead of connected to a database
server) I get an error from LibO that the file was created in a newer
version of LibreOffice. Actually, it was created in StarOffice 8 but
opens successfully in OOo 3.1, 3.2, and 3.3 RC 3. Same question: any
idea why this is happening, if it's a bug, and if so, where to report it?
- --
Steven Shelton
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk02B70ACgkQXUonIzCvpdN5HACgmNQD4DtWjYpcjWz21e7W194v
OL4An2FOyhZ5SzoE5KkGFhN+lQwwp0YH
=bmoa
-----END PGP SIGNATURE-----
--
Unsubscribe instructions: E-mail to users+help@libreoffice.org
List archive: http://listarchives.libreoffice.org/www/users/
*** All posts to this list are publicly archived for eternity ***
Context
- [libreoffice-users] Two LO issues . . . any insights? · Steven Shelton
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.