How to edit online Help pages, please

Hi, everybody.

I am currently writing some beginners’ learning materials for ScriptForge (I am one of them).
There is some phrasing in some Help pages which will be better explained in another way. I have the blessing for these small changes from ScriptForge creators. In fact, I am working with them.

But I cannot find instructions on how to start editing them. I’m sorry, but I am unavailable at meeting time on Fridays (working hours for me), and I may have lost the full explanation.

@ohallot, I’m sorry to bother you directly, but can you provide some instructions (maybe a video?).

Also, I want to propose to put the whole ScriptForge main title outside the BASIC macros “tree branch”, because it is relevant to both BASIC and Python. It should be under Script Development Tools tree branch, or on its own.

I want to learn how to edit the Help pages, that’s why I did not file a ticket in Bugzilla.

If you don’t want to clone the full LibreOffice source code and the Help submodule alongside it, you can use direct editing in Gerrit’s web interface. That should be fine for phrasing changes.

The instructions were updated relatively recently, leveraging the new edit link feature in Gitiles file view, which I developed with help from Gitiles devs. However, this is now hampered by attacks on our infrastructure, which have forced us to rate-limit the access to Gitiles views. We need to keep hitting refresh sometimes multiple times to get past the 503 errors in Gitiles views.

Oooooooooooooooh!

Exactly that I was seeing. That explains it (I thought it was broken).
Thank you very much, Ilmari, as always!

Yes, I just want to do small changes (hopefully).

Then I guess if I want to relocate the ScriptForge branch to a more
exterior one, I would need to clone the whole repo, don’t I?

Celia

HI @LobaLuna

Unless we take action to move all languages altogether in the weblate installation, simply relocating (or even renaming) Help files in master branch triggers retranslation of the moved/renamed files.

Also, it will require to adjust the build makefiles as well.

A house of cards crossed my mind… :kissing_heart:

Cheers
Olivier

Totally agree, @ohallot. Not an easy task, indeed.
What about a redirectional page, like an alias on Linux? That might be a
patch.
It’s very confusing to look for ScriptForge Python info in BASIC’s
branch…

Hi, Ilmari,

Apparently, Sundays are good days to access the Gitiles views.

Since this is my first edit in Gerrit, I made a tiny, little change.
Just added a small phrases to this page:
https://gerrit.libreoffice.org/c/help/+/183764/1/source/text/sbasic/shared/03/sf_filesystem.xhp

This is the commit page:
https://gerrit.libreoffice.org/c/help/+/183764

However, I still get a Verified-1 by Jenkins and cannot see “Publish
Edit” button.
The reason (or sort, if I understand correctly) has something to do with
the bot:

Build Failed

https://ci.libreoffice.org/job/gerrit_xmllint/8018/ : FAILURE

the build failed because of an issue with the bot itself, not with the 
code.
The Bot failed to checkout the source ( 
https://ci.libreoffice.org/job/gerrit_xmllint/8018/ )

I do not know what to do next. I leave it as is. Can you help me,
please?

1 Like

Hi @LobaLuna
Relax… Not your fault :slight_smile:
You patch is OK but Jenkins is not in his best days.
Cheers
Olivier

Thank you, my friend! ;D