I guess it will be a bit cumbersome because I’m using an appimage.
Do I have to extract the files, copy the new pythonscript.py, and then repack the files, @karolus ?
thereis only one file in the archiv …extract it … rename it to »pythonscript.py« and copy it into …/libreoffice/program/
1 Like
Well, I’m stalled.
@karolus, even I managed to extract, copy, and repackage the AppImage (even I checked the different sizes of pythonscript.py to be sure it is copied into the AppImage), I’m not able to open any Python script.
Obviously, I have python, and JRE/JDK installed.
I installed LibO Fresh from sources, according to wiki for parallel installations, but I see the same situation…
But I do have python3 installed; it seems the bridge between LibO and python is not. Neither Arch nor Manjaro have this package
JRE/JDK is completely unrelated. Forget about JRE/JDK in the frame of this question. It would only be important, when discussing features like Java macro support, or Base wizards.
Indeed, the script support provider is not that single file, even if a package would only contain one file. E.g., without respective .rdb files in <INSTALLLOCATION>/program/services, this won’t work; and I don’t know what else would be needed.
partially off topic: @mikekaganski
I find a couple off …rdb -files in …/program/services/ … but wait 
tada its …xml! wtf… Who thought up this nonsense?
Why nonsense? RDBs were upgraded quite long ago (I believe, that it was at least planned already in OOo times, even if implemented only in LO).
unoidl-write mentions “new- or legacy-format .rdb file”.
Or I may be completely confusing things; another documentation page seems to describe the files as binary.
It’s actually nice that binary formats are being replaced by human-readable formats wherever possible, but does it have to be the worst human-readable format of all?
Maybe it is easier to install regular than repairing an appimage…
1 Like
If you mean xml, we shouldn’t be surprised. ODF is xml-based, so it makes sense to use xml instead of inventing yet another markup language (yaml already exists anyway).
.
And professionals are going to have a lot of fun, when all(?) invoices are going to be in xml… 
Thanks for the clarification about JRE/JDK. Wasn’t sure at all.
Thanks for the support, anyways, @mikekaganski
That’s also another thing I have to learn: XSLT to import invoices data into Calc. Endless! ;D
Already tried that first, @Wanderer. Even tried the parallel installation for the native LibO download, to avoid distro’s annoyances. No luck to me.
Manjaro is a bit behind Arch, and the current libreoffice-fresh package is 24.2.3.2, which lacks the manual option to create a report (which I need). This regression was corrected in 24.2.4.2, the current version.
In contrast, Python works well, using the APSO extension (Manjaro 24.2.3.2 version). Hence, my impulse to try the appimage, because I need both features (manual creation of reports and Python macros).
It’s frustrating, to be honest, specially because I ran out of ideas to solve this 
I don’t know, what “the manual option” is, but the former Oracle Report Builder, but this tool was written in java. I didn’t see it in the options in above links, but it is a common limit/flaw on LibreOffice for Linux, to come without java-dependecies. - usually a decision of the maintainer.
Indeed it needs Java.
You can see how the manual creation menu item is missing. You can only see the wizard option.
Yes that was the default in OpenOffice, as the other was an extension then. It seems to be a known topic, discussed here:
An package in AUR may solve your problem:
The answer that AndyRTR gives is lame (in my opinion). Since it’s difficult to maintain the package, he decided to avoid the Report Builder (which I also need harder than trying to learn Python scripting).
That’s the reason I am trying to make the AppImage to work with Python in Manjaro, @Wanderer
@LobaLuna: if your issue is already solved? … ignore the suggested workaround!
The following is testet
- firstly i removed the »libreoffice-script-provider-python« package with:
sudo apt-get purge libreoffice-script-provider-python
( 1. only for me to test you dont need that) - then I download only the 2 files pythonscript.py and scriptproviderforpython.rdb from this site
- copy them both to the right location below ……libreoffice/program:
> sudo cp pythonscript.py ……/libreoffice/program/pythonscript.py > sudo cp scriptproviderforpython.rdb ……/libreoffice/program/services/scriptproviderforpython.rdb
Hi, @karolus!
It’s not solved yet. I’m going to try your solution. Give me a couple of days. I’ve been very busy at work. Thank you very much in advance!
Hi, @karolus
No, within the new AppImage are those files included, but they do not show the HelloWorldPython. I tested in Manjaro, with AppImage 24.2.5, or a rpm-parallel installation…
Funny thing is in Arch, yes, I see the HelloWorldPython (BUT not the Report Builder for Base).
It appears only Debian-like distros fit the requirements for LibreOffice 