Re: [libreoffice-documentation] Re: Question about BG6207.
Hello Dan, For your First Question: The paragraph says that the heading of the table inserted in writer can be taken from the field names in the database table by clicking on "Insert table heading" and selecting "Apply column name". or you can insert a blank row on top of the table to insert the heading of the table manually by selecting "Create row only" after checking " Apply column name "(see figure 5). The second option is better according to me as in most of the cases, field names can be confusing, so a different heading can be given. In this case also, you need to be in writer or calc. Pulkit Krishna On Sat, Mar 28, 2020 at 9:28 AM Pulkit Krishna wrote: > Hello Dan, > Regarding your second question: > Yes, You are supposed to be in Writer when doing this. The heading given > is Mail Merge. The chapter is linking database and mail merge is one of the > way to do this. The instructions written in the guide are clear (or rather > I will say, will become clear) except the fact the you have to do so in > writer is not given. I took it for understood that mail merge should be > done in writer only, so I didn't mentioned it. You can mention it after the > heading "Mail Merge" before returning the chapter to feedback folder.As you > say you have not used mail merge since before 2008 so either you can try > mail merge or refer to writer guide for more clearer instruction. Well, we > can also refer to writer guide there. Kindly add the reference there. > Pulkit Krishna > > > On Sat, Mar 28, 2020 at 12:29 AM Dan Lewis > wrote: > >> >> On 3/27/20 11:24, Dan Lewis wrote: >> > >> > The row chosen for the table heading can be taken from the column >> > names, or the record may be written out with space left for the >> > headings to be edited in later. >> > >> > This paragraph is found on page 7, 3 paragraphs below Figure 5. >> > >> > I have no idea of how I can review this as I have no idea how to do >> this. >> > >> > Dan >> > >> Then on pages 9 & 10: >> >> To launch the database, right-click on the database itself or on one of >> its tables or queries; this immediately refreshes the display in the >> data source browser. After that the Mail Merge Wizard can be called up >> by using the corresponding button. >> >> >> Data source of current document >> >> Click on the *Data Source of Current Document*button to open a direct >> view ofthe table which forms the basis for the data inserted into the >> document. In the above example, the Persontable from the Addresses >> database/appears/. >> >> I get a refreshment when I right click a query or table in the Data >> Source window, but what that got to do with the Mail Merge Wizard? What >> is the corresponding button? >> >> The Data Source of Current Document button is a mystery to me. Am I >> suppose to be in Writer when I do this? This button is only suppose to >> be available for use when it Writer or Calc. There is some missing >> information here. I have not used Mail Merge since before 2008, so I am >> very rusty here. >> >> Dan >> >> >> >> -- >> To unsubscribe e-mail to: >> documentation+unsubscr...@global.libreoffice.org >> Problems? >> https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ >> Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette >> List archive: https://listarchives.libreoffice.org/global/documentation/ >> Privacy Policy: https://www.documentfoundation.org/privacy >> > -- To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/documentation/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-documentation] Re: Question about BG6207.
Hello Dan, Regarding your second question: Yes, You are supposed to be in Writer when doing this. The heading given is Mail Merge. The chapter is linking database and mail merge is one of the way to do this. The instructions written in the guide are clear (or rather I will say, will become clear) except the fact the you have to do so in writer is not given. I took it for understood that mail merge should be done in writer only, so I didn't mentioned it. You can mention it after the heading "Mail Merge" before returning the chapter to feedback folder.As you say you have not used mail merge since before 2008 so either you can try mail merge or refer to writer guide for more clearer instruction. Well, we can also refer to writer guide there. Kindly add the reference there. Pulkit Krishna On Sat, Mar 28, 2020 at 12:29 AM Dan Lewis wrote: > > On 3/27/20 11:24, Dan Lewis wrote: > > > > The row chosen for the table heading can be taken from the column > > names, or the record may be written out with space left for the > > headings to be edited in later. > > > > This paragraph is found on page 7, 3 paragraphs below Figure 5. > > > > I have no idea of how I can review this as I have no idea how to do this. > > > > Dan > > > Then on pages 9 & 10: > > To launch the database, right-click on the database itself or on one of > its tables or queries; this immediately refreshes the display in the > data source browser. After that the Mail Merge Wizard can be called up > by using the corresponding button. > > > Data source of current document > > Click on the *Data Source of Current Document*button to open a direct > view ofthe table which forms the basis for the data inserted into the > document. In the above example, the Persontable from the Addresses > database/appears/. > > I get a refreshment when I right click a query or table in the Data > Source window, but what that got to do with the Mail Merge Wizard? What > is the corresponding button? > > The Data Source of Current Document button is a mystery to me. Am I > suppose to be in Writer when I do this? This button is only suppose to > be available for use when it Writer or Calc. There is some missing > information here. I have not used Mail Merge since before 2008, so I am > very rusty here. > > Dan > > > > -- > To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org > Problems? > https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ > Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette > List archive: https://listarchives.libreoffice.org/global/documentation/ > Privacy Policy: https://www.documentfoundation.org/privacy > -- To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/documentation/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-documentation] Base Documentation
Thanks! That the method I always use. On Fri, 27 Mar 2020 at 22:36 Pulkit Krishna wrote: > The method described in contributors guide in which portion of the chapter > are copied to the main book except copyright and contents. > > On 27 Mar 2020 4:53 p.m., "Jean Weber" wrote: > >> What is the “stacking method”? I’m not familiar with that term. >> Jean >> >> On Fri, 27 Mar 2020 at 20:00 Pulkit Krishna >> wrote: >> >>> Hell Everybody, >>> Chapter 10 has been placed in the published folder. >>> >>> Jean and Oliver: I think we should use the stacking method for preparing >>> the full book of base guide 6.2 as there would be need for much work to >>> be >>> done on each chapter like:- >>> 1) Putting the contents and copyright in sections. >>> 2) Anchoring all the images to paragraph instead of as character. >>> 3) Making sure that all the chapter have the copyright and contents >>> section >>> set to become invisible in full book by using a condition and declaring a >>> variable in the master document. >>> >>> So I think we should use the stacking method for version 6.2. in version >>> 6.4 we will take care of these things from begining and use the master >>> document. >>> >>> Pulkit Krishna >>> >>> -- To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/documentation/ Privacy Policy: https://www.documentfoundation.org/privacy
[libreoffice-documentation] Doc Team Meeting Minutes of MARCH 12th 2020
Dave Barton kindly reminded me to publish the minutes) THURSDAY March 12th 2020, 18:00 UTC Presents: Drew Jensen, Dave Barton, Olivier Note: Dave had issues with microphone Discussion Olivier:"Guides Translatablility" - Guides are considered references in LO literature + Much appreciated by L10n communities + Serve as reference for training + Also migration consulting job + Many How-tos for newbies, + Soon to close the published/release - Issues + Guides are written in English with "pure LibreOffice" and ODT format + Changes between release can trigger high volume of retranslation + Computer Aided Translation (CAT) is a stand-alone tool - work on files + can share translation memory (TM) but work "per file" + Depends on desktop, no shared work, until finished + TM helps, but nevertheless, translator must approve each suggestion + CAT tools hides XML gribberish, good, but XML ch graphics and concepts are presentaitons images such digital photos Drew: Recovering illness + Base context, usage of word "Link": + ="Join" in a SQL statement + ="relation" when connecting 2 tables in a RDB + ="link" when creating a form (in Base context). Next meeting THURSDAY MArch 26th 2020 18:00 UTC -- Olivier Hallot LibreOffice Documentation Coordinator Comunidade LibreOffice Rio de Janeiro - Brasil - Local Time: UTC-03:00 http://tdf.io/joinus -- To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/documentation/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-documentation] Writing techniques
Hello, Sorry to butt in after being absent so long, but I'm worried about these proposed rules. I agree with rules to keep sentences and paragraphs short, breaking up long sentences and paragraphs when possible. On the other hand, I'm uneasy about rules like Peter's (1) and (2) stipulating maximum numbers of words or sentences. If the numbers are intended as rules of thumb, they should be rewritten to reflect this. If they are meant to be hard limits, it's easy to imagine situations where following such a rule could make the result harder to understand. Second, I struggle to see how rules (3-5) would make translation easier, or whether this is a good reason to implement them. Regarding (4), if a translator's command of English is so poor that they cannot understand common contractions, it seems doubtful that using one-to-one replacements would make all the difference. Regarding (5), if anything I think Latin abbreviations should be avoided for the sake of readers of the English version, for maximum accessibility. It appears from the wiki history that this provision was already in the style guide. Finally, regarding (3), genitive possessives are such a basic component of English grammar that I worry that circumlocutions would harm readability to an unacceptable degree, even if this improves ease of translation. No examples are given, so I don't know what is intended. There are examples of cases to avoid possessive pronouns already in the style guide, but these are not contexts in which a full noun (phrase) would be used. I think I understand the background that Peter is coming from, but I think this issue requires more discussion. --Kenneth On Fri, Mar 27, 2020 at 6:59 AM Peter Schofield wrote: > Hello Olivier > > Definitely no objections from me. Hopefully, we will then get a standard > English appearing across all the guides. > > Regards > Peter Schofield > psaut...@gmail.com > > > > > On 27 Mar 2020, at 12:32, Olivier Hallot > wrote: > > > > Hello All > > > > If no objection rises, I'll merge the suggestions in the wiki page. > > > > Kind regards > > Olivier > > > > Em 27/03/2020 07:28, Peter Schofield escreveu: > >> Hello Ilmari > >> > >> The Style Guide does not cover all my suggestions, mainly use of > apostrophe and word contractions. These two items do cause problems when > translating English. > >> My ideas about paragraphs and sentences are similar to the Style Guide, > but I have put a number in the requirement. This does help if writers > follow the suggestion. > >> Regards > >> Peter Schofield > >> psaut...@gmail.com > >> > >> > >> > >>> On 27 Mar 2020, at 10:11, Ilmari Lauhakangas < > ilmari.lauhakan...@libreoffice.org> wrote: > >>> > >>> Peter Schofield kirjoitti 27.3.2020 klo 10.23: > After going through the meeting notes (which I could not attend), I > though that it maybe a good idea to air my views about writing standards. > The following ideas come from my experience in working within > Simplified English rules when I worked for Airbus and Ericcson. > 1. Paragraphs no more the six sentences long. > 2. Sentences should only contain a maximum of 20 words, with the > occasional sentence allowed to be 25 words. > 3. Never use the possessive apostrophe (for example Peter’s). Rewrite > the sentence to remove the need for a possessive apostrophe. > 4. Never use contractions of words (for example: don’t becomes do > not; won’t becomes will not, and so on) > 5. Never use Latin abbreviations (for example: etc becomes and so on; > e.g. becomes for example; i.e. becomes that is). > There are many more rules, but the above basic rules are a good > start. They are designed to make English text easier to translate into > other languages and that is why it is called Simplified English. > Please let me know your opinion. > >>> > >>> There is a style guide in the wiki: > https://wiki.documentfoundation.org/Documentation/DocumentationTeamInfo/StyleGuide > >>> > >>> Ilmari > >>> > >>> -- > >>> To unsubscribe e-mail to: > documentation+unsubscr...@global.libreoffice.org > >>> Problems? > https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ > >>> Posting guidelines + more: > https://wiki.documentfoundation.org/Netiquette > >>> List archive: > https://listarchives.libreoffice.org/global/documentation/ > >>> Privacy Policy: https://www.documentfoundation.org/privacy > >> > >> > > > > -- > > Olivier Hallot > > LibreOffice Documentation Coordinator > > Comunidade LibreOffice > > Rio de Janeiro - Brasil - Local Time: UTC-03:00 > > http://tdf.io/joinus > > > > -- > > To unsubscribe e-mail to: > documentation+unsubscr...@global.libreoffice.org > > Problems? > https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ > > Posting guidelines + more: > https://wiki.documentfoundation.org/Netiquette > > List archive: https://listarchives.libreoffice.org/global/documentation/ > > Privacy Policy:
Re: [libreoffice-documentation] Writing techniques
Hi Peter, all I merged your suggestions to the Style wiki page/chapter: https://wiki.documentfoundation.org/Documentation/DocumentationTeamInfo/StyleGuide#Writing_style The 5th item was already mentioned (Latin abbreviations) Regards Olivier Em 27/03/2020 08:59, Peter Schofield escreveu: > Hello Olivier > > Definitely no objections from me. Hopefully, we will then get a standard > English appearing across all the guides. > > Regards > Peter Schofield > psaut...@gmail.com > > > >> On 27 Mar 2020, at 12:32, Olivier Hallot >> wrote: >> >> Hello All >> >> If no objection rises, I'll merge the suggestions in the wiki page. >> >> Kind regards >> Olivier >> >> Em 27/03/2020 07:28, Peter Schofield escreveu: >>> Hello Ilmari >>> >>> The Style Guide does not cover all my suggestions, mainly use of apostrophe >>> and word contractions. These two items do cause problems when translating >>> English. >>> My ideas about paragraphs and sentences are similar to the Style Guide, but >>> I have put a number in the requirement. This does help if writers follow >>> the suggestion. >>> Regards >>> Peter Schofield >>> psaut...@gmail.com >>> >>> >>> On 27 Mar 2020, at 10:11, Ilmari Lauhakangas wrote: Peter Schofield kirjoitti 27.3.2020 klo 10.23: > After going through the meeting notes (which I could not attend), I > though that it maybe a good idea to air my views about writing standards. > The following ideas come from my experience in working within Simplified > English rules when I worked for Airbus and Ericcson. > 1. Paragraphs no more the six sentences long. > 2. Sentences should only contain a maximum of 20 words, with the > occasional sentence allowed to be 25 words. > 3. Never use the possessive apostrophe (for example Peter’s). Rewrite the > sentence to remove the need for a possessive apostrophe. > 4. Never use contractions of words (for example: don’t becomes do not; > won’t becomes will not, and so on) > 5. Never use Latin abbreviations (for example: etc becomes and so on; > e.g. becomes for example; i.e. becomes that is). > There are many more rules, but the above basic rules are a good start. > They are designed to make English text easier to translate into other > languages and that is why it is called Simplified English. > Please let me know your opinion. There is a style guide in the wiki: https://wiki.documentfoundation.org/Documentation/DocumentationTeamInfo/StyleGuide Ilmari -- To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/documentation/ Privacy Policy: https://www.documentfoundation.org/privacy >>> >>> >> >> -- >> Olivier Hallot >> LibreOffice Documentation Coordinator >> Comunidade LibreOffice >> Rio de Janeiro - Brasil - Local Time: UTC-03:00 >> http://tdf.io/joinus >> >> -- >> To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org >> Problems? >> https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ >> Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette >> List archive: https://listarchives.libreoffice.org/global/documentation/ >> Privacy Policy: https://www.documentfoundation.org/privacy > > -- Olivier Hallot LibreOffice Documentation Coordinator Comunidade LibreOffice Rio de Janeiro - Brasil - Local Time: UTC-03:00 http://tdf.io/joinus -- To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/documentation/ Privacy Policy: https://www.documentfoundation.org/privacy
[libreoffice-documentation] Re: Question about BG6207.
On 3/27/20 11:24, Dan Lewis wrote: The row chosen for the table heading can be taken from the column names, or the record may be written out with space left for the headings to be edited in later. This paragraph is found on page 7, 3 paragraphs below Figure 5. I have no idea of how I can review this as I have no idea how to do this. Dan Then on pages 9 & 10: To launch the database, right-click on the database itself or on one of its tables or queries; this immediately refreshes the display in the data source browser. After that the Mail Merge Wizard can be called up by using the corresponding button. Data source of current document Click on the *Data Source of Current Document*button to open a direct view ofthe table which forms the basis for the data inserted into the document. In the above example, the Persontable from the Addresses database/appears/. I get a refreshment when I right click a query or table in the Data Source window, but what that got to do with the Mail Merge Wizard? What is the corresponding button? The Data Source of Current Document button is a mystery to me. Am I suppose to be in Writer when I do this? This button is only suppose to be available for use when it Writer or Calc. There is some missing information here. I have not used Mail Merge since before 2008, so I am very rusty here. Dan -- To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/documentation/ Privacy Policy: https://www.documentfoundation.org/privacy
[libreoffice-documentation] Question about BG6207.
The row chosen for the table heading can be taken from the column names, or the record may be written out with space left for the headings to be edited in later. This paragraph is found on page 7, 3 paragraphs below Figure 5. I have no idea of how I can review this as I have no idea how to do this. Dan -- To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/documentation/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-documentation] Writing techniques
Hello Olivier Definitely no objections from me. Hopefully, we will then get a standard English appearing across all the guides. Regards Peter Schofield psaut...@gmail.com > On 27 Mar 2020, at 12:32, Olivier Hallot > wrote: > > Hello All > > If no objection rises, I'll merge the suggestions in the wiki page. > > Kind regards > Olivier > > Em 27/03/2020 07:28, Peter Schofield escreveu: >> Hello Ilmari >> >> The Style Guide does not cover all my suggestions, mainly use of apostrophe >> and word contractions. These two items do cause problems when translating >> English. >> My ideas about paragraphs and sentences are similar to the Style Guide, but >> I have put a number in the requirement. This does help if writers follow the >> suggestion. >> Regards >> Peter Schofield >> psaut...@gmail.com >> >> >> >>> On 27 Mar 2020, at 10:11, Ilmari Lauhakangas >>> wrote: >>> >>> Peter Schofield kirjoitti 27.3.2020 klo 10.23: After going through the meeting notes (which I could not attend), I though that it maybe a good idea to air my views about writing standards. The following ideas come from my experience in working within Simplified English rules when I worked for Airbus and Ericcson. 1. Paragraphs no more the six sentences long. 2. Sentences should only contain a maximum of 20 words, with the occasional sentence allowed to be 25 words. 3. Never use the possessive apostrophe (for example Peter’s). Rewrite the sentence to remove the need for a possessive apostrophe. 4. Never use contractions of words (for example: don’t becomes do not; won’t becomes will not, and so on) 5. Never use Latin abbreviations (for example: etc becomes and so on; e.g. becomes for example; i.e. becomes that is). There are many more rules, but the above basic rules are a good start. They are designed to make English text easier to translate into other languages and that is why it is called Simplified English. Please let me know your opinion. >>> >>> There is a style guide in the wiki: >>> https://wiki.documentfoundation.org/Documentation/DocumentationTeamInfo/StyleGuide >>> >>> Ilmari >>> >>> -- >>> To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org >>> Problems? >>> https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ >>> Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette >>> List archive: https://listarchives.libreoffice.org/global/documentation/ >>> Privacy Policy: https://www.documentfoundation.org/privacy >> >> > > -- > Olivier Hallot > LibreOffice Documentation Coordinator > Comunidade LibreOffice > Rio de Janeiro - Brasil - Local Time: UTC-03:00 > http://tdf.io/joinus > > -- > To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org > Problems? > https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ > Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette > List archive: https://listarchives.libreoffice.org/global/documentation/ > Privacy Policy: https://www.documentfoundation.org/privacy -- To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/documentation/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-documentation] Writing techniques
Hello Bernard The use of “never” is deliberate as it does make it easier to translate English. Also, using the “Never” items in a document does make it harder for a user whose mother tongue is not English to understand what is meant. I have had experience of this. I have not heard of George Miller, but will now look him up. Regards Peter Schofield psaut...@gmail.com > On 27 Mar 2020, at 12:49, Poole, Bernard J wrote: > > I like these rules, Peter, with one question mark: Should the word "Never" be > replaced by the word "Rarely?" > > I'm thinking especially of Rule 3 where the possessive apostrophe is > sometimes hard to work around without making a sentence unnecessarily > awkward. I think there should be exceptions allowed for this rule, don't you > think? > > Essentially, Peter, your ideas here echo those of George Miller (1956), with > whom you are no doubt already aware: > > https://www.informationmapping.com/in/resources/blog/writing-for-the-web-the-magical-number-seven-plus-or-minus-two > > I wrote a paper related to this subject as it pertains to Software > Engineering: > > Poole, Bernard J., Noreen L. Prokop, "Miller's Magical Number: A Heuristic > Applied to Software Engineering," in > INFORMATION EXECUTIVE, Journal of the Data Processing Management Association, > June 1989. > > I'd love to know your thoughts on this. > > Bernard > > Bernard John Poole, MSIS, PGCE > Associate Professor Emeritus CS & Education > University of Pittsburgh at Johnstown > Johnstown, PA 15904, USA > e-mail: po...@pitt.edu > home page: www.pitt.edu/~poole > > “This is my simple religion. There is no need for temples; no need for > complicated philosophy. Our own brain, our own heart is our temple. The > philosophy is kindness.” (The Dalai Lama) > > > From: Peter Schofield > Sent: Friday, March 27, 2020 4:23 AM > To: LibreOffice > Subject: [libreoffice-documentation] Writing techniques > > After going through the meeting notes (which I could not attend), I though > that it maybe a good idea to air my views about writing standards. > > The following ideas come from my experience in working within Simplified > English rules when I worked for Airbus and Ericcson. > > 1. Paragraphs no more the six sentences long. > 2. Sentences should only contain a maximum of 20 words, with the occasional > sentence allowed to be 25 words. > 3. Never use the possessive apostrophe (for example Peter’s). Rewrite the > sentence to remove the need for a possessive apostrophe. > 4. Never use contractions of words (for example: don’t becomes do not; won’t > becomes will not, and so on) > 5. Never use Latin abbreviations (for example: etc becomes and so on; e.g. > becomes for example; i.e. becomes that is). > > There are many more rules, but the above basic rules are a good start. They > are designed to make English text easier to translate into other languages > and that is why it is called Simplified English. > > Please let me know your opinion. > > Regards > Peter Schofield > psaut...@gmail.com > > > > > -- > To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org > Problems? > https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.libreoffice.org%2Fget-help%2Fmailing-lists%2Fhow-to-unsubscribe%2Fdata=02%7C01%7Cpoole%40pitt.edu%7C1413db2756b74c92e1be08d7d2283990%7C9ef9f489e0a04eeb87cc3a526112fd0d%7C1%7C1%7C637208942524998701sdata=%2BX0NlagMob1VRV5MH6v0bFLmLGQ1cxYm2EjUCvuUOLM%3Dreserved=0 > Posting guidelines + more: > https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.documentfoundation.org%2FNetiquettedata=02%7C01%7Cpoole%40pitt.edu%7C1413db2756b74c92e1be08d7d2283990%7C9ef9f489e0a04eeb87cc3a526112fd0d%7C1%7C1%7C637208942524998701sdata=GlGKJzamKk5UkG7cntot4eJUEc%2Fq%2B5i7w29HqJYBdTA%3Dreserved=0 > List archive: > https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Flistarchives.libreoffice.org%2Fglobal%2Fdocumentation%2Fdata=02%7C01%7Cpoole%40pitt.edu%7C1413db2756b74c92e1be08d7d2283990%7C9ef9f489e0a04eeb87cc3a526112fd0d%7C1%7C1%7C637208942524998701sdata=0NhzhWQP3FkgFwfEnqHzxAoY2bYvMbJQesGlUxZW4s0%3Dreserved=0 > Privacy Policy: > https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.documentfoundation.org%2Fprivacydata=02%7C01%7Cpoole%40pitt.edu%7C1413db2756b74c92e1be08d7d2283990%7C9ef9f489e0a04eeb87cc3a526112fd0d%7C1%7C1%7C637208942524998701sdata=AFo52hCEGSMQam%2BOt%2BUMrYoIhMF3aukqSNq84QCj4wc%3Dreserved=0 -- To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/documentation/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-documentation] Writing techniques
Hello All If no objection rises, I'll merge the suggestions in the wiki page. Kind regards Olivier Em 27/03/2020 07:28, Peter Schofield escreveu: > Hello Ilmari > > The Style Guide does not cover all my suggestions, mainly use of apostrophe > and word contractions. These two items do cause problems when translating > English. > My ideas about paragraphs and sentences are similar to the Style Guide, but I > have put a number in the requirement. This does help if writers follow the > suggestion. > Regards > Peter Schofield > psaut...@gmail.com > > > >> On 27 Mar 2020, at 10:11, Ilmari Lauhakangas >> wrote: >> >> Peter Schofield kirjoitti 27.3.2020 klo 10.23: >>> After going through the meeting notes (which I could not attend), I though >>> that it maybe a good idea to air my views about writing standards. >>> The following ideas come from my experience in working within Simplified >>> English rules when I worked for Airbus and Ericcson. >>> 1. Paragraphs no more the six sentences long. >>> 2. Sentences should only contain a maximum of 20 words, with the occasional >>> sentence allowed to be 25 words. >>> 3. Never use the possessive apostrophe (for example Peter’s). Rewrite the >>> sentence to remove the need for a possessive apostrophe. >>> 4. Never use contractions of words (for example: don’t becomes do not; >>> won’t becomes will not, and so on) >>> 5. Never use Latin abbreviations (for example: etc becomes and so on; e.g. >>> becomes for example; i.e. becomes that is). >>> There are many more rules, but the above basic rules are a good start. They >>> are designed to make English text easier to translate into other languages >>> and that is why it is called Simplified English. >>> Please let me know your opinion. >> >> There is a style guide in the wiki: >> https://wiki.documentfoundation.org/Documentation/DocumentationTeamInfo/StyleGuide >> >> Ilmari >> >> -- >> To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org >> Problems? >> https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ >> Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette >> List archive: https://listarchives.libreoffice.org/global/documentation/ >> Privacy Policy: https://www.documentfoundation.org/privacy > > -- Olivier Hallot LibreOffice Documentation Coordinator Comunidade LibreOffice Rio de Janeiro - Brasil - Local Time: UTC-03:00 http://tdf.io/joinus -- To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/documentation/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-documentation] Base Documentation
What is the “stacking method”? I’m not familiar with that term. Jean On Fri, 27 Mar 2020 at 20:00 Pulkit Krishna wrote: > Hell Everybody, > Chapter 10 has been placed in the published folder. > > Jean: > I have deleted the note as commented by you but the last paragraph about > incompatibility between HSQLDB and java is necessary because of two > reasons:- > > 1) We need to inform the users that the problem is no more. > 2) It is still true that external connections are faster than internal > HSQLDB. Even external HSQLDB is faster than its internal counterpart. > > Jean and Oliver: I think we should use the stacking method for preparing > the full book of base guide 6.2 as there would be need for much work to be > done on each chapter like:- > 1) Putting the contents and copyright in sections. > 2) Anchoring all the images to paragraph instead of as character. > 3) Making sure that all the chapter have the copyright and contents section > set to become invisible in full book by using a condition and declaring a > variable in the master document. > > So I think we should use the stacking method for version 6.2. in version > 6.4 we will take care of these things from begining and use the master > document. > > Pulkit Krishna > > -- To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/documentation/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-documentation] Writing techniques
Hello Leo I have plenty of tips I could share, but those were the easiest ones to put in a suggestion. The Simplified English guide I have used is the ASD-STE100 and that is a tome that takes ages to get through and digest. Too big to incorporate into a LibreOffice Style Guide. I need some spare time to edit and only use the good bits for a suggestion. I think later in the year when all the other jobs have been done whilst we are in lockdown Regards Peter Schofield psaut...@gmail.com > On 27 Mar 2020, at 11:24, Leo Moons wrote: > > Dear Peter, > > Thanks a lot for sharing your ideas and I am pretty sure we can use these > ideas also in other languages. Maybe you have more tips you can share? > > Many thanks > Best regards > > Leo Moons > LibreOffice/nl > > > Op 27/03/2020 om 09:23 schreef Peter Schofield: >> After going through the meeting notes (which I could not attend), I though >> that it maybe a good idea to air my views about writing standards. >> >> The following ideas come from my experience in working within Simplified >> English rules when I worked for Airbus and Ericcson. >> >> 1. Paragraphs no more the six sentences long. >> 2. Sentences should only contain a maximum of 20 words, with the occasional >> sentence allowed to be 25 words. >> 3. Never use the possessive apostrophe (for example Peter’s). Rewrite the >> sentence to remove the need for a possessive apostrophe. >> 4. Never use contractions of words (for example: don’t becomes do not; won’t >> becomes will not, and so on) >> 5. Never use Latin abbreviations (for example: etc becomes and so on; e.g. >> becomes for example; i.e. becomes that is). >> >> There are many more rules, but the above basic rules are a good start. They >> are designed to make English text easier to translate into other languages >> and that is why it is called Simplified English. >> >> Please let me know your opinion. >> >> Regards >> Peter Schofield >> psaut...@gmail.com >> >> >> >> > > > -- > To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org > Problems? > https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ > Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette > List archive: https://listarchives.libreoffice.org/global/documentation/ > Privacy Policy: https://www.documentfoundation.org/privacy -- To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/documentation/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-documentation] Writing techniques
Hello Ilmari The Style Guide does not cover all my suggestions, mainly use of apostrophe and word contractions. These two items do cause problems when translating English. My ideas about paragraphs and sentences are similar to the Style Guide, but I have put a number in the requirement. This does help if writers follow the suggestion. Regards Peter Schofield psaut...@gmail.com > On 27 Mar 2020, at 10:11, Ilmari Lauhakangas > wrote: > > Peter Schofield kirjoitti 27.3.2020 klo 10.23: >> After going through the meeting notes (which I could not attend), I though >> that it maybe a good idea to air my views about writing standards. >> The following ideas come from my experience in working within Simplified >> English rules when I worked for Airbus and Ericcson. >> 1. Paragraphs no more the six sentences long. >> 2. Sentences should only contain a maximum of 20 words, with the occasional >> sentence allowed to be 25 words. >> 3. Never use the possessive apostrophe (for example Peter’s). Rewrite the >> sentence to remove the need for a possessive apostrophe. >> 4. Never use contractions of words (for example: don’t becomes do not; won’t >> becomes will not, and so on) >> 5. Never use Latin abbreviations (for example: etc becomes and so on; e.g. >> becomes for example; i.e. becomes that is). >> There are many more rules, but the above basic rules are a good start. They >> are designed to make English text easier to translate into other languages >> and that is why it is called Simplified English. >> Please let me know your opinion. > > There is a style guide in the wiki: > https://wiki.documentfoundation.org/Documentation/DocumentationTeamInfo/StyleGuide > > Ilmari > > -- > To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org > Problems? > https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ > Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette > List archive: https://listarchives.libreoffice.org/global/documentation/ > Privacy Policy: https://www.documentfoundation.org/privacy -- To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/documentation/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-documentation] Writing techniques
Dear Peter, Thanks a lot for sharing your ideas and I am pretty sure we can use these ideas also in other languages. Maybe you have more tips you can share? Many thanks Best regards Leo Moons LibreOffice/nl Op 27/03/2020 om 09:23 schreef Peter Schofield: After going through the meeting notes (which I could not attend), I though that it maybe a good idea to air my views about writing standards. The following ideas come from my experience in working within Simplified English rules when I worked for Airbus and Ericcson. 1. Paragraphs no more the six sentences long. 2. Sentences should only contain a maximum of 20 words, with the occasional sentence allowed to be 25 words. 3. Never use the possessive apostrophe (for example Peter’s). Rewrite the sentence to remove the need for a possessive apostrophe. 4. Never use contractions of words (for example: don’t becomes do not; won’t becomes will not, and so on) 5. Never use Latin abbreviations (for example: etc becomes and so on; e.g. becomes for example; i.e. becomes that is). There are many more rules, but the above basic rules are a good start. They are designed to make English text easier to translate into other languages and that is why it is called Simplified English. Please let me know your opinion. Regards Peter Schofield psaut...@gmail.com -- To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/documentation/ Privacy Policy: https://www.documentfoundation.org/privacy
[libreoffice-documentation] Base Documentation
Hell Everybody, Chapter 10 has been placed in the published folder. Jean: I have deleted the note as commented by you but the last paragraph about incompatibility between HSQLDB and java is necessary because of two reasons:- 1) We need to inform the users that the problem is no more. 2) It is still true that external connections are faster than internal HSQLDB. Even external HSQLDB is faster than its internal counterpart. Jean and Oliver: I think we should use the stacking method for preparing the full book of base guide 6.2 as there would be need for much work to be done on each chapter like:- 1) Putting the contents and copyright in sections. 2) Anchoring all the images to paragraph instead of as character. 3) Making sure that all the chapter have the copyright and contents section set to become invisible in full book by using a condition and declaring a variable in the master document. So I think we should use the stacking method for version 6.2. in version 6.4 we will take care of these things from begining and use the master document. Pulkit Krishna -- To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/documentation/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-documentation] Writing techniques
Peter Schofield kirjoitti 27.3.2020 klo 10.23: After going through the meeting notes (which I could not attend), I though that it maybe a good idea to air my views about writing standards. The following ideas come from my experience in working within Simplified English rules when I worked for Airbus and Ericcson. 1. Paragraphs no more the six sentences long. 2. Sentences should only contain a maximum of 20 words, with the occasional sentence allowed to be 25 words. 3. Never use the possessive apostrophe (for example Peter’s). Rewrite the sentence to remove the need for a possessive apostrophe. 4. Never use contractions of words (for example: don’t becomes do not; won’t becomes will not, and so on) 5. Never use Latin abbreviations (for example: etc becomes and so on; e.g. becomes for example; i.e. becomes that is). There are many more rules, but the above basic rules are a good start. They are designed to make English text easier to translate into other languages and that is why it is called Simplified English. Please let me know your opinion. There is a style guide in the wiki: https://wiki.documentfoundation.org/Documentation/DocumentationTeamInfo/StyleGuide Ilmari -- To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/documentation/ Privacy Policy: https://www.documentfoundation.org/privacy
[libreoffice-documentation] Writing techniques
After going through the meeting notes (which I could not attend), I though that it maybe a good idea to air my views about writing standards. The following ideas come from my experience in working within Simplified English rules when I worked for Airbus and Ericcson. 1. Paragraphs no more the six sentences long. 2. Sentences should only contain a maximum of 20 words, with the occasional sentence allowed to be 25 words. 3. Never use the possessive apostrophe (for example Peter’s). Rewrite the sentence to remove the need for a possessive apostrophe. 4. Never use contractions of words (for example: don’t becomes do not; won’t becomes will not, and so on) 5. Never use Latin abbreviations (for example: etc becomes and so on; e.g. becomes for example; i.e. becomes that is). There are many more rules, but the above basic rules are a good start. They are designed to make English text easier to translate into other languages and that is why it is called Simplified English. Please let me know your opinion. Regards Peter Schofield psaut...@gmail.com -- To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/documentation/ Privacy Policy: https://www.documentfoundation.org/privacy
[libreoffice-documentation] Getting started with Writer
I have taken chapter one of the Writer Guide for a first review. Kees -- To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/documentation/ Privacy Policy: https://www.documentfoundation.org/privacy
