It would be nice would to have completely clean PDF to ODF conversion, preferable integrated with KOffice and OO.org of course, but even stand-alone version would be useful. Well, since KOffice is able to import PDF you can just hit "save as" to store it as ODF. I would call that integrated.
bdubSOv1iKIJ403M is right though that it won't be able to recover the original structure. So the question is whether you can call that "clean". It just does what is possible. No one suggest to build a lossless document workflow on that.
BTW: KOffice 2 will bring a lot of new scripting features. I'm pretty sure that you'll be able to script KOffice to create a command line tool for PDF -> ODF conversion.
- The wrong facts spread by Mr. Yates involved KOffice - Inge Wallin is a KOffice developer - Inge Wallin responded on behalf of the KOffice team - The open letter was published on dot.kde.org
I don't know why you'd expect anything but a KDE-centric text. IMHO there's nothing wrong with that.
> Will QT 4 and KDE 4 be ported to Windows within a year?
As far as Qt4 is concerned there is no problem. Qt has been available on Windows for ages, directly from Trolltech. It's only that Trolltech's Qt4 is available on Windows *under the GPL* while Qt3 was not (at least not the version from Trolltech, there had been efforts to port the GPLed X11 version to Windows).
Strange machine you have there. My notebook that should be slower than your computer and that has only half the memory compiles kdelibs *and* kdebase in a couple of hours.
> wonder if the Safari source code is available so you can diff between the safari versions and > see what's changed... do you think that's feasible?
AFAIK that's what they tried. But that diff contains, say, a thousand changes. How do you find out the ones that belong together to make up the bugfix or the new feature you want to port (without the CVS history)?
> This is open source. Other people can modify it how they choose. They then post back those changes. Tough shit if those changes aren't useful.
It's still bad manners to start off with an unnecessary fork.
And that's what Apple did. They developed Webcore in secret based on some version of KHTML. Then, in their initial release announcement they still talked about "crossplatform KHTML and an adapter lib". That didn't sound bad at the time:
"...takes the cross-platform KHTML library (part of the KDE project) and combines it with an adapter library specific to WebCore called KWQ that makes it work with Mac OS X technologies. KHTML is written in C++ and KWQ is written in Objective C++, but WebCore presents an Objective C programming interface."
They could have developed KHTML in the KDE CVS together with KDE, and their adapter lib in their own system. They didn't.
Today there doesn't seem to be anything left of this separation between platform-specific and platform-independent parts. Ugly.
Besides, Apple releases the source code in big lumps when a new webcore release comes out, without version history (Note: I'm not talking about Hyatt's patches here.). That's what makes it extremely hard for the KDE developers to find out what set of changes make up what bugfix or feature enhancement. Readonly access to Apple's revision control system would have remedied that but was denied.
All perfectly legal, it's just that it's not nice. No cooperation that deserves that name and a clear sign that Apple still hasn't understood how Open Source works. They could have done better.
Your point is none at all because you don't have to. It just means that Gentoo is not for you. I agree, there should be distros for you, and there are. But you have no right claiming "an OS has to be such and such.". There are different people, ones that value different aspects in a distro higher. Please speak only for yourself, do yourself a favour and pick a commercial end-user distro.
I'm running Sarge with KDE from unstable and I've never seen your problem.
> Some k packages (kde) are 3.3.3-x, some are 3.3.2-x, and a few are 3.3.4-x [...] > Why did some packages of kde 3.3.4 make it into sarge
The most recent version of KDE is 3.3.2!
Could it be that you misread the version number? My kdelibs version is 3.3.1-4, for example. 3.3.3-x and 3.3.4-x should not exist. Do you have any non-standard servers in your sources.list, especially any questionable ones?
(Note that qt-3.3.3-x would be ok, that's a completely separate thing.)
> Any way of removing the google toolbar?
Sure. That can be done under Settings -> Configure Toolbars.
BTW: I find the gg: shortcut much more convenient than a bookmark. Type gg:java into konqi's location bar to google for java, for example.
> AbiWord will probably never use the OASIS format.
That would be a shame. Here's a standardised open format that can already accomodate the needs of two office suites (OOo and KOffice (will be the native format in version 1.4)). If other suites were to join in then the format would gain even more acceptance.
Slashdot Mirror
He wanted to tell you that he, Boudewijn Rempt, coordinates the upcoming release.
I would call that integrated.
bdubSOv1iKIJ403M is right though that it won't be able to recover the original structure.
So the question is whether you can call that "clean". It just does what is possible.
No one suggest to build a lossless document workflow on that.
BTW: KOffice 2 will bring a lot of new scripting features.
I'm pretty sure that you'll be able to script KOffice to create a command line tool for PDF -> ODF conversion.
... and in the times of StarOffice 5 it even came with a GUI that looked like a separate desktop.
... 'cause that would require electricity.
BTW: You can set the bitrates used for encoding in the control center.
Not an answer to your question, but interesting in this context:
I hear KPlato will switch to the taskjuggler engine.
- The wrong facts spread by Mr. Yates involved KOffice
- Inge Wallin is a KOffice developer
- Inge Wallin responded on behalf of the KOffice team
- The open letter was published on dot.kde.org
I don't know why you'd expect anything but a KDE-centric text. IMHO there's nothing wrong with that.
> Will QT 4 and KDE 4 be ported to Windows within a year?
As far as Qt4 is concerned there is no problem. Qt has been available on Windows for ages, directly from Trolltech. It's only that Trolltech's Qt4 is available on Windows *under the GPL* while Qt3 was not (at least not the version from Trolltech, there had been efforts to port the GPLed X11 version to Windows).
Strange machine you have there. My notebook that should be slower than your computer and that has only half the memory compiles kdelibs *and* kdebase in a couple of hours.
24 hours for kdelibs alone? You must be kidding.
You're mean. You're destroying people's prejudice that KDE can only add features and bloat.
Good decision, BTW.
> wonder if the Safari source code is available so you can diff between the safari versions and
> see what's changed... do you think that's feasible?
AFAIK that's what they tried. But that diff contains, say, a thousand changes. How do you find out the ones that belong together to make up the bugfix or the new feature you want to port (without the CVS history)?
> This is open source. Other people can modify it how they choose. They then post back those changes. Tough shit if those changes aren't useful.
It's still bad manners to start off with an unnecessary fork.
And that's what Apple did. They developed Webcore in secret based on some version of KHTML. Then, in their initial release announcement they still talked about "crossplatform KHTML and an adapter lib". That didn't sound bad at the time:
"...takes the cross-platform KHTML library (part of the KDE project) and combines it with an adapter library specific to WebCore called KWQ that makes it work with Mac OS X technologies. KHTML is written in C++ and KWQ is written in Objective C++, but WebCore presents an Objective C programming interface."
Source: This article from 2003
They could have developed KHTML in the KDE CVS together with KDE, and their adapter lib in their own system. They didn't.
Today there doesn't seem to be anything left of this separation between platform-specific and platform-independent parts. Ugly.
Besides, Apple releases the source code in big lumps when a new webcore release comes out, without version history (Note: I'm not talking about Hyatt's patches here.). That's what makes it extremely hard for the KDE developers to find out what set of changes make up what bugfix or feature enhancement. Readonly access to Apple's revision control system would have remedied that but was denied.
All perfectly legal, it's just that it's not nice. No cooperation that deserves that name and a clear sign that Apple still hasn't understood how Open Source works. They could have done better.
> helluva lot more than what you have to pay to make a propriety app with GTK
This is not true if you have to take the developer time it takes into account. Companies do have to.
According to this source it actually does not only sound like one: http://dot.kde.org/1111118006/1111143814/
Your point is none at all because you don't have to. It just means that Gentoo is not for you. I agree, there should be distros for you, and there are. But you have no right claiming "an OS has to be such and such.". There are different people, ones that value different aspects in a distro higher. Please speak only for yourself, do yourself a favour and pick a commercial end-user distro.
- from a non-Gentoo user
I'd say those people should take a look at xfce or http://www.rule-project.org/. There are projects that are optimised for low-power machines.
But that cannot be the focus of modern desktop development!
Won't happen in 3.5.
;).
- Would break the binary compatibility guaranteed throughout the KDE 3.x cycle that third-party apps rely on.
- Too much effort anyway
KDE 4.0 will kick arts (and ass
You may think what you want about MySQL AB's licensing policy, but sorry, the term shareware is utter nonsense in this context.
What exactly is shareware about the GPL?
Let me add:
p ://packages.debian.org/unstable/kde/
These page confirm it:
http://packages.debian.org/testing/kde/
htt
Not even 3.3.2 exists in either testing or unstable, let alone 3.3.3 or 3.3.4. So, how can you have that package versions?
I'm running Sarge with KDE from unstable and I've never seen your problem.
> Some k packages (kde) are 3.3.3-x, some are 3.3.2-x, and a few are 3.3.4-x
[...]
> Why did some packages of kde 3.3.4 make it into sarge
The most recent version of KDE is 3.3.2!
Could it be that you misread the version number? My kdelibs version is 3.3.1-4, for example. 3.3.3-x and 3.3.4-x should not exist. Do you have any non-standard servers in your sources.list, especially any questionable ones?
(Note that qt-3.3.3-x would be ok, that's a completely separate thing.)
> Any way of removing the google toolbar?
Sure. That can be done under Settings -> Configure Toolbars.
BTW: I find the gg: shortcut much more convenient than a bookmark. Type gg:java into konqi's location bar to google for java, for example.
> AbiWord will probably never use the OASIS format.
That would be a shame. Here's a standardised open format that can already accomodate the needs of two office suites (OOo and KOffice (will be the native format in version 1.4)). If other suites were to join in then the format would gain even more acceptance.
KDE does it in a similar way, too, and has for a long time:
Release Schedules / Development Plans
Thanks.