On 2011-01-21 10:13 AM, Fabian Rodriguez wrote:
I believe the appropriate way to submit, track and try solving these
problems would be via a bug report. I can document this specifically
for this kind of problem, let me know what you think. A little
hand-holding goes a long way and pointing directly to this kind of "5
steps to submit your problematic PPS file" would work towards that.
I emphatically disagree for reasons stated more than once before.
This is the OOo way.
LibO needs a *very simple* way to submit problem documents - a way
without having to register with a site or learn how to submit a bug.
There would be volunteers who would then verify such reports, and *they*
would then open a bug report, once they have confirmed the problem.
Anything else will just get the same results OOo has had for many
years... little to ZERO *effective* problem document submissions...
--
Best regards,
Charles
--
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
- Re: [libreoffice-users] Re: And yet another .pps that Impress doesn't do right (continued)
Re: [libreoffice-users] And yet another .pps that Impress doesn't do right · Richard L. Hess
[libreoffice-users] Re: And yet another .pps that Impress doesn't do right · Marc ParĂ©
Re: [libreoffice-users] And yet another .pps that Impress doesn't do right · Charles Marcus
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.