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


Hi :)
A big 

+1
to that.  

Regards from 

Tom :)  






________________________________
From: Felmon Davis <davisf@union.edu>
To: users@global.libreoffice.org 
Sent: Friday, 3 May 2013, 17:41
Subject: Re: [libreoffice-users] Re: Paragraph styles


On Fri, 3 May 2013, Wolfgang Keller wrote:

I never even try to share documents between different programs, such
as Word and LO or OO.

I never even try to share documents between two users using both the
same program *and* the same document template, if the program is Word
(or LO /OO). With these applications, the re-use of content is
exclusively limited to raw, unformatted text. Trying anything else will
drive you up the walls.

your walls must be very adhesive. I share documents with people all the time because a couple of 
committees I've been on had me as the 'master of documents', that is, I would take other people's 
work and bundle it together, edit and produce drafts for them to work on, then I would do up the 
final report. they almost always are using some version of Word.

sure, there are problems but my walls are pretty footprint-free. but I think this goes to show not 
only are there different standards of tolerance for problems, there different magnitudes of 
problems, thus, if I were dealing with 100 people instead of six or seven, it might be a different 
issue.

of course I'm not denying there are other solutions which are technically superior in some way. 
but for many of us the situation is not as dire as you paint it, walls and all.

F.

If you need collaborative authoring, you need something that
*imposes* a pre-defined document structure (such as e.g. an XML
schema, LaTeX document classes unfortunately are not as restrictive) and
thus absolutely locks out *any* possiblity of "finger-painting", and
preferrably something that also provides seamless integration for
revision control systems such as e.g. Subversion.

With LyX/LaTeX, structured XML authoring applications (or some document
processing applications like Worperfect or Framemaker, provided the
authors are perfectly disciplined), collaborative authoring is
possible to a certain degree.

With Word (or LO/OO) it is strictly impossible at any reasonable
degree of efficiency.

If there was a way in LO/OO to imperatively re-strict the user interface
for a certain document to the application of styles defined within the
document, this might improve things, but given how styles are
implemented in LO/OO, I doubt that it would really work. Besides that
styles don't hold structure information anyway, since templates aren't
schemas in LO/OO.

Sincerely,

Wolfgang



-- Felmon Davis

You'd like to do it instantaneously, but that's too slow.

-- For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted




-- 
For unsubscribe instructions e-mail to: users+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent 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.