Hello Olivier
One book template will be created based on the chapter template. It will have dummy front and rear covers with a dummy preface included. Instructions will be added in comments to replace the covers and amend the preface for the correct user guide.
Page styles will be added for the covers - front right page only - rear left page only.
It will take a few days before a draft appears on NextCloud.
Regards
Peter Schofield
Technical Writer, LO Documentation Team
psauthor@gmail.com
Peter and Olivier,
I may have missed discussion of this point, so you may be doing it already: If we’re using master documents to compile our books, the book template should be a master doc template, not an ordinary template.
Jean
Hello Jean and Olivier
I have made a start on a template for the complete user guide. Hope to have first draft by middle of next week.
It is a very long time since I worked with master documents (about 30 years). However, I will investigate LO Master Documents and see what has to be done to create a template.
Regards
Peter Schofield
psauthor@gmail.com
Technical Writer, LO Documentation Team
Hello Peter,
Master document templates are new. As far as I can tell, for our guides the steps to create one starting with the chapter template are (1) create the book template (OTT) as you have been doing, (2) create a new ODT (book file) from that template, (3) create a master document (ODM) from the ODT [File > Send > Create Master Document], (4) save the ODM as a master doc template (0TM).
Jean
Hello Jean
Thanks for the info. I shall have a go, probably at the weekend. It is a long time since I have worked with master documents.
Regards
Peter Schofield
psauthor@gmail.com
Technical Writer, LO Documentation Team
Hi Peter
Please have a look at the published Calc Guide 7.4 as it was built based on a master document. The master document is CG74-CalcGuide.odm. It was based on the LO chapter template available in the same folder.
I think you just need to open the master, drop the links to the chapters, apply your latest changes of the chapter templates (if necessary), and save the master as template.
If I’m not mistaken, you get the covers styles (where images are in the background), the book TOC already set and the copyright beef.
Cheers
Olivier
First, sorry for the lousy English (Google translate) my English is even worse
Suggestions for character styles:
The keystroke and code Character Styles in the template have a size of 11 or 10 points, so they do not apply correctly to paragraph styles that do not have that size. (Titles, Table Content etc.)
To create a character style that fits the size of any paragraph style, the character style “without character style” should be taken as a model.
Although the font size of the style looks like 12 point, it is an approximation relative to the font size of the “Default Paragraph” style.
This property must not be modified at any time if we want it to adapt to any font size of a paragraph style. You can change the highlighting, Bold, Italics, Font Color etc. Any property can be changed at any time, without affecting the suitability of the paragraph to which it is applied except for the size.
if you change the size (from the relative 12pt) to another size, and later want to revert, the size will no longer adapt to other paragraph styles. Therefore the related styles must be created again.
1.-Rename the old Keystroke stile, for example Keystroke_old (the name of the applied styles will be have that name),
2.- Create a new Keystroke style that will not be resized but italicized
3.- Use find and replace to replace all “Keystroke_old” styles with the new “Keystroke”.
The “Liberation Mono” font, despite being from the same Liberation family,
it is slightly larger than “Liberation Sans” (alters the paragraph spacing) and has a fairly expanded kerning, my suggestion is to use “DejaVu Sans Mono” in Code styles whose kerning is better suited
Hello Antonio
The idea of character styles is to make them more prominent in a paragraph for LO users to notice the words and what they are for. I am not sure what you mean with your message, but I find the present character styles OK and understand what they are for.
The Code character style matches the Code paragraph style. That is the reason for using 10pt. This allows for more characters to fit on one line in the paragraph style to help prevent long lines of code of line breaking.
The Keystroke character style uses the Liberation Mono font so it stands out for keyboard shortcuts.
Character styles are only used in the body of the text. Also, they are not used in titles or headings and will not appear in the Table of Contents.
Regards
Peter Schofield
psauthor@gmail.com
Technical Writer, LO Documentation Team
Hello
I am sending this email only to you so as not to fill the post with comments.
To show the reason for the modifications that I think are necessary, I have created a template and uploaded it to the Nextcloud Contributors Resources folder. (Proposed_modification_Chapter_Template-7.4.ott)
-It is a copy of the template LO-UG-Chapter-Template-7-4.ott
-I have inserted a page at the beginning as an example
-I just created a new style (Keystroke_New) I have not made any more modifications
Hello
Will look at your suggestions when I return from my holiday, which will be on 18 November 2022.
Regards
Regards
Peter Schofield
Technical Writer, LO Documentation Team
Hello Antonio
With paragraph styles having different font sizes and text colouring, using a character style in a paragraph will help to emphasise a word, for example keystroke. A character style only changes the emphasis (bold or italic), or the font (Liberation Mono), or both emphasis and font and does not change font size.
It is recommended to not use a character style in a heading paragraph style, but to reword the heading so there is no need to use a character style.
Liberation Mono is installed with LibreOffice. This means that will not be any font problem when an LO document is opened on another computer.
It is recommended not to use Caution or Warning in a software user guide.
A Caution is used to give notice that there is a possible risk of damage and slight risk of injury if something is not done correctly.
A Warning is used when there is a high risk of injury and danger to life or a high risk of damage if something is not done correctly.
An LO user guide is a software user guide and there is only a need for Notes and Tips to be used.
Peter Schofield
psauthor@gmail.com
Technical Writer, LO Documentation Team
sorry again for my bad english
– With paragraph styles having different font sizes and text colouring, using a character style in a paragraph will help to emphasize a word,…
I already knew that… But if you change the font size of a character style, it does NOT adjust to the font size of the paragraph style
– It is recommended not to use Caution or Warning in a software user guide…
The modified template is not going to be part of any guide, I have used it to warn whoever created the styles (I don’t know if it was you), and I think it is important enough because it damages the document layout.
– It is recommended to not use a character style in a heading paragraph style,
I also knew, the paragraph styles to which I have applied the character styles are just examples of how the current character style (KeyStroke, which does NOT adjust) and the one created as an example (Keystroke_New which adjust perfectly ).
– Liberation Mono is installed with LibreOffice. This means that there will not be any font problem when an LO document is opened on another computer.
The DejaVu font family is also installed with LibreOffice, at least in version 7.3 it is included in the installer
Hello Antonio
After a little testing using several computer displays I have come to the conclusion that there is no need to change the font for the character style Keystroke. The definition quality of a computer display and the zoom factor used for LibreOffice do affect what is displayed and what an LO user sees. There are subtle differences between DejaVu Sana Mono and Liberation Mono, but not enough to change the Keystroke character style in the chapter template.
Maybe you did not understand my explanation about a Caution. There is no risk of damage or injury when us LibreOffice software to create documents. Therefore, using a Caution is not required. There is only a need for Notes and Tips is a software user guide.
Hope that helps.
No need to apologise for your English. It is good. Not 100%, but good. Even my English is not perfect and I am native speaker.
Regards
Peter Schofield
psauthor@gmail.com
Technical Writer, LO Documentation Team
Hello Peter
I see that you have not understood my suggestions, it is possible that I do not explain it well so I will try to be more concise and please read it carefully.
1.- The suggestion for the use of DejaVu Sans Mono is for the CODE character styles and their derivatives, (Literal, Number, String … ). This font has tighter kerning and is thicker, so at small sizes it is more readable. It was the font that LibreOffice put by default in the macro editor in previous versions. -This is just a suggestion.
2.- The font used for KeyStroke is correct, (but not the size)
When defining the character style KeyStroke, the font size has been changed and has been set at 11 points (a fixed font size has been created).
The size created by default is relative to the size of the default paragraph style, normally 12 points and This size should NOT be changed, although other attributes can be changed (color, highlighting etc.) – The size created by default is not really 12 points, it has no size (the size of the letter used in the default paragraph style is displayed, but no size is defined)
When changing the size of the font, it will have a fixed size. For example, if the size of Keystroke is changed to 11 points,
when applying the character style to a word in a paragraph of 18 points, the text will have a size of 18 points in everything except the word that has the Keystroke character style, which will be 11 points.
If the size of the character style is not touched, that size will not be defined, so it adapts to any paragraph style,
In the previous example, all, absolutely all the text of the paragraph will have a size of 18 points and the word in which the Keystroke character style has been applied will have the defined attributes, but the font size of the entire paragraph will be 18 points.
If at any time the font size for Keystroke is changed, and later you want it to adapt to any paragraph style, the logical thing would be to change its size back to 12 points (or the font size of the Default paragraph style), This is not possible, because the font size has already been converted to fixed and when applying it in the 18 point paragraph, it will not adapt.
The whole paragraph will have a size of 18 points except the word with the keystroke character style, which will now be 12 points.
The solution is to create the Keystroke style again and not touch its size.
3- in the Code character style the font size has also been changed and it does not adapt as it sould be either.
Finally
I disagree with your assertion about Caution notices in software user guides, that “It is recommended not to use” them. Recommended by whom? They are often used to indicate potential loss or corruption of data.
Jean
I agree with Antonio’s comments about character styles. They should not have a font size defined, for the reasons given. The problem described is most noticeable to me in tables but occurs elsewhere too.
Jean
I understand this comment suggests applying the size to the Code paragraph style and not the Character style. Code font size has deliberately been set to allow 80 characters on a line as a reasonable compromise for most code.
The suggestion about changing the current font type (Liberation Mono) to DejaVu Sans Mono in Code styles Obviously refers to both the Code paragraph style and the Code character style.
Other than this suggestion I think this should be corrected.:
1- The Code character style has the same problem as the KeyStroke character style: It doesn’t scale to the font sizes of the paragraph styles because it is set to a fixed size of 10 points.
Note that the character style is also applied to paragraphs with a style other than code.
2- The character styles for syntax highlighting in macros (ch2_LibreOffice_Operator etc.) have the same problem because they inherit from the Ch2_LibreOffice style and Ch2_LibreOffice inherits from Code.
To resolve this issue in documents with Code character styles already applied:
– To change the already applied Code character style (Old_Code) in other non-macro paragraphs (Text Body etc.) Use the Find and Replace tool and replace all occurrences of the Old_Code style with the new Code style
– To change the styles on the text relative to the macros without having to change all the applied highlighting styles, the easiest solution is:
Modify the ch2_LibreOffice character style in the Organizer tab to inherit the new Code style.
All styles with syntax highlighting will seamlessly adapt to the paragraph style where they are applied.
Finaly remove te Old_Code character style when not be in use.
Code font size has deliberately been set to allow 80 characters on a line as a reasonable compromise for most code.
To present the 80 characters per line, the code paragraph style must be used, set to the appropriate font size (may be 10 pt).
When applying the character styles they will adapt if they are well defined.
Note:
Hello Antonio
The Code paragraph style is Liberation Mono and font size is 10pt. This allows for a line length of 80 characters, which is
Regards
Peter Schofield
psauthor@gmail.com
Technical Writer, LO Documentation Team