Re: [libreoffice-users] Presentation - video record
On 6/16/2020 2:14 PM, charles meyer wrote: I'm trying to coordinate a presentation with Libre Presentation. Can Presentation record screens on your laptop like MS Power Point? If so, could you please share those steps? Thank you. Charles. I don't think Presentation can do it natively. I use free third party programs to accomplish this. In Windows, I use a free program called ShareX, which works just fine. You can also do it through Zoom and include your own picture in a corner of the screen through its screen share feature. In Linux, I use Kazam. Virgil -- To unsubscribe e-mail to: users+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/users/ Privacy Policy: https://www.documentfoundation.org/privacy
[libreoffice-users] Presentation - video record
I'm trying to coordinate a presentation with Libre Presentation. Can Presentation record screens on your laptop like MS Power Point? If so, could you please share those steps? Thank you. Charles. -- To unsubscribe e-mail to: users+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/users/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-users] Compatibility with markdown
On 2020/06/16 00:31, H wrote: > Were you thinking of https://github.com/abcBHM/MD2odt or perhaps of > https://github.com/DjebbZ/markdown-to-odt? The latter seems to be one-way > only though. Neither project has been updated for a while and it seems as if > they can both be forked? Neither of them look right. jonathon -- To unsubscribe e-mail to: users+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/users/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-users] Document hierarchy and Indexing [as applied to LO Guides]
On 6/16/2020 3:54 AM, John Kaufmann wrote: Hi Robert, On 2020-06-16 03:38, Robert Großkopf wrote: ... newbies will create all content in one document. So it is no problem to set Level 1 ~ Heading 1 Level 2 ~ Heading 2 Level 3 ~ Heading 3 But if there are separate document for each chapter of a guide you couldn't get a well formed Master Document for a guide. Heading 1 must be there in Level 2 and the Title of the separate Documents must be in Level 1. Hope the global documents have been created the same way, as, for example, the German Base Handbuch. Thanks for that. I knew there must be something I was not seeing, and will consider the implications of Master Document construction. (Will post again when I have thought it through.) In any case, though, shouldn't the same construction logic apply to all LO Guides? Regards, John This thread reminds me that LO's greatest advantage is that the user has complete control over everything... And LO's greatest drawback is that the user has complete control over everything... Virgil -- To unsubscribe e-mail to: users+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/users/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-users] Document hierarchy and Indexing [as applied to LO Guides]
Hi Robert, On 2020-06-16 03:38, Robert Großkopf wrote: ... newbies will create all content in one document. So it is no problem to set Level 1 ~ Heading 1 Level 2 ~ Heading 2 Level 3 ~ Heading 3 But if there are separate document for each chapter of a guide you couldn't get a well formed Master Document for a guide. Heading 1 must be there in Level 2 and the Title of the separate Documents must be in Level 1. Hope the global documents have been created the same way, as, for example, the German Base Handbuch. Thanks for that. I knew there must be something I was not seeing, and will consider the implications of Master Document construction. (Will post again when I have thought it through.) In any case, though, shouldn't the same construction logic apply to all LO Guides? Regards, John -- To unsubscribe e-mail to: users+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/users/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-users] Document hierarchy and Indexing [as applied to LO Guides]
Hi John, newbies will create all content in one document. So it is no problem to set Level 1 ~ Heading 1 Level 2 ~ Heading 2 Level 3 ~ Heading 3 But if there are separate document for each chapter of a guide you couldn't get a well formed Master Document for a guide. Heading 1 must be there in Level 2 and the Title of the separate Documents must be in Level 1. Hope the global documents have been created the same way, as, for example, the German Base Handbuch. Regards Robert -- Homepage: https://www.familiegrosskopf.de/robert -- To unsubscribe e-mail to: users+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/users/ Privacy Policy: https://www.documentfoundation.org/privacy
[libreoffice-users] Document hierarchy and Indexing [as applied to LO Guides]
A confusing difference in presentation models between some LO Guides
(Calc, GettingStarted) -- call these "Group A"
and others:
(Base, Draw, Impress, Writer[*w*]) -- "Group B"
prompts:
(1) A look at the different ways the hierarchical styles are handled,
and
(2) A question (concluding, below) about Writer's default styles.
(1) LO Guides hierarchical styles
=
All LO Guides use style "Title" for Chapter titles, but only group B assigns
"Title" as Outline (hierarchy) Level 1, with subsequent Heading 1, etc, demoted from
Writer's default; that is:
Level 1 ~ Title
Level 2 ~ Heading 1
Level 3 ~ Heading 2
Level 4 ~ Heading 3 [and also Heading 4 - a potential hazard]
Group A accepts Writer's default Outline (hierarchy) assignments:
Level 1 ~ Heading 1
Level 2 ~ Heading 2
Level 3 ~ Heading 3
...
with style "Title" having no Outline role, assigned to hierarchical value "Text
body".
This means that, for group A, the Chapter titles /do not show up/ in the
Navigator view or in PDF Bookmarks, which make navigating those documents
tedious and somewhat bewildering. OTOH, for group B, the Navigator view and
corresponding PDF Bookmarks are fully hierarchical, making those documents much
easier to navigate.
([*w*] The Writer Guide is a special case: while fully hierarchical and thus
easy to navigate in theory, the bookmarks were not exported to the PDF file,
and so there are no PDF Bookmarks - a shame, but easily fixable from the
downloadable ODT file.)
However, group A and group B documents all have indexed Table of Contents
(ToC). The difference between their constructions is:
* Group A's ToC format is only two-level, using the option "Create from:
Additional Styles", assigning:
- "Title" (which has Outline value "Text body") to level 1 and
- "Heading 1" (which has Outline value "Level 1") to level 2.
But because of:
- the lack of level 1 in PDF bookmarks,
- the lack of sub-levels in the ToC, and
- the constant shifting of hierarchy levels between ToC and PDF
Bookmarks,
navigation of those documents is needlessly tiring and frustrating.
* Group B's ToC, OTOH, goes as deep as the document itself, and matches the Navigator and PDF
Bookmarks, because its ToC is indexed using the default "Create from: Outline" rather
than "Create from: Additional styles". Navigating those documents is easy.
This analysis, such as it is, seems to point to a preference; I like easy and consistent. However, in this case, the ease and consistency of Group B
come from /redefining Writer's default hierarchy style assignments/ for Levels 1..3 ("Heading 1", "Heading 2", "Header
3") -- defaults which themselves provide a simple consistency -- in order to put style "Title" at Outline Level 1. Moreover, that
approach does those hierarchy reassignments by disconnecting those styles from their normal "Heading" root style, and leaving both
"Header 3" and "Header 4" at Outline Level 4. So I'm not convinced that Group B's solution is a good answer, either.
Obviously the "easy" answer is to merge the approach of Group A (keeping Writer's style defaults) and Group B
(keeping Writer's indexing defaults) by the simple expedient of using style "Heading 1" (rather than
"Title") for Chapter titles, "Heading 2" and so on for hierarchical sub-headings. Then the ToC is
simple, the Navigator is happy, and PDF Bookmarks are complete -- all by simply following the defaults. But LO's own
Guides chose a different approach (well, two different approaches), and I'm not sure that I'm qualified to critique
either of those alternatives. That leads to:
(2) A question about Writer's default styles
A newbie to Writer's styles [we all were, once] is likely to appreciate the simplicity of the sequence "Heading 1" ..
"Heading 10" (all based on style "Heading" (which itself has no hierarchy value)) for organizing documents.
That approach provides such simple clarity that, even when making custom hierarchical styles, one is inclined to follow that same
model. The same newbie, though, might then wonder, What is the point of styles "Title" and "Subtitle" in a
structured document?
It seems clear that the ToC indexing exception for "Create from: Additional styles" (rather than
"Create from: Outline") was made to accommodate just such situations as using "Title" for
Level 1 -- but why? After using OO, then LO, for years, I had almost forgotten those newbie questions [made
all the more awkward by the fact that the GettingStarted and Writer Guides lack PDF Bookmarks], but a recent
return to the Guides forced me to recall those early questions... and realize I still lack good answers.
Is this a case of developers responding to feature requests run amok (perhaps with
