OTOH, doing new screenshots is a great way to check whether the text makes
sense, is missing no important info, and is correct.
On Sat, 29 Feb 2020 at 19:58 Jean Weber <firstname.lastname@example.org> wrote:
My opinion, FWIW: I think it's a waste of time to redo the screenshots
in Windows, though I have no objection to doing so. Some of the
sections in Chapter 2 may be Linux-only; I'm not sure. And a chapter
with new screenshots will need a quick review to make sure they are
all okay, correctly anchored, and so on.
On Sat, Feb 29, 2020 at 7:03 PM Rob Westein <email@example.com> wrote:
On 28-02-2020 10:32, Pulkit Krishna wrote:
Hello Jean, Dan and Rob,
I have adjusted the screenshots that you commented on so that they
current standard (For example on page 24, I have cropped the figure so
it does not include the german title.
I have adjusted the screenshots but if you want you can take the
from the published, replace the screenshots and put it back there and
inform the mailing list.But I would advice you to skip chapter 1 as
are not many needs of screenshot replacement and I have adjusted all
Just to be clear... I thought we agreed to use Windows OS to create the
screendumps... (Dan told us to use Windows OS) The first Image in
chapter 1 does not looks like Windows at all...
So I redo all screenshots in Windows??
To unsubscribe e-mail to: firstname.lastname@example.org
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/documentation/
Impressum (Legal Info)
: 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