This is in reference to Bug #86578. On March 4, V. Stuart Foote said "The
issues are all result of the substantial refactoring of Writers style
frames, first put in at 4.3 then pulled out, and left in 4.4 which continues
to have issues.
as ref'd comment 4 of tdf#86578"
If I understand Stuart's comment correctly, this suggests that known
defective (?) code was recognized and backed out of the earlier 4.3
releases, but left in for any future builds, such as the 4.4 branch. I would
like to use the 4.4 branch, since it fixes several bugs (and greatly
improves the pdf export), but cannot use it due to bug 86578.
I really don't understand the rolling release scheme, but I'm having
difficulty grasping why the "refactoring" hasn't been backed out of the 4.4
branch as well. Are whatever improvements that came from the refactoring
worth causing such problems (86578 has been listed as "most annoying" so I
can't be the only one affected)?
I guess my core question is whether or not there is any chance that this bug
will be "fixed" any time soon.
Thanks for any insight ...
View this message in context: http://nabble.documentfoundation.org/Regarding-Bugs-tp4145631.html
Sent from the Users mailing list archive at Nabble.com.
To unsubscribe e-mail to: email@example.com
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
- [libreoffice-users] Regarding Bugs ?? · CVAlkan
Impressum (Legal Info)
: 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