On Tuesday 03 November 2009 13:56:14 Boudewijn Rempt wrote: > On Sunday 01 November 2009, Anne Wilson wrote: > > I have updated the images on this page, mainly using ones from your > >  website. Could you please check the page and adjust in terms of whether > >  any features have been removed or new ones should be added? > > > > Anne > > Forwarded to Thorsten, the KPresenter maintainer since he's not subscribed >  to this list. > Than

On Sunday 01 November 2009, Anne Wilson wrote: > I have updated the images on this page, mainly using ones from your >  website. Could you please check the page and adjust in terms of whether >  any features have been removed or new ones should be added? > > Anne > Forwarded to Thorsten, the KPresenter maintainer since he's not subscribed to this list. -- Boudewijn Rempt | http://www.valdyas.org____________________________________ koffice mailing list koffice@...

I have updated the images on this page, mainly using ones from your website.   Could you please check the page and adjust in terms of whether any features have been removed or new ones should be added? Anne -- New to KDE4? - get help from http://userbase.kde.orgJust found a cool new feature?  Add it to UserBase ____________________________________ koffice mailing list koffice@... To unsubscribe please visit: https://mail.kde.org/mailman/listinfo/koffice signature.asc (205 bytes) Dow

2009/9/22 Thomas Zander <zander@...>: > On Saturday 19. September 2009 21.07.28 ext Dotan Cohen wrote: >> > That sounds like a bug somewhere; RTL docs I have open just fine in >> > kword. >> >> I assume that these are documents originally created in Kword? Upon >> testing, I see that those display fine, it is OOo documents that are >> problematic. > > After some research I found out the following; > * KWord didn't implement text directi

On Saturday 19. September 2009 21.07.28 ext Dotan Cohen wrote: > > That sounds like a bug somewhere; RTL docs I have open just fine in > > kword. > > I assume that these are documents originally created in Kword? Upon > testing, I see that those display fine, it is OOo documents that are > problematic. After some research I found out the following; * KWord didn't implement text direction for master pages. I added that. Will commit shortly. * OOo saves documents incorrect

I do not see how to add Latex formulae in Kword documents. Googling the subject leads me to believe that it is possible (I find many SVN commits and bug reports) however I do not see it in the program UI. How is this done? Thanks. -- Dotan Cohen http://what-is-what.comhttp://gibberish.co.il____________________________________ koffice mailing list koffice@... To unsubscribe please visit: https://mail.kde.org/mailman/listinfo/koffice

> That sounds like a bug somewhere; RTL docs I have open just fine in kword. I assume that these are documents originally created in Kword? Upon testing, I see that those display fine, it is OOo documents that are problematic. > Maybe you can report the issue on bugs.kde.org where you can attach a test- > document? > Here you go: https://bugs.kde.org/show_bug.cgi?id=207915> The way that RTL works in KOffice is that the option to change direction only > appears when the document

On Saturday 19. September 2009 19.01.14 Dotan Cohen wrote: > > KOffice does have such support already, could you be more specific of > > what you are missing? > > All documents are opening as LTR documents (left aligned) and I see no > options in Format  -> Page Layout / Paragraph to set RTL. That sounds like a bug somewhere; RTL docs I have open just fine in kword. Maybe you can report the issue on bugs.kde.org where you can attach a test- document? The way that RT

> KOffice does have such support already, could you be more specific of what you > are missing? > All documents are opening as LTR documents (left aligned) and I see no options in Format  -> Page Layout / Paragraph to set RTL. Actually, when existing documents are opened the Format and other menus are blank, but when I open a new document I don't see these options. But that is a different issue which I will start a thread on as soon as I get the RTL issue addressed. Thanks. --

On Saturday 19. September 2009 17.53.37 Dotan Cohen wrote: > I have begun testing the Koffice 2.1 betas (specifically, Kword) for > document compatibility with OOo-created ODF documents. One major > problem that I have found is the apparent lack of Right-to-Left > document support, necessary for Hebrew, Arabic, and Farsi documents. > Is this feature really missing, or am I simply unable to find it? KOffice does have such support already, could you be more specific of what you are

I have begun testing the Koffice 2.1 betas (specifically, Kword) for document compatibility with OOo-created ODF documents. One major problem that I have found is the apparent lack of Right-to-Left document support, necessary for Hebrew, Arabic, and Farsi documents. Is this feature really missing, or am I simply unable to find it? Thanks in advance. -- Dotan Cohen http://what-is-what.comhttp://gibberish.co.il____________________________________ koffice mailing list koffice@... To unsubscribe pl

Hi all, Last summer I was approached by a member of Maemo R&D about my involvement with the ODF Technical Committee. The subject was how to get an office reader shrunk down to allow it to be used on an embedded device. Naturally I pitched KOffice as something that I think has the best potential. One thing led to another and since last summer Nokia has been supporting a project that makes KOffice work better on small devices. Nokia supported both me and KO GmbH to work on fixing bugs and en

Just quickly tested the Kubuntu Beta 2 KWord an wow, it's SO much faster in loading a file and displays the content correctly. Well done guys! -- Best Regards / Med venlig hilsen   Thomas Olsen Til uvedkommende, der læser med: Der er ingen grund til at læse min mail. Jeg har intet at gøre med FARC, al-Jihad, al-Qaida, Hamas, Hizb al-Mujahidin eller ETA. Jeg har aldrig gjort Zakat, går ikke ind for Istishad, har ikke lavet en bilbombe eller kernevåben og jeg ved dårligt nok, hvad A

On Tuesday 15 September 2009 22:05:30 Boudewijn Rempt wrote: > Sorry, wrong list. This is not my day today... > ____________________________________ > koffice mailing list > koffice@... > To unsubscribe please visit: > https://mail.kde.org/mailman/listinfo/koffice> And still it was an interesting read. Ciao Jan ____________________________________ koffice mailing list koffice@... To unsubscribe please visit: https://mail.kde.org/mailman/listinfo/koffice

Sorry, wrong list. This is not my day today... ____________________________________ koffice mailing list koffice@... To unsubscribe please visit: https://mail.kde.org/mailman/listinfo/koffice

Joining in with with my own thoughts: Motivation I like sketching. There may be better artists, but I still like doing it. I started working on Krita instead of Gimp because Gimp didn't satisfy my painting urges (in 2003) and because the code looked decidedly unhackable. Krita was nearly ready back then, I thought, only missing an actual painting tool. I didn't work on MyPaint, because that application started in 2004. My comparison application are art rage (nice, but unusable because the p

On Tue, 15 Sep 2009, David Faure wrote: > kpresenter doesn't read .kpr files anymore? Windows... Sounds to me like the plugins aren't found. There is a kpr2odf filter that would allow kpresenter to open .kpr files, and the rtf filter is enabled, too. > > ----------  Forwarded Message  ---------- > > Subject: Re: How to view .kpr files ? > Date: Tuesday 15 September 2009 > From: stelian chirila <stelianc@...> > To: David Faure <faure@...> > Cc:

kpresenter doesn't read .kpr files anymore? ----------  Forwarded Message  ---------- Subject: Re: How to view .kpr files ? Date: Tuesday 15 September 2009 From: stelian chirila <stelianc@...> To: David Faure <faure@...> Cc: Hi David I installed KD and KOffice and KPresenter. I have errors to all of them but some how when I told Windows XP to open *.KPR with kpresenter.exe the system was not able to recognize the format. I installed KDE 4.3. Are you able or somebody from y

Hi Just added http://www.koffice.org/download/; This page is not listed in Applications category (while it fits better to a General category listed on top of page or so) , I probably have no rights to alter the sidebar. With the above, constant url is now present, and my proposal is not to just "blog" about updates (example is http://www.koffice.org/news/downloads/packages-for-21beta1/) but update the download/ page. Otherwise google will soon have dozens of download pages on our

On Tuesday 08 September 2009, John Murphy wrote: > Hi, > I cannot get kword to run on openSUSE 11.1 X64. Have you compiled yourself or are these packages opensuse provides? Which version of kword are you trying to use? > The only one of the suite I can get to run is karbon. > I get no error messages when running from konsole - so I cannot help >  further. What would you like to know to help me resolve this problem. You could try to run kbuildsycoca4 manually; that might help

Hi, I cannot get kword to run on openSUSE 11.1 X64. The only one of the suite I can get to run is karbon. I get no error messages when running from konsole - so I cannot help further. What would you like to know to help me resolve this problem. Thanks, johnM ____________________________________ koffice mailing list koffice@... To unsubscribe please visit: https://mail.kde.org/mailman/listinfo/koffice

Hi: As part of my MS research at UMBC (www.is.umbc.edu) I am performing source code analysis of KOffice projects. I will really appreciate someone answering the following questions about the KOffice project. In the KOffice bug tracking system (https://bugs.kde.org/) what are the exact meaning of categories (e.g new, assigned, etc.) under Bug Resolution?Similarly what are the exact meaning of categories (e.g. upstream, moved, etc.) under Bug Status (https://bugs.kde.org/)? I could not locat

I have directed him to windows.kde.org. -- regards / pozdrawiam, Jaroslaw Staniek  Kexi & KOffice (http://www.kexi-project.org, http://www.koffice.org)  KDE Libraries for MS Windows (http://windows.kde.org)  http://www.linkedin.com/in/jstaniek____________________________________ koffice mailing list koffice@... To unsubscribe please visit: https://mail.kde.org/mailman/listinfo/koffice

Hello, Could anybody answer this guy, please. Cheers, Mark Dear sir,I visited the koffice.org site to download koffice running on windows platform.But i could not find download link for the same.Kindly let me know if there is any such service available. Thank youSagar Siddhapura. _______________________________________________ kde-www mailing list kde-www@... https://mail.kde.org/mailman/listinfo/kde-www____________________________________ koffice mailing list koffice@... To unsubscribe please

For quite some time almost every blog by a KDE PIM developer is about Akonadi in one for or the other, often about "Akonadi porting" or "porting to Akonadi".

Akonadi itself can already be difficult to explain, combined with "porting" it probably has only meaning left if you are a developer.

The thing anyone else will be able to extract are delays.
Delays in the sense that we, the developers working on KDE PIM, are enthusiastic about our plans on what we want to achieve for a certain KDE release, only to be disappointed that we didn't get as far as we originally hoped for.

For example an initial guess was to have KAddressBook and KOrganizer ported in time for the 4.3 release, but lack of resources meant we didn't even get to start working on KOrganizer in any significant form and the new KAddressBook would lack some features.
So KAddressBook is held back and finished for 4.4, KOrganizer is still being worked on.

So what is all this porting business actually about and why does it take so long?

Imagine a situation where you want to cook something (well, you can imagine anything els of course, but it will greatly improve the understanding of the following example if you restrict your fantasy to cooking for now).

After you've decided what you want to cook, you'll have to get your ingredients, which usually means going out for shopping. When you get home, probably after quite some time and travelled distance, you'll have to prepare these ingredients (wash, peel, chop, etc.) and then start the actual cooking.

That works pretty well, millions of people do between that once in a while and every day.
So you meet other cooks and discover that while you have individual styles for preparing ingredients and the cooking process, you all despise the shopping chore, especially when shops are crowed, roads are jammed, weather is nasty, and so on.

On one of those lazy sunday afternoons you read about outsourcing and immediately convince your fellow cooks to outsource shopping to a shopping specialist.
You snicker at the thought of this poor fellow having to brave the nasty weather, travel the jammed roads, wait in line at stores, while you comfortably wait for the devlivery.

However, you discover that you have to adjust your approach to cooking to accomodate for this for of ingredient acquisition.
With your initial approach you knew when you would be doing what for how long (not counting unavoidable delays during shopping).
With your new approach you don't anything between placing your order and the arrival of the goods. Sure, you could be waiting at the door step, but that gets boring after a while. You can spend some time preparing everything you already have at home, but usually that won't keep you busy long enough. So you do something else instead, maybe reading Planet KDE and learning that those lazy developers have balantly copied your outsourcing idea

Switching to a different reality there is this cook called KMail (in this reality cooks are, for an unknown reason, actually called "mail user agents").
An absolut expert in preparing an ingredient called "message" (weird reality, I know), peeling of envelopes, chopping into pieces (jokingly called "multi parts"), etc. You know, the usual cooking stuff, just done expertly.

But again the shopping for "messages" at shops called "servers", with owners of sometimes questionable character, low quality offerings and so on, is making KMail's life unpleasent.
So of course outsourcing that to a shopping specialist (in this reality, weird as it is, called "Akonadi") is the way to go.

Unfortunately our cook KMail discovers, while adjusting to the different cooking approach, that all these years of shopping had resulted in acquiring certain habits (in another reality, the author of this blog has the habit of not using shopping lists because eventually he'll recognize things to buy at the shop anyway).

Habits that need to be unlearned or replaced by habits which fit the new situation better. Habits our cook might not have been aware of or vowed never to think about again.
Fortunately there is a group of motivational trainers (having the surprisingly sensible name "KDE PIM Developers") who will help to overcome those.

It takes time, but it is totally worth it.

Recently a number of nice coincidences happened: I received my second-hand Intuos3 A5 tablet just day before the new shiny Qt 4.6 has landed with QTouchEvent (among many other features). Also I conducted my 3+ hours of trainings on APIs designing to my coworkers (based on Jasmin's document) just week before we had some essential KOffice APIs discussions based on the same material thanks to Olivier Goffart (QtDF).

At sprints I tend to devote my time rather to different areas than those related to regular development. And I like that. For example I agreed on helping Lukas Tvrdy, talented Krita developer working on gorgeous brushes, to help hime with setting up his "win7+kde4.3+emerge+msvc2k9+some-tools-that-make-cmd.exe-suck-less" development environment. At one point, the story is that for debugging some tricky bits of applications the extra installation is handful. Also the code is checked better by having access to multiple different builds - we learned that no single compiler catches all possible human mistakes. Now as the Symbian port of Qt is stable, Qt itself is validated in another way too, and KDE frameworks are no different in this regard - the libs work on so many targets now. Portability is a clear benefit for both users and developers.
Summing up, setting the environment on win7 was nearly a success on the first evening (we just continued on Sunday) - emerge tool works out of the box, with only minor compile fixes needed sometimes as usual in trunk development of KDElibs or Qt (ah, Lukas - now you'd probably like to recompile to 4.6 ).

I hope the pictures show you the climate of the cool meeting:

(kudos to the organizers, both the community and the company)

If you've been paying attention at the back there, you'll know that openSUSE started using a new community-driven online update administration process for 11.2. As well as Novell employees, community people are taking care of the workflow of examining and approving online updates to buggy packages. Now I have a favour to ask of you - the online updates that are ready to go out need testing to make sure they don't inflict gross mischief on users' systems.

KNetworkManager has an online update sitting in this queue awaiting testing. As anyone who has read http://bugzilla.novell.com/show_bug.cgi?id=553908 knows, I forgot to initialise 2 bools added to KNetworkManager just before 11.2 shipped, causing the settings that control whether DNS and routing settings from DHCP to be applied to be set randomly, so the update team wants someone more reliable's opinion on whether my fix for that is any good.

If you want to test it out and take part, add the 11.2 update test repo (or manually browse this URL and install all the NetworkManager-kde4 packages yourself) - http://download.opensuse.org/update/11.2-test . NB that due to a process bug the release number is the same so you will have to --force the install. If it works for you, please comment on bnc#553908 to that effect.

I just have to say it, I'm thoroughly impressed by Burkhard Lück's determination to improve the user-documentation of KDE applications (particularly the kdebase ones). This is much needed, a huge undertaking, and probably also not very rewarding work. This being said, I'm sure he would appreciate some help -- if you can speak English (you can, otherwise you wouldn't be reading this) and want to contribute to the KDE documentation, subscribe to the kde-doc-english mailing-list

The Ubuntu Developer Summit happened in Dallas last week with 200 developers from every part of Ubuntu as well as upstreams and hardware vendors around. Naturally the best looking of the lot was the Kubuntu contributors who turned up to discuss the next six months in the world's finest KDE distribution. The Lucid Lynx will be a Long Term Support edition and it's exciting that KDE 4 is now at a stage of maturity where this will be possible to do for the first time. LTS means fixing, completing and assuring over and above any new features. The Doctor is in the house.

Kubuntu Contributors: Julian Edwards (Soyuz), Roman Shtylman (Installer Bling), Roderick Greening (The Creator, USB style), Michael Casadevall (fixes your broken Arm), Jonathan Riddell (moi), Ralph Janke (5 a day, every day), Aurelien Gateau (Desktop Experience), Jussi Schultink (IRC Council), Mackenzie Morgan (s/Abort/Stop/), Scott Kitterman (negotiator)

So what's in store? Read the specifications for full details.

Under Packaging, of course we want KDE 4.4 and Qt 4.6. We will review all the patches and make sure any we carry have a clear rationale (this is mostly done already). We'll have a policy of discussing any patches with upstream and assume to follow their wishes where we want to add any. We won't go packaging beta applications unless upstream agree. KOffice 1 will die but KOffice 2 may not all yet be ready for main. We'll look at the Pulseaudio changes to Phonon (we don't use Pulseaudio in Kubuntu by default currently but many Gnome apps do so it's not something which is going away). We'll get Virtuoso working with Nepomuk and we'll get policykit-1 in which means KPackagekit can be updated to the latest version.

Kubuntu Netbook will no longer be a Preview thanks to lovely work from the Plasma Netbook dudes. We need to make sure kubuntu-netbook and kubuntu-desktop work sensibly when both are installed. Apps and UIs will be reviewed for Netbook suitability.

On the development front I hope to make good progress on printer config, there's a rewrite of update-notifier-kde in the works, more than one person has promised to get SMB file sharing working and we want to get touchpad configuration easy.

In Ayatana Integration the Canonical Desktop Team wants to adopt KDE's new systray tray spec (or notifier item as I believe its now called) for Gnome. They want to change it so the icon menu will be rendered natively with items sent over Dbus and we had a meeting with the Plasma folks to thrash out the details of that.

We have a new website layout in the works, we need to poke sysadmins and security team to get that working. We'd like to crystalise some marketing (besides being like Ubuntu Desktop but blue) and work out our target users and get some slogans. We'd also like to make use of the Ubuntu loco teams by finding Kubuntu contacts for each one.

On bug triage we'll not DrKonqi for upstream KDE apps to stop our poor bug triagers being flooded with upstream bugs (it has the obvious downside that KDE bug triagers will get any bugs which are our fault but hopefully that'll be kept to a minimum).

For translations we got the Launchpad devs to promise proper QA reporting so we can be sure Launchpad is helping and not hurting our translations.

If you want to help out, take a look at the Todo list then come and find us on #kubuntu-devel.

The Ubuntu Family in Dallas

Dallas is a curious place. They don't say "hello" they say "how are you", I didn't work out if it was a question or just a greeting. You can't get anywhere without a car although mostly we took Limos because mere taxis wouldn't be luxurious enough. Talking of luxury, rooftop swimming pool and nobody uses it except me! After a week of hard discussions, early mornings and sharing a toothbrush I've escaped to the highlands and its failing internet, time for some cabogganing.

So, openSUSE 11.2 is out, and that means a lot of people start using it and, well, occassionally run into bugs and sometimes even report them. As much as 11.2 appears to be a fine release, this is bound to happen now too, and that means that the number of KDE bugreports for openSUSE in the Novell bugzilla will grow again and will need to be handled.

And now it seems to be a good time to do some housekeeping there. Many of the bugreports there are old by now, for older KDE releases, or even for openSUSE releases that are no longer supported (bye bye openSUSE 10.3). Having too many bugreports means a lot of effort needs to be spent just managing them - if developers and packages are supposed to fix problems, they first need to know which ones are important and should be worked on first. For this reason we have guidelines for sorting KDE bugreports, however, with the recent the release of 11.2, there hasn't been time to review all recent bugreports, and many of other bugreports are not valid anymore.

This is exactly the time when you can help KDE in openSUSE. If you like the 11.2 release and would like to contribute back, if you've already wanted to contribute but didn't know how or thought that you don't have the required knowledge, or even if there is a bug you'd like to see fixed and would want to help the developers and packagers to have more time to concentrace on it, this is the chance. We are starting another KDE bug squashing session, with the aim to review and sort all KDE bugreports for openSUSE. And it is not difficult - all you need is openSUSE 11.2 installed, the ability to use Bugzilla, and the howto describing all the details.

So if you want to be part of the openSUSE KDE team, come (today, tomorrow, this week, whenever you want) to #opensuse-kde IRC channel on FreeNode, ask if you have any questions, consult the howto and you can pick from the prepared groups of bugreports and let's squash some of those bugs.

If you have no idea what this means, don't worry, neither do I.

What I do know, however, is that a lot of people around KMail and are extremely happy about this

Basically the folks working hard on porting KDE PIM apps to Akonadi have reached one of their bonus mission goals: they've got rid of a very old, very obscure, tedious to maintain, mindboggling to work with (you get the picture, right?) legacy part of the mail handling framework.

Well, I guess bonus goal might give the wrong impression here. It is not less important than any of the primary mission objectives (to stay in game jargon). It is a bonus because it makes other things easier, boost your enthusiasm, lets you look forward for the challenges to come.
Think in terms of finding the double barrel shotgun in Doom, getting the Holy Grenade in Worms, looting an epic item in WoW, getting super cow powers in Aptitude.

So, congratulations to the folks at KDAB. You rock!

Not really a KDE related post, but instead one about the OpenChange project.

OpenChange is a project to implement the Microsoft Exchange / Outlook protocols, and we're creeping up on the 0.9 release. For those not familiar with it, the aim is to be wire-level compatible, so that you can use a FOSS client (such as Evolution or an Akonadi client) with an unmodified Exchange server.

OpenChange depends on some underlying Samba4 libraries, so we normally work with the Samba project to get releases that basically match up - we don't want to rely on building bits of Samba4 from the git repository, and we don't want to depend on really on versions of Samba4. Not too far ahead, and not too far behind. Just right...

The next release of Openchange (0.9 "COCHRANE") will rely on Samba 4 alpha9. So the main thing to do is to make sure that we can work with the current state of Samba 4, to provide patches to Samba for stuff that needs to be fixed on the Samba side, and to have changes for OpenChange ready to go.

We expect to release within two weeks of Samba 4 alpha9, but OpenChange 0.9 will be released when it is considered done.

We anticipate a 0.10 release in early 2010, and probably a subsequent 0.11 release prior to 1.0.

I've gone through the trac tickets, and moved anything that can't reasonably be achieved for 0.9 to a 0.10 milestone. Large changes have to wait for 0.10 - it is getting very late to risk destablising libmapi.
So what we still have left:
- integrate exchange2ical work from Ryan Lepinski into trunk
- ensure that OpenChange works with FreeBSD/OpenBSD
- ensure that OpenChange works with OpenSolaris
- libmapi/Samba4 API updates
- mapiproxy/Samba4 API updates and association group API evolution
- a couple of tickets that may not be too hard to fix, related to pkg-config support
- a ticket related to Free / Busy time support that has a crash.
- a patch that checks some return values that we current don't handle.
- some documentation stuff.

Details are on http://trac.openchange.org.

Known problems:
- openchange development server will not be working "as it is". Resolving this requires revision of the OpenChange schema updates (to match Samba4 changes). This may not be resolved for 0.9.

If I've dropped a patch, or there is something you really need for 0.9, now is your chance to make yourself known. Probability of a patch being applied is inversely proportional to complexity, and also inversely proportional to how close I think the release is. That is, simple and soon is good.

Today I updated the KDE Licensing Policy with a couple of changes following requests from folks. Most notably Creative Commons is now allowed. This is only for standalone media files (such as an image for a splash screen) and not for anything which might want to be mixed with GPL material such as icons. "Attribution-Share Alike 3.0 Unported" is the version allowed. The other change is requiring BSD licencing for CMake modules, which brings the policy into line with existing practice.

The Ubuntu Developer Summit is happening this week in Dallas. The theme of the discussions is LTS and what it will take to have a release in six months which can be supported for three years hence. We've been having sessions on packaging, development, bugs policy, translations and more. You can find the schedule and how to take part in sessions on the summit website, there are icecast streams for all the rooms. The Kubuntu specs are on this wiki page still works in progress of course. It's going to be great to have a KDE 4 release suitable for LTS, just six months to do it!

Some of the Kubuntu Team take to the ice rink