Linux/Ubuntu user using KDE/kdm & KickOff..

Documentation General
#1

Focus:
Is there a way that I can access the work in progress documentation for Linux...
and get involved in writing more of it... if you need my help?

Background / leadup --
I have been in Application Development/Enhancement for 30 years.
On occasion (maybe 3 years of that 30) I have been called to enhance
existing documentation to reflect changes.

I am currently trying to find any LibreOffice documentation dealing
with running under KDE.
After a few minutes of looking today, I was able to find MY
installation of LibreOffice in /usr/lib/libreoffice/program
not /opt/libreoffice/program where another forum somewhere told me to
look (thanks to the "which" command).

Yet, I am still trying to find help adding Libre Office (okay any app,
but I am focused on Libre Office) to KickOff (KDE's menu).

I eventually found the Libre Office documentation, and the Libre
Office documentation wiki ... and found out that Linux documentation
is still work in progress.

Is there a way that I can access the work in progress documentation for Linux...
and get involved in writing more of it... if you need my help?

#2

Hi :slight_smile:
Welcome in :slight_smile: Hopefully this wiki-page might help
http://wiki.documentfoundation.org/Documentation/Development
but our wiki-pages have just grown kinda organically and sorting them out is
very low priority so it can be tricky finding what you need. Hopefully that
page might help!
Regards from
Tom :slight_smile:

#3

Hi :slight_smile:
I was wondering if KDE Documentation might help. I think this?
http://www.kde.org/documentation/
or maybe this?
http://www.kde.org/community/
Sorry i'm not sure how to help! Hopefully something there might help?
Regards from
Tom :slight_smile:

#4

Tom:

Thank you for the two sets of links. I review them Wednesday
afternoon (was busy all day Tuesday, and I have to travel Wednesday
morning).

Again, I toss my hat into the ring to help, if I can.

#5

Hi :slight_smile:
It's still Tuesday here. Ooops, scratch that!
Regards from
Tom :slight_smile:

#6

Barry,
I've been hoping to hear from David Nelson, who may know more than I
about the state of the docs about installing on Linux. Here is a wiki
page, which may or may not be the one currently under development:
http://wiki.documentfoundation.org/Installing_LibreOffice_on_Linux
I also have a copy of this in ODT; I'm not sure if both are in sync,
but I believe so. I don't see it on the wiki (though it may be there
and I can't find it), so I will send a copy directly to your gmail
address if you like.

At some point you will probably want to get an account on our Alfresco
content management system website, but learning your way around that
might be a bit much at this point. You are welcome to get a wiki
account and edit the page there, or edit the ODT that I can send you.

BTW, the instructions we give are for people downloading LibreOffice
(LO) from our website and installing it themselves. It is installed in
a different location from any version of LO that may come with your
distro and/or be installed from your distro's repository. We should
probably mention that when writing/updating docs about using LO on
Linux.

We definitely do need help; the group does not have enough people to
do all that is needed... or sometimes even to identify what's needed.

--Jean

#7

Hi Barry
On Linux the location of installed programs can vary widely.
Many are put into /usr/bin. If you compile from source often the prefix
will be /usr/local/bin.
In "olden" times it was normal that /opt was the location of "optional
programs.

Have a look at
http://slashmedia.wordpress.com/2007/12/23/linux-directory-structure/
or google around a bit and you will find the history of the unix folder
structure.

But OOo and LibO have used /opt as the top level folder for all builds
which have come from the organisations themselves.

The problem comes when you have installed a customised version of one of
these packages. I mean customised by Canonical/OpenSuSE etc. Then the
folder in which it may be found can and does differ from the "original".

That is what you have found out! :=)

You can install other versions of the program to use a more up to date
build, and it will (if downloaded from the OOo/LibO site) install into
the /opt folder. If it is a stable build it will go
into (for example) /opt/openoffice.org or /opt/libreoffice3.4. If a pre
release build it probably ends up in /opt/ooo-dev or /opt/lo-dev.

It is quite feasible to have multiple versions of the programs installed.
I have LO3.4 and 3.4m1 daily build as well as OOo 3.4beta on my laptop.
Running different versions concurrently can be a bit tricky.

The other gotcha is the association of file extensions. Your originally
installed version in /user/lib/.... will probably be the version opened if
you double click an odt file.

It is relatively simple to change these file associations if you want.

Adding additional menu entries is often not necessary if you have
installed the -kde-integration or -gnome-integration packages. Of course
this is a generalisation and all generalisations are false.

Feel free to shout on this list if you need more help, there are plenty of
people "lurking", and most of the Linux power users are much better
qualified than me to give advice.

regards
Martin

#8

_Jewel of the Nile_
"Isn't that function next Tuesday"
"Today is next Tuesday"

jonathon
- --
If Bing copied Google, there wouldn't be anything new worth requesting.

If Bing did not copy Google, there wouldn't be anything relevant worth
requesting.

                              DaveJakeman 20110207 Groklaw.

#9

Hi,

I've been hoping to hear from David Nelson, who may know more than I
about the state of the docs about installing on Linux. Here is a wiki
page, which may or may not be the one currently under development:
http://wiki.documentfoundation.org/Installing_LibreOffice_on_Linux
I also have a copy of this in ODT; I'm not sure if both are in sync,
but I believe so. I don't see it on the wiki (though it may be there
and I can't find it), so I will send a copy directly to your gmail
address if you like.

The last person who did work on the Linux installation guide was Nino
Nokak, to the best of my knowledge. It has evolved considerably since
the first draft I did.

It was originally written to cover installation on a variety of
popular Linux distribs, but became somewhat unwieldy.

Since that time, I have seen a few LibO installation guides for
particular Linux distribs, and they were actually much easier to read
since they were tackling a smaller scope of one distrib.

I have it on my not-so-small to-do list to review Nino's edits, but
this is not likely to happen any time very soon...

#10

Hi,

Hi,

> I've been hoping to hear from David Nelson, who may know more than
> I about the state of the docs about installing on Linux. Here is a
> wiki page, which may or may not be the one currently under
> development:
> http://wiki.documentfoundation.org/Installing_LibreOffice_on_Linux
> I also have a copy of this in ODT; I'm not sure if both are in
> sync, but I believe so. I don't see it on the wiki (though it may
> be there and I can't find it), so I will send a copy directly to
> your gmail address if you like.

The last person who did work on the Linux installation guide was Nino
Nokak, to the best of my knowledge.

No, that's not true :wink:

(I've been editing the parallel installation instructions[1] which
adresses advanced users)

[1] http://wiki.documentfoundation.org/Installing_in_parallel

Cheers,
Nino

#11

Hi :slight_smile:
Ahh, excellent. The Install in Parallel page is often needed by the Users List
Thanks Nino
Regards from
Tom :slight_smile:

#12

Note that you should always mention that installing in parallel needs
you to know what you are doing, so it's meant for advanced users only.

Nino

#13

Hi :slight_smile:
People seem happy with it. I think the page helps people understand what they
are doing and gain a greater understanding of how LibreOffice settings are
stored.
Regards from
Tom :slight_smile:

Impressum (Legal Info) | Datenschutzerklärung (Privacy Policy)   Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.