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


Le 10/06/2015 22:39, Jay Philips a écrit :

On 06/10/2015 11:46 PM, Jean-Baptiste Faure wrote:

I am interested but I refuse to use Google Docs to contribute to
LibreOffice project. So, no input from me.

You can download the current version of the document below and make
track changes and comments to it and email it back to me. I hope that
is something that is acceptable to you.

If you don't want use Etherpad, why don't you use the wiki ?

Wikis are not WYSIWYG

To write some UI proposals, I don't find that it is a problem.
As an example, here my most precise proposal :

IMHO, the wiki format is ok for UI proposals.
To have such a document with mockups in A4 pages (european std letter) would require a lot of work with page breaks and would be less easy/fluid to read.

and hard to edit.

Yes, it's a bit boring, but it forces writer to concentrate on content, structuring, not on aesthetics.
(isn't there a thread about styles vs direct formatting ;-) ?)

I agree that inserting image is really boring.
But for text, I find it basic/rough but ok :
usually, we use 3 to 4 levels of headers, bullets, paragraph numbering, bold, italic : anything that is basic in a wiki.

Wikipedia worked on a new editor [1] : any chances to use it in TDF wiki ?

You cant format a wiki similar to a document.

As previously said, I think it's an advantage for UI proposals that have lots of images (mockups, screenshots...) : you don't waste time with page layouts/breaks !

You dont have commenting

We can have something that looks similar : for the Renaissance project, each proposal had comments.
Here is my proposal, with some comments (and one from Christoph Noack) :

I agree that it's not the same functionality level than gdoc's comments, but we can work with something so simple than that.
(and comment history would be automatically saved by wiki)

> and track changes.

Wiki have history and can make diffs.

Likely when  the document is fully finished, it would be published
to  the wiki,
similar to how we are doing with the HIG.

I would make the opposite :
work on wiki, edit, changes...
When it's finished, create an official document in A4 with first page, summary, page numbers, headers, footers, references, correct page breaks for images... well, a 'state of the art' of LibreOffice document ;-)
And then integrated in the wiki (odt & pdf) as last revision.



to test it :

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.