Just as a little reminder. Have these files been processed through Milos
Sramek's latest "odtclean.py" script:
Unless you have the facilities to run the script, I suggest you ask
Milos or Oliver to do this before publication.
On 18/02/2021 09:49, Jean Weber wrote:
I have now reviewed this chapter. It needed only one small but
significant change (from a note from Rob earlier in this thread), plus
a few trivial changes, mostly to improve page breaks. I propose to
publish it, if no one objects within 72 hours. Then I will compile the
full GS book and publish that.
On Mon, Feb 15, 2021 at 11:08 AM Jean Weber <firstname.lastname@example.org> wrote:
I have dropped all of the replacement figures into this chapter. It is
in the WiP folder.
If you've been waiting until all the figures were redone, now is the
time to review the chapter. Someone?
(Yes, I know many of you were otherwise occupied last week. I hope
you're back to documentation now.)
On Mon, Feb 15, 2021 at 4:25 AM Rob Westein <email@example.com> wrote:
Uploaded the last figures in a zip file into the WIP folder.
On 11-02-2021 03:32, Jean Weber wrote:
Thanks, Rob. I've dropped them into the chapter and uploaded the
images and the updated chapter file to nextcloud. Still more to come?
All: This chapter is still looking for reviewers.
On Wed, Feb 10, 2021 at 5:03 PM Rob Westein <firstname.lastname@example.org> wrote:
here are some updates of some images. I'm unable to upload them to
nextcloud. So I'll share them via dropbox:
On 07-02-2021 15:37, Rob Westein wrote:
Did another check and and the table definition of "Payment Type" on
page 15, just above "Defining relationships", is not correct. Field
PaymentID is missing.
Table Payment Type contains 2 fields:
- PaymentID (Integer) Primary Key
- Type (Text)
On 04-02-2021 06:56, Rob Westein wrote:
whoops! I will correct them. Thanks for your comment....
On 04-02-2021 05:51, Jean Weber wrote:
I started dropping the replacement screenshots into the chapter.
Figure 1: Text above figure says, "Make sure that the HSQLDB Embedded
entry is selected in the Embedded database drop-down menu" but the
replacement image (unlike the original image) shows the default
Figure 3 also shows Firebird Embedded in the status bar at the bottom.
If we're going to tell people to use HSQLDB (at least for the example
in this chapter), these two screenshots need to show that.
Other pix look okay.
On Wed, Feb 3, 2021 at 5:14 PM Rob Westein <email@example.com> wrote:
Placed some some screenshots in the WIP folder. It is still not
Will complete the asap!
On 01-02-2021 01:55, Jean Weber wrote:
I think the Base screenshots are the most time-consuming, due to
setting up the scenarios from a real database -- not just taking a
picture of a dialog as is often the case for other components.
On Mon, Feb 1, 2021 at 3:03 AM Rob Westein <firstname.lastname@example.org>
Should I put the new screenshots in the WIP folder?
Will do that tommorow evening.
Producing screenshots took a lot more time than expected :-(
On 30-01-2021 06:43, Jean Weber wrote:
I have applied the v7 template and cleaned up some list
page breaks, but I have not otherwise reviewed it.
The file is in the WiP folder.
Considering all the delays, I recommend that someone review the
chapter in parallel with Rob redoing the screenshots.
This is the last chapter before the book can be compiled and
To unsubscribe e-mail to: email@example.com
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/documentation/
Re: [libreoffice-documentation] GS7008 Base · Dave Barton
- Re: [libreoffice-documentation] GS7008 Base (continued)
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