Planet ODF

July 25, 2014

Google News

UK.gov's Open Source switch WON'T get rid of Microsoft, y'know - Register


UK.gov's Open Source switch WON'T get rid of Microsoft, y'know
Register
ODF is the open specification for document markup, as employed by suites like OpenOffice. Microsoft is not happy: in selecting ODF, No.10 Downing Street rejected Microsoft's Office Open XML (OOXML) or supporting a dual standard of OOXML and ODF.

July 25, 2014 11:37 AM

Docker acquires Orchard, SAP supports OpenStack, ODF and more - opensource.com


Docker acquires Orchard, SAP supports OpenStack, ODF and more
opensource.com
In this week's edition of our open source news roundup, we take a look at Docker acquiring Orchard, SAP who will support Cloud Foundry and OpenStack, the UK government who made ODF its official document standard, and more!

July 25, 2014 09:42 AM

UK chooses ODF format for saving electronic documents - ITWorld Canada


ZDNet

UK chooses ODF format for saving electronic documents
ITWorld Canada
That's what came to mind when I read this week that the British government has chosen the XML-based open document format (ODF) over Microsoft's OOXML for saving editable electronic documents it receives and sends. PDF/A or HTML are the formats for ...
UK makes ODF its official documents format standardZDNet
UK government officially adopts Open Document FormatRegister
UK Government Adopts ODF, but Not Microsoft's OOXMLRedmondmag.com
PCWorld -ComputerWeekly.com -ComputerworldUK
all 42 news articles »

July 25, 2014 03:37 AM

WebODF news

WebODF 0.5.2 released, bringing more fixes

Not even two weeks passed after the first update to WebODF 0.5 and there is the second.

It brings improvements in the rendering of the ODP slides and makes nagivation in ODT documents via home/end keys, or up/down cursor keys more reliable in all browsers.

July 25, 2014 12:00 AM

July 24, 2014

Google News

UK Government Adopts Open Standards - iProgrammer


UK Government Adopts Open Standards
iProgrammer
The UK Government has selected ODF (Open Document Format) as a required standard for sharing and collaborating on documents across all governement bodies. PDF/A and HTML are the selected standards for viewing government documents.

July 24, 2014 04:40 PM

Open source ownCloud innovates unique collaboration scheme - FierceEnterpriseCommunications


Open source ownCloud innovates unique collaboration scheme
FierceEnterpriseCommunications
Since version 6, ownCloud has included the capability for multiple users to collaboratively edit documents in ODF format (first popularized by OpenOffice) from within the portal. The word processor is built directly into the system. While most ...

and more »

July 24, 2014 02:38 PM

Open source ownCloud innovates unique collaboration scheme - FierceEnterpriseCommunications


Open source ownCloud innovates unique collaboration scheme
FierceEnterpriseCommunications
Since version 6, ownCloud has included the capability for multiple users to collaboratively edit documents in ODF format (first popularized by OpenOffice) from within the portal. The word processor is built directly into the system. While most ...

July 24, 2014 02:38 PM

Charles H. Schulz

What the UK Government’s adoption of ODF really means

On Tuesday the news that the UK Government had decided to use ODF as its official and default file format started to spread. The full announcement with technical details may be found here; the Document Foundation published its press release on Thursday morning there.

This decision is a landmark for several reasons. First, it is not every day that you see an entire ODF-logogovernment migrate to a standardized file format. You may hear about government branches using this or that solution, but nothing that is so “abstract” than a file format.  This time the UK Government has made the conscious decision to define a coherent policy in handling its digital documents, from the stage where they are created, edited and circulated all the way to the archival phase. It also comes year after the decision of the State of Massachusetts. As such the decision covers a variety of standards (HTML, PDF and ODF); yet its scope, as Glyn Moody rightly reminds us, also means that the devil will lie in the details of the execution.

Most of the migrations from one office suite to another tend to happen without any coherent document management policy. Many organizations moving from, say, Microsoft Office to LibreOffice do not necessarily adopt ODF as their default format and will carry on supporting whatever version of the MS Office file format internally. This usually leads to frustrations and compatibility problems. This time, the UK Government decision takes a different approach. By deciding about the formats first, the UK creates the conditions necessary to have real choices for its government and its citizens, thus setting a level playing field for everyone. Many people have understood this decision as being a move against Microsoft. It is not or at least it should not be. Microsoft Office implements ODF files and its latest editions, as I’m being told are actually quite good at it. What this move does, however, is to ensure no other solution will be at a competitive disadvantage because of a technical or legal (aka patents) lock-in. Of course, it remains to be seen what concrete actions the UK Government will take in order to ensure a smooth transition between proprietary formats and open standards; and it remains to be seen how well it will ensure a proper change management across all of its departments so that its agents feel comfortable with ODF documents and whatever new office suites that may be adopted as a result of the decision. Much could be lost at that stage, but much could be gained as well. And of course, just like with the Netherlands, the decision itself might end up being toned down or take a somewhat different meaning.

While reading among the tea leaves is not my favourite past time, it is relevant to assume that this decision may change a few things around the IT industry as well. By way of an example, I have always been amazed at Apple’s clean support of ODF inside Mac OS X but its constant absence across the iWork editions. Perhaps Apple will feel compelled to introduce ODF files in iWork now? Only time will tell. Cloud solutions will also have to improve or implement ODF and in some cases PDF support in a proper way.

The decision might also have consequences for other European countries and perhaps for the European institutions themselves, as the UK will now be an actual example of a country that has migrated to ODF, and not just one of the countries that made the choice of Free and Open Source Software. This is rare enough to catch the attention of several member states CIO offices.

This move to open standards by the UK Government is also telling of a deeper change in IT industry. We may reach the stage where finally, the average user starts to realize that the old Windows + Office paradigm starts to get exhausted. What can you do with Office documents aside opening them imperfectly in alternatives and opening them in a more effective way with Microsoft software? Actually, not much. Unless you get SharePoint. But the whole point is that in 2014, trying to extract revenue by creating lock-in on office files is no longer acceptable. That, I think, is what the UK Government decision really means. And if I’m right, it’s only the beginning.

Last but not least, this post would not be over without thanking many people whom I’ve worked with for several years in my position at my former company, Ars Aperta, in my former role at OpenOffice.org, at the OASIS Consortium and even today when contributing to the LibreOffice project. I’m thinking about people at OpenForum Europe, the FFII, the APRIL, the AFUL, the OASIS, the now defunct ODF Initiative and everyone else I am forgetting right now but who should be remembered. It’s nice sometimes, after such successes, to turn back and look at the road behind us. It can only give more confidence to walk on the one ahead.

by Charles at July 24, 2014 10:27 AM

July 23, 2014

www.opendocsociety.org

New co-chair of ODF TC

The ODF Technical Committee at OASIS has elected Oliver-Rainner Wittmann as its new co-Chair, joining Patrick Durusau. Mr. Wittmann is an employee of IBM and as erstwhile employee of SUN Microsystems has been a longstanding member of the ODF TC. Wittman is currently part of the team working on Apache OpenOffice, the well-known open source office suite.

Mr. Wittman is the successor of Rob Weir, who held the position of co-chair since 2007 until now. In his capacity of co-chair he played an important role in the tumultuous period around the ISO/IEC standardisation of IS29500. He also was a prominent figure in the various ODF plugfests, organised by OpenDoc Society together with a number of governments, academic institutions and open source communities.

Due to changes in his role at his employer, Weir is longer directly involved with document formats and editors. He will temporarily stay on as liaison from the ODF TC to ISO/IEC WG6, to provide some continuity. Weir's analytic skills, strong pen, in-depth knowledge of office applications and file formats, as well as his sharp wit will be missed by many in the ODF community.

July 23, 2014 07:10 PM

Google News

UK government adopts ODF for sharing and collaboration - TechRadar UK


UK government adopts ODF for sharing and collaboration
TechRadar UK
The British government has officially adopted PDF/A and HTML for viewing government documents while ODF (Open Document Format) has been selected for collaborating and sharing government documents. The move, which was announced by the ...

July 23, 2014 04:54 PM

UK government adopts ODF for sharing and collaboration - TechRadar UK


UK government adopts ODF for sharing and collaboration
TechRadar UK
The British government has officially adopted PDF/A and HTML for viewing government documents while ODF (Open Document Format) has been selected for collaborating and sharing government documents. The move, which was announced by the ...

July 23, 2014 04:54 PM

Le gouvernement britannique adopte le format ODF Microsoft conteste et ne voit ... - Developpez.com


Le gouvernement britannique adopte le format ODF Microsoft conteste et ne voit ...
Developpez.com
Le Royaume-Uni a finalement adopté le format ODF (Open Document Format for Office Applications) pour le partage des documents au sein du gouvernement et des institutions publiques. L'annonce a été faite hier, 22 juillet 2014, par le « Cabinet Office » ...

July 23, 2014 04:48 PM

Government Adopts Open Document Formats - TechWeekEurope UK


Government Adopts Open Document Formats
TechWeekEurope UK
It pointed out that the government will begin using open formats to ensure both citizens and government workers “can use the applications that best meet their needs.” PDF/A or HTML will now the standard “for viewing government” while ODF is now ...

July 23, 2014 04:37 PM

Il Governo britannico ha scelto ODF - Punto Informatico


Il Governo britannico ha scelto ODF
Punto Informatico
L'annuncio del governo britannico arriva a conclusione di una lungo periodo di flirt con i formati open partito all'inizio dell'anno, stabilendo che gli standard da usare saranno PDF/A o HTML per la fruizione dei documenti governativi e ODF (Open ...

July 23, 2014 04:17 PM

UK government adopts ODF for document exchange with citizens and suppliers - Techworld.com


UK government adopts ODF for document exchange with citizens and suppliers
Techworld.com
The U.K. government has adopted ODF as its standard for the exchange of word processor and spreadsheet files between departments and with citizens and suppliers, meaning that companies and citizens will not be required to buy a particular application ...

July 23, 2014 03:50 PM

UK government adopts ODF for document exchange with citizens and suppliers - CIO Magazine


UK government adopts ODF for document exchange with citizens and suppliers
CIO Magazine
The U.K. government has adopted ODF as its standard for the exchange of word processor and spreadsheet files between departments and with citizens and suppliers, meaning that companies and citizens will not be required to buy a particular application ...

July 23, 2014 03:38 PM

UK government adopts ODF for document exchange with citizens and suppliers - Australian Techworld


UK government adopts ODF for document exchange with citizens and suppliers
Australian Techworld
The U.K. government has adopted ODF as its standard for the exchange of word processor and spreadsheet files between departments and with citizens and suppliers, meaning that companies and citizens will not be required to buy a particular application ...

July 23, 2014 03:38 PM

Brytyjski rząd rezygnuje ze standardu OpenXML na rzecz ODF w dokumentach - PCLab.pl


Brytyjski rząd rezygnuje ze standardu OpenXML na rzecz ODF w dokumentach
PCLab.pl
Wielka Brytania zrezygnowała z OpenXML, który jest domyślnie wykorzystywany w pakiecie Office i postanowiła przejść na Open Document Format (ODF). Administracja ma zacząć używać tylko i wyłącznie otwartych standardów, by ułatwić korzystanie z ...

July 23, 2014 02:35 PM

UK adopts ODF as standard format for government documents - Techie News


Techie News

UK adopts ODF as standard format for government documents
Techie News
The UK government has announced that all government documents intended for viewing, sharing or collaborating should be in PDF/A or HTML or ODF formats hereon. The war between Microsoft's OpenXML and open source office suites like LIbreOffice and ...

July 23, 2014 02:28 PM

So long, Microsoft! UK government abandons Office, embraces free-to-use ... - Expert Reviews


Expert Reviews

So long, Microsoft! UK government abandons Office, embraces free-to-use ...
Expert Reviews
Switching document formats might not sound exciting, but news that government departments are shunning Office in favour of the free-to-use open document format (ODF) is brilliant news. Microsoft has whined that the benefits of the switch are "unclear ...

July 23, 2014 12:59 PM

Microsoft slams government's open file adoption - V3.co.uk


Microsoft slams government's open file adoption
V3.co.uk
Specifically the move will see the government use PDF/A or HTML file formats for documents that only need to be viewed, and the Open Document Format (ODF) for documents that will be shared or created and used collaboratively. The government claims ...

July 23, 2014 11:58 AM

Az Egyesült Királyságban kötelező az ODF - HWSW


Az Egyesült Királyságban kötelező az ODF
HWSW
A kormány a dokumentumok publikálására a PDF/A és HTML formátumokat választotta ki, míg dokumentumcserére és közös munkára az ODF-et írta elő. A hivatalos indoklás szerint az egységesen kiválasztott formátumok használata esetén nem merülnek fel ...
Az Egyesült Királyság az ODF-et választotta a kormányzati dokumentumok ...Hungarian Unix Portal

all 2 news articles »

July 23, 2014 11:43 AM

Government picks Open Document Format as standard - Computer Business Review


Government picks Open Document Format as standard
Computer Business Review
The Government has officially adopted ODF as the standard format for working on its documents, provoking the ire of Microsoft. The Coalition announced last night that Open Document Format would be the default for sharing and collaborating on docs ...

July 23, 2014 11:36 AM

Government opts for open standard document format - Government Computing Network


Government opts for open standard document format
Government Computing Network
Microsoft has criticised the government's decision to "restrict its support of the file formats it uses for sharing and collaboration to just open document format (ODF) and HTML," questioning the potential benefits of the policy for UK citizens. The ...

July 23, 2014 11:21 AM

UK government formally adopts ODF, PDF, HTML - bit-tech.net


bit-tech.net

UK government formally adopts ODF, PDF, HTML
bit-tech.net
The UK government has formally announced a shift to open standards for its electronic documentation, adopting the Open Document Format (ODF) for editable files and a mixture of Portable Document Format (PDF) and HTML for display files.

July 23, 2014 10:45 AM

Huge Win for ODF in UK: Let's Not Mess it up - ComputerworldUK (blog)


Huge Win for ODF in UK: Let's Not Mess it up
ComputerworldUK (blog)
The default format for saving government documents must be Open Document Format (ODF). Information should be shared in ODF version 1.2 (or later). ODF version 1.1 may be used for transition to the implementation of ODF 1.2. Where users need to ...

July 23, 2014 10:16 AM

Microsoft questions UK Government's ODF adoption pledge - IT PRO


IT PRO

Microsoft questions UK Government's ODF adoption pledge
IT PRO
The move was announced by Cabinet Office Minister Francis Maude yesterday, who said the adoption of ODF will boost collaboration between government workers and third parties as they will no longer require specialist software to open or work on official ...

July 23, 2014 09:48 AM

Microsoft questions UK Government's ODF adoption pledge - IT PRO


IT PRO

Microsoft questions UK Government's ODF adoption pledge
IT PRO
The move was announced by Cabinet Office Minister Francis Maude yesterday, who said the adoption of ODF will boost collaboration between government workers and third parties as they will no longer require specialist software to open or work on official ...

July 23, 2014 09:48 AM

Microsoft questions UK Government's ODF adoption pledge - IT PRO


IT PRO

Microsoft questions UK Government's ODF adoption pledge
IT PRO
The move was announced by Cabinet Office Minister Francis Maude yesterday, who said the adoption of ODF will boost collaboration between government workers and third parties as they will no longer require specialist software to open or work on official ...

July 23, 2014 09:48 AM

UK government adopts ODF as standard document format - ComputerworldUK


UK government adopts ODF as standard document format
ComputerworldUK
The UK government has announced the open standards it has chosen for sharing and viewing official documents. The government has formally adopted the Open Document Format (ODF) as the standard for sharing and collaborating on documents and ...

July 23, 2014 09:45 AM

Offene Formate: ODF und PDF werden Regierungsstandard im UK - Golem.de


Offene Formate: ODF und PDF werden Regierungsstandard im UK
Golem.de
Darüber hinaus werden Dokumente innerhalb der Regierung künftig nur noch in einem Format bearbeitet, was die gemeinsame Erarbeitung vereinfachen soll. Immerhin sollten so Fehler ausgeschlossen werden, die durch einen Wechsel des Formats ...

July 23, 2014 09:33 AM

UK government shuns Microsoft with adoption of the ODF standard - Inquirer


UK government shuns Microsoft with adoption of the ODF standard
Inquirer
THE UK GOVERNMENT has chosen the Open Document Format (ODF) for in-house use, and rejected Microsoft's OOXML. Adoption of open standards was announced by Cabinet Office minister Francis Maude, who said in his announcement that other ...

July 23, 2014 08:52 AM

Engelse overheid negeert lobby Microsoft, kiest voor ODF - Automatisering Gids


Engelse overheid negeert lobby Microsoft, kiest voor ODF
Automatisering Gids
De dagen van felle strijd tussen Microsoft en de voorstanders van het open bestandsformaat ODF liggen al weer geruime tijd achter ons. Microsoft was, en is, voorstander van gebruik van zijn eigen OpenXML-bestandsindeling. Die voorkeur heeft veel te ...

and more »

July 23, 2014 08:29 AM

Britische Regierung legt flächendeckend ODF als Standard fest - silicon.de


Britische Regierung legt flächendeckend ODF als Standard fest
silicon.de
Es wird erwartet, dass sämtliche Regierungen das Open Document Format (ODF) unterstützten. Damit soll sichergestellt werden, dass Bürger und Regierungsmitarbeiter bei der Auswahl ihrer Software-Lösungen mehr Flexibilität bekommen. Für das ...
Großbritannien macht offenes Dokumentenformat ODF verbindlichPro-Linux
Britische Regierung schreibt ODF 1.2 als Datenformat vorHeise Newsticker
Offene Formate: ODF und PDF werden Regierungsstandard im UKGolem.de

all 4 news articles »

July 23, 2014 08:10 AM

Британското правителство прие ODF като стандарт в администрацията - kaldata.com


Британското правителство прие ODF като стандарт в администрацията
kaldata.com
Вчера британското правителство съобщи преминаването на администрацията на Острова към използването на Open Document Format (ODF) като стандарт за използване от страна учрежденията при обработката и споделянето на документи.

July 23, 2014 07:08 AM

UK government officially adopts Open Document Format - Register


UK government officially adopts Open Document Format
Register
The United Kingdom government has formally adopted the open document format (ODF) as the standard format for government documents. The announcement says PDF/A or HTML are now the standard “for viewing government” while ODF is now expected ...

July 23, 2014 06:03 AM

Reino Unido hace de ODF el formato estándar para documentos oficiales - MuyLinux


MuyLinux

Reino Unido hace de ODF el formato estándar para documentos oficiales
MuyLinux
En cualquier caso, la decisión es -de cumplirse- igualmente beneficiosa para los formatos abiertos, pues obligará a Microsoft y muy especialmente a Google Docs a dar mejor soporte a ODF, si es que pretenden tener cabida en este nuevo ecosistema.
ODF ya es el formato estándar de documentos en Reino UnidoMuyComputer

all 2 news articles »

July 23, 2014 05:53 AM

July 22, 2014

Google News

UK makes ODF its official documents format standard - ZDNet


ZDNet

UK makes ODF its official documents format standard
ZDNet
Until, the UK government announced on Tuesday, that it will now require all official office suites to support ODF. The document format world has just been turned upside down. The UK Minister for the Cabinet Office Francis Maude, said in prepared ...
UK chooses ODF format for saving electronic documentsITWorld Canada
UK Government Adopts ODF, but Not Microsoft's OOXMLRedmondmag.com
UK government officially adopts Open Document FormatRegister
PCWorld -ComputerWeekly.com -ComputerworldUK
all 43 news articles »

July 22, 2014 09:26 PM

www.opendocsociety.org

UK government adopts ODF as only format

The UK Cabinet Office is the latest government to officially adopt the Open Document Format as its office format of choice. The document file format is expected to be used across all government bodies for sharing or collaborating on government documents.

The Open Document Format offers superior interoperability compared to legacy proprietary formats, and best serves the needs of users:

https://www.gov.uk/government/news/open-document-formats-selected-to-meet-user-needs The move supports the government’s policy to create a level playing field for suppliers of all sizes, with its digital by default agenda on track to make cumulative savings of £1.2 billion in this Parliament for citizens, businesses and taxpayers.

July 22, 2014 08:17 PM

July 18, 2014

WebODF news

WebODF 0.5.1 released, bringing fixes

Less than 3 weeks after the release of WebODF 0.5.0 there is the first update.

It brings improvements in the rendering of the numbering of multi-level lists, solves issues during the startup of the Wodo.TextEditor on Safari and more.

July 18, 2014 12:00 AM

July 14, 2014

Planet KDE

Notes from Calligra Sprint. Part 2: Memory fragmentation in Krita fixed

During the second day of Calligra sprint in Deventer we split into two small groups. Friedrich, Thorsten, Jigar and Jaroslaw were discussing global Calligra issues, while Boud and me concentrated on the performance of Krita and its memory consumption.

We tried to find out why Krita is not fast enough for painting with big brushes on huge images. For our tests we created a two-layer image 8k by 8k pixels (which is 3x256 MiB (2 layers + projection)) and started to paint with 1k by 1k pixels brush. Just to compare, SAI Painting Tool simply forbids creating images more than 5k by 5k pixels and brushes more than 500 pixels wide. And during these tests we found out a really interesting thing...

I guess everyone has at least once read about custom memory management in C++. All these custom new/delete operators, pool allocators usually seem so "geekish" and for "really special purposes only". To tell you the truth, I though I would never need to use them in my life, because standard library allocators "should be enough for everyone". Well, until curious things started to happen...

Well, the first sign of the problems appeared quite long ago. People started to complain that according to system monitor tools (like 'top') Krita ate quite much memory. We could never reproduce it. And what's more 'massif' and internal tile counters always showed we have no memory leaks. We used exactly the number of tiles we needed to store the image of a particular size.

But while making these 8k-image tests, we started to notice that although the number of tiles doesn't grow, the memory reported by 'top' grows quite significantly. Instead of occupying usual 1.3 GiB, which such image would need (layers data + about 400MiB for brushes and textures) reported memory grew up to 3 GiB and higher until OOM Killer woke up and killed Krita. This gave us a clear evidence that we have some problems with fragmentation.

Indeed, during every stoke we have to create about 15000(!) 16KiB objects (tiles). It is quite probable that after a couple of strokes the memory becomes rather fragmented. So we decided to try boost::pool for allocation of these chunks... and it worked! Instead of growing the memory footprint stabilized on 1.3GiB. And that is not counting the fact that boost::pool doesn't free the free'd memory until destruction or explicit purging [0]

Now this new memory management code is already in master! According to some synthetic tests, the painting should become a bit fasted. Not speaking about the much smaller memory usage.

Conclusion:

If you see unusually high memory consumption in your application, and the results measured by massif significantly differ from what you see in 'top', you probably have some fragmentation problem. To proof it, try not to return the memory back to the system, but reuse it. The consumption might fall significantly, especially is you allocate memory in different threads.



[0] - You can release unused memory by explicitly calling release_memory(), but 1) the pool must be ordered, which is worse performance; 2) the release_memory() operation takes about 20-30 seconds(!), so there is no use of it for us.



by Dmitry Kazakov (dmitryK) at July 14, 2014 06:01 AM

July 13, 2014

Planet KDE

Notes from Calligra Sprint in Deventer. Part 1: Translation-friendly code

Last weekend we had a really nice sprint Deventer, which was hosted by Irina and Boudewijn (thank you very much!). We spent two days on discussions, planning, coding and profiling our software, which had many fruitful results.

On Saturday we were mostly talking and discussing our current problems, like porting Calligra to Qt5 and splitting libraries more sanely (e.g. we shouldn't demand mobile applications compile and link QWidget-based libraries). Although these problems are quite important, I will not describe them now (the other people will blog about it very soon). Instead I'm going to tell you about a different problem we also discussed — translations.

The point is, when using i18n() macro, it is quite easy to make mistakes which will make translator's life a disaster, so we decided to make a set of rules of thumb which developers should follow for not creating such issues. Here are these five short rules:

  1. Avoid passing a localized string into a i18n macro
  2. Add context to your strings
  3. Undo commands must have (qtundo-format) context
  4. Use capitalization properly
  5. Beware of sticky strings
Next we will talk about each of the rules in details:

1. Avoid passing a localized string into a i18n macro

They might be not compatible in case, gender or anything else you have no idea about

// Such code is incorrect in 99% of the cases
QString str = i18n(“foo bar”);
i18n(“Some nice string %1”, str);


Example 1

// WRONG:
wrongString = i18n(“Delete %1”, XXX ? i18n(“Layer”) : i18n(“Mask”))

// CORRECT:

correctString = XXX ? i18n(“Delete Layer”) : i18n(“Delete Mask”)
 

Such string concatenation is correct in English, but it is completely inappropriate in many languages in which a noun can change its form depending on the case. The problem is that in macro i18n(“Mask”) the word "Mask" is used in nominative case (is a subject), but in expression "Delete Mask” it is in accusative case (is an object). For example is Russan the two strings will be different and the translator will not be able to solve the issue easily.

Example 2

// WRONG:
wrongString = i18n(“Last %1”, XXX ? i18n(“Monday”) : i18n(“Friday”))

// CORRECT:
correctString = XXX ? i18n(“Last Monday”) : i18n(“Last Friday”)

This case is more complicated. Both words "Monday" and "Friday" are used in the nominative case, so they will not change their form. But "Monday" and "Friday" have different gender in Russian, so the adjective "Last" must change its form depending on the second word used. Therefore we need to separate strings for the two terms.

The tricky thing here is that we have 7 days in a week, so ideally we should have 7 separate strings for "Last ...", 7 more strings for "Next ..." and so on.

Example 3 — Using registry values

// WRONG:
KisFilter *filter = filterRegistry->getFilter(id);
i18n(“Apply %1”, filter->name())

// CORRECT: is there a correct way at all?
KisFilter *filter = filterRegistry->getFilter(id);
i18n(“Apply: \”%1\””, filter->name())

Just imagine how many objects can be stored inside the registry. It can be a dozen, a hundred or a thousand of objects. We cannot control the case, gender and form of each object in the list (can we?). The easiest approach here is to put the object name in quotes and "cite" that literally. This will hide the problem in most of the languages.

2. Add context to your strings

Prefer adding context to your strings rather than expecting translators reading your thoughts

Here is an example of three strings for blur filter. They illustrate the three most important translation contexts

i18nc(“@title:window”, “Blur Filter”)

Window titles are usually nouns (and translated as nouns). There is no limit on the size of the string.

i18nc(“@action:button”, “Apply Blur Filter”)

Button actions are usually verbs. The length of the string is also not very important.

i18nc(“@action:inmenu”, “Blur”)

Menu actions are also verbs, but the length of the string should be as short as possible.

3. Undo commands must have (qtundo-format) context

Adding this context tells the translators to use “Magic String” functionality. Such strings are special and are not reusable anywhere else.

In Krita and Calligra this context is now added automatically, because we use C++ type-checking mechanism to limit the strings passed to an undo command:

KUndo2Command(const KUndo2MagicString &text, KUndo2Command *parent);

4. Use capitalization properly

See KDE policy for details.

5. Beware of sticky strings

When the same string without a context is reused in different places (and especially in different files), doublecheck whether it is appropriate.

E.g. i18n("Duplicate") can be either a brush engine name (noun) or a menu action for cloning a layer (verb). Obviously enough not all the languages have the same form of a word for both verb and noun meanings. Such strings must be split by assigning them different contexts.

Alexander Potashev has created a special python script that can iterate through all the strings in a .po file and report all the sticky strings in a convenient format.

Conclusion

Of course all these rules are only recommendation. They all have exceptions and limitations, but following them in the most trivial cases will make the life of translators much easier.

In the next part of my notes from the sprint I will write how Boud and me were hunting down memory fragmentation problems in Krita on Sunday... :)

by Dmitry Kazakov (dmitryK) at July 13, 2014 02:44 PM

July 09, 2014

Google News

FSFE wettert gegen Microsoft-Software bei der Europäischen Kommission - Pro-Linux


FSFE wettert gegen Microsoft-Software bei der Europäischen Kommission
Pro-Linux
Auf Anfrage der Abgeordneten Amelia Andersdotter im Europäischen Parlament hatte die Kommission eine Strategie vorgelegt, in der sie das offene Dokumentenformat ODF empfiehlt, zugleich aber OOXML weiter unterstützt, nachzulesen in einem Strategiepapier ...

and more »

July 09, 2014 07:35 AM

July 06, 2014

Charles H. Schulz

What’s up with Open Standards?

It has been a while since I have discussed open standards here, even though I have alluded to them in passing. There are currently a number of initiatives and policies ongoing at the European level that are bringing this topic back on the table, especially with regard to public procurement practices. Why does it matter? Because it shows that beyond any kind of advantage, convenience, or the mere ability to have a real choice of IT solutions suppliers, open standards are considered by much of the private and public sectors as some sort of nuisance.

Depending on how you see it, the “battle” for open standards is either won, or it is  still ongoing at the normative level (think about the DRM injection in HTML5 that happened at the W3C). Open Standards, more than ever before, rule the IT industry and the Internet. Cloud technologies rely on open standards to a large extent; purchasing music tracks online lets you increasingly download open file formats that, while they may not be exactly standardized themselves, have open specifications and are unencumbered wiith digital restrictions management (yes, that’s how DRM should really be called).ODF-logo

On the other hand, desktop technologies are still a major issue. One could assume it is because of the stranghold of an entrenched  monopoly, and perhaps it is, to some extent. We are in 2014 however, and both open standards and FOSS desktop offerings (LibreOffice, Firefox, Linux  distributions for the desktop) are legion. These have a real uptake among what is  often referred to as the consumers’ market and that’s great news, but when it comes to what’s going on in the workplace, there seems to be little choice aside the MS Office + Outlook + SharePoint on Windows stack. Why  is that the case? Why is the European Commission still trying to tackle the problem in 2014?

The Desktop is traumatizing

And more exactly, change is traumatizing. Technology changes very quickly, but the more structured the workplace you have, the less adaptative it will be for IT  solutions. If you add the specific culture of the organization that can sometimes be more or less rigid and centered on one vertical industry, you will find long cycles of deployment for any kind of IT technologies and a reluctance to “switch” to a new brand or a new kind of software. This could not be more true on the desktop. I’ve been writing this for years here, but there are reasons for that: the desktop is used by pretty much everyone in the organization. While it  is  somewhat changing with the arrival of tablets and smartphones, desktops are here to stay. The problem is that desktops are very complex systems -offering a graphical interface and tools for pretty much every kind of uses and situations one can imagine- and as such come with more quirks than other devices and other software platforms. These quirks end up being noticed by the users, who most of the time are not computer-savy and will be reluctant to change. Worse,  their  skills will directly or indirectly be challenged by the change. This fear of change ends up being passed on to the CIO level, who has to make the purchase decision, and does not want to be hold liable for having chosen that “weird, so called innovative solution no one gets”.

Just like with any fear, we are not talking about rationality. In 2014, people who use Twitter on a daily basis will shout if their desktop has changed overnight. It is not a good practice to do that kind of brutal change anyway, but the very concept of microblogging was unknown to them 5 years ago. They embraced it with no trouble at all. Their desktop, however, is a holy land, the solitaire game and their office suite their hallowed relics.

Open Standards can sometimes be hard to understand

It is hard enough for people to understand what protocols such as TCP/IP do. These open standards however are invisible to most of them, even if they’re using them on a daily basis. Other open standards, such as OpenDocument Format, are probably not conceivable by some people, who think that an office document is “an extension of Microsoft Office”. I have even heard of teachers, here in France, who refused to even mention ODF because such a thing “could not possibly exist”. The conceptual distinction between a file and an application has not permeated much, even in the twenty first century.

Yet, open standards are the way to go. They may not always be the superior technology, but they offer a level playing field for the industry to build on and innovate with. The Internet has been built on this, so does cloud computing. Desktop solutions are no different. Using open standards brings you back in control of your suppliers and IT infrastructure; it ultimately helps reducing costs and keep your data safe, reusable and sustainable  for dozens of year to come. You can read more about it in the excellent article by Bjorn Lundell published here. Ultimately, the lock-in of the desktop solutions will stop being meaningful as the state of the art will change so much the solutions that are seen as essential today will stop being that important. But the documents, the images, the data, all your content will still be locked in undocumented file formats that need to be reverse-engineered in order to edit them. No one should build such a silo for the future and then throw away the key. That’s what has been happening for more than a decade on the desktop, unfortunately. Where does that lead  us? I think we can already see where: vendor lock-in is here to stay on a more or less large extent; but so are open standards. There will then be people who are stuck with their vendors and constantly handle the legacy; there will be the others, who actually enable information technologies to help them innovate. For them, the story has only started.

by Charles at July 06, 2014 01:07 PM

July 05, 2014

ODF Wikipedia Page

Frietjes at 16:16, 5 July 2014

← Previous revision Revision as of 16:16, 5 July 2014
Line 312: Line 312:
 
[[Category:OpenDocument]]
 
[[Category:OpenDocument]]
 
[[Category:Open formats]]
 
[[Category:Open formats]]
  +
[[Category:OpenOffice]]
 
[[Category:Markup languages]]
 
[[Category:Markup languages]]
 
[[Category:Document-centric XML-based standards]]
 
[[Category:Document-centric XML-based standards]]

by Frietjes at July 05, 2014 04:16 PM

Apache Foundation

Presentations and videos from FOSDEM 2014

fosdem2014a-1024.jpg fosdem2014b-1024.jpg fosdem2014c-1024.jpg fosdem2014d-1024.jpg

Presentations and videos from the Open Document Editors Devroom at FOSDEM 2014 are now available.

The OpenOffice presence at the event was strong and well-received, with a number of interesting talks and many visits at the booth. And the devroom was a nice way to get together with other projects focused on the ODF format.

Make sure you don't miss the following talks about improvements that are coming (or already came!) to OpenOffice:


Changes to 'fields' in Writer for Apache OpenOffice 4.1      Oliver-Rainer Wittmann

Improving the XHTML export filter
Andrea Pescetti

genLang, a new workflow for translation
(partial video available here)
Jan Iversen

Quality Assurance
Raphael Bircher

Create Sidebar Extensions for OpenOffice Andre Fischer

OpenOffice and Eclipse Andre Fischer

Exploring OpenOffice History using GIT Grafts
Herbert Duerr

Digital signing of releases

Jan Iversen

The full list of talks from the Open Document Editors devroom is available as well. Most have a presentation attached.


by pescetti at July 05, 2014 03:13 PM

Planet KDE

Calligra sprint in full process

One week-end of Calligra sprint is currently going on in the old and cozy center of Deventer in the Netherlands.
Yesterday everyone safely arrived, and have been in discussions since then… Right now we are all sitting in the livingroom of Boudewijn and Irina (who are being great hosts to the sprint) around the coffee table, everyone a laptop on their lap, in after-lunch digesting mode, with the full discussions to be continued now every minute.


by Friedrich Kossebau (frinring) at July 05, 2014 12:13 PM

Calligra 2.8.5 Released

This is the last but one update to the 2.8 series of the Calligra Suite, and Calligra Active released to fix recently found issues. The Calligra team recommends everybody to update.

Why is 2.8.4 skipped? Shortly before 2.8.4 release we discovered bug that sneaked in 2.8.2 version and decided to skip the 2.8.4 entirely and quickly release 2.8.5 instead with a proper fix. The bug is related to not showing file formats in Save dialogs.

Issues Fixed in This Release

General

  • Show file formats in Save dialogs
  • Added a number of missing translations

Kexi

  • Only move to initial top-left position in table view on initial show (bug 334577)
  • Display proper record’s page number when coming back to report’s data view (bug 335269)
  • Properly remember previous search keywords in the Find Dialog (bug 334514)
  • Fix crash for SELECT queries containing (invalid) “ORDER BY 0″ parameter
  • Properly sort names of newly added tables and queries in Form Designer’s data source drop-down list (bug 334093)
  • Fix crash possible when accessing queries with duplicated table names. Example query “SELECT t.foo FROM t, t”. Display error message so user can fix the statement. (bug 315852)
  • Fix squashed up toolbar buttons for windows-based styles (bug 335149)
  • Fix crash when removing a Database Connection (bug 315288)
  • Temporarily hide “sort” buttons in forms because sorting is not implemented there anyway (related to bug 150372)
  • Make Ctrl+S keyboard shortcut work for Save action in all designers (bug 334587)
  • Fix deselecting text form’s text editor widget when moving to other widget (bug 336054)
  • Let the spreadsheet import plugin to be found by Kexi
  • Fix crash on changing Auto Tab Order form property, set to true by default (bug 336927)
  • Properly retrieve map element after saving and re-opening report (bug 336985)
  • Removed resource leaks

Calligra Stage

  • Re-enable KPresenter (KPR)-to-Open Document Presentation (ODP) document filter

Try It Out

About Calligra

Calligra Suite is a graphic art and office suite. It is a part of the applications family from the KDE community. See more information at the website http://www.calligra.org.

by Calligra News at July 05, 2014 10:43 AM

July 02, 2014

Planet KDE

KMyMoney – Port to KF5 has begun

A couple of days ago I received an email from Cristian, with two screenshots of KMyMoney running on KDE Frameworks 5.
There’s still lots to be done, but it’s a good start.
kmm-kf5_1
kmm-kf5
One thing where we’ll need help is getting a Qt5 version of KDChart. That’s what we use for charts in our reports. Calligra uses it too, so hopefully we’ll see something come up soon.

Cristian will be attending the Randa meeting in August, to work further on the port. Please, help make the sprint happen, donate to the fundraising and spread the word about it.

by Alvaro Soliverez (Hei_Ku) at July 02, 2014 08:08 PM

July 01, 2014

Google News

Представена е библиотеката WebODF 0.5.0 с възможност за редактиране ... - kaldata.com


Представена е библиотеката WebODF 0.5.0 с възможност за редактиране ...
kaldata.com
Публикувана е новата версия на JavaScript-библиотеката WebODF 0.5.0, позволяваща интегрирането в произволен сайт или уеб-приложение на средства за преглед, създаване и редактиране на документи с формат Document Format (ODF).

July 01, 2014 02:35 PM

Microsoft ha reso open source il suo OOXML SDK - oneBlog (Blog)


oneBlog (Blog)

Microsoft ha reso open source il suo OOXML SDK
oneBlog (Blog)
E non usa ODF, per cui il casino sopra si ripeterebbe potenzialmente ad ogni versione a COMPLETA DISCREZIONE di chi crea il software. MS lo fatto e sta racimolando miliardi con l'obbligo di farti aggiornare alla versione più recente, figurati se per ...

and more »

July 01, 2014 01:30 PM

WebODF 0.5 bringt Texteditor für ODF-Dokumente - Pro-Linux


ITespresso.de

WebODF 0.5 bringt Texteditor für ODF-Dokumente
Pro-Linux
WebODF ist eine JavaScript-Bibliothek, die das Ansehen und Bearbeiten von Dateien im Open-Document-Format (ODF) in Webseiten und in Programmen für PC oder Mobilgeräte ermöglicht und dabei nur Web-Standards verwendet. Auch das gemeinsame ...
WebODF 0.5 unterstützt Online-Editieren im Open Document FormatITespresso.de
WebODF 0.5: ODF-Dokumente im Browser editierenGolem.de

all 4 news articles »

July 01, 2014 09:49 AM

June 30, 2014

Planet KDE

WebODF v0.5.0 released: Highlights

Today, after a long period of hard work and preparation, having deemed the existing WebODF codebase stable enough for everyday use and for integration into other projects, we have tagged the v0.5.0 release and published an announcement on the project website.

Some of the features that this article will talk about have already made their way into various other projects a long time ago, most notably ownCloud Documents and ViewerJS. Such features will have been mentioned before in other posts, but this one talks about what is new since the last release.

The products that have been released as ‘supported’ are:

  • The WebODF library
  • A TextEditor component
  • Firefox extension

Just to recap, WebODF is a JavaScript library that lets you display and edit ODF files in the browser. There is no conversion of ODF to HTML. Since ODF is an XML-based format, you can directly render it in a browser, styled with CSS. This way, no information is lost in translation. Unlike other text editors, WebODF leaves your file structure completely intact.

The Editor Components

WebODF has had, for a long time, an Editor application. This was until now not a feature ‘supported’ to the general public, but was simply available in the master branch of the git repo. We worked over the months with ownCloud to understand how such an editor would be integrated within a larger product, and then based on our own experimentation for a couple of awesome-new to-be-announced products, designed an API for it.

As a result, the new “Wodo” Editor Components are a family of APIs that let you embed an editor into your own application. The demo editor is a reference implementation that uses the Wodo.TextEditor component.

There are two major components in WebODF right now:

  1. Wodo.TextEditor provides for straightforward local-user text editing,by providing methods for opening and saving documents. The example implementation runs 100% client-side, in which you can open a local file directly in the editor without uploading it anywhere, edit it, and save it right back to the filesystem. No extra permissions required.
  2. Wodo.CollabTextEditor lets you specify a session backend that communicates with a server and relays operations. If your application wants collaborative editing, you would use this Editor API. The use-cases and implementation details being significantly more complex than the Wodo.TextEditor component, this is not a ‘supported’ part of the v0.5.0 release, but will, I’m sure, be in the next release(s) very soon. We are still figuring out the best possible API it could provide, while not tying it to any specific flavor of backend. There is a collabeditor example in WebODF master, which can work with an ownCloud-like HTTP request polling backend.

These provide options to configure the editor to switch on/off certain features.

Of course, we wholeheartedly recommend that people play with both components, build great things, and give us lots of feedback and/or Pull Requests. :)

New features

Notable new features that WebODF now has include:

  • SVG Selections. It is impossible to have multiple selections in the same window in most modern browsers. This is an important requirement for collaborative editing, i.e., the ability to see other people’s selections in their respective authorship colors. For this, we had to implement our own text selection mechanism, without totally relying on browser-provided APIs.
    Selections are now smartly computed using dimensions of elements in a given text range, and are drawn as SVG polygon overlays, affording numerous ways to style them using CSS, including in author colors. :)
  • Touch support:
    • Pinch-to-zoom was a feature requested by ownCloud, and is now implemented in WebODF. This was fairly non-trivial to do, considering that no help from touch browsers’ native pinch/zoom/pan implementations could be taken because that would only operate on the whole window. With this release, the document canvas will transform with your pinch events.
    • Another important highlight is the implementation of touch selections, necessitated by the fact that native touch selections provided by the mobile versions of Safari, Firefox, and Chrome all behave differently and do not work well enough for tasks which require precision, like document editing. This is activated by long-pressing with a finger on a word, following which the word gets a selection with draggable handles at each end.
Touch selections

Drawing a selection on an iPad

  • More collaborative features. We added OT (Operation Transformations) for more new editing operations, and filled in all the gaps in the current OT Matrix. This means that previously there were some cases when certain pairs of simultaneous edits by different clients would lead to unpredictable outcomes and/or invalid convergence. This is now fixed, and all enabled operations transform correctly against each other (verified by lots of new unit tests). Newly enabled editing features in collaborative mode now include paragraph alignment and indent/outdent.

  • Input Method Editor (IME). Thanks to the persistent efforts of peitschie of QSR International, WebODF got IME support. Since WebODF text editing does not use any native text fields with the assistance of the browser, but listens for keystrokes and converts them into operations, it was necessary to implement support for it using JavaScript using Composition Events. This means that you can now do this:

Chinese - Pinyin (IBUS)

Chinese – Pinyin (IBUS)

and type in your own language (IBUS is great at transliteration!)

Typing in Hindi

Typing in Hindi

  • Benchmarking. Again thanks to peitschie, WebODF now has benchmarks for various important/frequent edit types. benchmark

  • Edit Controllers.  Unlike the previous release when the editor had to specifically generate various operations to perform edits, WebODF now provides certain classes called Controllers. A Controller provides methods to perform certain kinds of edit ‘actions’ that may be decomposed into a sequence smaller ‘atomic’ collaborative operations. For example, the TextController interface provides a removeCurrentSelection method. If the selection is across several paragraphs, this method will decompose this edit into a complex sequence of 3 kinds of operations: RemoveText, MergeParagraph, and SetParagraphStyle. Larger edits described by smaller operations is a great design, because then you only have to write OT for very simple operations, and complex edit actions all collaboratively resolve themselves to the same state on each client. The added benefit is that users of the library have a simpler API to deal with.

On that note…

We now have some very powerful operations available in WebODF. As a consequence, it should now be possible for new developers to rapidly implement new editing features, because the most significant OT infrastructure is already in place. Adding support for text/background coloring, subscript/superscript, etc should simply be a matter of writing the relevant toolbar widgets. :) I expect to see some rapid growth in user-facing features from this point onwards.

A Qt Editor

Thanks to the new Components and Controllers APIs, it is now possible to write native editor applications that embed WebODF as a canvas, and provide the editor UI as native Qt widgets. And work on this has started! The NLnet Foundation has funded work on writing just such an editor that works with Blink, an amazing open source SIP communication client that is cross-platform and provides video/audio conferencing and chat.

To fulfill that, Arjen Hiemstra at KO has started work on a native editor using Qt widgets, that embeds WebODF and works with Blink! Operations will be relayed using XMPP.

Teaser:
blink-prototype

Other future tasks include:

  • Migrating the editor from Dojo widgets to the Closure Library, to allow more flexibility with styling and integration into larger applications.
  • Image manipulation operations.
  • OT for annotations and hyperlinks.
  • A split-screen collaborative editing demo for easy testing.
  • Pagination support.
  • Operations to manipulate tables.
  • Liberating users from Google’s claws cloud. :)

If you like a challenge and would like to make a difference, have a go at WebODF. :)


by Aditya Bhatt (adityab) at June 30, 2014 09:43 PM

WebODF news

WebODF 0.5.0 released, gains text editor

WebODF text editor

WebODF text editor

KO GmbH and the developers of WebODF today released WebODF 0.5. After a long period of hard work, this new version features editing of OpenDocument Text files. It also contains lots of display improvements. WebODF still uses only HTML, CSS and JavaScript without any need for a special server software.

June 30, 2014 12:00 AM

June 29, 2014

Planet KDE

Thanks KDE

It's more than year of my encounter with source code of some real life application.(Thanks to KDE) I had never before seen such huge source code. The guidelines on techbase were so comprehensive that I didn't even realize that I had started fixing imperative bugs. The best part was that KDE had all types of applications, under various categories like multimedia, education, games etc. So I could try my hand on many different applications and recognize my interest. I enjoyed hacking source code of Kstars the most. And I compiled the code with the help of instruction on techbase and KDE's cool developers at IRC, who are always eager to help. I used to get fascinated on running those awesome application on my plasma desktop. I used to wonder how they work. The secret was revealed then. I sent mail in KDE developer's mailing list that I want to contribute and how do I start even though answer was there on techbase. And reply came that I can search though bugs related to application of my interest on bugzilla  and try to fix it. I did it. It was really so easy. 

Here, I have advice for students like me, who have very basic knowledge of any programming language and wants to contribute to open source, but are afraid that they have no experience and no experties  in language. LOL, you don't need to have experience to get experience. And when I started hecking into source code of KStars which is mostly written in C++, I had never written single line in C++ before, trust me. So don't worry if you are not expert in any language, all you need is quest to learn and little bit concept of programming. Take help from those cool techies hanging on IRCs. Don't hesitate to ask any question there, thinking that they might be stupid. They invest their time in answering your question rather than in rating it ;-). 

I had really cool year of coding. I have learn a lot in this one year. I have learn to talk to people, to search a solution from google, ways to learn and much more. Apart from all these KDE is full of opportunities like SoK, GSoC, meet-ups, conferences etc. Summer of code where we can learn skill to heck and code under guidance of well experienced mentors. And sprints like Randa, Calligra Sprint etc, where we have opportunity to meet those well experienced and expert of their areas, developers. Thanks KDE, thanks you very much for those superb opportunity, which are like dream for we students. 

BTW, I am going to this year's Randa meeting. I have seen photos and read though blogs of previous attendees. I can't wait for it. I have already made so many plans for discussions, fixing bugs and sharing ideas on Kstars.

KDE is already helping us in so many ways, so why don't we give it some token of thanks. Yes we can say thanks to KDE by making little contribution in organizing to one of such sprint i.e. Randa ;-) ofcourse. Please make little donation : http://www.kde.org/fundraisers/randameetings2014/index.php :) Your small drop will help us fill ocean ;-) 

Like Small drops make a mighty ocean

by Vijay Dhameliya (vijay13) at June 29, 2014 09:18 AM

June 28, 2014

Google News

Lipcse nyílt forrású irodai programcsomagra vált - Hungarian Unix Portal


Lipcse nyílt forrású irodai programcsomagra vált
Hungarian Unix Portal
A nyílt forrású irodai programcsomag bevezetésével párhuzamosan a város alapértelmezetté tette a belső dokumentumkezelésre az Open Document Format-ot (ODF). 2014 januárjában a város 4300 munkaállomásából 2792-n már futottak a nyílt forrás irodai ...

June 28, 2014 08:10 AM

June 26, 2014

Google News

OwnCloud 7 beta released - ZDNet


OwnCloud 7 beta released
ZDNet
The actual editing is done with ownCloud Documents, a cloud-based Open Document Format (ODF) editor. Once edited, the documents are converted back to Word format. Sound interesting? You can try the ownCloud 7 Community Edition beta today.

and more »

June 26, 2014 09:45 PM

June 23, 2014

Google News

新・OS X ハッキング! (121) BSDレイヤー温故知新(5)「固有コマンド:textutil」 - マイナビニュース


新・OS X ハッキング! (121) BSDレイヤー温故知新(5)「固有コマンド:textutil」
マイナビニュース
OS Xに付属の「テキストエディット」は、OpenOffice.orgと後継のLibreOfficeを中心にサポートされる「OpenDocument ForMat(ODF)」およびMicrosoft Office 2007以降の標準ファイル形式である「Office Open XML(OOXML)」の文書を読み書きできるが、textutilコマンドもほぼ ...

June 23, 2014 11:30 AM

June 20, 2014

Google News

Was bringt Open Source Software der Schweiz? - Computerworld


Computerworld

Was bringt Open Source Software der Schweiz?
Computerworld
Des Weiteren werde die Interoperabilität mit offenen Dokumentenformaten wie dem Open Document Format (ODF) oft vernachlässigt, sodass die Bevölkerung gezwungen wird Microsoft Office Produkte zu beschaffen um Behördenformulare bearbeiten zu ...

and more »

June 20, 2014 12:31 PM

June 18, 2014

Planet KDE

Thumbnails & previews for your Geo Data files (KML, GPX, OSM, …)

Almost two years ago (uh, already?) I went to Prague for a developer sprint of the team of Marble, the virtual globe and world atlas. My goal was to work on a proper maps shape plugin for Calligra.

We are ready to render, or? … Or?

Just, it showed that Marble at that time was not properly supporting the needs such a plugin has. Biggest showstopper was that Marble did not expose the information if and when all external data needed for rendering was available. Think e.g. of map pieces (so called tiles) still having to be downloaded from a server like OpenStreetMap‘s one. Not knowing the state is not good e.g. if a document with a map is to be rendered to a real printer.

Telling the File Manager some more about Marble and Geo Data Files

At that sprint then I worked instead on making sure that there are proper mime-types registered for the types of geo data files that Marble can read and display (like OSM data files, ESRI shapefiles and GPX files). So that such files are nicely displayed in the file manager with matching icon & type description and can get Marble assigned as handler. And:

[...]
Next step is to finish the thumbnail plugin, so one can also have nice previews of the content of these filetypes.
[...]

The thumbnailer was started in the train back from Prague, but Dresden was arrived before it was properly working. Then… the code went out of focus and mind, that step frozen in the middle of the air…

Getting ready to render!

These days, Calligra still has no maps shape plugin. Now and then I nag^Wbeg the Marble developers for the issue (how lame, indeed), as there are other interesting use cases for rendering of map stills, like:

  • Creating a jigsaw puzzle for Palapeli, the jigsaw puzzle gaming program
  • Creating an animation for a movie in Kdenlive, the video editor
  • Yes, even creating the thumbnails for geo data files, if not using the simple installed map theme

Last week luckily earthwings found some personal interest to draft code for renderer state. Time to add a bit of momentum, by reviving the thumbnailer code, to serve as a use case. Still found in its old place, after some bit-rot cleanup and finally solving the problems of last time (different mindset, and things seem so obvious) it works now good enough for serious usage:

Thumbnails for Geo Data files

Thumbnails for Geo Data files

Some things need some more thinking (which map theme to use when, how to properly detect the sky object the data is for, how to deal with thumbnail generation in offline-state), but it’s a good first complete step :) It does not yet use the new render state feature, but should be soon.

So look forward to Marble 1.9, bringing previews for geo data files to your filemanager and in the file dialogs! (And do not forget to enable them in Dolphin > Settings > Configure Dolphin… > General > Previews, disabled for all types by default).

And perhaps, perhaps, one day we finally also will have a maps shape plugin for Calligra…

BTW, if you want to help development of Marble, other KDE Edu projects and more, consider to donate for enabling the Randa Meetings 2014. Every little amount will help, as it sums up. Best do it now! :)


by Friedrich Kossebau (frinring) at June 18, 2014 10:02 PM

June 17, 2014

Planet KDE

Managing internal dependencies in a build of Calligra

During the move of KDE’s software projects from Subversion to Git most projects split their subprojects over multiple Git repositories. Calligra did not, but is keeping all code of all apps and extras in one single repository. That is all of the apps Author, Braindump, Flow, Karbon, Kexi, Krita, Plan, Sheets, Stage and Words as well as all of the extras like the file format converter, the Okular generators, file thumbnailers and other file manager integration.
One of the reasons is that many libraries and plugins are shared among the different programs, and the API of the libraries is still changing a lot between releases. By having API-changing commits to be atomic to all of the Calligra code, all developers have less problems to have consistent revisions of the libs and programs.

All can be too much

A downside is: people interested in only one of the Calligra programs still have to get all of the Calligra code and also are faced with possibly having to build all of Calligra. Such people could be developers working only on e.g. Kexi, users wanting to only build the bleeding edge of their favourite program, e.g. Krita, or packagers/integrators only interested in e.g. viewer components for office file formats.

To support the different building needs, by the time more and more all kind of if(SOMEFLAG) [...] endif(SOMEFLAG) were added to random CMakeLists.txt files. And with additionally the conditional building due to optional external dependencies, things got complex. And thus sometimes broken.

Products, Features, and Product Sets

To get things more structured again, the concepts of “product”, “feature” and “product set” have been introduced to describe the stuff that gets build and their internal dependencies:

A “product” is the smallest functional unit which can be created in the build and which is useful on its own when installed. Examples are e.g. libraries, plugins or executables. Products have external and internal required dependencies at build-time. Internal dependencies are noted in terms of other products or features (see below) and could be e.g. other libraries to link against or build tools needed to generate source files. A product gets defined by setting an identifier, a descriptive fullname and the needed internal build-time requirements. Any other product or feature listed as requirement must have been defined before.

Example:

calligra_define_product(BUILDTOOL_RNG2CPP "rng2cpp")
calligra_define_product(LIB_CALLIGRA "Calligra core libs"  REQUIRES BUILDTOOL_RNG2CPP)

A “feature” is not a standalone product, but adds abilities to one or multiple given products. One examples is e.g. scriptability. Features have external and internal required dependencies at build-time. Internal dependencies are noted in terms of other products or features and could be e.g. other libraries to link against or build tools needed to generate source files. A feature gets defined by setting an identifier, a descriptive fullname and the needed internal build-time requirements. Any other product or feature listed as requirement must have been defined before.

Example:

calligra_define_feature(FEATURE_SCRIPTING "Scripting feature")

A “product set” is a selection of products which should be build together. The products can be either essential or optional to the set. If essential (REQUIRED), the whole product set will not be build if a product is missing another internal or external dependency. If optional (OPTIONAL), the rest of the set will still be build in that case.
The products to include in a set can be listed directly or indirectly: they can be named themselves, or another product set can be included in a set, whose products will then be part of the first set as well.
Products and product sets can be listed as dependencies in multiple product sets. As with dependencies for products, they must have been defined before.

Example:

calligra_define_productset(STAGE "Full Stage (for Desktop)"
    REQUIRES
        APP_STAGE
    OPTIONAL
        # extras
        FILEMANAGER
        # plugins
        PLUGIN_DEFAULTTOOLS
        PLUGIN_ARTISTICTEXTSHAPE
        PLUGIN_DOCKERS
        PLUGIN_PATHSHAPES
        PLUGIN_VARIABLES
        PLUGIN_CHARTSHAPE
        PLUGIN_PICTURESHAPE
        PLUGIN_TEXTSHAPE
        PLUGIN_PLUGINSHAPE
        PLUGIN_FORMULASHAPE
        PLUGIN_VECTORSHAPE
        PLUGIN_VIDEOSHAPE
        # filters
        FILTERS_STAGE
)

There are a number of predefined product sets, but everyone can add their own custom product set by adding a file locally in the folder cmake/productsets, named with the name of the productset in lowercase and the extension “.cmake” and containing simply the definition as described above.
The ids of products and features (but not sets) are used to generate CMake variables SHOULD_BUILD_${ID}, which then are used to control what is build and how.

Deciding what to build

The product set(s) to build are passed via the CMake flag PRODUCTSET and are a whitespace separated list of product sets, products and features, though usually just a single product set, e.g. the predefined “ALL”, which is also the default.

Based on the dependency tree that is resulting from the definition of all products, features and product sets, then the internally required products and features are estimated for the requested set.
Following that it is checked whose of those have all needed external dependencies or must be disabled from the build. Finally then the internal dependencies are checked again, and the final set of products and features that will be really built is collected.

Seeing the dependencies

With the knowledge about the internal dependencies available, one is tempted to export this data in a format that can further processed, e.g. to visualize it. And thus now when running CMake, a file product_deps.dot in DOT notation is generated in the top-level build directory. This one can e.g. be transformed on the commandline into a PNG file, by

dot -Tpng product_deps.dot > product_deps.png

The following is generated for me currently when “ALL” products and features should be build (I am missing a few external dependencies for some filters):

Calligra product set "ALL"

Calligra product set “ALL”

If I would like to only build the KEXI and SHEETS product sets, by passing -DPRODUCTSET="KEXI SHEETS" to CMake, the graph changes to this, showing that only the products will be built which are required or optional in the dependency trees of both product sets:

Calligra product set "KEXI SHEETS"

Calligra product set “KEXI SHEETS”

More ideas

Besides creating pretty graphs to look at to get a (better) picture, other use cases might be possible:

  • packagers could get some template file created for the packages they would create from all of Calligra
  • Libs which are dependencies to other libs or app products could be automatically added to the target_link_libraries and their headers dirs to the include_directories
  • CI build servers could only build those products and features which would be affected by the new commits

Then a use-case seems to be that people would like to select a pre-defined product set, but blacklist a few of the products/features. Support for that still has to been developed and done.

I wonder how much of all this might make sense enough to be moved into CMake itself. Currently though this whole system still needs to prove its usefulness by being adapted in more detail by all of Calligra, not only most parts. There is also a chance of having over-engineered things :) And instead Calligra should be simply split over multiple repositories as well. Not sure.

Be enlightened and inspired

This blog post basically should explain a little what all this product sets stuff is about to both all Calligra contributors who have yet not looked into details as well as externals with perhaps similar problems as the Calligra project.

If this approach could be also a solution for you, have a look at the macros in cmake/modules/CalligraProductSetMacros.cmake, they should be reusable outside of Calligra as well, only the new macro calligra_product_deps_report has Calligra specific code inside and could be made generic as well, if there is interest.

kickstarter-29-front-ban


by Friedrich Kossebau (frinring) at June 17, 2014 01:17 AM

June 14, 2014

FreeCode

DataNucleus AccessPlatform 4.0.0

DataNucleus AccessPlatform is a standards-compliant Java persistence product. It is fully compliant with the JDO1, JDO2, JDO2.1, JDO2.2, JDO3, JPA1, JPA2 and JPA2.1 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 the MongoDB, LDAP, NeoDatis, JSON, Excel/ODF spreadsheets, XML, BigTable, HBase, and Neo4j databases.

Release Notes: Support for multi-column type converters for MongoDB, Neo4j, and HBase was added. Column length control for UUID support was added for RDBMS. A bug was fixed in the L2 cache update procedure for a transaction rollback. HBase internal API usage was upgraded to support current versions of HBase. The generic table/column model used by other datastores was adopted for RDBMS support also. The Eclipse plugin was fixed. Assorted fixes and minor improvements were also made.

Screenshot

Release Tags: JDO, JPA, Persistence

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

Licenses: Apache 2.0

by DataNucleus at June 14, 2014 06:27 AM

June 13, 2014

Google News

Computer experts stage street protest in Oslo against Microsoft document ... - The Age


Computer experts stage street protest in Oslo against Microsoft document ...
The Age
He said there was already a good ISO standard, called OpenDocument Format, or ODF, that allows documents to be opened by programs from different software companies. They also demanded reforms to the ISO to ensure "standardization of standardization ...

June 13, 2014 09:45 AM

June 05, 2014

Planet KDE

Calligra-powered Okular plugin for ODT, DOC & DOCX

You might know that Okular has a plugin system, for adding support for more document formats. And you might know that Calligra since years also provides a plugin to Okular, which adds support to view slides from files in the OpenDocument Presentation (ODP) format. And not only for the ODP format: by simply using the Calligra import filters for PPT and PPTX you can also view the slides locked away in those formats.

The different apps of Calligra used to be built on the KParts system, so any files in formats supported by them would be also viewable in KPart-embedding programs like Konqueror or KDevelop. But due to the currently on-going creation of a new MVC-oriented foundation for the Calligra programs this has changed, the Calligra modules are no more KParts.

Now I happen to now and then read ODT files directly in KDevelop. And Okular has some native support for ODT. But it is not as powerful as what I am used to from Calligra, so I wanted that back. The best thing of course would be to write a Calligra-plugin directly for KDevelop (like done for the Okteta integration). But I wanted something quicker, and with less work. Writing KPart-wrappers around the Calligra modules would have been the next option. But then I remembered that Sven, who did the Calligra ODP generator plugin for Okular, had also once started an ODT generator, but left it in a branch. And Okular also has an UI optimized for document reading. So a commit cherry-pick and some bit-rot fixes later I had ODT files nicely displayed in KDevelop again, thanks to the chain Calligra Words engine -> Okular KPart -> KDevelop :)

See here Okular displaying the ODT 1.2 spec, of course in ODT format:
Calligra-based ODT generator for Okular

And like the ODP generator plugin adds support for PPT and PPTX by simply using the existing filters, the very same is possible with the ODT generator plugin and the import filters for documents locked away in DOC and DOCX formats. A link on a webpage to a file in DOCX format? Click it and view the file directly in the Okular KPart, powered by Calligra’s ODT generator plugin and DOCX import filter:
Calligra-based DOCX generator for Okular

Currently the generators are just simple rendering ones. Of course we want the generators to be proper extended ones, including TextPage support, so you get all the comfort as you have when reading PDF files in Okular. Come and join the coding fun: navigate your editor to the generators’ code in extras/ and your browser to the excellent Okular generator Howto.

You instead would like to extend the support to other formats that Calligra has import filters for (Stage, Words)? Then take a look at the commit which added support for DOC and DOCX: just adding desktop files, per format one for the Application, one for the KPart and one for the generator itself :)

Waiting for your review request on the Review board (group “calligra”)!

Your preferred format is not yet there? Consider adding it, e.g. by joining the Document Liberation Project and adding also a import filter to Calligra.

So look forward to Calligra 2.9 later this year, bringing a better ODT viewer and some for DOC & DOCX to an Okular near your fingertips :) And perhaps more, at your will!


by Friedrich Kossebau (frinring) at June 05, 2014 09:49 PM

June 04, 2014

Planet KDE

Calligra Words and Author section handling state.

GSoC 2014 is running and I am working now on implementing outliner for Calligra Author.

Calligra Author is a special application to make creating novels and textbooks, those are usually big in size and require some specific tools during their creation to help their authors. As planned, Author should support 4 basic steps of developing a book:

  1. Concept and Planning
  2. Writing
  3. Review
  4. Publishing

The last 3 phases are already present in Author as a set of really helpful features. The goal of this project is to implement the tools for the first step and implement an outliner. It should support organizing scenes into some hierarchy and store additional data for them. You write each scene separately and define actors, items, time and date, etc. for it. Then outliner help you to check that all is consistent. You can see, for example, when some actor first time appears.

So I plan to use RDF meta-data to save outliner info and use openDocument sections to mark heirarchy of scenes.

I've started from implementing section handling. When I started to work on project, I found that current Calligra Words doesn't support sections at all (you can only open and without changing save document with sections). Fixing this is a first step for me and I'm still struggling with it, but have some results.

Below you can see current state of section boundary indication, it is for debug now, final version will be better.

Section boundary indication.
Next picture shows you how text insertion, deletion and copy-paste works:
Section handling in action
You can find all the code in words-section-deniskup branch on KDE Git of Calligra. And if you have some ideas or have found some bugs don't hesitate to write me.


by Denis Kuplyakov (denerkup) at June 04, 2014 03:42 PM

May 30, 2014

FreeCode

DataNucleus AccessPlatform 4.0.0 M4

DataNucleus AccessPlatform is a standards-compliant Java persistence product. It is fully compliant with the JDO1, JDO2, JDO2.1, JDO2.2, JDO3, JPA1, JPA2 and JPA2.1 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 the MongoDB, LDAP, NeoDatis, JSON, Excel/ODF spreadsheets, XML, BigTable, HBase, and Neo4j databases.

Release Notes: Performance for some cases was improved by 60%. Support for USING was added to Cassandra schema generation. Support for some PostgreSQL types was improved. Support for more java.time classes was added. Many bugs and minor features were fixed.

Screenshot

Release Tags: JDO, JPA, Persistence

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

Licenses: Apache 2.0

by DataNucleus at May 30, 2014 09:17 PM

May 26, 2014

Google News

LibreOffice 4.3 Beta available to try - PC Authority


LibreOffice 4.3 Beta available to try
PC Authority
LibreOffice 4.3 now supports the import and export of nested comments in ODF, DOC, DOCX and RTF files, while users can now opt to reformat all the comments in a document simultaneously. Images are now scaled proportionally by default (hold [Shift] to ...

May 26, 2014 10:15 PM

LibreOffice 4.3 Beta available to try, improves Start Center - BetaNews


BetaNews

LibreOffice 4.3 Beta available to try, improves Start Center
BetaNews
From this new release, the Start Center now offers previews of all file types, not just OpenOffice's own native ODF format. Users can now also selectively delete recent documents by rolling their mouse over a document and clicking the delete button ...

and more »

May 26, 2014 04:13 PM

Planet KDE

Want AppStream metadata for your KDE project? Act now!

And again, another KDE-AppStream post ;-) If you want to know more about AppStream metadata and why adding it to your project is a good idea, you might be interested in this blogpost (and several previous ones I wrote).

Originally, my plan was to directly push metadata to most KDE projects. The problem is that there is no way to reach all maintainers and have them opt-out for getting metadata pushed to their repositories. There is also no technical policy for a KDE project, since “KDE” is really only about the community right now, and there are no technical criteria a project under the KDE umbrella has to fulfill (at least to my knowledge, in theory, even GTK+ projects are perfectly fine within KDE).

Since I feel very uncomfortable in touching other people’s repositories without sending them a note first, I think the best way forward is an opt-in approach.

So, if you want your KDE project to ship metadata, follow these simple steps:

1. Check if there already is metadata for your project

That’s right – we already have some metadata available. Checkout the kde-appstream-metadata-templates repository at Github. You can take the XML file from there, if you want. Just make sure that there are no invalid tags in the description field (no <a/> nodes allowed, for example – the content is not HTML!), check if you have an SPDX-compliant <project_license/> tag, check if the provided public interfaces in the <provides/> tag match your project and also test if the URLs work.

Then you can copy the modified AppStream metadata to your project.

2. Write new metadata

How to write new metadata is described in detail at this TechBase Wiki page. Just follow the instructions.

In case you need help or want me to push the metadata to your project if you don’t have the time, you can also write me an email: matthias [{AT}] tenstral . net – or alternatively file a bug against the Github project linked above.

Don’t forget to have CMake install your shiny new metadata into /usr/share/appdata/.

All metadata you add to your project will automatically get translated by the KDE l10n scripts, no further action is required. So far, projects like Ark, K3b and Calligra are shipping metadata, and the number of AppStream-aware projects in KDE is growing constantly, which greatly improves their visibility in software centers, and will help distributions a lot in organizing installed software.

If you have further questions, please ask! .-)

by Matthias Klumpp (ximion) at May 26, 2014 02:17 PM

May 21, 2014

Google News

ドコモのNOTTV/フルセグ「TV BOX」にTwonky採用。リモート視聴など今後の展開を聞く - AV Watch


ドコモのNOTTV/フルセグ「TV BOX」にTwonky採用。リモート視聴など今後の展開を聞く
AV Watch
NTTドコモのスマホ/タブレットにも採用されている、マイクロソフトのDRM「PlayReady」を活用したパケットビデオの「PlayReady ODF(Open DRM Framework) SDK」も採用したことで、dビデオ、dアニメストア、dヒッツのコンテンツもテレビなどで利用できる。 TV BOXにTwonky ...

and more »

May 21, 2014 03:02 AM

May 20, 2014

Planet KDE

KDE Software Compilation 4.13.1 available in the stable repositories


KDE's first update of its 4.13 series of Applications and Development Platform is now available in Chakra's stable repositories.

This release was targeted at updating translations and bug fixing, with over 50 bugs being resolved. According to the official release announcement, these "include improvements to Personal Information Management suite Kontact, Umbrello UML Modeller, the Desktop search functionality, web browser Konqueror and the file manager Dolphin".

In addition, this move includes:

  • A new artwork set code-named "Sirius", which will be shipped with the upcoming ISO, with new themes for GRUB, KDM, KSplash, Yakuake and a new Desktop wallpaper
  • octopi, a pacman GUI which will replace our previously used fork named oktopi, since they have both merged upstream
  • Linux kernel rebuild with security patch for CVE
  • Calligra suite 2.8.3
  • LibreOffice 4.2.4
  • Two new kcm modules that when installed are available in system settings, kcm-pacman-repoeditor for editing pacman repositories and kcm-about-distro which shows a small summary of your system and installation
  • Various other package updates and bug fixes.

    As always, make sure your mirror is fully synchronized before performing this update. To check, run mirror-check in Konsole, or use the mirror-check application found under the "Internet" category in the application launcher.
  • by Chakra OS at May 20, 2014 09:39 PM

    May 17, 2014

    ODF Wikipedia Page

    89.173.219.155: /* Standardization */ added references and parts

    Standardization: added references and parts

    ← Previous revision Revision as of 08:19, 17 May 2014
    Line 137: Line 137:
     
    *The [[ Organization for the Advancement of Structured Information Standards|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=22 November 2009}}</ref> It includes the editorial changes made to address JTC1 ballot comments. It is available in ODF, HTML and PDF formats.
     
    *The [[ Organization for the Advancement of Structured Information Standards|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=22 November 2009}}</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=31 October 2006 | 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=6 February 2007 | 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=15 February 2007 | 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>{{cite web|url=http://www.zdnet.co.uk/talkback/0,1000001161,39409700-39001068c-20093634o,00.htm|title=OOXML expert: ODF standard is broken|author=Peter Judge|publisher=ZDNet|date=2 May 2008 -- 14:47 GMT (07:47 PDT)|accessdate=10 September 2012}}</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 name="iso.org"/><ref name="http"/>
     
    *'''[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=31 October 2006 | 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=6 February 2007 | 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=15 February 2007 | 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>{{cite web|url=http://www.zdnet.co.uk/talkback/0,1000001161,39409700-39001068c-20093634o,00.htm|title=OOXML expert: ODF standard is broken|author=Peter Judge|publisher=ZDNet|date=2 May 2008 -- 14:47 GMT (07:47 PDT)|accessdate=10 September 2012}}</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 name="iso.org"/><ref name="http"/>
    *'''[http://docs.oasis-open.org/office/v1.2/OpenDocument-v1.2.pdf 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=5 October 2011 |accessdate=12 April 2012}}</ref><ref>{{citation |url=http://www.oasis-open.org/committees/office/ |title=OASIS Open Document Format for Office Applications (OpenDocument) TC |accessdate=12 April 2012}}</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. In October 2011, the OASIS ODF Technical Committee expected to "start the process of submitting ODF 1.2 to ISO/IEC JTC 1 soon".<ref name="odf12" /> In May 2012, the ISO/IEC JTC 1/SC 34/WG 6 members reported that ''after some delay, the process of preparing ODF 1.2 for submission to JTC 1 for PAS transposition is now in progress''.<ref>{{citation |url=http://kikaku.itscj.ipsj.or.jp/sc34/open/1777.pdf |title=Minutes of teleconference meeting of ISO/IEC JTC 1/SC 34/WG 6, 2012-05-23 |format=PDF |quote=Patrick Durusau reported that, after some delay, the process of preparing ODF 1.2 for submission to JTC 1 for PAS transposition is now in progress. It is not yet know when the submission will be ready ... |accessdate=21 October 2012}}</ref> In 2013, the members of the OASIS OpenDocument technical committee requested that OASIS submit the ODF 1.2 to ISO/IEC JTC1 for approval as a proposed International Standard under JTC's "Publicly Available Specification" (PAS) transposition procedure.<ref>{{citation |url=https://www.oasis-open.org/news/announcements/member-review-of-proposed-submission-of-odf-v1-2-to-iso-iec-jtc1 |title=Member Review of Proposed Submission of ODF v1.2 to ISO/IEC JTC1 |date=2013-08-19 |accessdate=2014-01-31}}</ref> As of 3 April 2014, ODF 1.2 had reached the enquiry stage of ISO's ratification process.<ref name="DIS 26300-1">{{cite web|title=ISO/IEC DIS 26300-1|url=http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=66363|publisher=ISO|accessdate=9 April 2014}}</ref>
    +
    *'''[http://docs.oasis-open.org/office/v1.2/OpenDocument-v1.2.pdf 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=5 October 2011 |accessdate=12 April 2012}}</ref><ref>{{citation |url=http://www.oasis-open.org/committees/office/ |title=OASIS Open Document Format for Office Applications (OpenDocument) TC |accessdate=12 April 2012}}</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. OpenDocument 1.2 consists of three parts: Part 1: OpenDocument Schema, Part 2: Recalculated Formula (OpenFormula) Format and Part 3: Packages. In October 2011, the OASIS ODF Technical Committee expected to "start the process of submitting ODF 1.2 to ISO/IEC JTC 1 soon".<ref name="odf12" /> In May 2012, the ISO/IEC JTC 1/SC 34/WG 6 members reported that ''after some delay, the process of preparing ODF 1.2 for submission to JTC 1 for PAS transposition is now in progress''.<ref>{{citation |url=http://kikaku.itscj.ipsj.or.jp/sc34/open/1777.pdf |title=Minutes of teleconference meeting of ISO/IEC JTC 1/SC 34/WG 6, 2012-05-23 |format=PDF |quote=Patrick Durusau reported that, after some delay, the process of preparing ODF 1.2 for submission to JTC 1 for PAS transposition is now in progress. It is not yet know when the submission will be ready ... |accessdate=21 October 2012}}</ref> In 2013, the members of the OASIS OpenDocument technical committee requested that OASIS submit the ODF 1.2 to ISO/IEC JTC1 for approval as a proposed International Standard under JTC's "Publicly Available Specification" (PAS) transposition procedure.<ref>{{citation |url=https://www.oasis-open.org/news/announcements/member-review-of-proposed-submission-of-odf-v1-2-to-iso-iec-jtc1 |title=Member Review of Proposed Submission of ODF v1.2 to ISO/IEC JTC1 |date=2013-08-19 |accessdate=2014-01-31}}</ref> As of 3 April 2014, ODF 1.2 had reached the enquiry stage of ISO's ratification process.<ref name="DIS 26300-1">{{cite web|title=ISO/IEC DIS 26300-1 - Information technology - Open Document Format for Office Applications (OpenDocument) v1.2 - Part 1: OpenDocument Schema |url=http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=66363 |publisher=ISO |accessdate=9 April 2014}}</ref><ref name="DIS 26300-2">{{cite web |title=ISO/IEC DIS 26300-2 - Information technology - Open Document Format for Office Applications (OpenDocument) v1.2 - Part 2: Recalculated Formula (OpenFormula) Format |url=http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=66375 |publisher=ISO |accessdate=2014-05-17}}</ref><ref name="DIS 26300-3">{{cite web |title=ISO/IEC DIS 26300-3 - Information technology - Open Document Format for Office Applications (OpenDocument) v1.2 - Part 3: Packages |url=http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=66376 |publisher=ISO |accessdate=2014-05-17}}</ref>
       
     
    ===Future===
     
    ===Future===

    by 89.173.219.155 at May 17, 2014 08:19 AM

    May 16, 2014

    Google News

    开源办公套件Calligra 2.8.3 发布 - LUPA开源社区


    开源办公套件Calligra 2.8.3 发布
    LUPA开源社区
    Calligra 使用开放文件格式(ODF,OpenDocument Format)作为默认的文件格式,并兼容其他文件格式,如Microsoft Office 的文件。Calligra依赖于KDE技术,常与KDE Software Compilation 相结合。 最新版本Calligra 2.8.3 ...

    May 16, 2014 04:01 AM

    May 15, 2014

    Planet KDE

    Calligra 2.8.3 Released

    This is the third (and last but one) update to the 2.8 series of the Calligra Suite, and Calligra Active released to fix recently found issues. The Calligra team recommends everybody to update.

    Issues Fixed in This Release

    General

    • Add support for line breaks when reading the OpenDocument Format.
    • Fix a bug in the style manager for filters.
    • Make the text shape (specifically the dock panel) work on Windows 8.1.
    • Excel document support: add support for 1904-based XLS files, typically created by Excel on Mac OS X.

    Kexi

    • Fix crash when closing form design window and color property isn’t saved. (bug 333551)
    • Make context menu work for tables in Query Designer.
    • Make it possible to set solid and inherited background color in form widgets. “Auto Fill Background” property has been added for this. It’s set to true when user selects background color. (bugs 333548, 333549)
    • Fixed crash in Debug GUI when trying to modify table field. (bug 333933)
    • Updated list of SQL keywords reserved for KexiSQL, SQLite, MySQL and PostgreSQL.
    • Make it possible to use reserved words as names for table columns. (bug 332160)
    • Fix crashes when closing tabs or windows (bug 334234)
    • Removed a number of resource leaks.

    Krita

    • Translation fix in the Multihand tool: Axis -> Axes.
    • More precise translations. (bug 333135)
    • A fix for the outline of invert selection.
    • Krita no longer closes immediately when a file is corrupted but gently warns the user.
    • Fix bug: deleting Group-Layer and contents when there are no other layers prevented user from creating new layers (crash). (bug 333496)
    • Improved detection of supported image formats.
    • Removed a number of resource leaks.
    • Add support for selection in GMIC filters. (bug 325771)
    • Fix crash when GMIC filter is applied to the layer which was moved. (bug 327980)
    • Add search box for filter names of the GMIC plug-in. A text box below the filters tree can now be used to find the GMIC filter by name.
    • Select only paint layers when gathering all Krita layers from layer stack.
    • Remember the last used preset across sessions.
    • Fix invalid recalculation of width and height between units.
    • Ensure that the channel flags are always reset when they are set to full, otherwise compositing will not be will work not efficient. (bug 333080)
    • Fix painting grid on lower zoom levels. (bug 333234)
    • Fix a triangular brush outline for a 1-pixel brush. (bug 334408)
    • Fix pixel-alignment of the Rectangle and Ellipse tools, perform alignment exactly how the user expects. (bug 334508)
    • Make layer actions such as “Delete the layer or mask” listed in the in Configure Shortcuts dialog. (bug 332367)
    • Fix handling a tablet when “Pan/Scroll” mode is assigned to a button. Note: Wacom’s “Pan/Scroll” feature supports only vertical wheel scroll, so using usual Middle-button panning is recommended. (bug 334204)
    GMIC filter search

    GMIC filter search in Krita

    Calligra Words

    • Export to text: fix missing number of spaces in the text:s tag.
    • Export to text: fix missing newlines after a heading.
    • Export to text: add support for line breaks.

    Try It Out

    About Calligra

    Calligra Suite is a graphic art and office suite. It is a part of the applications family from the KDE community. See more information at the website http://www.calligra.org.

    by Calligra News at May 15, 2014 10:25 AM

    May 13, 2014

    Google News

    В Мюнхене 15 тыс. муницицпальных компьютеров переведены на Linux - Total.kz


    В Мюнхене 15 тыс. муницицпальных компьютеров переведены на Linux
    Total.kz
    LiMux несет с собой полностью готовое к использованию десктопное окружение на базе СПО, в том числе свободные офисные программы OpenOffice, которые работают с открытым форматом Open Document Format (ODF). Этот формат стал ...

    and more »

    May 13, 2014 07:57 AM

    В Мюнхене 15 тыс. муницицпальных компьютеров переведены на Linux - Total.kz


    В Мюнхене 15 тыс. муницицпальных компьютеров переведены на Linux
    Total.kz
    LiMux несет с собой полностью готовое к использованию десктопное окружение на базе СПО, в том числе свободные офисные программы OpenOffice, которые работают с открытым форматом Open Document Format (ODF). Этот формат стал ...

    and more »

    May 13, 2014 07:46 AM

    Как Мюнхен перевёл 15 000 ПК с Windows на Linux - InternetUA


    InternetUA

    Как Мюнхен перевёл 15 000 ПК с Windows на Linux
    InternetUA
    LiMux несет с собой полностью готовое к использованию десктопное окружение на базе СПО, в том числе свободные офисные программы OpenOffice, которые работают с открытым форматом Open Document Format (ODF). Этот формат стал ...

    and more »

    May 13, 2014 06:47 AM

    May 12, 2014

    Google News

    Как Мюнхен перевёл 15 000 ПК с Windows на Linux - GIGAmir


    GIGAmir

    Как Мюнхен перевёл 15 000 ПК с Windows на Linux
    GIGAmir
    LiMux несет с собой полностью готовое к использованию десктопное окружение на базе СПО, в том числе свободные офисные программы OpenOffice, которые работают с открытым форматом Open Document Format (ODF). Этот формат стал ...

    May 12, 2014 04:23 PM

    8 ứng dụng miễn phí tốt nhất cho năm 2014 - Khoa Học Phổ Thông


    8 ứng dụng miễn phí tốt nhất cho năm 2014
    Khoa Học Phổ Thông
    Mặc dù định dạng mặc định nó dùng là ODF (Open Document Format), chương trình vẫn có thể đọc và lưu các định dạng DOC và DOCX. Với DOCX, việc hiển thị file có đôi chút thua kém so với Microsoft Office. Chương trình có thêm một sidebar ở bên phải ...

    May 12, 2014 12:43 AM

    May 10, 2014

    ODF Wikipedia Page

    Emk (ja): fix dead el

    fix dead el

    ← Previous revision Revision as of 09:03, 10 May 2014
    Line 137: Line 137:
     
    *The [[ Organization for the Advancement of Structured Information Standards|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=22 November 2009}}</ref> It includes the editorial changes made to address JTC1 ballot comments. It is available in ODF, HTML and PDF formats.
     
    *The [[ Organization for the Advancement of Structured Information Standards|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=22 November 2009}}</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=31 October 2006 | 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=6 February 2007 | 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=15 February 2007 | 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>{{cite web|url=http://www.zdnet.co.uk/talkback/0,1000001161,39409700-39001068c-20093634o,00.htm|title=OOXML expert: ODF standard is broken|author=Peter Judge|publisher=ZDNet|date=2 May 2008 -- 14:47 GMT (07:47 PDT)|accessdate=10 September 2012}}</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 name="iso.org"/><ref name="http"/>
     
    *'''[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=31 October 2006 | 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=6 February 2007 | 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=15 February 2007 | 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>{{cite web|url=http://www.zdnet.co.uk/talkback/0,1000001161,39409700-39001068c-20093634o,00.htm|title=OOXML expert: ODF standard is broken|author=Peter Judge|publisher=ZDNet|date=2 May 2008 -- 14:47 GMT (07:47 PDT)|accessdate=10 September 2012}}</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 name="iso.org"/><ref name="http"/>
    *'''[http://docs.oasis-open.org/office/v1.2/OpenDocument-v1.2.pdf 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=5 October 2011 |accessdate=12 April 2012}}</ref><ref>{{citation |url=http://www.oasis-open.org/committees/office/ |title=OASIS Open Document Format for Office Applications (OpenDocument) TC |accessdate=12 April 2012}}</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. In October 2011, the OASIS ODF Technical Committee expected to "start the process of submitting ODF 1.2 to ISO/IEC JTC 1 soon".<ref name="odf12" /> In May 2012, the ISO/IEC JTC 1/SC 34/WG 6 members reported that ''after some delay, the process of preparing ODF 1.2 for submission to JTC 1 for PAS transposition is now in progress''.<ref>{{citation |url=http://www.itscj.ipsj.or.jp/sc34/open/1777.pdf |title=Minutes of teleconference meeting of ISO/IEC JTC 1/SC 34/WG 6, 2012-05-23 |format=PDF |quote=Patrick Durusau reported that, after some delay, the process of preparing ODF 1.2 for submission to JTC 1 for PAS transposition is now in progress. It is not yet know when the submission will be ready ... |accessdate=21 October 2012}}</ref> In 2013, the members of the OASIS OpenDocument technical committee requested that OASIS submit the ODF 1.2 to ISO/IEC JTC1 for approval as a proposed International Standard under JTC's "Publicly Available Specification" (PAS) transposition procedure.<ref>{{citation |url=https://www.oasis-open.org/news/announcements/member-review-of-proposed-submission-of-odf-v1-2-to-iso-iec-jtc1 |title=Member Review of Proposed Submission of ODF v1.2 to ISO/IEC JTC1 |date=2013-08-19 |accessdate=2014-01-31}}</ref> As of 3 April 2014, ODF 1.2 had reached the enquiry stage of ISO's ratification process.<ref name="DIS 26300-1">{{cite web|title=ISO/IEC DIS 26300-1|url=http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=66363|publisher=ISO|accessdate=9 April 2014}}</ref>
    +
    *'''[http://docs.oasis-open.org/office/v1.2/OpenDocument-v1.2.pdf 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=5 October 2011 |accessdate=12 April 2012}}</ref><ref>{{citation |url=http://www.oasis-open.org/committees/office/ |title=OASIS Open Document Format for Office Applications (OpenDocument) TC |accessdate=12 April 2012}}</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. In October 2011, the OASIS ODF Technical Committee expected to "start the process of submitting ODF 1.2 to ISO/IEC JTC 1 soon".<ref name="odf12" /> In May 2012, the ISO/IEC JTC 1/SC 34/WG 6 members reported that ''after some delay, the process of preparing ODF 1.2 for submission to JTC 1 for PAS transposition is now in progress''.<ref>{{citation |url=http://kikaku.itscj.ipsj.or.jp/sc34/open/1777.pdf |title=Minutes of teleconference meeting of ISO/IEC JTC 1/SC 34/WG 6, 2012-05-23 |format=PDF |quote=Patrick Durusau reported that, after some delay, the process of preparing ODF 1.2 for submission to JTC 1 for PAS transposition is now in progress. It is not yet know when the submission will be ready ... |accessdate=21 October 2012}}</ref> In 2013, the members of the OASIS OpenDocument technical committee requested that OASIS submit the ODF 1.2 to ISO/IEC JTC1 for approval as a proposed International Standard under JTC's "Publicly Available Specification" (PAS) transposition procedure.<ref>{{citation |url=https://www.oasis-open.org/news/announcements/member-review-of-proposed-submission-of-odf-v1-2-to-iso-iec-jtc1 |title=Member Review of Proposed Submission of ODF v1.2 to ISO/IEC JTC1 |date=2013-08-19 |accessdate=2014-01-31}}</ref> As of 3 April 2014, ODF 1.2 had reached the enquiry stage of ISO's ratification process.<ref name="DIS 26300-1">{{cite web|title=ISO/IEC DIS 26300-1|url=http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=66363|publisher=ISO|accessdate=9 April 2014}}</ref>
       
     
    ===Future===
     
    ===Future===

    by Emk (ja) at May 10, 2014 09:03 AM

    May 09, 2014

    Google News

    The pdf graveyards can only expect an increase in their undead populations - The Guardian


    The Guardian

    The pdf graveyards can only expect an increase in their undead populations
    The Guardian
    In Britain, the Cabinet Office recommended in January that the government should use open standards, including ODF, html, CSV (for spreadsheets), plain text, and (sorry, democracy) pdf – but only "for static versions of non-statistical data produced ...

    and more »

    May 09, 2014 05:35 PM

    May 07, 2014

    Google News

    Microsoft moins cher que l'open source sur le long terme, selon le DSI de ... - Developpez.com


    Microsoft moins cher que l'open source sur le long terme, selon le DSI de ...
    Developpez.com
    Le gouvernement britannique avait même manifesté son intention de faire adopter le format open source ODF comme standard pour les documents électroniques. Cependant, de façon pratique, l'open source pourrait ne pas être une solution moins chère par ...

    May 07, 2014 07:41 AM

    アシスト、クリエイティブ・コモンズ・ライセンスで「LibreOffice」の研修用テキストを公開 - SankeiBiz


    アシスト、クリエイティブ・コモンズ・ライセンスで「LibreOffice」の研修用テキストを公開
    SankeiBiz
    Microsoft Officeとの互換性も高く、大手企業/自治体による採用実績が増加していること、ファイル形式に国際標準規格(ISO26300)および日本工業規格(JIS X4401)に登録されているODF(OpenDocument Format)を採用していることなどから注目を集めています。

    and more »

    May 07, 2014 03:14 AM

    アシスト、クリエイティブ・コモンズ・ライセンスで「LibreOffice」の研修用テキストを公開 - @Press (プレスリリース)


    アシスト、クリエイティブ・コモンズ・ライセンスで「LibreOffice」の研修用テキストを公開
    @Press (プレスリリース)
    Microsoft Officeとの互換性も高く、大手企業/自治体による採用実績が増加していること、ファイル形式に国際標準規格(ISO26300)および日本工業規格(JIS X4401)に登録されているODF(OpenDocument Format)を採用していることなどから注目を集めています。

    and more »

    May 07, 2014 03:06 AM

    May 01, 2014

    Planet KDE

    Calligra 2.8.1 is Out

    Packages for the release of KDE's document suite Calligra 2.8.1 are available for Kubuntu 12.04 LTS and 13.10. You can get it from the Kubuntu Backports PPA (alongside KDE SC 4.13). They are also in our development release.

    by Kubuntu News at May 01, 2014 10:02 PM

    Google News

    1億回ダウンロード越えした「Apache OpenOffice」、バージョン4.1を公開 - SourceForge.JP Magazine


    1億回ダウンロード越えした「Apache OpenOffice」、バージョン4.1を公開
    SourceForge.JP Magazine
    新機能としては、ワープロソフト「Writer」でテキスト範囲にコメントや注釈を付けられるようになった。コメントの範囲のハイライト表示も可能。この機能はODFOpen Document Format)1.2で実装されたもので、OOXMLファイルフォーマットとの互換性を強化するという。

    May 01, 2014 05:56 AM

    April 30, 2014

    Google News

    OS X 10.7 or later - TechCentral.ie


    OS X 10.7 or later
    TechCentral.ie
    OpenOffice also saves your documents in the open document format (ODF) meaning that they can be opened within other office suites, even Office itself. Version 4.1 comes with the following significant changes: - Mac OS X version is now 64-bit and ...

    April 30, 2014 01:46 PM

    정부 오피스 SW 시장, 한컴 독주 끝날까 - 디지털데일리


    디지털데일리

    정부 오피스 SW 시장, 한컴 독주 끝날까
    디지털데일리
    ODF는 오픈도큐먼트포맷(Open Document Format)의 약자로, 국제표준화기구(ISO)의 표준 승인을 받은 오픈소스 기반의 문서파일 형식이다. 현재 브라질, 크로아티아, 덴마크, 에콰도르, 헝가리, 이탈리아, 말레이시아, 러시아, 남아프리카공화국 등에서 ODF를 국가 ...

    and more »

    April 30, 2014 12:57 AM

    April 29, 2014

    FreeCode

    DataNucleus AccessPlatform 4.0.0 M3

    DataNucleus AccessPlatform is a standards-compliant Java persistence product. It is fully compliant with the JDO1, JDO2, JDO2.1, JDO2.2, JDO3, JPA1, JPA2 and JPA2.1 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 the MongoDB, LDAP, NeoDatis, JSON, Excel/ODF spreadsheets, XML, BigTable, HBase, and Neo4j databases.

    Release Notes: The bytecode enhancement contract was changed, meaning JPA users no longer need the JDO API jar to be present. Support for multi-column type converters was added for Excel, ODF, and JSON datastores. Schema evolution and query in-datastore support was added for Cassandra. Support for JPA exclude-unlisted-classes was fixed. EclipsePluginRegistry was dropped in favour of OSGiPluginRegistry. Many other bugs were fixed and improvements were made.

    Screenshot

    Release Tags: JDO, JPA, Persistence

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

    Licenses: Apache 2.0

    by DataNucleus at April 29, 2014 01:16 PM

    April 24, 2014

    Google News

    Malawi Records No Cholera Case in Two Years - AllAfrica.com


    Malawi Records No Cholera Case in Two Years
    AllAfrica.com
    ... sanitation and hygiene messages to the masses through various channels; print and electronic and the involvement of local leaders in community initiatives such as Community Led Total Sanitation (CLTS) which advocates for ODF (Open Defecation Free) ...

    April 24, 2014 03:52 AM

    April 23, 2014

    Google News

    What Life Is Like When Having Your Period Means You Are Shunned by Society - Pacific Standard


    What Life Is Like When Having Your Period Means You Are Shunned by Society
    Pacific Standard
    But what the hell can we do?” On the four-hour road trip from Nepalgunj, the location of the nearest airport, we encountered signs in Nepali, declaring villages to be ODF (open-defecation-free), meaning that they now have adequate toilets. But many do ...

    April 23, 2014 07:13 PM

    April 20, 2014

    Charles H. Schulz

    LibreOffice, the distraction-free way

    There is a growing momentum towards specialized “text editors” these days, and these tools are not meant for “geeks” or “hackers”, far from that: there are targeted at people who write long chunks of texts, and only text. You may have already guessed who they might be: fiction writers, journalists, etc. There is now a nice ecosystem of tools, most of them non free software, like Scrivener, that is in full expansion. If I’d tell you office suites can offer just the same benefits, you would call me biased. And indeed I might be. Just a tad…. But it’s true. On the other hand, people having specific needs in the way they write and edit texts are very real, from developers to fiction writers. The question is: should an office suite like LibreOffice accomodate everyone – and does it already?

    I will first show how to turn LibreOffice into a distraction-free text editor -yes you can do that quite easily- and then I will try to answer the question above: should an office suite like LibreOffice accomodate everyone? in an attempt at defining what LibreOffice, and especially Writer, is and does as a tool.

    LibreOffice Writer as a distraction-free text editor in a few simple steps:

    The whole point of the following suggestions is to take away elements from LibreOffice’s writer interface.

    1. Get rid of the ruler: Go to the View top menu then unselect the Ruler
    2. Take away any unwanted toolbar from the same View menu (then use the Toolbar submenu), such as Drawing or WordArt bars. Don’t get me wrong: you could make every bar disappear but it’s not helpful: just get rid of what you think is clutter.
    3. In the Options menu go to Writer, Appearance, then change the Application background to a shade of dark grey (70 up to 90%). Do not mistake this with the document background, there’s a specific entry for the Writer background.
    4. The last step is  optional: get rid of the Stylist vertical integration. Many people do not have this as a default, I do because it makes me save time when I have to select styles as I’m typing a document. To me, it’s not clutter so I left it that way. Below is a screenshot of LibreOffice in distraction-free mode with the stylist nested on the right, while the second screenshot is the same configuration of LibreOffice without the nested stylist. LibreOffice_distractionfree_stylist

    Why do I mention the stylist? Because using styles is pretty much the single most important tool you need to be familiar with when using an office suite. Any office suite, that’s to say, otherwise you will end up wondering why office suites are so complex when you just have to type a letter to your insurance company… although there’s certainly a huge userbase for that.

    LibreOffice_distractionfree_enneagon

    What do styles do? They structure your document visually and logically. They make the difference between a simple text with bold, underlined and italic words appearing from time to time, and an ordered document with chapters, sections, paragraphs that stands both the test of time (and format conversion) and multiple revisions or updates. They also help you create great looking documents and create templates. In a nutshell, using LibreOffice without styles is like driving a car in first gear or using Emacs only through the scratch buffer (that one’s for the geeks). By the way, the same is true for MS Office styles, but LibreOffice and its predecessor OpenOffice.org are known to handle styles in a consistently more powerful way.

    But styles cannot  do everything. They cannot magically turn an office suite into a full development environment or code editor for instance. That would be pushing the enveloppe a bit too far. Which prompts the question of what an office suite like LibreOffice can, could and should do.

    It is clear to anyone who used an office suite and code editors or IDEs such as Emacs, Cloud9 (code editor in the cloud) , NetBeans or Eclipse, that LibreOffice serves different needs. There is no will, and no point for anyone to turn LibreOffice into a code editor (aside the macro and dialog editor that’s already embedded in the suite, as shown on the right), because an office suite is not and will never be a development environment. LibreOffice_macroeditor

    It is not rare to hear that word processors are a thing of a past, but that’s  an ill-informed opinion. It is not that the cloud is supposedly overthrowing everything, but rather it comes, I think, from several misconceptions and prejudices about office suites. Let me first hint at what word processors are not:

    • code editors: Seriously, some people need to drop that ball. I’m the first one to wish for a full blown html editor that works inside LibreOffice, but certainly not for a full suite with compilers and debuggers. These are specific tools, aimed at a specific range of uses.
    • LaTeX editors: I have good friends who use these – in short, these are powerful tools allowing you to focus on text and then frame and format the text the way you want in a programmatic way. These editors require a lot of practice and learning before you can use them. LaTex editors are used mostly in academic fields. They are not word processors, and to be honest, the notion that you must spend years of training to design a document in LaTex even in 2014 strikes me as nonsensical.
    • wordpads, simple text editors: a word processor can definitely do that, but you could of course use  something less complex, if all you need is a simple text editor such as TextEdit or WordPad.
    • online pads; if you were to implement a collaborative stack in an office suite, it could actually be turned into an etherpad/framapad type of tool, although the value of a word processor may lie elsewhere.

    At this stage then, it becomes useful to try to define what a word processor does and why it matters.

    A word processor edits and handles documents . Not code, not notes (although it could), only actual documents. Faced with this shockingly simple yet – in my humble opnion powerful – assertion, what do we do with it?

    Word processors help you read, edit, save, open documents in a very fast and relatively easy way compared to everything else. Documents are not only made up of words and sentences. They come with a structural logic, specific formating, styles, layouts and graphical elements. While it may appeal to one of the broadest audience on the earth (people who have access to a computer and would like to write a document, such as a letter or a book or a shopping list) it does not mean that word processors or office suites are made for everyone else except developers, engineers and fiction writers. It means word processors excel at editing documents in a powerful way without much of training (compared to a full fledged academic or technical cursus in learning vi, emacs, LaTex editors…) and this uncanny ability  does not really exist among any other tool out there. Sure, if you spend four years editing a document in LaTex, you will likely learn enough to make your PhD. thesis look good. Sure, there’s a customized major mode in Emacs enabling some proper visual document to be edited, but you need to know and learn about it beforehand, customize it some more, get acquainted with the custom shortcuts, etc.

    I’m not berating these tools: I’m a regular and devout Emacs user myself. But I do love the comfort and smoothness of firing up LibreOffice Writer and write that nice memo or strategic overview for the Document Foundation just by pointing on the stylist, clicking, expressing my thoughts through the text I’m wirting, changing the fonts, run the spell checker, saving the document, closing it. Tomorrow, when I’ll open it, it will look just as good, and I might even make it look crisper for the benefits of my readers. How long will it take me? A couple of minutes. Ten, if I’m in the mood of changing everything. It cannot get any easier than that. Office suites, and especially word processors are powerful tools. They help create and develop one’s intelligence, and by sharing documents enhance the collective intelligence of groups and crowds. They are meant to be what the LibreOffice project strives to provide: engines of creation, tools for intelligence.

    by Charles at April 20, 2014 01:10 PM

    April 18, 2014

    Google News

    다운로드 1억건 돌파한 '오픈오피스' - 블로터닷넷


    블로터닷넷

    다운로드 1억건 돌파한 '오픈오피스'
    블로터닷넷
    오픈오피스를 사용하고 저장할 수 있는 형식은 ODF(Open Document Format)로, 공공 문서 국제표준형식이다. ODF 텍스트 문서인 PDT 파일은 MS 오피스나 한컴오피스에서도 열 수 있다. 오픈오피스는 4.0이후 버전부터 MS 제품과의 호환성에 신경을 써서, 오픈 ...

    April 18, 2014 05:15 AM

    April 16, 2014

    FreeCode

    OpenTBS 1.9.0

    OpenTBS is a PHP tool that helps you to make OpenOffice and MS Office documents using templates. You first design your template using OpenOffice or MS Office, and then OpenTBS merges it with data that you supply from PHP code and databases. It has facilities to manage pictures. The resulting documents are saved to file, served for download, or returned as a string. In fact, OpenTBS can merge any OpenDocument files, any OpenXML files, and any XML files compressed in a Zip archive. No extra exe file is required and it makes no temporary files, since all work is done in memory. OpenTBS is based on the TinyButStrong template engine.

    Release Notes: 8 bugfixes, 6 new features, and 3 enhancements. The new features are: commands for selecting a file, selecting headers and footers, retrieving the list of headers and footers, searching a string in slides, and a new argument $Master for counting a selecting slides. Important fixed bugs are regarding compatibility between LibreOffice and Excel.

    Screenshot

    Release Tags: major feature, minor bugs

    Tags: OpenOffice, php classes, Internet, Software Development, Dynamic Content, Zip, Template engine, Ms Office, ODF, OOXML, odt, ods, odg, odm, odp, ott, ots, otg, OTP, docx, xlsx, pptx., LibreOffice

    Licenses: LGPL

    by Skrol29 at April 16, 2014 10:38 PM

    Planet KDE

    Calligra 2.8.2 Released

    The Calligra team has released a bugfix version 2.8.2 of the Calligra Suite, and Calligra Active. This release contains a few important bug fixes to 2.8.0 and we recommend everybody to update.

    Bugfixes in This Release

    Here is an overview of the most important fixes. There are several others that are not mentioned here.

    General

    • Move Export to PDF command to the Export menu section instead of the Print section for conformance with other office suites (bug 332603).
    • Fix “Missing import filter” bug when saving if not extension is specified (even if selecting a File type is set to a format) (bug 328975).
    • Use native file dialogs on Windows.

    Kexi

    • Make Rich Text property false by default for Text Editor form widget. Rich Text often causes misbehaviour.

    Krita

    • Fix resetting the slider spin box when double clicking on it (bug 330165).
    • Ignore tablet press/release events which did not produce any sane buttons (bug 331925).
    • Added support for ‘evdev’ tablets (bugs 332239, 331572, 329641).
    • Save line smoothing options between runs of Krita. This is really needed for low-level tablets like Genius to filter the trajectory they report to us.
    • Make Krita auto-recognize axes labels of Evdev tablets. The labels are stored in a special property of the XInput device.
    • Recognize Surface Pro 2 tablets on Windows (bug 331922).
    • Fixed size of predefined images.
    • Set default gradient to alpha (bug 329008).
    • Clean up the layout of the Transform tool.
    • Hide unused settings for stroke in the Path tool (bug 331556).
    • Fixed memory leaks in brush handling.
    • Fixed memory leaks when resources fail to load.
    • Fixed memory leaks when creating strokes (bug 331592).
    • Don’t crash on creating a file layer in Krita Gemini (bug 332871).
    • Improved splash screen.
    • Fix loading plugins for Krita Gemini.
    • Save tags with special characters properly (bug 332708).
    • Fix removing of tags, don’t load or save dummy tags.
    • Add import for PSD layer groups (bug 289857).
    • Fix translation issues.
    • Fix startup of Krtita Sketch and Gemini.

    Try It Out

    About Calligra

    Calligra is part of the applications from the KDE community. See more information at the website http://www.calligra.org/.

    by Calligra News at April 16, 2014 05:17 PM

    April 12, 2014

    Google News

    LibreOffice 4.2.3 est disponible sous Linux, Windows et Max OS - GinjFo


    GinjFo

    LibreOffice 4.2.3 est disponible sous Linux, Windows et Max OS
    GinjFo
    ... automatiques, un rafraichissement automatique de la liste des imprimantes, l'importation des données d'image et non d'images liées, le bon fonctionnement de l'option d'affichage de la grille ou encore la sauvegarde de fichiers SVG dans le format ODF.

    April 12, 2014 08:47 AM

    April 10, 2014

    Google News

    Galicien empfiehlt Open Document Format - Pro-Linux


    Galicien empfiehlt Open Document Format
    Pro-Linux
    Die galicische Regierung empfiehlt der öffentlichen Hand die Verwendung des Open Document Format (ODF, ISO 26300) und hat anlässlich des diesjährigen Document Freedom Day am 26. März einen Leitfaden dazu veröffentlicht. Von Ferdinand Thommes.

    April 10, 2014 09:06 AM

    April 09, 2014

    Google News

    Windows XP va in pensione, Linux no. - 2duerighe


    Windows XP va in pensione, Linux no.
    2duerighe
    È LiMux, distribuzione Linux personalizzata per le loro esigenze, insieme al formato ODF ( Open Document Format ) e LibreOffice come suite di produttività, a funzionare su circa quindicimila pc del comune tedesco. Il risparmio economico ed i costanti ...

    April 09, 2014 06:45 PM

    Kingsoft Office Suite for Linux - MS Office Alternative Ubuntu Installation - LXer (press release)


    Kingsoft Office Suite for Linux - MS Office Alternative Ubuntu Installation
    LXer (press release)
    One of the drawbacks of this commercial suite is that it doesn't support OpenDocument Format, instead you can export your documents to PDF, or save them as MS Office formats or Kingsoft Office formats. Kingsoft Writer – The word processor The writer ...

    April 09, 2014 04:19 PM

    ODF Wikipedia Page

    ClareTheSharer: /* Standardization */ Sorry, got lost switching away from Visual Editor and edited wrong place

    Standardization: Sorry, got lost switching away from Visual Editor and edited wrong place

    ← Previous revision Revision as of 16:10, 9 April 2014
    Line 137: Line 137:
     
    *The [[ Organization for the Advancement of Structured Information Standards|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=22 November 2009}}</ref> It includes the editorial changes made to address JTC1 ballot comments. It is available in ODF, HTML and PDF formats.
     
    *The [[ Organization for the Advancement of Structured Information Standards|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=22 November 2009}}</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=31 October 2006 | 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=6 February 2007 | 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=15 February 2007 | 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>{{cite web|url=http://www.zdnet.co.uk/talkback/0,1000001161,39409700-39001068c-20093634o,00.htm|title=OOXML expert: ODF standard is broken|author=Peter Judge|publisher=ZDNet|date=2 May 2008 -- 14:47 GMT (07:47 PDT)|accessdate=10 September 2012}}</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 name="iso.org"/><ref name="http"/>
     
    *'''[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=31 October 2006 | 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=6 February 2007 | 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=15 February 2007 | 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>{{cite web|url=http://www.zdnet.co.uk/talkback/0,1000001161,39409700-39001068c-20093634o,00.htm|title=OOXML expert: ODF standard is broken|author=Peter Judge|publisher=ZDNet|date=2 May 2008 -- 14:47 GMT (07:47 PDT)|accessdate=10 September 2012}}</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 name="iso.org"/><ref name="http"/>
    *'''[http://docs.oasis-open.org/office/v1.2/OpenDocument-v1.2.pdf 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=5 October 2011 |accessdate=12 April 2012}}</ref><ref>{{citation |url=http://www.oasis-open.org/committees/office/ |title=OASIS Open Document Format for Office Applications (OpenDocument) TC |accessdate=12 April 2012}}</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. In October 2011, the OASIS ODF Technical Committee expected to "start the process of submitting ODF 1.2 to ISO/IEC JTC 1 soon".<ref name="odf12" /> In May 2012, the ISO/IEC JTC 1/SC 34/WG 6 members reported that ''after some delay, the process of preparing ODF 1.2 for submission to JTC 1 for PAS transposition is now in progress''.<ref>{{citation |url=http://www.itscj.ipsj.or.jp/sc34/open/1777.pdf |title=Minutes of teleconference meeting of ISO/IEC JTC 1/SC 34/WG 6, 2012-05-23 |format=PDF |quote=Patrick Durusau reported that, after some delay, the process of preparing ODF 1.2 for submission to JTC 1 for PAS transposition is now in progress. It is not yet know when the submission will be ready ... |accessdate=21 October 2012}}</ref> In 2013, the members of the OASIS OpenDocument technical committee have requested that OASIS submit the ODF 1.2 to ISO/IEC JTC1 for approval as a proposed International Standard under JTC's "Publicly Available Specification" (PAS) transposition procedure.<ref>{{citation |url=https://www.oasis-open.org/news/announcements/member-review-of-proposed-submission-of-odf-v1-2-to-iso-iec-jtc1 |title=Member Review of Proposed Submission of ODF v1.2 to ISO/IEC JTC1 |date=2013-08-19 |accessdate=2014-01-31}}</ref>
    +
    *'''[http://docs.oasis-open.org/office/v1.2/OpenDocument-v1.2.pdf 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=5 October 2011 |accessdate=12 April 2012}}</ref><ref>{{citation |url=http://www.oasis-open.org/committees/office/ |title=OASIS Open Document Format for Office Applications (OpenDocument) TC |accessdate=12 April 2012}}</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. In October 2011, the OASIS ODF Technical Committee expected to "start the process of submitting ODF 1.2 to ISO/IEC JTC 1 soon".<ref name="odf12" /> In May 2012, the ISO/IEC JTC 1/SC 34/WG 6 members reported that ''after some delay, the process of preparing ODF 1.2 for submission to JTC 1 for PAS transposition is now in progress''.<ref>{{citation |url=http://www.itscj.ipsj.or.jp/sc34/open/1777.pdf |title=Minutes of teleconference meeting of ISO/IEC JTC 1/SC 34/WG 6, 2012-05-23 |format=PDF |quote=Patrick Durusau reported that, after some delay, the process of preparing ODF 1.2 for submission to JTC 1 for PAS transposition is now in progress. It is not yet know when the submission will be ready ... |accessdate=21 October 2012}}</ref> In 2013, the members of the OASIS OpenDocument technical committee requested that OASIS submit the ODF 1.2 to ISO/IEC JTC1 for approval as a proposed International Standard under JTC's "Publicly Available Specification" (PAS) transposition procedure.<ref>{{citation |url=https://www.oasis-open.org/news/announcements/member-review-of-proposed-submission-of-odf-v1-2-to-iso-iec-jtc1 |title=Member Review of Proposed Submission of ODF v1.2 to ISO/IEC JTC1 |date=2013-08-19 |accessdate=2014-01-31}}</ref> As of 3 April 2014, ODF 1.2 had reached the enquiry stage of ISO's ratification process.<ref name="DIS 26300-1">{{cite web|title=ISO/IEC DIS 26300-1|url=http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=66363|publisher=ISO|accessdate=9 April 2014}}</ref>
       
     
    ===Future===
     
    ===Future===
    *'''''OpenDocument 1.3''''' (a.k.a. "ODF-Next") As of January, 2014, the current state of a possible future version of OpenDocument specification is a working draft (a preliminary unapproved sketch, outline, or version of the specification). The OASIS Advanced Document Collaboration subcommittee (created in December, 2010) is working on an update of OpenDocument change-tracking that will not only enhance the existing change-tracking feature set, but also lay the foundation for the standardization of real-time collaboration by making change tracking compatible with real-time collaboration.<ref>{{citation |url=https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office-collab |title=OpenDocument - Advanced Document Collaboration SC |accessdate=2014-01-31}}</ref><ref>{{citation |url=http://www.robweir.com/blog/2010/12/odf-tc-creates-advanced-document-collaboration-subcommittee.html |title=ODF TC Creates Advanced Document Collaboration Subcommittee |date=2010-12-05 |accessdate=2014-01-31}}</ref><ref>{{citation |url=https://fosdem.org/2014/schedule/event/real_time_compatible_odf_change_tracking/ |title=Real-time compatible ODF change-tracking |accessdate=2014-01-31}}</ref> As of 3 April 2014, ODF 1.2 had reached the enquiry stage of ISO's ratification process.<ref name="DIS 26300-1">{{cite web|title=ISO/IEC DIS 26300-1|url=http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=66363|publisher=ISO|accessdate=9 April 2014}}</ref>
    +
    *'''''OpenDocument 1.3''''' (a.k.a. "ODF-Next") As of January, 2014, the current state of a possible future version of OpenDocument specification is a working draft (a preliminary unapproved sketch, outline, or version of the specification). The OASIS Advanced Document Collaboration subcommittee (created in December, 2010) is working on an update of OpenDocument change-tracking that will not only enhance the existing change-tracking feature set, but also lay the foundation for the standardization of real-time collaboration by making change tracking compatible with real-time collaboration.<ref>{{citation |url=https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office-collab |title=OpenDocument - Advanced Document Collaboration SC |accessdate=2014-01-31}}</ref><ref>{{citation |url=http://www.robweir.com/blog/2010/12/odf-tc-creates-advanced-document-collaboration-subcommittee.html |title=ODF TC Creates Advanced Document Collaboration Subcommittee |date=2010-12-05 |accessdate=2014-01-31}}</ref><ref>{{citation |url=https://fosdem.org/2014/schedule/event/real_time_compatible_odf_change_tracking/ |title=Real-time compatible ODF change-tracking |accessdate=2014-01-31}}</ref>
       
     
    ==Application support==
     
    ==Application support==

    by ClareTheSharer at April 09, 2014 04:10 PM