Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#2885 - koffice 1.4 documentation is missing
Attached to Project:
Arch Linux
Opened by Dmitry Kagan (mitya) - Monday, 27 June 2005, 09:41 GMT
Last edited by Damir Perisa (damir.perisa) - Friday, 13 January 2006, 16:02 GMT
Opened by Dmitry Kagan (mitya) - Monday, 27 June 2005, 09:41 GMT
Last edited by Damir Perisa (damir.perisa) - Friday, 13 January 2006, 16:02 GMT
|
DetailsIn koffice 1.4 PKGBULD:
rm -rf ....../kde/share/doc 1. KOffice documentation shouldn't be removed. Unlike the info/man situation, there is no alternative documentation source for KOffice apps. 2. KOffice documentation is meant to be integrated into KDE documentation and there is documentation for all other KDE apps. Thanks! |
This task depends upon
Closed by Alexander Baldeck (kth5)
Tuesday, 24 January 2006, 19:23 GMT
Reason for closing: Won't fix
Tuesday, 24 January 2006, 19:23 GMT
Reason for closing: Won't fix
Perhaps it is just me, but it seems a little disturbing going online for docs on an obviously offline app like kword, for example.
Like I said earlier, in other cases we have man pages. KDE apps are not the case.
How about a separate package for koffice documentation? This will solve the dilema.
Thanks!
The KOffice documentation at http://docs.kde.org/stable/en/koffice/
dates back to 2001. Sad...
http://docs.kde.org/stable/en/koffice/koffice/index.html --- 2001
http://docs.kde.org/stable/en/koffice/kword/index.html --- 2005
http://docs.kde.org/stable/en/koffice/kpresenter/index.html --- 2002
about man pages and info pages: man pages are needed so that you know what argument means what in a commandline app. in a gui-app, at least i'm in most cases just learning by doing. of course i understand that there are people who like to have it more rational and structured. if there is a need for them (that's why i think a poll in the forums would be usefull) then i'm ready to enlarge the pkg of koffice to include all the docs ... but i don't want 2 days later to read a bug-report to remove the docs again. nor want i to maintain a koffice-docs pkg myself. hope you see my point of view. what do you suggest?
as koffice is scheduled to be split at least into kexi and koffice i suggest to add yet another package for just the docs: koffice-docs.
when you splitt out kexi, i will rebuild labplot to include kexi support. the koffice-docs are very low priority ;-)
rumor has it that a beta of the upcoming koffice is around already so i will wait and see if things haved changed.