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


Hi Nino!

Am Freitag, den 05.11.2010, 22:50 +0100 schrieb Nino Novak:
Christoph, 

while I see your arguments, please try to see the problems with messed 
up pages.

I never messed up a page in the OpenOffice.org Wiki by using the
rich-text editor. So why? :-)

So you save minutes to have better formatted tables while imposing hours 
of work to others who have to fix broken pages.

(I'm exaggerating a bit, I know, but please see the point I want to 
make.)

Sorry, I don't see a valid point. Volker referred to Manuel in a
previous mail "misuse of the so-called FCKEditor can lead to these
mistakes". So it ends up being technological imperfection, nothing more.
Those limitations can be addressed by better processes or better
tooling.

As for me, the people contributing most to the wiki [1] should decide. 
And they should also decide who is in charge to fix broken pages ;-)

From my point-of-view, I'd rater like to talk about content being added
and improved - instead of limiting the capabilities for the editors. But
however, the rich-text editor is still there ... so I don't complain
(too much) *g*

Cheers,
Christoph


-- 
E-mail to website+help@libreoffice.org for instructions on how to unsubscribe
List archives are available at http://www.libreoffice.org/lists/website/
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.