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

Hi :)
Wow!!  Just found this excellent page
by William Gathoye

It is not always 100% perfect English but it's a great read and has some
quite compelling sections.  For example;
which i really hadn't realised at all.  I thought there was a major blocker
preventing this and that on-top of having to re-write 100% of the coding
first.  However it now seems that only 10% of the code needs re-writing!
The UI issue seems a lot less of a problem too!

I wish that instead of the issues being 1, 2, 3 they gave the date, perhaps
in reverse order such as


but it is MUCH easier to see those things in hindsight and it probably
wouldn't have occurred to me at the time either.  Luckily it is fairly easy
to set-up new pages, copy&paste contents and then set-up redirects from the
old pages.

The bit i never figure out is how to get the table-of-contents at the
beginning of the page.

Just out of curiosity can it be floated off to a different side?  (Even if
it can it's probably better to keep it where it is to make it consistent
with the other wiki-pages)

It looks like a huge amount of work has gone into this and it's really
great to see it collect together information from so many mailing lists.

Good work William!
Regards from
Tom :)

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.