(old)Puppy Linux Discussion Forum

Hello all,

I have put at every Puppyist's disposal, here, v. 4.1.6 (latest as of
this writing) of OpenOffice.

You'll need both the full aOO and the English language pack to have the
interface and help files, etc., in English. The two needed sfs's are currently
at the bottom of the repo list mentioned above.

The latest OpenOffice for PuppyLinux: as classical and powerful as ever!

BFN.

Thanks Musher - this will be useful.

When the sfs installer tried to run the writer it came up with the attached error and terminated.

I was able to start the program by looking for the bin in /opt and it runs fine, but also no menu entries to assist starting. Is that what the dsktop2 pet is for - does it add menu entires?

cheers!

Hi greengeek.

Thanks for testing.

I don't know why their *.desktop files always come ex-factory with
"%U". What does "%U" mean, anyway?

To answer your question: yes, that little pet provides hopefully good
alternative launchers for OpenOffice.

BFN.

I don't know why their *.desktop files always come ex-factory with
"%U". What does "%U" mean, anyway?

I don't know exactly what %U does mean, though I've seen lots of different stuff like that often placed in addition to the command under Exec= e.g.: %f or even -f etc.pp.

That's just another reason why I'd edited the .desktop files of all .sfs modules I create. Often the program just complains a file not being found, but runs. Sometimes programs don't run then.

Sometimes there's also combinations of different additions to the command or even the command env is used plus some addions plus the name of the program or the name of run-time environments like qt etc.pp.

https://askubuntu.com/questions/30210/w ... -a-command

It's a parameter for the Exec key in .desktop files (defined in the Desktop Entry Specification) that describes how arguments to the program (from the file manager/program launcher, e.g. multiple selected files) should be handled:

%u A single URL. Local files may either be passed as file: URLs or as file path.

%U A list of URLs. Each URL is passed as a separate argument to the executable program. Local files may either be passed as file: URLs or as file path.

So, e.g., /usr/share/applications/gedit.desktop contains:

Exec=gedit %U

which means that arguments to gedit will be treated as a list of URLs (or local files).

You must change %U with "$@" in puppy. I have built the italian localized openoffice 4.1.6:

https://www.italianpuppy.org/community/ ... 09#msg9209

Hello all.

Pursuant to the remark made above by greengeek, I unsquashed /
resquashed the aOO-4.1.6 sfs with the following edits:

-- I removed the annoying "%U" from the "Exec=" line in all the *.desktop
files. That bug is solved: the aOO apps will now launch as they should.

-- while I was working on them, I added as 1st line of each of the *.desktop files AND made them executable.
This means that to run say, scalc, you can simply type, in console,and scalc will run.
You're right to think it's a useless refinement!

Warning to users outside the kennels:
Those edits probably make this aOO-4.1.6 sfs usable on PuppyLinux only.

Re-upload at augras' ftp repo has just completed: this edited sfs is now
ready for your downloads. (Same URL as in 1st post.)

Enjoy.

Hi rusher,

I see that Libreoffice is now in its last 32bit edition, so can you tell me the specs for OpenOffice?

I would like to have Open Office for 64bit Puppy.

Any available?

Sorry after much searching found this:
[urlhttps://www.openoffice.org/dev_docs/source/sys_reqs_aoo41.html[/url]

HI Darry.
This sfs is for 32-bits.

@Rainer:
How's this? I'll produce a 64-bits version -- it's only a matter of putting a
series of deb or rpm archives in the right order in a sfs -- and you test it?
( I do not have a 64-bit set-up. )

darry19662018 wrote:Sorry after much searching found this:
[urlhttps://www.openoffice.org/dev_docs/source/sys_reqs_aoo41.html[/url]

Hi.
Your page is giving a 404.
BFN.

Ok!

ITSMERSH wrote:Ok!

Actually, it is better if each user who wants his linguistic version does it.
Sorry. Also at this time I have limited bandwidth left.

There is no secret:

1- Donwload the DEB-package version for your language ( ES, PT, RO, DE,
etc. ) AND for the strength of your computer ( 32-bit or 64-bit ) from the
OpenOffice site -- on a partition with lots of room.
(I mention the DEB package because PupLin has the < dpkg-deb > tool;
it is simpler this way.)

2- Unpack this tar.gz archive with SFR's excellent UExtract;

3- Create there ( on your partition with "lots of room" ) a directory
called < /mnt/sdXN/aOO-4.1.6_PupLin-64bits_AB >, where:
X is your drive letter
N is your partition number and
AB ( at the end ) stands for your language code. For example, Do not forget to adapt X, N, and AB.

4- Go back in the directory where the unpacked deb archives are and
open a console there;

5- Issue or type the one-liner: 6- "cd" to directory "desktop integration" and repeat the one-liner;

6a- A mirror of the aOO suite should now be in directory
aOO-4.1.6_PupLin-64bits_AB. Please check if the tree seems ok.
(Comparison attached.)

7- Now go back at the top level of your partition and use < mksquashfs >
with your favorite parameters on directory aOO-4.1.6_PupLin-64bits_AB.
After the required wait you will have an sfs for your localized
ApacheOpenOffice;

8- Use sfs_load to load it.

That's it. IHTH. BFN.

~~~~~~~~~~
Sorry in advance if the above presents too many details for an exper-
ienced Puppyist like yourself, but I wanted everyone to understand.

Hi ITSMERSH,

Apache OpenOffice-4.16, 64-bit, see my post here, http://murga-linux.com/puppy/viewtopic. ... 413#979413. One link on it now takes you to the 4.16 release download page for both 32-and-64 bit versions of the Full Suites. Another takes you to language packs for other than the Full Suite you chose in the language of choice on the first link. I didn't test, but I think this caution still applies: "Caution: Makes sure its the language pack. In the row above each language pack is a package for a full suite. I don't know whether and how these differ from the full suites on the other page."

You'll also find a 'Menu' pet on the above post.

I was using PaDS 1.0.4 when the post was written. Obviously, you don't need an explanation of how using your PaDS 1.1.4 would change those instructions.

I've edited that post to now point to PaDS 1.1.4

Good reminder, mikeslr.
Thanks.