Re: Ping Francis

[F Campos Costero]

Keith,
Have you been able to clone the repository or otherwise recover your files?
Is there something you need from me?
Francis

On Tue, Mar 5, 2024 at 4:33 PM Keith N. McKenna 
wrote:

> dennis.hamil...@acm.org wrote:
> > Keith,
> >
> > If you made the mess using GitHub, you can revert git changes.  You
> might have
> > to do several, but there should be some way to get back to a clean point.
> >
> Actually, no I cannot. I had to areset my system, therebye losing all my
> applications except what came installed on the system.
>
> That is how I noticed the problem in the first place. Because of that, I
> can no longer revert the changes from GitHub.
>
> Regards
> Keith
>
>
>
> -
> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: doc-h...@openoffice.apache.org
>
>

Re: Ping Francis

[F Campos Costero]

 Oops! I responded to Dennis by mistake. It's late.

Hi Keith,
I checked the latest commits on the Writer-Guide, Calc-Guide,
Impress-Guide, Templates, and Getting-Started-Guide on the apache
repository and they all match the latest commits on my local copy. I don't
think anything is different on my local repository. The most recent commit
is to the Impress guide on Feb. 28 and the most recent changes on Writer
and Calc are on the 22nd and 24th. Does the problem you are seeing go back
that far?
Francis

On Tue, Mar 5, 2024 at 12:18 AM F Campos Costero 
wrote:

> Hi Keith,
> I checked the latest commits on the Writer-Guide, Calc-Guide,
> Impress-Guide, Templates, and Getting-Started-Guide on the apache
> repository and they all match the latest commits on my local copy. I don't
> think anything is different on my local repository. The most recent commit
> is to the Impress guide on Feb. 28 and the most recent changes on Writer
> and Calc are on the 22nd and 24th. Does the problem you are seeing go back
> that far?
> Francis
>
> On Mon, Mar 4, 2024 at 4:42 PM  wrote:
>
>> Keith,
>>
>> If you made the mess using GitHub, you can revert git changes.  You might
>> have
>> to do several, but there should be some way to get back to a clean point.
>>
>> Francis,
>>
>> Ordinarily, you do a quick branch of the clone without synchronizing to
>> the
>> main repository first.  Then push the branch back to the repo.  That
>> might
>> create a lot of trouble.  Keith would have to deal with merge conflicts
>> in
>> accepting your changes..
>>
>> Keith and Francis,
>>
>> You have an unusual way of using branches for the AOO docs, so those
>> standard
>> solutions might not work in this situation.  If Francis has commit
>> privileges
>> to the main repository, there are other solutions.
>>
>> I bid you good fortune.
>>
>> -Original Message-
>> From: F Campos Costero 
>> Sent: Monday, March 4, 2024 12:40
>> To: doc@openoffice.apache.org
>> Subject: Re: Ping Francis
>>
>> Hi Keith,
>> I'll take a look at this tonight. I'm in the US eastern time at the
>> moment, so
>> within the next six hours or so. If I have the slightest doubt about what
>> a
>> commit will do, I'll post a message here so we can consult. I don't want
>> to
>> create any problems while "fixing" things.
>> Francis
>>
>> On Mon, Mar 4, 2024 at 1:50?PM Keith McKenna 
>> wrote:
>>
>> > Greetings Francis;
>> >
>> > It seems that I totally screwed up the openofficce-docs repository the
>> > other day. Only thing that is still correct is the Getting Started
>> Guide.
>> >
>> > Can you please recommit everything from your clone to the main
>> > repository except The Getting Started Guide.
>> >
>> > Thank you very much.
>> > Regards
>> > Keith
>> >
>> >
>> > -
>> > To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
>> > For additional commands, e-mail: doc-h...@openoffice.apache.org
>> >
>> >
>>
>>
>>

Re: Ping Francis

[F Campos Costero]

Hi Keith,
I'll take a look at this tonight. I'm in the US eastern time at the moment,
so within the next six hours or so. If I have the slightest doubt about
what a commit will do, I'll post a message here so we can consult. I don't
want to create any problems while "fixing" things.
Francis

On Mon, Mar 4, 2024 at 1:50 PM Keith McKenna 
wrote:

> Greetings Francis;
>
> It seems that I totally screwed up the openofficce-docs repository the
> other day. Only thing that is still correct is the Getting Started Guide.
>
> Can you please recommit everything from your clone to the main
> repository except The Getting Started Guide.
>
> Thank you very much.
> Regards
> Keith
>
>
> -
> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: doc-h...@openoffice.apache.org
>
>

Re: [I] AOO41CG01 Ready for Next Revies. [openoffice-docs]

[F Campos Costero]

I went through all of the chapters and applied the OOoTextBody_ListIntro
style where it was needed. I committed the changes with a relatively
lengthy commit message so it would be clear later what I did.

Francis

https://github.com/apache/openoffice-docs/commit/84927ed0aa17d6d84cc305e36876fe15b16648b8

On Fri, Feb 23, 2024 at 5:44 AM Keith N. McKenna 
wrote:

> FJCC (via GitHub) wrote:
> >
> > FJCC commented on issue #137:
> > URL:
> https://github.com/apache/openoffice-docs/issues/137#issuecomment-1960535325
> >
> > Keith - since you found several instances of the wrong paragraph
> style in text preceding a list, I think I should go through the other
> chapters and fix that error. Let me know if you agree and that you will
> hold off on editing other chapters so we don't end up with conflicting
> edits.
> >
> >
> That sounds likw=e a very good idea.Francis. For now I will concentrate
> on ghetting the Writer Guidebook compiled and it and the chapters
> published to the wiki.
>
>
> -
> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: doc-h...@openoffice.apache.org
>
>

Impress guide

[F Campos Costero]

I'm going to start working on the Impress guide. The big items are
replacing the outdated images and incorporating appropriate references to
the Sidebar. I hope Michele will then be able to edit the text.

The Calc guide has already been fully edited by Michele and I have reviewed
those changes and updated the front matter. There is surely more to do,
because these things are never really done, but we reached a good stopping
point.

Regards,
Francis

Re: [I] AOO41WG10 Ready for 3rd Review [openoffice-docs]

[F Campos Costero]

I replaced the version of chapter 10 with the one that was the result of
commit 5336d21

On Wed, Jan 3, 2024 at 11:07 AM Keith N. McKenna 
wrote:

> FJCC (via GitHub) wrote:
> >
> > FJCC commented on issue #126:
> > URL:
> https://github.com/apache/openoffice-docs/issues/126#issuecomment-1871501951
> >
> > I think we have gotten tangled up here. Issue 118, which is closed,
> was opened on 2023-12-18 and it was a review of chapter 10. There are then
> commits on the 18th and the 20th after I and Michele accepted Keith's
> changes and made some more edits. Here is the git log of those.
> >
> > > commit 5336d2149344969cb119cf17a31ac779388b3629
> > > Author: Francis 
> > > Date:   Wed Dec 20 16:16:12 2023 -0700
> > >
> > > AOO41WG410...odt Edited by Michele, reviewed by FJCC
> > >
> > > commit 7bc935b0bbd0b857991cee6c7a16e86ccd8f1aeb
> > > Author: Francis 
> > > Date:   Mon Dec 18 15:59:08 2023 -0700
> > >
> > > AOO41WG410...odt accept Keith's edits + a few corrections
> >
> > The latest commit, ba4a1b3, seems to have the version of chapter 10
> that went into issue 118. If Keith can confirm that a mistake has been
> made, I can make a new commit with the version of chapter 10 that came out
> of issue 118, with Michele's edits.
> >
> >
> Yes there was a mistake there. Please re-commit.
>
> Regards
> Keith
>
>
>
> -
> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: doc-h...@openoffice.apache.org
>
>

Re: Problem with footer in AOO41WG11.odt

[F Campos Costero]

I just looked at AOOWG4111-UsingMailMerge.odt from the Writer-Guide branch
and I don't see that problem. I looked at my local copy that is up to date
with the Writer-Guide branch on GitHub. Should I email my copy to your
personal email?

On Fri, Dec 1, 2023 at 10:37 AM Keith N. McKenna 
wrote:

> Greetings all;
>
> I am having a strange problem with the Footer in chapter 11 of the
> Writer Guide. The footer has page number field followed by a chapter
> field of type chapter number and name. Up to page 9 all is correct. From
> page 10 onwards it starts picking up random text from the page. and I
> cannot find a way to change it.
>
> Hopefully someone will have an idea of how to straighten it out. Any
> help would be greatly apprteciated.
>
> Regards
> Keith
>
>
>
> -
> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: doc-h...@openoffice.apache.org
>
>

New AOOdoc.ott

[F Campos Costero]

Keith,
I see you made a change to AOOdoc.ott. Is that ready for me to download the
latest version or are more changes in the works?
Regards,
Francis

New folder structure

[F Campos Costero]

Keith - I see you made an OldNamingConvention folder in the Writer Guide
and moved some files into it. Since this was done after my commits 887145d
and d8e6530, I get the impression those commits caused some problems. I'm
sorry if they did. All I meant to do is update my local repository with
your most recent changes and then commit the latest edits to AOO41WG8.odt.
I didn't touch any other files as far as I know. Did my commits cause a
problem?
Regards,
Francis

Document footers

[F Campos Costero]

Keith,
As Michele and I review the Writer Guide, I see that the content of the
footers is not consistent. Instead of trying to deduce the correct pattern,
I thought it better to ask.
It seems that on the pages with the OOoPageStyle style, which is most of
each chapter, the footer should have the chapter title (entered with a
Chapter field, which gets its value from the paragraph with the OOoHeading
0 paragraph style) and the page number, separated with a |. Page numbers go
on the outside margin.
On the pages with the OOoFrontMatter page style, the footer has a Title
field and page number, again separated with |.
Pages with the styles OOoCopyright and OOoFirstPage do not have anything in
the footer.
Is that the right pattern?
Regards,
Francis

Re: Back to documentation work

[F Campos Costero]

Welcome back, Keith!


On Wed, Oct 11, 2023 at 11:40 AM Keith N. McKenna 
wrote:

> After multiple system problems and personal issues, I am back to work on
> documentation with an new Windows 11 Pro system. I will now be spending
> the bulk of my volunteer time on getting the initial Writer documents
> published.
>
> I am pleased to see that work is proceeding on the Calc Documents.As
> well as the work in publishing the Getting Started manual in mwiki
> format being pursued.
>
> Thank you all for the hard work you have put in to getting these long
> neglected documents revived.
>
> Regards
> Keith
>
>
> -
> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: doc-h...@openoffice.apache.org
>
>

Re: Missing figure 16 in PDF for Chapter 11 - Setting Up and Customizing Apache OpenOffice

[F Campos Costero]

Thanks, Dick! I'll see if I can fix that.
Francis

On Thu, Aug 3, 2023 at 7:12 AM Dick Groskamp
 wrote:

> In the PDF for chapter 11 (Chapter 11 - Setting Up and Customizing
> Apache OpenOffice
>  -)
>
> it seems figure 16 is missing
>
> --
> DiGro
> ___
> Apache OpenOffice 4.1.14 (Dutch) and scanned with Ziggo Safe Online
> (F-Secure)
>

Re: Need help stripping front matter from chapter files

[F Campos Costero]

On Wed, Jul 12, 2023 at 4:47 PM Keith N. McKenna 
wrote:

> Jean Weber wrote:
> > MD is a user-defined variable, which was inserted into the master
> document
> > for the book.
> > Jean
>
> Jean;
>
> If you could give a a brief rundown on how that variable is inserted
> into the master document it would be a great help in creating the full
> book.
>
> Regards
> Keith
>
> >
> > On Wed, 5 Jul 2023 at 06:18 F Campos Costero 
> wrote:
> >
> >>
> >> I noticed that in the Format -> Sections dialog that Section 1 is set
> to be
> >> hidden when MD != 0. I guess that MD somehow represents Master Document
> and
> >> that the section should be hidden if the document is part of a master
> >> document. I do not know whether MD is a user-defined variable or if it
> is a
> >> predefined. I will look into that but I have other things to do at the
> >> moment.
> >> Francis
> >>
> >
>
>
>
> -
> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: doc-h...@openoffice.apache.org
>
>
Keith,
I played with a couple of chapters in a master document and came up with
the following method.
1. I chose the menu item File -> New -> Master Document
2. I inserted some dummy text to serve as the front matter of the master
document.
3. I used the Navigator to insert chapters 3 and 4 as sub documents. Their
individual front matter was visible at this point.
4. At the end of the front matter of the master document, I wrote the line
"Here is MD:"
5. WIth the cursor at the end of that line, I chose the menu Insert ->
Fields -> Other and chose the Variables tab.
6. Under Type, I chose Set Variable, in the Name box I wrote MD, and in
Value I entered 1. I clicked Insert. The front matter within chapters 3 and
4 is no longer visible.
7. I selected the whole line "Here is MD: 1" (which displays the value set
for MD) and chose the menu Insert -> Section. On the Sections tab, I set
the name of the new section to Contains_MD, chose that it be hidden, and
clicked Insert. The line "Here is MD: 1"is no longer visible and the front
matter within chapters 3 and 4 remains hidden.

If you want to see the hidden section containing MD, select the menu Format
-> Sections. Pick Contains_MD from the list on the left and remove the
checkmark from the Hidden option.
There may be a more elegant way to do that, but the method seems to work.

Francis

Re: Need help stripping front matter from chapter files

[F Campos Costero]

Thanks, Jean. That makes sense.
Francis

On Tue, Jul 4, 2023 at 7:05 PM Jean Weber  wrote:

> MD is a user-defined variable, which was inserted into the master document
> for the book.
> Jean
>
> On Wed, 5 Jul 2023 at 06:18 F Campos Costero 
> wrote:
>
> >
> > I noticed that in the Format -> Sections dialog that Section 1 is set to
> be
> > hidden when MD != 0. I guess that MD somehow represents Master Document
> and
> > that the section should be hidden if the document is part of a master
> > document. I do not know whether MD is a user-defined variable or if it
> is a
> > predefined. I will look into that but I have other things to do at the
> > moment.
> > Francis
> >
>

Re: Need help stripping front matter from chapter files

[F Campos Costero]

On Tue, Jul 4, 2023 at 12:02 PM Keith N. McKenna 
wrote:

> F Campos Costero wrote:
> > On Sun, Jul 2, 2023 at 5:44 PM Keith N. McKenna <
> keith.mcke...@comcast.net>
> > wrote:
> >
> >> Greetings all;
> >>
> >> As I am getting ready to start publishing some of the Writer Guide's
> >> chapter files I am running across a problem stripping the front matter
> >> from the files to be able to then combine them into the complete book.
> >>
> >> The problem is with the heading for the TOC. As it is not a part of the
> >> TOC, it has to be deleted separately. This can be done, but the page
> >> break cannot be deleted causing a blank page to remain between the
> >> chapter tittle and the the start of the text of the chapter. I foresee
> >> this creating havoc when it comes time to compile the complete book.
> >>
> >> Is there a way to delete this extra page, or will it be taken care of
> >> when creating the full book.
> >>
> >> Thanks in advance for any insight that you can Proved
> >> Keith
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> >> For additional commands, e-mail: doc-h...@openoffice.apache.org
> >>
> >> Hi Keith,
> > I don't understand where the page break is coming from in the chapter I'm
> > looking at. I'm using AOO41WG4. I see a hard page break between the ToC
> and
> > the Introduction. I don't see one between the paragraph with the heading
> > "Publication date and software version" and the heading for the ToC but
> > something causes the ToC heading to be on a new page. Does that agree
> with
> > what you see? What exactly do you delete to get the blank page? Should I
> be
> > looking at another document?
> > Francis
> >
> Francis & Michele;
>
> Yes That is what I see. What I do to create that blank page is to first
> select the Toc Header and change the style to
>
>
> -
> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: doc-h...@openoffice.apache.org
>
> Ok, I made some progress. The key is that the page with the Copyright
heading and the pages with the ToC are in section. Here is what I did on a
copy of AOO41WG4.
-
Select the menu Format -> Sections.
Select Section 1 on the left. That is the only section in this document but
others may have more sections
Click Options
Set the background to red
Click OK twice to get back to the document and confirm that the text I want
to delete now has a red background.
Go back to Format -> Sections.
Pick Section 1.
Click Remove.
Click OK
The red background is now gone and I can delete the text and ToC without
generating a blank page.

I noticed that in the Format -> Sections dialog that Section 1 is set to be
hidden when MD != 0. I guess that MD somehow represents Master Document and
that the section should be hidden if the document is part of a master
document. I do not know whether MD is a user-defined variable or if it is a
predefined. I will look into that but I have other things to do at the
moment.
Francis

Re: Need help stripping front matter from chapter files

[F Campos Costero]

On Sun, Jul 2, 2023 at 5:44 PM Keith N. McKenna 
wrote:

> Greetings all;
>
> As I am getting ready to start publishing some of the Writer Guide's
> chapter files I am running across a problem stripping the front matter
> from the files to be able to then combine them into the complete book.
>
> The problem is with the heading for the TOC. As it is not a part of the
> TOC, it has to be deleted separately. This can be done, but the page
> break cannot be deleted causing a blank page to remain between the
> chapter tittle and the the start of the text of the chapter. I foresee
> this creating havoc when it comes time to compile the complete book.
>
> Is there a way to delete this extra page, or will it be taken care of
> when creating the full book.
>
> Thanks in advance for any insight that you can Proved
> Keith
>
>
> -
> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: doc-h...@openoffice.apache.org
>
> Hi Keith,
I don't understand where the page break is coming from in the chapter I'm
looking at. I'm using AOO41WG4. I see a hard page break between the ToC and
the Introduction. I don't see one between the paragraph with the heading
"Publication date and software version" and the heading for the ToC but
something causes the ToC heading to be on a new page. Does that agree with
what you see? What exactly do you delete to get the blank page? Should I be
looking at another document?
Francis

Re: [GitHub] [openoffice-docs] FJCC commented on issue #102: AOO41WG4 Needs Review

[F Campos Costero]

On Wed, Jun 21, 2023 at 1:20 PM Keith N. McKenna 
wrote:

> FJCC (via GitHub) wrote:
> >
> > FJCC commented on issue #102:
> > URL:
> https://github.com/apache/openoffice-docs/issues/102#issuecomment-1599616502
> >
> > On Sat, Jun 17, 2023 at 12:24 PM Keith N. McKenna ***@***.***>
> > wrote:
> >
> > > AOO41WG4 is ready for review.
> > >
> > > —
> > > Reply to this email directly, view it on GitHub
> > > , or
> unsubscribe
> > > <
> https://github.com/notifications/unsubscribe-auth/ACGKX6PYJZIGOPZPVGL4T3DXLXY6JANCNFSM6AAZKL7NU4
> >
> > > .
> > > You are receiving this because you are subscribed to this thread.
> > >
> > Hi Keith,
> > I have reviewed AOO41WG4. I have not yet accepted your deletion of
> Figure
> > 53 on page 49. Did you mean to delete that figure? I think the text
> is
> > already very brief and it should be expanded if there will not be a
> figure.
> > Regards,
> > Francis
> >
>
> Francis;
>
> That should be a deletion and then an insertion of the picture again to
> correct the problem of the Caption not showing properly for Figure 53,
> and figure 54 showing as Figure 53 rather than 54.
>
> Regards
> Keith
>
> > > Message ID: ***@***.***>
> > >
> >
> >
> >
>
>
>
> -
> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: doc-h...@openoffice.apache.org
>
> Ok, got it. I'll make sure those things are correct.
Francis

Re: AOO41WG2 Ready for Review

[F Campos Costero]

On Tue, Jun 13, 2023 at 11:05 AM Keith N. McKenna 
wrote:

> 3rd review of AOO41WG2 is needed. Whomever does it please close the open
> issue when done.
>
> Regards
> Keith
>
>
> -
> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: doc-h...@openoffice.apache.org
>
>
I reviewed this and passed that version on to Michele. I'll push her
version to the repository and close the issue.
Regards,
Francis

Re: Calc needs another review

[F Campos Costero]

On Thu, May 4, 2023 at 8:40 AM Keith N. McKenna 
wrote:

> F Campos Costero wrote:
> > On the Calc Guide, I will first accept or reject all of the changes
> > currently shown and push those versions back to the repository. Judging
> > from the first chapter, all of my and Dick's changes have not yet been
> > accepted. I hope I will have time after that to do a full review of each
> > document. Let me know if that plan isn't good.
> > Regards,
> > Francis
> >
> That sounds good Francis. Thanks for moving this along.
>
> Keith
>
> > On Tue, May 2, 2023 at 9:08 AM Keith N. McKenna <
> keith.mcke...@comcast.net>
> > wrote:
> >
> >> F Campos Costero wrote:
> >>> I'll take a look at the Calc changes.
> >>> Francis
> >>>
> >>
> >> Thanks Francis. I will finish with the Getting started changes from
> >> Czeslaw morning, and will get back to the Writer Guide this afternoon.
> >>
> >> Regards
> >> Keith
> >>
> >>> On Mon, May 1, 2023 at 1:07 PM Keith N. McKenna <
> >> keith.mcke...@comcast.net>
> >>> wrote:
> >>>
> >>>> Digro has had changes for Calc waiting review for some time could
> >>>> another member of the team start reviewing those so that Guide can
> start
> >>>> Moving along.
> >>>>
> >>>> I am still trying to catch up with with the Getting Started changes
> from
> >>>> Czeslaw that Francis made and re publishing them, as well as trying to
> >>>> work on the Writer Guide.
> >>>>
> >>>> I have also been spending a lot of time taking my Girlfriend in and
> out
> >>>> of the Veterans Administration Hospital in the Jamaica Plains section
> of
> >>>> Boston for medical issues.
> >>>>
> >>>> Thank you all in Advance
> >>>> Keith
> >>>>
> >>>>
> >>>> -
> >>>> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> >>>> For additional commands, e-mail: doc-h...@openoffice.apache.org
> >>>>
> >>>>
> >>>
> >>
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> >> For additional commands, e-mail: doc-h...@openoffice.apache.org
> >>
> >>
> >
>
>
>
> -
> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: doc-h...@openoffice.apache.org
>
> I just pushed new versions of all the Calc Guide chapters. I limited my
changes to formatting and fixing typos. Some sections would benefit from
broader revisions but I did not start that. Michele's input on that would
be very valuable.
I did not modify the front matter of any of the chapters and that will have
to be updated. I assume Keith has text that can be used for that with
minimal revisions.

Regards,
Francis

Re: Help need with compiling the Getting Started Book

[F Campos Costero]

On Fri, May 26, 2023 at 8:00 AM Keith N. McKenna 
wrote:

> F Campos Costero wrote:
> > On Mon, May 22, 2023 at 8:54 AM F Campos Costero 
> > wrote:
> >
> >>
> >>
> >> On Sun, May 21, 2023 at 12:07 PM Keith N. McKenna <
> >> keith.mcke...@comcast.net> wrote:
> >>
> 
> >>>> On Wed, May 17, 2023 at 11:21 AM F Campos Costero <
> >>> fjcc.apa...@gmail.com>
> >>>> wrote:
> >>>>
> >>>
> >>> Hi Francis;
> >>>
> >>> Thank you for looking into this. The files to be used are all at the
> top
> >>> level. The ones in ForWiki, already have all the front matter in them
> >>> and are strictly to create the PDFs and chapter files for distribution
> >>> on the mwiki.
> >>>
> >>> The problem was with figure 4 in AOO41GS2, which would be figure 5 in
> >>> the complete book.
> >>>
> >>> If you can correct whatever you find and finish compiling the book it
> >>> would be greatly appreciated.
> >>>
> >>> Regards
> >>> Keith
> >>>
> >>>
> >>
> >>> Hi Keith
> >>>
> >>   I'll try to compile the whole text and see how it goes.
> >> Francis
> >>
> >
> > Keith,
> > I compiled all of the AOO41GS#.odt files into a file named
> AllChapters.odt.
> > I had to reinsert a figure or two in most of the chapters. After saving
> it
> > and taking a break, I scrolled through the whole document looking for
> > missing figures both among the numbered figures in frames and the in-line
> > images that show individual toolbar icons. That was very tedious, so I'm
> > not highly confident I didn't miss anything. However, I didn't see any
> > missing figures. There is a comment on page 251 that needs to be
> resolved.
> > I'm not sure what you would like for the next step. I could just push the
> > AllChapters file (with a different name?) to the top level folder of the
> > repository, or I can make it available separately.
> > Regards,
> > Francis
> >
> Francis;
>
> For now, since there are questions to be resolved, push it to the Review
> folder as AOO41GS.odt.
> Again thank you for helping to get this straightened out.
>
> Regards
> Keith
>
>
>
> -
> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: doc-h...@openoffice.apache.org
>
>
Keith,
I just pushed AOO41GS.odt to the Review folder.
Regards,
Francis

Re: Help need with compiling the Getting Started Book

[F Campos Costero]

On Mon, May 22, 2023 at 8:54 AM F Campos Costero 
wrote:

>
>
> On Sun, May 21, 2023 at 12:07 PM Keith N. McKenna <
> keith.mcke...@comcast.net> wrote:
>
>> F Campos Costero wrote:
>> > I do see problems with the figures when I use the menu Insert -> File
>> on a
>> > blank document to insert AOO41GS2.odt. Instead of a problem with one
>> > figure, I saw problems with figures 2,4,11,12, and 17. The document
>> showed
>> > a placedholder rather than the actual figure. I could delete the
>> > placeholder and copy and paste the figures from the chapter file in
>> most of
>> > the cases. For figures 12 and 17, I had to delete the frame intended to
>> > hold the figure, delete the placeholder (which was somehow not in the
>> > frame), insert a new frame, and then copy over the figure from the
>> chapter
>> > file.
>> > If you turn on View -> Nonprinting Characters, you can see that figures
>> 12
>> > and 17 are unusual. The figure caption is preceded by several empty
>> > paragraphs. I bet I did something wrong when I inserted those figures
>> long
>> > ago.
>> > I inserted AOO41GS3.odt without any problems.
>> >
>> > Regards,
>> > Francis
>> >
>> > On Wed, May 17, 2023 at 11:21 AM F Campos Costero <
>> fjcc.apa...@gmail.com>
>> > wrote:
>> >
>>
>> Hi Francis;
>>
>> Thank you for looking into this. The files to be used are all at the top
>> level. The ones in ForWiki, already have all the front matter in them
>> and are strictly to create the PDFs and chapter files for distribution
>> on the mwiki.
>>
>> The problem was with figure 4 in AOO41GS2, which would be figure 5 in
>> the complete book.
>>
>> If you can correct whatever you find and finish compiling the book it
>> would be greatly appreciated.
>>
>> Regards
>> Keith
>>
>>
>
>> Hi Keith
>>
>  I'll try to compile the whole text and see how it goes.
> Francis
>

Keith,
I compiled all of the AOO41GS#.odt files into a file named AllChapters.odt.
I had to reinsert a figure or two in most of the chapters. After saving it
and taking a break, I scrolled through the whole document looking for
missing figures both among the numbered figures in frames and the in-line
images that show individual toolbar icons. That was very tedious, so I'm
not highly confident I didn't miss anything. However, I didn't see any
missing figures. There is a comment on page 251 that needs to be resolved.
I'm not sure what you would like for the next step. I could just push the
AllChapters file (with a different name?) to the top level folder of the
repository, or I can make it available separately.
Regards,
Francis

Re: Help need with compiling the Getting Started Book

[F Campos Costero]

On Sun, May 21, 2023 at 12:07 PM Keith N. McKenna 
wrote:

> F Campos Costero wrote:
> > I do see problems with the figures when I use the menu Insert -> File on
> a
> > blank document to insert AOO41GS2.odt. Instead of a problem with one
> > figure, I saw problems with figures 2,4,11,12, and 17. The document
> showed
> > a placedholder rather than the actual figure. I could delete the
> > placeholder and copy and paste the figures from the chapter file in most
> of
> > the cases. For figures 12 and 17, I had to delete the frame intended to
> > hold the figure, delete the placeholder (which was somehow not in the
> > frame), insert a new frame, and then copy over the figure from the
> chapter
> > file.
> > If you turn on View -> Nonprinting Characters, you can see that figures
> 12
> > and 17 are unusual. The figure caption is preceded by several empty
> > paragraphs. I bet I did something wrong when I inserted those figures
> long
> > ago.
> > I inserted AOO41GS3.odt without any problems.
> >
> > Regards,
> > Francis
> >
> > On Wed, May 17, 2023 at 11:21 AM F Campos Costero  >
> > wrote:
> >
>
> Hi Francis;
>
> Thank you for looking into this. The files to be used are all at the top
> level. The ones in ForWiki, already have all the front matter in them
> and are strictly to create the PDFs and chapter files for distribution
> on the mwiki.
>
> The problem was with figure 4 in AOO41GS2, which would be figure 5 in
> the complete book.
>
> If you can correct whatever you find and finish compiling the book it
> would be greatly appreciated.
>
> Regards
> Keith
>
>

> Hi Keith
>
 I'll try to compile the whole text and see how it goes.
Francis

Re: Help need with compiling the Getting Started Book

[F Campos Costero]

I do see problems with the figures when I use the menu Insert -> File on a
blank document to insert AOO41GS2.odt. Instead of a problem with one
figure, I saw problems with figures 2,4,11,12, and 17. The document showed
a placedholder rather than the actual figure. I could delete the
placeholder and copy and paste the figures from the chapter file in most of
the cases. For figures 12 and 17, I had to delete the frame intended to
hold the figure, delete the placeholder (which was somehow not in the
frame), insert a new frame, and then copy over the figure from the chapter
file.
If you turn on View -> Nonprinting Characters, you can see that figures 12
and 17 are unusual. The figure caption is preceded by several empty
paragraphs. I bet I did something wrong when I inserted those figures long
ago.
I inserted AOO41GS3.odt without any problems.

Regards,
Francis

On Wed, May 17, 2023 at 11:21 AM F Campos Costero 
wrote:

> Hi Keith,
> I'll try to compile the complete book later today. To make sure we are
> working with the same files, please confirm that:
> 1. You are using the template file AOOdoc.ott from the Templates branch
> 2. The odt chapter files are in the Getting-Sarted-Guide branch in the
> ForWiki folder
> 3. The Aoo41GSFrontMatter.odt file is the one at the top level of the
> Getting-sarted-Guide branch.
>
> Which figure in chapter 1 is causing problems?
>
> Regards,
> Francis
>
> On Wed, May 17, 2023 at 9:47 AM Keith N. McKenna <
> keith.mcke...@comcast.net> wrote:
>
>> I am having difficulty compiling the Complete book for the Getting
>> Started Guide. All the chapters  except Chapter 1 (AOO41GS2) Compile
>> perfectly. There is one figure in chapter 1 that does not come through
>> properly. It is there in the Chapter file, but not the the complete
>> book. If one of you could try to compile it and see if there is still a
>> problem it would be greatly appreciated.
>>
>> The way I have been doing it is to create a blank writer file from the
>> AOO Template and then insert the chapters along with any manual breaks
>> as needed, then at the top insert Aoo41GSFrontMatter.odt which contains
>> the Tittle Page, Copyright Page and a blank TOC.
>>
>> Thank a lot for the help
>>
>> Regards
>> Keith
>>
>>
>> -
>> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: doc-h...@openoffice.apache.org
>>
>>

Re: Help need with compiling the Getting Started Book

[F Campos Costero]

Hi Keith,
I'll try to compile the complete book later today. To make sure we are
working with the same files, please confirm that:
1. You are using the template file AOOdoc.ott from the Templates branch
2. The odt chapter files are in the Getting-Sarted-Guide branch in the
ForWiki folder
3. The Aoo41GSFrontMatter.odt file is the one at the top level of the
Getting-sarted-Guide branch.

Which figure in chapter 1 is causing problems?

Regards,
Francis

On Wed, May 17, 2023 at 9:47 AM Keith N. McKenna 
wrote:

> I am having difficulty compiling the Complete book for the Getting
> Started Guide. All the chapters  except Chapter 1 (AOO41GS2) Compile
> perfectly. There is one figure in chapter 1 that does not come through
> properly. It is there in the Chapter file, but not the the complete
> book. If one of you could try to compile it and see if there is still a
> problem it would be greatly appreciated.
>
> The way I have been doing it is to create a blank writer file from the
> AOO Template and then insert the chapters along with any manual breaks
> as needed, then at the top insert Aoo41GSFrontMatter.odt which contains
> the Tittle Page, Copyright Page and a blank TOC.
>
> Thank a lot for the help
>
> Regards
> Keith
>
>
> -
> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: doc-h...@openoffice.apache.org
>
>

Re: Working with Open Office

[F Campos Costero]

Hello Michele,
Thanks for your interest in the documentation team! There is plenty of work
to be done. We have been working on updating the User Guides from the 3.X
version to the 4.1 version. There are six guides and only one, Getting
Started, has been released in a 4.1 version. Each guide has 300 - 400
pages.  Three of us, me, Keith N. McKenna and Dick Groskamp, have been
active over the last couple of years.  We use a Git repository to store and
track the versions and we edit them with Writer.

A few questions:
Are you interested in updating the user guides or were you thinking of some
other kind of contribution? We are happy to get any kind of help.
Have you subscribed to the doc mailing list? If not, the instructions for
subscribing are here: https://www.apache.org/foundation/mailinglists.html
Have you worked with Git? We use it at a very basic level.

I look forward to hearing how you would like to contribute to the
documentation team.
Best regards,
Francis Campos


On Wed, May 10, 2023 at 12:02 AM Michele Petrovsky <
petrovskymich...@gmail.com> wrote:

> Hope this finds you all well.
>
> Peter Kovacs suggested I get in touch with you, as a first step in
> volunteering with Open Office.
>
> I'm a late bloomer as a techie - bachelor's in history.  Took me another
> few years, but eventually got a Master's in Information Science from the
> University of Pittsburgh.  Which led to technical writing, which in turn
> led to teaching.
>
> All of those caused me to get in touch with Open Office.  I've been
> retired for a couple of years now, and miss the classroom and teaching
> experience a lot.  I'd be grateful for anything I can do for / with you
> folks.  As another part of introducing myself, I'm taking the liberty of
> attaching here a sample of my work.  It's a PowerPoint presentation I used
> in one of my introductory programming classes.
>
> By all means let me know if there's a chance for us to work together.  And
> in any case thanks for the opportunity.
>
> *Michele Petrovsky*
>
>
> -
> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: doc-h...@openoffice.apache.org

Re: Calc needs another review

[F Campos Costero]

On the Calc Guide, I will first accept or reject all of the changes
currently shown and push those versions back to the repository. Judging
from the first chapter, all of my and Dick's changes have not yet been
accepted. I hope I will have time after that to do a full review of each
document. Let me know if that plan isn't good.
Regards,
Francis

On Tue, May 2, 2023 at 9:08 AM Keith N. McKenna 
wrote:

> F Campos Costero wrote:
> > I'll take a look at the Calc changes.
> > Francis
> >
>
> Thanks Francis. I will finish with the Getting started changes from
> Czeslaw morning, and will get back to the Writer Guide this afternoon.
>
> Regards
> Keith
>
> > On Mon, May 1, 2023 at 1:07 PM Keith N. McKenna <
> keith.mcke...@comcast.net>
> > wrote:
> >
> >> Digro has had changes for Calc waiting review for some time could
> >> another member of the team start reviewing those so that Guide can start
> >> Moving along.
> >>
> >> I am still trying to catch up with with the Getting Started changes from
> >> Czeslaw that Francis made and re publishing them, as well as trying to
> >> work on the Writer Guide.
> >>
> >> I have also been spending a lot of time taking my Girlfriend in and out
> >> of the Veterans Administration Hospital in the Jamaica Plains section of
> >> Boston for medical issues.
> >>
> >> Thank you all in Advance
> >> Keith
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> >> For additional commands, e-mail: doc-h...@openoffice.apache.org
> >>
> >>
> >
>
>
>
> -
> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: doc-h...@openoffice.apache.org
>
>

Re: Calc needs another review

[F Campos Costero]

I'll take a look at the Calc changes.
Francis

On Mon, May 1, 2023 at 1:07 PM Keith N. McKenna 
wrote:

> Digro has had changes for Calc waiting review for some time could
> another member of the team start reviewing those so that Guide can start
> Moving along.
>
> I am still trying to catch up with with the Getting Started changes from
> Czeslaw that Francis made and re publishing them, as well as trying to
> work on the Writer Guide.
>
> I have also been spending a lot of time taking my Girlfriend in and out
> of the Veterans Administration Hospital in the Jamaica Plains section of
> Boston for medical issues.
>
> Thank you all in Advance
> Keith
>
>
> -
> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: doc-h...@openoffice.apache.org
>
>

Re: Review of first 3 chapters of Writer Guide

[F Campos Costero]

Keith,
I'm sorry to hear you were sick. I hope you are fully better.
All of my commits for the Writer Guide have already been pushed to the
repo.
On future chapters, I will inspect any tracked changes that are present
when I get the document but I will accept or reject them before I push the
new version back to the repo. I think having every change viewed by one
other person is enough and I'd like to avoid having large numbers of
changes in a document.
I'm also ready to push Czeslaw's changes to the Getting Started guide if
you are ok with me replacing the files in the Review folder. I posted a
question in Czeslaw's thread about that.
Regards,
Francis

On Wed, Feb 8, 2023 at 1:47 PM Keith N. McKenna 
wrote:

> Francis;
>
> Ideally You should go through the changes one, by one anseither accept
> them or reject them. However, there is a bug that makes that difficult
> if there are more than 4 or 5 changes. I will try to track that bug down
> and raise its priority to hopefully get it fixed.
>
> I see no reason given the known bug of accepting the changes and then
> making any new changes as necessary.
>
> Regards
> Keith
>
>
> F Campos Costero wrote:
> > I finished my review of the first three chapters of the Writer Guide.
> After
> > I pushed the commits, it occurred to me that I probably should have
> > accepted all of Keith's edits that were in place when I fetched the
> > documents. Does anyone object to a standard process of accepting all
> > previous Tracked Changes and making new commits only with new edits or
> > revisions of the previous ones? I have found that having a large number
> of
> > tracked changes makes documents unwieldy and even unstable.
> >
> > Regards,
> > Francis
> >
> > On Mon, Jan 23, 2023 at 6:09 PM F Campos Costero 
> > wrote:
> >
> >> Keith,
> >> Sorry, I got myself confused. I incorporated Czeslaw's changes into the
> >> Getting Started Guide chapters 2 and 3 and did another pass through
> those
> >> chapters. I am just starting the review of the Writer guide. My comments
> >> above about folder structure apply to the Getting Started Guide but they
> >> will apply to the Writer Guide soon.
> >>
> >> Francis
> >>
> >> On Mon, Jan 23, 2023 at 12:38 PM F Campos Costero <
> fjcc.apa...@gmail.com>
> >> wrote:
> >>
> >>> Keith,
> >>> I just assigned the reviews of chapters 2 and 3 to myself. These are
> both
> >>> done, actually, as I worked on them over the weekend. I took the
> version of
> >>> the two chapters from the ForWiki folder, edited them (Czeslaw's
> changes
> >>> plus a few minor changes of my own) and saved them in the Review
> folder.
> >>> This was all done on my local computer. The local Review folder now
> >>> contains my new versions of chapters 2 and 3 plus the previously
> existing
> >>> review versions of all the other chapters. How do you want to handle
> those
> >>> older "review" versions? Should I delete them, since they are, I
> suppose,
> >>> superseded by the files in the ForWiki folder?
> >>> There are also copies of all the chapters in the folder one level up
> from
> >>> the ForWiki and Review folders. They seem to be, at the moment,
> duplicates
> >>> of the versions in ForWiki. Do we need those? I would think that we
> need,
> >>> at most, two copies of the files, one representing what is on the wiki
> and
> >>> another that is the working copy.  We could just have a single visible
> >>> version and just be diligent about  tagging the versions that get
> posted to
> >>> the wiki, but I'm fine with whatever people are comfortable with. Three
> >>> copies, though, seems like more than is necessary.
> >>> Regards,
> >>> Francis
> >>>
> >>> On Mon, Jan 23, 2023 at 10:47 AM Keith N. McKenna <
> >>> keith.mcke...@comcast.net> wrote:
> >>>
> >>>> Francis;
> >>>>
> >>>> I had a conversation with infra today as I was not able to assign you
> >>>> either. What you have to do is go ti http://gitbox.apache.org/ and
> link
> >>>> your ASF id there. Than you should be able to assign yourself, or I
> can
> >>>> assign you. In issues only committers or those with the triage
> privilege
> >>>> can be assigned to issues.
> >>>>
> >>>> Please let me know how it works out.
> >>>>
> >>>> Regards
> >>>

Re: 4.1 Getting Started Guide Guide - remarks

[F Campos Costero]

I have made all of the edits suggested by Czeslaw. There are a couple of
cases where I had questions and those are noted in the commit messages.
Before I push my commits, I'd like to get confirmation from Keith that I am
not going to cause problems with any of his work on the Getting Started
guide. All of the revised documents are in the Review folder in my local
repository.. I did not change the documents in the top level folder or in
the ForWiki folder. However, the versions in the Review folder seemed to be
later versions than the ones in ForWiki. I would have expected ForWiki and
Review to be identical immediately after documents were posted to the wiki,
which I thought was the state we were in. Have I misunderstood the intent
of the Review and ForWiki folders?
 Regards,
Francis


On Sat, Feb 4, 2023 at 11:08 AM F Campos Costero 
wrote:

> I have implemented Czeslaw's edits as far as chapter 8. I should get
> through all of them early next week. I will then push the revised versions
> to the Review folder. The edits on chapter 7 were excellent. I had largely
> rewritten that chapter and it certainly benefited from the revisions.
>
> Regards,
> Francis
>
> On Sun, Jan 29, 2023 at 8:06 PM Czesław Wolański <
> czeslaw.wolan...@gmail.com> wrote:
>
>> Hi,
>>
>> Remarks on Chapter 7
>> .pdf file is available at the following link:
>>
>>
>> https://drive.google.com/file/d/1HPjbs4wYTOLeimnQ_hnu6-OHq056wWJO/view?usp=share_link
>>
>>
>> Regards,
>> Czesław
>>
>> Am Sa., 7. Jan. 2023 um 18:50 Uhr schrieb Czesław Wolański <
>> czeslaw.wolan...@gmail.com>:
>>
>> > Hi,
>> >
>> > Remarks on Chapter 9
>> >
>> > ZIP archive is available at the link given below.
>> >
>> >
>> >
>> https://drive.google.com/file/d/1EXS3c50bXaeuULNujkbfc5eEpgRpO6dF/view?usp=sharing
>> >
>> >
>> > Regards,
>> > Czesław
>> >
>> > вс, 1 янв. 2023 г. в 05:45, Czesław Wolański <
>> czeslaw.wolan...@gmail.com>:
>> >
>> >> Hi,
>> >>
>> >> Remarks on Chapter 5
>> >>
>> >> ZIP archive is available at the following link:
>> >>
>> >>
>> >>
>> https://drive.google.com/file/d/1zaL0muMZCYnV7f7na9_l_EycBgCS1wL4/view?usp=share_link
>> >>
>> >>
>> >> Regards,
>> >> Czesław
>> >>
>> >> Am Fr., 30. Dez. 2022 um 16:50 Uhr schrieb Czesław Wolański <
>> >> czeslaw.wolan...@gmail.com>:
>> >>
>> >>> Hi,
>> >>>
>> >>> Remarks on Chapter 4
>> >>>
>> >>> A .pdf file can be downloaded from the following link:
>> >>>
>> >>>
>> >>>
>> https://drive.google.com/file/d/1bavwXS85pY3y163vtDKaEh37hzow7FFS/view?usp=share_link
>> >>>
>> >>>
>> >>> Regards,
>> >>> Czesław
>> >>>
>> >>> Am So., 18. Dez. 2022 um 06:41 Uhr schrieb Czesław Wolański <
>> >>> czeslaw.wolan...@gmail.com>:
>> >>>
>> >>>> Hi,
>> >>>>
>> >>>> Remarks on Chapter 8 and 10
>> >>>>
>> >>>> ZIP archive is available at the link given below.
>> >>>>
>> >>>>
>> >>>>
>> https://drive.google.com/file/d/1OQlQgdIST_FgJI8s4RrRGGQi1HlbO94j/view?usp=share_link
>> >>>>
>> >>>>
>> >>>> Regards,
>> >>>> Czesław
>> >>>>
>> >>>> Am Fr., 16. Dez. 2022 um 19:10 Uhr schrieb Czesław Wolański <
>> >>>> czeslaw.wolan...@gmail.com>:
>> >>>>
>> >>>>> Hi,
>> >>>>>
>> >>>>> Remarks on Chapter 3
>> >>>>> .pdf file is available at the following link:
>> >>>>>
>> >>>>>
>> >>>>>
>> https://drive.google.com/file/d/1gfCKT_4Oafl4hAlA2C9rbiAZ-_p1RiHF/view?usp=share_link
>> >>>>>
>> >>>>>
>> >>>>> Regards,
>> >>>>> Czesław
>> >>>>>
>> >>>>> Am Do., 15. Dez. 2022 um 12:19 Uhr schrieb Czesław Wolański <
>> >>>>> czeslaw.wolan...@gmail.com>:
>> >>>>>
>> >>>>>> Hi,
>> >>>>>>
>> >>>>>> Remarks on Chapter 2 and 6.
>> >>>>>> ZIP archive can be downloaded from the following link:
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> https://drive.google.com/file/d/1C8kkHWkF0IiSbokMZzVZG5jzR1sTjyTe/view?usp=share_link
>> >>>>>>
>> >>>>>> Regards,
>> >>>>>> Czesław
>> >>>>>>
>> >>>>>> Am Mi., 14. Dez. 2022 um 22:51 Uhr schrieb Czesław Wolański <
>> >>>>>> czeslaw.wolan...@gmail.com>:
>> >>>>>>
>> >>>>>>> Hi,
>> >>>>>>>
>> >>>>>>> First of all, I would like to thank again everyone involved in the
>> >>>>>>> work on the 4.1 Getting Started Guide.
>> >>>>>>>
>> >>>>>>> I have and will have remarks on the Guide. To begin with, Chapter
>> 11:
>> >>>>>>>
>> >>>>>>> ZIP archive is available at the link given below.
>> >>>>>>>
>> >>>>>>>
>> >>>>>>>
>> https://drive.google.com/file/d/14BmyeqZC6C2wL4vy312TdOlkWpi_482j/view?usp=share_link
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> Regards,
>> >>>>>>> Czesław
>> >>>>>>>
>> >>>>>>
>>
>

Re: 4.1 Getting Started Guide Guide - remarks

[F Campos Costero]

I have implemented Czeslaw's edits as far as chapter 8. I should get
through all of them early next week. I will then push the revised versions
to the Review folder. The edits on chapter 7 were excellent. I had largely
rewritten that chapter and it certainly benefited from the revisions.

Regards,
Francis

On Sun, Jan 29, 2023 at 8:06 PM Czesław Wolański 
wrote:

> Hi,
>
> Remarks on Chapter 7
> .pdf file is available at the following link:
>
>
> https://drive.google.com/file/d/1HPjbs4wYTOLeimnQ_hnu6-OHq056wWJO/view?usp=share_link
>
>
> Regards,
> Czesław
>
> Am Sa., 7. Jan. 2023 um 18:50 Uhr schrieb Czesław Wolański <
> czeslaw.wolan...@gmail.com>:
>
> > Hi,
> >
> > Remarks on Chapter 9
> >
> > ZIP archive is available at the link given below.
> >
> >
> >
> https://drive.google.com/file/d/1EXS3c50bXaeuULNujkbfc5eEpgRpO6dF/view?usp=sharing
> >
> >
> > Regards,
> > Czesław
> >
> > вс, 1 янв. 2023 г. в 05:45, Czesław Wolański  >:
> >
> >> Hi,
> >>
> >> Remarks on Chapter 5
> >>
> >> ZIP archive is available at the following link:
> >>
> >>
> >>
> https://drive.google.com/file/d/1zaL0muMZCYnV7f7na9_l_EycBgCS1wL4/view?usp=share_link
> >>
> >>
> >> Regards,
> >> Czesław
> >>
> >> Am Fr., 30. Dez. 2022 um 16:50 Uhr schrieb Czesław Wolański <
> >> czeslaw.wolan...@gmail.com>:
> >>
> >>> Hi,
> >>>
> >>> Remarks on Chapter 4
> >>>
> >>> A .pdf file can be downloaded from the following link:
> >>>
> >>>
> >>>
> https://drive.google.com/file/d/1bavwXS85pY3y163vtDKaEh37hzow7FFS/view?usp=share_link
> >>>
> >>>
> >>> Regards,
> >>> Czesław
> >>>
> >>> Am So., 18. Dez. 2022 um 06:41 Uhr schrieb Czesław Wolański <
> >>> czeslaw.wolan...@gmail.com>:
> >>>
>  Hi,
> 
>  Remarks on Chapter 8 and 10
> 
>  ZIP archive is available at the link given below.
> 
> 
> 
> https://drive.google.com/file/d/1OQlQgdIST_FgJI8s4RrRGGQi1HlbO94j/view?usp=share_link
> 
> 
>  Regards,
>  Czesław
> 
>  Am Fr., 16. Dez. 2022 um 19:10 Uhr schrieb Czesław Wolański <
>  czeslaw.wolan...@gmail.com>:
> 
> > Hi,
> >
> > Remarks on Chapter 3
> > .pdf file is available at the following link:
> >
> >
> >
> https://drive.google.com/file/d/1gfCKT_4Oafl4hAlA2C9rbiAZ-_p1RiHF/view?usp=share_link
> >
> >
> > Regards,
> > Czesław
> >
> > Am Do., 15. Dez. 2022 um 12:19 Uhr schrieb Czesław Wolański <
> > czeslaw.wolan...@gmail.com>:
> >
> >> Hi,
> >>
> >> Remarks on Chapter 2 and 6.
> >> ZIP archive can be downloaded from the following link:
> >>
> >>
> >>
> https://drive.google.com/file/d/1C8kkHWkF0IiSbokMZzVZG5jzR1sTjyTe/view?usp=share_link
> >>
> >> Regards,
> >> Czesław
> >>
> >> Am Mi., 14. Dez. 2022 um 22:51 Uhr schrieb Czesław Wolański <
> >> czeslaw.wolan...@gmail.com>:
> >>
> >>> Hi,
> >>>
> >>> First of all, I would like to thank again everyone involved in the
> >>> work on the 4.1 Getting Started Guide.
> >>>
> >>> I have and will have remarks on the Guide. To begin with, Chapter
> 11:
> >>>
> >>> ZIP archive is available at the link given below.
> >>>
> >>>
> >>>
> https://drive.google.com/file/d/14BmyeqZC6C2wL4vy312TdOlkWpi_482j/view?usp=share_link
> >>>
> >>>
> >>> Regards,
> >>> Czesław
> >>>
> >>
>

Re: Review of first 3 chapters of Writer Guide

[F Campos Costero]

I finished my review of the first three chapters of the Writer Guide. After
I pushed the commits, it occurred to me that I probably should have
accepted all of Keith's edits that were in place when I fetched the
documents. Does anyone object to a standard process of accepting all
previous Tracked Changes and making new commits only with new edits or
revisions of the previous ones? I have found that having a large number of
tracked changes makes documents unwieldy and even unstable.

Regards,
Francis

On Mon, Jan 23, 2023 at 6:09 PM F Campos Costero 
wrote:

> Keith,
> Sorry, I got myself confused. I incorporated Czeslaw's changes into the
> Getting Started Guide chapters 2 and 3 and did another pass through those
> chapters. I am just starting the review of the Writer guide. My comments
> above about folder structure apply to the Getting Started Guide but they
> will apply to the Writer Guide soon.
>
> Francis
>
> On Mon, Jan 23, 2023 at 12:38 PM F Campos Costero 
> wrote:
>
>> Keith,
>> I just assigned the reviews of chapters 2 and 3 to myself. These are both
>> done, actually, as I worked on them over the weekend. I took the version of
>> the two chapters from the ForWiki folder, edited them (Czeslaw's changes
>> plus a few minor changes of my own) and saved them in the Review folder.
>> This was all done on my local computer. The local Review folder now
>> contains my new versions of chapters 2 and 3 plus the previously existing
>> review versions of all the other chapters. How do you want to handle those
>> older "review" versions? Should I delete them, since they are, I suppose,
>> superseded by the files in the ForWiki folder?
>> There are also copies of all the chapters in the folder one level up from
>> the ForWiki and Review folders. They seem to be, at the moment, duplicates
>> of the versions in ForWiki. Do we need those? I would think that we need,
>> at most, two copies of the files, one representing what is on the wiki and
>> another that is the working copy.  We could just have a single visible
>> version and just be diligent about  tagging the versions that get posted to
>> the wiki, but I'm fine with whatever people are comfortable with. Three
>> copies, though, seems like more than is necessary.
>> Regards,
>> Francis
>>
>> On Mon, Jan 23, 2023 at 10:47 AM Keith N. McKenna <
>> keith.mcke...@comcast.net> wrote:
>>
>>> Francis;
>>>
>>> I had a conversation with infra today as I was not able to assign you
>>> either. What you have to do is go ti http://gitbox.apache.org/ and link
>>> your ASF id there. Than you should be able to assign yourself, or I can
>>> assign you. In issues only committers or those with the triage privilege
>>> can be assigned to issues.
>>>
>>> Please let me know how it works out.
>>>
>>> Regards
>>> Keith
>>>
>>>
>>> F Campos Costero wrote:
>>> > Hi Keith,
>>> > I was going to assign myself to issue 95, the review of chapter 2, but
>>> I do
>>> > not see any way to do that. Do I need to be granted some authority or
>>> am I
>>> > not seeing something obvious? My github user id is FJCC.
>>> >
>>> > Francis
>>> >
>>> >
>>> > On Fri, Jan 13, 2023 at 1:06 PM Keith N. McKenna <
>>> keith.mcke...@comcast.net>
>>> > wrote:
>>> >
>>> >> Thanks Francis
>>> >>
>>> >> Keith
>>> >>
>>> >> F Campos Costero wrote:
>>> >>> Keith
>>> >>> I hope I can start to review the documents before the end of next
>>> week. I
>>> >>> have another thing I have to work on for a few more days. Once I'm
>>> free,
>>> >>> I'll pick an issue.
>>> >>> Francis
>>> >>>
>>> >>> On Thu, Jan 12, 2023 at 1:32 PM Keith N. McKenna <
>>> >> keith.mcke...@comcast.net>
>>> >>> wrote:
>>> >>>
>>> >>>> A second review of Chapters 1-3 of the Writer Guide are needed.
>>> Please
>>> >>>> Assign yourself to the GitHub issues and review.
>>> >>>>
>>> >>>> Francis if you cannot assign yourself, let me know which you will
>>> do and
>>> >>>> gn you.and I will assi
>>> >>>>
>>> >>>> Thanks
>>> >>>> Keith
>>> >>>>
>>> >>>>
>>> >>>>
>>> -
>>> >>>> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
>>> >>>> For additional commands, e-mail: doc-h...@openoffice.apache.org
>>> >>>>
>>> >>>>
>>> >>>
>>> >>
>>> >>
>>> >>
>>> >> -
>>> >> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
>>> >> For additional commands, e-mail: doc-h...@openoffice.apache.org
>>> >>
>>> >>
>>> >
>>>
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
>>> For additional commands, e-mail: doc-h...@openoffice.apache.org
>>>
>>>

Re: Review of first 3 chapters of Writer Guide

[F Campos Costero]

Keith,
Sorry, I got myself confused. I incorporated Czeslaw's changes into the
Getting Started Guide chapters 2 and 3 and did another pass through those
chapters. I am just starting the review of the Writer guide. My comments
above about folder structure apply to the Getting Started Guide but they
will apply to the Writer Guide soon.

Francis

On Mon, Jan 23, 2023 at 12:38 PM F Campos Costero 
wrote:

> Keith,
> I just assigned the reviews of chapters 2 and 3 to myself. These are both
> done, actually, as I worked on them over the weekend. I took the version of
> the two chapters from the ForWiki folder, edited them (Czeslaw's changes
> plus a few minor changes of my own) and saved them in the Review folder.
> This was all done on my local computer. The local Review folder now
> contains my new versions of chapters 2 and 3 plus the previously existing
> review versions of all the other chapters. How do you want to handle those
> older "review" versions? Should I delete them, since they are, I suppose,
> superseded by the files in the ForWiki folder?
> There are also copies of all the chapters in the folder one level up from
> the ForWiki and Review folders. They seem to be, at the moment, duplicates
> of the versions in ForWiki. Do we need those? I would think that we need,
> at most, two copies of the files, one representing what is on the wiki and
> another that is the working copy.  We could just have a single visible
> version and just be diligent about  tagging the versions that get posted to
> the wiki, but I'm fine with whatever people are comfortable with. Three
> copies, though, seems like more than is necessary.
> Regards,
> Francis
>
> On Mon, Jan 23, 2023 at 10:47 AM Keith N. McKenna <
> keith.mcke...@comcast.net> wrote:
>
>> Francis;
>>
>> I had a conversation with infra today as I was not able to assign you
>> either. What you have to do is go ti http://gitbox.apache.org/ and link
>> your ASF id there. Than you should be able to assign yourself, or I can
>> assign you. In issues only committers or those with the triage privilege
>> can be assigned to issues.
>>
>> Please let me know how it works out.
>>
>> Regards
>> Keith
>>
>>
>> F Campos Costero wrote:
>> > Hi Keith,
>> > I was going to assign myself to issue 95, the review of chapter 2, but
>> I do
>> > not see any way to do that. Do I need to be granted some authority or
>> am I
>> > not seeing something obvious? My github user id is FJCC.
>> >
>> > Francis
>> >
>> >
>> > On Fri, Jan 13, 2023 at 1:06 PM Keith N. McKenna <
>> keith.mcke...@comcast.net>
>> > wrote:
>> >
>> >> Thanks Francis
>> >>
>> >> Keith
>> >>
>> >> F Campos Costero wrote:
>> >>> Keith
>> >>> I hope I can start to review the documents before the end of next
>> week. I
>> >>> have another thing I have to work on for a few more days. Once I'm
>> free,
>> >>> I'll pick an issue.
>> >>> Francis
>> >>>
>> >>> On Thu, Jan 12, 2023 at 1:32 PM Keith N. McKenna <
>> >> keith.mcke...@comcast.net>
>> >>> wrote:
>> >>>
>> >>>> A second review of Chapters 1-3 of the Writer Guide are needed.
>> Please
>> >>>> Assign yourself to the GitHub issues and review.
>> >>>>
>> >>>> Francis if you cannot assign yourself, let me know which you will do
>> and
>> >>>> gn you.and I will assi
>> >>>>
>> >>>> Thanks
>> >>>> Keith
>> >>>>
>> >>>>
>> >>>> -
>> >>>> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
>> >>>> For additional commands, e-mail: doc-h...@openoffice.apache.org
>> >>>>
>> >>>>
>> >>>
>> >>
>> >>
>> >>
>> >> -
>> >> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
>> >> For additional commands, e-mail: doc-h...@openoffice.apache.org
>> >>
>> >>
>> >
>>
>>
>>
>> -
>> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: doc-h...@openoffice.apache.org
>>
>>

Re: Review of first 3 chapters of Writer Guide

[F Campos Costero]

Keith,
I just assigned the reviews of chapters 2 and 3 to myself. These are both
done, actually, as I worked on them over the weekend. I took the version of
the two chapters from the ForWiki folder, edited them (Czeslaw's changes
plus a few minor changes of my own) and saved them in the Review folder.
This was all done on my local computer. The local Review folder now
contains my new versions of chapters 2 and 3 plus the previously existing
review versions of all the other chapters. How do you want to handle those
older "review" versions? Should I delete them, since they are, I suppose,
superseded by the files in the ForWiki folder?
There are also copies of all the chapters in the folder one level up from
the ForWiki and Review folders. They seem to be, at the moment, duplicates
of the versions in ForWiki. Do we need those? I would think that we need,
at most, two copies of the files, one representing what is on the wiki and
another that is the working copy.  We could just have a single visible
version and just be diligent about  tagging the versions that get posted to
the wiki, but I'm fine with whatever people are comfortable with. Three
copies, though, seems like more than is necessary.
Regards,
Francis

On Mon, Jan 23, 2023 at 10:47 AM Keith N. McKenna 
wrote:

> Francis;
>
> I had a conversation with infra today as I was not able to assign you
> either. What you have to do is go ti http://gitbox.apache.org/ and link
> your ASF id there. Than you should be able to assign yourself, or I can
> assign you. In issues only committers or those with the triage privilege
> can be assigned to issues.
>
> Please let me know how it works out.
>
> Regards
> Keith
>
>
> F Campos Costero wrote:
> > Hi Keith,
> > I was going to assign myself to issue 95, the review of chapter 2, but I
> do
> > not see any way to do that. Do I need to be granted some authority or am
> I
> > not seeing something obvious? My github user id is FJCC.
> >
> > Francis
> >
> >
> > On Fri, Jan 13, 2023 at 1:06 PM Keith N. McKenna <
> keith.mcke...@comcast.net>
> > wrote:
> >
> >> Thanks Francis
> >>
> >> Keith
> >>
> >> F Campos Costero wrote:
> >>> Keith
> >>> I hope I can start to review the documents before the end of next
> week. I
> >>> have another thing I have to work on for a few more days. Once I'm
> free,
> >>> I'll pick an issue.
> >>> Francis
> >>>
> >>> On Thu, Jan 12, 2023 at 1:32 PM Keith N. McKenna <
> >> keith.mcke...@comcast.net>
> >>> wrote:
> >>>
> >>>> A second review of Chapters 1-3 of the Writer Guide are needed. Please
> >>>> Assign yourself to the GitHub issues and review.
> >>>>
> >>>> Francis if you cannot assign yourself, let me know which you will do
> and
> >>>> gn you.and I will assi
> >>>>
> >>>> Thanks
> >>>> Keith
> >>>>
> >>>>
> >>>> -
> >>>> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> >>>> For additional commands, e-mail: doc-h...@openoffice.apache.org
> >>>>
> >>>>
> >>>
> >>
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> >> For additional commands, e-mail: doc-h...@openoffice.apache.org
> >>
> >>
> >
>
>
>
> -
> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: doc-h...@openoffice.apache.org
>
>

Re: Review of first 3 chapters of Writer Guide

[F Campos Costero]

Hi Keith,
I was going to assign myself to issue 95, the review of chapter 2, but I do
not see any way to do that. Do I need to be granted some authority or am I
not seeing something obvious? My github user id is FJCC.

Francis


On Fri, Jan 13, 2023 at 1:06 PM Keith N. McKenna 
wrote:

> Thanks Francis
>
> Keith
>
> F Campos Costero wrote:
> > Keith
> > I hope I can start to review the documents before the end of next week. I
> > have another thing I have to work on for a few more days. Once I'm free,
> > I'll pick an issue.
> > Francis
> >
> > On Thu, Jan 12, 2023 at 1:32 PM Keith N. McKenna <
> keith.mcke...@comcast.net>
> > wrote:
> >
> >> A second review of Chapters 1-3 of the Writer Guide are needed. Please
> >> Assign yourself to the GitHub issues and review.
> >>
> >> Francis if you cannot assign yourself, let me know which you will do and
> >> gn you.and I will assi
> >>
> >> Thanks
> >> Keith
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> >> For additional commands, e-mail: doc-h...@openoffice.apache.org
> >>
> >>
> >
>
>
>
> -
> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: doc-h...@openoffice.apache.org
>
>

Re: Review of first 3 chapters of Writer Guide

[F Campos Costero]

Keith
I hope I can start to review the documents before the end of next week. I
have another thing I have to work on for a few more days. Once I'm free,
I'll pick an issue.
Francis

On Thu, Jan 12, 2023 at 1:32 PM Keith N. McKenna 
wrote:

> A second review of Chapters 1-3 of the Writer Guide are needed. Please
> Assign yourself to the GitHub issues and review.
>
> Francis if you cannot assign yourself, let me know which you will do and
> gn you.and I will assi
>
> Thanks
> Keith
>
>
> -
> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: doc-h...@openoffice.apache.org
>
>

Re: 4.1 Getting Started Guide Guide - remarks

[F Campos Costero]

Thanks for checking these chapters. I'm busy with something else right now
but I will definitely review your input and modify the documents.
regards,
Francis

On Fri, Dec 16, 2022 at 11:11 AM Czesław Wolański <
czeslaw.wolan...@gmail.com> wrote:

> Hi,
>
> Remarks on Chapter 3
> .pdf file is available at the following link:
>
>
> https://drive.google.com/file/d/1gfCKT_4Oafl4hAlA2C9rbiAZ-_p1RiHF/view?usp=share_link
>
>
> Regards,
> Czesław
>
> Am Do., 15. Dez. 2022 um 12:19 Uhr schrieb Czesław Wolański <
> czeslaw.wolan...@gmail.com>:
>
> > Hi,
> >
> > Remarks on Chapter 2 and 6.
> > ZIP archive can be downloaded from the following link:
> >
> >
> >
> https://drive.google.com/file/d/1C8kkHWkF0IiSbokMZzVZG5jzR1sTjyTe/view?usp=share_link
> >
> > Regards,
> > Czesław
> >
> > Am Mi., 14. Dez. 2022 um 22:51 Uhr schrieb Czesław Wolański <
> > czeslaw.wolan...@gmail.com>:
> >
> >> Hi,
> >>
> >> First of all, I would like to thank again everyone involved in the work
> >> on the 4.1 Getting Started Guide.
> >>
> >> I have and will have remarks on the Guide. To begin with, Chapter 11:
> >>
> >> ZIP archive is available at the link given below.
> >>
> >>
> >>
> https://drive.google.com/file/d/14BmyeqZC6C2wL4vy312TdOlkWpi_482j/view?usp=share_link
> >>
> >>
> >> Regards,
> >> Czesław
> >>
> >
>

Re: Seeking Opinions on Renaming the OOO3 ODF Files

[F Campos Costero]

On Sun, Aug 21, 2022 at 12:10 PM Keith N. McKenna 
wrote:

> Jean Weber wrote:
> > I agree. Much easier to follow.
> >
> > BTW, the OOo3 naming convention was for a purpose that is no longer
> > relevant: something intended to be automated but never implemented  JHW
> >
> > On Sun, 21 Aug 2022 at 07:40 Keith N. McKenna  >
> > wrote:
> >
> Thanks Jean always wondered what that naming convention was for.
>
> Regards
> Keith
>
> >> I am thinking that it might be a good idea to rename the OOo3 ODF files.
> >> The are all in a format nnnAAvv-ChapterName, IE
> 0201WG33-IntroducingWriter.
> >>
> >> As we started off with AOO41GSn for the chapters, I was thinking
> >> following on with that naming sceme for the rest of the quides.
> >>
> >> Please let me know if you agree with this or not.
> >>
> >> Regards
> >> Keith
> >>
> >>
> >
>
>

> The proposed new naming scheme is certainly better than the old one.
>
Regards,
Francis

>
> -
> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: doc-h...@openoffice.apache.org
>
>

Re: Need help with correcting these errors

[F Campos Costero]

 Dick & Keith,

I was about to post my version of the repaired figures for AOO41GS7 and I
saw Dick's version. His looks better than mine so I will not muddy the
waters with mine. My method was to copy the images to a Draw document,
delete the images and frames in the Writer document, and reinsert the
content.
Dick - Do you remember which figures were embedded as shapes? I am worried
that I have been doing something wrong in my editing.

Regards,
Francis

On Thu, Jul 7, 2022 at 11:10 AM Dick Groskamp  wrote:

> OK, that went wrong. Should have been this:
>
> On 2022/07/07 16:45:53 Dick Groskamp wrote:
>
> Keith / Francis,
>
> I've been working on the list with errors as well.
>
> I've gone through all the chapters and fixed what I could fix.
>
> After that I tried to built an error-free .odm 
>
> That was no succes because I encounterd some unexpected behavior/errors
> again.
>
> It seemed to me that one of the problem was lying in the pictures. So I
> numbered them all, as well as the frames they were in ( if any).
>
>  I then noticed that some pictures were embedded as Shapes (no Pictures).
> Found some shapes that were hidden behind the picture.
>
> Changed the Shapes to pictures by Grouping them with the accompanying
> Picture and exporting them as .png from Draw. Then re-inserted as  picture
> in the OOoFigure style.
>
> That seemed to clear some things.
>
> I've sent you my file AOO41GS7_digro_20220707.odt with the problematic
> pictures, you are talking about, fixed (I think)
>
> Please have a look, I think I'm still getting closer but not there yet 
>
> Greetings
>
> DiGro
> ___
> Apache OpenOffice 4.1.12 (Dutch) and scanned with Ziggo Safe Online
> (F-Secure)
>
> -
> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: doc-h...@openoffice.apache.org
>
>

Re: Need help with correcting these errors

[F Campos Costero]

Keith,
I will take a look at this tomorrow.
Francis

On Wed, Jul 6, 2022 at 9:51 AM Keith N. McKenna 
wrote:

> I am trying to resolve this list of errors below, especially the 4th one
> listed as on page 154 of the PDF in the ForWiki folder. It does appear
> to be due the the frame of the Figure above it being to large.
> Everything I have tried to reduce the space has only proved to move one
> or both figures out of sequence.
> The problem is in AOO41GS7.odt, which is Chapter 6 on Draw.
> Any help that can be provided would be gretly appreciated.
>
> Regards
> Keith
>
> Jean Weber wrote:
> > Looking more closely at the compiled book, I found a lot of formatting
> > and other errors. I started recording them here, but I've given up.
> > These will give you the general idea of the errors I found. Some (such
> > as incorrect x-refs) are more important than others. --Jean
> >
> > Formatting:
> > Page 3, near the top, "What You See May Be Different" should be a
> Heading 1.
> > Page 63, There appears to be an extra table row below the Tip, causing
> > an extra border to appear.
> > Page 124, There is a blank table row at the top of the page.
> > Page 154, Figure 136 falls into the bottom footer/margin, probably
> > caused by an extra-large space above the heading "Rulers". This space
> > appears to be due to the frame enclosing Figure 134.
> > Page 178, blank page, should be removed.
> > Page 181, Extra blank paragraph at top of page, pushing the heading
> > down. Remove blank paragraph.
> > Page 186: step 1), "Error: Reference source not found"
> > Page 187, page break leaving large space at bottom for no apparent
> reason.
> > Page 188, Figure 164 is too far off to the right, probably not
> > anchored correctly.
> > Page 210, Figure 187 is escaping off the top of the page. Probably not
> > anchored correctly.
> > Page 220, Too much space above heading "Creating Reports"
> >
> > Incorrect x-refs: (I have no idea how these got all goofed up). There
> > probably are more.
> > Page 122, x-ref to Figure 124 should be to Figure 107.
> > Page 137, x-ref to Figure 121 should be to Figure 123. X-ref to Figure
> > 123 (near bottom of page) should be to Figure 124.
> > Page 138, x-ref to Figure 121 should be to Figure 123.
> > Page 141, x-ref to Figure 117 should be to Figure 126.
> > Page 146, x-ref to Figure 111 should be to Figure 129. X-ref to Figure
> > 110 (near bottom of page) should be to Figure 128.
> > Page 147, x-ref to Figure 109 (near bottom of page) should be to Figure
> 131.
> > Page 149, x-ref to Figure 108 should be to Figure 132.
> > Page 154, x-ref to Figure 151 should be to Figure 135.
> > Page 165, x-ref to Figure 148 should be to Figure 151. x-ref to Figure
> > 147 should be to Figure 152.
> > Page 169, x-ref to Figure 146 should be to Figure 153. x-ref to Figure
> > 145 should be to Figure 154.
> > Page 170, x-ref to Figure 139 should be to Figure 154. x-ref to Figure
> > 143 should be to Figure 155.
> > Page 173, x-ref to Figure 140 should be to Figure 156. x-ref to Figure
> > 138 should be to Figure 157.
> >
> > In addition, some headings are in the wrong font and/or font size.
> > There may be more.
> > Page 104: "Formatting Numbers"
> > Page. 135: "Adding Pictures or Objects to a Slide"
> > Page 194, "Entering Data With the New Form"
> > Page 195: "Modify the Form", "Using the Wizard...", and "Making the Form"
> > Page 200, "Laying out a Form..." and "Making the Form"
> > Page 203, "Navigation Bar" and "Adding a List Box"
> > Page 205, "Changing the Tab Order"
> > Page 216, "Make a Query With..."
> > Page 217, "Query with Two..."
> > Page 218, "Query that Summarizes..." and "Query Summarizing..."
> >
>
>
>
> -
> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: doc-h...@openoffice.apache.org
>
>

Re: Formatting Errors in PDF of Getting Started Guide

[F Campos Costero]

On Tue, Jun 14, 2022 at 5:32 AM Dick Groskamp
 wrote:

> Op 13-6-2022 om 20:57 schreef Keith N. McKenna:
> > Dick, Francis and Jean.
> > See comments in line
> > Keith N. McKenna wrote:
> >> Dick Groskamp wrote:
> >>> Op 12-6-2022 om 22:38 schreef F Campos Costero:
> >>>> I agree with Dick's plan.  Thanks for volunteering to start the
> >>>> revisions.
> >>>> I will not be able to help with that during this coming week but I
> >>>> might be
> >>>> able to the following week.
> >>>> I looked briefly at the text near Fig. 15 where Jean noted an
> >>>> error. It
> >>>> seems the paragraph styles are used correctly in that list but the
> >>>> previous
> >>>> list slightly earlier in the document ends with the style OOo List
> >>>> 1 Cont
> >>>> instead of  OOo List 1 End. Maybe that is enough to cause the problem?
> >>>> Francis
> >>>>
> >>>>
> >>>> On Sun, Jun 12, 2022 at 8:37 AM Dick Groskamp 
> >>>> wrote:
> >>>>
> >>>>> OK, to cut things short:
> >>>>> I will go over the chapters in the GitHub ForWiki folder, trying to
> >>>>> eliminate the errors I find.
> >>>>> After checking all the chapters I will assemble a PDF to see what
> >>>>> happens
> >>>>> if I make an ODM from the fixed chapters.
> >>>>>
> >>>>> Meanwhile I would suggest to withdraw the published PDF from the
> >>>>> mwiki
> >>>>>
> >>>>> On 2022/06/12 00:16:41 Jean Weber wrote:
> >>>>>> On Sun, Jun 12, 2022 at 1:56 AM Keith N. McKenna
> >>>>>>  wrote:
> >>>>>>> Jean Weber wrote:
> >>>>>>>> The PDF of the Getting Started Guide has many serious formatting
> >>>>>>>> errors which I do not see in the chapter ODTs. [...]
> >>>>>>>>
> >>>>>>>> Jean
> >>>>>>>>
> >>>>>>> Jean;
> >>>>>>>
> >>>>>>> [...] What sort of formatting errors are you seeing?
> >>>>>> Here is a sample of some things I found. There are many, many more.
> >>>>>> PLEASE NOTE that most of these problems are in the full book, but
> >>>>>> NOT
> >>>>>> in the chapter files.
> >>>>>>
> >>>>>> There are many inconsistent uses of numbered and/or bulletted lists
> >>>>>> throughout the book, probably due to incorrect/inconsistent style
> >>>>>> use.
> >>>>>> I am not going to itemize all of them, but here are some examples
> >>>>>> from
> >>>>>> Chapter 1.
> >>>>>> Page 19, at the top is a paragraph numbered 1), but the paragraph
> >>>>>> just
> >>>>>> before Figure 15 on page 18 should be 1) and this paragraph 2).
> >>>>>> Further down, there is another paragraph numbered 1), as it
> >>>>>> should be,
> >>>>>> but the next paragraph does not have a number, even though it is
> >>>>>> part
> >>>>>> of the same procedure; it should be 2).
> >>>>>> Further down, under Saving a Document Automatically, the two final
> >>>>>> paragraphs are a procedure and should be numbered 1) and 2).
> >>>>>> Page 20, the use (or not) of bullet points is inconsistent, and the
> >>>>>> final paragraph is centered but should not be.
> >>>>>>
> >>>>>> A few random examples from other chapters, after which I gave up
> >>>>>> looking.
> >>>>>> Page 72 (in Chapter 3), under Adding a Movie or Sound, there is an
> >>>>>> un-numbered procedure. Further down is an item in a different
> >>>>>> procedure numbered 3), but the other items in that procedure have no
> >>>>>> numbers.
> >>>>>> Under Using Mail Merge, several items should have bullet points.
> >>>>>> Page 81 (in Chapter 4), there is an item numbered 4), but the other
> >>>>>> items in the procedure have no numbers.
> >>>>>> Page 115, list begins with 4) but the actual first list item is 

Re: Formatting Errors in PDF of Getting Started Guide

[F Campos Costero]

I agree with Dick's plan.  Thanks for volunteering to start the revisions.
I will not be able to help with that during this coming week but I might be
able to the following week.
I looked briefly at the text near Fig. 15 where Jean noted an error. It
seems the paragraph styles are used correctly in that list but the previous
list slightly earlier in the document ends with the style OOo List 1 Cont
instead of  OOo List 1 End. Maybe that is enough to cause the problem?
Francis


On Sun, Jun 12, 2022 at 8:37 AM Dick Groskamp  wrote:

> OK, to cut things short:
> I will go over the chapters in the GitHub ForWiki folder, trying to
> eliminate the errors I find.
> After checking all the chapters I will assemble a PDF to see what happens
> if I make an ODM from the fixed chapters.
>
> Meanwhile I would suggest to withdraw the published PDF from the mwiki
>
> On 2022/06/12 00:16:41 Jean Weber wrote:
> > On Sun, Jun 12, 2022 at 1:56 AM Keith N. McKenna
> >  wrote:
> > >
> > > Jean Weber wrote:
> > > > The PDF of the Getting Started Guide has many serious formatting
> > > > errors which I do not see in the chapter ODTs. [...]
> > > >
> > > > Jean
> > > >
> > >
> > > Jean;
> > >
> > > [...] What sort of formatting errors are you seeing?
> >
> > Here is a sample of some things I found. There are many, many more.
> > PLEASE NOTE that most of these problems are in the full book, but NOT
> > in the chapter files.
> >
> > There are many inconsistent uses of numbered and/or bulletted lists
> > throughout the book, probably due to incorrect/inconsistent style use.
> > I am not going to itemize all of them, but here are some examples from
> > Chapter 1.
> > Page 19, at the top is a paragraph numbered 1), but the paragraph just
> > before Figure 15 on page 18 should be 1) and this paragraph 2).
> > Further down, there is another paragraph numbered 1), as it should be,
> > but the next paragraph does not have a number, even though it is part
> > of the same procedure; it should be 2).
> > Further down, under Saving a Document Automatically, the two final
> > paragraphs are a procedure and should be numbered 1) and 2).
> > Page 20, the use (or not) of bullet points is inconsistent, and the
> > final paragraph is centered but should not be.
> >
> > A few random examples from other chapters, after which I gave up looking.
> > Page 72 (in Chapter 3), under Adding a Movie or Sound, there is an
> > un-numbered procedure. Further down is an item in a different
> > procedure numbered 3), but the other items in that procedure have no
> > numbers.
> > Under Using Mail Merge, several items should have bullet points.
> > Page 81 (in Chapter 4), there is an item numbered 4), but the other
> > items in the procedure have no numbers.
> > Page 115, list begins with 4) but the actual first list item is not
> numbered.
> >
> > Some lists use numbers followed by a closing parenthesis; some use
> > numbers followed by a period (full stop). Again, inconsistent style
> > use, though trivial compared to the random use of numbering at all.
> >
> > Other formatting errors are in the chapter files as well as the full
> > book. Examples (there are many others):
> > Page 8, the Note is formatted differently from Notes, Tips, Cautions
> > in other chapters.
> > Page 20, the final paragraph is incorrectly tagged as OOFigure, so it
> > is centered but should not be.
> >
> > -
> > To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> > For additional commands, e-mail: doc-h...@openoffice.apache.org
> >
> >
>
> -
> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: doc-h...@openoffice.apache.org
>
>

Re: Thoughts for moving forward

[F Campos Costero]

On Tue, Jun 7, 2022 at 5:22 PM Keith N. McKenna 
wrote:

> Dennis Hamilton wrote:
> > Here's my recommendation.
> >
> >   1.  Do not wait for 4.2.  Use the available energy  and volunteer
> power to advance the Guides for 4.1.
> >
> >   2. Do not ever tie yourself to a speculative schedule not under your
> control.  Not ever.
> >
> > 3. When 4.2 ships or is ready for/in beta, ship a supplement.  There are
> not supposed to be breaking changes.  Probably will though.  Just make a
> quick supplement that can be used in the interim before new 4.2 documents
> are available.  The supplement will also earn feedback for things that
> people notice that are not covered or need to be covered better, and that
> will lead to supplement updates and also improved 4.2 documents.
> >
> > Regards,
> >
> >   - Dennis
> >
> Thanks for your recommendation Dennis. It was an approach I hadn't
> thought of. I am hoping that I will from the other members of the team
> as well so that we can come to consensus on the path.
>
> Regards
> Keith
>
> -
> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: doc-h...@openoffice.apache.org


I agree with Dennis that we should not wait for 4.2. I doubt that the
changes between 4.1.x and 4.2 will cause anything like the number of
revisions needed to update the existing guides to match the current release
and the schedule for 4.2 cannot even be guessed. Let's just plow ahead.
Regards,
Francis

Re: Confirmation of Internet options on 4.1.x

[F Campos Costero]

On a Linux installation of OpenOffice I do see an E-mail option under Tools
-> Options -> Internet that I do not see on Windows. That matches my
understanding of the Choosing Internet Options section of Chapter 12 of the
Getting Started Guide.
Regards,
Francis


On Thu, May 5, 2022 at 2:12 PM Keith N. McKenna 
wrote:

> There is a note from Jean in Chapter 12 of the 4.1 Getting Started guide
> (AOO41GS12.odt) to verify the Internet options at Tools > Internet for
> Linux Systems. Would someone who uses AOO on Linux please check those
> settings so that I can the final review of that chapter for publication,
> as well as the entire book.
>
> Regards
> Keith
>
>
>
>
> -
> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: doc-h...@openoffice.apache.org
>
>

Re: Back at editing the Getting Started Guide

[F Campos Costero]

I confirmed that my forked repository at
https://github.com/FJCC/openoffice-docs is up to date with my local files
for the Writer Guide and the Calc Guide. That work was a first pass through
all of the chapters of each guide, applying the AOOdoc template, updating
the material and fixing typos. There are a few open questions that are
documented in comments within the guides or in the commits.
These guides are not ready for publication but I think they are ready for a
review by others. I would be happy to fix any systematic defects in
formatting or style

Francis

On Mon, Feb 14, 2022 at 8:17 PM Keith N. McKenna 
wrote:

> In article
>  gmail.com>, fjcc.apa...@gmail.com says...
> >
> > If I remember correctly, I completed first pass revisions of the Writer
> and
> > Calc guides. They have their own branches in my Git repo. I do not have
> > time this evening to remind myself of the exact status of those documents
> > but I will do that tomorrow. My computer's OS got corrupted since I did
> > that work and I will have to install software and do a little file
> > archeology.
> > Francis
> >
>
> Thanks Francis, I will look forwardfrom hearing from you
> so we can get back to work on those. Meanwhile I will
> continue with final edits to have the Getting Started
> Guide published.
>
> Regards,
> Keith
>
> > On Mon, Feb 14, 2022 at 12:44 PM Keith N. McKenna <
> keith.mcke...@comcast.net>
> > wrote:
> >
> > > Hello all;
> > >
> > > I had been away pursuing the call to relitious life as a
> > > Benedictine monk and discovered that the it was not where
> > > I had been called. As a resulyt I am back and readying the
> > > Getting Started Guide for final publishing.
> > >
> > > Has any work been done on the other guides? If so,let me
> > > know and I will start looking at those as well.
> > >
> > > Regards
> > > Keith
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> > > For additional commands, e-mail: doc-h...@openoffice.apache.org
> > >
> > >
>
>
>
>
> -
> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: doc-h...@openoffice.apache.org
>
>

Re: Back at editing the Getting Started Guide

[F Campos Costero]

If I remember correctly, I completed first pass revisions of the Writer and
Calc guides. They have their own branches in my Git repo. I do not have
time this evening to remind myself of the exact status of those documents
but I will do that tomorrow. My computer's OS got corrupted since I did
that work and I will have to install software and do a little file
archeology.
Francis

On Mon, Feb 14, 2022 at 12:44 PM Keith N. McKenna 
wrote:

> Hello all;
>
> I had been away pursuing the call to relitious life as a
> Benedictine monk and discovered that the it was not where
> I had been called. As a resulyt I am back and readying the
> Getting Started Guide for final publishing.
>
> Has any work been done on the other guides? If so,let me
> know and I will start looking at those as well.
>
> Regards
> Keith
>
>
> -
> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: doc-h...@openoffice.apache.org
>
>

Re: Status of Getting Started Guide?

[F Campos Costero]

Hi Jean,
As far as I know, the Getting Started guide has not been published. Dick
Groskamp (DiGro) did review my initial version but the process stopped
there.
Francis

On Fri, Feb 11, 2022 at 1:48 PM Jean Weber  wrote:

> Did the Getting Started Guide ever get published? Is it available anywhere
> other than on git?
>
> Jean
>

Update to Getting Started and Calc guides

[F Campos Costero]

I just pushed changes to the Getting Started and the Calc Guides to my fork
of the docs repository.

For the Getting Started guide, I made a new chapter,
AOO41GS13-GettingStartedWithMacros.odt
,
which is an update of the similar chapter from the 3.3 version of the
guide. Jean did not have a similar chapter in her version of the 4.1 guide,
upon which all the other chapters are based. I left the original AOO41GS13,
which covers open standards, in place. I was inclined to delete that
chapter but we can renumber it if other people want to keep it.

The Calc guide is my first pass at every chapter of that guide. I applied
the AOOdoc.ott template and updated the text and figures.

Regards,
Francis

Re: Documentation volunteer - introduction

[F Campos Costero]

Hi Nadeem,
I am not sure what Keith has in mind for the review process versus
publication. Let's wait to hear from him. We are still trying to work out
how to do everything and I don't think any changes have been made to the
documents on the web site.
Since Git cannot generate a diff for these binary files, I am not sure what
the best method is to avoid conflicts between  multiple reviewers. I think
a viable workflow for the moment is to get documents from my fork. You
should be able to clone that. You would then have my last version of both
the Getting Started guide and the Writer guide. The safest path, if you
want to do some editing, might be for you to edit the Writer guide and for
Keith to edit the Getting Started guide. If you can push commits to my
fork, you could directly push your versions back up. If you cannot directly
change my fork, you could send me the revised versions and I will push
them. (Would you be willing to make a trivial change to one document from
the Writer guide, adding a space at the end, and try to push that to my
fork?) When all the editing is done, I can make a pull request for Keith to
move the docs to the Apache repo and do whatever publication process he has
in mind.

With respect to this question:
* "Also, what sort of changes/review should I be making? I*

*understand there are formatting and probably typo-related things to
workon, but is there some sort of guide to look at as reference?"*
No, there is not a guide. I have invented a process as I went along. I will
try to explain that here.

   - I apply the template AOOdoc.ott that is available in the Templates
   branch of the Apache repo. I use the template changer extension to do this.
   - I change all product references from OpenOffice.org to either
   OpenOffice or Apache OpenOffice.
   - The abbreviation OOo is changed to AOO
   - I update all text and figures to reflect current features and
   appearance. For example, images of dialogs that include the old
   OpenOffice.org name are replaced with an image of the latest dialog. I also
   added a lot of references to the Sidebar and provided images where that was
   appropriate.
   - Check that formatting is applied via styles instead of hard
   formatting, using the styles from the template whenever possible and
   minimize the number of styles used. (The template implements  a set of
   styles whose names start with OOo.) The idea is to simplify the formatting
   in the hopes of making the translation to the Wiki easier. The main changes
   were using the character style OOoMenuPath for all cases of bold text,
   eliminating the style OOoStrongEmphasis and hard formatting, and using
   OOoEmphasis instead of hardcoded italic.
   - Checking all numbered lists for proper numbering. Applying the new
   template seems to mess up numbered lists.
   - Check for multiple spaces in inappropriate places using Find & Replace
   - Search for stray areas of Liberation Sans font from the old template
   that somehow survive the template change.
   - Remove text that references archaic technology, e.g. faxes, or
   literature. I didn't do this in every case.
   - Update web page links.
   - Spell check. (Some documents were written in non-US English and I
   don't think I always changed those spellings.)

The hardest part is updating features. You just have to know the software.
I am not an OpenOffice guru but I relied on 10+ years of helping on the
forum. There are also instances of factual errors and catching those is
also tough. I really hope someone else can update the Impress and Draw
guides!

Francis




On Thu, Jun 17, 2021 at 12:57 AM Nadeem Patel  wrote:

> Hi Francis,
>
> I see there are review and published, so I now I understand which have been
> reviewed and published already and which need to be reviewed. While this is
> something I might need to actually be concerned about, I am curious to know
> how the files receive a published or review on GitHub
> (ex. Published/AOO41GS1.odt → Getting-Started-Guide/AOO41GS1.odt
> or Review/AOO41GS12.odt → Getting-Started-Guide/AOO41GS12.odt). I'm asking
> because I would like to get a better idea of the repo and how things change
> there and how it appears on the actual website. My other questions are a
> bit more straightforward. Should I download the file that is listed as
> "Review..." and make changes or is there a different place I should be
> getting the files? Also, what sort of changes/review should I be making? I
> understand there are formatting and probably typo-related things to work
> on, but is there some sort of guide to look at as reference? I know you
> said we can just pick up something and get started, but I also don't want
> to go about things incorrectly, so I thought I should ask. Thanks for your
> help!
>
> Best,
>
> Nadeem
>
> On Wed, Jun 16, 2021 at 11:07 PM F Campos Costero 
> wrote:
>
> > Hi

Re: Documentation volunteer - introduction

[F Campos Costero]

Hi Nadeem,
It looks like Keith has been restructuring the repo. If you click on the
link to the commit that starts with 8928b59 (there is a link on the right
just above the file names) you can see that the files were all moved into a
single folder.

In case you cannot see the link. the URL is Move all files to
Getting-Started-Guide · apache/openoffice-docs@8928b59 · GitHub
<https://github.com/apache/openoffice-docs/commit/8928b59a4295ca79d5ee49ae40f9656be54c1f05>

Please let me know if there is anything I can do to help you get started on
something. I know it is hard to know where to start. There is no one to
assign tasks, so a new person has to find something for themself or help
with one of the few ongoing efforts.. I simply got copies of the user
guides and started editing. Only a few people have edited any documentation
lately, so you are unlikely to step on any toes.
Francis

On Wed, Jun 16, 2021 at 6:29 PM Nadeem Patel  wrote:

> Hello,
>
> I just wanted to follow up and get some clarification. When I go to
>
> https://github.com/apache/openoffice-docs/tree/Getting-Sarted-Guide/Getting-Started-Guide
> ,
> I don't see a published and review folder. Am I missing something?
>
> Best,
>
> Nadeem
>
>
>
>
> On Thu, Jun 3, 2021 at 4:19 PM Keith N. McKenna  >
> wrote:
>
> > On 2021-06-02 14:05, F Campos Costero wrote:
> > Greetings Francis and Comments in line.
> >
> > > Hi Nadeem,
> > > What I have been working on for a while now is updating the user
> guides.
> > > The old guides are available at [1]. Keith has set up a Git repository
> > [2]
> > > where a branch is dedicated to each guide. I forked that repository [3]
> > and
> > > I have done initial revisions of the Getting Started guide and the
> Writer
> > > guide. I am slowly working my way through the Calc guide and I am about
> > > half done with that. As far as I know, only the first three chapters of
> > the
> > > Getting Started guide (A0041GS1.odt - A0041GS3.odt) have been reviewed
> by
> > > anyone else.  If you are willing to jump into reviewing the other
> > chapters,
> > > there is plenty to do. Each guide is a few hundred pages and each
> chapter
> > > is typically 20 - 40 pages.
> >
> > I apologize for that Francis. Some things in my personal life came up in
> > mid-May that took a lot of my time.  I am at this point back working on
> > reviewing Chapter 4 of the getting started guide.
> > Some new information on who the Copyright holder should be listed as on
> > the copyright page. It should be The Apache Software Foundation.Also
> > traditionally we follow the American English use headline style
> > capitalization. Follow American English capitalization guidelines for
> > headings. Capitalize the first letter of every word except conjunctions,
> > articles, prepositions of fewer than four letters, and the "to" in
> > infinitives.  I am doing this as I review the the chapters of the
> > Getting Started Guide.
> >
> > > The documentation process was dormant for quite a while and Keith has
> > been
> > > trying hard to revive it. We have just recently started to use Git and
> we
> > > may well have to change the process as we learn how to work with it.
> Are
> > > you familiar with Git? We only use the most basic features.
> >
> > I am making some changes know that I believe will help with the process
> > of review and merging. Instead of using review and release folders for
> > each branch I am adding Guide Folders in Main that will always hold the
> > currently published complete guide as well as the chapters.This should
> > make the review and merge process much easier.I will make the changes in
> > GitHub today.
> >
> > I am also going to create a how to contribute guide as well as some
> > style guides, that will give some guidance on Heading styles and other
> > things so that we create a consistent look and feel across the
> > documentation we create.
> >
> > Regards
> > Keith
> >
> >
> > > If you are interested in helping with the guides, I can tell you more
> > about
> > > the workflow we have been using. If that isn't the kind of thing you
> were
> > > looking for, I am sure we can find something else.
> > > I would like to give Keith a chance to participate in this
> conversation.
> > > He has more experience with the broader documentation process than I
> do.
> > >
> > > Francis
> > >
> > > [1]
> > >
> >
> https://wiki.openoffice.org/wiki/Documentation/OOo3_User_Gui

Re: Chapter missing from Getting Started

[F Campos Costero]

Hi Jean,
Wow, I am embarrassed that I forgot the origin of the Getting Started
guide. Your work on that saved me a lot of time and really helped me get
started on document revisions. I am sorry I was so forgetful.
Francis

On Mon, Jun 7, 2021 at 4:22 PM Jean Weber  wrote:

> The repo version of the guide came from a book I had updated for AOO3.4. I
> had not included the macros chapter. (Long story on the history of that
> book.) You’ll need to start from the v3.3 version of the macros chapter.
>
> Jean
>
> On Tue, 8 Jun 2021 at 05:29 F Campos Costero 
> wrote:
>
> > Keith - I just noticed that the 3.3 version of the Getting Started Guide
> > posted at [1] includes a chapter named Getting Started with Macros. That
> > chapter was not included in the Getting Started document in the Apache
> Git
> > repository. I think including that chapter would be valuable. Do you
> > remember where you got the repo version of the guide? If I add a chapter,
> > we will have to be sure I do not mess up any references to chapter
> numbers.
> > Cross references within chapters are done with fields but between
> chapters
> > they are done with plain text, e.g. "See chapter 7 for more details"
> where
> > the 7 is manually entered.
> >
> > Francis
> >
> > [1]
> >
> >
> https://wiki.openoffice.org/wiki/Documentation/OOo3_User_Guides/OOo3.3_Chapters_ODT
> >
>

Chapter missing from Getting Started

[F Campos Costero]

Keith - I just noticed that the 3.3 version of the Getting Started Guide
posted at [1] includes a chapter named Getting Started with Macros. That
chapter was not included in the Getting Started document in the Apache Git
repository. I think including that chapter would be valuable. Do you
remember where you got the repo version of the guide? If I add a chapter,
we will have to be sure I do not mess up any references to chapter numbers.
Cross references within chapters are done with fields but between chapters
they are done with plain text, e.g. "See chapter 7 for more details" where
the 7 is manually entered.

Francis

[1]
https://wiki.openoffice.org/wiki/Documentation/OOo3_User_Guides/OOo3.3_Chapters_ODT

Re: Documentation volunteer - introduction

[F Campos Costero]

Hi Nadeem,
Let's start with the Apache repo, (GitHub - apache/openoffice-docs: Apache
OpenOffice Documentation
<https://github.com/apache/openoffice-docs/tree/main>). To see the Getting
Started files, you have to switch to the Getting-Sarted-Guide (sic)
branch.  There is a button fairly near the top of the screen with a drop
down list that you can use to switch branches. It probably will say Main
when you first access the site. When you change it to Getting-Sarted-Guide,
you should see two folders: Published and Review. The documents in
Published have been moved there by Keith. The documents in Review are as
they were after I modified the originals and need to be reviewed. In the
Review folder, you can click on, say, AOO41GS4.odt. That will take you to a
new page with a Download button on the right side. Click that and you
should get the document.

My repository has the same Review folder, though not all of the branches of
the Apache repo, and you can also download from there. You just have to
switch to the desired branch, as in the Apache repo. You could also just
clone the whole repo onto your system.

The procedure for editing has been rather clumsy so far. Dick Groskamp
(user DiGro) downloaded the documents, made suggested changes while
recording them (menu Edit -> Changes -> Record in Writer) and then emailed
the document to me on my personal email, I then accepted the changes, made
any other changes, and pushed the document to my repository. There has to
be a better way to do that but Dick ran into problems pushing commits to my
repository. Let's not worry about that at the moment. If you can just
download a document, that will be a good start.

I cannot make any changes on the Apache repo because I am not a commiter on
the project. Keith has to handle everything on that repo.

As for developing new content, you can certainly do that. What gets done on
an Apache project is up to the volunteers and the only limits are the need
to keep the project compatible with the Apache license other such legal
requirements, e.g. don't violate trademarks or copyrights. Since the email
is too long already, I will just mention two possible kinds of new content
that span the range of possible documents. A few months ago, someone
suggested writing some Quick Start materials. The Getting Started guide is
about 300 pages and rather intimidating. That could probably be done
relatively quickly. If you want to go big, there is no Base guide at all.
That would probably be 300 pages and require knowing the Base application
quite well.

Francis

On Wed, Jun 2, 2021 at 3:38 PM Nadeem Patel  wrote:

> Hello Francis,
>
> I can certainly help out with this. I would also like to help develop new
> content if that is something you guys need. Feel free to bring Keith into
> this conversation if you think that's best. I have used Git for past
> projects. I would appreciate a breakdown of how to navigate around the
> GitHub repo and how to go about the workflow. I only see four files and not
> sure where and how to make edits/changes. Thanks!
>
> Best,
>
> Nadeem
>
> On Wed, Jun 2, 2021 at 1:05 PM F Campos Costero 
> wrote:
>
> > Hi Nadeem,
> > What I have been working on for a while now is updating the user guides.
> > The old guides are available at [1]. Keith has set up a Git repository
> [2]
> > where a branch is dedicated to each guide. I forked that repository [3]
> and
> > I have done initial revisions of the Getting Started guide and the Writer
> > guide. I am slowly working my way through the Calc guide and I am about
> > half done with that. As far as I know, only the first three chapters of
> the
> > Getting Started guide (A0041GS1.odt - A0041GS3.odt) have been reviewed by
> > anyone else.  If you are willing to jump into reviewing the other
> chapters,
> > there is plenty to do. Each guide is a few hundred pages and each chapter
> > is typically 20 - 40 pages.
> > The documentation process was dormant for quite a while and Keith has
> been
> > trying hard to revive it. We have just recently started to use Git and we
> > may well have to change the process as we learn how to work with it. Are
> > you familiar with Git? We only use the most basic features.
> > If you are interested in helping with the guides, I can tell you more
> about
> > the workflow we have been using. If that isn't the kind of thing you were
> > looking for, I am sure we can find something else.
> > I would like to give Keith a chance to participate in this conversation.
> > He has more experience with the broader documentation process than I do.
> >
> > Francis
> >
> > [1]
> >
> >
> https://wiki.openoffice.org/wiki/Documentation/OOo3_User_Guides/OOo3.3_Chapters_ODT
> > [2] GitHub - apache/openoffice-docs: Apache

Re: Documentation volunteer - introduction

[F Campos Costero]

Hi Nadeem,
What I have been working on for a while now is updating the user guides.
The old guides are available at [1]. Keith has set up a Git repository [2]
where a branch is dedicated to each guide. I forked that repository [3] and
I have done initial revisions of the Getting Started guide and the Writer
guide. I am slowly working my way through the Calc guide and I am about
half done with that. As far as I know, only the first three chapters of the
Getting Started guide (A0041GS1.odt - A0041GS3.odt) have been reviewed by
anyone else.  If you are willing to jump into reviewing the other chapters,
there is plenty to do. Each guide is a few hundred pages and each chapter
is typically 20 - 40 pages.
The documentation process was dormant for quite a while and Keith has been
trying hard to revive it. We have just recently started to use Git and we
may well have to change the process as we learn how to work with it. Are
you familiar with Git? We only use the most basic features.
If you are interested in helping with the guides, I can tell you more about
the workflow we have been using. If that isn't the kind of thing you were
looking for, I am sure we can find something else.
I would like to give Keith a chance to participate in this conversation.
He has more experience with the broader documentation process than I do.

Francis

[1]
https://wiki.openoffice.org/wiki/Documentation/OOo3_User_Guides/OOo3.3_Chapters_ODT
[2] GitHub - apache/openoffice-docs: Apache OpenOffice Documentation

[3] GitHub - FJCC/openoffice-docs: Apache OpenOffice Documentation


On Tue, Jun 1, 2021 at 10:50 PM Nadeem Patel  wrote:

> I would like to add that I am interested in developing new content,
> editing, proofreading, research or possibly even helping to create UML
> diagrams. Thanks!
>
> On Tue, Jun 1, 2021 at 11:37 PM Nadeem Patel 
> wrote:
>
> > Hello,
> >
> > My name is Nadeem Patel. I came across the Apache OpenOffice Community
> and
> > would love to contribute. I have been looking to build my
> > documentation/technical writing portfolio while also improving the
> > necessary skills for such writing.
> >
> > I graduated from Northwestern University, where I studied journalism and
> > computer science. Currently, I am working as a digital producer at a
> major
> > news network while working on data science projects during my free time.
> > The majority of my experiences include writing, development or both.
> > Through this volunteering opportunity, I hope to continue utilizing my
> > skills and continue to build on my experiences. Thank you for your time
> and
> > look forward to being involved!
> >
> > Best,
> >
> > Nadeem Patel
> >
>

Re: Join mailing list (volunteer)

[F Campos Costero]

Hello Nadeem,
Thank you for volunteering! To subscribe to the mailing list, you need to
send a message to  doc-subscr...@openoffice.apache.org  The procedure is
explained in the Using Mailing Lists section of
https://openoffice.apache.org/mailing-lists.html.
Once you are subscribed, I suggest you post a message briefly describing
your background and interests and we can discuss how to get you started on
something.

Regards,
Francis

On Mon, May 31, 2021 at 11:50 PM Nadeem Patel  wrote:

> Hello,
>
> I would like to join the doc mailing list.
>

Writer Guide

[F Campos Costero]

I just pushed my first revision of the Writer Guide chapters to my fork. I
used the AOOdoc.ott template. None of the chapters needed heavy revision  I
added references to the Sidebar in many places and updated many figures. I
left comments for open items, most of which are the repeated need to update
the front matter in each chapter.
Francis

Re: AOOdoc.ott

[F Campos Costero]

The Getting Started chapters GS1 - GS12 + the master document have had
AOOdoc.ott applied as the template. GS1 - GS3 include changes as suggested
by Keith or Dick. In hindsight, I should have commited GS2 and GS3
separately since they included Dick's suggested edits and had not been
previously pushed. I'm learning as I go!
Francis

On Wed, Mar 31, 2021 at 2:35 PM F Campos Costero 
wrote:

> Keith,
> I have pushed the latest version of GS1 up to my fork. Dick had edits for
> GS2 and GS3 and I have those ready to go. I believe he has already applied
> AOOdoc.ott to them and I will check that. I will also apply AOOdoc.ott to
> all of the remaining chapters of the Getting Started guide and push all of
> those up to the fork. So, after tonight my versions of GS1 - GS3 will have
> been reviewed by either you or Dick and all of the GS chapters will use the
> new template.
>
> I'm also nearly done with my first pass at revising the Writer guide. I
> hope to push that up to my fork by early next week.
>
> Francis
>
> On Wed, Mar 31, 2021 at 12:46 PM Keith N. McKenna <
> keith.mcke...@comcast.net> wrote:
>
>> On 3/30/2021 12:53 PM, F Campos Costero wrote:
>> > I understand that AOOdoc.ott is being applied to the Getting Started
>> guide
>> > chapters.
>> >
>> > Is the only difference between that template and the template I applied
>> the
>> > blue color used for text such as chapter numbers?
>> >
>> > I have been working on the Writer guide and it uses a different
>> template.
>> > The main difference I have noticed is that the OOoTableText paragraph
>> style
>> > is DejaVu Sans in the Getting Started guide and it is DejaVu Serif in
>> the
>> > Writer guide. (I used the first chapter of the Writer guide to define
>> the
>> > template.) There may be other differences. Should we settle on a single
>> > template for all of the documents?
>> >
>> > I will apply AOOdoc.ott to all of the documents in my fork once we
>> discuss
>> > whether any changes need to be made to it.
>> >
>> > Francis
>> >
>> That is the only difference between AOO41GS.ott and AOOdoc.ott. I
>> renamed it to make it more generic rather than have people think it was
>> only for that specific guide.
>>
>> We should use the AOOdoc.ott for all of the guides we inherited from
>> OOOAuthors.
>>
>> On a separate note. Where are the latest updated versions of the Getting
>> Started Guide.
>>
>> Regards
>> Keith
>>
>>

Re: AOOdoc.ott

[F Campos Costero]

Keith,
I have pushed the latest version of GS1 up to my fork. Dick had edits for
GS2 and GS3 and I have those ready to go. I believe he has already applied
AOOdoc.ott to them and I will check that. I will also apply AOOdoc.ott to
all of the remaining chapters of the Getting Started guide and push all of
those up to the fork. So, after tonight my versions of GS1 - GS3 will have
been reviewed by either you or Dick and all of the GS chapters will use the
new template.

I'm also nearly done with my first pass at revising the Writer guide. I
hope to push that up to my fork by early next week.

Francis

On Wed, Mar 31, 2021 at 12:46 PM Keith N. McKenna 
wrote:

> On 3/30/2021 12:53 PM, F Campos Costero wrote:
> > I understand that AOOdoc.ott is being applied to the Getting Started
> guide
> > chapters.
> >
> > Is the only difference between that template and the template I applied
> the
> > blue color used for text such as chapter numbers?
> >
> > I have been working on the Writer guide and it uses a different template.
> > The main difference I have noticed is that the OOoTableText paragraph
> style
> > is DejaVu Sans in the Getting Started guide and it is DejaVu Serif in the
> > Writer guide. (I used the first chapter of the Writer guide to define the
> > template.) There may be other differences. Should we settle on a single
> > template for all of the documents?
> >
> > I will apply AOOdoc.ott to all of the documents in my fork once we
> discuss
> > whether any changes need to be made to it.
> >
> > Francis
> >
> That is the only difference between AOO41GS.ott and AOOdoc.ott. I
> renamed it to make it more generic rather than have people think it was
> only for that specific guide.
>
> We should use the AOOdoc.ott for all of the guides we inherited from
> OOOAuthors.
>
> On a separate note. Where are the latest updated versions of the Getting
> Started Guide.
>
> Regards
> Keith
>
>

AOOdoc.ott

[F Campos Costero]

I understand that AOOdoc.ott is being applied to the Getting Started guide
chapters.

Is the only difference between that template and the template I applied the
blue color used for text such as chapter numbers?

I have been working on the Writer guide and it uses a different template.
The main difference I have noticed is that the OOoTableText paragraph style
is DejaVu Sans in the Getting Started guide and it is DejaVu Serif in the
Writer guide. (I used the first chapter of the Writer guide to define the
template.) There may be other differences. Should we settle on a single
template for all of the documents?

I will apply AOOdoc.ott to all of the documents in my fork once we discuss
whether any changes need to be made to it.

Francis

Re: [GitHub] [openoffice-docs] FJCC commented on pull request #30: Getting sarted guide

[F Campos Costero]

I just pushed my latest version of the Getting Started branch that includes
DiGro's edits of AOO41GS1.odt.

As we move on to other documents, don't worry about searching for double
spaces. I will do that myself. I am sure there are more important errors
to catch.
Francis.

On Wed, Mar 24, 2021 at 2:13 PM Keith N. McKenna 
wrote:

> On 3/23/2021 5:20 PM, F Campos Costero wrote:
> > Keith,
> > I think I could simply edit the GS1 file, commit it and push that up to
> my
> > fork. My main concern is with maintaining a clear workflow so we do not
> end
> > up with multiple partially edited versions of any document. If you have
> no
> > more edits for GS1, I'll do the two edits suggested by DiGro and push
> them
> > up to my fork. In the future, how should we handle getting input from
> > multiple reviewers? Since Git can't do a diff on these documents, we
> can't,
> > I assume, use the usual git tools for conflict resolution. Should each
> > reviewer download the doc from the author's fork, send the revised doc
> > (with changes recorded and comments as needed) directly to the author,
> have
> > the author integrate the changes into his/her version, possibly with
> > changes from other reviewers, and push the doc as a new commit to the
> fork?
> > I am not sure enough in my Git knowledge to call that a proposal but it
> is
> > what we are doing in this case.
> > Francis
> >
>
> Francis;
>
> My knowledge of GitHub is probably less than yours at this point. What
> you say sounds doable.I have no more edits to AOO41GS1.
>
> Regards
> Keith
> > On Tue, Mar 23, 2021 at 12:49 PM Keith N. McKenna <
> keith.mcke...@comcast.net>
> > wrote:
> >
> >> On 3/21/2021 7:14 PM, GitBox wrote:
> >>>
> >>> FJCC commented on pull request #30:
> >>> URL:
> >>
> https://github.com/apache/openoffice-docs/pull/30#issuecomment-803677439
> >>>
> >>>
> >>>DiGro - thanks for reviewing the file and catching those errors. I
> >> really appreciate you taking the time. I downloaded the file and I see
> the
> >> edits you made. I'm not sure how Keith wants to handle responding to
> edits
> >> needed in the pull request, so I will give him a chance to chime in.
> >>>I will search future versions for multiple spaces. I should have
> >> realized that was needed.
> >>>
> >>>
> >>
> >> Francis;
> >>
> >> I see no reason that just attaching it to the pull request wouldn't
> >> work. I am newbie at GitHub, so if anyone knows I reason that it
> >> wouldn't, please speak up and let us know.
> >>
> >> Regards
> >> Keith
> >>
> >>
>
>
>

Re: [GitHub] [openoffice-docs] FJCC commented on pull request #30: Getting sarted guide

[F Campos Costero]

Keith,
I think I could simply edit the GS1 file, commit it and push that up to my
fork. My main concern is with maintaining a clear workflow so we do not end
up with multiple partially edited versions of any document. If you have no
more edits for GS1, I'll do the two edits suggested by DiGro and push them
up to my fork. In the future, how should we handle getting input from
multiple reviewers? Since Git can't do a diff on these documents, we can't,
I assume, use the usual git tools for conflict resolution. Should each
reviewer download the doc from the author's fork, send the revised doc
(with changes recorded and comments as needed) directly to the author, have
the author integrate the changes into his/her version, possibly with
changes from other reviewers, and push the doc as a new commit to the fork?
I am not sure enough in my Git knowledge to call that a proposal but it is
what we are doing in this case.
Francis

On Tue, Mar 23, 2021 at 12:49 PM Keith N. McKenna 
wrote:

> On 3/21/2021 7:14 PM, GitBox wrote:
> >
> > FJCC commented on pull request #30:
> > URL:
> https://github.com/apache/openoffice-docs/pull/30#issuecomment-803677439
> >
> >
> >DiGro - thanks for reviewing the file and catching those errors. I
> really appreciate you taking the time. I downloaded the file and I see the
> edits you made. I'm not sure how Keith wants to handle responding to edits
> needed in the pull request, so I will give him a chance to chime in.
> >I will search future versions for multiple spaces. I should have
> realized that was needed.
> >
> >
>
> Francis;
>
> I see no reason that just attaching it to the pull request wouldn't
> work. I am newbie at GitHub, so if anyone knows I reason that it
> wouldn't, please speak up and let us know.
>
> Regards
> Keith
>
>

Re: Latest 4.1 Getting Started Changes

[F Campos Costero]

Keith,
I did another pull request. Is the plan to do a pull request for each doc
despite the fact that GS1 - GS12 have already been revised?
Francis

On Fri, Mar 19, 2021 at 11:02 AM Keith N. McKenna 
wrote:

> Francis;
>
> Could you please submit a PR for your latest changes for AOO411GS1.odt
>
> Thanks
> Keith
>
>

Re: [GitHub] [openoffice-docs] FJCC commented on issue #19: Update AOO41GS1

[F Campos Costero]

Keith,
When reviewing the docs in the pull request I just made, it is important
not to turn on change tracking for AOO41GS8.odt. For some reason doing that
causes the document to make many duplicates of the text frame that
holds Figure 20, at least it does on my system. I had to rescue the
document twice by editing its content.xml.

I am not happy with the spacing between some of the figures and the
subsequent text but I got tangled up trying to fix it. I will work on
finding a clean solution for that.

Francis

On Tue, Mar 9, 2021 at 11:16 PM F Campos Costero 
wrote:

> Keith,
> I will try to do one more pass at GS8 and do a pull request for everything
> tomorrow. I want to be clear that I am not claiming that any of the
> chapters are ready to be published. I made several decisions in defining
> the template that should be reviewed and quite possibly revised. I will
> include a copy of the template in the review folder. I do think it is time
> for another set of eyes to look at the documents, suggest revisions to the
> general layout and look for errors.
> Francis
>
> On Tue, Mar 9, 2021 at 5:26 PM Keith N. McKenna 
> wrote:
>
>> On 3/9/2021 1:47 PM, GitBox wrote:
>> >
>> > FJCC commented on issue #19:
>> > URL:
>> https://github.com/apache/openoffice-docs/issues/19#issuecomment-794295544
>> >
>> >
>> >I applied a template to AOO41GS1 - AOO41GS12 and I removed all of
>> the manual formatting. There are still a few open issues marked with
>> comments. AOO41GS8 needs more proofreading.
>> >
>> >
>> > 
>> > This is an automated message from the Apache Git Service.
>> > To respond to the message, please log on to GitHub and use the
>> > URL above to go to the specific comment.
>> >
>> > For queries about this service, please contact Infrastructure at:
>> > us...@infra.apache.org
>> >
>>
>> Francis;
>>
>> Can you do pull requests for the chapters that you have completed so
>> that they can be committed to the repository and and start the review
>> cycle.
>>
>> Regards
>> Keith
>>
>

Re: [GitHub] [openoffice-docs] FJCC commented on issue #19: Update AOO41GS1

[F Campos Costero]

Keith,
I will try to do one more pass at GS8 and do a pull request for everything
tomorrow. I want to be clear that I am not claiming that any of the
chapters are ready to be published. I made several decisions in defining
the template that should be reviewed and quite possibly revised. I will
include a copy of the template in the review folder. I do think it is time
for another set of eyes to look at the documents, suggest revisions to the
general layout and look for errors.
Francis

On Tue, Mar 9, 2021 at 5:26 PM Keith N. McKenna 
wrote:

> On 3/9/2021 1:47 PM, GitBox wrote:
> >
> > FJCC commented on issue #19:
> > URL:
> https://github.com/apache/openoffice-docs/issues/19#issuecomment-794295544
> >
> >
> >I applied a template to AOO41GS1 - AOO41GS12 and I removed all of the
> manual formatting. There are still a few open issues marked with comments.
> AOO41GS8 needs more proofreading.
> >
> >
> > 
> > This is an automated message from the Apache Git Service.
> > To respond to the message, please log on to GitHub and use the
> > URL above to go to the specific comment.
> >
> > For queries about this service, please contact Infrastructure at:
> > us...@infra.apache.org
> >
>
> Francis;
>
> Can you do pull requests for the chapters that you have completed so
> that they can be committed to the repository and and start the review
> cycle.
>
> Regards
> Keith
>

Re: Getting Started Guide status

[F Campos Costero]

Keith,
Thanks for tracking my contributions in the comments. Getting credit isn't
a huge deal but I do appreciate the effort. I'm definitely not a committer.
Back when the project came to ASF, it was decided not to give committer
status to forum moderators, which is certainly reasonable, and I haven't
been much of a presence on the dev list since then.
Francis

On Thu, Feb 25, 2021 at 5:05 PM Keith N. McKenna 
wrote:

> Francis, comments in line
>
> On 2/25/2021 12:20 AM, F Campos Costero wrote:
> > Keith,
> > I opened an issue for updating AOO41GS8 but  it seems I do not have the
> > status needed to assign it.. I am actually well into the revision but
> there
> > are a lot of changes, so I will have to spend more time on it.
> > Francis
> >
>
> I was afraid of that Francis. You are not a committer for OpenOffice or
> at least if you are you haven't gone through the process of linking your
> GitHub account. I could not even assign you to the ones I did for your
> other chapters. I will update the one you did with a comment so you get
> credit for the work.
>
> Regards
> Keith.
> > On Tue, Feb 23, 2021 at 1:32 PM Keith N. McKenna <
> keith.mcke...@comcast.net>
> > wrote:
> >
> >> On 2/16/2021 1:34 PM, F Campos Costero wrote:
> >>> I just pushed the first pass of revisions to most of the remaining
> >> chapters
> >>> of the Getting Started guide, The only documents I have not worked on
> yet
> >>> are AOO41GS8 (the Base chapter), AOO41GS13 (covers Open Source, Open
> >>> Standards & Open Document. I am considering dropping all or most of
> it),
> >>> and AOO41GS14, which is just the alphabetical index. The Base chapter
> >> needs
> >>> more extensive revision than any other chapter and I will start on that
> >>> next. I expect it will take me a few days to complete the first pass.
> >>>
> >>> I am unsure what the status is of Keith's work setting up issues and
> >>> discussion on Github. Should I post anything there?
> >>>
> >>> Francis
> >>>
> >> Francis;
> >>
> >> I am going to set up Issues for all but the 2 documents that you mention
> >> and start the review cycle. When you start on the other 2 Open an issue
> >> and assign it to yourself and assign it to the project board. If you
> >> have difficulties Let me know. Unfortunately this process is still a
> >> work in progress. Hopefully between all of us we can get it smoothed
> out.
> >>
> >> Regards
> >> Keith
> >>
> >>
> >>
>
>
>

Re: Finished review of AOO41GS1

[F Campos Costero]

Keith,
If we want to have one commit per chapter, I could make a second pass at
the chapters to at least change the font as you suggested and then commit
those changes one chapter at a time. I'm close to having GS8 ready, so I
can probably get everything into my fork by early next week. I'm sure I'll
also find some typos and other mistakes but those revisions should go
quickly. There are one or two open questions that will not be answered but
I always intended to close those at a later date. Let me know if you don't
like that plan.
Francis

On Thu, Feb 25, 2021 at 4:55 PM Keith N. McKenna 
wrote:

> Francis, comments inline
>
> On 2/24/2021 4:14 PM, F Campos Costero wrote:
> > Keith,
> > It looks to me like you reviewed the version of AOO41GS1 at
> > openoffice-docs/Review
> > at Getting-Sarted-Guide · apache/openoffice-docs (github.com)
> > <
> https://github.com/apache/openoffice-docs/tree/Getting-Sarted-Guide/Review
> >
> > while
> > my version is on my fork at openoffice-docs/Review at
> Getting-Sarted-Guide
> > · FJCC/openoffice-docs (github.com)
> > <
> https://github.com/FJCC/openoffice-docs/tree/Getting-Sarted-Guide/Review>.
> > Am I confused?
> Francis it is quite possible we are both confused. I saw your push and
> it looked like Digro had approved them. But maybe I was the one confused.
>
> >
> > Concerning pulls requests, my commits cover more than one chapter. The
> > first commit covers GS1 - GS4 and the second covers GS5 -GS7 and
> GS9-GS12.
> > Won't we have to review everything, or at least everything in a
> particular
> > commit, before doing a PR and merge? In hindsight, I probably should have
> > done a commit for every chapter.
> >
> > Francis
>
> For the ones you have ready you can do the 2 PR's and I will approve
> them back to review and start the review cycle over again.
>
> For the others it is probably best if you do a PR per chapter.
>
> Regards
> Keith
> >
> > On Wed, Feb 24, 2021 at 10:06 AM Keith N. McKenna <
> keith.mcke...@comcast.net>
> > wrote:
> >
> >> Francis;
> >>
> >> I finished the review of the Preface and it looks very good. I noted one
> >> change. If you agree with the change accept it, turn off Record changes
> >> and submit a PR to have it published.
> >>
> >> Regards
> >> Keith
> >>
> >>
>
>
>

Re: Getting Started Guide status

[F Campos Costero]

Keith,
I opened an issue for updating AOO41GS8 but  it seems I do not have the
status needed to assign it.. I am actually well into the revision but there
are a lot of changes, so I will have to spend more time on it.
Francis

On Tue, Feb 23, 2021 at 1:32 PM Keith N. McKenna 
wrote:

> On 2/16/2021 1:34 PM, F Campos Costero wrote:
> > I just pushed the first pass of revisions to most of the remaining
> chapters
> > of the Getting Started guide, The only documents I have not worked on yet
> > are AOO41GS8 (the Base chapter), AOO41GS13 (covers Open Source, Open
> > Standards & Open Document. I am considering dropping all or most of it),
> > and AOO41GS14, which is just the alphabetical index. The Base chapter
> needs
> > more extensive revision than any other chapter and I will start on that
> > next. I expect it will take me a few days to complete the first pass.
> >
> > I am unsure what the status is of Keith's work setting up issues and
> > discussion on Github. Should I post anything there?
> >
> > Francis
> >
> Francis;
>
> I am going to set up Issues for all but the 2 documents that you mention
> and start the review cycle. When you start on the other 2 Open an issue
> and assign it to yourself and assign it to the project board. If you
> have difficulties Let me know. Unfortunately this process is still a
> work in progress. Hopefully between all of us we can get it smoothed out.
>
> Regards
> Keith
>
>
>

Re: Finished review of AOO41GS1

[F Campos Costero]

Keith,
It looks to me like you reviewed the version of AOO41GS1 at
openoffice-docs/Review
at Getting-Sarted-Guide · apache/openoffice-docs (github.com)

while
my version is on my fork at openoffice-docs/Review at Getting-Sarted-Guide
· FJCC/openoffice-docs (github.com)
.
Am I confused?

Concerning pulls requests, my commits cover more than one chapter. The
first commit covers GS1 - GS4 and the second covers GS5 -GS7 and GS9-GS12.
Won't we have to review everything, or at least everything in a particular
commit, before doing a PR and merge? In hindsight, I probably should have
done a commit for every chapter.

Francis

On Wed, Feb 24, 2021 at 10:06 AM Keith N. McKenna 
wrote:

> Francis;
>
> I finished the review of the Preface and it looks very good. I noted one
> change. If you agree with the change accept it, turn off Record changes
> and submit a PR to have it published.
>
> Regards
> Keith
>
>

Re: [GitHub] [openoffice-docs] knmc commented on issue #15: Create branch for the Base Guide

[F Campos Costero]

I thought that since none of the documentation is being distributed with
the product released by the PMC, i.e. the AOO suite, we could use materials
with licenses that would not usually be allowed. The Guides are dual
licensed as GPL 3 (category X)  or CC-by Category B, binary only). I'm not
sure what "binary" means for documentation but distributing an odt file
does not seem to meet that criterion. Am I confused?
Francis

On Mon, Feb 22, 2021 at 10:27 AM Keith N. McKenna 
wrote:

> On 2/22/2021 6:26 AM, Dick Groskamp wrote:
> >
> >
> > On 2021/02/22 05:13:57, GitBox  wrote:
> >>
> >> knmc commented on issue #15:
> >> URL:
> https://github.com/apache/openoffice-docs/issues/15#issuecomment-783087015
> >>
> >>
> >>Could this be the same one?
> >>[](
> https://wiki.openoffice.org/w/index.php?title=QA/Database=20120801061326=500=history
> )
> >>
> >>
> >> 
> >> This is an automated message from the Apache Git Service.
> >> To respond to the message, please log on to GitHub and use the
> >> URL above to go to the specific comment.
> >>
> >> For queries about this service, please contact Infrastructure at:
> >> us...@infra.apache.org
> >>
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> >> For additional commands, e-mail: doc-h...@openoffice.apache.org
> >>
> >>
> > The file is here:
> https://wiki.openoffice.org/w/images/0/02/Base_tutorial.pdf
> > Just uploaded it a short while ago, since it was missing.
> >
> > The SQL that belongs to the file is also there:
> > https://wiki.openoffice.org/w/images/1/1d/Base_Tutorial_SQL_code.txt
> >
> > Both files mentioned on our wiki: https://wiki.openoffice.org/wiki/Base
> >
> > Greetings
> >
> Digro;
>
> I do not believe that this should be distributed from the  mwiki.It is
> Licensed under the cc-by-nc-sa 3.0 which is a category X license.
>
> The other you linked to is the wiki version of the Getting started guide
> chapter 8 which we already have.I appears that we will have to take that
> odt file as a starting point and write the rest from scratch.
>
> As always other options are both appreciated and encouraged.
>
> Regards
> Keith
>
>

Getting Started Guide status

[F Campos Costero]

I just pushed the first pass of revisions to most of the remaining chapters
of the Getting Started guide, The only documents I have not worked on yet
are AOO41GS8 (the Base chapter), AOO41GS13 (covers Open Source, Open
Standards & Open Document. I am considering dropping all or most of it),
and AOO41GS14, which is just the alphabetical index. The Base chapter needs
more extensive revision than any other chapter and I will start on that
next. I expect it will take me a few days to complete the first pass.

I am unsure what the status is of Keith's work setting up issues and
discussion on Github. Should I post anything there?

Francis

Re: GNU Linux install guide - 6 pages....

[F Campos Costero]

Well, my day yesterday did not go as planned and I did not get back to
this.
What, if anything, needs to be done with respect to Marcia's Debian Install
Guide? I looked through it and everything looks right, though I do not have
the commands all memorized, so there could possibly be an error.  It would
be good to give other people a chance to review documents before posting
them but it is simple enough to review such a short document now. We are
all developing the process and learning as we go, so we should expect some
hiccups.

Keith - do you have any comments on Marcia's email?

Marcia - are you willing to give any more feedback about how to improve
what we are doing?

I am keeping this message on the docs list, since I do not think general
members of the dev list will want to see a detailed discussion. Feel free
to correct me on that.

Francis

On Tue, Feb 9, 2021 at 9:43 PM F Campos Costero 
wrote:

>
> Sorry, I did not do Reply All.
>
> -- Forwarded message -----
> From: F Campos Costero 
> Date: Tue, Feb 9, 2021 at 9:41 PM
> Subject: Re: GNU Linux install guide - 6 pages
> To: 
>
>
> Marcia,
> I am very sorry you have had a bad experience trying to contribute to the
> docs team. I have just gotten involved myself and my views certainly do not
> represent any official or team perspective. The docs group has made very
> little progress for a long time due to many obstacles but I think there is
> finally a bit of movement with the repair of the MediaWiki extension,  the
> new repository and the decision to make odt the base format, insulating
> most volunteers from technical issues that caused a lot of uncertainty. You
> were certainly a very positive contributor  and I was very much looking
> forward to working with you on the larger documents. Please do continue on.
> I also strongly support your concerns being openly addressed and rectified
> where that is possible.
>
> I want to review the previous emails before saying more, particularly
> because it is getting late for me. I hope that tomorrow I can discuss with
> you and other interested parties how to improve the docs team.
>
> Francis
>
> On Tue, Feb 9, 2021 at 8:17 PM marcia wilbur  wrote:
>
>> Hi.
>>
>> I realize I did prematurely create a simple installation guide for GNU
>> Linux users without realizing the licensure.
>> This could be fixed.
>> However, I received an email off this list from Keith stating the guide
>> was not peer reviewed.
>>
>> I wonder, were these guides?
>> http://openoffice-uni.org/
>>
>> this was also posted online.
>>
>> One recommendation - please make the onboarding simple and
>> straightforward for those volunteering in this effort for documentation.
>>
>> I was just trying to be a positive force and influence for this project,
>> but really and am disappointed by the docs team - well, particularly and
>> the continued push to use the old docs, mix method of documentation and as
>> I heard during fosdem = the idea... this project cannot move forward as a
>> current offering - like a corporation
>>
>> I do encourage the docs team to move forward with current useful
>> documentation for the project, working with developers in an effort to
>> drive innovation.
>>
>> I hope you can move forward with these attitudes in a positive manner.
>>
>> Keith, all future communication should be made here.
>>
>> Thank you.
>>
>>
>>
>>
>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>
>>

Status of Doc checkout process

[F Campos Costero]

With the Git repository not quite set up yet (thanks Keith or all the
work!), I have held off on updating the checkout spreadsheet since I think
we will ultimately use a different method. I have just finished my first
pass at AOO41GS5 and I will move on to 6.

 It would be good to have the checkout document separate from the branch
being edited so you don't have to do a pull request of all of the edits
just to notify that you have moved on to other chapters. Could there be a
global check out document in Main?

Francis

Re: Update of 4 docs from Getting Started branch

[F Campos Costero]

Dennis,
Thanks for the advice! I did intend for people to look at the fork and I
even had the link on my clipboard. I had a little domestic crisis
this morning and my brain was not fully engaged, I guess.

 I turned on Issues and Discussion in my fork, I think. If you have a
moment to check, it would be nice to confirm that and for me to see what it
looks like on my end. We will have to have Git primer for docs volunteers
but I have to learn these things myself. Before now, I have only used the
command line to work with repositories on  systems I control, so all this
fancy GUI collaboration is new.

I have long wondered how well MS Office supports the Open Document format
since document exchange is a persistent topic on the forum. Back when ods
support first came to Excel, I learned that saving an ods file would result
in all of the formulas being silently dropped. That scarred me. I'm sure
they have improved since then.

Francis

On Wed, Feb 10, 2021 at 2:06 PM Dennis Hamilton  wrote:

> Without a pull request, I am unclear how you expect anyone to see this
> unless you mean for us to look at your fork?
>
> That is, at the FJCC/openoffice-docs Getting-Started branch?
> <https://github.com/FJCC/openoffice-docs/tree/Getting-Sarted-Guide>
>
> There I see your 4-document updates earlier today in the Review folder
> there.
>
> Francis, if you enable Issues and Discussions on your fork, others can
> comment on the changes you have there before you ask for them to be pulled
> to Apache/openoffice-docs.
>
> There I could have told you that where you made the change in
> AOOO41GS1.odt, it should be "The subscription is needed ... "
>
>  - Dennis
>
> PS: Odd side note.  Apparently my default for .odt is Microsoft Word.  It
> opened the Preface just fine, and showed me the comments from Jean and you
> also.  I then re-opened in Writer.  There is nor visible difference in the
> document that is presented.
>
>
> -Original Message-
> From: F Campos Costero 
> Sent: Wednesday, February 10, 2021 11:20
> To: doc@openoffice.apache.org
> Subject: Update of 4 docs from Getting Started branch
>
> I just pushed my first revision of the first four sub documents of the
> Getting Started Guide (AOO41GS1 - AOO41GS4). I have not made a pull request
> yet. Since this is a new process for everyone, I thought Keith, Marcia or
> someone else might want an early look. I only turned on Record Changes for
> GS3 and GS4. Sorry! The biggest change was incorporation of the Sidebar in
> AOO41GS2 and Jean did almost all of that.
> All comments welcome!
> Francis
>

Update of 4 docs from Getting Started branch

[F Campos Costero]

I just pushed my first revision of the first four sub documents of the
Getting Started Guide (AOO41GS1 - AOO41GS4). I have not made a pull request
yet. Since this is a new process for everyone, I thought Keith, Marcia or
someone else might want an early look. I only turned on Record Changes for
GS3 and GS4. Sorry! The biggest change was incorporation of the Sidebar in
AOO41GS2 and Jean did almost all of that.
All comments welcome!
Francis

Re: Branch Getting-Started-Guide populated

[F Campos Costero]

Thanks, Keith. I will start working on the docs today or tomorrow. I don't
see the ods file in either branch. Am I missing the obvious or did you not
post it yet?
Francis

On Sun, Feb 7, 2021 at 2:19 PM Keith N. McKenna 
wrote:

> The files from Jean's taming book are now in the repository in the
> Branch Getting-Started-Guide. As jean is no longer interested in in
> updating her book, we have to change the name a few other things.
>
> There are all the chapter files plus a Master Document file (.odm)
> Because the chapter files were created from the Master Document the
> numbering is slightly off File File AOO41GS1.odt is not chapter one it
> is the preface.S2 is chapter 1 and so on. There is also a spreadsheet
> CheckOut.ods to track who is working on what until I can get with Infra
> around whether we can activate pages and projects on our repository.
>
>
> Regards
> Keith
>
>
>
>
>
>
>

Re: Repository Organization

[F Campos Costero]

At the moment, I am only planning changes by inserting comments. Some of
the images need to be updated, there are a few erroneous statements, and
there are some out-of-date statements that should be revised or deleted. I
hope to hold off on real editing until I see what Marcia has done, which
she hopes to post tomorrow. She and I will have to coordinate, probably by
chapter, if we will both be working on Taming.

I had also thought of using a tracking document so people can record what
they are working on. Most of the guides are available as standalone
chapters, so one could have a reasonably granular view of the work in
progress.

I think all of the 3.3 user guides could be loaded in the repository at
this point. I would be surprised if I can push to the repository or create
branches, I have no official Apache status and I suppose random people are
not allowed to do such things.

Francis

On Fri, Feb 5, 2021 at 1:10 PM Dave  wrote:

>
> Would a Document/Chapter "Status" spreadsheet be a possible option?
> Whereby a contributor "checks out" a file they will be working on by
> updating the spreadsheet and updates again upon returning the file.
>
> On 05/02/2021 19:29, Dennis Hamilton wrote:
> > Oh.  I would have thought the starting base documents would go in there
> first.  Under an OOo3.2 or something.
> >
> > How are Frances and Marcia avoiding collisions and/or duplication ?
> >
> > -Original Message-
> > From: Keith N. McKenna 
> > Sent: Friday, February 5, 2021 10:30
> > To: doc@openoffice.apache.org
> > Subject: Re: Repository Organization
> >
> > [orcmid] [ ... ]
> >
> > Both Frances and Marcia are marking up possible changes to Jean's taming
> aoo book and nothing is in the repository yet as it was just created a
> couple of days ago.
> >
> > Regards
> > Keith
>
> -
> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: doc-h...@openoffice.apache.org
>
>

Re: Repository Organization

[F Campos Costero]

I have limited experience with Git, using it only for my own small
projects, so my opinion should be weighted accordingly. My initial thought
is to not branch based on releases but to branch  on documents. Tagging
commits as representing a certain AOO release or perhaps as representing a
certain AOO release with respect to one document would be enough.

Am I right in thinking we would have about 15 documents even if everything
is brought up to date? The documents that come to mind are one guide per
application (6), the Taming AOO book, some OS specific short guides, and
the programming guide. I am not sure whether the developer's guide or the
building guide are part of the doc team's project.

The work flow I am imagining is to have a branch dedicated to each
document. When the document is ready to  become the latest version, the
branch is merged into a Main branch that has all of the documents in the
form in which they appear on the documentation web site. I suppose one
would update the document-specific branch to the latest version of all the
other documents just before pushing it to Main, I am not clear on just how
that would work. None of the public facing documents is ever edited except
in its own branch.  (There might be templates or other administrative
documents that are handled differently.) Each document-specific branch runs
on indefinitely since it will always have, in some commit, the
released version of that document.

Does that make even a little sense?

Francis

On Wed, Feb 3, 2021 at 10:06 AM Dennis Hamilton  wrote:

> There is only one project for all of it, so it is not clear how well the
> handling of multiple guides and other publications can be sequenced and
> synchronized.  Unfortunately, a check-out at this level will bring
> everything to a contributor's computer.  I don't know if there is a
> finer-grained way to handle this.  It would be worth investigating.  Most
> top-level GitHub projects provide multiple (sub-) projects so coordination
> is better.  However, github.com/apache/ is that level so such capability
> is already taken [;<).
>
> A subdirectory structure that has a folder for each guide or other
> publication, and maybe folders on templates and other materials for
> authors/editors would be helpful.  If these are actually (sub-) projects,
> working is even easier. There could still be subfolders on released, draft,
> or however you want to do that.
>
> It is possible to **label** *releases* rather than use branches for that
> purpose.  Also, it is better to branch at the individual document level, so
> maybe the branch name would specify what guide is being worked on in that
> branch.  When a document continues to be applicable to a newer release, one
> could simply tag it for that release as well.  There will need to be ground
> rules about this that are clear enough people don't do pushes against the
> wrong branches, etc.  The value is that you don't have to update all the
> documents for every dot-dot-release and interested parties can look at just
> the Getting Started, or the Writer document or whatever, and know what
> multiple releases the current one applies to.  You may need to have
> language as part of the substructure also, not just platform, however those
> varieties are to be handled.
>
> Sometimes, when the impact of a release is minor, one might one to provide
> a companion supplement to a full guide, also tagged for that release.
>
> There are many GitHub projects that can be inspected for how this sort of
> thing is done.  < https://github.com/MicrosoftDocs> is one example
> although I think the organization can be more thoughtful when focus is on
> AOO docs.  Carl Marcum must know of some approaches related to work he has
> done.
>
> If you have the rights, you can also enable Issues, Discussion and even
> Wiki for the openoffice-docs project.  You can then work out matters there
> in a form that is easier and more organized than using docs @ oo.a.o
> threads as a coordination mechanism.
>
> Happy day-after USA Ground Hog Day.  We have passed to the other side.
>
>  - Dennis
>
> PS: I still think you need to look at and consult Community Forum folk.
> There is a significant amount of experience there and it is almost all
> (power-) user facing.
>
>
> -Original Message-
> From: Keith N. McKenna 
> Sent: Wednesday, February 3, 2021 07:20
> To: doc@openoffice.apache.org
> Subject: Repository has been created
>
> I got word earlier from Carl Marcum that the repository
> https://github.com/apache/openoffice-docs has been created. It is pretty
> sparse at the moment as there is only the README.md file from my repo on
> GitHub.
>
> The next step is to define the the branches. Do we want a separate branch
> for each release of the the software for example 4.1.9, 4.1.10 or just for
> the major.minor, for example 4.1, 4.2 etc.
>
> The branch for each release has the potential to create more work in that
> we could be creating new documentation that 

Re: Question sent to ASF legal around using the old OOo documentation

[F Campos Costero]

In the thread titled "CC License on Externally-Produced Documentation"
(started on Jan 22), DaveB pointed out:

"There is nothing to discuss by the PMC or anyone else about having the
documentation on an ASF-owned repository. This has been happening since
AOO first came into existence see:
https://wiki.openoffice.org/wiki/Documentation/OOo3_User_Guides/OOo3.3_Chapters_ODT
All of those are under GNU General Public License
(http://www.gnu.org/licenses/gpl.html), version 3 or later, or the
Creative Commons Attribution License
(http://creativecommons.org/licenses/by/3.0/), version 3.0 or later,
being served from Registrant Organization: The Apache Software Foundation."


That is an excellent point. Let's just move forward with requesting a
repository for documentation.

Francis

On Sun, Jan 31, 2021 at 3:18 PM Keith N. McKenna 
wrote:

> See one comment in line.
> On 1/9/2021 12:05 PM, Dennis Hamilton wrote:
> > The TL;DR: What LibreOffice has done is no use for the creation of AOO
> documentation.
> >
> > THE SITUATION
> >
> > First, what LibreOffice does about cleaning up their help files is not
> something of concern to AOO (although leaving in links to openoffice.org
> support would be annoying).
> >
> > LibreOffice has made two noteworthy forks, one from openoffice.org
> (under LGPL license), and one from AOO (under Apache license).  The second
> allowed LibreOffice to fork code contributed to the ASF by IBM that was not
> part of openoffice.org.  The Apache-licensed fork also allowed the
> derivative to be licensed under the MPL, the license offered on current
> releases of LibreOffice.  [L]GPL licenses do not permit this.  It is also
> the case that patches and bug reports at AOO can be absorbed by LibreOffice
> (and not vice versa) although the maintenance and feature changes in the
> time since LibreOffice was originally forked makes LibreOffice increasingly
> different.
> >
> One slight errata one the above paragraph. We can and have received code
> from LibreOffice as long as the author of that code agrees to dual
> license it under ALv2 and current LO license.A work around for sure but
> it has gained us some code fixes.
>
> Keith
>
> > Technically, making a derivative that is made available under a
> different license does not impact the copyright on the original code or the
> unaltered code in the derivative.  That has to do with how copyright
> works.  Generally, one has no copyright on work of another.  The prominent
> exception is work for hire, where the employer has copyright where the
> employee would have otherwise.  That is not the issue here.
> >> I do not speak for the ASF or ASF Legal.  I can point out that the ASF
> has expressed disinterest in policing how others fork code from ASF
> projects apart from abuses of ASF trademarks.
> >
> > ASF has a SERIOUS POLICY AND PRACTICE COMMITMENT to clean provenance and
> good open-source citizenship of ASF projects and what is carried in project
> repositories and releases.  IT IS THAT COMMITMENT that gives rise to the
> difficulty of building ASF Project content based on the OpenOffice.org
> documentation produced elsewhere and not part of the Oracle grant of
> openoffice.org code to the ASF.  (This extends to how libraries under
> different licenses, when optionally used in builds of ASF releases, are
> excluded from direct inclusion in the ASF Project repositories, a provision
> that is not helpful in deriving documentation for AOO.)
> >
> > While it may seem peculiar, it is the case that the ASF has no concern
> were a third party to fork the OpenOffice.org 3.2 documentation and align
> it with current AOO releases, provided that ASF trademarks were respected
> and there was no claimed origin and support of the ASF and the AOO
> project.  The results should respect all licenses and copyright of the
> original documentation, of course.
> >
> > It is unfortunate that the good offices of the ODF Authors project were
> not accepted at a time when it could have made a difference.  That option
> is no longer available.  Jean Weber is to be commended for the effort she
> expended in providing that opportunity.  The AOO Project did not exercise
> the will or the capacity to take that avenue.  And here we are, where we
> have always been, as time goes by.
> >
> >  - Dennis
> >
> > -Original Message-
> > From: marcia wilbur 
> > Sent: Saturday, January 9, 2021 04:17
> > To: doc@openoffice.apache.org
> > Subject: Re: Question sent to ASF legal around using the old OOo
> documentation
> >
> > Of course, while in the libreoffice code last week, I did notice a
> tremendous amount of references to and use of "openoffice".
> >
> > I had been in the help for Libreoffice!
> >
> > /user/share/libreoffice/help/en-us
> >
> >
> > Attached is a screen capture "default.css".
> >
> > Now, I am not *as* familiar (yet) with the Apache License as I am with
> the GPL, So, I think this may be another ticket for legal to review.
> >
> > In a fork with GPL, no 

How to unsubscribe

[F Campos Costero]

There have been several emails recently from people wanting to unsubscribe
from the mail list. To do that,  please send an email from the account that
is receiving mail to
doc-unsubscr...@openoffice.apache.org

You should then receive a confirmation message to which you must respond.
Please check your spam folder if it seems the email did not arrive.

Regards,
Francis

Re: Getting Started Guide (was Proposed Process for Documentation)

[F Campos Costero]

I think Keith's preference was to use Git. I have only used Git a little to
track my own work but that choice seems fine to me.
Marcia - are you OK with that choice? If so, we would have to ask how one
gets a repository set up under the project's ownership.

Francis

On Sat, Jan 30, 2021 at 6:22 PM marcia wilbur  wrote:

> Thanks for the resource!
> I am wondering, I know we use styles etc... within writer, but do we have
> a style guide or a style cheatsheet?
>
> Also, was there a determination on options for collaboration?
> For example, I have marked up portions of the taming document - what is
> the process for sharing?
> The wiki? Gitbox area?  e-mail?
>
> Thanks,
>
> - Original Message -
> From: "Keith N. McKenna" 
> To: doc@openoffice.apache.org
> Sent: Saturday, January 30, 2021 4:34:39 PM
> Subject: Re: Getting Started Guide (was Proposed Process for Documentation)
>
> On 1/28/2021 1:37 PM, F Campos Costero wrote:
> > Another benefit of Marcia writing a Linux guide is that it could be used,
> > with her approval, as a template for other guides. Maybe I am being too
> > optimistic but I expect  most of the topics would be the same among the
> > three guides and the general organization should be the same.
> >
> > Francis
> >
> I have a document template .ott file that is based on the Version 3.3
> OOo documentation. It has all of the styles used there as well as the
> ones in Jeanne's Taming Guide as well as  couple from he later that
> where new and I felt where better than those supplied in the
> original.The use of AOO and its designed in use of templates are, in my
> opinion, important for 2 reasons. First it gives the documentation a
> consistent and professional look and feel. Second it showcases the
> strengths of the product and is in itself a strong marketing tool.
>
> There may be a few additions or deletions that could be made, but it is
> usable as it stands. It can be copied from:
>
> https://github.com/knmc/AOO-DocumentationProject/blob/Templates/AOO%20Documentation%20Template.ott
> .
> Any Questions on its use or suggestions for how to make it better are
> always welcome and can be addressed to this list.
>
> Regards
> Keith
>
> 
>
> -
> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: doc-h...@openoffice.apache.org
>
>

Re: Linux AOO Getting Started Guide

[F Campos Costero]

I see images on both Linux Mint 18.04 and Windows 10. For example, on page
13 I see an image of the Page Style dialog.

Francis

On Thu, Jan 28, 2021 at 11:53 AM marcia wilbur  wrote:

> Thanks for that information.
> My focus so far has been with Debian based and variants, but could be
> expanded to others or generalized for others.
>
> As for BSD, those users are so intense, they don't need guidance! Just
> joking. This is a consideration, and I definitely will consider this during
> the content creation process.
>
> Also, I made some comments for the first dozen or so pages of "taming".
>
> However, images are not displaying in my version of OO. 4.1.8
> Can someone else open the document and let me know if images are
> displaying for 4.1.8 on Linux or even another OS
>
> I used a competing product to open the odt and images display fine.
>
> thanks.
>
> - Original Message -
> From: "Dennis Hamilton" 
> To: doc@openoffice.apache.org
> Sent: Thursday, January 28, 2021 9:48:45 AM
> Subject: Linux AOO Getting Started Guide
>
> Marcia,
>
> Thank you for the license links and your appraisal.
>
> Your choosing GNU Linux to feature will be welcome.  There are also some
> variations to consider, since different desktop Linux distributions may
> have somewhat different application appearance and, in particular, install
> differences when AOO is not furnished by the distribution.
>
> I don't know if you consider BSD Unix and FreeBSD within your reach or
> not.  The CC-By licensing will be favorable there.  Also, some Linux
> distros might provide AOO as an installable option.  I think BSD also did
> that, in the past.  I don't know if the practice has been continued.
>
> There is now a Windows Subsystem for Linux (WSL) as a native subsystem
> (not just under a VM).  I have no idea whether anyone uses AOO for
> production use in that case, but a reviewer might with regard to checking
> your Getting Started drafts.  The installation of WSL improves with each
> W10 release, and the ability to launch Windows apps from the WSL (and vice
> versa) is improving all the time.  <
> https://docs.microsoft.com/en-us/windows/wsl/install-win10>.
>
> I wish you success in creation of a Getting Started guide that is oriented
> to what Linux users will see and need to know for successful application of
> Apache OpenOffice Linux-targeted release versions.
>
>  - Dennis
>
>
> -Original Message-
> From: marcia wilbur 
> Sent: Wednesday, January 27, 2021 21:32
> To: doc@openoffice.apache.org
> Subject: Re: Getting Started Guide (was Proposed Process for Documentation)
>
> Hi. According to CC 3.0 - there must be information regarding changes
> being made in general. "if changes were made" However, I did not see any
> indication of specifics (that might be time consuming but maybe like a
> changelog for docs) Here is the link to cc 3.0 info
> [orcmid]
>  and also <
> https://creativecommons.org/licenses/by/4.0/>
> [orcmid]
>
> No additional restrictions - You may not apply legal terms or
> technological measures that legally restrict others from doing anything the
> license permits.
>
>
> I did not realize the GNU Linux user base was so low... even then.
> However, I will continue the effort for the 3% or so - because I'm weird
> like that. I started the Get Started, I'll see it through. Thank you for
> the information.
>
> In this case,  I would say - an effort for the larger user base is
> important.
>
> Someone who is willing to take on the Windows content - making this more
> current would be a good idea.
> Are we using gitbox?
>
> I won't touch Windows, I don't have windows... but I can mark up and give
> feedback for that taming or whatever doc using OO and provide
> feedback/recommendations for documentation. However, do not associate me
> with any Windows effort - haha :)
>
> The feedback is for everyone.
>
> Thanks.
>
>
>
>
> - Original Message -
> From: "Dennis Hamilton" 
> To: doc@openoffice.apache.org
> Sent: Wednesday, January 27, 2021 10:29:52 AM
> Subject: RE: Getting Started Guide (was Proposed Process for Documentation)
>
> Two things,
>
>  1. It is useful to know the demographics of Apache OpenOffice users.  The
> latest board report does not break out downloads by platforms and languages
> any longer.   In October 2015 this was the breakdown for AOO 4.1.1
> downloads at that point in time:
>
>87.7% were for Windows
> 9.1% were for Macintosh
> 3.2% were for everything else, including Linux
>
> The prevalent languages have tended to toggle between English and French.
>
> I would be surprised to learn that this pattern has changed in any
> significant way.
>
> The Community Forums activity might also be valuable in this respect, and
> easier to find.
>
> Of course, for documentation, how different platforms are supported is up
> to those willing to develop such documentation.  I have no quarrel,
> especially for Getting Started, with 

Re: Getting Started Guide (was Proposed Process for Documentation)

[F Campos Costero]

Another benefit of Marcia writing a Linux guide is that it could be used,
with her approval, as a template for other guides. Maybe I am being too
optimistic but I expect  most of the topics would be the same among the
three guides and the general organization should be the same.

Francis

On Wed, Jan 27, 2021 at 10:32 PM marcia wilbur  wrote:

> Hi. According to CC 3.0 - there must be information regarding changes
> being made in general. "if changes were made" However, I did not see any
> indication of specifics (that might be time consuming but maybe like a
> changelog for docs)
> Here is the link to cc 3.0 info:
>
> https://creativecommons.org/licenses/by/3.0/
> Under the following terms:
> Attribution — You must give appropriate credit, provide a link to the
> license, and indicate if changes were made. You may do so in any reasonable
> manner, but not in any way that suggests the licensor endorses you or your
> use.
>
> No additional restrictions — You may not apply legal terms or
> technological measures that legally restrict others from doing anything the
> license permits.
>
>
> I did not realize the GNU Linux user base was so low... even then.
> However, I will continue the effort for the 3% or so - because I'm weird
> like that. I started the Get Started, I'll see it through. Thank you for
> the information.
>
> In this case,  I would say - an effort for the larger user base is
> important.
>
> Someone who is willing to take on the Windows content - making this more
> current would be a good idea.
> Are we using gitbox?
>
> I won't touch Windows, I don't have windows... but I can mark up and give
> feedback for that taming or whatever doc using OO and provide
> feedback/recommendations for documentation. However, do not associate me
> with any Windows effort - haha :)
>
> The feedback is for everyone.
>
> Thanks.
>
>
>
>
> - Original Message -
> From: "Dennis Hamilton" 
> To: doc@openoffice.apache.org
> Sent: Wednesday, January 27, 2021 10:29:52 AM
> Subject: RE: Getting Started Guide (was Proposed Process for Documentation)
>
> Two things,
>
>  1. It is useful to know the demographics of Apache OpenOffice users.  The
> latest board report does not break out downloads by platforms and languages
> any longer.   In October 2015 this was the breakdown for AOO 4.1.1
> downloads at that point in time:
>
>87.7% were for Windows
> 9.1% were for Macintosh
> 3.2% were for everything else, including Linux
>
> The prevalent languages have tended to toggle between English and French.
>
> I would be surprised to learn that this pattern has changed in any
> significant way.
>
> The Community Forums activity might also be valuable in this respect, and
> easier to find.
>
> Of course, for documentation, how different platforms are supported is up
> to those willing to develop such documentation.  I have no quarrel,
> especially for Getting Started, with addressing whatever platforms an
> author wants to specialize for to accommodate the readers.
>
>  2. I understand that the contributor of a document under CC-BY specifies
> how attribution is to be made.  I am not aware that there is any
> requirement to specify the changes made.  Normally, one simply provides the
> attribution and source of the document(s) on which the derivative is based.
>
> Marcia, can you point us to where in the CC-BY description that changes
> must be identified?
>
>  - Dennis
>
> -Original Message-
> From: marcia wilbur 
> Sent: Wednesday, January 27, 2021 02:28
> To: doc@openoffice.apache.org
> Subject: Re: Getting Started Guide (was Proposed Process for Documentation)
>
> [orcmid] [ ... ]
>
> One thing to mention - is the taming doc is under CC 3.0.
> This requires attribution and indication changes were made with a deriv
>
> [ ... ]
>
> -
> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: doc-h...@openoffice.apache.org
>
> -
> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: doc-h...@openoffice.apache.org
>
>

Re: Getting Started Guide (was Proposed Process for Documentation)

[F Campos Costero]

It seems we have two possible projects for Robert to work on: a Mac version
of a brief Getting Started guide and the updating of Jean's Taming AOO
book.

I like the idea of short OS-specific guides. The people most likely to need
a Getting Started guide are also probably the most likely to get confused
by information that is not relevant to their OS and 300 pages is
intimidating if you are really a total novice. Each OS also has quirks
associated with installation that would be well handled in a dedicated
guide. Writing the guides from scratch would allow licensing them however
the author prefers. If they are relatively brief, we could have new content
up quickly and such visible progress would be welcome.

A huge advantage of revising Taming AOO is that it probably does not need a
lot of changes. Though the revision would probably take quite a while, I
expect the rate of producing up-to-date content would be high.

I think I will start to go through the Taming AOO book and make notes on
what changes should or could be made.

@Robert - Are you interested in writing a Mac Getting Started guide from
scratch? Alternatively, you and I could survey different sections of Taming
AOO for necessary revisions.

@Marcia - If Robert is interested in writing a Mac guide, would it make
sense to coordinate the content of the two guides so the scopes are similar?

Francis



On Wed, Jan 27, 2021 at 3:28 AM marcia wilbur  wrote:

> Hi.
>
> I did start from scratch. I am in content development phase of the get
> started for GNU Linux.
>
> @Robert,
>
> What Mac users need is a guide for specific Mac Options and functionality.
> One issue is Mac user options are not represented in current documentation
> - comprehensively. In fact, in some cases, in documentation, GNU Linux
> users and Mac users are represented as a second class to Windows.
>
> Using the Taming guide as an example:
>
>
> Page 18:
>
> Using the Quickstarter in Linux and Mac OS X
> Apache OpenOffice under Linux has a Quickstarter that looks and acts like
> the one described
> above for Windows. (The checkbox on the Memory page is labeled Enable
> systray quickstarter.
> If you do not have this checkbox, the Quickstarter module is not installed
> on your system.)
> Mac OS X provides similar functionality through a pop-up menu from the
> dock.
>
>
> There is no GNU Linux or Mac images, just a textual description of 
> this is like the windows one here.
> Could be improved!
>
>
> also the preface states:
>
> Anyone who wants to get up to speed quickly with Apache OpenOffice will
> find this book valuable.
>
>
> 316 pages seems a bit much to get up to speed "quickly".
>
>
> One thing to mention - is the taming doc is under CC 3.0.
> This requires attribution and indication changes were made with a deriv
>
> http://taming-apacheopenoffice.com/downloads/TamingAOO34.pdf
>
>
>
> - Original Message -
> From: "Robert Farrell" 
> To: doc@openoffice.apache.org
> Sent: Wednesday, January 27, 2021 12:53:22 AM
> Subject: Re: Getting Started Guide (was Proposed Process for Documentation)
>
> Yes, I can work on that. Tell me what needs to be done. I do not want to
> double up on someone else’s efforts.
>
> Robert
>
> Robert Farrell
> robertfarr...@embarqmail.com
>
>
>
> > On Jan 25, 2021, at 10:03 AM, F Campos Costero 
> wrote:
> >
> > I think discussion specific to a new Getting Started Guide should have
> its
> > own thread, so i am launching this one.
> >
> > @Marcia - It is great that you are working on a guide. Did you start it
> > from scratch or is it based on some other document? How far have you
> gotten?
> >
> > @Robert - You expressed interest in working on a Getting Started Guide.
> > Have you seen the links that Jean provided to her book?
> > PDF  http://taming-apacheopenoffice.com/downloads/TamingAOO34.pdf
> > ODT  http://taming-apacheopenoffice.com/downloads/TamingAOO34.odt
> >
> > Would you be interested in working on that?
> >
> > Francis
>
>
> -
> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: doc-h...@openoffice.apache.org
>
> -
> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: doc-h...@openoffice.apache.org
>
>

Re: CC License on Externally-Produced Documentation

[F Campos Costero]

 How do we bring to a close the question of how to host the working texts?
Should a thread be opened, perhaps on dev, to allow the PMC to express
opinions and then vote on having the documentation on an ASF-owned
repository?

Francis

On Sun, Jan 24, 2021 at 3:55 PM Andrea Pescetti  wrote:

> On 22/01/2021 Dennis Hamilton wrote:
> > In the case of documentation projects and their repositories, the
> exception is not workable.
>
> Hello Dennis, nice to hear from you... it's been a while!
>
> I basically I agree to everything, but I go a bit further in that I
> don't see a restriction on using an ASF-owned repository.
>
> We all agree that most of what was written to this list about licenses
> mixes up releases and other work. Documentation does not go into an
> Apache release and it does not undergo a formal vote by the PMC, so the
> release policy does not apply to it.
>
> This means that people from the project can work on CC-BY documentation,
> and here we agree.
>
> And, if you ask me, my view is that they can do that even using an
> ASF-owned repository different from our source repository; then others
> might believe that every commit is a release and then we might interpret
> https://issues.apache.org/jira/browse/LEGAL-552 in different ways.
>
> But honestly I would still pursue the avenue of a dedicated ASF
> repository. All we need to do is, maybe, reopen LEGAL-552 and ask for
> additional clarifications.
>
> Regards,
>Andrea.
>
> -
> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: doc-h...@openoffice.apache.org
>
>

Getting Started Guide (was Proposed Process for Documentation)

[F Campos Costero]

I think discussion specific to a new Getting Started Guide should have its
own thread, so i am launching this one.

@Marcia - It is great that you are working on a guide. Did you start it
from scratch or is it based on some other document? How far have you gotten?

@Robert - You expressed interest in working on a Getting Started Guide.
Have you seen the links that Jean provided to her book?
PDF  http://taming-apacheopenoffice.com/downloads/TamingAOO34.pdf
ODT  http://taming-apacheopenoffice.com/downloads/TamingAOO34.odt

Would you be interested in working on that?

Francis

Re: User guide for AOO

[F Campos Costero]

Jean - Thank you for considering this! It would be a very valuable
contribution. If you do decide to go ahead with the revision, would you
prefer to do the updating entirely on your own or could others help in some
way?

Francis

On Thu, Jan 21, 2021 at 4:41 PM Jean Weber  wrote:

> I'm thinking of updating my self-published “Getting Started” book on AOO
> and making it available to the community in free PDF and low-cost printed
> copy, whether you choose to link to it or publicise it in any way. It could
> be dual-licensed CC-BY & GPL, but not A2.
>
> The v3.4 version of this book began in the ODFAuthors group, but after AOO
> rejected it, I completed it and published it under my own name in 2013. It
> doesn’t cover the full range of topics as for the old OOo book, but IMO a
> “Getting Started” book doesn’t need to do that.
>
> Jean
>

Re: Proposed Process for Documentation

[F Campos Costero]

I agree that there is no significant  conflict here. The only outstanding
question is where to host the documents. Settling that should not inhibit
anyone from working on documents.

One feature of the Apache governance method is that volunteers decide what
will get done and how it will be done. The question of document hosting can
be decided by the interested parties. The PMC should know what will be
done, in case it is obviously unacceptable, but making a decision and
taking action is largely up to the few people in this discussion.

I will find Jean's message about her Getting Started Guide and ask for more
details about what she is considering.

Francis

On Sat, Jan 23, 2021 at 7:04 PM Dennis Hamilton  wrote:

> -Original Message-
> From: Keith N. McKenna 
> Sent: Saturday, January 23, 2021 15:43
> To: doc@openoffice.apache.org
> Subject: Re: Proposed Process for Documentation
>
> [orcmid] [ ... ]
>
> As there are obviously still conflicting views on how documentation should
> be handled. I have decided to step away from this entirely and concentrate
> my volunteer efforts elsewhere.
>
> Regards
> Keith
>
> [orcmid]
> I don't think there are conflicting views.  There have been considerations
> of a few approaches and ways of satisfying ASF sensibilities.   There are
> some concerns about ASF sensibilities with regard to carrying
> "foreign"-licensed materials in ASF repositories.
>
> For example, one option would be going the AOOAuthors route and hosting
> that effort on GitHub.
>
> The alternative Keith favors involves hosting within the AOO project in a
> manner that does not conflict with ASF sensibilities about licenses.  As
> far as I can tell, no one is stopping that being set up and contributors
> recruited.
>
> One caveat.  Jean Weber has offered to update her self-published "Getting
> Started" book on AOO to be suitable for AOO 4.1 users (unless 4.2 is
> imminent, I suppose).  It would seem valuable to rely on that, including
> assisting her, rather than have duplicate effort inside the AOO project.
>  So maybe there should be a different focus for the AOO effort, starting
> with OO 3.2 User Guides.
>
>  - Dennis
>
> -
> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: doc-h...@openoffice.apache.org
>

Re: New Doc Volunteer

[F Campos Costero]

Hello Robert,

Thank you very much for volunteering!  I'll keep this message very brief
because I am at the end of a long work day and not feeling very coherent.
Regarding your question, it is probably best to consider what the likely
situation will be rather than all possible licensing scenarios. There is a
body of documentation licensed under the Creative Commons Attribution
License (CC-BY) (http://creativecommons.org/licenses/by/3.0/ ) that would
provide a rich resource for documenting the current version of OpenOffice.
The current plan, I believe, is to work under the permissions of that
license. You would have a copyright to what you write but you would license
many of those rights to anyone who has a copy of your work. Please take a
look at the web page I linked and perhaps the license itself. I'm sure
people here would be happy to discuss any questions you have, though I
don't think we have any lawyers on this list.
Regards,
Francis

On Thu, Jan 21, 2021 at 8:53 PM Robert Farrell 
wrote:

> Hi all,
>
> I’m a technical writer who has worked on documentation for medical devices
> and software. I have been using OpenOffice for several years for other
> projects, and have always appreciated the open source nature of the
> software.
>
> I have never worked on a project where documentation is licensed.
> Everything I’ve worked on has been work-for-hire and copyrighted (which
> means, of course, no attributions) as opposed to licensing. What do I need
> to take into consideration when creating documentation for this project?
>
> Thanks
>
>
> Robert Farrell
> robertfarr...@embarqmail.com
>
>
>
>
> -
> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: doc-h...@openoffice.apache.org
>
>

Re: Proposed Process for Documentation

[F Campos Costero]

Keith - Have you looked into using Git with the odt file format. I did a
quick search and it seems that Git can only handle a plain text version of
the document if you want to see a Diff between two versions. So you could
see which words had changed and differences in the grouping of text in
paragraphs but things like the formatting of text or arrangement of images
with respect to the text could not be tracked through git diff. Of course,
changes could be tracked within the odt file, though even that is not
comprehensive. For example, changing a paragraph's style  does not seem to
be captured. Dennis's point about how edits will be coordinated and
versions controlled is very important.. I have no experience with technical
writing beyond writing drafts and handing them to "the documentation
people" to do their magic, so I can't give any really informed advice. The
matter does bear some very careful thinking and discussion. Luckily, we
will not have to deal with a huge team right away.

regards,
Francis

On Thu, Jan 14, 2021 at 10:26 AM Keith N. McKenna 
wrote:

> On 1/13/2021 6:17 PM, Dennis Hamilton wrote:
> > I don't see an attachment (apart from the digital signature).  Is there
> a GitHub reposi8tory set up available?
> >
> > Good news though.
> >
> > I am curious how the coordination of edits and the use of GitHub version
> control will be navigated.  I look forward to seeing how that unfolds.
> >
> >  - Dennis
> >
> Sorry about that. I could claim it was a senior moment, but since you
> have a few years on me that one is not going to work. This time I am
> attaching it.
>
> Keith
> > -Original Message-
> > From: Keith N. McKenna 
> > Sent: Wednesday, January 13, 2021 13:34
> > To: doc@openoffice.apache.org
> > Subject: Proposed Process for Documentation
> >
> > Greetings All;
> > After a discussion on legal@, as long as we do not include them in an
> > "Official Release" we can use the .odt files for version 3 that are
> > stored on the mwiki to bring them up to date for version 4.x.x and above.
> >
> > Attached is a proposed process utilizing a GitHub repository for version
> > control of the User Guides and other Documentation. It is in .odt format
> > with changes enabled. Please feel free to edit it and/or make any
> > comments you feel are needed.
> >
> > Regards
> > Keith
> >
> >
> > -
> > To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> > For additional commands, e-mail: doc-h...@openoffice.apache.org
> >
>
>

Re: [proposal} Trying to re-generate the Documentation effort

[F Campos Costero]

To remove yourself from the mailing list, send a message to
*doc*-unsubscr...@openoffice.apache.org

Regards,
Francis

On Thu, Dec 10, 2020 at 10:43 PM Mitul Patel  wrote:

> Dear All,
>
> Sorry for the sudden intrusion.
>
> May I be removed from this mailing list?
>
> Sincerely,
> Mitul Patel
>
> On Fri, Dec 11, 2020, 04:52 Keith N. McKenna 
> wrote:
>
> > On 12/9/2020 10:45 PM, F Campos Costero wrote:
> > > I agree with your recommendation; it is the obvious path. I made one
> tiny
> > > tweak to the document. I look forward to a discussion of next steps.
> > > Regards,
> > > Francis
> > >
> > Francis;
> >
> > Can you send me the revised document so I can accept the changes you
> > made. I will be starting a Process document either later tonight or
> > tomorrow.
> >
> > Regards
> > Keith
> >
> > > On Tue, Dec 8, 2020 at 3:59 PM Keith N. McKenna <
> > keith.mcke...@comcast.net>
> > > wrote:
> > >
> > 
> >
> >
>

Re: [proposal} Trying to re-generate the Documentation effort

[F Campos Costero]

I agree with your recommendation; it is the obvious path. I made one tiny
tweak to the document. I look forward to a discussion of next steps.
Regards,
Francis

On Tue, Dec 8, 2020 at 3:59 PM Keith N. McKenna 
wrote:

> On 6/13/2020 4:52 PM, Keith N. McKenna wrote:
> > Greetings all;
> >
> > As the subject states I am proposing a new methodology to try to
> > reinvigorate the stalled documentation effort for AOO. For the first
> > step in this I have created a draft document that lays out the problems
> > and also some proposed solutions. As all most of you have been involved
> > in the documentation effort I would appreciate your comments and
> > suggested changes to it. The document was created in Writer and has
> > record and read changes turned on. Feel free to make any changes or
> > additions you feel could be helpful. Of course comments or suggestions
> > are welcome as replies to the to this mailing list as well.
> >
> > Thank you all in advance for taking time to contribute to this effort
> > and I hope many of you will return to the documentation team as we move
> > forward with this.
> >
> > Regards
> > Keith N. McKenna
> >
> >
> The final draft of the proposal document including my recommendations is
> ready for review and can be downloaded in ODF or PDF format from the
> following: https://1drv.ms/f/s!AsMYmStvrJNJinVnnJWlYCHrxzmc.
>
>
> The odt document is set to record changes so if anyone has any changes
> they would like to see you can add them directly to the document. Thank
> you in advance to reviewing this hopefully final draft.
>
> Regards
> Keith
>
>

Re: Hello!

[F Campos Costero]

Hi Katie,
I see your message has gone unanswered for too long so I will jump in.
Keith has been trying to revive the documentation team and I offered to
help where I can.  The big technical hang up was that the extension to
export Writer documents in MediaWiki format was broken for a long time. I
understand that it has been fixed in version 4.1.8. If we are truly past
that problem, there is a lot of work that can be done. Let's give Keith a
little time to respond since this is a holiday week in the US. In the
meantime, welcome to the team! I think you have just the interests and
background we need!
Francis

On Mon, Nov 23, 2020 at 2:05 PM Katie Knish  wrote:

> Hi everyone!
>
> My name is Katie Knish, and I just signed up to be on the documentation
> team. My background is mostly in editing (largely within the sciences and
> medical communications, with some fiction and advertising thrown in years
> ago). I just did a JavaScript bootcamp over the summer after teaching
> myself other coding topics for a couple years, and I've long been a fan of
> OpenOffice and of the collaborative nature of open source.
>
> I've been interested in diving into technical writing for a while now but
> am unsure where to start. My writing and editing skills are strong, as is
> my ability to distill complex topics into materials appropriate for a range
> of audiences, and I'd love to help out in any way I can!
>
> Thanks! I hope everyone's having a good Monday.
>
> Katie
>

Re: [proposal} Trying to re-generate the Documentation effort

[F Campos Costero]

Hello Detlef,
I am new to the documentation team but speaking for myself I would very
much welcome your participation. I too looked briefly at pandoc to
translate from odt to MeidaWiki. The result was certainly not a complete
success. It seemed the image references would have to be inserted manually.
This thread is probably not the place to discuss the details but I am
interested in finding the best way to do the odt -> MediaWiki translation.
Let's see what the result of this thread is. In any case, whatever
contribution you can make to the documentation in general would be very
welcome.
Regards,
Francis

On Sat, Jun 13, 2020 at 3:14 PM Detlef Nannen 
wrote:

> Hello,
>
> I read your discussion of DocBooc. Also, I have already installed Pandoc
> and made first tests. Didn't work out well, but I'm only at the beginning.
>
> Some time ago, I started to translate an old documentation about Writer
> into German and then update it to version 4.x. After some time I stopped
> the action. In the team this will surely become easier. Will this work
> here?
>
> --
> Greetings
> Detlef Nannen
>
> Am 13. Juni 2020 22:52:42 schrieb "Keith N. McKenna"
> :
>
> > Greetings all;
> >
> > As the subject states I am proposing a new methodology to try to
> > reinvigorate the stalled documentation effort for AOO. For the first
> > step in this I have created a draft document that lays out the problems
> > and also some proposed solutions. As all most of you have been involved
> > in the documentation effort I would appreciate your comments and
> > suggested changes to it. The document was created in Writer and has
> > record and read changes turned on. Feel free to make any changes or
> > additions you feel could be helpful. Of course comments or suggestions
> > are welcome as replies to the to this mailing list as well.
> >
> > Thank you all in advance for taking time to contribute to this effort
> > and I hope many of you will return to the documentation team as we move
> > forward with this.
> >
> > Regards
> > Keith N. McKenna
>
>
>
>
> -
> To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: doc-h...@openoffice.apache.org
>
>

Re: Applying as Technical Writer

[F Campos Costero]

Dave,
Can you explain what you would like to have done? Would you like to have
HTML versions of the documents or some other changes to the web page?
Francis

On Tue, Jun 9, 2020 at 12:53 AM Dave  wrote:

> Please have a look at my documentation for students at openoffice-uni.org.
> Would be grateful.
>
> On Tue 9. Jun 2020 at 06:03, F Campos Costero 
> wrote:
>
> > Hello Kerin,
> > Thank you for volunteering to support Apache OpenOffice! I have just
> > started to help with the documentation, so I cannot provide a lot of
> > guidance at the moment. I have been doing user support on the forum for
> > about ten years, so I am familiar with the project in general. Keith
> > McKenna will probably be the person who can provide the most guidance
> and I
> > hope you will hear from him within the next day.
> >
> > Best regards,
> >
> > Francis
> >
> > On Mon, Jun 8, 2020 at 9:28 PM Kerin Khan  wrote:
> >
> > > Hello,
> > >
> > >
> > > My name is Kerin. I am a 3rd-year Cognitive Science student at UC
> > Berkeley.
> > > I have 2 years of experience building Javascript, Html, and CSS
> > projects. I
> > > want to contribute to the technical documentation for a duration of 6
> > > months. I could help 10 hours per week. I look forward to hearing from
> > you.
> > >
> > >
> > > Thanks,
> > >
> > > Kerin
> > >
> >
>

Re: Applying as Technical Writer

[F Campos Costero]

Hello Kerin,
Thank you for volunteering to support Apache OpenOffice! I have just
started to help with the documentation, so I cannot provide a lot of
guidance at the moment. I have been doing user support on the forum for
about ten years, so I am familiar with the project in general. Keith
McKenna will probably be the person who can provide the most guidance and I
hope you will hear from him within the next day.

Best regards,

Francis

On Mon, Jun 8, 2020 at 9:28 PM Kerin Khan  wrote:

> Hello,
>
>
> My name is Kerin. I am a 3rd-year Cognitive Science student at UC Berkeley.
> I have 2 years of experience building Javascript, Html, and CSS projects. I
> want to contribute to the technical documentation for a duration of 6
> months. I could help 10 hours per week. I look forward to hearing from you.
>
>
> Thanks,
>
> Kerin
>