Lotus Symphony realigns with Apache OpenOffice ITworld.com It also keeps a major Open Document Format (ODF) project ensconced within IBM-friendly governance. But IBM is not going to go this route, at least for now: this week's announcement shows that Big Blue is realigning its development team with that of the ... and more »

Formal name is Apache OpenOffice, trying to be consistent about it

← Previous revision		Revision as of 23:28, 13 May 2012
Line 148:		Line 148:
	*[[AbiWord]]<ref>[http://www.abisource.com/wiki/OpenDocument Abisource.com]</ref><ref name="abiword">[http://www.abisource.com/release-notes/2.4.2.phtml Abiword 2.4.2 Release Notes.] Retrieved 2009-03-03</ref>		*[[AbiWord]]<ref>[http://www.abisource.com/wiki/OpenDocument Abisource.com]</ref><ref name="abiword">[http://www.abisource.com/release-notes/2.4.2.phtml Abiword 2.4.2 Release Notes.] Retrieved 2009-03-03</ref>
	*[[Adobe Buzzword]]<ref>{{cite web|url=http://labs.adobe.com/technologies/buzzword/ |title=Adobe Buzzword online word processor from Acrobat.com |publisher=Labs.adobe.com |date= |accessdate=2009-05-19}}</ref>		*[[Adobe Buzzword]]<ref>{{cite web|url=http://labs.adobe.com/technologies/buzzword/ |title=Adobe Buzzword online word processor from Acrobat.com |publisher=Labs.adobe.com |date= |accessdate=2009-05-19}}</ref>
		+	*[[Apache OpenOffice]]<ref name="register" />
	*[[Atlantis Word Processor]]<ref>[http://www.atlantiswordprocessor.com/en/news/1_6_5.htm Atlantis Word Processor 1.6.5 release notes]. Retrieved 2010-01-28</ref>		*[[Atlantis Word Processor]]<ref>[http://www.atlantiswordprocessor.com/en/news/1_6_5.htm Atlantis Word Processor 1.6.5 release notes]. Retrieved 2010-01-28</ref>
	*[[Calligra Suite]]<ref>{{cite web|url=http://www.calligra-suite.org/words/ |title=Words |publisher=Calligra Suite |date= |accessdate=2012-02-23}}</ref>		*[[Calligra Suite]]<ref>{{cite web|url=http://www.calligra-suite.org/words/ |title=Words |publisher=Calligra Suite |date= |accessdate=2012-02-23}}</ref>
Line 203:		Line 204:
	*[[NATO]] with its 26 members uses ODF as a mandatory standard for all members.<ref>[http://www.h-online.com/news/NATO-supports-ODF-open-document-format--/111127 H-online.com]</ref>		*[[NATO]] with its 26 members uses ODF as a mandatory standard for all members.<ref>[http://www.h-online.com/news/NATO-supports-ODF-open-document-format--/111127 H-online.com]</ref>
	*The TAC (Telematics between Administrations Committee), composed of e-government policy-makers from the 25 [[European Union]] Member States, endorsed a set of recommendations for promoting the use of open document formats in the public sector.<ref name="ec.europa.eu">[http://ec.europa.eu/idabc/en/document/3197.html IDA promotes the use of open document formats for e-government interoperability]</ref>		*The TAC (Telematics between Administrations Committee), composed of e-government policy-makers from the 25 [[European Union]] Member States, endorsed a set of recommendations for promoting the use of open document formats in the public sector.<ref name="ec.europa.eu">[http://ec.europa.eu/idabc/en/document/3197.html IDA promotes the use of open document formats for e-government interoperability]</ref>
−	*The free office suites [[LibreOffice]], [[OpenOffice.org]], [[Calligra]] and [[KOffice]] all promote the OpenDocument Format, as it is used as their default file format.	+	*The free office suites [[Apache OpenOffice]], [[LibreOffice]], [[Calligra]] and [[KOffice]] all promote the OpenDocument Format, as it is used as their default file format.
	*Several organisations, such as the [http://opendocumentfellowship.com/ OpenDocument Fellowship] and [http://opendocsociety.org/ OpenDoc Society] were founded to support and promote OpenDocument.		*Several organisations, such as the [http://opendocumentfellowship.com/ OpenDocument Fellowship] and [http://opendocsociety.org/ OpenDoc Society] were founded to support and promote OpenDocument.
	<!-- *The [http://www.oidi.org OIDI.org] (Open Interoperative Document Initiative) is committed to encouraging efforts by governments at all levels, around the globe, to implement changes necessary to ensure public documents are open and interoperable and thus available to all citizens/residents without the need for specific vendor software. -->		<!-- *The [http://www.oidi.org OIDI.org] (Open Interoperative Document Initiative) is committed to encouraging efforts by governments at all levels, around the globe, to implement changes necessary to ensure public documents are open and interoperable and thus available to all citizens/residents without the need for specific vendor software. -->

DataNucleus AccessPlatform is a standards-compliant Java persistence product. It is fully compliant with the JDO1, JDO2, JDO2.1, JDO2.2, JDO3, JPA1, and JPA2 Java standards, and provides a REST API. It complies with the OGC Simple Feature Spec for persistence of geospatial Java types. It allows access to all popular RDBMS available today, together with db4o, LDAP, NeoDatis, JSON, Excel/ODF spreadsheets, XML, BigTable, and HBase databases.

Release Notes: Support for non-transactional atomic updates was added. The "native"/"auto" value generation algorithm was rewritten to include "identity"/"sequence" etc. Full support for nondurable identity was added for RDBMS, MongoDB, HBase, Excel, and ODF datastores. Support for the REST API was rewritten to provide complete query support. Various improvements were made to the "simple" SCO container wrappers. Various problems were fixed in metadata handling, detachment/attachment, and date-string conversion.

Release Tags: JDO, JPA, Persistence

Tags: Database, API, ORM, JDO, JPA, Persistence

Licenses: Apache 2.0

Open source suites go beyond Microsoft Office InfoWorld (blog) The group has a commitment to the Open Document Format and is improving the quality of its ODF support. With its roots in the K Desktop Environment (KDE), Calligra is only realistically available for GNU/Linux at present, but there's an experimental ...

Apache releases OpenOffice 3.4 SmartCompany.com.au Other new features in the latest version include native language support for 15 languages, enhanced Open Document Format (ODF) handling, the ability to include pivot tables in spreadsheets, enhanced graphics including native support for Scalable Vector ... and more »

Inquirer

Ubuntu 12.04 Precise Pangolin review Inquirer A standard installation of Ubuntu 12.04 includes Libreoffice, an office suite that supports Microsoft's proprietary file formats while promoting the ISO standard Open Document Format (ODF). Canonical has stayed with the tried and tested Firefox web ... and more »

ZDNet

Open Source Suites Highly Active ComputerworldUK (blog) The user interface is clear and appealing and there's support for the important Open Document Format (ODF) file format. It's available online. The project has also announced it's Google Summer of Code student activities, which will add useful new ... Apache releases new OpenOffice build, promises faster upgradesRegister all 21 news articles »

ZDNet

Apache releases new OpenOffice build, promises faster upgrades Register Other new features include a speeding up of the boot process and better support for ODF, notably ODF 1.2 encryption, as well as multiple images within the format. The entire software suite is now also under the Apache License 2 regime. Open Source Suites Highly ActiveComputerworldUK (blog) Read more on:SmartCompany.com.au all 21 news articles »

When Calligra 2.4 was released there was a flurry of interest resulting in a number of articles in the press and blog posts. Some of these were regular reviews of higher and lower quality. One of them, which I think was one of the better ones, was this one by Påvel (in Swedish). In the review he says that Calligra has a good foundation, he likes it but there are obvious problems with it. I find that an honest and true assessment, especially since it is obvious that he has really tried it and been bitten by some bugs. (Some of these bugs are already fixed in 2.4.2, most of the rest will be gone in 2.5.)

But that is not the topic of this blog post. In one paragraph he says that "since it is a KDE program it will work best in that environment." and offhandedly states that "In Gnome it will drag in a couple of hundred MB as KDE dependencies". I found that unlikely, given all the work that we in KO GmbH have done on Calligra for embedded platforms but I know that there is some overhead involved. But how much is it?

So I asked in #kde-devel on irc if anybody had done the measurements to say how big the overhead of KDE applications is in a non-kde environment. It appeared that nobody had done that, or at least nobody knew about any figures.  But I managed to trigger the curiosity of Michael Pyne enough so that he immediately decided to check it.

He started up his trusty Fluxbox environment and did a continuous measurement of the free memory (taking into account buffers and cache) and found out the following:

When a KDE application is started in a non-KDE environment the memory goes up (of course) and when it is killed again the memory goes down. The memory that remains used is probably the KDE overhead in the form of libraries (Qt and the kdelibs) and daemons (kdeinit4 and kded4). This overhead is 48 MB.

Michael also said that he found that it took "102084 1KiB blocks of memory to run konqueror, konversation, + associated KDE daemon procs in fluxbox." That figure includes everything: the Qt runtime, kde libraries and the applications themselves and is a very low figure for what you get.

As a side note, you will get the same overhead when you run e.g. Libreoffice on your desktop since they have their own toolkit. The difference is that that toolkit is not used anywhere else in any other application.

So, there you have it. Admittedly this is very unscientific but 48 MB is significantly below 200 MB, so much that the 200 MB figure can easily be dismissed. And even when you include two applications and all the toolkits and libraries it still hardly goes over 100. So until somebody takes a more scientific approach I will state that the KDE overhead in a totally non-kde environment is 48 MB.

Read more in the official announcement.  You can download Apache OpenOffice 3.4 now, from http://download.openoffice.org/    Tell your friends.  And welcome home.

Related posts:

1. An Invitation to Apache OpenOffice
2. Apache OpenOffice: How to Get Involved
3. First release of the Apache ODF Toolkit

I spent 5 days in Vienna, participating at the Libre Graphics Meeting 2012. It is conference full of developers, artists and users connected to open-source tools. You can meet there MyPaint, Gimp, Inkscape or Scribus developers. At least I did! Or you can meet some independent developers who created cool custom open-source tools and very nice people interested in design.

Besides the regular program we visited Metalab. It’s part of the Hackerspace scene. It is a great place for hackers to meet and build stuff. Not just code, but also hardware, photography or food. Metalab is full of interesting geeky stuff like laser cutter, 3D printer or game consoles since the age of Atari! Pity that something like that is not close enough to me. I had very nice conversions with LGM friends there. Let’s review the conference from my point of view. But first I would like to thank KDE for sponsoring me the travel expenses!

TL;DR: Very interesting stuff everywhere.

First day of the conference was full of color management talks. Richard Hughes talked about ColorHug and colord. ColorHug is interesting piece of open source hardware: display colorimeter. It allows you to calibrate your screen for accurate color matching. More information on the official website.

Kai-Uwe Behrmann talked about OpenICC and Oyranos. Chris Lilley about color management in SVG2. I don’t understand this topics, but I read very good article about it recently, so if you are confused about it, go ahead and read it. It is important topic, if you print photos or you want to calibrate two monitors to show the colors in the same visual way.

Second half of the day started with lovely Russian Valek Filippov. He was talking about re-lab project which is about reverse engineering of the proprietary formats for the compatibility reasons. I used oletoy from this project back then when I was working on Calligra. For investigating Excel files it was really great and helped me a lot! Valek’s presentation was followed by Fridrich Strba (who comes from Slovakia by the way, go Slovakia! :-]), he talked about LibreOffice and support of the proprietary graphics formats in LO.

Igor Novikov presented the restart of the sK1 Project. Next presentation by Behdad Esfahbod was very interesting, he was talking about rendering of the text on the GPU. With this approach you can free CPU from performance CPU-consuming tasks like rasterization. It’s way to go on low-performance devices like smart phones.

Ramon Miranda is involved in Gimp, MyPaint and Krita as the artist and the creator of brush presets. He is famous for his GIMP Paint Studio. His presentation was important for me as he was talking about painting and that is always interesting to me. His background lays in traditional art and he is exploring digital painting. And he is exploring it very successfully producing nice art. Very talented painter and nice man.  Martin Renold (Maxy), original creator, developer, maintainer gave talk about “Predictive painting” in MyPaint. I could not miss it. I always like to talk with Martin about painting algorithms.

Tom Lechner talked about lovely tool, his Laidout contains many fancy tools not available in other packages. I liked that you could put pictures on curve for example. HarfBuzz, the free text shaping engine by Behdad Esfahbod catched my attention too.

From the “An awesome FLOSS design collaboration work-flow” by Máirín Duffy and Emily Dirsh, Sparkleshare caught my attention. It’s a git-backed, dropbox-like system that automatically checks in and pushes files to a shared git repository.

On Friday I started with Powerstroke in Inkscape. Very nice effects were demoed. You need Inkscape trunk for Powerstroke to be able to play with it. We might take some inspiration either for Karbon or maybe even for some vector brush engine for Krita.

Then train of GIMP related talks started. Peter Sikking, interaction design guru, and Kate Price talked about text handling in GIMP. OpenCL in Gegl and GIMP by Victor Oliveira: Mesa is implementing OpenCL support! NVidia, AMD and Intel provide proprietary solutions so far. Øyvind Kolås a.k.a. pippin with some Gimp developer mitch talked about Gegl integration in GIMP. Recently a huge step was made towards integrating this very fast, important back-end (e.g. 16 bit per channel) for pixel buffers. Many pictures with goats were presented.

Tube Open Movie by Bassam Kurdali was actually remote presentation. Bassam sent video to organizers and it was projected for the whole audience. Then he answered some questions through #lgm IRC channel.

Saturday started with our presentation about Krita. Together with Timothee Giet, a.k.a. Animtim, we presented some new workflow improvements in Krita. Curve brush, multi-hand and mirror painting caught some attention too. Tom Lechner had nice suggestion for multi-hand tool: Escher-like strokes. Then we showed some piece of art done by Krita. Timothee Giet then continued with his talk about animation with Synfig studio.

Then I attended Krita workshop about workflow to create illustrations and comics with Krita where Timothee showed Krita in the real-world usecase. It was very well attended workshop, around 22 people there, full room of people. We found some problems with Krita 2.4 in Fedora package. Now I realize that it was probably disabled feature shortly before release and already available in master (full-screen canvas with ‘Tab’ key). I use Fedora, but I never use the packages, because you can’t have installed both. Krita 2.3 is by the way very old. Please refrain from using it. Krita 2.3 misses so many work and features, many of those that Timothee presented in his workflow. You can get Krita 2.4 for Fedora 16 in testing KDE repo. Few problems found at the workshop: old 2.3 version, disabled feature in 2.4 and brush editor is too big for netbooks

Closing talk by Louis Desjardins. It was decided that the next LGM is going to be in Madrid, Spain. Handshakes with familiar faces, visiting Vienna and travel back home. It was great time to be there.

The event was covered by blogposts and ideas from talks were picked on twitter/identi.ca. Here are few I found:

Ideas from talks I
Ideas from talks II
Nicu Bunu
Timothee a.k.a. Animtim

This last thursday Boudwewijn schedule a skype chat group to present the main concepts of the Krita development. It was really nice, since a more dynamic interaction was made with the students. It answered some doubts I had and important features was explained. It covered from the KDE and Calligra foundation of Krita to dockers and resource management of the software.

I am posting here a few notes about what I got from it and some notes on how I imagine some of these will affect directly in my project. If any concept that I wrote here is wrong, please, leave a comment correcting me. This would be really helpful and more than welcome!

Color Management

I am familiar with color models concept, but not so familiar with color spaces. This was a good point in the presentation. It clarified to me that I do not have to worry about how to deal with these spaces since the color management libraries take care of it. Although I have some interest to understand how to manage colors, I think I will have to leave that for another time.

Tiles

Krita tiles was a really new concept to me. After you talk about the advantages of divide the pixels in groups, it makes sense and we question ourselves why we didn't though about that before. Dmitry posted in the mail group a nice article about the Krita tiles. I believe I have to take some time to discuss this point with him. In my project I'll deal with a considerable amount of particles so a full understaning on this framework will garantee a better performance of the brush. In one of the books I'm reading, a improvement in the grain interactions performance is done with the division of the space in tiles, although is suggested to divide the 2D region or in uniform Voronoi tiles or in a hexagonal grid. I think that in a general way, the effects are the same for the application, so the tile form doesn't play a mean role.

Data Structure and Image composition

This was one of the trickiest definitions of the presentation. In a program like Krita, which have a big amount of processing and operations done at pixels, it's expected that we should have a not so straightforward data structure.

The base class of the image components is the KisBaseNode class. It takes care of other nodes, layers and selections of the image. However this class do not have anything to do with its peers. For that, we use a KisNode, which is the parent class for Layers and Masks. Along with that, every node has a representation of it, which we call the Projection of that node. It's a rendered result of the layer, with the processed data applied. For the composition of the final image result, a multithread structure is behind each node. Then to produce the result in the parent node, the setDirty method will pass through all the way up to it.

I don't know if in the future I will need to modify or create a new layer type since the feeling of live sandpainting would need a lot of updates in the canvas. I asked that in the chat group and probably I will not need to do it. For instance, the closest feature in Krita that deals with this kind of painting is the Deform Brush. It modifies the closest pixels several times and updates the canvas after each mouse movement, so it's more or less what I wanted.

Canvas and Tool Handling

The canvas take care of the user interaction through mouse, keyboard and tablet, paints the decorations and the visible image results. It has two implementations: one based on OpenGL and another based on QPainter. I had to look directly on the code to understand this better, but i think the main reason to have two implementations is that if the user have OpenGL on his/her computer, a better perfomance widget can be used. Otherwise, the QPainter based canvas will be used. Both classes inherit from KisAbstractCanvasWidget, so both has to have the same event handling.

When we modify something with a tool, the canvas have a Tool Proxy, which manages the current tool. So, when we change from some tool to another, the native events are mapped to the newly chosen tool. Then, when the tool does a operation, it requires a canvas update so the user can get the result.

Painting

I didn't have much trouble to understand this point. Pentalis helped me a lot in this part. I even made a simple paintop modifying one of the paintops plugins in the source code. The Chalk Brush have a simple implementation and it was easy to understand the code and modify it. Most of my doubts in doing it was in the underlying structure, like how paint devices and layers worked together, but the presentation answered most of it.

Filters, Resources, Imports and Exports

These features wasn't so hard to understand. Filters have the usual concept and is applyed in a multi-threaded stateless way. It is implemented as plugins in Krita. Imports and Exports use the KoFilter class as base of the implementation and invokes KoFilterChain to do the sequence of operations to complete the conversions. Resources are managed using KoResourceServer and manages resources of one type at a time. To represent the resource itself we use a KoResource as base class.

That's it

This was what I got from the presentation. I have some notes about other questions that came after, but I believe that I have to write it with more visual details to a full undestanding about what I'm working on. My particle simulation didn't work as I was expecting and I have to spend some time debugging it. Pentalis suggested that, after the simulation is working, I write the positions updates in QImages so we could have the visual feel of the particles moving. After that, I have to formulate how I will do this visual feeling in Krita, but I believe that with this brief background I will be able to do it.

See you later!

Since the student who initially asked for being my SoK student has gone silent, I'm now declaring myself available for another student.

I know some people has already come by irc asking, and I sort of turned them down. Well now is you chance to come back!

Three weeks ago Calligra developer C Boemann suggested that we should have a bug week for the parts of Calligra that don't have their own maintainer to nurture them, namely the common parts. These are core libraries and plugins that are used in all the applications and therefore very important. A bug here makes all Calligra applications worse.

In Calligra we have a policy that says that each application should have a maintainer but the common parts should not. This emphasizes the needs of the applications rather than the wishes of the maintainer and it has worked very well for us since we instigated the policy.The downside is that there is nobody who is really responsible for them; the responsibility of all is the responsibility of none.

The idea was to focus on the common bugs for a week. This last week was the week that was chosen, and now the results are in. To see the common bugs, you can use one of the reports on bugs.kde.org: https://bugs.kde.org/component-report.cgi?product=calligracommon. As you can see, there are no more known bugs for the picture shape (flake-picture) and no more for the color engine (pigment).

The bug week excluded embedded documents, which are not supported at all in Calligra at this point, and everything that has to do with text, which actually has a maintainer. The rest of the components went from 192 bugs down to 95. I find that pretty impressive!

Another way to see what has happened is to look at the Weekly bug statistics. Despite the name you can see the number of bugs and the change in bug statistics for any period of time. This link shows the change in bugs for the Calligra common product (you have to scroll a bit down to find it) and for the 3 weeks since the bug week was suggested. There was a lot of focus on these bugs even before the actual bugweek so I include the whole period. The results are:

• For bugs: +7 -70
• For wishes: +2 -43

This means that around 100 bugs and wishes were fixed or implemented in the 3 weeks. The actual numbers are slightly higher but not everything was fixed. There were a couple of wild dreams which we found weren't really right for bugs.kde.org and there were some bugs that weren't really common after all.

But in general I think we can pronounce the Calligra Common Bug Week an astounding success!

Open Document Format to Be Supported by Microsoft Office 15 Midsize Insider Midsize businesses eager for Office to support Open Document Format (ODF) 1.2 may have their wish granted. A technical preview of the Office 15 productivity suite demonstrated support of ODF 1.2. A beta version of the program that includes ODF is set ...

Google Drive vs. Microsoft SkyDrive: 4 reasons Google wins out ITworld.com Search is a pain with SkyDrive as it only peers into documents in Office file formats. Google Drive's search is far more advanced: in addition to Office formats, search works in any format Google Docs can save to (ODF, PDF, TXT). and more »

SkyDrive for Windows ZDNet UK (blog) Viewing and editing files on SkyDrive has some advantages over Google Drive and Docs; Office format files (and other formats like WordPerfect, ODF, text and HTML files) open in the Office Web Apps, without changing the file format the way Google Docs ... and more »

In Calligra 2.4 we disabled change tracking because it didn't have the quality we felt comfortable releasing.

Now I ask you dear users to share your requirements for the ultimate change tracking systemt. But also describe how you have been using change tracking in the past (in any application) and what was good and bad, what you felt missing, etc.

I'd like personal accounts and anything you share should be free from interlectual property claims.

Go to the forum post that I have also made.

Calligra is an integrated suite of applications that cover office, creative, and management needs. It offers applications on both desktop computers and mobile platforms like tablets and smartphones. OpenDocument Format (ODF) is used, making it compatible with OpenOffice.org, LibreOffice, and Microsoft Office. Calligra Suite contains the following applications: Calligra Words (word processor), Sheets (spreadsheets), Stage (presentations), Flow (diagrams and flowcharts), Kexi (visual database creator), Braindump (note taking), Plan (project management), Krita (drawing), and Karbon (vector graphics).

Release Notes: This release contains a number of important bugfixes.

Release Tags: Stable, major bug fixes

Tags: KDE, Qt, Office, Office Suites, Office/Business, ODF, OpenDocument Format, Word Processors, Spreadsheet, Presentation, Flowcharts, diagrams, Databases, drawing, Graphics, project management

Licenses: GPL, GPLv2, LGPL

A shiny new Kubuntu release all for you. You can install it safe in the knowledge that the Kubuntu community will make security updates and major bug fixes for 5 years along with Canonical's lovely resources doing the same on much of the rest of the Ubuntu packages.

There's a few Known issues in this release I'm unhappy with, kmix crashes, akonadi upgrades are still not pleasant, Plasma activity manager likes to crash too, and users of 11.10 need to update to the latest packages before starting an upgrade. Sorry about those, we'll get onto them.

In terms of new features we've kept it light to be able to fit with the requirements of Long Term Support, but all the packages have been updated. I especially like what OwnCloud are doing, they've seen a big improvement and are getting some useful apps for providing from a server.

New stuff I like is Calligra and KDE Telepathy, I use these both a lot. It's really handy to be able to stay on Facebook chat without being distracted by the aimless news on Facebook webpages and Calligra has saved my day more than once when Libreoffice has crashed (on its own documents!).

Kubuntu Active is a shiny new Ubuntu flavour for tablets. It's a technology preview for now because it's not a very smooth experience yet and it's i386 only but.. ooh what shinyness!

Kubuntu is in interesting times, we're trying to branch out from one sponsor of Canonical to several. Those sponsors will include Canonical of course. Kubuntu as a project has had a long history of working with Canonical. Canonical have invested in sponsoring staff and producing CDs, as well as providing infrastructure and release management. Although Canonical has decided to adjust where it focuses it's resources, I am delighted that Canonical is continuing to support the Kubuntu project with infrastructure and other resources that help us as a project to build Kubuntu. I am also delighted that Blue Systems have stepped forward to fund my continued work on Kubuntu so that I can continue to give my full attention to the project and build the best possible KDE-based Operating System for our users

I've had some questions about Planet KDE recently.

Planet KDE is intended for personal blogs of KDE contributors blogging with a KDE focus. All KDE contributors are welcome to add their feeds to planet by editing the file in svn or filing a bug.

A while ago I added some categories because people were asking about adding blogs that weren't KDE contributors. Which categories are shown can be easily edited on your local browser by clicking "Configure" at the top of the page. KDE.News has the dot.kde.org feed and is on by default, Project News has KDE and KDE friendly projects like Calligra or Kubuntu in it and is also on by default. There are also categories for blogs not in English and for user blogs. Finally there's the microblogging category which is for twitter feeds and shows in a box on the side if you turn it on.

Hopefully that provides a way for KDE fans to easily read about what is happening in our community.

The last weeks I have been doing my small share of bit-flipping to contribute to the polishing of that big, big rough diamond which there is called Calligra, doing some pixel pushing here and there (e.g. on the line-end-style selectors and the rulers) and fixing a few bugs.

Now I wanted to give all icons used in Calligra a check, to see both if there is an icon for the given icon-id as well as if there are icon files installed which are no longer used. After all Calligra is a quite large codebase, coming over a long and winding road (some files have up to 13 and more authors, the first one usually in 1998 ), so a few icon usages got broken during the trip.

Problem
But how to get all icon-ids in your codebase?

I have used a simple approach to get at least most of them, doing a grep for lines with “KIcon(“. That gave me more than 1000 lines for Calligra, and almost all also directly used an icon-id, so there was chance to do a check and create a report for these.

Now this is quite unsatisfying to not be able to easily get a list of all the icon resources used in your codebase. How do you deal with this in your project?

Proposal
Ideally icon-ids would be kind-of tagged when used, so like gettext is able to extract all strings which need a translation, some geticon would be able to extract all icon-ids. The result could then be used to check the icon-ids against the icons available from the icon themes and the icons installed from the project itself, ideally automatically (as doing that manually is… pretty boring, time-consuming and error-prone).

I could imagine that there could be some macros

kicon("some-icon")

and

kiconid("some-icon")

which would resolve to

KIcon(QLatin1String("some-icon"))

and

"some-icon"

and would enable to automatically extract these icon-ids.

What do you think? Comments, other/better proposals welcome!

This summer, Google’s Summer of Code is bigger than ever. Sixty students are ready to start work under the umbrella of the KDE project, and out of those sixty, eight are going to work on Calligra. We have some newcomers and some old hands. Let’s introduce the projects!

Presentation Animations

While Calligra Stage already supports animating the graphical objects on a slide, it is lacking a good and user-friendly tool to create those animations. Paul Mendez from Ecuador is going to work on this task. Shapes will be put in a time-line with actions defined for every step, as shown in this mock-up he drafted for his application:

Bibliographies and Citations for Calligra Words

Handling bibliographies and citations is currently quite primitive and unfinished in Calligra Words, but it’s an important feature for an application that at one point might have been named “Calligra Papers” — students writing papers are one of the target audiences. Calligra Words developer Smit Patel will create a system to store and edit citations and then interface this system with external bibliography engines like Kile and Bibus.

More and better OpenFormula Support for Calligra Sheets

Calligra Sheets supports the OpenFormula specification to implement formula functions — but not yet at the highest level! Nityam Vakil will undertake the task to get us there, by implementing the missing 18 functions. And writing unit tests for them, of course.

Saving Charts to OpenDocument

In the past year or two, Calligra has made huge steps improving our loading and display of charts from OpenDocument and OOXML documents. But saving has lagged rather badly… And that’s a situation that obviously won’t do! So Brijesh Patel will spend his summer improving the issue. In fact, he has already started writing patches for saving pie and ring charts!

Mathematical Formulas

KOffice 1.6 had pretty good support for showing and editing mathematical formulas, but support has had a bumpy road in the transition to Qt4 and the formula component could be so much better… Enter Abishek, who is not afraid of a really tough job. He will improve editing of formulas, but also the rendering quality.

Krita

The other three students will be working on Krita. Head over to krita.org to see what they will be working on!

 

Google Drive vs. Microsoft SkyDrive: 4 Reasons Google Wins Out PC World India Search is a pain with SkyDrive as it only peers into documents in Office file formats. Google Drive's search is far more advanced: in addition to Office formats, search works in any format Google Docs can save to (ODF, PDF, TXT). and more »

Google Drive vs. Microsoft SkyDrive: 4 reasons Goo... Good Gear Guide Search is a pain with SkyDrive as it only peers into documents in Office file formats. Google Drive's search is far more advanced: in addition to Office formats, search works in any format Google Docs can save to (ODF, PDF, TXT). and more »

Google Drive vs. Microsoft SkyDrive: 4 Reasons Google Wins Out PCWorld Search is a pain with SkyDrive as it only peers into documents in Office file formats. Google Drive's search is far more advanced: in addition to Office formats, search works in any format Google Docs can save to (ODF, PDF, TXT). and more »

Microsoft to support ODF 1.2 open document standard in Office 15 PC Advisor By Loek Essers | 25 April 12 Microsoft has demonstrated support for the Open Document Format (ODF) 1.2 standard in a technical preview of the forthcoming Office 15 productivity suite, and plans to release a beta version with the feature late this ... Microsoft Office 15 to support ODF 1.2The H all 2 news articles »

Microsoft to support ODF 1.2 open document standard in Office 15 PC World Magazine Microsoft has demonstrated support for the Open Document Format (ODF) 1.2 standard in a technical preview of the forthcoming Office 15 productivity suite, and plans to release a beta version with the feature late this summer. The company announced its ... and more »

Microsoft to support ODF 1.2 open document standard in Office 15 ITworld.com By Loek Essers, IDG News Service | Software 1 comment April 25, 2012, 10:51 AM — Microsoft has demonstrated support for the Open Document Format (ODF) 1.2 standard in a technical preview of the forthcoming Office 15 productivity suite, ... and more »

Microsoft to support ODF 1.2 open document standard in Office 15 Australian Techworld Microsoft has demonstrated support for the Open Document Format (ODF) 1.2 standard in a technical preview of the forthcoming Office 15 productivity suite, and plans to release a beta version with the feature late this summer. The company announced its ... and more »

Microsoft to support ODF 1.2 open document standard in Office 15 Good Gear Guide Microsoft has demonstrated support for the Open Document Format (ODF) 1.2 standard in a technical preview of the forthcoming Office 15 productivity suite, and plans to release a beta version with the feature late this summer. The company announced its ... and more »

Microsoft to support ODF 1.2 open document standard in Office 15 ARNnet Microsoft has demonstrated support for the Open Document Format (ODF) 1.2 standard in a technical preview of the forthcoming Office 15 productivity suite, and plans to release a beta version with the feature late this summer. The company announced its ... and more »

Microsoft to support ODF 1.2 open document standard in Office 15 Network World By Loek Essers, IDG News Service Microsoft has demonstrated support for the Open Document Format (ODF) 1.2 standard in a technical preview of the forthcoming Office 15 productivity suite, and plans to release a beta version with the feature late this ... and more »

Microsoft to support ODF 1.2 open document standard in Office 15 Computerworld By Loek Essers IDG News Service - Microsoft has demonstrated support for the Open Document Format (ODF) 1.2 standard in a technical preview of the forthcoming Office 15 productivity suite and plans to release a beta version with the feature late this ... and more »

Microsoft to Support ODF 1.2 Open Document Standard in Office 15 PCWorld (blog) By Loek Essers, IDG-News-Service:Amsterdam-Bureau Microsoft has demonstrated support for the Open Document Format (ODF) 1.2 standard in a technical preview of the forthcoming Office 15 productivity suite, and plans to release a beta version with the ... and more »

Support for ODF from the Hungarian government The H The Hungarian government has committed to invest just over a million pounds (370 million HUF) in the development of applications that use the open document format (ODF), according to a report on the European Union's Joinup web site.

So Thursday and Friday last week I was in Brussels for an ODF plugfest representing KO GmbH and the Calligra project. The plugfest is some kind of a mix between interacting with other ODF implementors (like Microsoft, IBM, LibreOffice etc), and a publicity event to engage the government and industry in the country where the plugfest is held.

So besides trying various interoperability scenarios, I also made a presentation about Calligra which was well received. Jos van den Oever also from KO GmbH made a presentation on WebOdf (a browser/javascript based editor). And Thorsten Zachmann from Nokia also represents Calligra, so all in all we have quite some impact.

Now back home and fast forward to Monday I got asked to join the ODF technical committee at OASIS. Jos van den Oever is already a member on behalf of KDE, and so he got me in (also for KDE). The initial purpose is to make recomendations and alterations for the next generation of change tracking in the ODF file format. I am working together with two other members of the TC, but, even though I'm not alone, I really feel the personal responsibility to make something good, as billions of people can potentially be affected.

But I've joined the real Technical Committee so I will be joining the weekly phone conferences and have my say on all matters ODF. Now, I will go slowly at first, getting acquainted with the processes and how best to get your point of view across. Luckily Thorsten and Jos will be able to help me with any insider knowledge I need.

So now with 3 TC members KDE is influencing the world of ODF even more than ever.

As the British Cabinet Office opened a consultation on open standards and the best procurement practices for the United Kingdom’s public sector a wave of lobbyists, flown in from the US or just homegrown on British soil, came flocking the Cabinet offices near St James a few weeks ago. The topic of the discussion remains, after all these years of struggle in many countries, just about the same: how to procure Free & Open Source Software, and Open Standards, despite the steady and implacable pressure and game-rigging of Microsoft and its friends from the BSA. In a sense it is the same old story, and therefore it’s a story that’s getting old. No pun intended to the Cabinet Office here, but the political and social pressure applied on public service by some powerful corporations is a shame and should be stopped. In any case, because the issues surrounding Free and Open Source Software as well as standards and patents are still widely misunderstood I thought I would be compiliing a short list of links on the matter:

• We’re starting with a blog post from Andy Updegrove, world-known experts on standards, on a case that’s apparently only remotely connected with the matter. However it provides rich background on the topic.
• “How Microsoft fought true open standards” by Glyn Moody, Part 1 and Part 2.
• “Why RAND is bad for Open Source” by Simon Phipps.
• Not so much of a shameful plug, but in this interview by Glyn Moody I try to highlight the issues surrounding RAND, software patents and open standards in a synthetic fashion.

Comments and questions welcome.

‎Software

← Previous revision		Revision as of 16:24, 21 April 2012
Line 163:		Line 163:
	*[[Microsoft Office 2007]] (from service pack 2 release)<ref>[http://www.microsoft.com/Presspass/press/2008/may08/05-21ExpandedFormatsPR.mspx Microsoft Expands List of Formats Supported in Microsoft Office]</ref>		*[[Microsoft Office 2007]] (from service pack 2 release)<ref>[http://www.microsoft.com/Presspass/press/2008/may08/05-21ExpandedFormatsPR.mspx Microsoft Expands List of Formats Supported in Microsoft Office]</ref>
	*[[Microsoft Office 2010]]		*[[Microsoft Office 2010]]
		+	*[[Microsoft SkyDrive]] / [[Office Web Apps]]<ref>http://www.zdnet.com/blog/microsoft/microsoft-adds-odf-support-url-shortening-to-its-skydrive-storage-service/12480</ref>
	*[[NeoOffice]]		*[[NeoOffice]]
	*[[Okular]]		*[[Okular]]

ITProPortal

Noon News: Berners-Lee: Demand Your Data from Google, Facebook, MPs Demand ... ITProPortal Microsoft has added support for the Open Document Format (ODF) which is more widely accepted than the proprietary Microsoft Office formats (docx, xlsx, pptx etc) to its online cloud storage solution, Skydrive, ahead of the impending launch of Google ...

Microsoft Adds ODF, Short UK, 300MB file Uploads To Skydrive ITProPortal Microsoft has added support for the Open Document Format (ODF) which is more widely accepted than the proprietary Microsoft Office formats (docx, xlsx, pptx etc) to its online cloud storage solution, Skydrive, ahead of the impending launch of Google ... and more »

Geeky gadgets

Microsoft SkyDrive Update Adds ODF Support, 300MB File Uploads And More Geeky gadgets The new update has now enable the ability for the service to support Open Document Format (ODF), which is an XML-based file format for spreadsheets, charts, presentations and word processing documents. As well as ODF support Microsoft has also ...

The eighth ODF plugfest will return to Brussels (Belgium) on April 19th/20th 2012, this time hosted by Microsoft Corporation and supported by OpenDoc Society.

The ODF plugfests are an ongoing series of vendor-neutral events, bringing together implementers and stakeholders of the standard. The goal is to achieve maximum interoperability by running scenario-based tests in a hands-on manner and discuss new and proposed features of the Open Document Format specification.

Lead architects from commercial and open source products, members of the OASIS ODF TC's and technical experts from national and regional governments will be present. Previous plugfests were held at The Hague (Netherlands), Orvieto (Italy), Granada (Spain), Brussels (Belgium), Borough of Windsor and Maidenhead (UK), Berlin (Germany) and Gouda (The Netherlands).

Coolest Gadget Reviews

Microsoft updates SkyDrive with support for ODF, Twitter Engadget First, Google went and updated Chrome's Cloud Print with the convenience of FedEx and now Microsoft's taking a spin at the remote wheel, enhancing its SkyDrive service with support for ODF (Open Document Format) -- an XML-based file type for documents ... SkyDrive Receives Twitter, ODF EnhancementsCoolest Gadget Reviews Microsoft SkyDrive Update Adds ODF Support, 300MB File Uploads And MoreGeeky gadgets all 15 news articles »

SkyDrive zaktualizowany - obsługuje większe pliki, format ODF i skracanie linków dobreprogramy Dzięki wprowadzonym zmianom SkyDrive pozwala teraz na pracę z dokumentami w formacie Open Document - użytkownik może edytować pliki ODF bezpośrednio w oknie przeglądarki, bez potrzeby używania aplikacji firm trzecich. Warto przypomnieć, że format ODF ... Microsoft aktualizuje Live SkyDriveWeb inside all 2 news articles »

Coolest Gadget Reviews

SkyDrive to support ODF format Generation NT (US) This will allow users to view office documents with the .odt, .ods and .odp file formats online through their browser. These ODF formats are the defaults used by the LibreOffice office suit. In addition to ODF, the other new features announced for ... Microsoft updates SkyDrive with support for ODF, TwitterEngadget SkyDrive Receives Twitter, ODF EnhancementsCoolest Gadget Reviews Microsoft SkyDrive Update Adds ODF Support, 300MB File Uploads And MoreGeeky gadgets all 15 news articles »

Why You Should Really Give Microsoft SkyDrive A Try (MSFT, GOOG) San Francisco Chronicle Microsoft made it even better this week by doing what would have been unthinkable a few years ago: you can now use SkyDrive with the free open source Microsoft Office alternative, LibreOffice, or any word processor that supports the ODF format. and more »

adding a 'register' ref; removing one software entry without article

← Previous revision		Revision as of 10:35, 18 April 2012
Line 138:		Line 138:
	*The OASIS Committee Specification [http://www.oasis-open.org/committees/download.php/19274/OpenDocument-v1.0ed2-cs1.pdf '''OpenDocument 1.0''' (second edition)] corresponds to the published ISO/IEC 26300:2006 standard. The content of ISO/IEC 26300 and OASIS OpenDocument v1.0 2nd ed. is identical.<ref>{{citation |url=http://standards.iso.org/ittf/PubliclyAvailableStandards/c043485_ISO_IEC_26300_2006(E).zip |title=ISO/IEC 26300:2006 |format=ZIP, PDF |publisher=ISO |accessdate=2009-11-22}}</ref> It includes the editorial changes made to address JTC1 ballot comments. It is available in ODF, HTML and PDF formats.		*The OASIS Committee Specification [http://www.oasis-open.org/committees/download.php/19274/OpenDocument-v1.0ed2-cs1.pdf '''OpenDocument 1.0''' (second edition)] corresponds to the published ISO/IEC 26300:2006 standard. The content of ISO/IEC 26300 and OASIS OpenDocument v1.0 2nd ed. is identical.<ref>{{citation |url=http://standards.iso.org/ittf/PubliclyAvailableStandards/c043485_ISO_IEC_26300_2006(E).zip |title=ISO/IEC 26300:2006 |format=ZIP, PDF |publisher=ISO |accessdate=2009-11-22}}</ref> It includes the editorial changes made to address JTC1 ballot comments. It is available in ODF, HTML and PDF formats.
	*'''[http://docs.oasis-open.org/office/v1.1/OS/OpenDocument-v1.1.pdf OpenDocument 1.1]''' includes additional features to address accessibility concerns.<ref>{{cite web | url=http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office#odf11 | title=OpenDocument 1.1 Specifications | year=2006 | accessdate=2006-10-31 | publisher=[[OASIS (organization)|OASIS]]}}</ref> It was approved as an OASIS Standard on 2007-02-01 following a call for vote issued on 2007-01-16.<ref>{{cite web | title=Approval of OpenDocument v1.1 as OASIS Standard | url=http://lists.oasis-open.org/archives/office/200702/msg00003.html | accessdate=2007-02-06 | publisher=[[OASIS (organization)|OASIS]]}}</ref> The public announcement was made on 2007-02-13.<ref>{{cite web | title=Members Approve OpenDocument Version 1.1 as OASIS Standard | url=http://www.oasis-open.org/news/oasis-news-2007-02-14.php | accessdate=2007-02-15 | publisher=[[OASIS (organization)|OASIS]]}}</ref> This version was not initially submitted to ISO/IEC, because it is considered to be a minor update to ODF 1.0 only, and OASIS were working already on ODF 1.2 at the time ODF 1.1 was approved.<ref>[http://www.zdnet.co.uk/talkback/0,1000001161,39409700-39001068c-20093634o,00.htm ZDnet.co.uk]</ref> However it was later submitted to ISO/IEC (as of March 2011, it was in "enquiry stage" as Draft Amendment 1 - ISO/IEC 26300:2006/DAM 1) and published in March 2012 as ''ISO/IEC 26300:2006/Amd 1:2012 - Open Document Format for Office Applications (OpenDocument) v1.1''.<ref>{{citation |url=http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=59302 |title=ISO/IEC 26300:2006/Amd 1:2012 - Open Document Format for Office Applications (OpenDocument) v1.1 |date=2012-03-08 |accessdate=2012-04-12}}</ref><ref>{{cite web |url=http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=59302 |title=ISO/IEC 26300:2006/DAM 1 - OpenDocument v1.1 |accessdate=2011-03-29}}</ref>		*'''[http://docs.oasis-open.org/office/v1.1/OS/OpenDocument-v1.1.pdf OpenDocument 1.1]''' includes additional features to address accessibility concerns.<ref>{{cite web | url=http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office#odf11 | title=OpenDocument 1.1 Specifications | year=2006 | accessdate=2006-10-31 | publisher=[[OASIS (organization)|OASIS]]}}</ref> It was approved as an OASIS Standard on 2007-02-01 following a call for vote issued on 2007-01-16.<ref>{{cite web | title=Approval of OpenDocument v1.1 as OASIS Standard | url=http://lists.oasis-open.org/archives/office/200702/msg00003.html | accessdate=2007-02-06 | publisher=[[OASIS (organization)|OASIS]]}}</ref> The public announcement was made on 2007-02-13.<ref>{{cite web | title=Members Approve OpenDocument Version 1.1 as OASIS Standard | url=http://www.oasis-open.org/news/oasis-news-2007-02-14.php | accessdate=2007-02-15 | publisher=[[OASIS (organization)|OASIS]]}}</ref> This version was not initially submitted to ISO/IEC, because it is considered to be a minor update to ODF 1.0 only, and OASIS were working already on ODF 1.2 at the time ODF 1.1 was approved.<ref>[http://www.zdnet.co.uk/talkback/0,1000001161,39409700-39001068c-20093634o,00.htm ZDnet.co.uk]</ref> However it was later submitted to ISO/IEC (as of March 2011, it was in "enquiry stage" as Draft Amendment 1 - ISO/IEC 26300:2006/DAM 1) and published in March 2012 as ''ISO/IEC 26300:2006/Amd 1:2012 - Open Document Format for Office Applications (OpenDocument) v1.1''.<ref>{{citation |url=http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=59302 |title=ISO/IEC 26300:2006/Amd 1:2012 - Open Document Format for Office Applications (OpenDocument) v1.1 |date=2012-03-08 |accessdate=2012-04-12}}</ref><ref>{{cite web |url=http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=59302 |title=ISO/IEC 26300:2006/DAM 1 - OpenDocument v1.1 |accessdate=2011-03-29}}</ref>
−	*'''OpenDocument 1.2''' was approved as an OASIS Committee Specification on {{date|2011-03-17|iso}} and as an OASIS Standard on {{date|2011-09-29|iso}}.<ref>[http://lists.oasis-open.org/archives/office/201103/msg00089.html OASIS office message: Ballot for CS approval of ODF Version 1.2 has passed]</ref><ref name="odf12">{{citation |url=http://www.oasis-open.org/news/pr/odf-1-2-approval |title=Members Approve OpenDocument Format (ODF) Version 1.2 as OASIS Standard |date=2011-10-05 |accessdate=2012-04-12}}</ref><ref>{{citation |url=http://www.oasis-open.org/committees/office/ |title=OASIS Open Document Format for Office Applications (OpenDocument) TC |accessdate=2012-04-12}}</ref> It includes additional accessibility features, [[Resource Description Framework|RDF]]-based metadata, a spreadsheet formula specification based on [[OpenFormula]], support for digital signatures and some features suggested by the public. The OASIS ODF Technical Committee expects to submit the ODF 1.2 to ISO/IEC JTC 1 soon.<ref name="odf12" />	+	*'''OpenDocument 1.2''' was approved as an OASIS Committee Specification on {{date|2011-03-17|iso}} and as an OASIS Standard on {{date|2011-09-29|iso}}.<ref>[http://lists.oasis-open.org/archives/office/201103/msg00089.html OASIS office message: Ballot for CS approval of ODF Version 1.2 has passed]</ref><ref name="odf12">{{citation |url=http://www.oasis-open.org/news/pr/odf-1-2-approval |title=Members Approve OpenDocument Format (ODF) Version 1.2 as OASIS Standard |date=2011-10-05 |accessdate=2012-04-12}}</ref><ref>{{citation |url=http://www.oasis-open.org/committees/office/ |title=OASIS Open Document Format for Office Applications (OpenDocument) TC |accessdate=2012-04-12}}</ref> It includes additional accessibility features, [[Resource Description Framework|RDF]]-based metadata,<ref name="register">{{Cite web|accessdate=18 April 2012|publisher=[[The Register]]|url=http://www.theregister.co.uk/2011/09/12/libreoffice_extensions_and_templates_store_open/|date=3 October 2011|title=Open Document Format updated to fix spreadsheets|first=Gavin|last=Clarke}}</ref> a spreadsheet formula specification based on [[OpenFormula]],<ref name="register" /> support for digital signatures and some features suggested by the public. The OASIS ODF Technical Committee expects to submit the ODF 1.2 to ISO/IEC JTC 1 soon.<ref name="odf12" />
	==Application support==		==Application support==
Line 149:		Line 149:
	*[[Adobe Buzzword]]<ref>{{cite web|url=http://labs.adobe.com/technologies/buzzword/ |title=Adobe Buzzword online word processor from Acrobat.com |publisher=Labs.adobe.com |date= |accessdate=2009-05-19}}</ref>		*[[Adobe Buzzword]]<ref>{{cite web|url=http://labs.adobe.com/technologies/buzzword/ |title=Adobe Buzzword online word processor from Acrobat.com |publisher=Labs.adobe.com |date= |accessdate=2009-05-19}}</ref>
	*[[Atlantis Word Processor]]<ref>[http://www.atlantiswordprocessor.com/en/news/1_6_5.htm Atlantis Word Processor 1.6.5 release notes]. Retrieved 2010-01-28</ref>		*[[Atlantis Word Processor]]<ref>[http://www.atlantiswordprocessor.com/en/news/1_6_5.htm Atlantis Word Processor 1.6.5 release notes]. Retrieved 2010-01-28</ref>
−	* [http://www.aspose.com/categories/file-format-components/aspose.words-for-.net-and-java/default.aspx Aspose.Words] is a component/library available for both .NET and Java platforms which enables opening and saving OpenDocument text (ODT) documents.
	*[[Calligra Suite]]<ref>{{cite web|url=http://www.calligra-suite.org/words/ |title=Words |publisher=Calligra Suite |date= |accessdate=2012-02-23}}</ref>		*[[Calligra Suite]]<ref>{{cite web|url=http://www.calligra-suite.org/words/ |title=Words |publisher=Calligra Suite |date= |accessdate=2012-02-23}}</ref>
	*[[Corel Corporation|Corel]] [[Corel WordPerfect Office|WordPerfect Office X4]]<ref>{{cite web		*[[Corel Corporation|Corel]] [[Corel WordPerfect Office|WordPerfect Office X4]]<ref>{{cite web
Line 156:		Line 155:
	|accessdate=2008-05-03}}</ref>		|accessdate=2008-05-03}}</ref>
	*[[Evince]]		*[[Evince]]
−	*[[Google Docs]]<ref>[http://www.google.com/support/forum/p/Google+Docs/thread?tid=014457aa446500fa&hl=en Google.com]</ref>	+	*[[Google Docs]]<ref name="register" /><ref>[http://www.google.com/support/forum/p/Google+Docs/thread?tid=014457aa446500fa&hl=en Google.com]</ref>
	*[[Gnumeric]]<ref>[http://projects.gnome.org/gnumeric/doc/sect-file-formats.shtml Gnumeric.org]</ref>		*[[Gnumeric]]<ref>[http://projects.gnome.org/gnumeric/doc/sect-file-formats.shtml Gnumeric.org]</ref>
−	*[[IBM Lotus Symphony]]<ref>[http://blogs.msdn.com/dmahugh/archive/2009/05/09/1-2-1.aspx Blogs.MSDN.com]</ref><ref>[http://symphony.lotus.com/software/lotus/symphony/help.nsf/ReleaseNotes Symphony.lotus.com]</ref>	+	*[[IBM Lotus Symphony]]<ref name="register" /><ref>[http://blogs.msdn.com/dmahugh/archive/2009/05/09/1-2-1.aspx Blogs.MSDN.com]</ref><ref>[http://symphony.lotus.com/software/lotus/symphony/help.nsf/ReleaseNotes Symphony.lotus.com]</ref>
	*[[Inkscape]] exports .odg		*[[Inkscape]] exports .odg
	*[[KOffice]]<ref>[http://koffice.org/filters/1.6/ Koffice.org]</ref>		*[[KOffice]]<ref>[http://koffice.org/filters/1.6/ Koffice.org]</ref>
−	*[[LibreOffice]]	+	*[[LibreOffice]]<ref name="register" />
	*[[Microsoft Office 2007]] (from service pack 2 release)<ref>[http://www.microsoft.com/Presspass/press/2008/may08/05-21ExpandedFormatsPR.mspx Microsoft Expands List of Formats Supported in Microsoft Office]</ref>		*[[Microsoft Office 2007]] (from service pack 2 release)<ref>[http://www.microsoft.com/Presspass/press/2008/may08/05-21ExpandedFormatsPR.mspx Microsoft Expands List of Formats Supported in Microsoft Office]</ref>
	*[[Microsoft Office 2010]]		*[[Microsoft Office 2010]]
	*[[NeoOffice]]		*[[NeoOffice]]
	*[[Okular]]		*[[Okular]]
−	*[[OpenOffice.org]]	+	*[[OpenOffice.org]]<ref name="register" />
	*[[Scribus]] imports .odt and .odg		*[[Scribus]] imports .odt and .odg
	*[[SoftMaker Office]]		*[[SoftMaker Office]]
	*[[Sun Microsystems]] [[StarOffice]]		*[[Sun Microsystems]] [[StarOffice]]
	*[[WordPad]] 6.1 (Windows 7) partial support.		*[[WordPad]] 6.1 (Windows 7) partial support.
−	*[[Zoho Office Suite]]	+	*[[Zoho Office Suite]]<ref name="register" />
	Various organizations have announced development of conversion software (including ''plugins'' and ''filters'') to support OpenDocument on [[Microsoft]]'s products.<ref>{{cite web | url=http://www.groklaw.net/article.php?story=20060504015438308 | title=OpenDocument Foundation to MA: We Have a Plugin | date=2006-05-04 | accessdate=2006-08-23 | publisher=Groklaw}}</ref><ref>{{cite news | url=http://www.zdnet.com.au/news/software/soa/Microsoft_Office_to_get_a_dose_of_OpenDocument/0,130061733,139255766,00.htm | title=Microsoft Office to get a dose of OpenDocument | date=2006-05-05 | accessdate=2006-12-06|publisher=CNet}}</ref> {{asof|July 2007}}, there are nine packages of conversion software.<!--Commented out invalid reference <ref name="odf20070727"/>--> Microsoft first released support for the OpenDocument Format in Office 2007 SP2.<ref>{{cite web | title=Office 2007 SP2 Supports ODF | url=http://www.pcworld.com/businesscenter/article/164015/office_2007_sp2_supports_odf.html | date=April 28, 2009 | publisher=PC World}}</ref> However, the implementation faced [[OpenDocument software#Microsoft Office 2007 SP2 support controversy|substantial criticism]] and the [[ODF Alliance]] and others claimed that the third party plugins provided better support.<ref name="sp2-fact-sheet">{{cite web | url=http://www.odfalliance.org/resources/fact-sheet-Microsoft-ODF-support.pdf | title=Fact-sheet Microsoft ODF support | accessdate=2009-05-24 | quote=''MS Excel 2007 will process ODF spreadsheet documents when loaded via the Sun Plug-In 3.0 for MS Office or the SourceForge “OpenXML/ODF Translator Add-in for Office,” but will fail when using the “built-in” support provided by Office 2007 SP2.'' | publisher=odfalliance}}</ref> Microsoft Office 2010 can open and save OpenDocument Format documents natively, although not all features are fully supported.<ref>[http://office.microsoft.com/en-us/starter-help/differences-between-the-opendocument-text-odt-format-and-the-word-docx-format-HA010355788.aspx Differences between the OpenDocument Text (.odt) format and the Word (.docx) format]</ref>		Various organizations have announced development of conversion software (including ''plugins'' and ''filters'') to support OpenDocument on [[Microsoft]]'s products.<ref>{{cite web | url=http://www.groklaw.net/article.php?story=20060504015438308 | title=OpenDocument Foundation to MA: We Have a Plugin | date=2006-05-04 | accessdate=2006-08-23 | publisher=Groklaw}}</ref><ref>{{cite news | url=http://www.zdnet.com.au/news/software/soa/Microsoft_Office_to_get_a_dose_of_OpenDocument/0,130061733,139255766,00.htm | title=Microsoft Office to get a dose of OpenDocument | date=2006-05-05 | accessdate=2006-12-06|publisher=CNet}}</ref> {{asof|July 2007}}, there are nine packages of conversion software.<!--Commented out invalid reference <ref name="odf20070727"/>--> Microsoft first released support for the OpenDocument Format in Office 2007 SP2.<ref>{{cite web | title=Office 2007 SP2 Supports ODF | url=http://www.pcworld.com/businesscenter/article/164015/office_2007_sp2_supports_odf.html | date=April 28, 2009 | publisher=PC World}}</ref> However, the implementation faced [[OpenDocument software#Microsoft Office 2007 SP2 support controversy|substantial criticism]] and the [[ODF Alliance]] and others claimed that the third party plugins provided better support.<ref name="sp2-fact-sheet">{{cite web | url=http://www.odfalliance.org/resources/fact-sheet-Microsoft-ODF-support.pdf | title=Fact-sheet Microsoft ODF support | accessdate=2009-05-24 | quote=''MS Excel 2007 will process ODF spreadsheet documents when loaded via the Sun Plug-In 3.0 for MS Office or the SourceForge “OpenXML/ODF Translator Add-in for Office,” but will fail when using the “built-in” support provided by Office 2007 SP2.'' | publisher=odfalliance}}</ref> Microsoft Office 2010 can open and save OpenDocument Format documents natively, although not all features are fully supported.<ref>[http://office.microsoft.com/en-us/starter-help/differences-between-the-opendocument-text-odt-format-and-the-word-docx-format-HA010355788.aspx Differences between the OpenDocument Text (.odt) format and the Word (.docx) format]</ref>

Ghacks Technology News

SkyDrive Gets ODF Support, More Features Ahead of Google Drive Launch Ghacks Technology News The service now supports file uploads of up to 300 Megabyte in the web browser (2 Gigabyte syncing from the desktop, at least under Windows 8), as well as the Open Document Format, short url support for Windows Phone images shared to Twitter, ... and more »

SkyDrive Updated with Support for ODF, 300MB Browser Uploads and Short URLs Technology Bites Microsoft announced new features today including support for Open Document Format (ODF), 300 MB browser uploads and short URLs for SkyDrive images. These features may not be big but Microsoft teases us with a promise that really big things are coming ...

Ghacks Technology News

SkyDrive updated to include 300MB browser uploads, short URLs for Windows ... The Verge SkyDrive now supports the Open Document Format (ODF), an XML-based file format supported in a number of word processing apps including Microsoft Office, OpenOffice, and Corel's WordPerfect. Although ODF support is the more noteworthy addition to ... SkyDrive Gets ODF Support, More Features Ahead of Google Drive LaunchGhacks Technology News all 5 news articles »

MSFT Office, OpenOffice.org, LibreOffice.org & now Calligra-Suite.org ComputerWeekly.com (blog) Originally part of KDE graphical desktop environment for Unix workstations and now other operating systems, the Calligra Project has produced a full suite of Office-style productivity apps that are Open Document Format (ODF) and Microsoft Office ... and more »

Since version 8.1 of Tiki Wiki CMS Groupware (usually simply called Tiki) was released, it is possible to edit ODF documents in Tiki. This is possible because WebODF has been added to Tiki8 as a new feature, called Tiki Docs. With this, Tiki joins the growing list of applications that use WebODF.

Tiki can open and show documents with WebODF, but more, it allows editing and saving. Each time you save, a new revision created and stored just like normal wiki pages. This means that you can always go back to earlier versions of the document. Downloading and uploading is also possible if you prefer to edit the documents in a native text editor like Calligra or OpenOffice/LibreOffice.

Calligra Project open source office suite released SmartCompany.com.au These apps use Open Document Format (ODF) and are Microsoft Office compatible. Aside from the desktop version – known as Calligra Suite – the Calligra team have also released a mobile version for Nokia's N900 smartphone (Calligra Mobile) and a document ... Try Calligra 2.4 for a New Microsoft Office AlternativePCWorld First Release of Calligra Office Suite now AvailableDigit all 6 news articles »

added OpenDocument urls

← Previous revision		Revision as of 14:20, 15 April 2012
Line 27:		Line 27:
	| standard = OASIS OpenDocument Format, ISO/IEC 26300:2006		| standard = OASIS OpenDocument Format, ISO/IEC 26300:2006
	| free = [[OpenDocument#Licensing|Yes]]		| free = [[OpenDocument#Licensing|Yes]]
−	| url =	+	| url = [http://www.oasis-open.org/committees/office/ OASIS], [http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_tc_browse.htm?commid=45374 ISO/IEC]
	}}		}}
	{{Infobox file format		{{Infobox file format

added OpenDocument version information to infoboxes

← Previous revision		Revision as of 13:52, 15 April 2012
Line 17:		Line 17:
	| magic =		| magic =
	| owner = [[OASIS (organization)|OASIS]]		| owner = [[OASIS (organization)|OASIS]]
−	| released =	+	| released = {{Start date and age|2005|05|01|df=yes}}
−	| latest release version =	+	| latest release version = 1.2
−	| latest release date =	+	| latest release date = {{Start date and age|2011|09|29|df=yes}}
	| genre = [[Document file format]]		| genre = [[Document file format]]
	| container for =		| container for =
Line 42:		Line 42:
	| magic =		| magic =
	| owner = [[OASIS (organization)|OASIS]]		| owner = [[OASIS (organization)|OASIS]]
−	| released =	+	| released = {{Start date and age|2005|05|01|df=no}}
−	| latest release version =	+	| latest release version = 1.2
−	| latest release date =	+	| latest release date = {{Start date and age|2011|09|29|df=yes}}
	| genre = [[Presentation]]		| genre = [[Presentation]]
	| container for =		| container for =
Line 50:		Line 50:
	| extended from = [[XML]]		| extended from = [[XML]]
	| extended to =		| extended to =
−	| standard = ISO/IEC 26300:2006	+	| standard = OASIS OpenDocument Format, ISO/IEC 26300:2006
	| free = [[OpenDocument#Licensing|Yes]]		| free = [[OpenDocument#Licensing|Yes]]
	| url =		| url =
Line 67:		Line 67:
	| magic =		| magic =
	| owner = [[OASIS (organization)|OASIS]]		| owner = [[OASIS (organization)|OASIS]]
−	| released =	+	| released = {{Start date and age|2005|05|01|df=no}}
−	| latest release version =	+	| latest release version = 1.2
−	| latest release date =	+	| latest release date = {{Start date and age|2011|09|29|df=yes}}
	| genre = [[Spreadsheet]]		| genre = [[Spreadsheet]]
	| container for =		| container for =
Line 92:		Line 92:
	| magic =		| magic =
	| owner = [[OASIS (organization)|OASIS]]		| owner = [[OASIS (organization)|OASIS]]
−	| released =	+	| released = {{Start date and age|2005|05|01|df=no}}
−	| latest release version =	+	| latest release version = 1.2
−	| latest release date =	+	| latest release date = {{Start date and age|2011|09|29|df=yes}}
	| genre = [[Graphics file format]]		| genre = [[Graphics file format]]
	| container for =		| container for =
Line 100:		Line 100:
	| extended from = [[XML]]		| extended from = [[XML]]
	| extended to =		| extended to =
−	| standard = ISO/IEC 26300:2006	+	| standard = OASIS OpenDocument Format, ISO/IEC 26300:2006
	| free = [[OpenDocument#Licensing|Yes]]		| free = [[OpenDocument#Licensing|Yes]]
	| url =		| url =

At Calligra we are mising several icons, including several applications icons.

So we are seeking an artist that are capable of creating oxygen compatible icons.

You will become a member of our very cool community, and take part of the revolution we are determined to make in the world of office and creative applications.

Contact us on irc channel #calligra or on our mailing list calligra-devel at kde.org

First Release of Calligra Office Suite now Available Digit The UI for most applications has been simplified, support for the ODF format has been improved, and the suite now handles Microsoft formats better. One of the most interesting developments though is the availability of mobile and tablet versions of the ...

Point dead link to the Waybaack Machine

← Previous revision		Revision as of 15:19, 14 April 2012
Line 211:		Line 211:
	=== Criticism ===		=== Criticism ===
−	*Different applications using ODF as a standard document format have different methods of providing macro/scripting capabilities. There is no [[macro language]] specified in ODF. Users and developers differ on whether inclusion of a standard scripting language would be desirable.<ref>{{cite web | url=http://www.linux.com/articles/47935 | title=Macros an obstacle to office suite compatibility | author=Marco Fioretti | accessdate=2008-05-11}} {{Dead link|date=April 2012}}</ref>	+	*Different applications using ODF as a standard document format have different methods of providing macro/scripting capabilities. There is no [[macro language]] specified in ODF. Users and developers differ on whether inclusion of a standard scripting language would be desirable.<ref>{{cite web | url=http://web.archive.org/web/20110521183559/http://www.linux.com/archive/articles/47935 | title=Macros an obstacle to office suite compatibility | author=Marco Fioretti | accessdate=2008-05-11}}</ref>
	* The ODF specification for tracked changes is limited and does not fully specify all cases, resulting in implementation-specific behaviors.<ref>{{cite web | url=http://blogs.msdn.com/dmahugh/archive/2009/05/13/tracked-changes.aspx | title=Tracked Changes | author=Doug Mahugh (Microsoft) | date=2009-05-13}}</ref> In addition, OpenDocument does not support change tracking in elements like tables or [[MathML]].<ref name="doyourmath">{{cite web | url=http://idippedut.dk/post/2008/01/29/Do-your-math-OOXML-and-OMML.aspx | title=Do your math - OOXML and OMML (Updated 2008-02-12) | author=Jesper Lund Stocholm (Danish ISO/IEC representative) | date=2008-12-12}}</ref>		* The ODF specification for tracked changes is limited and does not fully specify all cases, resulting in implementation-specific behaviors.<ref>{{cite web | url=http://blogs.msdn.com/dmahugh/archive/2009/05/13/tracked-changes.aspx | title=Tracked Changes | author=Doug Mahugh (Microsoft) | date=2009-05-13}}</ref> In addition, OpenDocument does not support change tracking in elements like tables or [[MathML]].<ref name="doyourmath">{{cite web | url=http://idippedut.dk/post/2008/01/29/Do-your-math-OOXML-and-OMML.aspx | title=Do your math - OOXML and OMML (Updated 2008-02-12) | author=Jesper Lund Stocholm (Danish ISO/IEC representative) | date=2008-12-12}}</ref>
	* It is not permitted to use generic ODF formatting style elements (like font information) for the MathML elements.<ref name="doyourmath"/>		* It is not permitted to use generic ODF formatting style elements (like font information) for the MathML elements.<ref name="doyourmath"/>

Calligra 2.4 est sortie LinuxFr Calligra est issu d'un fork de Koffice et prend en charge les format ODF (comme OpenOffice.org et LibreOffice) pour les applications où un tel format de stockage est défini. C'est la première version stable de Calligra et la première version pour ...

Try Calligra 2.4 for a New Microsoft Office Alternative PCWorld Because Calligra uses ODF, it's compatible with most other office applications, including OpenOffice.org, LibreOffice, and Microsoft Office. In fact, “it can also import the native file formats of Microsoft Office with great accuracy, in many cases the ... Calligra Project open source office suite releasedSmartCompany.com.au First Release of Calligra Office Suite now AvailableDigit all 6 news articles »

As the avid readers of Planet KDE and the Dot can hardly have missed, Calligra made its first real release this week. This release has been long in coming - we started the Calligra project almost one and a half years ago, which is a long time for free software. But the release made the wait worth it: Two new applications, a completely rewritten text layout engine that doesn't prevent showing of any feature in ODF, improved filters, etc, etc. Not bad...

And most important of all: This release is the foundation of the things to come. We took a long time to get it out because we wanted the foundation to be strong enough so that we can build a sky scraper on top of it. From now on we will release new versions every 4 months and make the process more incremental.

We will do this by adopting a stricter policy for committing into the master branch so that in principle it stays releasable all the time. The basic rules will most likely look like this. Allowed into master are:

• single commit bug fixes

• merges from feature branches or single commit features

To sum up the status of Calligra right now you can say that we have a really strong foundation (meaning we can load/render/save most of ODF) but a weaker user interface. In other words, the engine can handle many things that are not yet possible for the user to manipulate using our UI.

So that brings us to the question in the title: Which features are most important to implement in the UI at this point? Also, which bugs are the most irritating for you? Let us know through bugs and wishes at http://bugs.kde.org/ ! You can find all the Calligra applications as calligrasomething where something is the name of the application.

You can of course also write comments to this blog entry but it is not guaranteed that the team will read them.

One thing that we already know will be part of 2.5 is improved manipulation of text tables since boemann, the Calligra Words maintainer, blogged about it. Of course I have my own pet list of things to improve but that's not the point of this post so I won't list it here.

Freie Software: Bürosuite Calligra in erster stabiler Version veröffentlicht PC Magazin Calligra setzt auf das OpenDocument-Format (ODF) auf und erlaubt so Kompatibilität mit anderen Suiten wie OpenOffice.org, LibreOffice und Microsoft Office. Um die fortgeschrittenen Eigenschaften von ODF nutzen zu können, wurde die Textlayout-Engine ... Erste stabile Version von Calligra veröffentlichtPro-Linux all 3 news articles »

Microsoft Open Technologies, Inc.: una sussidiaria per l'open source Ossblog.it (Blog) Quest'ultima, espressamente citata da Paoli, è l'organizzazione che gestisce Open Document Format (ODF). Microsoft gli oppone Office Open XML (OOXML), come potrà risolvere il conflitto? Riguardo a Windows Phone, Paoli parla del supporto a PhoneGap: il ... and more »

OpenOffice and LibreOffice have the ability to run macros. These macros can be written in a number of programming languages. The most common one is called OpenOffice Basic or LibreOffice Basic. For this language there is a built-in editor. It is also possible to record macros in Basic and edit them afterwards.

OpenOffice Basic or LibreOffice Basic is not standardized in the OpenDocument Format (ODF). ODF does not standardize on any programming language for use in the macros. In fact, in LibreOffice/OpenOffice, one can use Basic, Python, Java and JavaScript.

Calligra is an integrated suite of applications that cover office, creative, and management needs. It offers applications on both desktop computers and mobile platforms like tablets and smartphones. OpenDocument Format (ODF) is used, making it compatible with OpenOffice.org, LibreOffice, and Microsoft Office. Calligra Suite contains the following applications: Calligra Words (word processor), Sheets (spreadsheets), Stage (presentations), Flow (diagrams and flowcharts), Kexi (visual database creator), Braindump (note taking), Plan (project management), Krita (drawing), and Karbon (vector graphics).

Release Notes: This is the first release of Calligra and is a continuation of the old KOffice project. It features a completely rewritten text layout engine that can handle most of the advanced layout features of ODF. This includes tables that span more than one page, footnotes and endnotes, and correct run around objects such as pictures. The user interface is simplified. New applications in this release are Flow, the diagram application, and Braindump, for note taking.

Release Tags: Stable, Major feature enchancements, major bug fixes

Tags: KDE, Qt, Office, Office Suites, Office/Business, ODF, OpenDocument Format, Word Processors, Spreadsheet, Presentation, Flowcharts, diagrams, Databases, drawing, Graphics, project management

Licenses: GPL, GPLv2, LGPL

Calligra 2.4 è al primo rilascio stabile: KOffice è stato sostituito Ossblog.it (Blog) I responsabili del progetto vantano un sistema di filtri per i formati proprietari di Microsoft tra i più efficienti e garantiscono una migliore interpretazione di Open Document Format (ODF). Il prototipo per Android, al pari di LibreOffice, ...

‎Standardization: ISO/IEC 26300:2006/Amd 1:2012 - Open Document Format for Office Applications (OpenDocument) v1.1 published

← Previous revision		Revision as of 12:37, 12 April 2012
Line 136:		Line 136:
	Further standardization work with OpenDocument includes:		Further standardization work with OpenDocument includes:
−	*The OASIS Committee Specification [http://www.oasis-open.org/committees/download.php/19274/OpenDocument-v1.0ed2-cs1.pdf OpenDocument 1.0 (second edition)] corresponds to the published ISO/IEC 26300:2006 standard. The content of ISO/IEC 26300 and OASIS OpenDocument v1.0 2nd ed. is identical.<ref>{{citation |url=http://standards.iso.org/ittf/PubliclyAvailableStandards/c043485_ISO_IEC_26300_2006(E).zip |title=ISO/IEC 26300:2006 |format=ZIP, PDF |publisher=ISO |accessdate=2009-11-22}}</ref> It includes the editorial changes made to address JTC1 ballot comments. It is available in ODF, HTML and PDF formats.	+	*The OASIS Committee Specification [http://www.oasis-open.org/committees/download.php/19274/OpenDocument-v1.0ed2-cs1.pdf '''OpenDocument 1.0''' (second edition)] corresponds to the published ISO/IEC 26300:2006 standard. The content of ISO/IEC 26300 and OASIS OpenDocument v1.0 2nd ed. is identical.<ref>{{citation |url=http://standards.iso.org/ittf/PubliclyAvailableStandards/c043485_ISO_IEC_26300_2006(E).zip |title=ISO/IEC 26300:2006 |format=ZIP, PDF |publisher=ISO |accessdate=2009-11-22}}</ref> It includes the editorial changes made to address JTC1 ballot comments. It is available in ODF, HTML and PDF formats.
−	*[http://docs.oasis-open.org/office/v1.1/OS/OpenDocument-v1.1.pdf OpenDocument 1.1] includes additional features to address accessibility concerns.<ref>{{cite web | url=http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office#odf11 | title=OpenDocument 1.1 Specifications | year=2006 | accessdate=2006-10-31 | publisher=[[OASIS (organization)|OASIS]]}}</ref> It was approved as an OASIS Standard on 2007-02-01 following a call for vote issued on 2007-01-16.<ref>{{cite web | title=Approval of OpenDocument v1.1 as OASIS Standard | url=http://lists.oasis-open.org/archives/office/200702/msg00003.html | accessdate=2007-02-06 | publisher=[[OASIS (organization)|OASIS]]}}</ref> The public announcement was made on 2007-02-13.<ref>{{cite web | title=Members Approve OpenDocument Version 1.1 as OASIS Standard | url=http://www.oasis-open.org/news/oasis-news-2007-02-14.php | accessdate=2007-02-15 | publisher=[[OASIS (organization)|OASIS]]}}</ref> This version was not initially submitted to ISO/IEC, because it is considered to be a minor update to ODF 1.0 only, and OASIS were working already on ODF 1.2 at the time ODF 1.1 was approved.<ref>[http://www.zdnet.co.uk/talkback/0,1000001161,39409700-39001068c-20093634o,00.htm ZDnet.co.uk]</ref> However it was later submitted to ISO/IEC and as of March 2011, it is in "enquiry stage" as Draft Amendment 1 (ISO/IEC 26300:2006/DAM 1).<ref>{{cite web |url=http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=59302 |title=ISO/IEC 26300:2006/DAM 1 - OpenDocument v1.1 |accessdate=2011-03-29}}</ref>	+	*'''[http://docs.oasis-open.org/office/v1.1/OS/OpenDocument-v1.1.pdf OpenDocument 1.1]''' includes additional features to address accessibility concerns.<ref>{{cite web | url=http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office#odf11 | title=OpenDocument 1.1 Specifications | year=2006 | accessdate=2006-10-31 | publisher=[[OASIS (organization)|OASIS]]}}</ref> It was approved as an OASIS Standard on 2007-02-01 following a call for vote issued on 2007-01-16.<ref>{{cite web | title=Approval of OpenDocument v1.1 as OASIS Standard | url=http://lists.oasis-open.org/archives/office/200702/msg00003.html | accessdate=2007-02-06 | publisher=[[OASIS (organization)|OASIS]]}}</ref> The public announcement was made on 2007-02-13.<ref>{{cite web | title=Members Approve OpenDocument Version 1.1 as OASIS Standard | url=http://www.oasis-open.org/news/oasis-news-2007-02-14.php | accessdate=2007-02-15 | publisher=[[OASIS (organization)|OASIS]]}}</ref> This version was not initially submitted to ISO/IEC, because it is considered to be a minor update to ODF 1.0 only, and OASIS were working already on ODF 1.2 at the time ODF 1.1 was approved.<ref>[http://www.zdnet.co.uk/talkback/0,1000001161,39409700-39001068c-20093634o,00.htm ZDnet.co.uk]</ref> However it was later submitted to ISO/IEC (as of March 2011, it was in "enquiry stage" as Draft Amendment 1 - ISO/IEC 26300:2006/DAM 1) and published in March 2012 as ''ISO/IEC 26300:2006/Amd 1:2012 - Open Document Format for Office Applications (OpenDocument) v1.1''.<ref>{{citation |url=http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=59302 |title=ISO/IEC 26300:2006/Amd 1:2012 - Open Document Format for Office Applications (OpenDocument) v1.1 |date=2012-03-08 |accessdate=2012-04-12}}</ref><ref>{{cite web |url=http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=59302 |title=ISO/IEC 26300:2006/DAM 1 - OpenDocument v1.1 |accessdate=2011-03-29}}</ref>
−	*OpenDocument 1.2 was approved as an OASIS Committee Specification on {{date|2011-03-17|iso}} and as an OASIS Standard on 29 September 2011.<ref>[http://lists.oasis-open.org/archives/office/201103/msg00089.html OASIS office message: Ballot for CS approval of ODF Version 1.2 has passed]</ref><ref name="odf12">{{citation |url=http://www.oasis-open.org/news/pr/odf-1-2-approval |title=Members Approve OpenDocument Format (ODF) Version 1.2 as OASIS Standard |date=2011-10-05 |accessdate=2012-04-12}}</ref><ref>{{citation |url=http://www.oasis-open.org/committees/office/ |title=OASIS Open Document Format for Office Applications (OpenDocument) TC |accessdate=2012-04-12}}</ref> It includes additional accessibility features, [[Resource Description Framework|RDF]]-based metadata, a spreadsheet formula specification based on [[OpenFormula]], support for digital signatures and some features suggested by the public. The OASIS ODF Technical Committee expects to submit the ODF 1.2 to ISO/IEC JTC 1 soon.<ref name="odf12" />	+	*'''OpenDocument 1.2''' was approved as an OASIS Committee Specification on {{date|2011-03-17|iso}} and as an OASIS Standard on {{date|2011-09-29|iso}}.<ref>[http://lists.oasis-open.org/archives/office/201103/msg00089.html OASIS office message: Ballot for CS approval of ODF Version 1.2 has passed]</ref><ref name="odf12">{{citation |url=http://www.oasis-open.org/news/pr/odf-1-2-approval |title=Members Approve OpenDocument Format (ODF) Version 1.2 as OASIS Standard |date=2011-10-05 |accessdate=2012-04-12}}</ref><ref>{{citation |url=http://www.oasis-open.org/committees/office/ |title=OASIS Open Document Format for Office Applications (OpenDocument) TC |accessdate=2012-04-12}}</ref> It includes additional accessibility features, [[Resource Description Framework|RDF]]-based metadata, a spreadsheet formula specification based on [[OpenFormula]], support for digital signatures and some features suggested by the public. The OASIS ODF Technical Committee expects to submit the ODF 1.2 to ISO/IEC JTC 1 soon.<ref name="odf12" />
	==Application support==		==Application support==

‎Standardization: The OASIS ODF Technical Committee expects to submit the ODF 1.2 to ISO/IEC JTC 1 soon.

← Previous revision		Revision as of 12:13, 12 April 2012
Line 138:		Line 138:
	*The OASIS Committee Specification [http://www.oasis-open.org/committees/download.php/19274/OpenDocument-v1.0ed2-cs1.pdf OpenDocument 1.0 (second edition)] corresponds to the published ISO/IEC 26300:2006 standard. The content of ISO/IEC 26300 and OASIS OpenDocument v1.0 2nd ed. is identical.<ref>{{citation |url=http://standards.iso.org/ittf/PubliclyAvailableStandards/c043485_ISO_IEC_26300_2006(E).zip |title=ISO/IEC 26300:2006 |format=ZIP, PDF |publisher=ISO |accessdate=2009-11-22}}</ref> It includes the editorial changes made to address JTC1 ballot comments. It is available in ODF, HTML and PDF formats.		*The OASIS Committee Specification [http://www.oasis-open.org/committees/download.php/19274/OpenDocument-v1.0ed2-cs1.pdf OpenDocument 1.0 (second edition)] corresponds to the published ISO/IEC 26300:2006 standard. The content of ISO/IEC 26300 and OASIS OpenDocument v1.0 2nd ed. is identical.<ref>{{citation |url=http://standards.iso.org/ittf/PubliclyAvailableStandards/c043485_ISO_IEC_26300_2006(E).zip |title=ISO/IEC 26300:2006 |format=ZIP, PDF |publisher=ISO |accessdate=2009-11-22}}</ref> It includes the editorial changes made to address JTC1 ballot comments. It is available in ODF, HTML and PDF formats.
	*[http://docs.oasis-open.org/office/v1.1/OS/OpenDocument-v1.1.pdf OpenDocument 1.1] includes additional features to address accessibility concerns.<ref>{{cite web | url=http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office#odf11 | title=OpenDocument 1.1 Specifications | year=2006 | accessdate=2006-10-31 | publisher=[[OASIS (organization)|OASIS]]}}</ref> It was approved as an OASIS Standard on 2007-02-01 following a call for vote issued on 2007-01-16.<ref>{{cite web | title=Approval of OpenDocument v1.1 as OASIS Standard | url=http://lists.oasis-open.org/archives/office/200702/msg00003.html | accessdate=2007-02-06 | publisher=[[OASIS (organization)|OASIS]]}}</ref> The public announcement was made on 2007-02-13.<ref>{{cite web | title=Members Approve OpenDocument Version 1.1 as OASIS Standard | url=http://www.oasis-open.org/news/oasis-news-2007-02-14.php | accessdate=2007-02-15 | publisher=[[OASIS (organization)|OASIS]]}}</ref> This version was not initially submitted to ISO/IEC, because it is considered to be a minor update to ODF 1.0 only, and OASIS were working already on ODF 1.2 at the time ODF 1.1 was approved.<ref>[http://www.zdnet.co.uk/talkback/0,1000001161,39409700-39001068c-20093634o,00.htm ZDnet.co.uk]</ref> However it was later submitted to ISO/IEC and as of March 2011, it is in "enquiry stage" as Draft Amendment 1 (ISO/IEC 26300:2006/DAM 1).<ref>{{cite web |url=http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=59302 |title=ISO/IEC 26300:2006/DAM 1 - OpenDocument v1.1 |accessdate=2011-03-29}}</ref>		*[http://docs.oasis-open.org/office/v1.1/OS/OpenDocument-v1.1.pdf OpenDocument 1.1] includes additional features to address accessibility concerns.<ref>{{cite web | url=http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office#odf11 | title=OpenDocument 1.1 Specifications | year=2006 | accessdate=2006-10-31 | publisher=[[OASIS (organization)|OASIS]]}}</ref> It was approved as an OASIS Standard on 2007-02-01 following a call for vote issued on 2007-01-16.<ref>{{cite web | title=Approval of OpenDocument v1.1 as OASIS Standard | url=http://lists.oasis-open.org/archives/office/200702/msg00003.html | accessdate=2007-02-06 | publisher=[[OASIS (organization)|OASIS]]}}</ref> The public announcement was made on 2007-02-13.<ref>{{cite web | title=Members Approve OpenDocument Version 1.1 as OASIS Standard | url=http://www.oasis-open.org/news/oasis-news-2007-02-14.php | accessdate=2007-02-15 | publisher=[[OASIS (organization)|OASIS]]}}</ref> This version was not initially submitted to ISO/IEC, because it is considered to be a minor update to ODF 1.0 only, and OASIS were working already on ODF 1.2 at the time ODF 1.1 was approved.<ref>[http://www.zdnet.co.uk/talkback/0,1000001161,39409700-39001068c-20093634o,00.htm ZDnet.co.uk]</ref> However it was later submitted to ISO/IEC and as of March 2011, it is in "enquiry stage" as Draft Amendment 1 (ISO/IEC 26300:2006/DAM 1).<ref>{{cite web |url=http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=59302 |title=ISO/IEC 26300:2006/DAM 1 - OpenDocument v1.1 |accessdate=2011-03-29}}</ref>
−	*OpenDocument 1.2 was approved as an OASIS Committee Specification on {{date|2011-03-17|iso}} and as an OASIS Standard on 29 September 2011.<ref>[http://lists.oasis-open.org/archives/office/201103/msg00089.html OASIS office message: Ballot for CS approval of ODF Version 1.2 has passed]</ref><ref>{{citation |url=http://www.oasis-open.org/news/pr/odf-1-2-approval |title=Members Approve OpenDocument Format (ODF) Version 1.2 as OASIS Standard |date=2011-10-05 |accessdate=2012-04-12}}</ref><ref>{{citation |url=http://www.oasis-open.org/committees/office/ |title=OASIS Open Document Format for Office Applications (OpenDocument) TC |accessdate=2012-04-12}}</ref> It includes additional accessibility features, [[Resource Description Framework|RDF]]-based metadata, a spreadsheet formula specification based on [[OpenFormula]], support for digital signatures and some features suggested by the public.	+	*OpenDocument 1.2 was approved as an OASIS Committee Specification on {{date|2011-03-17|iso}} and as an OASIS Standard on 29 September 2011.<ref>[http://lists.oasis-open.org/archives/office/201103/msg00089.html OASIS office message: Ballot for CS approval of ODF Version 1.2 has passed]</ref><ref name="odf12">{{citation |url=http://www.oasis-open.org/news/pr/odf-1-2-approval |title=Members Approve OpenDocument Format (ODF) Version 1.2 as OASIS Standard |date=2011-10-05 |accessdate=2012-04-12}}</ref><ref>{{citation |url=http://www.oasis-open.org/committees/office/ |title=OASIS Open Document Format for Office Applications (OpenDocument) TC |accessdate=2012-04-12}}</ref> It includes additional accessibility features, [[Resource Description Framework|RDF]]-based metadata, a spreadsheet formula specification based on [[OpenFormula]], support for digital signatures and some features suggested by the public. The OASIS ODF Technical Committee expects to submit the ODF 1.2 to ISO/IEC JTC 1 soon.<ref name="odf12" />
	==Application support==		==Application support==

‎Standardization: ODF 1.2 finally approved on 29 September 2011 as an OASIS Standard

← Previous revision		Revision as of 11:58, 12 April 2012
Line 138:		Line 138:
	*The OASIS Committee Specification [http://www.oasis-open.org/committees/download.php/19274/OpenDocument-v1.0ed2-cs1.pdf OpenDocument 1.0 (second edition)] corresponds to the published ISO/IEC 26300:2006 standard. The content of ISO/IEC 26300 and OASIS OpenDocument v1.0 2nd ed. is identical.<ref>{{citation |url=http://standards.iso.org/ittf/PubliclyAvailableStandards/c043485_ISO_IEC_26300_2006(E).zip |title=ISO/IEC 26300:2006 |format=ZIP, PDF |publisher=ISO |accessdate=2009-11-22}}</ref> It includes the editorial changes made to address JTC1 ballot comments. It is available in ODF, HTML and PDF formats.		*The OASIS Committee Specification [http://www.oasis-open.org/committees/download.php/19274/OpenDocument-v1.0ed2-cs1.pdf OpenDocument 1.0 (second edition)] corresponds to the published ISO/IEC 26300:2006 standard. The content of ISO/IEC 26300 and OASIS OpenDocument v1.0 2nd ed. is identical.<ref>{{citation |url=http://standards.iso.org/ittf/PubliclyAvailableStandards/c043485_ISO_IEC_26300_2006(E).zip |title=ISO/IEC 26300:2006 |format=ZIP, PDF |publisher=ISO |accessdate=2009-11-22}}</ref> It includes the editorial changes made to address JTC1 ballot comments. It is available in ODF, HTML and PDF formats.
	*[http://docs.oasis-open.org/office/v1.1/OS/OpenDocument-v1.1.pdf OpenDocument 1.1] includes additional features to address accessibility concerns.<ref>{{cite web | url=http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office#odf11 | title=OpenDocument 1.1 Specifications | year=2006 | accessdate=2006-10-31 | publisher=[[OASIS (organization)|OASIS]]}}</ref> It was approved as an OASIS Standard on 2007-02-01 following a call for vote issued on 2007-01-16.<ref>{{cite web | title=Approval of OpenDocument v1.1 as OASIS Standard | url=http://lists.oasis-open.org/archives/office/200702/msg00003.html | accessdate=2007-02-06 | publisher=[[OASIS (organization)|OASIS]]}}</ref> The public announcement was made on 2007-02-13.<ref>{{cite web | title=Members Approve OpenDocument Version 1.1 as OASIS Standard | url=http://www.oasis-open.org/news/oasis-news-2007-02-14.php | accessdate=2007-02-15 | publisher=[[OASIS (organization)|OASIS]]}}</ref> This version was not initially submitted to ISO/IEC, because it is considered to be a minor update to ODF 1.0 only, and OASIS were working already on ODF 1.2 at the time ODF 1.1 was approved.<ref>[http://www.zdnet.co.uk/talkback/0,1000001161,39409700-39001068c-20093634o,00.htm ZDnet.co.uk]</ref> However it was later submitted to ISO/IEC and as of March 2011, it is in "enquiry stage" as Draft Amendment 1 (ISO/IEC 26300:2006/DAM 1).<ref>{{cite web |url=http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=59302 |title=ISO/IEC 26300:2006/DAM 1 - OpenDocument v1.1 |accessdate=2011-03-29}}</ref>		*[http://docs.oasis-open.org/office/v1.1/OS/OpenDocument-v1.1.pdf OpenDocument 1.1] includes additional features to address accessibility concerns.<ref>{{cite web | url=http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office#odf11 | title=OpenDocument 1.1 Specifications | year=2006 | accessdate=2006-10-31 | publisher=[[OASIS (organization)|OASIS]]}}</ref> It was approved as an OASIS Standard on 2007-02-01 following a call for vote issued on 2007-01-16.<ref>{{cite web | title=Approval of OpenDocument v1.1 as OASIS Standard | url=http://lists.oasis-open.org/archives/office/200702/msg00003.html | accessdate=2007-02-06 | publisher=[[OASIS (organization)|OASIS]]}}</ref> The public announcement was made on 2007-02-13.<ref>{{cite web | title=Members Approve OpenDocument Version 1.1 as OASIS Standard | url=http://www.oasis-open.org/news/oasis-news-2007-02-14.php | accessdate=2007-02-15 | publisher=[[OASIS (organization)|OASIS]]}}</ref> This version was not initially submitted to ISO/IEC, because it is considered to be a minor update to ODF 1.0 only, and OASIS were working already on ODF 1.2 at the time ODF 1.1 was approved.<ref>[http://www.zdnet.co.uk/talkback/0,1000001161,39409700-39001068c-20093634o,00.htm ZDnet.co.uk]</ref> However it was later submitted to ISO/IEC and as of March 2011, it is in "enquiry stage" as Draft Amendment 1 (ISO/IEC 26300:2006/DAM 1).<ref>{{cite web |url=http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=59302 |title=ISO/IEC 26300:2006/DAM 1 - OpenDocument v1.1 |accessdate=2011-03-29}}</ref>
−	*OpenDocument 1.2 was approved as an OASIS Committee Specification on {{date|2011-03-17|iso}}.<ref>[http://lists.oasis-open.org/archives/office/201103/msg00089.html OASIS office message: Ballot for CS approval of ODF Version 1.2 has passed]</ref> It includes additional accessibility features, [[Resource Description Framework|RDF]]-based metadata, a spreadsheet formula specification based on [[OpenFormula]], support for digital signatures and some features suggested by the public.	+	*OpenDocument 1.2 was approved as an OASIS Committee Specification on {{date|2011-03-17|iso}} and as an OASIS Standard on 29 September 2011.<ref>[http://lists.oasis-open.org/archives/office/201103/msg00089.html OASIS office message: Ballot for CS approval of ODF Version 1.2 has passed]</ref><ref>{{citation |url=http://www.oasis-open.org/news/pr/odf-1-2-approval |title=Members Approve OpenDocument Format (ODF) Version 1.2 as OASIS Standard |date=2011-10-05 |accessdate=2012-04-12}}</ref><ref>{{citation |url=http://www.oasis-open.org/committees/office/ |title=OASIS Open Document Format for Office Applications (OpenDocument) TC |accessdate=2012-04-12}}</ref> It includes additional accessibility features, [[Resource Description Framework|RDF]]-based metadata, a spreadsheet formula specification based on [[OpenFormula]], support for digital signatures and some features suggested by the public.
	==Application support==		==Application support==

As you can read all over PlanetKDE, Calligra 2.4 has been released. In case you have not found them yet, since quite some time Calligra packages(including Krita) are available for openSUSE users, e.g. in KDE:Release:48. Koffice2 packages are removed.

One of the most re-occuring questions regarding KDE PIM within openSUSE is, how one can sync data with Google. KDE:Release:48 now holds the package akonadi-google which replaces the unmaintained akonadi-google-data package.

Both, Calligra and akonadi-google, will be part of openSUSE 12.2.

Finally I would like to point openSUSE KDE users to the beta packages of Digikam. IMHO Digikam is one of the most active and responsive (including bugs.kde.org handling) projects within KDE – attracting new developers by attracting more users. Those that want to help testing Digikam but are not familiar with building software, can get git snapshot packages from KDE:Unstable:Playground. Beware, those are git snapshots and thus might break some functionality. The package is updated at least once a week, so it should help to check for fixed/new bugs.

First stable release of the Calligra office and productivity suite The H Source: Calligra Calligra has a "completely rewritten" text layout engine, a simplified user interface and can handle more parts of the Open Document Format (ODF) than KOffice. Other changes include improved import filters for Microsoft document ... and more »

Erste Release der freien Bürosuite Calligra Linux-Magazin Online Die Office-Software verwendet das Open Document Format (ODF) als Standard-Dateiformat. Die Suite besteht aus der Textverarbeitung Calligra Words, der Tabellenkalkulation Sheets und dem Präsentationsprogramm Stage, für Diagramme ist die Komponente Flow ... and more »

Let's all congratulate the Calligra team for releasing Calligra 2.4.0, the first version of their integrated application suite for KDE. It has really gone a long way from the old KOffice codebase. Of course, Gentoo already has ebuilds as app-office/calligra. Give it a try! Cheers!

Calligra has been released, KDE's document suite of applications. It has applications for word processing, spreadsheets, presentations, drawing and much more. Congratulations Calligra team. Install the packages from kubuntu-ppa/backports or direct from 12.04.

Calligra has been released, KDE's document suite of applications. It has applications for word processing, spreadsheets, presentations, drawing and much more.

Take the tour to discover the many apps of Calligra.

It can be installed from the backport
PPA for 11.10 and the main archive for our development release.

After about 2 years of development and 1½ year since we officially formed the Calligra project I'm happy that Calligra 2.4 is being released later today.

In my vision Calligra becomes a ground breaking fresh alternative to the established free and proprietary players. Calligra should create history and revolutionize it. We are not there yet, but we have great plans and are very much still evolving.

We don't believe that applications have to chose between being powerful and complex, or being dumbded down to make them easy to use. In the Calligra Words team we have this crede "powerfeatures made easy" and we are committed to making this come true by working hard on the usability as well as adding powerfeatures. And we don't want to just add configuration options. We want to create our interfaces in a way that puts all the power at your fingertips in the most intuitive way.

We know we are not there yet. As I said it's early days yet, but we have already made some new first-of-a-kind usability improvements for the next version (2.5). Let me share an example with you. In other wordprocessors when you drag the borders of a table you see a line that shows you where the border will end up. In Caligra Words 2.5 not only do you instantly see the text being relayouted, but you also get helpers that show you the width of the columns or height of rows as you manipulate them. Additionally, if you press shift while dragging a border it changes the way it moves the following column(s). Obviously using the shift key for extended functionality is not an original idea, but coupled with the innovative helper (note how it even suggests to use the shift key) this makes this powerfeature easy reachable and understandable for the avarage user.

Click for video

This underlines what I said of us wanting to be more than just another player on the market. We want to create history. We want to innovate and think out of the box. But before we could do that we had to create a solid baseline, and that is what 2.4 represents.

So for 2.4 we concentrated on becoming a solid document viewer so you would have no need to look elsewhere. And also to fulfil your daily editing needs, with quite a number of advanced features also already working.

It thus brings us great joy that early adopters of our betas and release candidates are saying that we rock and find us really usable. That is so gratifying to hear. Thank you!

And to top it off we wil begin to release new versions every 4 months or so.

A little under a year ago I wrote a happy post about LibreOffice. The team back then showed a strong focus on cleaning up and re-architecturing LibreOffice to make it ready for the future.

Much work

SUSE's Michael Meeks recently made the awesome graph on the right about the stuff being cleaned up from LibreOffice - besides removing a large amount of unused code there has been translating of comments and much other stuff. As I wrote in my previous post: that was (and still is) much needed. Without a lean and mean code base you can't get and keep contributors and making changes takes forever. As say the 3-months GSOC project needed to just get a multi-line edit in Calc shows... And getting contributors is a major goal of LibreOffice - with over 200 new people commiting code, they're quite good at it!

I've had plenty of complaints during the 3.4 series. Stability has been a serious issue. But I do realize that re-factoring and cleaning up takes time and often causes (temporary) issues so I can live with that. And as Meeks said in the announcement of LibreOffice 3.5, we can "now benefit from a substantially cleaner, leaner and more feature rich LibreOffice 3.5.". So I went and downloaded ~600 MB of Free/Libre goodness which is now packaged for openSUSE...

Features

In part thanks to the substantially cleaned code base a number of big improvements can be found in this release. The coolest is imho the grammar check - I know grammar is hard to test but the grammar check has been tuned to have almost zero false positives so if and when it tells you something is wrong, it'll be wrong. The improvements in typography are very noticable as well, fonts look much nicer. And I greatly appreciate the new header/footer interface. Finally, there is the real time word count - I used to use Calligra Words for this feature and its nice to see LO getting it too. Yes, I mostly use writer - can you tell?

But there are plenty of other improvements in the other apps too, including the multi-line input area in Calc so LO 3.5 is certainly a worthy upgrade. I did find a bug, which I have reported ;-)

Speaking off...

On the note of Words - Calligra is on the verge of releasing Calligra 2.4 and I must say that's another FOSS Office release I greatly look forward to, if only due to its about 10 times smaller footprint on my too-tiny SSD ;-)

That release will be even more packed with goodies but then again, it's taken the team about a year to finish it. I especially look forward to Krita, which is now ready for professional artists and from what I've seen of the beta's and RC's it'll be something good enough to make artists move over to Linux. And I'd recommend openSUSE as you can hear Krita lead developer Boud frequently complain that he'd have an easier time supporting users with issues if they'd all just run openSUSE which works flawlessly with tablets.

Getting it

Muktware wrote an article on how to install LO 3.5 in openSUSE but I wasn't particularly looking forward to downloading and installing RPM files by hand so I've waited until a more convenient installation method was available. It is now, just click the link below, give your password and it'll get installed. This works for openSUSE 12.1, openSUSE Tumbleweed users get the upgrade automatically once it is deemed stable enough - the spoils of a Rolling Release... Awesomeness :D

click here for a convenient one-click-installation of LibreOffice 3.5.2 from the LibreOffice-Unstable branch in openSUSE


On an entirely different note, my google plus stream is full of complaints and praise about GNOME Shell which I'm using on my laptop this week (during travel to Nurnberg and Prague). Certainly an interesting experience.

Sven posted his thoughs on the difficulties supporting Krita on Windows. I'd like to dig in a bit deeper here. The first question is, is it worth it?

Well, the highly experimental Calligra installer has been downloaded about 15.000 times. That's a lot of downloads! Judging from the ratio of referrals from krita.org and calligra.org, Krita is probably the reason for the two-thirds of those downloads.

So, apparently there is a demand for Krita on Windows that makes people download it even though we're extremely explict about its extremely experimental status!

We also know that there are bugs specific to Windows, like the slow move tool, a bug with duplicated layers being broken and so on. We know that the top toolbar looks ugly and that there are other issues where being non-native really is apparent.

Another thing I know is that developing on Windows really is no fun. As the Tomahawk Windows dude says:

We do need developers on Windows too, but no-one in a sane state of mind wants to develop there.. ;-)

So what Krita needs is to find a volunteer who completely and utterly disagrees with that quote... Someone who loves Windows, cares about the look and feel of an application on Windows, and who simply loves developing on Windows. If you're that person, contact me!

The other option would, of course, be to find the money to pay someone to work on Windows.

But we're not talking 1000 euro/month here -- we're out of the student summer job territory! At a conservative estimate, we'd need between five and seven times as much: 5000-7000 euros of regular income to hire a full-time developer. So we're out of donations territory, out of Summer of Code territory. It's a big job, which needs to be done well.

If there are 15.000 downloads of an experimental version of Krita in about three months -- maybe there is a market. Maybe we could package Krita, put it in an app store like Intel's app-up, on Amazon, sell it directly, go with a pay-what-you-like model like Ardour. Whatever -- and use the proceeds pay a full-time developer to work on the Windows version of Krita. It'll, indirectly and directly, also benefit Krita on its main platform.

I'm seriously investigating all the options here, including finding some kick-start funding.

(Note: Krita is GPL, but that doesn't stop us from charging money for a binary, even though we can't stop anyone from copying the binary around or reselling it -- and I don't even want to do that. Free software is Free software. Being GPL, proprietary extras and improvements are also out of the question. And that's the way I like it.)

Oh, and as a side-node: next to the highly experimental Calligra 2.4 installer that includes Krita next to the other apps, there's also an extremely experimental Krita-only installer that packages Krita fresh from git master. Just to help me figure out how to do it. Get yours while it's fresh at KO GmbH's download page.

The word of the day is: CLA ...ok, so that's not actually a word, but rather an initialism ;) Hi everybody! Some of you already know me, though mainly as that guy who has funny hair and talks about Gluon a lot. Today, however, i come to you in my new guise, as the guy who's going to be talking a whole lot about WebODF over the next while! So, what's this WebODF thing, some of you say? Well,

DataNucleus AccessPlatform is a standards-compliant Java persistence product. It is fully compliant with the JDO1, JDO2, JDO2.1, JDO2.2, JDO3, JPA1, and JPA2 Java standards, and provides a REST API. It complies with the OGC Simple Feature Spec for persistence of geospatial Java types. It allows access to all popular RDBMS available today, together with db4o, LDAP, NeoDatis, JSON, Excel/ODF spreadsheets, XML, BigTable, and HBase databases.

Release Notes: Support for the latest versions of the javax.cache API have been moved to "core". The "xmltypeoracle" plugin has been merged into "rdbms". A new statistics API has been added. Support for JMX (the "management" plugin) has been moved into "core". Some fixes have been added to the proxies for Collections to reduce SQL statements. The RDBMS plugin has received various fixes to range handling on Oracle, and to JDOQL in general. MongoDB has been given various improvements to querying and persistence, including query parameters and COUNT, and inheritance of embedded objects. Most datastores now support persisting Enum fields as numeric.

Release Tags: JDO, JPA, Persistence

Tags: Database, API, ORM, JDO, JPA, Persistence

Licenses: Apache 2.0

‎Criticism

← Previous revision		Revision as of 08:14, 8 April 2012
Line 211:		Line 211:
	=== Criticism ===		=== Criticism ===
−	*Different applications using ODF as a standard document format have different methods of providing macro/scripting capabilities. There is no [[macro language]] specified in ODF. Users and developers differ on whether inclusion of a standard scripting language would be desirable.<ref>{{cite web | url=http://www.linux.com/articles/47935 | title=Macros an obstacle to office suite compatibility | author=Marco Fioretti | accessdate=2008-05-11}}</ref>	+	*Different applications using ODF as a standard document format have different methods of providing macro/scripting capabilities. There is no [[macro language]] specified in ODF. Users and developers differ on whether inclusion of a standard scripting language would be desirable.<ref>{{cite web | url=http://www.linux.com/articles/47935 | title=Macros an obstacle to office suite compatibility | author=Marco Fioretti | accessdate=2008-05-11}} {{Dead link|date=April 2012}}</ref>
	* The ODF specification for tracked changes is limited and does not fully specify all cases, resulting in implementation-specific behaviors.<ref>{{cite web | url=http://blogs.msdn.com/dmahugh/archive/2009/05/13/tracked-changes.aspx | title=Tracked Changes | author=Doug Mahugh (Microsoft) | date=2009-05-13}}</ref> In addition, OpenDocument does not support change tracking in elements like tables or [[MathML]].<ref name="doyourmath">{{cite web | url=http://idippedut.dk/post/2008/01/29/Do-your-math-OOXML-and-OMML.aspx | title=Do your math - OOXML and OMML (Updated 2008-02-12) | author=Jesper Lund Stocholm (Danish ISO/IEC representative) | date=2008-12-12}}</ref>		* The ODF specification for tracked changes is limited and does not fully specify all cases, resulting in implementation-specific behaviors.<ref>{{cite web | url=http://blogs.msdn.com/dmahugh/archive/2009/05/13/tracked-changes.aspx | title=Tracked Changes | author=Doug Mahugh (Microsoft) | date=2009-05-13}}</ref> In addition, OpenDocument does not support change tracking in elements like tables or [[MathML]].<ref name="doyourmath">{{cite web | url=http://idippedut.dk/post/2008/01/29/Do-your-math-OOXML-and-OMML.aspx | title=Do your math - OOXML and OMML (Updated 2008-02-12) | author=Jesper Lund Stocholm (Danish ISO/IEC representative) | date=2008-12-12}}</ref>
	* It is not permitted to use generic ODF formatting style elements (like font information) for the MathML elements.<ref name="doyourmath"/>		* It is not permitted to use generic ODF formatting style elements (like font information) for the MathML elements.<ref name="doyourmath"/>

Introducing the new Community License Agreement for WebODF contributors. This short document describes what rights you as a contributor, and KO GmbH as the maintainer, have to the work you contribute to the WebODF project.

So, you may well think, why should do we want you to sign a CLA to contribute work to WebODF? Surely it's already covered by the project's nice, free software license!

The idea

The other day, I took it upon myself to write a browser-based Prezi-like app without using flash. Condition: It should run purely client-side.

It was also an experiment in evaluating whether the current APIs available in modern browsers are enough to handle the task. What follows is an account of what works, what doesn’t, and what could be done better.

SVG vs Canvas

When you’re building a rich graphics-intensive app like Prezi, you usually have two ways of rendering content: SVG and Canvas.

1. SVG provides a neat DOM that can be manipulated with existing DOM handling javascript libraries, such as jQuery. Canvas, on the other hand, is just a bitmap buffer. This means that you have to program your own DOM-like scene graph if you wish to use Canvas for handling presentation elements. Libraries for this already exist – most notably, fabric.js, but none are as convenient to use as a real DOM. SVG wins here.

2. Canvas is just a dumb bitmap buffer. Animating it is faster than animating SVG with Javascript, but it isn’t accessible. You can’t select text with the mouse. You can’t embed rich content. SVG wins in this regard; you can even embed YouTube videos and forms and such.

3. SVG is not implemented as completely or identically across different browsers as Canvas is. The worst offender here is, of course, IE9 (a lack of SMIL animation support, among other things). Text rendering looks noticeably different in every browser. This can be mitigated somewhat by not allowing the browser to use default fonts, but using custom webfonts like Google’s toolkit. The rest of the rendering should look fine if you stay away from edge cases (literally) such as not drawing objects outside the main SVG canvas, for example:

<svg xmlns="http://www.w3.org/2000/svg" version="1.1" width="100" height="100">
<rect x="10" y="10" width="50" height="80" rx="-10" ry="-10" fill="red"/>
</svg>

4. SVG and Fonts are not friends. Everything is supposed to be vectorized, but fonts aren’t handled that way. If you notice the animations in the example linked to near the end of this post, you’ll see that during zooming, the fonts ‘shake’ when resizing, because they don’t scale smoothly as normal vector content. The only way to achieve smooth scaling is to convert the text to paths, but that defeats the purpose of text accessibility. There is an SVG Fonts spec, which aims to remedy this by having each font glyph rendered using SVG paths, which would mean real vector fonts which can be selected with the mouse and handled as normal text, plus identical rendering everywhere. Webkit and Opera support this spec, but Mozilla and IE have outright refused to implement it, with the explanation being that WOFF is a ‘superior alternative’ or ‘enough’. This is quite wrong and their arguments are not satisfactory. WOFF is not vector content, and therefore can’t be (and isn’t) rendered identically everywhere. Period.

Taking 1 and 2 as points in our favor, and tolerating 2 and 4, I chose SVG to be the superior but not polished-enough alternative.

Animation

Next, we want to animate. We won’t use CSS3 animations (not supported well enough everywhere). SMIL animation is fast, but works only with non-IE browsers. Heck, we’ll just use plain old JavaScript. I’m using Sozi‘s javascript code for animating.

The Editor

We want to make an SVG editor, in which after designing the document, we can choose certain elements to be nodes in the presentation path, and then have the editor inject the JavaScript code required to animate the presentation.

As it turns out, SVG-edit is an open source, completely client-side SVG editor, and perfectly suited for the task at hand.

I decided to take it’s core and build on top of it, stripping out the unneeded parts and adding some more useful features.  It looks like this right now:

Rendering the Timeline

At KO GmbH, we have started work on a pilot project to add real-time collaborative editing to WebODF. In this pilot, we will create an editor that has most of the same features that Etherpad has. The editor will use ODF as the native document format and all changes in the document are sent to other instances of the editor as operations. Even within an instance of the editor, keyboard events are translated to operations before being sent to the local instance of the document. This design means that collaborative editing is a central part of the editing functionality of WebODF.

The work for this pilot will happen in a separate branch of WebODF.

One of the new things in Krita 2.4 (soon to be released) is pretty decent Photoshop file import. Not everything is supported, but you should be able to load RGB, Lab and CMYK files with multiple layers, thanks to the work by Siddharth Sharma.

Next is filling in the missing parts, and export, of course!

But for that we need to have a good, representative corpus of PSD files, with known version numbers. A bit like the corpus we have for applications like Words, Stage and Sheets -- http://websvn.kde.org/trunk/tests/calligratests/.

These office documents are tested regularly using special tools Thorsten Zachmann built for Calligra. We need that for Krita as well.

So I want to call upon all readers here to contribute PSD files to our collection. I need to know the version of Photoshop they were created with and the files will be committed to this public subversion repository, so they must be appropriately licensed or be public domain.

Please help us out! You can send the files to boud@valdyas.org.

Solucionada grave vulnerabilidad en diversas suites ofimáticas libres Xombra.com Crearía una vía para la ejecución remota de código arbitrario, a través de documentos ODF (Open Document Format, por ejemplo los ".odt") especialmente manipulados. Un documento ODF utiliza compresión ZIP y está compuesto por diferentes archivos en su ...

アシスト、オープンソースのオフィス・ソフト「LibreOffice」のeラーニングを提供開始 CNET Japan 高機能でMicrosoft Office と高い互換性を持ち、大手企業／自治体による採用実績があること、ファイル形式に国際標準規格（ISO26300）および日本工業規格（JIS X4401）に登録されているODF（OpenDocument Format）が採用されていることなどから注目を集めています。 and more »

アシスト、オープンソースのオフィス・ソフト「LibreOffice」のeラーニングを提供開始 毎日新聞 高機能でMicrosoft Office と高い互換性を持ち、大手企業／自治体による採用実績があること、ファイル形式に国際標準規格（ISO26300）および日本工業規格（JIS X4401）に登録されているODF（OpenDocument Format）が採用されていることなどから注目を集めています。 and more »

Solucionada grave vulnerabilidad en diversas suites ofimáticas libres Hispasec Crearía una vía para la ejecución remota de código arbitrario, a través de documentos ODF (Open Document Format, por ejemplo los ".odt") especialmente manipulados. Un documento ODF utiliza compresión ZIP y está compuesto por diferentes archivos en su ... and more »

And Now for Something Completely Different.
Kexi's Easter Egg just appeared and quite magically it's only available on April Fools' Day ;)

To try, run any beta of Kexi 2.4 or 2.5 alpha. Then close the app, run again and look closer. Enjoy!

It works (I hope - untested!) thanks to the remote updates for the user feedback/news module[*] that we managed to fit within the Calligra 2.4 release plan. More on that later.

[*] BTW, you won't find any traces in the source code...

Linux się jednak opłaca? Porzucając Windows i Office, Monachium w rok ... Gazeta.pl Pod koniec grudnia 2009 roku ogłoszono ukończenie pierwszego etapu - pełne przejście na format ODF i OpenOffice.org działające na 100% komputerów. Jednak sytuacja wcale nie była prosta. W 2010 roku Florian Schießl, jeden z architektów LiMuxa, ...

Munich mayor says switch to Linux saved money, reduced complaints PC Advisor Munich uses the Open Document Format (ODF) as a standard, and OpenOffice is extended by an in-house developed system called WollMux. The extension includes numerous features including templates, forms and letterheads. "By the end of 2012, ... and more »

Munich Mayor Says Switch to Linux Saved Money, Reduced Complaints PCWorld Munich uses the Open Document Format (ODF) as a standard, and OpenOffice is extended by an in-house developed system called WollMux. The extension includes numerous features including templates, forms and letterheads. "By the end of 2012, ... and more »

Мюнхен сэкономил миллионы за счёт перехода на Ubuntu и OpenOffice Хакер В новой системе стандартным форматом документов стал Open Document Format (ODF), в качестве браузера и почтового клиента используются Firefox и Thunderbird. Несмотря на опасения, после перехода на Linux не возникло особых проблем с совместимостью. and more »

DataNucleus AccessPlatform is a standards-compliant Java persistence product. It is fully compliant with the JDO1, JDO2, JDO2.1, JDO2.2, JDO3, JPA1, and JPA2 Java standards, and provides a REST API. It complies with the OGC Simple Feature Spec for persistence of geospatial Java types. It allows access to all popular RDBMS available today, together with db4o, LDAP, NeoDatis, JSON, Excel/ODF spreadsheets, XML, BigTable, and HBase databases.

Release Notes: Support for bulk loading of objects has been added to pm.getObjectsById. Update of a Set has been improved to not do a clear+addAll. Persist of a 1-N uni FK collection now uses one less SQL statement for RDBMS. Error reporting when detach fails has been improved. JPA JTA/nonJTA "datasource" persistence properties have been fixed. Non-referential flush process (non-RDBMS datastores) has been fixed to correctly detect newly persisted objects.

Release Tags: JDO, JPA, Persistence

Tags: Database, API, ORM, JDO, JPA, Persistence

Licenses: Apache 2.0

Undid revision 484355735 by 84.14.163.66 (talk)

← Previous revision		Revision as of 12:27, 28 March 2012
Line 280:		Line 280:
	* [http://opendocumentformat.org/ OpenDocumentFormat.org] Portal for consumers, business users and developers with information on OpenDocument format.		* [http://opendocumentformat.org/ OpenDocumentFormat.org] Portal for consumers, business users and developers with information on OpenDocument format.
	* [http://opendocsociety.org/ OpenDoc Society] Association with members around the world that promote best practices in office productivity such as OpenDocument format.		* [http://opendocsociety.org/ OpenDoc Society] Association with members around the world that promote best practices in office productivity such as OpenDocument format.
−	* [http://opendocumentfellowship.org/ OpenDocument Fellowship] Volunteer organization with members around the world to promote the adoption, use and development of the OpenDocument format.	+	* [http://opendocumentfellowship.com/ OpenDocument Fellowship] Volunteer organization with members around the world to promote the adoption, use and development of the OpenDocument format.
	* [http://www.odfalliance.org/ OpenDocument Format Alliance] The alliance works globally to educate policymakers, IT administrators and the public on the benefits and opportunities of the OpenDocument Format, to help ensure that government information, records and documents are accessible across platforms and applications, even as technologies change today and in the future.		* [http://www.odfalliance.org/ OpenDocument Format Alliance] The alliance works globally to educate policymakers, IT administrators and the public on the benefits and opportunities of the OpenDocument Format, to help ensure that government information, records and documents are accessible across platforms and applications, even as technologies change today and in the future.
	* [http://opendocument.xml.org/ OpenDocument XML.org] The official community gathering place and information resource for the OpenDocument OASIS Standard (ISO/IEC 26300).		* [http://opendocument.xml.org/ OpenDocument XML.org] The official community gathering place and information resource for the OpenDocument OASIS Standard (ISO/IEC 26300).

Wrong external ling for Open Document Fellowship

← Previous revision		Revision as of 12:23, 28 March 2012
Line 280:		Line 280:
	* [http://opendocumentformat.org/ OpenDocumentFormat.org] Portal for consumers, business users and developers with information on OpenDocument format.		* [http://opendocumentformat.org/ OpenDocumentFormat.org] Portal for consumers, business users and developers with information on OpenDocument format.
	* [http://opendocsociety.org/ OpenDoc Society] Association with members around the world that promote best practices in office productivity such as OpenDocument format.		* [http://opendocsociety.org/ OpenDoc Society] Association with members around the world that promote best practices in office productivity such as OpenDocument format.
−	* [http://opendocumentfellowship.com/ OpenDocument Fellowship] Volunteer organization with members around the world to promote the adoption, use and development of the OpenDocument format.	+	* [http://opendocumentfellowship.org/ OpenDocument Fellowship] Volunteer organization with members around the world to promote the adoption, use and development of the OpenDocument format.
	* [http://www.odfalliance.org/ OpenDocument Format Alliance] The alliance works globally to educate policymakers, IT administrators and the public on the benefits and opportunities of the OpenDocument Format, to help ensure that government information, records and documents are accessible across platforms and applications, even as technologies change today and in the future.		* [http://www.odfalliance.org/ OpenDocument Format Alliance] The alliance works globally to educate policymakers, IT administrators and the public on the benefits and opportunities of the OpenDocument Format, to help ensure that government information, records and documents are accessible across platforms and applications, even as technologies change today and in the future.
	* [http://opendocument.xml.org/ OpenDocument XML.org] The official community gathering place and information resource for the OpenDocument OASIS Standard (ISO/IEC 26300).		* [http://opendocument.xml.org/ OpenDocument XML.org] The official community gathering place and information resource for the OpenDocument OASIS Standard (ISO/IEC 26300).