[libreoffice-documentation] Re: First pass complete
Le 15/02/11 06:18, David Nelson a écrit : Hi David, I'm not sure what to say about this. Personally, I don't have a problem with Windows screenshots but, anticipating what certain others might say, it might be better to hold back a little longer and do those screenshots so as to put the problem to rest... I hear you :-) Time to chime in then. Just as a reminder to all : The reason is simple : Microsoft basically says no UI elements, icons or other bits of our copyright protected OS in documentation under an open source licence, that is then likely to be sold / commercialised, unless they, i.e. Microsoft, give you permission to do so. 1) MS were apparently contacted in the past (by Florian from what I have read, but I have no actual confirmation of that) about giving their permission to such use in the German OOo community documentation effort, and no positive reply was forthcoming. Remember that at the time, Sun had also signed a mutual agreement with Microsoft to settle all IP-related litigation, but the agreement was not a blanket free-for-all get off the hook. Indeed, most of the details of the agreement never came out, and I'd place no bets on MS having allowed the community free electron aspect of OOo any leeway whatsoever, contrary to whatever Sun might have gained for StarOffice, its proprietary product offering. 2) The current authoring / documentation community may wish to throw caution to the wind, but it is my understanding that TDF would not particularly relish the thought of being accused of any sort of infringement by MS, or even giving them the chance to do so. MS have had a fairly broad communication strategy of indicating when they felt others, particularly the free software community, infringed on their IP rights in one way or another. Getting market penetration is one thing - doing so at the risk of being accused of infringement is not the way to gain the support of a more widespread public, especially those in executive IT functions, who will have their own legal departments breathing down their necks. All it takes is one press release from an antagonistic player. It doesn't matter whether MS, or anyone else for that matter, is right or wrong, what matters is the effect it will have on the project as a whole. Oh, and just because OOoAuthors / ODFAuthors was unaware of this, or chose to ignore it in the past is no excuse. They (as in the organisation) should be equally aware of the problem, but the risks they take are their own. Alex -- Unsubscribe instructions: E-mail to documentation+h...@libreoffice.org List archive: http://listarchives.libreoffice.org/www/documentation/ *** All posts to this list are publicly archived for eternity ***
[libreoffice-documentation] Document 0102GS3-en
Hello, on page 6 of the document there is a point *Help formatting * * *where can this option be found? cheers Karl-Heinz -- Unsubscribe instructions: E-mail to documentation+h...@libreoffice.org List archive: http://listarchives.libreoffice.org/www/documentation/ *** All posts to this list are publicly archived for eternity ***
[libreoffice-documentation] Re: First pass complete
Everything I've seen in the Writer document has been done on Windows (Vista or 7). If we want to avoid using MS's elements, useful screen shots like showing what's on a particular property page can be done by shooting the client area of the window only. There is also a product called Window Blinds which allows skinning of Windows. -- View this message in context: http://nabble.documentfoundation.org/First-pass-complete-tp2489501p2505130.html Sent from the Documentation mailing list archive at Nabble.com. -- Unsubscribe instructions: E-mail to documentation+h...@libreoffice.org List archive: http://listarchives.libreoffice.org/www/documentation/ *** All posts to this list are publicly archived for eternity ***
Re: [libreoffice-documentation] First pass complete
Later chapters have a lot of Linux pix. Jean On Wednesday, February 16, 2011, JDługosz d6474gh...@snkmail.com wrote: Everything I've seen in the Writer document has been done on Windows (Vista or 7). If we want to avoid using MS's elements, useful screen shots like showing what's on a particular property page can be done by shooting the client area of the window only. There is also a product called Window Blinds which allows skinning of Windows. -- View this message in context: http://nabble.documentfoundation.org/First-pass-complete-tp2489501p2505130.html Sent from the Documentation mailing list archive at Nabble.com. -- Unsubscribe instructions: E-mail to documentation+h...@libreoffice.org List archive: http://listarchives.libreoffice.org/www/documentation/ *** All posts to this list are publicly archived for eternity *** -- Unsubscribe instructions: E-mail to documentation+h...@libreoffice.org List archive: http://listarchives.libreoffice.org/www/documentation/ *** All posts to this list are publicly archived for eternity ***
[libreoffice-documentation] Terminology: selecting is not enough!
I noticed in the chapters I'm working on that often various things, such as all the items on the various pages of the Options dialog, it refers to selecting an option. In one place it was more noticeable in the user was directed to select something in the dialog. In that case, the terminology is clearly wrong. Selecting is not the same as operating on the widget. Selecting directs the attention to it, and another operation may then be performed, such as toggling a check box. I suppose in some context where the option itself is referred to in an imperative sense, saying the option is selected is OK and in fact I didn't notice initially. But you'd have to be careful about the wording of the sentence: are you being imperative or directing the user's action? It's more consistent and easier to just use a word that always works. To that end, I'm changing whatever descriptive phrase was used to enabled (antonym: disabled). That works for any type of control (check box, radio box, combo-box). I'm also trying to be more careful about wording things to reflect the desired state, rather than the action. I.e. clicking on an option doesn't necessarily enable it: it will toggle it, and you shouldn't click on it unless it was off before. So don't (just) direct the user to click on something to achieve an effect. Rather, the effect occurs when the option is enabled. And of course this is the very case in which merely selecting it doesn't do anything other than make the gui draw a selection rectangle around that item. -- View this message in context: http://nabble.documentfoundation.org/Terminology-selecting-is-not-enough-tp2507713p2507713.html Sent from the Documentation mailing list archive at Nabble.com. -- Unsubscribe instructions: E-mail to documentation+h...@libreoffice.org List archive: http://listarchives.libreoffice.org/www/documentation/ *** All posts to this list are publicly archived for eternity ***
