BG7309 Macros - ScriptForge Proposal

I've uploaded a draft ScriptForge proposal and accompanying database to
NextCloud.

Comments:

   1. The draft needs checking (one macro example is not supported) and
   reformatting
   2. There is a note about standard colours for code that has been applied
   to the basic code except for the last few pages. It needs to be extended to
   python and sql.
   3. Raising spacing at the top and bottom of paragraphs again, and orphan
   lines/headings

There is a major usability issue I've found with using code from the pdf
documents. Copy/paste replaces any leading space on indented lines with a
single space. This is particularly an issue with python because indentation
is part of the syntax. How can this be fixed in the pdf documents?

I see between adding that draft and posting to the mailing list Olivier
Hallot has included an earlier draft in the chapter he had checked out.
I'll check out that chapter and update it to the latest ScriptForge draft.

How can python code be formatted in colour?

I have macros that can color code Python as well as a few other languages. This works by setting character styles with the character style has the color association. So maybe that's what you want maybe it's not.

You also might be able to just load it into a Python editor that does color coding and then copy and paste, some editors transfer the color when you do that.

⁣Get BlueMail for Android ​

Updated to BG7309-Macros_SF_OH_FW_24Jan2022_16Mar2022.odt which
incorporates a few SourceForge demo updates. Existing drafts moved to
archive. Please advise if not correctly logged in tracking sheet.

Hi Flywire, all

I have updated the published chapter with all the changes accepted. Therefore, the master file and the pdf are also updated.

Regards
Olivier

Olivier Hallot confirmed those macros were used to color the code. I
suppose it is https://extensions.libreoffice.org/en/extensions/show/71

   1. The template should check the macros (extension) are loaded
   2. Instead of the macro being a manual process can it be integrated into
   the code style? ie style formats code (as you'd expect).
   3. Color was applied to all code, including SQL (a good thing) but it
   looks a bit off eg python macro names

How can I export an odt document with colorized code to pdf with code
color? The pdf I exported has color but the code sections are still B&W.

I probably have an updated version of the extension. I of I remember I will see guess current the public version is.

The macros could be included in the template but that would not integrate it.

The extension works by setting character styles. I have exported to PDF with color intact. If this fails for you, either expert has changed or you're settings are different than mine.

I cannot verify until next week, but I can test if you like.

⁣Get BlueMail for Android ​

Through testing, I've realised:

   1. V7 Base Guide doesn't use the template, or even the same style names,
   causing most of the code formatting inconsistencies. Thanks to Dave Barton
   for pointing out the "Code" style in the 7.2x template. I've updated the
   wiki to link to the resources folder rather than the V6 chapter template.
   2. The Code Colorizer Formatter extension
   https://extensions.libreoffice.org/en/extensions/show/71 only changes
   code color in these documents, not the formatting contained in the styles
   (not that I'd seen any documentation to that effect).
   3. The Getting Started guide has a caption on each code block.
   Unfortunately, the template doesn't provide an example with sample code so
   there is no guidance here but the presentation across the guides should be
   consistent.

I have updated the published chapter with all the changes accepted.

The initial code had a fair few issues to be resolved so what's the process
to update the chapter in published?
https://wiki.documentfoundation.org/Documentation/Development/User_Guides#Workflow
closes it after it's submitted to the Published folder.