Date: prev next · Thread: first prev next last
2010 Archives by date, by thread · List index


 Hi Paul,

It is unfortunate indeed that your first experience with the Libreoffice
community has left you feeling this way, and whilst I agree that such
fledgling communities often lack in diplomacy and professionalism where
they are overflowing with enthusiasm, their general aims are
praiseworthy. Obviously, if zealotry becomes the overriding undertone to
the detriment of actually trying to understand a user's problems, then
there will be a problem and users will become disenchanted.

To be fair to LibreOffice, Sun/Oracle may have had a firm hand in the
management of the OOo project, but having been on many OOo lists since
the beginning, worked on QA, bugs reports, etc, I can honestly say that
users were often considered by a few developers (and I say, just a few),
as "insignificant". It was very much a case of "problem, what problem ?"
or "WONTFIX", the reasons for which seemed incongruous or illogical to
me (and others). It would be a great shame if that attitude were to be
found within the LibreOffice and TDF community, and I am sure that that
is not the intention, but as I mentioned above, this is still a
fledgling project. One can only hope that things will improve over time
as the project develops. I feel it is perhaps a little unrealistic to
expect a breakaway group to be able to replace all that was good in the
Sun/OOo Community with a perfectly rounded alternative within the such a
short time, but I things appear to be on the way to getting organised
appropriately.

As to your specific problems with the LibreOffice HTML module, I would
suggest that you lookup the problems listed in the bug reports related
to OpenOffice.org. You can find some of them here via the link below :

http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&component=Word+processor&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&short_desc=web&short_desc_type=allwords


It has to be said that, on the whole, this module (I'll call it the Web
module) has been the ugly duckling of the OOo stable for a very long
time. Even back in the days of StarOffice, before OOo even came into
existence, its capabilities as a web page editor / designer were
relatively limited, and it could not be considered W3C compliant. Even
during Sun's tenure, it was not given priority treatment, so I wouldn't
be surprised that there are still some functions of a modern-day, W3C
compliant, web page editor lacking. Perhaps the problem you have
discovered is one of them, I honestly do not know. If I repeat the query
above, replacing "web" with "span", it gives :

http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&component=Word+processor&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&short_desc=span&short_desc_type=allwords&long_desc=&long_desc_type=allwords

You might like to look through them and see if any match the behaviour
you describe or are similar.


Alex




-- 
E-mail to discuss+help@documentfoundation.org for instructions on how to unsubscribe
List archives are available at http://www.documentfoundation.org/lists/discuss/
All messages you send to this list will be publicly archived and cannot be deleted

Context


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.