23 Nov
2011
23 Nov
'11
1:25 a.m.
On Tuesday 22 November 2011 12:06:51 pm Darrell Anderson wrote:
I think our approach must not focus on MS compatibility. That is a hill far too steep to
climb. Not even the OO/LO people have achieved that --- and they never will. Every time I
test importing complex Word documents into OO/LO Writer they look broken. I'm talking
complex documents, not simple letters and memos with manual formatting. :) I have no hope
of any free/libre word processor having full compatibility with MS Office --- nor do I
care. The TDE team should focus "marketing" efforts on KOffice as a personal
office suite. Ignore the compatibility discussions.
Of course full compatibility won't ever be achieved. However, even OOo/Lo do it better
than KOffice. I don't want to suggest making it a main concern, though I do think we
should make a future goal to at least "catch up" with OOo/LO.
Well, then. Looks like I need to learn how to package the apps separately. Can anybody
here help with that? A mini how-to?
You'd need to separate the files into different packages. Put the core libraries in
one package, then separate the binaries and other libraries into other packages. If you
use RPM for package management, I can provide an example of how to do that. I don't
know how to do packaging on any other system.
--
Kristopher Gamrat
Ark Linux webmaster
http://www.arklinux.org/
If this suite is advertised as a personal office suite
rather than
professional the apps remain viable for many
Trinity
users. The tight
integration with TDE is a bonus too.
absolutely, yes.
I like kword and kspread well, ligthtweight, fast, well
integrated,
does (nearly) every thing I need, so far.
some quirks though (inconsistent font sizes, e.g.).
(I also tried koffice2.x several times, before it became
calligra, and it was
a complete mess, unusable, data loss etc.).
OO, however, is a monster and just plain overkill, I just
use it rarely when I
have to look at some M$-office documents sent from
someone... Somebody mentioned ODF support. We might need to
ensure ODF support is up to date.
Tim, if KOffice ODF support is lagging, can we add that as a candidate for R15 (not R14
--- R15)?
It was awhile back when I used KOffice. I haven't used it since 3.5.9, I don't
know if it was updated in 3.5.10, though it would probably still need updated.
I hope KOffice is not removed from the Trinity line,
but I am wondering how
much work is involved to package the apps
separately.
Likely there would
need to be a koffice-base package that contains
all
the common libraries,
headers, etc.
hm, there ARE separate packages, e.g. kspread:
> aptitude show kspread-trinity