On Tue, 2013-11-05 at 14:00 -0500, Tanstaafl wrote:
On 2013-11-05 7:47 AM, Adam Tauno Williams <awilliam@whitemice.org> wrote:
Still having the same issue on:
Version: 4.1.1.2
Build ID: 410m0(Build:2)
Why would you post a reply about a 6 month old version as 'still having
the same issue...'?
Well, it has been that way since 3.6:build-304
For one, I am curious if any other user sees this issue? Or has a
work-around?
This is a user list, after all.
It is quite frustrating, I have been maintaining large documents in
OOo/LOo for years; this breaking has been unpleasant to say the least.
Why not try on the latest shipping version (4.1.3)?
Agree. I assumed by version was more current than that; as it pulls
from the LibreOffice:/Unstable/openSUSE_12.3 repository. But it appears
that repository only goes up the 4.1.1.2.
I will test again on a more current version.
--
Adam Tauno Williams <mailto:awilliam@whitemice.org> GPG D95ED383
Systems Administrator, Python Developer, LPI / NCLA
--
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
- Re: [libreoffice-users] Master Document & Alphabetical Index [Not including all sub-documents] (continued)
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.