Re: Fwd: RE: [libreoffice-documentation] I'm not a spammer!

2013-12-02 Thread Florian Effenberger
Hello, Klaus-Jürgen kindly forwarded me your e-mail, so I'll reply inline. Note: Please Cc me on replies, as I do not read this list. K-J LibreOffice wrote on 2013-12-02 08:07: I think I know what's happening. I haven't answered a number of the anti-spam questions correctly, and the time

Re: [libreoffice-documentation] Copy documentation from OpenOffice.org?

2013-12-02 Thread C
On Mon, Dec 2, 2013 at 11:34 AM, Tom Davies tomc...@gmail.com wrote: Hi :) This whole argument is bizarre considering that we seem quite happy to include screen-shots taken on Windows platforms. it's as though we think that MS will never be bothered about us cutting into one of their core

Re: [libreoffice-documentation] Copy documentation from OpenOffice.org?

2013-12-02 Thread Tom Davies
Hi :) This whole argument is bizarre considering that we seem quite happy to include screen-shots taken on Windows platforms. it's as though we think that MS will never be bothered about us cutting into one of their core profit areas and would never try to find some way of attacking us. We seem

[libreoffice-documentation] Next task

2013-12-02 Thread John Smith
Hi Jean Just to let you know I've made a start on the Writer guide for 4.2. Regards JohnS -- To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more:

[libreoffice-documentation] Release 4.2 icon set

2013-12-02 Thread John Smith
Jean, Just had a thought on this subject. Are we staying with Galaxy, which I see is no longer listed as Galaxy(default), or are we going with Tango? I know we had this discussion earlier this year, but is it now time to bite the bullet? On another point, is the template being changed from

Re: [libreoffice-documentation] Release 4.2 icon set

2013-12-02 Thread Jean Weber
On Tue, Dec 3, 2013 at 3:20 AM, John Smith clicks...@yahoo.co.uk wrote: Jean, Just had a thought on this subject. Are we staying with Galaxy, which I see is no longer listed as Galaxy(default), or are we going with Tango? I know we had this discussion earlier this year, but is it now time to

[libreoffice-documentation] LibreOffice books discount price

2013-12-02 Thread Jean Weber
Lulu.com, where the printed copies of the LibreOffice user guides are published and sold, is having a sale: 30% off until midnight on Thursday, December 5, US east coast time. The code is: LULUVIP6131 Direct link to LO books: http://www.lulu.com/spotlight/opendocument Note: the 30% off discount

Re: [libreoffice-documentation] Copy documentation from OpenOffice.org?

2013-12-02 Thread Gary Schnabl
One point about screen captures that should be considered in authoring the user guides is eliminate their use in most cases in procedural documentation--and use them only if those instances where they are really useful. Describing the appropriate menu commands with their associated submenu

Re: [libreoffice-documentation] Copy documentation from OpenOffice.org?

2013-12-02 Thread Robinson Tryon
On Mon, Dec 2, 2013 at 6:12 AM, C smau...@gmail.com wrote: Screenshots are considered to be derivative works under US Copyright Law (refer to the US Copyright Act of 1976, Section 101 if you want details). There is nothing wrong with including screenshots (as part of your documentation) of an

Re: [libreoffice-documentation] Copy documentation from OpenOffice.org?

2013-12-02 Thread tk
Gary Schnabl wrote: One point about screen captures that should be considered in authoring the user guides is eliminate their use in most cases in procedural documentation--and use them only if those instances where they are really useful. The virtue of pictures is that they provide ready

Re: [libreoffice-documentation] Copy documentation from OpenOffice.org?

2013-12-02 Thread Jean Hollis Weber
On 3 Dec 2013, at 13:45, Gary Schnabl gschn...@swdetroit.com wrote: One point about screen captures that should be considered in authoring the user guides is eliminate their use in most cases in procedural documentation--and use them only if those instances where they are really useful.