Planet ODF

November 21, 2014

ODF Wikipedia Page

Dewritech: clean up, typo(s) fixed: commitee → committee using AWB

clean up, typo(s) fixed: commitee → committee using AWB

← Previous revision Revision as of 19:08, 21 November 2014
Line 131: Line 131:
 
{{Main|OpenDocument standardization}}
 
{{Main|OpenDocument standardization}}
   
The OpenDocument standard was developed by a Technical Committee (TC) under the [[ Organization for the Advancement of Structured Information Standards]] industry consortium. The ODF-TC has members from a diverse set of companies and individuals. Active TC members have voting rights. Members associated with Sun and IBM have sometimes had a large voting influence.<ref>{{cite web | url=http://www.oasis-open.org/committees/membership.php?wg_abbrev=office | title=OpenDocument TC's {{Sic|hide=y|publicly|-}}visible membership roster | accessdate=3 November 2007}}</ref> The standardization process involved the developers of many office suites or related document systems. The first official ODF-TC meeting to discuss the standard was 16 December 2002; OASIS approved OpenDocument as an OASIS Standard on 1 May 2005. OASIS submitted the ODF specification to [[ISO/IEC JTC1|ISO/IEC Joint Technical Committee 1]] (JTC1) on 16 November 2005, under Publicly Available Specification (PAS) rules.
+
The OpenDocument standard was developed by a Technical Committee (TC) under the [[Organization for the Advancement of Structured Information Standards]] industry consortium. The ODF-TC has members from a diverse set of companies and individuals. Active TC members have voting rights. Members associated with Sun and IBM have sometimes had a large voting influence.<ref>{{cite web | url=http://www.oasis-open.org/committees/membership.php?wg_abbrev=office | title=OpenDocument TC's {{Sic|hide=y|publicly|-}}visible membership roster | accessdate=3 November 2007}}</ref> The standardization process involved the developers of many office suites or related document systems. The first official ODF-TC meeting to discuss the standard was 16 December 2002; OASIS approved OpenDocument as an OASIS Standard on 1 May 2005. OASIS submitted the ODF specification to [[ISO/IEC JTC1|ISO/IEC Joint Technical Committee 1]] (JTC1) on 16 November 2005, under Publicly Available Specification (PAS) rules.
   
 
After a six-month review period, on 3 May 2006, OpenDocument unanimously passed its six-month DIS (Draft International Standard) ballot in [[JTC 1]] ([[ISO/IEC JTC1/SC34]]), with broad participation,<ref>{{cite web | url=http://www.jtc1sc34.org/repository/0728revc.htm | title=Summary of Voting on DIS ISO/IEC 26300 - Open Document Format for Office Applications (OpenDocument) v1.0 | date=13 June 2006 | accessdate=24 August 2006 | author=ISO/IEC SC34 Secretariat | work=ISO/IEC JTC 1/SC 34 Document Repository | archiveurl=http://web.archive.org/web/20061001180333/http://www.jtc1sc34.org/repository/0728revc.htm | archivedate = 1 October 2006}}</ref> after which the OpenDocument specification was "approved for release as an ISO and IEC International Standard" under the name ISO/IEC 26300:2006.<ref>{{cite web | url=http://www.iso.org/iso/en/commcentre/pressreleases/2006/Ref1004.html | title=ISO and IEC approve OpenDocument OASIS standard for data interoperability of office applications | date=8 May 2006 | accessdate=24 August 2006 | work=ISO Press Releases | publisher=[[International Organization for Standardization|ISO]]}}</ref>
 
After a six-month review period, on 3 May 2006, OpenDocument unanimously passed its six-month DIS (Draft International Standard) ballot in [[JTC 1]] ([[ISO/IEC JTC1/SC34]]), with broad participation,<ref>{{cite web | url=http://www.jtc1sc34.org/repository/0728revc.htm | title=Summary of Voting on DIS ISO/IEC 26300 - Open Document Format for Office Applications (OpenDocument) v1.0 | date=13 June 2006 | accessdate=24 August 2006 | author=ISO/IEC SC34 Secretariat | work=ISO/IEC JTC 1/SC 34 Document Repository | archiveurl=http://web.archive.org/web/20061001180333/http://www.jtc1sc34.org/repository/0728revc.htm | archivedate = 1 October 2006}}</ref> after which the OpenDocument specification was "approved for release as an ISO and IEC International Standard" under the name ISO/IEC 26300:2006.<ref>{{cite web | url=http://www.iso.org/iso/en/commcentre/pressreleases/2006/Ref1004.html | title=ISO and IEC approve OpenDocument OASIS standard for data interoperability of office applications | date=8 May 2006 | accessdate=24 August 2006 | work=ISO Press Releases | publisher=[[International Organization for Standardization|ISO]]}}</ref>
Line 138: Line 138:
   
 
Further standardization work with OpenDocument includes:
 
Further standardization work with OpenDocument includes:
*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]''' 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. It consists of three parts: Part 1: OpenDocument Schema, Part 2: Recalculated Formula (OpenFormula) Format and Part 3: Packages. Version 1.2 of the specification was approved as an OASIS Standard on 29 September 2011.<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> It has been submitted to the relevant ISO commitee under the Publicly Available Specification (PAS) procedure in March 2014.<ref>{{cite web | url=http://isotc.iso.org/livelink/livelink?func=ll&objId=16678620&objAction=Open | format=PDF | title=Minutes of ISO/IEC JTC 1/SC 34/WG 6 teleconference meeting, 2014-04-16 | date=2014-04-24 | | accessdate=2014-10-13}}</ref> As of October 2014, it has been unanimously approved as a Draft International Standard, some comments have been raised in process that need to be addressed before OpenDocument 1.2 can proceed to become an International Standard.<ref>{{cite web | url=http://isotc.iso.org/livelink/livelink?func=ll&objId=16810106&objAction=Open | format=PDF | title=ISO/IEC JTC 1/SC 34/WG 6 N 103 Minutes of teleconference meeting of ISO/IEC JTC 1/SC 34/WG 6 2014-09-24, 23:00-00:00 UTC | date=2014-09-25 | accessdate=2014-10-13}}</ref>
+
*'''[http://docs.oasis-open.org/office/v1.2/OpenDocument-v1.2.pdf OpenDocument 1.2]''' 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. It consists of three parts: Part 1: OpenDocument Schema, Part 2: Recalculated Formula (OpenFormula) Format and Part 3: Packages. Version 1.2 of the specification was approved as an OASIS Standard on 29 September 2011.<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> It has been submitted to the relevant ISO committee under the Publicly Available Specification (PAS) procedure in March 2014.<ref>{{cite web | url=http://isotc.iso.org/livelink/livelink?func=ll&objId=16678620&objAction=Open | format=PDF | title=Minutes of ISO/IEC JTC 1/SC 34/WG 6 teleconference meeting, 2014-04-16 | date=2014-04-24 | accessdate=2014-10-13}}</ref> As of October 2014, it has been unanimously approved as a Draft International Standard, some comments have been raised in process that need to be addressed before OpenDocument 1.2 can proceed to become an International Standard.<ref>{{cite web | url=http://isotc.iso.org/livelink/livelink?func=ll&objId=16810106&objAction=Open | format=PDF | title=ISO/IEC JTC 1/SC 34/WG 6 N 103 Minutes of teleconference meeting of ISO/IEC JTC 1/SC 34/WG 6 2014-09-24, 23:00-00:00 UTC | date=2014-09-25 | accessdate=2014-10-13}}</ref>
   
 
===Future===
 
===Future===
Line 218: Line 218:
 
*Several organisations, such as the [http://opendocumentfellowship.com/ OpenDocument Fellowship] and [http://opendocsociety.org/ OpenDoc Society] were founded to support and promote OpenDocument.
 
*Several organisations, such as the [http://opendocumentfellowship.com/ OpenDocument Fellowship] and [http://opendocsociety.org/ OpenDoc Society] were founded to support and promote OpenDocument.
 
<!-- *The [http://www.oidi.org OIDI.org] (Open Interoperative Document Initiative) is committed to encouraging efforts by governments at all levels, around the globe, to implement changes necessary to ensure public documents are open and interoperable and thus available to all citizens/residents without the need for specific vendor software. -->
 
<!-- *The [http://www.oidi.org OIDI.org] (Open Interoperative Document Initiative) is committed to encouraging efforts by governments at all levels, around the globe, to implement changes necessary to ensure public documents are open and interoperable and thus available to all citizens/residents without the need for specific vendor software. -->
*The UK government has adopted ODF as the standard for all documents in the UK civil service <ref>{{cite web | url=https://www.gov.uk/government/news/open-document-formats-selected-to-meet-user-needs|title=Open document formats selected to meet user needs}} </ref>
+
*The UK government has adopted ODF as the standard for all documents in the UK civil service <ref>{{cite web | url=https://www.gov.uk/government/news/open-document-formats-selected-to-meet-user-needs|title=Open document formats selected to meet user needs}}</ref>
 
*The [[Wikimedia Foundation]] supports ODF export from [[MediaWiki]], which powers [[Wikipedia]] and a number of other Internet [[wiki]]-based sites.<ref>{{cite web | url= http://wikimediafoundation.org/wiki/Wikis_Go_Printable | title= Wikis Go Printable | work= [[Wikimedia Foundation]] | date= 13 December 2007 | accessdate= 31 December 2007}}</ref>
 
*The [[Wikimedia Foundation]] supports ODF export from [[MediaWiki]], which powers [[Wikipedia]] and a number of other Internet [[wiki]]-based sites.<ref>{{cite web | url= http://wikimediafoundation.org/wiki/Wikis_Go_Printable | title= Wikis Go Printable | work= [[Wikimedia Foundation]] | date= 13 December 2007 | accessdate= 31 December 2007}}</ref>
   

by Dewritech at November 21, 2014 07:08 PM

Janvlug: /* Worldwide adoption */ Norway is not a EU member

Worldwide adoption: Norway is not a EU member

← Previous revision Revision as of 14:25, 21 November 2014
Line 265: Line 265:
 
** [[Italy]]
 
** [[Italy]]
 
** [[Netherlands]]<ref>{{cite web |title=ODF 1.2 on Dutch "apply or explain" list |url=https://lijsten.forumstandaardisatie.nl/open-standaard/odf12}}</ref>
 
** [[Netherlands]]<ref>{{cite web |title=ODF 1.2 on Dutch "apply or explain" list |url=https://lijsten.forumstandaardisatie.nl/open-standaard/odf12}}</ref>
** [[Norway]]<ref name="NorwayDocumentStandard">{{cite web |title=New obligatory IT standards for the state sector adopted |url=http://www.regjeringen.no/en/dep/fad/press-centre/press-releases/2009/new-obligatory-it-standards-for-the-stat.html?id=570650 |accessdate=19 December 2012}}</ref>
 
 
** [[Poland]]
 
** [[Poland]]
 
** [[Portugal]]<ref>{{cite web |url=http://www.esop.pt/portugal-publishes-open-standards-catalogodf-pdf-and-several-other-standards-are-mandatory/ |title=ESOP » Portugal publishes open standards catalog. ODF, PDF and several other standards are mandatory |publisher=Esop.pt |date= |accessdate=2013-05-01}}</ref>
 
** [[Portugal]]<ref>{{cite web |url=http://www.esop.pt/portugal-publishes-open-standards-catalogodf-pdf-and-several-other-standards-are-mandatory/ |title=ESOP » Portugal publishes open standards catalog. ODF, PDF and several other standards are mandatory |publisher=Esop.pt |date= |accessdate=2013-05-01}}</ref>
Line 273: Line 272:
 
{{endflatlist}}
 
{{endflatlist}}
 
{{startflatlist}}
 
{{startflatlist}}
  +
* [[Norway]]<ref name="NorwayDocumentStandard">{{cite web |title=New obligatory IT standards for the state sector adopted |url=http://www.regjeringen.no/en/dep/fad/press-centre/press-releases/2009/new-obligatory-it-standards-for-the-stat.html?id=570650 |accessdate=19 December 2012}}</ref>
 
* Russia
 
* Russia
 
* [[Serbia]]
 
* [[Serbia]]

by Janvlug at November 21, 2014 02:25 PM

Janvlug: /* Worldwide adoption */ Added attribute to NATO referece.

Worldwide adoption: Added attribute to NATO referece.

← Previous revision Revision as of 14:17, 21 November 2014
Line 237: Line 237:
 
!style="padding:0.25em 1.0em;"| International
 
!style="padding:0.25em 1.0em;"| International
 
|colspan="2" class="hlist" style="vertical-align:top;padding:0.25em 0.5em;"|
 
|colspan="2" class="hlist" style="vertical-align:top;padding:0.25em 0.5em;"|
* [[NATO]]<ref>https://nhqc3s.hq.nato.int/Apps/Architecture/NISP2/standard.aspx?vndb=standards&vsbn=y&refid=iso-iec-26300&sbbs=y</ref>
+
* [[NATO]]<ref>{{cite web |title=NATO Interoperability Standards and Profiles |url=https://nhqc3s.hq.nato.int/Apps/Architecture/NISP2/standard.aspx?vndb=standards&vsbn=y&refid=iso-iec-26300&sbbs=y |accessdate=21 November 2014}}</ref>
 
|-
 
|-
   

by Janvlug at November 21, 2014 02:17 PM

Janvlug: /* Worldwide adoption */ Added reference to NATO site stating ODF as mandatory standard

Worldwide adoption: Added reference to NATO site stating ODF as mandatory standard

← Previous revision Revision as of 14:10, 21 November 2014
Line 237: Line 237:
 
!style="padding:0.25em 1.0em;"| International
 
!style="padding:0.25em 1.0em;"| International
 
|colspan="2" class="hlist" style="vertical-align:top;padding:0.25em 0.5em;"|
 
|colspan="2" class="hlist" style="vertical-align:top;padding:0.25em 0.5em;"|
* [[NATO]]
+
* [[NATO]]<ref>https://nhqc3s.hq.nato.int/Apps/Architecture/NISP2/standard.aspx?vndb=standards&vsbn=y&refid=iso-iec-26300&sbbs=y</ref>
 
|-
 
|-
   

by Janvlug at November 21, 2014 02:10 PM

November 20, 2014

Charles H. Schulz

Standards and Weapons

I have been writing a lot about the benefits of standards -especially open standards- for economic growth and citizens’ empowerement. Today however, I would like to explore, or at least highlight  a more obscure side of standards.

Standards can be used as weapons; by weapons I mean tools of influence, economic and technological domination from one country, one company over others. Standards are not just developed by means of sitting around a table with other parties and deciding how it will be developed. Sometimes, a party will push forward the base of a standard, and by sharing this base, will ultimately influence the whole industry or ecosystem through the outcome of standardization: the existence of the standard and its adoption. Other times, the very fact that a standard is being developed and pushed on the market is a threat to existing other standards. In a way, this is what could have happened with ODF, only in this case the Microsoft Office binary file formats were never standards in the first place. But then the very fact that OOXML was ever submitted to the ISO created the second standard that partly broke the momentum of ODF adoption.

 Other examples can be seen in other industries as well. Is there anything that can be done? Well, for one thing, it is important to realize that standards can become a rather dynamic affair. A standard with an expected power struggle, that is a standard that is already a bone of contention between two companies or two countries can be turned around into a struggle of different nature between different opponents.

Another important consideration is that a standard should always be contemplated not just in terms of what problem it claims to be solving but through a variety of parameters. Chiefly among them, the identity of its authors, the intellectual property rights and regime applicable to its specification, the state of the standard implementations and the players providing them, the existing standards in the same field, etc.

My humble experience in the field of digital standards makes me think that no standard is ever innocent, not in itself but by the intent of its authors or implementors. Even a nice and deeply useful standard such as ODF is a big stone thrown in the backyard of Microsoft. At this point you may be wondering if this post is essentially a change in position from what I’ve written here thoughout all these years (after all, this blog is called “Moved by Freedom, Powered by Standards”). It actually isn’t in any way. Standards are tools; they are opportunities for collaboration, economic and technical improvement. But they are limited in regulating the good or bad will of their stakeholders, and truth be told, I don’t think any process or tools could ever do that ex ante. The development rules, the IPR, the transparency of the process can be very effective in regulating the defects as well as whatever issues specific to standard itself may appear. They can even help fostering an effective ecosystem around the standard. But once you step up to a more strategic level, you need to go beyond the standards’ internal and external qualities (the specification itself, its IPR, its development process, etc.) . You need to understand who is doing what in the industry, who are the contenders and established players, the technological and legal disruptions, and even the political intent driving to the adoption of a standard or discouraging it. You need to understand why there’s even a standard in the first place.

With what has been previously called “true open standards”, things tend to improve insofar as their true openness guarantee the absence of vendor lock-in. Yet true open standards are assessed dynamically, never on the basis of predefined rules. As an example, one may demand that the IPR mode of a standard be only Royalty-Free. If there are two Royalty-Free competing standards, both satisfy this requirement, yet perhaps one of these two is ultimately controlled by a vendor, while the other one has a genuine inclusive development process. The history of ODF and OOXML is an interesting case in regard of using pre-defined criteria that may lead to a partial assessment of a standard.

All in all, standards are tools, and tools can often be used as weapons. It is never about the tool itself, but about the hand guiding it. Anybody can use a hammer, even me and my two left hands. But you can choose to hammer nails to suspend picture frames on a wall, or you can choose to use the hammer to throw it in the face of someone. The hammer is not responsible of your choice, for you only have had an intent guiding the hammer. Standards are no different; they can be both tools of liberation and economic welfare, or they can be used as competition crushers and weapons of economical warfare. In any case, judge by the hand first and the tool second.

by Charles at November 20, 2014 11:30 AM

November 19, 2014

Apache OpenOffice Blog

Europe Commission approves Tradeshift data format for goverment purchasing - Bobsguide (press release)


Europe Commission approves Tradeshift data format for goverment purchasing
Bobsguide (press release)
OASIS is the same organization that created ODF, the Open Document Format (ISO/IEC 26300), a widely used International Standard for word processing. As a result of the EC decision, Tradeshift's users can expect easy data integration with regulatory and ...

and more »

November 19, 2014 11:03 AM

November 18, 2014

Apache OpenOffice Blog

EC approves Tradeshift data format for government purchasing - Finextra


EC approves Tradeshift data format for government purchasing
Finextra
OASIS is the same organization that created ODF, the Open Document Format (ISO/IEC 26300), a widely used International Standard for word processing. As a result of the EC decision, Tradeshift's users can expect easy data integration with regulatory and ...

and more »

November 18, 2014 05:02 PM

EC approves Tradeshift data format for government purchasing - Finextra


EC approves Tradeshift data format for government purchasing
Finextra
OASIS is the same organization that created ODF, the Open Document Format (ISO/IEC 26300), a widely used International Standard for word processing. As a result of the EC decision, Tradeshift's users can expect easy data integration with regulatory and ...

and more »

November 18, 2014 05:01 PM

UK Government

Statistical data set: ENV18 - Local authority collected waste: annual results tables

Updated: New datasets published.

These datasets contain the annual results for local authority collected waste in England including:

  • England and the regions data downloads for April 2000 to March 2014
  • local council data downloads from April 2005 to March 2014
  • household recycling by material type April 1996 to March 2010

Local authority collected waste from households from January 2010 to March 2014 - England data.

This file is in an OpenDocument format

This file may not be suitable for users of assistive technology. Request a different format.

If you use assistive technology and need a version of this document in a more accessible format, please email defra.helpline@defra.gsi.gov.uk. Please tell us what format you need. It will help us if you say what assistive technology you use.

Local authority collected waste generation from April 2000 to March 2014 (England and regions) and local authority data April 2013 to March 2014

This file is in an OpenDocument format

This file may not be suitable for users of assistive technology. Request a different format.

If you use assistive technology and need a version of this document in a more accessible format, please email defra.helpline@defra.gsi.gov.uk. Please tell us what format you need. It will help us if you say what assistive technology you use.

Local authority collected waste statistics - Local authority data, England: April 2012 to March 2013

This file may not be suitable for users of assistive technology. Request a different format.

If you use assistive technology and need a version of this document in a more accessible format, please email defra.helpline@defra.gsi.gov.uk. Please tell us what format you need. It will help us if you say what assistive technology you use.

Local authority collected and household waste statistics 2011 to 2012

This file may not be suitable for users of assistive technology. Request a different format.

If you use assistive technology and need a version of this document in a more accessible format, please email defra.helpline@defra.gsi.gov.uk. Please tell us what format you need. It will help us if you say what assistive technology you use.

Local authority collected and household waste statistics 2010 to 2011

This file may not be suitable for users of assistive technology. Request a different format.

If you use assistive technology and need a version of this document in a more accessible format, please email defra.helpline@defra.gsi.gov.uk. Please tell us what format you need. It will help us if you say what assistive technology you use.

Local authority collected and household waste statistics 2009 to 2010

This file may not be suitable for users of assistive technology. Request a different format.

If you use assistive technology and need a version of this document in a more accessible format, please email defra.helpline@defra.gsi.gov.uk. Please tell us what format you need. It will help us if you say what assistive technology you use.

Local authority collected and household waste statistics 2008 to 2009

This file may not be suitable for users of assistive technology. Request a different format.

If you use assistive technology and need a version of this document in a more accessible format, please email defra.helpline@defra.gsi.gov.uk. Please tell us what format you need. It will help us if you say what assistive technology you use.

Local authority collected and household waste statistics 2007 to 2008

This file may not be suitable for users of assistive technology. Request a different format.

If you use assistive technology and need a version of this document in a more accessible format, please email defra.helpline@defra.gsi.gov.uk. Please tell us what format you need. It will help us if you say what assistive technology you use.

Local authority collected and household waste statistics 2006 to 2007

This file may not be suitable for users of assistive technology. Request a different format.

If you use assistive technology and need a version of this document in a more accessible format, please email defra.helpline@defra.gsi.gov.uk. Please tell us what format you need. It will help us if you say what assistive technology you use.

Local authority collected and household waste statistics 2005 to 2006

This file may not be suitable for users of assistive technology. Request a different format.

If you use assistive technology and need a version of this document in a more accessible format, please email defra.helpline@defra.gsi.gov.uk. Please tell us what format you need. It will help us if you say what assistive technology you use.

England carbon metric report - Summary

This file may not be suitable for users of assistive technology. Request a different format.

If you use assistive technology and need a version of this document in a more accessible format, please email defra.helpline@defra.gsi.gov.uk. Please tell us what format you need. It will help us if you say what assistive technology you use.

Household recycling by material and region, England: April 1996 to March 2010

This file may not be suitable for users of assistive technology. Request a different format.

If you use assistive technology and need a version of this document in a more accessible format, please email defra.helpline@defra.gsi.gov.uk. Please tell us what format you need. It will help us if you say what assistive technology you use.

November 18, 2014 09:30 AM

Statistical data set: ENV19 - Local authority collected waste: quarterly tables

Updated: Final quarter figures incorporated.

This data set covers the provisional quarterly estimates of local authority collected waste generation and management for England and the regions.

Quarterly local authority collected waste statistics from 2010 incorporation January to March 2014

This file is in an OpenDocument format

This file may not be suitable for users of assistive technology. Request a different format.

If you use assistive technology and need a version of this document in a more accessible format, please email defra.helpline@defra.gsi.gov.uk. Please tell us what format you need. It will help us if you say what assistive technology you use.

November 18, 2014 09:30 AM

November 17, 2014

Apache OpenOffice Blog

£17 million project for 140 new homes in Salford's Ordsall - bdaily


bdaily

£17 million project for 140 new homes in Salford's Ordsall
bdaily
Launched in 2006 the Ordsall Development Framework (ODF) was created to bring about transformational change to historically one of the most deprived areas in the UK. Under the partnership with Salford City Council, LPC Living, which is owned by the ...

and more »

November 17, 2014 02:36 PM

November 14, 2014

UK Government

Corporate information: Research at HMRC

Research reports

Our research and analysis publications can be found at HMRC Publications: Research and analysis.

Working papers series

The Working Papers are occasional papers on analytical issues, produced by or on behalf of HMRC.

Contact the research team

For enquiries on the HMRC research and analysis programme, contact:

Brian O'Callaghan
HMRC Knowledge Analysis and Intelligence Directorate
4th Floor, South Spur
Bush House SW Wing
Strand
London
WC2B 4RD

Email: Brian O’Callaghan

For information on Customer Understanding Research:

Uma Kushalappa
HMRC Customer Insight & Knowledge Team
3E/03
100 Parliament St
London
SW1A 2BQ

Email: Uma Kushalappa

Research activities funded by HMRC

The documents below set out current research activities funded by HMRC’s programme of research:

The HMRC Datalab

The HMRC Datalab allows approved academics to access de-identified HMRC data in a secure environment.

The aim of the Datalab is to help researchers to produce high quality research that benefits both HMRC and the wider academic community.

Data protection policies and standards

The Datalab follows HMRC’s strict data protection policies. There are restrictions on working practices to safeguard taxpayer confidentiality. To become an ‘approved academic researcher’, institutions have to submit a proposal and complete a short training course.

The Datalab is governed by the Commissioners for Revenue and Customs Act (CRCA) 2005, which dictates who HMRC can allow to access their data and for what reasons.

Research proposals for the Datalab must serve one of HMRC’s functions under the CRCA 2005. See IDG47000 - Disclosure for the purposes of HMRC’s functions or further information.

Applying to use the HMRC Datalab

To apply to use the HMRC Datalab:

  1. download and complete the Datalab project proposal form: HMRC Datalab Project Proposal Application (ODT, 24.7KB)

  2. email the form to: HMRC Datalab

It’s important that your proposal shows how your research will be:

  • useful for HMRC
  • improved using HMRC data rather than other available sources

The Datalab Team will then advise you on your project, and may request more detailed information.

Proposals are then evaluated against these criteria:

  • contribution to HMRC functions
  • long-term benefit to HMRC
  • research design and likely impact of the research
  • feasibility of the research

HMRC is more likely to support projects that are relevant to contemporary research questions.

All research in the HMRC Datalab must be independent, with the results intended for publication.

It may be useful to see this list of approved research proposals to help you with your submission:

HMRC research proposals approved to date

This file may not be suitable for users of assistive technology. Request a different format.

If you use assistive technology and need a version of this document in a more accessible format, please email onlineservicessyndicationteam@hmrc.gsi.gov.uk. Please tell us what format you need. It will help us if you say what assistive technology you use.

These are topics currently of interest to HMRC which we would like to see explored in the HMRC Datalab:

  • efficiency improvements within HMRC
  • compliance
  • data issues
  • tax policy

Application submission deadlines

Applications are assessed on a quarterly basis:

  • 15 December 2014, to be discussed on 16 January 2015
  • 13 March 2015, to be discussed on 10 April 2015
  • 13 June 2015, to be discussed on 10 July 2015

Available datasets

These are the datasets currently available in the HMRC Datalab.

Other HMRC datasets

You can submit a proposal requesting the use of datasets not listed above, if the information you need is currently not available in the Datalab. Please consult our data catalogue for further information on the data that HMRC holds:

HMRC Data Catalogue

Using and matching your own data

You will need to describe the data you would like to bring and the HMRC Datalab Team will consider each dataset on a case by case basis.

Key identifiers have been removed from the HMRC Datalab datasets as part of the de-identification process so matching will have to be undertaken by HMRC.

Contact the HMRC Datalab

If you have any questions about the Datalab please contact us.

Bush House (South West Wing)
Strand
London
WC2B 4RD

Email: HMRC Datalab

November 14, 2014 03:36 PM

Guidance: Enterprise Management Incentives (EMI) Notification template

On this page you’ll find the attachment you need to tell HMRC about EMI options granted during the tax year, along with guidance notes to help you fill out the worksheet.

Get the right software

You’ll need software that can open Open Document Format (ODF) files, such as a recent version of Microsoft Excel or the free LibreOffice. Download the latest version of LibreOffice.

November 14, 2014 02:51 PM

Apache OpenOffice Blog

"Oh-oh-XML" - Digitale Zeitbombe in deutschen Amtsstuben - Netzpolitik.org


"Oh-oh-XML" - Digitale Zeitbombe in deutschen Amtsstuben
Netzpolitik.org
ODF-78c8e0a8f69c7b2c Dieser Beitrag ist eine Ergänzung zu Matthias' Zusammenfassung der LiMux-Debatte in der Stadt München, die mit dem Aufruf endet, dass Bund und Länder Offene Standards unterstützen müssen. In der Tat hinkt die deutsche ...

and more »

November 14, 2014 07:04 AM

November 13, 2014

Apache OpenOffice Blog

Stada kann EinbuÃ?en in Russland auffangen - AD HOC NEWS


Stada kann EinbuÃ?en in Russland auffangen
AD HOC NEWS
News: Eurpäische Kommission empfiehlt Open Document Format Alle Institutionen der EU sollen in der Lage sein, das Open Document Format (ODF) intern und im Dialog mit den Bürgern und anderen Institutionen einzusetzen. Das erklärte jetzt MaroÅ¡ Å ...

and more »

November 13, 2014 03:41 PM

November 10, 2014

Apache OpenOffice Blog

Microsoft-Chef Satya Nadella spricht vor Studenten der TU-Berlin - WinFuture


WinFuture

Microsoft-Chef Satya Nadella spricht vor Studenten der TU-Berlin
WinFuture
Bis zur 2013er-Version konnte man mit MS Office nämlich nicht ein einziges natives Dateiformat eines anderen Office-Paketes am Markt einlesen (Und auch jetzt kann MS Office lediglich das ODF-Format lesen, während OpenOffice bei mir sogar alte ...

and more »

November 10, 2014 04:43 PM

Xerox declares the end of paper (again) - FierceEnterpriseCommunications


Xerox declares the end of paper (again)
FierceEnterpriseCommunications
From what the company's videos manage to show, it's a system for storing and distributing documents in a new format--not ODF, not PDF and not OOXML. The purpose of this, as Xerox describes it, is to enable a common data store of all documents that ...

and more »

November 10, 2014 01:34 PM

November 07, 2014

Planet KDE

Where is KDE 5 and when can I use it?

The vast majority of users, when talking about "using KDE", are talking about the desktop. Plasma, that is. So when you ask "when will KDE 5 be ready?", your answer will be that our brand new desktop is already at version 5.1 and making swift progress! Stability is quite good, but there's work to do in the feature area. Distributions don't ship it as default yet.

If you ask for 'official packages from my distribution', most distributions, including Fedora, openSUSE and Kubuntu, have had packages since 5.0. The just-released openSUSE 13.2 ships with Plasma 4.11 (the latest and last version in the stable 4 series) as default desktop but has Plasma 5.1 as option, next to GNOME Shell, XFCE and everything else. Kubuntu similarly released with Plasma 4.11 and a tech preview with Plasma 5.1 simultaneously. Both have KDE Applications 4.14.x, as there is no release of the Frameworks based apps yet. openSUSE offers a repo with newer apps but they're unstable as popcorn in an oven.

"when will this be default in distributions?" might be your next question. A good estimate is that by Plasma 5.4, to be released in the 2nd quarter next year, distributions will move over to the new series. Kubuntu has already announced they will ship Plasma as default desktop in 15.04 and I expect others with a similar or later release date to follow suit.

How ready is it?

While progress has been very fast and the team has been focusing on the end user experience, there still are glitches and missing features. Many of the supporting apps and widgets are still being ported or optimized for the new environment. Klipper has seen awesome work by Martin Graßlin with help from the new KDE design team, work on KMix is in progress and things like HiDPI support aren't entirely fleshed out yet either.

I'd recommend moving over your work desktop or laptop for 5.4. Until then, help test and improve it to make sure it is ready for you! Use the experimental packages for openSUSE or Kubuntu for testing, or build your own. This is a good time to get involved as there are plenty of relatively simple yet very impact-full tasks waiting for volunteers!

What is KDE 5 and why do you call it 'Plasma'?

To talk about something you have to define it, and I realize that that is a a bit more complicated than it used to be. In July I blogged about the disappearance of the 'software compilation'. That term was introduced after we re-branded KDE to no longer be the product we made, but the people who made it.

To understand the relation, compare KDE to another organization which creates (among other things) software: Microsoft. Like KDE, they create products and technologies like Office (KDE makes Calligra), Windows (KDE develops Plasma), .NET (KDE releases Frameworks), C# (KDE uses C++). Nobody confuses Microsoft Office with Microsoft 8.1 so this should be easy enough, I hope!

Why the change?

We used to release our desktop, applications and libraries at once, the KDE releases. Unfortunately that created two problems:
  • It confused many users about what was needed to run KDE applications. Could you only run Amarok in KDE? Did you have to install all of KDE to use Krita? For advanced users, these are simple to answer, but on user forums they kept coming up and you'd hear users at conferences tell you they never tried Krita because they did not like KDE (meaning the desktop).
  • The KDE 4.0 release had been a disaster in part because we released all its components at the same time, while not all were of the same quality. Many of the applications had been ported almost a year before and were quite mature, while especially Plasma, the desktop, had undergone a serious rewrite and simply wasn't ready.

To deal with these two issues, we changed the meaning of "KDE" to be the people in our community and started talking about the separate products as what we released. That was still all released at once, so most users continued to talk about KDE 4.x

Today things are different. While the libraries (KDE Frameworks) are currently at version 5.4 (released monthly), Plasma is at 5.2 (released every 3 months) and the KDE Applications are at 4.14. The latter will release soon with a date-based name, as it is build on a mix of the 4.x series and the 5.x series of our libraries so a common version number just doesn't work.

Here's a view of how it all fits together:



What goes with what?

You might ask next: "what version of what goes with what?" - a fair question. Luckily, the distributions will mostly deal with these dependency questions for you!

Still, if you want, here is an overview of how the relations currently are.

Frameworks releases monthly, combining bug fixes and (small) features. You can use the latest, stability is very important for the Frameworks team and it should be perfectly safe. Of course, this introduces a bit of an issue for distributions, which often don't want to mix feature- and bugfix releases. I'm not sure how they will deal with this. The backwards compatibility of Frameworks should allow updating them like bug fixes, but we'll have to see who does what.

Plasma releases every 3 months and usually depends on the latest or latest -1 version of Frameworks at release time. It will work just fine with versions newer than what it depends on as minimum.

Applications is still in the 4.x series, but many applications are already ported to Frameworks and the first release (14.12) will come next month. The numbering will be year.month, so if the next release comes 4 months later, it will be 15.4. They, too, will probably require latest or latest -1 version of Frameworks when released.

As of today, most distributions stick with the latest version of Plasma in the 4.x series (that is 4.11) and the latest version of KDELibs in the 4.x series, 4.14 (technically 4.9 but the numbers have been kept in line with Applications to keep things simpler).

Bringing it all together:
if you want a stable system, stay on Plasma 4.11 with KDELibs and Applications 4.14 for now. If you want to try out the new tech, try Plasma 5.2, which depends on Frameworks 5.3. With Applications 4.14 - no newer release is out yet, but openSUSE offers regular git checkouts and they have been working quite well for me personally. Find instructions here.


Note:
The 4.x series has already been split up. If you run "KDE 4.14", you don't. The last official Platform release is 4.9 and Plasma is at 4.11. Only the applications have continued to release, and speeding up their release cycle, while the Platform has seen increasing version numbers to keep packaging easy.

by Jos Poortvliet at November 07, 2014 08:01 PM

Charles H. Schulz

The Document Foundation sets precedents & paves new opportunities for Free Software

These past weeks have marked a significant twist in the way the Document Foundation is supporting the LibreOffice project and in general, the Free and Open Source Software world. Three distinct pieces of news should indeed be put together in order to shed light on the way the Document Foundation is changing the way Free Software projects can work in order to grow and gain traction. In chronological order, here are the three announcements you should pay attention to:
– The Document Foundation opens a tender to develop a full viewer (and limited editor) for Android
CloudOn, a member of the Advisory Board of the Document Foundation and a very active contributor of code, releases its new, full touch-based document viewer and editor for the iPad, entirely based on LibreOffice.
– The Document Foundation extends its certification programme to migration and training professionals.

Put together, a new story is emerging. Part of it was expected since the beginning of the LibreOffice project, while other parts came up unexpectedly, yet welcome. Let me explain. The other day I was writing about the roles of Free and Open Source Foundations. The funny thing about that is that while some foundations have roles that are easy to understand, several others operate in ways that may not make immediate sense to all. It seems that the Document Foundation falls in this latter category.

The Document Foundation role is to support and grow the LibreOffice & Document Liberation project and promote Free Software and Open Standards. You will notice in this statement two key points; first, it is not directly the role of the Document Foundation to develop the LibreOffice code: the community of volunteers is in charge of that and second, the actual role of the foundation is actually to protect and cater to the community’s needs and logistics.

At this point, it should be clear that at least in the case of the Document Foundation, we don’t hire developers to work on LibreOffice. But we feel there’s a difference between being a non profit entity distributing t-shirts and an entity actually supporting and growing the project. As such, we have overcome the lack of skills and time to develop an Android client by dedicating resources to this development, enabling talented developers to work on this project during a fixed period of time and funded by the foundation. Clearly, if such a development had been so easy we would already have an Android version.

The second case is a bit different, but highlights that the licensing choices of the LibreOffice project do not make it some sort of project for hobbyists. Here, we have a dynamic startup investing in the codebase and in the project in order to bet its own business on LibreOffice. The result is a visually stunning, touch based document viewer and editor for the iPad; it is also the only client able to read and edit documents in OOXML, ODF and several other formats on this device. Is it proprietary? I’m afraid it is. But the important lesson here is on two levels: in order to create such a product, CloudOn had to invest heavily in the development of LibreOffice (i.e, make actual, sizable contributions to the LibreOffice codebase) and, despite everything we have heard in the past, our licensing scheme is flexible enough to accomodate many different kind of scenarios without ripping off the actual project from its resources and code.

Last but not least, the certification for migration and training professionals is an important announcement: by assessing a reasonable level of competence and knowledge on LibreOffice, the certification aims at turning the market into a readable and transparent set of service offerings the customers can choose from while benefiting from a real stamp of minimum quality to be expected.

The conclusion at this stage I take from these three announcements is that the Document Foundation moves into new territories that will ultimately help LibreOffice and the FOSS world in general. By setting these precedents, the Document Foundation finds ways to strengthen the business ecosystem and invest resources into much needed strategic initiatives. This is what an independent foundation can do for the community it stems from and it is a powerful, yet at times intriguing model that prompts a new thinking on Free and Open Source Software projects.

by Charles at November 07, 2014 04:39 PM

November 06, 2014

Apache OpenOffice Blog

Government open standards - the curious case of Microsoft and the minister - ComputerWeekly.com


ComputerWeekly.com

Government open standards - the curious case of Microsoft and the minister
ComputerWeekly.com
Most people would see little to argue with in the choice of a standard called the Open Document Format (ODF). It is widely used and respected, and is supported by the most popular word processor and spreadsheet products in the world – Microsoft's Word ...

November 06, 2014 11:04 AM

November 05, 2014

Apache OpenOffice Blog

Rusland verplicht open source - NU.nl


NU.nl

Rusland verplicht open source
NU.nl
Dit kan dus zowel de ODF (Open Document Format) als OOXML (Office OpenXML) zijn. Laatstgenoemde is oorspronkelijk door Office-producent Microsoft ontwikkeld en beide zijn officiële open standaarden. In de loop van komend jaar moeten de diverse ...

and more »

November 05, 2014 04:23 PM

November 04, 2014

Apache OpenOffice Blog

Departments lack common targets for implementing open-document standards - ComputerWeekly.com


ComputerWeekly.com

Departments lack common targets for implementing open-document standards
ComputerWeekly.com
However, ODF won't be implemented until 28 February 2018, with plans to be reviewed in 2016 to assess if it can be completed sooner. A spokesperson for the Treasury told Computer Weekly while the department can generate documents in the ODF format ...
DCLG to address open source obstaclesCivil Service World

all 2 news articles »

November 04, 2014 05:12 PM

[열린마당]한글 '워드' 안깔린 PC서도 민원 신청 OK - 한라일보


[열린마당]한글 '워드' 안깔린 PC서도 민원 신청 OK
한라일보
주민들이 행정기관 민원실에 많이 제출하는 민원 신청서와 공직에 지원하는 민간 전문가가 작성하는 개방형직위 응시원서에 대해 한글문서와 함께 '개방형 문서 서식(open document format, ODF)' 파일도 제공하고 있다. 방문민원 건수가 가장 많은 전입신고서(1088 ...

November 04, 2014 01:01 PM

DCLG to address open source obstacles - Civil Service World


Civil Service World

DCLG to address open source obstacles
Civil Service World
Also, the current version of Microsoft Office only supports the ODF 1.1 standard, and not all applications support the use of ODF formatted documents. The use of ODF needs to be integrated into business applications, the department added. A third phase ...
Departments lack common targets for implementing open-document standardsComputerWeekly.com

all 2 news articles »

November 04, 2014 12:26 PM

November 03, 2014

Apache Foundation

Call for talks: Open Document Editors Devroom at FOSDEM 15

FOSDEM 15 will be held at the ULB Campus Solbosch on Saturday, January 31, and Sunday, February 1st, 2015.

Open document editors are coming again to FOSDEM with a shared devroom which gives every project in this area a chance to present ODF related developments and innovations. The devroom is jointly organized by Apache OpenOffice and LibreOffice.

We invite submission of talks for the Open Document Editors devroom, to be held on Saturday, January 31, from 10AM to 6PM.

Length of talks should be limited to 20 minutes, as we would like to have questions after each presentation, and to fit as many presenters as possible in the schedule. Exceptions must be explicitly requested and justified.

Technical talks (code, extensions, localization, QA, tools and adoption related cases) about open document editors or the ODF document format are welcome.

Submissions must be done by the speakers using the Pentabarf system:
https://penta.fosdem.org/submission/FOSDEM15

While filing your proposal, please provide the title of your talk, a short abstract (one or two paragraphs), some information about yourself (name, bio and photo, but please do remember that your profile might be already stored at Pentabarf) and specify what topic (Apache OpenOffice, LibreOffice, other ODF editors, ODF in general...) your talk is about.

You do not need to create a new account if you already have one. If the password has been lost, you can easily recover it.

The deadline is Sunday, December 14, 2014. Accepted speakers will be notified by December 28, 2014.

You can send any questions to the devroom mailing list:
open-document-devroom-AT-lists.fosdem-DOT-org

by pescetti at November 03, 2014 10:23 PM

October 28, 2014

Apache OpenOffice Blog

Rivoluzion​e informatic​a in Municipio - Legnanonews


Legnanonews

Rivoluzion​e informatic​a in Municipio
Legnanonews
Da oggi, nello scambio di documenti all'interno del Municipio con soggetti esterni, nell'invio di mail e nella pubblicazione di documenti sul portale comunale, verrà adottato il formato aperto ODF (Open Document Format). Un'altra importante novità è l ...

October 28, 2014 05:57 PM

October 27, 2014

Apache OpenOffice Blog

大里仁愛90天汰換辦公室軟體導入開源軟體省百萬授權費 - iThome Online


大里仁愛90天汰換辦公室軟體導入開源軟體省百萬授權費
iThome Online
檔案格式轉換上,OpenOffice預設的文件交換格式為ISO標準的開放文件格式(OpenDocument FormatODF),也可以轉成微軟Office及其他常見的檔案格式。 其他同樣導入OpenOffice的組織還有聯合報、臺中榮總醫院等,不過相較之下,廖啓志的作法更為果斷,整個 ...

October 27, 2014 02:28 AM

October 24, 2014

www.opendocsociety.org

Tenth ODF plugfest in London

Earlier this year the UK Cabinet Office officially adopted the Open Document Format as the office format of choice.The international document file format standard is expected to be used across all government bodies for sharing or collaborating on government documents. This will help create a level playing field for suppliers of all sizes, increase productivity and competitiveness and  make large cumulative savings for citizens, businesses and taxpayers.

We are excited to be able to announce that the UK Cabinet Office will be hosting the tenth ODF Plugfest on December 8th and 9th 2014 in London. The ODF plugfests are an ongoing series of vendor-neutral events, bringing together implementers and stakeholders of the standard.he goal is to achieve maximum interoperability by running scenario-based tests in a hands-on manner and discuss new and proposed features of the Open Document Format specification.

Lead architects from commercial and open source products, members of the OASIS ODF TC's and technical experts from national and regional governments will be present. Plugfests have been held in a number of countries across Europe since 2009, when the first ODF plugfest was launched in The Hague by the Netherlands Minister of Foreign Trade at the time, Frank Heemskerk.
10th ODF plugfest logo

October 24, 2014 11:14 AM

Google News

Il Comune di Legnano viaggia tutto in OpenOffice - AsseSempione.info


Il Comune di Legnano viaggia tutto in OpenOffice
AsseSempione.info
Da oggi, nello scambio di documenti all'interno del Municipio con soggetti esterni, nell'invio di mail e nella pubblicazione di documenti sul portale comunale, verrà adottato il formato aperto ODF (Open Document Format). Un'altra importante novità è l ...

October 24, 2014 09:11 AM

October 23, 2014

Google News

[WIS 2014 영상] 인프라웨어, 'PC용 폴라리스 오피스' 선보여 - Aving


[WIS 2014 영상] 인프라웨어, 'PC용 폴라리스 오피스' 선보여
Aving
또한 10월 말 출시될 정식버전에서는 ODF(Open document format)와 함께 MS의 PPT, Excel과 호환되는 슬라이드, 시트까지 지원된다. 이 외에도 다양한 업무환경을 지원할 수 있는 모바일 스캐너, 모바일 프린트, 전자칠판 솔루션 등을 비롯하여 기업용 모바일 보안 ...

October 23, 2014 07:05 AM

October 22, 2014

Google News

10 ways to help users move from Microsoft Office to LibreOffice - TechRepublic (blog)


TechRepublic (blog)

10 ways to help users move from Microsoft Office to LibreOffice
TechRepublic (blog)
There are extensions for each of the LibreOffice tools, including the likes of the Alternative dialog for Find/Replace and the Multi-format Save. These extensions help make .... ODF formats can be opened by MS Office 2007 SP2 and newer. My experience ...

October 22, 2014 10:21 AM

Planet KDE

Calligra Gemini - now also for Linux :)


Some people may remember earlier this year when Krita Gemini became (to my knowledge) the first open source software to become greenlit on Steam. For those who don't, yeah, that really happened ;) Krita Gemini was a project created in cooperation between the KDE community's Calligra team, the little software consultancy KO GmbH, and a large semiconductor manufacturer named Intel, who had some devices they needed to be able to show off. Krita Gemini is available on the Steam store, though not yet for Linux (as it turns out, Steam packaging for Linux is even more awkward than building stand-alone installers for Windows, an odd sort of situation for us used to sensible package managers)


Earlier this year (late April 2014) the team from KO and Calligra which built Krita Gemini had a teleconference with the Intel team, and we agreed that other applications would be well suited to a similar attention, and we came up with the idea of building Calligra Gemini, an application which would encapsulate Words and Stage, Calligra's word processor and presentation tool respectively, in the same way that Krita Gemini encapsulates Krita, with automatic switching between the existing desktop UX and a new touch friendly UX created for the purpose. Over the last little while, i've been posting builds on the project minisite (along with release notes and screenshots and such).


So now, with the initial work on that project reaching its conclusion, i decided that it was time to expose a few more people to it than what's been the case so far. So, over the course of this weekend, between making some tasty bread, cleaning and cooking dinner, i have been working on some packages for people who don't run Windows. Specifically, i have made a set of packages for openSUSE (just 13.1, in various guises, for now - others will follow), and they're available right here (and also shown on the project's minisite linked above)


Finally, i also released a short story i've been writing over the last couple of weeks (while waiting on the editors to get back to me on the novel i've also been working on). This is relevant here because i have been dogfooding; it was written entirely using Calligra Gemini, and the pdf and ePub versions were produced using the Calligra features as well. Finally, the work is stored in a git repository, which is also controlled by Calligra Gemini's support for using Git as cloud storage. The story is available as pdf and ePub on my deviantArt page :)

The word of the day is: Geiko

by Dan Leinir Turthra Jensen (leinir) at October 22, 2014 07:41 AM

WebODF news

Open Source Business Award 2014 for WebODF

Open Source Business Award 2014

Open Source Business Award 2014

The project WebODF has been awarded with the third price in the Open Source Business Award 2014 (OSBAR), selected out of 17 nominated projects.

October 22, 2014 12:00 AM

October 20, 2014

Google News

'폴라리스 오피스' 문서 SW 판도 바꾸나 - 아이뉴스24


아이뉴스24

'폴라리스 오피스' 문서 SW 판도 바꾸나
아이뉴스24
또 폴라리스 오피스는 MS오피스의 파워포인트(PPT), 엑셀(Excel)과 호환되는 슬라이드, 시트도 지원하고, 최근 공공기관 문서 표준화 움직임에 따라 공공기관에서 도입이 검토되고 있는 오픈도큐먼트포맷(ODF, Open Document Format)도 지원한다. ODF는 국제 ...
인프라웨어, 스마트워크 환경 솔루션 공개ajunews

all 9 news articles »

October 20, 2014 08:39 AM

'폴라리스 오피스' 문서 SW 판도 바꾸나 - 아이뉴스24


아이뉴스24

'폴라리스 오피스' 문서 SW 판도 바꾸나
아이뉴스24
또 폴라리스 오피스는 MS오피스의 파워포인트(PPT), 엑셀(Excel)과 호환되는 슬라이드, 시트도 지원하고, 최근 공공기관 문서 표준화 움직임에 따라 공공기관에서 도입이 검토되고 있는 오픈도큐먼트포맷(ODF, Open Document Format)도 지원한다. ODF는 국제 ...

October 20, 2014 08:39 AM

[BB-1020] 신형 맥미니, 메모리 업그레이드 불가 - 블로터닷넷


아이뉴스24

[BB-1020] 신형 맥미니, 메모리 업그레이드 불가
블로터닷넷
또한, 10월 말 출시될 정식버전에서는 ODF (Open document format)와 함께 MS의 PPT, Excel과 호환되는 슬라이드, 시트까지 지원합니다. 이 외에도 다양한 업무환경을 지원할 수 있는 모바일 스캐너, 모바일 프린트, 전자칠판 솔루션 등을 비롯하여 기업용 모바일 ...
'폴라리스 오피스' 문서 SW 판도 바꾸나아이뉴스24

all 9 news articles »

October 20, 2014 02:43 AM

인프라웨어 WIS, 참가스마트워크 환경 솔루션 공개 - 이투데이


인프라웨어 WIS, 참가스마트워크 환경 솔루션 공개
이투데이
또한, 10월 말 출시될 정식버전에서는 ODF (Open document format)와 함께 MS의 PPT, Excel과 호환되는 슬라이드, 시트까지 지원된다. 이 외에도 다양한 업무환경을 지원할 수 있는 모바일 스캐너, 모바일 프린트, 전자칠판 솔루션 등을 비롯하여 기업용 모바일 보 ...

October 20, 2014 01:39 AM

인프라웨어, 스마트워크 환경 솔루션 공개 - ajunews


ajunews

인프라웨어, 스마트워크 환경 솔루션 공개
ajunews
또한, 10월 말 출시될 정식버전에서는 ODF (Open document format)와 함께 MS의 PPT, Excel과 호환되는 슬라이드, 시트까지 지원된다. 이 외에도 다양한 업무환경을 지원할 수 있는 모바일 스캐너, 모바일 프린트, 전자칠판 솔루션 등을 비롯하여 기업용 모바일 보 ...

and more »

October 20, 2014 01:10 AM

October 16, 2014

Google News

Munich va-t-elle retourner à Windows ? Pour le maire de la ville, cela coûterait ... - Developpez.com


Munich va-t-elle retourner à Windows ? Pour le maire de la ville, cela coûterait ...
Developpez.com
Plaintes liées essentiellement à la compatibilité entre les formats utilisés dans OpenOffice et Microsoft Office. Compte tenu du fait que le format ODF ne soit pas adopté sur le plan national, la municipalité serait parfois confrontée à la manipulation ...

October 16, 2014 11:36 AM

October 15, 2014

www.opendocsociety.org

OpenDoc Society collaborates with UK Cabinet Office

OpenDoc Society has signed an agreement to work together with the Office of the Chief Technology Officer (OCTO) of the UK Government Digital Service (GDS) to help the UK government migrate to OpenDocument Format. OCTO's goal is to equip government with the right technology to deliver great digital services.

The UK Cabinet Office announced the selection of the Open Document Format (ODF) for use across government for editable government documents in July 2014.

OpenDoc Society and GDS will collaborate on providing 'hands on' guidance to advise technology leaders in the UK government on how to implement and transition to ODF with the minimum of disruption for their users inside and outside of government.

The guidance will be primarily aimed at technology professionals in government who are managing the implementation of ODF in their organisation. It aims to provide the technical information required to implement/migrate to ODF with regards to software application management in an enterprise environment and integration with other tools, for example accessibility tools. We expect the result of this collaboration to be useful in helping technology professionals to devise implementation plans, build business cases and inform decision makers, project managers and trainers. This includes information that end users should find useful in avoiding interoperability issues across different software packages and software versions.

October 15, 2014 08:30 AM

October 14, 2014

ODF Wikipedia Page

PC-XT: fix tag typo; formatting: 5x link→cite web, 2x HTML entity, heading-style, link→cite news (using Advisor.js)

fix tag typo; formatting: 5x link→cite web, 2x HTML entity, heading-style, link→cite news (using Advisor.js)

← Previous revision Revision as of 18:23, 14 October 2014
Line 115: Line 115:
 
{{Main|OpenDocument technical specification}}
 
{{Main|OpenDocument technical specification}}
   
The most common [[filename extension]]s used for OpenDocument documents are:<ref>{{es icon}} [http://www.ua.es/en/rua/formatos.html UA.es]</ref><ref name="hg flat opendocument">{{cite web |url=http://www.ensode.net/roller/dheffelfinger/entry/openoffice_documents_version_control_with |title=OpenOffice.org Document Version Control With Mercurial |accessdate=7 June 2010}}</ref>
+
The most common [[filename extension]]s used for OpenDocument documents are:<ref>{{cite web|url=http://www.ua.es/en/rua/formatos.html|title=UA.es|work=ua.es|language=es}}</ref><ref name="hg flat opendocument">{{cite web |url=http://www.ensode.net/roller/dheffelfinger/entry/openoffice_documents_version_control_with |title=OpenOffice.org Document Version Control With Mercurial |accessdate=7 June 2010}}</ref>
   
 
* <code>.odt</code> and <code>.fodt</code> for [[word processing]] (text) documents
 
* <code>.odt</code> and <code>.fodt</code> for [[word processing]] (text) documents
Line 152: Line 152:
 
The OpenDocument format is used in [[free software]] and in [[proprietary software]].
 
The OpenDocument format is used in [[free software]] and in [[proprietary software]].
 
This includes [[office suites]] (both stand-alone and web-based) and individual applications such as word-processors, spreadsheets, presentation, and data management applications. Prominent office suites supporting OpenDocument fully or partially include:
 
This includes [[office suites]] (both stand-alone and web-based) and individual applications such as word-processors, spreadsheets, presentation, and data management applications. Prominent office suites supporting OpenDocument fully or partially include:
*[[AbiWord]]<ref>{{cite web|url=http://www.abisource.com/wiki/OpenDocument_support|title=OpenDocument support|publisher=AbiSource community|work=AbiWord Wiki|accessdate=10 September 2012}}</ref><ref name="abiword">[http://www.abisource.com/release-notes/2.4.2.phtml Abiword 2.4.2 Release Notes.]. Retrieved 2009-03-03</ref>
+
*[[AbiWord]]<ref>{{cite web|url=http://www.abisource.com/wiki/OpenDocument_support|title=OpenDocument support|publisher=AbiSource community|work=AbiWord Wiki|accessdate=10 September 2012}}</ref><ref name="abiword">{{cite web|url=http://www.abisource.com/release-notes/2.4.2.phtml|title=Abiword 2.4.2 Release Notes.|work=abisource.com|accessdate=2009-03-03}}</ref>
 
*[[Adobe Buzzword]]<ref>{{cite web|url=http://labs.adobe.com/technologies/buzzword/ |title=Adobe Buzzword online word processor from Acrobat.com |publisher=Labs.adobe.com |date= |accessdate=19 May 2009}}</ref>
 
*[[Adobe Buzzword]]<ref>{{cite web|url=http://labs.adobe.com/technologies/buzzword/ |title=Adobe Buzzword online word processor from Acrobat.com |publisher=Labs.adobe.com |date= |accessdate=19 May 2009}}</ref>
 
*[[Apache OpenOffice]]
 
*[[Apache OpenOffice]]
*[[Atlantis Word Processor]]<ref>[http://www.atlantiswordprocessor.com/en/news/1_6_5.htm Atlantis Word Processor 1.6.5 release notes]. Retrieved 2010-01-28</ref>
+
*[[Atlantis Word Processor]]<ref>{{cite news|url=http://www.atlantiswordprocessor.com/en/news/1_6_5.htm|title=Atlantis Word Processor 1.6.5 release notes|work=atlantiswordprocessor.com|accessdate=2010-01-28}}</ref>
 
*[[Calligra Suite]]<ref>{{cite web|url=http://www.calligra-suite.org/words/ |title=Words |publisher=Calligra Suite |date= |accessdate=23 February 2012}}</ref>
 
*[[Calligra Suite]]<ref>{{cite web|url=http://www.calligra-suite.org/words/ |title=Words |publisher=Calligra Suite |date= |accessdate=23 February 2012}}</ref>
 
*[[Corel Corporation|Corel]] [[Corel WordPerfect Office|WordPerfect Office X6]]<ref>{{cite web
 
*[[Corel Corporation|Corel]] [[Corel WordPerfect Office|WordPerfect Office X6]]<ref>{{cite web
Line 164: Line 164:
 
*[[Gnumeric]]<ref>{{cite web|url=http://projects.gnome.org/gnumeric/doc/sect-file-formats.shtml|title=File Formats|author=Eric Baudais & others|publisher=GNOME Documentation Project|work=The Gnumeric Manual, version 1.10|date=February 2010|accessdate=10 September 2012}}</ref>
 
*[[Gnumeric]]<ref>{{cite web|url=http://projects.gnome.org/gnumeric/doc/sect-file-formats.shtml|title=File Formats|author=Eric Baudais & others|publisher=GNOME Documentation Project|work=The Gnumeric Manual, version 1.10|date=February 2010|accessdate=10 September 2012}}</ref>
 
*[[Google Docs]]
 
*[[Google Docs]]
*[[IBM Lotus Symphony]]<ref name="register" /><ref>{{cite web|url=http://blogs.msdn.com/dmahugh/archive/2009/05/09/1-2-1.aspx |title=1 + 2 = 1?|author=Doug Mahugh|publisher=MSDN Blogs|date=10 May 2009<!-- 2:26 AM-->|accessdate=10 September 2012}}</ref><ref>[http://symphony.lotus.com/software/lotus/symphony/help.nsf/ReleaseNotes Symphony.lotus.com]</ref>
+
*[[IBM Lotus Symphony]]<ref name="register" /><ref>{{cite web|url=http://blogs.msdn.com/dmahugh/archive/2009/05/09/1-2-1.aspx |title=1 + 2 = 1?|author=Doug Mahugh|publisher=MSDN Blogs|date=10 May 2009<!-- 2:26 AM-->|accessdate=10 September 2012}}</ref><ref>{{cite web|url=http://symphony.lotus.com/software/lotus/symphony/help.nsf/ReleaseNotes|title=Symphony.lotus.com|work=symphony.lotus.com}}</ref>
 
*[[Inkscape]] exports .odg
 
*[[Inkscape]] exports .odg
*[[KOffice]]<ref>[http://koffice.org/filters/1.6/ Koffice.org]</ref>
+
*[[KOffice]]<ref>{{cite web|url=http://koffice.org/filters/1.6/|title=Koffice.org|work=koffice.org}}</ref>
 
*[[LibreOffice]]<ref name="register" />
 
*[[LibreOffice]]<ref name="register" />
 
*Microsoft Office 2003 and Office XP (with the Open Source OpenXML/ODF Translator Add-in for Office)<ref>{{cite web|url=http://odf-converter.sourceforge.net/download.html#hRequirements|title=OpenXML/ODF Translator Add-ins for Office|accessdate={{Date|2014-01-31}}}}</ref>
 
*Microsoft Office 2003 and Office XP (with the Open Source OpenXML/ODF Translator Add-in for Office)<ref>{{cite web|url=http://odf-converter.sourceforge.net/download.html#hRequirements|title=OpenXML/ODF Translator Add-ins for Office|accessdate={{Date|2014-01-31}}}}</ref>
Line 183: Line 183:
 
*[[Zoho Office Suite]]<ref name="register" />
 
*[[Zoho Office Suite]]<ref name="register" />
   
Various organizations have announced development of conversion software (including ''plugins'' and ''filters'') to support OpenDocument on [[Microsoft]]'s products.<ref>{{cite web | url=http://www.groklaw.net/article.php?story=20060504015438308 | title=OpenDocument Foundation to MA: We Have a Plugin | date=4 May 2006 | accessdate=23 August 2006 | publisher=Groklaw}}</ref><ref>{{cite news | url=http://www.zdnet.com.au/news/software/soa/Microsoft_Office_to_get_a_dose_of_OpenDocument/0,130061733,139255766,00.htm | title=Microsoft Office to get a dose of OpenDocument | date=5 May 2006 | accessdate=6 December 2006|publisher=CNet}}</ref> {{asof|July 2007}}, there are nine packages of conversion software.<!--Commented out invalid reference <ref name="odf20070727"/>--> Microsoft first released support for the OpenDocument Format in Office 2007 SP2.<ref>{{cite web | title=Office 2007 SP2 Supports ODF | url=http://www.pcworld.com/businesscenter/article/164015/office_2007_sp2_supports_odf.html | date=28 April 2009 | publisher=PC World}}</ref> However, the implementation faced [[OpenDocument software#Microsoft Office 2007 SP2 support controversy|substantial criticism]] and the [[ODF Alliance]] and others claimed that the third party plugins provided better support.<ref name="sp2-fact-sheet">{{cite web | url=http://web.archive.org/web/20090611181719/http://www.odfalliance.org/resources/fact-sheet-Microsoft-ODF-support.pdf | title=Fact-sheet Microsoft ODF support | accessdate=24 May 2009 | quote=''MS Excel 2007 will process ODF spreadsheet documents when loaded via the Sun Plug-In 3.0 for MS Office or the SourceForge “OpenXML/ODF Translator Add-in for Office,” but will fail when using the “built-in” support provided by Office 2007 SP2.'' | publisher=odfalliance}}</ref> Microsoft Office 2010 can open and save OpenDocument Format documents natively, although not all features are supported.<ref>[http://office.microsoft.com/en-us/starter-help/differences-between-the-opendocument-text-odt-format-and-the-word-docx-format-HA010355788.aspx Differences between the OpenDocument Text (.odt) format and the Word (.docx) format]</ref>
+
Various organizations have announced development of conversion software (including ''plugins'' and ''filters'') to support OpenDocument on [[Microsoft]]'s products.<ref>{{cite web | url=http://www.groklaw.net/article.php?story=20060504015438308 | title=OpenDocument Foundation to MA: We Have a Plugin | date=4 May 2006 | accessdate=23 August 2006 | publisher=Groklaw}}</ref><ref>{{cite news | url=http://www.zdnet.com.au/news/software/soa/Microsoft_Office_to_get_a_dose_of_OpenDocument/0,130061733,139255766,00.htm | title=Microsoft Office to get a dose of OpenDocument | date=5 May 2006 | accessdate=6 December 2006|publisher=CNet}}</ref> {{asof|July 2007}}, there are nine packages of conversion software.<!--Commented out invalid reference <ref name="odf20070727"/>--> Microsoft first released support for the OpenDocument Format in Office 2007 SP2.<ref>{{cite web | title=Office 2007 SP2 Supports ODF | url=http://www.pcworld.com/businesscenter/article/164015/office_2007_sp2_supports_odf.html | date=28 April 2009 | publisher=PC World}}</ref> However, the implementation faced [[OpenDocument software#Microsoft Office 2007 SP2 support controversy|substantial criticism]] and the [[ODF Alliance]] and others claimed that the third party plugins provided better support.<ref name="sp2-fact-sheet">{{cite web | url=http://web.archive.org/web/20090611181719/http://www.odfalliance.org/resources/fact-sheet-Microsoft-ODF-support.pdf | title=Fact-sheet Microsoft ODF support | accessdate=24 May 2009 | quote=''MS Excel 2007 will process ODF spreadsheet documents when loaded via the Sun Plug-In 3.0 for MS Office or the SourceForge “OpenXML/ODF Translator Add-in for Office,” but will fail when using the “built-in” support provided by Office 2007 SP2.'' | publisher=odfalliance}}</ref> Microsoft Office 2010 can open and save OpenDocument Format documents natively, although not all features are supported.<ref>{{cite web|url=http://office.microsoft.com/en-us/starter-help/differences-between-the-opendocument-text-odt-format-and-the-word-docx-format-HA010355788.aspx|title=Differences between the OpenDocument Text (.odt) format and the Word (.docx) format|work=office.microsoft.com}}</ref>
   
 
[[Mac OS X 10.5]] offers both a new [[TextEdit]] version and [[Quick Look]] feature supporting the OpenDocument Text format (albeit with some formatting loss).{{Clarify|date=October 2009}}
 
[[Mac OS X 10.5]] offers both a new [[TextEdit]] version and [[Quick Look]] feature supporting the OpenDocument Text format (albeit with some formatting loss).{{Clarify|date=October 2009}}
Line 202: Line 202:
 
Key contributor [[Sun Microsystems]] made an irrevocable intellectual property covenant, providing all implementers with the guarantee that Sun will not seek to enforce any of its enforceable U.S. or foreign patents against any implementation of the OpenDocument specification in which development Sun participates to the point of incurring an obligation.<ref name="SunOpenDocumentPatentStatement">{{cite web | url = http://www.oasis-open.org/committees/office/ipr.php | title = Sun OpenDocument Patent Statement | work = OASIS Open Document Format for Office Applications (OpenDocument) TC | author = Microsystems, Inc. | publisher = OASIS foundation}}</ref>
 
Key contributor [[Sun Microsystems]] made an irrevocable intellectual property covenant, providing all implementers with the guarantee that Sun will not seek to enforce any of its enforceable U.S. or foreign patents against any implementation of the OpenDocument specification in which development Sun participates to the point of incurring an obligation.<ref name="SunOpenDocumentPatentStatement">{{cite web | url = http://www.oasis-open.org/committees/office/ipr.php | title = Sun OpenDocument Patent Statement | work = OASIS Open Document Format for Office Applications (OpenDocument) TC | author = Microsystems, Inc. | publisher = OASIS foundation}}</ref>
   
A second contributor to ODF development, [[IBM]] &mdash; which, for instance, has contributed Lotus spreadsheet documentation<ref>{{cite web|url=http://lists.oasis-open.org/archives/office/200607/msg00076.html|title=Formula subcommittee status|author=David A. Wheeler|publisher=office@lists.oasis-open.org, office-formula@lists.oasis-open.org|date=21 Jul 2006<!-- 13:50:46 -0400 (EDT)-->|accessdate=12 September 2012}}</ref> &mdash; has made their patent rights available through their'' Interoperability Specifications Pledge'' in which "IBM irrevocably covenants to you that it will not assert any Necessary Claims against you for your making, using, importing, selling, or offering for sale Covered Implementations."<ref name="IBM-ISP-list">{{cite web|url=http://www-03.ibm.com/linux/ossstds/isplist.html|title=Interoperability Pledge Specification List|work=Interoperability Specifications Pledge|publisher=IBM Corp|date=12 December 2011|accessdate=10 September 2012}}</ref>
+
A second contributor to ODF development, [[IBM]] which, for instance, has contributed Lotus spreadsheet documentation<ref>{{cite web|url=http://lists.oasis-open.org/archives/office/200607/msg00076.html|title=Formula subcommittee status|author=David A. Wheeler|publisher=office@lists.oasis-open.org, office-formula@lists.oasis-open.org|date=21 Jul 2006<!-- 13:50:46 -0400 (EDT)-->|accessdate=12 September 2012}}</ref> has made their patent rights available through their'' Interoperability Specifications Pledge'' in which "IBM irrevocably covenants to you that it will not assert any Necessary Claims against you for your making, using, importing, selling, or offering for sale Covered Implementations."<ref name="IBM-ISP-list">{{cite web|url=http://www-03.ibm.com/linux/ossstds/isplist.html|title=Interoperability Pledge Specification List|work=Interoperability Specifications Pledge|publisher=IBM Corp|date=12 December 2011|accessdate=10 September 2012}}</ref>
   
 
The [[Software Freedom Law Center]] has [http://www.softwarefreedom.org/resources/2006/OpenDocument.html examined] whether there are any legal barriers to the use of the OpenDocument Format (ODF) in free and open source software arising from the standardization process. In their opinion ODF is free of legal encumbrances that would prevent its use in free and open source software, as distributed under licenses authored by Apache and the FSF.
 
The [[Software Freedom Law Center]] has [http://www.softwarefreedom.org/resources/2006/OpenDocument.html examined] whether there are any legal barriers to the use of the OpenDocument Format (ODF) in free and open source software arising from the standardization process. In their opinion ODF is free of legal encumbrances that would prevent its use in free and open source software, as distributed under licenses authored by Apache and the FSF.
Line 218: Line 218:
 
*Several organisations, such as the [http://opendocumentfellowship.com/ OpenDocument Fellowship] and [http://opendocsociety.org/ OpenDoc Society] were founded to support and promote OpenDocument.
 
*Several organisations, such as the [http://opendocumentfellowship.com/ OpenDocument Fellowship] and [http://opendocsociety.org/ OpenDoc Society] were founded to support and promote OpenDocument.
 
<!-- *The [http://www.oidi.org OIDI.org] (Open Interoperative Document Initiative) is committed to encouraging efforts by governments at all levels, around the globe, to implement changes necessary to ensure public documents are open and interoperable and thus available to all citizens/residents without the need for specific vendor software. -->
 
<!-- *The [http://www.oidi.org OIDI.org] (Open Interoperative Document Initiative) is committed to encouraging efforts by governments at all levels, around the globe, to implement changes necessary to ensure public documents are open and interoperable and thus available to all citizens/residents without the need for specific vendor software. -->
*The UK government has adopted ODF as the standard for all documents in the UK civil service <rev>{{cite web | url=https://www.gov.uk/government/news/open-document-formats-selected-to-meet-user-needs|title=Open document formats selected to meet user needs}} </ref>
+
*The UK government has adopted ODF as the standard for all documents in the UK civil service <ref>{{cite web | url=https://www.gov.uk/government/news/open-document-formats-selected-to-meet-user-needs|title=Open document formats selected to meet user needs}} </ref>
 
*The [[Wikimedia Foundation]] supports ODF export from [[MediaWiki]], which powers [[Wikipedia]] and a number of other Internet [[wiki]]-based sites.<ref>{{cite web | url= http://wikimediafoundation.org/wiki/Wikis_Go_Printable | title= Wikis Go Printable | work= [[Wikimedia Foundation]] | date= 13 December 2007 | accessdate= 31 December 2007}}</ref>
 
*The [[Wikimedia Foundation]] supports ODF export from [[MediaWiki]], which powers [[Wikipedia]] and a number of other Internet [[wiki]]-based sites.<ref>{{cite web | url= http://wikimediafoundation.org/wiki/Wikis_Go_Printable | title= Wikis Go Printable | work= [[Wikimedia Foundation]] | date= 13 December 2007 | accessdate= 31 December 2007}}</ref>
   
Line 227: Line 227:
 
* It is not permitted to use generic ODF formatting style elements (like font information) for the MathML elements.<ref name="doyourmath"/>
 
* It is not permitted to use generic ODF formatting style elements (like font information) for the MathML elements.<ref name="doyourmath"/>
   
== Worldwide adoption ==
+
==Worldwide adoption==
 
{{main|OpenDocument adoption}}
 
{{main|OpenDocument adoption}}
   

by PC-XT at October 14, 2014 06:23 PM

Google News

[기고]한글'워드' 안 깔린 PC로도 민원 신청서 작성 OK - 제주의소리


제주의소리

[기고]한글'워드' 안 깔린 PC로도 민원 신청서 작성 OK
제주의소리
주민들이 행정기관 민원실에 많이 제출하는 민원 신청서와 공직에 지원하는 민간 전문가가 작성하는 개방형직위 응시원서에 대해 한글문서와 함께 '개방형 문서 서식(open document format, ODF)' 파일도 제공하고 있다. 방문민원 건수가 가장 많은 전입신고서(1 ...
개방형 문서서식 확대...'한글워드' 없어도 민원신청서 OKHeadline jeju

all 3 news articles »

October 14, 2014 12:45 AM

개방형 문서서식 확대...'한글워드' 없어도 민원신청서 OK - Headline jeju


Headline jeju

개방형 문서서식 확대...'한글워드' 없어도 민원신청서 OK
Headline jeju
온라인 검색에 익숙한 사람이라면 금방 받을 수 있지만 아직 ODF에 대해 생소한 사람들을 위해 자세한 안내가 필요하다. 예를들면, 민원24의 검색창에서 민원신청서를 조회하고 전입신고의 ODF를 클릭하면 신청서가 출력된다. 얼핏 보면 아주 사소한 일일 런지는 ...

and more »

October 14, 2014 12:26 AM

October 13, 2014

Google News

España, el país que apuesta por los estándares abiertos pero sólo usa PDF - eldiario.es


eldiario.es

España, el país que apuesta por los estándares abiertos pero sólo usa PDF
eldiario.es
Hace unos meses, el Gobierno de Reino Unido realizó un anuncio, precisamente, en este sentido: todos los documentos publicados por el Gobierno estarán en formatos abiertos, concretamente en ODF ( Open Document Format). El anuncio era significativo ...

October 13, 2014 07:04 PM

Svobodný software a peníze - LinuxEXPRES


Svobodný software a peníze
LinuxEXPRES
... podílel na vývoji kancelářského balíku OpenOffice.org, později spoluzaložil The Document Foundation, v jejímž rámci pracuje na vývoji balíku LibreOffice. Účastnil se také návrhu a následném prosazování otevřeného formátu ODF (Open Document Format) ...

October 13, 2014 01:56 PM

ODF Wikipedia Page

StevenDH: /* Standardization */ remove my preview-reflist

Standardization: remove my preview-reflist

← Previous revision Revision as of 13:40, 13 October 2014
Line 144: Line 144:
 
===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>
 
*'''''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>
 
{{reflist}}
 
   
 
==Application support==
 
==Application support==

by StevenDH at October 13, 2014 01:40 PM

StevenDH: /* Standardization */ update and shrink v1.2 paragraph, details are at OpenDocument standardization

Standardization: update and shrink v1.2 paragraph, details are at OpenDocument standardization

← Previous revision Revision as of 13:25, 13 October 2014
Line 140: Line 140:
 
*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. 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>
+
*'''[http://docs.oasis-open.org/office/v1.2/OpenDocument-v1.2.pdf OpenDocument 1.2]''' 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. It consists of three parts: Part 1: OpenDocument Schema, Part 2: Recalculated Formula (OpenFormula) Format and Part 3: Packages. Version 1.2 of the specification was approved as an OASIS Standard on 29 September 2011.<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> It has been submitted to the relevant ISO commitee under the Publicly Available Specification (PAS) procedure in March 2014.<ref>{{cite web | url=http://isotc.iso.org/livelink/livelink?func=ll&objId=16678620&objAction=Open | format=PDF | title=Minutes of ISO/IEC JTC 1/SC 34/WG 6 teleconference meeting, 2014-04-16 | date=2014-04-24 | | accessdate=2014-10-13}}</ref> As of October 2014, it has been unanimously approved as a Draft International Standard, some comments have been raised in process that need to be addressed before OpenDocument 1.2 can proceed to become an International Standard.<ref>{{cite web | url=http://isotc.iso.org/livelink/livelink?func=ll&objId=16810106&objAction=Open | format=PDF | title=ISO/IEC JTC 1/SC 34/WG 6 N 103 Minutes of teleconference meeting of ISO/IEC JTC 1/SC 34/WG 6 2014-09-24, 23:00-00:00 UTC | date=2014-09-25 | accessdate=2014-10-13}}</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>
 
*'''''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>
  +
  +
{{reflist}}
   
 
==Application support==
 
==Application support==

by StevenDH at October 13, 2014 01:25 PM

Fustbariclation: /* Support for OpenDocument */

Support for OpenDocument

← Previous revision Revision as of 07:05, 13 October 2014
Line 218: Line 218:
 
*Several organisations, such as the [http://opendocumentfellowship.com/ OpenDocument Fellowship] and [http://opendocsociety.org/ OpenDoc Society] were founded to support and promote OpenDocument.
 
*Several organisations, such as the [http://opendocumentfellowship.com/ OpenDocument Fellowship] and [http://opendocsociety.org/ OpenDoc Society] were founded to support and promote OpenDocument.
 
<!-- *The [http://www.oidi.org OIDI.org] (Open Interoperative Document Initiative) is committed to encouraging efforts by governments at all levels, around the globe, to implement changes necessary to ensure public documents are open and interoperable and thus available to all citizens/residents without the need for specific vendor software. -->
 
<!-- *The [http://www.oidi.org OIDI.org] (Open Interoperative Document Initiative) is committed to encouraging efforts by governments at all levels, around the globe, to implement changes necessary to ensure public documents are open and interoperable and thus available to all citizens/residents without the need for specific vendor software. -->
*The UK government has adopted ODF as the standard for all documents in the UK civil service <rev>{{cite web | url=https://www.gov.uk/government/news/open-document-formats-selected-to-meet-user-needs}} </ref>
+
*The UK government has adopted ODF as the standard for all documents in the UK civil service <rev>{{cite web | url=https://www.gov.uk/government/news/open-document-formats-selected-to-meet-user-needs|title=Open document formats selected to meet user needs}} </ref>
 
*The [[Wikimedia Foundation]] supports ODF export from [[MediaWiki]], which powers [[Wikipedia]] and a number of other Internet [[wiki]]-based sites.<ref>{{cite web | url= http://wikimediafoundation.org/wiki/Wikis_Go_Printable | title= Wikis Go Printable | work= [[Wikimedia Foundation]] | date= 13 December 2007 | accessdate= 31 December 2007}}</ref>
 
*The [[Wikimedia Foundation]] supports ODF export from [[MediaWiki]], which powers [[Wikipedia]] and a number of other Internet [[wiki]]-based sites.<ref>{{cite web | url= http://wikimediafoundation.org/wiki/Wikis_Go_Printable | title= Wikis Go Printable | work= [[Wikimedia Foundation]] | date= 13 December 2007 | accessdate= 31 December 2007}}</ref>
   

by Fustbariclation at October 13, 2014 07:05 AM

Fustbariclation: /* Support for OpenDocument */

Support for OpenDocument

← Previous revision Revision as of 07:04, 13 October 2014
Line 218: Line 218:
 
*Several organisations, such as the [http://opendocumentfellowship.com/ OpenDocument Fellowship] and [http://opendocsociety.org/ OpenDoc Society] were founded to support and promote OpenDocument.
 
*Several organisations, such as the [http://opendocumentfellowship.com/ OpenDocument Fellowship] and [http://opendocsociety.org/ OpenDoc Society] were founded to support and promote OpenDocument.
 
<!-- *The [http://www.oidi.org OIDI.org] (Open Interoperative Document Initiative) is committed to encouraging efforts by governments at all levels, around the globe, to implement changes necessary to ensure public documents are open and interoperable and thus available to all citizens/residents without the need for specific vendor software. -->
 
<!-- *The [http://www.oidi.org OIDI.org] (Open Interoperative Document Initiative) is committed to encouraging efforts by governments at all levels, around the globe, to implement changes necessary to ensure public documents are open and interoperable and thus available to all citizens/residents without the need for specific vendor software. -->
  +
*The UK government has adopted ODF as the standard for all documents in the UK civil service <rev>{{cite web | url=https://www.gov.uk/government/news/open-document-formats-selected-to-meet-user-needs}} </ref>
 
*The [[Wikimedia Foundation]] supports ODF export from [[MediaWiki]], which powers [[Wikipedia]] and a number of other Internet [[wiki]]-based sites.<ref>{{cite web | url= http://wikimediafoundation.org/wiki/Wikis_Go_Printable | title= Wikis Go Printable | work= [[Wikimedia Foundation]] | date= 13 December 2007 | accessdate= 31 December 2007}}</ref>
 
*The [[Wikimedia Foundation]] supports ODF export from [[MediaWiki]], which powers [[Wikipedia]] and a number of other Internet [[wiki]]-based sites.<ref>{{cite web | url= http://wikimediafoundation.org/wiki/Wikis_Go_Printable | title= Wikis Go Printable | work= [[Wikimedia Foundation]] | date= 13 December 2007 | accessdate= 31 December 2007}}</ref>
   

by Fustbariclation at October 13, 2014 07:04 AM

October 11, 2014

ODF Wikipedia Page

Sardanaphalus: /* Worldwide adoption */ wikitable

Worldwide adoption: wikitable

← Previous revision Revision as of 23:42, 11 October 2014
Line 231: Line 231:
 
One objective of open formats like OpenDocument is to guarantee long-term access to data without legal or technical barriers, and some governments have come to view open formats as a public policy issue. Several governments around the world have introduced policies of partial or complete adoption.<ref name="papers.ssrn.com"/> What this means varies from case to case; in some cases, it means that the ODF standard has a national standard identifier; in some cases, it means that the ODF standard is permitted to be used where national regulation says that non-proprietary formats must be used, and in still other cases, it means that some government body has actually decided that ODF will be used in some specific context. The following is an incomplete list:
 
One objective of open formats like OpenDocument is to guarantee long-term access to data without legal or technical barriers, and some governments have come to view open formats as a public policy issue. Several governments around the world have introduced policies of partial or complete adoption.<ref name="papers.ssrn.com"/> What this means varies from case to case; in some cases, it means that the ODF standard has a national standard identifier; in some cases, it means that the ODF standard is permitted to be used where national regulation says that non-proprietary formats must be used, and in still other cases, it means that some government body has actually decided that ODF will be used in some specific context. The following is an incomplete list:
   
{|
+
{| class="wikitable"
|- style="vertical-align:top;"
+
|-
!style="text-align:right;padding-right:1.25em;"| International
+
|colspan="2" class="hlist"|
+
!style="padding:0.25em 1.0em;"| International
  +
|colspan="2" class="hlist" style="vertical-align:top;padding:0.25em 0.5em;"|
 
* [[NATO]]
 
* [[NATO]]
  +
|-
   
|- style="vertical-align:top;"
+
!rowspan="4" style="padding:0.25em 1.0em;"| National
!rowspan="4" style="text-align:right;padding-right:1.25em;"| National
+
|style="text-align:right;padding-right:0.5em;"| Africa
|style="text-align:right;padding-right:1.25em;"| Africa
+
|class="hlist" style="vertical-align:top;padding:0.25em 0.5em;"|
|class="hlist"|
 
 
* [[South Africa]]
 
* [[South Africa]]
+
|-
|- style="vertical-align:top;"
+
|style="text-align:right;padding-right:0.5em;"| Asia
|style="text-align:right;padding-right:1.25em;"| Asia
+
|class="hlist" style="vertical-align:top;padding:0.25em 0.5em;"|
|class="hlist"|
 
 
* [[Japan]]
 
* [[Japan]]
 
* [[Malaysia]]
 
* [[Malaysia]]
Line 249: Line 250:
 
* [[Russia]]
 
* [[Russia]]
 
* [[South Korea]]
 
* [[South Korea]]
+
|-
|- style="vertical-align:top;"
+
|style="text-align:right;padding-right:0.5em;"| Europe
|style="text-align:right;padding-right:1.25em;"| Europe
+
|style="vertical-align:top;padding:0.25em 0.5em;"|
|class="hlist"|
+
{{startflatlist}}
 
* [[European Union]]<ref name="ec.europa.eu"/>
 
* [[European Union]]<ref name="ec.europa.eu"/>
 
** [[Belgium]]
 
** [[Belgium]]
Line 268: Line 269:
 
** [[Sweden]]
 
** [[Sweden]]
 
** [[United Kingdom]]<ref>{{cite web |url=https://www.gov.uk/government/publications/open-source-open-standards-and-re-use-government-action-plan |title=Open source, open standards and re-use: government action plan |publisher=[[Government of the United Kingdom]] |date=27 January 2010 |deadurl=no<!--present in archive.com-->}}</ref>
 
** [[United Kingdom]]<ref>{{cite web |url=https://www.gov.uk/government/publications/open-source-open-standards-and-re-use-government-action-plan |title=Open source, open standards and re-use: government action plan |publisher=[[Government of the United Kingdom]] |date=27 January 2010 |deadurl=no<!--present in archive.com-->}}</ref>
  +
{{endflatlist}}
  +
{{startflatlist}}
 
* Russia
 
* Russia
 
* [[Serbia]]
 
* [[Serbia]]
 
* [[Switzerland]]
 
* [[Switzerland]]
+
{{endflatlist}}
|- style="vertical-align:top;"
+
|-
|style="text-align:right;padding-right:1.25em;white-space:nowrap;"| S America
+
|style="text-align:right;white-space:nowrap;padding-right:0.5em;"| S America
|class="hlist"|
+
|class="hlist" style="vertical-align:top;padding:0.25em 0.5em;"|
 
* [[Brazil]]
 
* [[Brazil]]
 
* [[Uruguay]]<ref>{{cite web |url=http://www.agesic.gub.uy/innovaportal/file/497/1/estandares_ofimatica_v20.pdf |title=Estándares de ofimática |publisher=Agestic.gub.uy |date= |accessdate=2013-05-01}}</ref>
 
* [[Uruguay]]<ref>{{cite web |url=http://www.agesic.gub.uy/innovaportal/file/497/1/estandares_ofimatica_v20.pdf |title=Estándares de ofimática |publisher=Agestic.gub.uy |date= |accessdate=2013-05-01}}</ref>
 
* [[Venezuela]]
 
* [[Venezuela]]
  +
|-
   
|- style="vertical-align:top;"
+
!style="padding:0.25em 1.0em;"| Subnational
!style="text-align:right;padding-right:1.25em;"| Subnational ||
+
|colspan="2" class="hlist" style="vertical-align:top;padding:0.25em 0.5em;"|
|class="hlist"|
 
 
* [[Andalusia]], Spain
 
* [[Andalusia]], Spain
 
* [[Assam]], India
 
* [[Assam]], India

by Sardanaphalus at October 11, 2014 11:42 PM

Sardanaphalus: /* Worldwide adoption */ corrections

Worldwide adoption: corrections

← Previous revision Revision as of 18:26, 11 October 2014
Line 233: Line 233:
 
{|
 
{|
 
|- style="vertical-align:top;"
 
|- style="vertical-align:top;"
!style="text-align:right;padding-right:1.5em;"| International
+
!style="text-align:right;padding-right:1.25em;"| International
 
|colspan="2" class="hlist"|
 
|colspan="2" class="hlist"|
 
* [[NATO]]
 
* [[NATO]]
   
 
|- style="vertical-align:top;"
 
|- style="vertical-align:top;"
!rowspan="4" style="text-align:right;padding-right:1.5em;"| National
+
!rowspan="4" style="text-align:right;padding-right:1.25em;"| National
|style="padding-right:1.0em;"| Africa
+
|style="text-align:right;padding-right:1.25em;"| Africa
 
|class="hlist"|
 
|class="hlist"|
 
* [[South Africa]]
 
* [[South Africa]]
   
 
|- style="vertical-align:top;"
 
|- style="vertical-align:top;"
|style="padding-right:1.0em;"| Asia
+
|style="text-align:right;padding-right:1.25em;"| Asia
 
|class="hlist"|
 
|class="hlist"|
 
* [[Japan]]
 
* [[Japan]]
 
* [[Malaysia]]
 
* [[Malaysia]]
 
* [[India]]
 
* [[India]]
  +
* [[Russia]]
 
* [[South Korea]]
 
* [[South Korea]]
   
 
|- style="vertical-align:top;"
 
|- style="vertical-align:top;"
|style="padding-right:1.0em;"| Europe
+
|style="text-align:right;padding-right:1.25em;"| Europe
 
|class="hlist"|
 
|class="hlist"|
* [[European Union]] member states<ref name="ec.europa.eu"/>
+
* [[European Union]]<ref name="ec.europa.eu"/>
 
** [[Belgium]]
 
** [[Belgium]]
 
** [[Croatia]]
 
** [[Croatia]]
Line 266: Line 267:
 
** [[Poland]]
 
** [[Poland]]
 
** [[Portugal]]<ref>{{cite web |url=http://www.esop.pt/portugal-publishes-open-standards-catalogodf-pdf-and-several-other-standards-are-mandatory/ |title=ESOP » Portugal publishes open standards catalog. ODF, PDF and several other standards are mandatory |publisher=Esop.pt |date= |accessdate=2013-05-01}}</ref>
 
** [[Portugal]]<ref>{{cite web |url=http://www.esop.pt/portugal-publishes-open-standards-catalogodf-pdf-and-several-other-standards-are-mandatory/ |title=ESOP » Portugal publishes open standards catalog. ODF, PDF and several other standards are mandatory |publisher=Esop.pt |date= |accessdate=2013-05-01}}</ref>
** [[Russia]]
 
** [[Serbia]]
 
 
** [[Slovakia]]
 
** [[Slovakia]]
 
** [[Sweden]]
 
** [[Sweden]]
** [[Switzerland]]
 
 
** [[United Kingdom]]<ref>{{cite web |url=https://www.gov.uk/government/publications/open-source-open-standards-and-re-use-government-action-plan |title=Open source, open standards and re-use: government action plan |publisher=[[Government of the United Kingdom]] |date=27 January 2010 |deadurl=no<!--present in archive.com-->}}</ref>
 
** [[United Kingdom]]<ref>{{cite web |url=https://www.gov.uk/government/publications/open-source-open-standards-and-re-use-government-action-plan |title=Open source, open standards and re-use: government action plan |publisher=[[Government of the United Kingdom]] |date=27 January 2010 |deadurl=no<!--present in archive.com-->}}</ref>
  +
* Russia
  +
* [[Serbia]]
  +
* [[Switzerland]]
   
 
|- style="vertical-align:top;"
 
|- style="vertical-align:top;"
|style="padding-right:1.0em;white-space:nowrap;"| South America
+
|style="text-align:right;padding-right:1.25em;white-space:nowrap;"| S America
 
|class="hlist"|
 
|class="hlist"|
 
* [[Brazil]]
 
* [[Brazil]]
Line 281: Line 282:
   
 
|- style="vertical-align:top;"
 
|- style="vertical-align:top;"
!style="text-align:right;padding-right:1.5em;"| Subnational ||
+
!style="text-align:right;padding-right:1.25em;"| Subnational ||
 
|class="hlist"|
 
|class="hlist"|
 
* [[Andalusia]], Spain
 
* [[Andalusia]], Spain

by Sardanaphalus at October 11, 2014 06:26 PM

Sardanaphalus: /* Worldwide adoption */ reduced unused space via table/hlists

Worldwide adoption: reduced unused space via table/hlists

← Previous revision Revision as of 18:08, 11 October 2014
Line 226: Line 226:
 
* It is not permitted to use generic ODF formatting style elements (like font information) for the MathML elements.<ref name="doyourmath"/>
 
* It is not permitted to use generic ODF formatting style elements (like font information) for the MathML elements.<ref name="doyourmath"/>
   
==Worldwide adoption==
+
== Worldwide adoption ==
{{Main|OpenDocument adoption}}
+
{{main|OpenDocument adoption}}
   
 
One objective of open formats like OpenDocument is to guarantee long-term access to data without legal or technical barriers, and some governments have come to view open formats as a public policy issue. Several governments around the world have introduced policies of partial or complete adoption.<ref name="papers.ssrn.com"/> What this means varies from case to case; in some cases, it means that the ODF standard has a national standard identifier; in some cases, it means that the ODF standard is permitted to be used where national regulation says that non-proprietary formats must be used, and in still other cases, it means that some government body has actually decided that ODF will be used in some specific context. The following is an incomplete list:
 
One objective of open formats like OpenDocument is to guarantee long-term access to data without legal or technical barriers, and some governments have come to view open formats as a public policy issue. Several governments around the world have introduced policies of partial or complete adoption.<ref name="papers.ssrn.com"/> What this means varies from case to case; in some cases, it means that the ODF standard has a national standard identifier; in some cases, it means that the ODF standard is permitted to be used where national regulation says that non-proprietary formats must be used, and in still other cases, it means that some government body has actually decided that ODF will be used in some specific context. The following is an incomplete list:
   
===International level===
+
{|
  +
|- style="vertical-align:top;"
  +
!style="text-align:right;padding-right:1.5em;"| International
  +
|colspan="2" class="hlist"|
 
* [[NATO]]
 
* [[NATO]]
   
{{col-begin}}
+
|- style="vertical-align:top;"
{{col-break}}
+
!rowspan="4" style="text-align:right;padding-right:1.5em;"| National
+
|style="padding-right:1.0em;"| Africa
===National level===
+
|class="hlist"|
 
====Africa====
 
 
* [[South Africa]]
 
* [[South Africa]]
   
====Asia====
+
|- style="vertical-align:top;"
  +
|style="padding-right:1.0em;"| Asia
  +
|class="hlist"|
 
* [[Japan]]
 
* [[Japan]]
 
* [[Malaysia]]
 
* [[Malaysia]]
Line 246: Line 246:
 
* [[South Korea]]
 
* [[South Korea]]
   
====Europe====
+
|- style="vertical-align:top;"
  +
|style="padding-right:1.0em;"| Europe
  +
|class="hlist"|
 
* [[European Union]] member states<ref name="ec.europa.eu"/>
 
* [[European Union]] member states<ref name="ec.europa.eu"/>
  +
** [[Belgium]]
  +
** [[Croatia]]
  +
** [[Denmark]]
  +
** [[France]]
  +
** [[Germany]]
  +
** [[Hungary]]
  +
** [[Italy]]
  +
** [[Netherlands]]<ref>{{cite web |title=ODF 1.2 on Dutch "apply or explain" list |url=https://lijsten.forumstandaardisatie.nl/open-standaard/odf12}}</ref>
  +
** [[Norway]]<ref name="NorwayDocumentStandard">{{cite web |title=New obligatory IT standards for the state sector adopted |url=http://www.regjeringen.no/en/dep/fad/press-centre/press-releases/2009/new-obligatory-it-standards-for-the-stat.html?id=570650 |accessdate=19 December 2012}}</ref>
  +
** [[Poland]]
  +
** [[Portugal]]<ref>{{cite web |url=http://www.esop.pt/portugal-publishes-open-standards-catalogodf-pdf-and-several-other-standards-are-mandatory/ |title=ESOP » Portugal publishes open standards catalog. ODF, PDF and several other standards are mandatory |publisher=Esop.pt |date= |accessdate=2013-05-01}}</ref>
  +
** [[Russia]]
  +
** [[Serbia]]
  +
** [[Slovakia]]
  +
** [[Sweden]]
  +
** [[Switzerland]]
  +
** [[United Kingdom]]<ref>{{cite web |url=https://www.gov.uk/government/publications/open-source-open-standards-and-re-use-government-action-plan |title=Open source, open standards and re-use: government action plan |publisher=[[Government of the United Kingdom]] |date=27 January 2010 |deadurl=no<!--present in archive.com-->}}</ref>
   
* [[Belgium]]
+
|- style="vertical-align:top;"
* [[Croatia]]
+
|style="padding-right:1.0em;white-space:nowrap;"| South America
* [[Denmark]]
+
|class="hlist"|
* [[France]]
 
* [[Germany]]
 
* [[Hungary]]
 
* [[Italy]]
 
* [[Netherlands]]<ref>{{cite web|title=ODF 1.2 on Dutch "apply or explain" list|url=https://lijsten.forumstandaardisatie.nl/open-standaard/odf12}}</ref>
 
* [[Norway]]<ref name=NorwayDocumentStandard>{{cite web|title=New obligatory IT standards for the state sector adopted|url=http://www.regjeringen.no/en/dep/fad/press-centre/press-releases/2009/new-obligatory-it-standards-for-the-stat.html?id=570650|accessdate=19 December 2012}}</ref>
 
* [[Poland]]
 
* [[Portugal]]<ref>{{cite web|url=http://www.esop.pt/portugal-publishes-open-standards-catalogodf-pdf-and-several-other-standards-are-mandatory/ |title=ESOP » Portugal publishes open standards catalog. ODF, PDF and several other standards are mandatory |publisher=Esop.pt |date= |accessdate=2013-05-01}}</ref>
 
* [[Russia]]
 
* [[Serbia]]
 
* [[Slovakia]]
 
* [[Sweden]]
 
* [[Switzerland]]
 
* [[United Kingdom]]<ref>{{cite web | url=https://www.gov.uk/government/publications/open-source-open-standards-and-re-use-government-action-plan | title=Open source, open standards and re-use: government action plan | publisher=[[Government of the United Kingdom]] | date=27 January 2010 | deadurl=no<!-- present in archive,com-->}}</ref>
 
 
{{col-break}}
 
 
====South America====
 
 
* [[Brazil]]
 
* [[Brazil]]
* [[Uruguay]] <ref>{{cite web|url=http://www.agesic.gub.uy/innovaportal/file/497/1/estandares_ofimatica_v20.pdf |title=Estándares de ofimática |publisher=Agestic.gub.uy |date= |accessdate=2013-05-01}}</ref>
+
* [[Uruguay]]<ref>{{cite web |url=http://www.agesic.gub.uy/innovaportal/file/497/1/estandares_ofimatica_v20.pdf |title=Estándares de ofimática |publisher=Agestic.gub.uy |date= |accessdate=2013-05-01}}</ref>
 
* [[Venezuela]]
 
* [[Venezuela]]
   
===Subnational levels===
+
|- style="vertical-align:top;"
* [[Andalusia]] ([[Spain]])
+
!style="text-align:right;padding-right:1.5em;"| Subnational ||
* [[Assam]] ([[India]])
+
|class="hlist"|
* [[Extremadura]] ([[Spain]])
+
* [[Andalusia]], Spain
* [[Hong Kong]] ([[China]])
+
* [[Assam]], India
* [[Kerala]] ([[India]])
+
* [[Extremadura]], Spain
* [[Massachusetts]] ([[United States]])<ref>{{cite web|url=http://www.eweek.com/c/a/Linux-and-Open-Source/Massachusetts-Verdict-MS-Office-Formats-Out/|title=Massachusetts Verdict: MS Office Formats Out|date=24 September 2005|publisher=eWeek|accessdate=23 October 2012}}</ref>
+
* [[Hong Kong]], China
* [[Misiones]] ([[Argentina]])
+
* [[Kerala]], India
* [[Munich]] (Bavaria, [[Germany]])<ref>{{cite web | url=http://www.h-online.com/open/news/item/Munich-administration-switches-to-OpenDocument-Format-895415.html | title=Munich administration switches to OpenDocument Format | author=Stefan Krempl | date=5 January 2010 | quote="Open source OpenDocument Format (ODF) is now the main document exchange standard, with PDF being used for non-editable files."}}</ref>
+
* [[Massachusetts]], United States<ref>{{cite web |url=http://www.eweek.com/c/a/Linux-and-Open-Source/Massachusetts-Verdict-MS-Office-Formats-Out/|title=Massachusetts Verdict: MS Office Formats Out |date=24 September 2005 |publisher=eWeek |accessdate=23 October 2012}}</ref>
* [[Paraná (state)|Paraná]] ([[Brazil]])
+
* [[Misiones]], Argentina
+
* [[Munich]], Bavaria, Germany<ref>{{cite web |url=http://www.h-online.com/open/news/item/Munich-administration-switches-to-OpenDocument-Format-895415.html |title=Munich administration switches to OpenDocument Format |author=Stefan Krempl |date=5 January 2010 |quote="Open source OpenDocument Format (ODF) is now the main document exchange standard, with PDF being used for non-editable files."}}</ref>
{{col-end}}
+
* [[Paraná (state)|Paraná]], Brazil
  +
|}
   
 
==See also==
 
==See also==

by Sardanaphalus at October 11, 2014 06:08 PM

October 02, 2014

Google News

Samsung to Replace In-house Word Processing Software with Microsoft Word - BusinessKorea


Samsung to Replace In-house Word Processing Software with Microsoft Word
BusinessKorea
... even though the measure is aimed at adapting to globalization. The criticism is due to the fact that the decision is against a growing trend towards the Open Document Format for Office Applications (ODF) to reduce serious dependence on Microsoft ...

and more »

October 02, 2014 07:46 AM

September 28, 2014

ODF Wikipedia Page

Janvlug: /* Europe */

Europe

← Previous revision Revision as of 22:00, 28 September 2014
Line 255: Line 255:
 
* [[Hungary]]
 
* [[Hungary]]
 
* [[Italy]]
 
* [[Italy]]
* [[Netherlands]]
+
* [[Netherlands]]<ref>{{cite web|title=ODF 1.2 on Dutch "apply or explain" list|url=https://lijsten.forumstandaardisatie.nl/open-standaard/odf12}}</ref>
 
* [[Norway]]<ref name=NorwayDocumentStandard>{{cite web|title=New obligatory IT standards for the state sector adopted|url=http://www.regjeringen.no/en/dep/fad/press-centre/press-releases/2009/new-obligatory-it-standards-for-the-stat.html?id=570650|accessdate=19 December 2012}}</ref>
 
* [[Norway]]<ref name=NorwayDocumentStandard>{{cite web|title=New obligatory IT standards for the state sector adopted|url=http://www.regjeringen.no/en/dep/fad/press-centre/press-releases/2009/new-obligatory-it-standards-for-the-stat.html?id=570650|accessdate=19 December 2012}}</ref>
 
* [[Poland]]
 
* [[Poland]]

by Janvlug at September 28, 2014 10:00 PM

September 26, 2014

Google News

Komentář: Jinde to jde. Proč tedy ne u nás? - LinuxEXPRES


Komentář: Jinde to jde. Proč tedy ne u nás?
LinuxEXPRES
Například Velká Británie nedávno schválila využití formátu ODF (Open Document Format – mezinárodní standard ISO/IEC 26300) jako standardního formátu dokumentů ve veřejné správě. Bernský kanton ve Švýcarsku schválil zákon, podle něhož mají být ...

September 26, 2014 01:34 PM

Charles H. Schulz

Reuniting LibreOffice and AOO – a personal take

As we are approaching the 4th anniversary of the LibreOffice project in just a few days, an old theme has been reappearing on the Internet: Apache OpenOffice and LibreOffice should reunite. I would like to share my perceptions on this topic although I think it is not a really important one, at least as long as the LibreOffice or Apache OpenOffice do not officially call for such a reunion. Before I start, let me remind everyone that what follows is my own opinion and neither the one of the Document Foundation, nor the one of the Democratic Party, the one of my Government, nor, at last, the one of Bob’s Shipping and Handling Company.

I am obviously biased in my judgement; I’m even a party to this game. But I am also relatively well informed on these matters, and you may want to read Leif Lodahl’s excellent post for more background. Let me clarify first that reuniting the two projects is an inherently political concept that covers several questions. Among them, here are a few that need to be answered.

1. How would we reunite?

 When the LibreOffice project was announced, the project asked Oracle to join and transfer the brand ownership to the new project. That didn’t pan out well. Oracle waited some time before deciding they would license the brand to the Apache Software Foundation, alongside the code of OpenOffice.org itself. There’s one important word here: Oracle licensed these assets.

Credits: Senate of the State of Berlin

Credits: Senate of the State of Berlin

It did not give nor sell them to the ASF. The full ability to dispose of the brand name “OpenOffice” would be somewhat uncertain from the onset, and LibreOffice would then be the brand used. Even if that was not the case, how would it exactly work? Would we release the same software under two brands? Two distinct releases under two different names?

2. What would we reunite?

That’s where the licensing part comes in: The choice of license is probably one of the biggest technical hurdle to such a reunification. On the one hand the LibreOffice codebase can, thanks to its licenses, accept patches licensed under the Apache license, but the reverse is more difficult (although perhaps not absolutely impossible). This constrained flow of code would be decisive, in the scenario of a reunification, as it would lead to stop the licensing of any new patch under the Apache license while leaving the present licensing scheme of the Document Foundation intact. My educated guess is that I don’t see the Apache Software Foundation allowing that to happen .

3. Where would we reunite?

In other words: what repository? Where? Would we use the ASF’s SVN repository of the Document Foundation’s own infrastructure with Git as the version control system of choice? Perhaps a third party (existing or created ad-hoc) would be another option.LibreOffice_external_logo_200px

4. Who?

Who would be the parties deciding is another delicate matter. On one side, the Document Foundation is an obvious stakeholder. Depending on the kind of reunification (more on this below), there would likely be some areas of discussion that would be not even considered just because of the Statutes of the Document Foundation (a charity cannot just go ahead and give away its assets like that). Aside the Document Foundation and the Apache Software Foundation, Oracle would probably be at least a necessary party to the discussion; and obviously, IBM. I’m sure I forget a few… but judging by the table, the dinner would likely be a delicate matter to handle. Having said that, it is not entirely clear what would be the voice of the broader community: as it stands, the Document Foundation is the only entity here directly representing its members, who are individual contributors of the LibreOffice project. The ASF does that too, but Apache OpenOffice is but one tiny fraction of the whole ASF community.

5. What kind of reunification do we want?

Beyond the rather specific questions asked above, this question has broader implications, because this is one that points out the actual reason and meaning of an hypothetical unification of the two projects. Do we want a merge of equals into a new structure? Is it even possible? I have highlighted a few points above that suggest this scenario would be technically difficult. Do we want LibreOffice to merge into ASF and AOO ? Obviously I don’t, but the question has been asked before. Why would we do that? Is  it even possible?AOO4_website_logo Licensing differences suggest that the LibreOffice-specific contributions would need to be dumped. It would end up meaning that LibreOffice would dissolve into AOO and disappear with all the work done for naught, and given the difference in size between the two projects it would just be like an elephant trying to go through a doorlock.  Do we  want AOO to merge into LibreOffice? Licensing-wise it would be possible. Would ASF want that? I don’t know. The Document Foundation can, I think accomodate the project and its members. We have seen massive migration waves before. We can certainly integrate the AOO team. Ultimately, the contributors of each project would be the judges by voting with their feet. And that is not something the Document Foundation, Apache, Oracle nor IBM will ever control.

6. What is it we’re trying to achieve?

When members of the old OpenOffice.org project used to sometimes discuss the future of that project with the good folks at Sun Microsystems, they would often hear the same question thrown back at them: “Tell us why a foundation for OpenOffice.org would help fix the project’s issues”. Invariably, any point that was raised in favour of a foundation was brushed away by providing whatever solution that did not involve the existence of an independent foundation. It used to illustrate perfectly the difference between real outcomes and the foreseen results based on a rational argumentation: the two don’t necessarily match. With a strange twist of irony, I must now ask the same question: “Why would the reunification help fix any of these projects’ issues?” I will quickly list here areas of concerns and topics that are usually pointed as reasons to unite the two office suites:

  • common branding / stronger brand value
  • everybody can now contribute to the same code base (yeaah!)
  • there’s no point in having two similar office suites
  • no more interoperability issues

The stronger brand value used to be a very good argument, perhaps even the best one, in 2010 and 2011. I started this post by highlighting that the LibreOffice project’s founders had actively sought Oracle’s consent to use OpenOffice for the new project. Now, we’re barely 72 hours away from the LibreOffice project’s fourth birthday. The project is doing well. There’s still much to do, but it has exceeded what many used to imagine would be possible. While the LibreOffice brand started from zero in 2010 and 2011, things have changed. Obviously, OpenOffice has a more known brand, as it capitalizes on 10 years of existence of its old project; I’m sorry to say that Apache OpenOffice has little merit in this achievement aside its very existence. But LibreOffice as a brand is now established and its brand value is growing pretty much everywhere. To destroy any one of these two brands all of a sudden would thus bear some painful consequences, although it may well happen in the end. Do we want this? Does anyone have an actual, sustainable and actionable plan for a brand transition? I have not heard of anything of that kind.

The fact that a common project could now contribute to the same codebase, thus making a “better and stronger” office suite is somewhat moot. LibreOffice took whatever it wanted from Apache OpenOffice through the licensing specifics of the two suites; but in sheer contributions, Apache OpenOffice has now little to offer to LibreOffice. Besides, the two contributors’ pools are so different in size that the addition of AOO developers would not be really meaningful to LibreOffice while if the reverse was true, things would be very interesting. However, it means that here again we pretend to play with contributors like we’re measuring army regiments. Community members come and go as they please, and a reunification is not something everyone is necessarily looking forward to.

There is indeed little value in having two similar office suites, although it is a fundamental expression of software freedom, and that alone should be enough. We also have something like 150 Linux distributions and if we really look around and apply this way of thinking,  we may want to merge with Calligra, Abiword and Gnumeric. That too, makes absolutely no sense. Remember, however, that neither AOO nor LibreOffice actually want to be “similar”, and despite a popular perception, they are growing rather different each quarter. The same can be said of Calligra, a project that runs on a very different code base. In a nutshell, clones may not make much sense, but choice is good especially if the choice involves real differences. There are now real differences between AOO and LibreOffice, in terms of features, of file format support, in terms of ecosystem and engineering processes as well. The choice between these two suites is becoming clearer as time goes by.  We shouldn’t forget that when we picture anything like a competition between Free and proprietary software, we are not implying that there should be only one option on either side.

Last but not least, interoperability issues have been mentioned by several well informed parties as being a problem and ultimately a hindrance to the adoption of Open Standards such as ODF. While this is a rather complex issue, it is also not a blindingly critical one, in the sense that the issues that can be met tend to arise in specific environments. These usually involve a userbase using OpenOffice.org or AOO together with LibreOffice and documents that have already been migrated to ODF. Growing differences in implementations invariably lead to visible differences in the presentations of documents (although there is no data loss) and therefore generate frustration and users’ discomfort. The only possible solution to these hurdles (aside a careful and diligent migration expert leading the ball) is to have AOO and LibreOffice cooperate on specific interoperability issues. But make no mistake: anyone else who would use Microsoft Office or Calligra with ODF documents would ultimately create its own incompatibilities. The actual scope of the problem is thus broader and has been expected for several years now; this is just not a mere AOO-LibreOffice  issue. A merger would solve this in the long term, but would still force some users to abandon one implementation for another.

Before I finish this very long post, let me just point out that when all is said and done on this topic, it really boils down to the actual will and intent of the stakeholders. It might seem unsavory for me to point this out, but to this day I still haven’t found any real reason for Apache OpenOffice to even exist. It does not mean that I hold this project’s members as idiots or incompetents, far from that. But if we talk about reunification, then it brings back the original question to the table: While we know why LibreOffice and the Document Foundation were created, we know of no real reason why Apache OpenOffice was started, aside one corporate will to license its own assets to a third party it is familiar with. So if the two projects were to reunite, one must pay close attention at the actual meaning of this movement and listen to the actual projects’ contributors. When Software Freedom is involved there is no point in bypassing the community.

by Charles at September 26, 2014 09:27 AM

Google News

Aprire i formati della PA - Apogeo Online


Aprire i formati della PA
Apogeo Online
FixMyDocuments.eu si pone l'obiettivo di aiutare le amministrazioni pubbliche europee che hanno deciso di sostenere gli ODF a implementare la loro scelta, documentando, registrando e segnalando online la loro conformità. ... Grazie a questa iniziativa ...

September 26, 2014 04:49 AM

September 25, 2014

Planet KDE

2.8.6 → 2.9 → 3.0 → ...

That was my first Akademy after a while, I've been following previous two with kids on my lap. I think Brno turned out to be both a pretty destination and decent host for all KDErs.
A new Kexi contributor Wojtek Kosowicz came with me. You can read about him here and his recent story here. Recently in Kexi there is a trend of new contributors coming from Poland, and specifically from Warsaw. I've heard they're a bit regretting afterwards they didn't join the Akademy too but I trust that will improve next year :)

I met many great old KDE friends. I had good time chatting with openSUSE's Bruno Friedmann, unbelievably dedicated to both the distro and KDE. I met the stars of the KDE Visual Design Group. Consumed a few quarters of time of Timothée Giet, well known Calligra and KDE contributor. Thanks for all inspirations! I mention these meetings as design has always been my special interest.

Kexi BoF on early Monday, unfortunately my last day, was filled with clearing up ambiguities of Kexi's feature set and approach to creation of custom apps (yes, Kexi's destiny is to act as complete run-time and design tool for apps). Friedrich Kossebau, who helps with Kexi/Calligra a lot, largely contributed to this meeting. The BoF as and extended with always reliable Kevin Krammer and other friends.

What are the KDE's products?
That was a topic that circulated in the air and i suppose many contributors took it back to their homes. From my user-oriented optics gained over years, KDE produces apps and development frameworks, period. Give this optics, Plasma is an app, that people could freely install and remove these days, without doing too much harm to their app experience.

People mix apps that fit best to their workflow given they have freedom to do so, many of us never close the browser, and never sign out of some services. Frameworks help with making the KDE apps easier to pick individually, to get even more "native" feeling on other environments, it's not enough to say it once :) Now times of Internet Explorer dragging everything (including Silverlight, three Java versions and Flash) with it to your home shall be over. It's enough that current browsers are fat, they are almost like a separate OS environments within your native OS.

Here, someone could even say the KDE Frameworks is a byproduct... but a great one.

2.8.6, 2.9, 3.0 and beyond
Yesterday Kexi 2.8.6 has been released within Calligra. Click the link for a list of changes, and a mention of pretty unusual addition to Kexi - it proposes direct donations on its Welcome screen. It turned out to be convenient and hopefully not too annoying given what the benefits might be. It's best explained by the screen shot.

 

 

By direct we mean that users can actually pick features they badly want "ASAP". There are various approaches. The Kexi's donation page features example list of issues to give some idea about budget estimations. An example (never announced) fundraising has been also published to give the idea to users that they are in control how these things would work, what types of features could get implemented or improved. (Krita has a donation link too since some time)

We in the team are clearly happy with the number of fixes that appeared in 2.8.6. Now we're on the good way to the 2.9 series, the flow of commits has started already. A few new features are possible until the December release, one of them is a structure tree for Reports. Qt 5 and KDE Frameworks 5-based version of Kexi will be called 3.0, and its development is expected to happen in parallel with 2.9 development and maintenance, so it all starts now to meet the "early 2015" deadline. I plan to share major news from this front on this blog.

 

CC BY 2.0 pcambra

by Jarosław Staniek (jstaniek) at September 25, 2014 08:56 AM

September 24, 2014

Planet KDE

Calligra 2.8.6 Released

We are pleased to announce that Calligra
Calligra Suite, and Calligra Active
2.8.6 have just been released. This last recommended update brings over 60 improvements to the 2.8 series of the applications and underlying development frameworks.

We are also glad to note that this release contains first contributions from Kamil Łysik, Michał Poteralski, and further improvements from the new contributor Wojciech Kosowicz. All for Kexi. Welcome on board!

What’s Next and How to Help?

Now we’re focusing on 2.9 series planned to debut in December this year and the new shiny 3.0 for 2015. You can meet us to share your thoughts or offer your support on general Calligra forums or dedicated Kexi or Krita forums. Many improvements are only possible thanks to the fact that we’re working together within the awesome community.

(if you’d like to maintain entire app, Karbon and Plan need new maintainers)

Calligra apps may be totally free, but their development is costly. Power, hardware, office space, internet access, traveling for meetings – everything costs. Direct donation is the easiest and fastest way to efficiently support your favourite applications. Everyone, regardless of any degree of involvement can do so. You can choose to:

Issues Fixed in This Release

General

  • Make rulers accept minimum length equal to zero. (bug 334968)
  • Fix a crash while copy/pasting (bug 334832)
  • Set the docker’s small font also on tool option panels for consistency.
  • Use the list of available file types when setting the file filter for picture shape. (bug 327782)
  • Put the New view action back to the View menu.
  • Prevent backtracking to undo the layout of a whole page, thus starting an infinite loop. This can be triggered by a page break in the middle of keepWithNext paragraphs. (bug 306000)

Kexi

  • Fix logic behind visibility of editing indicator in tabular and form views
  • Make Next and Last button in Page selector of Report data view to be disabled on last page.
  • Fix build error on OpenBSD operating system (missing include directory for ICU).
  • Fix row selection/highlighting when clicking/hovering over record marker. (bug 337914)
  • Fix an issue with resolving version of plugins (at least) on Linux.
  • Improve behaviour of tabbed toolbar when Design Tab is present.
  • Avoid displaying actions for parts that do not create objects.
  • Set labels to right in the Find dialog.
  • Fix a crash when pressed Tab on a form with one date picker. (bug 338766)
  • Avoid crashes when closing Kexi views.
  • Allow to create report items of specific size using mouse drag. (bug 334967)
  • Fix crash in Report designer.
  • Fix possible crash on opening report with a barcode element.
  • Fix icon alignment in Kexi record navigator buttons.
  • Add running desktop name and version to the feedback agent. Recognizes Plasma 4 and 5 at least.
  • Position pasted report element with an offset to the active element or to the corner. (bug 334967)
  • Add donations info to Kexi’s status bar. Currently only opens a BountySource page.
  • Improve experience by adding a dedicated database password dialog.
  • Avoid keeping potentially wrong password entered in the password dialog. We don’t want to re-use it.
  • Improve default size of modal assistant dialogs.
  • Hide system PostgreSQL (postgres) and MySQL (performance_schema) databases from the visible database list.
  • Use consistent sorting of unicode text values. (bug 338808)
  • Fix background opacity handling and new background/foreground’s defaults for report elements.
  • Many fixes for Kexi’s Database Import assistant (bugs 336556, 336557, 336558):
    • When needed ask for password to access source or destination servers.
    • Reload source database list if user pressed back and selected different connection.
    • Improve saving recent directories.
    • Do not ask twice about destination filename.
    • In addition to title, properly ask for database name for server destination databases.
    • Properly open imported database (file).

Krita

  • Fix bug that randomly disables tablet support.
  • Fix a crash with the latest evdev tablet drier.
  • Fix recognition of the Wacom stylus’ serial ID.
  • Add an option to disable touch capabilities of Wacom tablets. If you want to use it, please add the following option to your kritarc configuration file: disableTouchOnCanvas=true. (bug 332773)
  • Make rotation on Linux be consistent with rotation on Windows. (bug 331358)
  • Fix tablet stylus rotation on Linux.
  • Improve performance of the OpenGL canvas, it’s twice faster now.
  • Reduce memory consumption when textures are updated.
  • Fix a crash in Channels docker when the image is closed.
  • Fix a crash when the number of patches that fits in a column is zero.
  • Use period key instead of non-standard stop key for the "Select previous favourite preset" command. (bug 331105)
  • Fix moving of shapes in groups in shape layers. (bug 308942)
  • Set focus to layer name text input in layer properties dialog.
  • Fix the HSV options bug. (bug 313494)
  • Round the corner point position of the rectangle base tool, otherwise there is some odd jumping. (bug 335144)
  • Fix Erase composite operation to handle the selections properly.
  • Fix the Blur filter when Y>X. (bug 336914)
  • Fix a crash after selecting Layer array clones more than a couple times. (bug 336804)
  • Don’t crash when trying to Ctrl-Alt pick a color from a group layer.
  • Don’t show icons in the menus on Windows.
  • Fix anisotropy in Color Smudge brush engine (offset calculation). (bug 334538)
  • Fix Lens Blur filter artifacts when used as an Adjustment Layer. (bug 336470)
  • Fix a hang-up when opening the filter dialog twice or running any stroke-based action while having the dialog open. (bug 334982)
  • Fix misbehavior of the Brush tool when selected on a vector layer. (bug 335660)
  • Fix saving 16 bit grayscale images to tiff, jpeg and ppm. (bug 338478)

Calligra Stage

  • Let Ctrl+Home and Ctrl+End keys go to top and bottom of text shape in stage.
  • Allow to exit text-edit mode by pressing Escape.

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 September 24, 2014 04:38 PM

September 18, 2014

Google News

한글 프로그램 없어도 민원신청 OK - 대한민국정책포털 korea.kr


대한민국정책포털 korea.kr

한글 프로그램 없어도 민원신청 OK
대한민국정책포털 korea.kr
정부는 국민들이 민원실에 많이 제출하는 민원신청서와 공직에 지원하는 민간 전문가가 작성하는 개방형직위 응시원서에 대해 HWP 파일과 함께 '개방형 문서' 서식(open document format, ODF) 파일도 제공하기로 했다. ODF는 파일문서의 구조가 완전히 개방돼 ...

September 18, 2014 07:46 AM

September 17, 2014

An Antic Disposition

ISO/IEC JTC1 Approves ODF 1.2 PAS Ballot

OASIS ODF 1.2, the current version of the Open Document Format standard, was approved by ISO/IEC JTC1 National Bodies after a 3-month Publicly Available Specification (PAS) ballot.  The final vote for DIS 26300 was:  17-0 for Parts 1 and 2, and 18-0 for Part 3.

Of course, this is a very good result and all those involved, whether TC members and staff at OASIS, implementors, adopters and promoters of ODF and open standards in general should be pleased and proud of this accomplishment.

This was a team effort, obviously, and I’d like to give special thanks to Patrick Durusau  and Chris Rae on the ODF TC for their special efforts preparing the PAS submission for ballot, Jamie Clark from OASIS for putting together the submission package and Francis Cave, Alex Brown, Murata Mokoto and Keld Simonsen in JTC1/SC34/WG6 for their continued advice, feedback and support.

Since comments were received by Japan and the UK,  we now start the comment disposition process.  The SC34 Secretariat will determine whether a Ballot Resolution Meeting (BRM) is required, or whether the comments can simply be handed to the Project Editor for application to the specification prior to publication.   One way or another, there will be a little more work before publication of the ODF 1.2 International Standard.

The OASIS ODF TC continues work on ODF 1.3, with renewed vigor.  After nearly a decade of involvement with ODF, and many years leading the committee, I’ve stepped down.   The TC has elected Oliver-Rainer Wittmann, a long-time TC member, ODF implementor and a familiar face at ODF Plugfests, to take over.   I’m currently exploring other areas related to open innovation (open standards, open source, open data, open APIs).  If you know of anything interesting, send me a note.

 

by Rob at September 17, 2014 03:22 PM

Google News

Open document formats campaign backed by EU's digital commissioner - ITworld.com


Open document formats campaign backed by EU's digital commissioner
ITworld.com
The campaign's website invites reports about public administrations that have pledged support for Open Document Format (ODF) files but then don't recognize the files, which typically have a .odt, .ods or .odp extension. If an administration has ...

and more »

September 17, 2014 12:32 PM

Open document formats campaign backed by EU's digital commissioner - Techworld.com


Open document formats campaign backed by EU's digital commissioner
Techworld.com
The campaign's website invites reports about public administrations that have pledged support for Open Document Format (ODF) files but then don't recognize the files, which typically have a .odt, .ods or .odp extension. If an administration has ...

and more »

September 17, 2014 12:16 PM

Open document formats campaign backed by EU's digital commissioner - Australian Techworld


Open document formats campaign backed by EU's digital commissioner
Australian Techworld
The campaign's website invites reports about public administrations that have pledged support for Open Document Format (ODF) files but then don't recognize the files, which typically have a .odt, .ods or .odp extension. If an administration has ...

and more »

September 17, 2014 12:16 PM

Open document formats campaign backed by EU's digital commissioner - Computerworld Australia


Open document formats campaign backed by EU's digital commissioner
Computerworld Australia
The campaign's website invites reports about public administrations that have pledged support for Open Document Format (ODF) files but then don't recognize the files, which typically have a .odt, .ods or .odp extension. If an administration has ...

and more »

September 17, 2014 12:12 PM

Open document formats campaign backed by EU's digital commissioner - CIO


Open document formats campaign backed by EU's digital commissioner
CIO
The campaign's website invites reports about public administrations that have pledged support for Open Document Format (ODF) files but then don't recognize the files, which typically have a .odt, .ods or .odp extension. If an administration has ...

and more »

September 17, 2014 12:08 PM

Open document formats campaign backed by EU's digital commissioner - PC World Magazine


Open document formats campaign backed by EU's digital commissioner
PC World Magazine
The campaign's website invites reports about public administrations that have pledged support for Open Document Format (ODF) files but then don't recognize the files, which typically have a .odt, .ods or .odp extension. If an administration has ...

and more »

September 17, 2014 12:06 PM

Open document formats campaign backed by EU's digital commissioner - PC World Magazine


Open document formats campaign backed by EU's digital commissioner
PC World Magazine
The campaign's website invites reports about public administrations that have pledged support for Open Document Format (ODF) files but then don't recognize the files, which typically have a .odt, .ods or .odp extension. If an administration has ...

September 17, 2014 12:06 PM

Open document formats campaign backed by EU's digital commissioner - CIO Magazine


Open document formats campaign backed by EU's digital commissioner
CIO Magazine
The campaign's website invites reports about public administrations that have pledged support for Open Document Format (ODF) files but then don't recognize the files, which typically have a .odt, .ods or .odp extension. If an administration has ...

and more »

September 17, 2014 12:03 PM

WebODF news

WebODF 0.5.4 released, undoing two regressions slipped into 0.5.3

Just 24 hours passed since the release of WebODF 0.5.3 and there has to be another, fixing regressions once we learned about them.

So go to the Download page and update your deployment of webodf.js or the Wodo.TextEditor. Or check the demos.

September 17, 2014 12:00 AM

September 16, 2014

WebODF news

WebODF 0.5.3 released, bringing another round of improvements and fixes

The latest version of WebODF brings improvements in the rendering of text styled as subscript or superscript, fixes positioning of the IME composition menu & avatar when entering characters, and more.

So go to the Download page and update your deployment of webodf.js or the Wodo.TextEditor. Or check the demos.

September 16, 2014 12:00 AM

September 15, 2014

Google News

FixMyDocument and Global Legislative Openness - ComputerworldUK (blog)


FixMyDocument and Global Legislative Openness
ComputerworldUK (blog)
Back in July, I wrote about the huge win for open standards when the UK government announced that it would be adopting ODF for sharing or collaborating on government documents. I also implored the open community to support this initiative in every way ...

September 15, 2014 02:22 PM

LibreOffice speichert im Word-Format - Lampertheimer Zeitung


Lampertheimer Zeitung

LibreOffice speichert im Word-Format
Lampertheimer Zeitung
Zum anderen ist in LibreOffice das Standard-Dateiformat zum Speichern auf ODF eingestellt, das LibreOffice-eigene Format. Das verursacht bei Microsoft-Office-Nutzern manchmal Probleme, wenn die neusten Filter nicht installiert sind. Doch das lässt sich ...

and more »

September 15, 2014 12:52 PM

September 14, 2014

Charles H. Schulz

Marketing Strategy Workshop 2014: More engagement, better conversations

Last week we had a great LiboCon 2014 in Bern, organized by a great team and a great (and often not known well enough) city. We had what has become some sort of tradition, by which I mean the Libreoffice Marketing Strategy Workshop. This year was a bit special however in that the workshop itself came after a series of other workshops dedicated to media training and messaging by Italo Vignoli and another session aimed at helping non-native English speakers promote LibreOffice in their language. All these sessions did prepare the audience to the strategy workshop but were also a very nice addition to it. I was also happy to notice a stronger attendance than previous years to the workshop, as well as a more diverse one that included at the same time active contributors, contributors of native-language projects, and “simple” visitors of the conference. Some of them actively contributed to the session, and I found that to be very useful.

While there was no shakedown of the marketing strategy this year, there was however a strong focus on online campaigning and volunteers’engagement methods. It was also a good opportunity to let everyone share ideas and experiences. Below are the main discussion points of the workshop. You may download the slides supporting the workshop directly here.

Achievements

This year we had several notable successes, despite remaining a project with a small marketing team. First, our new website has been one of our most visible achievements and has been in most cases very well received. LibreOffice needed a more visually appealing website, and there was an interesting discussion as to how we were conveying the idea of what LibreOffice is, both as a software and as a project. We will come back to that in the latter part of the post.

Second, there is a real momentum around LibreOffice on social networks, with the presence on each online service acting like a specific channel for a certain type of activity and conversations. For instance, Facebook is our the network with our biggest outreach, yet it is probably the most passive one, with very few conversations taking place. The volume of the audience however makes it worth maintaining an active presence there. On Twitter we have two accounts, @tdforg and @libreoffice . We started tweeting irregularly through @tdforg and got lots of success for three years; but we had kept @libreoffice under wraps. Starting in 2014, we started to differentiate between @tdforg being more about official announcements, and @libreoffice tweeting several times a day. In both cases we reached several thousands of subscribers and are engaging in (short) conversations with users on a regular basis. Google + is also a big success and a quite interesting one. Here again, we have several thousands of followers but what’s really interesting is that it is a place where people discuss topics and post new ones. Users support is also happening sometimes there.

Reddit was a modest (several dozens of members) channel for us and has now grown to several hundreds so it’s definitely something to keep an eye on.

All this work described above has led to one specific and recurring objective: Increasing LibreOffice’s brand awareness and growing our contributor’s base. We still have lots of work to do, and we had a discussion about the results of the LibreOffice ad in the german special edition of Die Zeit. We realized that should we decide to go for these traditional ads, we would need to have a more comprehensive campaign with an actual story line in order to yield measurable results.

Another set of achievements has been the real improvements in how the communications on the LibreOffice releases are handled  throughout the community. Thanks to a clearer and more inclusive process, the LibreOffice native-language teams have the time to localize the release and announce it by translating the press release in due time. This is no little effort when you consider the work put into the localization, the quality assurance on the various betas and release candidates, and the translation of the PR itself. Last but not least, and before we skip to the other parts of the workshop, this year was also a successful year in terms of articles written about LibreOffice and the Document Foundation. This also helps us increase the brand awareness and help us grow our userbase and our community.

Challenges & Solutions

Despite our achievements, our marketing team remains small (around 4 individuals contributing on a non permanent basis, sometimes daily, sometimes weekly). The discussion this year suggested that we put more effort into contributor’s engagement and while this used to be somewhat of a tricky question, I think we now have enough hindsight to make it work. In order to understand the situation one needs to take a step back and consider the following.

When the LibreOffice project was created it was one of the best opportunities to start afresh in the way the community and how each of us contributes to the project was valued. As a result, it was decided that a strong meritocracy would be instrumental in improving the low rate of contributions of the former OpenOffice.org project in a substantial way. It worked and still works really well for most of the project, but marketing or promotion did not overly benefit from that. Of course, it helped us gain time and stop wasting energy dealing with distractions such as endless (and pointless) discussions on “product marketing mixes” and so on. Yet it did not help us multiply our base of marketing contributors. The principle, which remains the same, that in order to be acknoledged by the community you must first contribute something to it, did not, however, handle too well the kind of contributors who would be happy just with little things, such as badges. While developers tend to not pay any kind of importance to these details, we also had to deal with the fine line between handing someone a badge and some sort of formal role, and giving a title to someone just because he or she would have asked for it. A title in itself is little, and probably nothing. Yet our experience with OpenOffice.org showed that it was very easy to have titles, and even easier to do nothing to earn it. Thus, anything that had to do with badges was viewed with skepticism, if not prejudice.

This year, we are going to start improving the quality of our contributors’ engagement with the project at least in non-technical areas. A badge does not imply any sort of hierarchy, or formal role. It does not replace the membership to the Document Foundation. It is just what it is, a badge.

At the same time, we would like to drive the same experiment than the one our Design and UX team had a few months ago: a full migration to the RedMine platform hosted on the project’s infrastructure. While we may stick to a few of our existing tools (the existing wiki), RedMine essentially turns your team’s activity into a project and tasks’ based workflow, while eliminating much of the noise. The discussion, because of the tools, are directly related to tasks, and tasks behave pretty much like issues opened in a bug tracker.

We had an interesting discussion about the need to engage in communication campaigns that tie in to specific news or moments. We should be able to “join the conversation”, when one of our competitors claim something we can talk about as well. These campaigns would definitely help us raise our brand awareness too. This will also require that the marketing team starts working on its own banners and online material without necessarily hogging the resources of the Design team.

Last but not least, we have experimented with something called LOWN (LibreOffice Weekly Newsletter), thanks to William Gathoye. This newsletter is not really meant for people outside our community. On the contrary it is designed for community members, who want to stay in touch with all corners of the project and learning about what’s going on in other teams. We may want to make it a montly newsletter, but it is encouraging to see this becoming a community based effort.

As a conclusion to this very long post, I would like to thank everyone who joined the workshop this year, it was a great moment of sharing and I think it will help us moving forward for next twelve months, be a better community and a more efficient project.

by Charles at September 14, 2014 09:27 AM

September 12, 2014

Google News

LibreOffice speichert im Word-Format - General-Anzeiger


General-Anzeiger

LibreOffice speichert im Word-Format
General-Anzeiger
Zum anderen ist in LibreOffice das Standard-Dateiformat zum Speichern auf ODF eingestellt, das LibreOffice-eigene Format. Das verursacht bei Microsoft-Office-Nutzern manchmal Probleme, wenn die neusten Filter nicht installiert sind. Doch das lässt sich ...

and more »

September 12, 2014 12:24 PM

LibreOffice speichert im Word-Format - Kreis-Anzeiger


Kreis-Anzeiger

LibreOffice speichert im Word-Format
Kreis-Anzeiger
Zum anderen ist in LibreOffice das Standard-Dateiformat zum Speichern auf ODF eingestellt, das LibreOffice-eigene Format. Das verursacht bei Microsoft-Office-Nutzern manchmal Probleme, wenn die neusten Filter nicht installiert sind. Doch das lässt sich ...

and more »

September 12, 2014 08:43 AM

Computer: OpenOffice speichert im Word-Format - FOCUS Online


FOCUS Online

Computer: OpenOffice speichert im Word-Format
FOCUS Online
Zum anderen ist in OpenOffice das Standard-Dateiformat zum Speichern auf ODF eingestellt, das OpenOffice-eigene Format. Das verursacht bei Microsoft-Office-Nutzern manchmal Probleme, wenn die neusten Filter nicht installiert sind. Doch das lässt sich ...

and more »

September 12, 2014 07:29 AM

Computer: OpenOffice speichert im Word-Format - Augsburger Allgemeine


Augsburger Allgemeine

Computer: OpenOffice speichert im Word-Format
Augsburger Allgemeine
In der Rubrik «Einstellungen für Standard-Dateiformat und ODF» bei der Option «Immer speichern als» die Einstellung «Microsoft Word 2007/2010/2013 XML» auswählen. Bestätigen, indem unten auf «OK» geklickt wird. Das bedeutet allerdings nicht, dass ...
OpenOffice speichert im Word-FormatAlzeyer Anzeiger

all 7 news articles »

September 12, 2014 07:24 AM

Computer: LibreOffice speichert im Word-Format - Augsburger Allgemeine


Augsburger Allgemeine

Computer: LibreOffice speichert im Word-Format
Augsburger Allgemeine
In der Rubrik «Einstellungen für Standard-Dateiformat und ODF» bei der Option «Immer speichern als» die Einstellung «Microsoft Word 2007/2010/2013 XML» auswählen. Bestätigen, indem unten auf «OK» geklickt wird. Das bedeutet allerdings nicht, dass ...
LibreOffice speichert im Word-FormatGeneral-Anzeiger

all 16 news articles »

September 12, 2014 07:24 AM

September 10, 2014

Google News

Стандартът ODF и офис пакетът LibreOffice - Personal Computer World


Стандартът ODF и офис пакетът LibreOffice
Personal Computer World
ODF (Open Document Format) Ако още не знаете, ODF (Open Document Format) представлява свободен стандарт за офис документи и съхранение на данни. Това е отворена иновативна технология за свободен файлов стандарт, който се ...

September 10, 2014 08:07 AM

September 09, 2014

Google News

Worlds' First Olympic Games Cricket scoring system developed in New Zealand - Scoop.co.nz (press release)


Worlds' First Olympic Games Cricket scoring system developed in New Zealand
Scoop.co.nz (press release)
This requires that all 44 Asian Games Federation sports output real time Olympic Data Format (ODF) information to websites, all forms of media, television graphics and results books with an identical “look and feel” format. Signopsys software will ...

and more »

September 09, 2014 03:11 AM

Worlds' First Olympic Cricket scoring system developed in NZ - Scoop.co.nz (press release)


Worlds' First Olympic Cricket scoring system developed in NZ
Scoop.co.nz (press release)
This requires that all 44 Asian Games Federation sports output real time Olympic Data Format (ODF) information to websites, all forms of media, television graphics and results books with an identical “look and feel” format. Signopsys software will ...

and more »

September 09, 2014 02:47 AM

September 08, 2014

Google News

Worlds' First Olympic Games Cricket scoring system developed in New Zealand - Scoop.co.nz (press release)


Worlds' First Olympic Games Cricket scoring system developed in New Zealand
Scoop.co.nz (press release)
This requires that all 44 Asian Games Federation sports output real time Olympic Data Format (ODF) information to websites, all forms of media, television graphics and results books with an identical “look and feel” format. Signopsys software will ...

and more »

September 08, 2014 11:19 PM

Worlds First Olympic Cricket scoring system developed in NZ - Scoop.co.nz (press release)


Worlds First Olympic Cricket scoring system developed in NZ
Scoop.co.nz (press release)
This requires that all 44 Asian Games Federation sports output real time Olympic Data Format (ODF) information to websites, all forms of media, television graphics and results books with an identical “look and feel” format. Signopsys software will ...

and more »

September 08, 2014 09:44 PM

Olympic Games cricket scoring system developed in NZ - Voxy


Olympic Games cricket scoring system developed in NZ
Voxy
This requires that all 44 Asian Games Federation sports output real time Olympic Data Format (ODF) information to websites, all forms of media, television graphics and results books with an identical "look and feel" format. Signopsys software will ...

and more »

September 08, 2014 08:13 PM

LibreOffice 4.3, First Take: Still desktop-bound - ZDNet


LibreOffice 4.3, First Take: Still desktop-bound
ZDNet
LibreOffice continues to warn you that documents you save in the Office formats may not retain all their contents, but using its own ODF format doesn't preserve compatibility either — images in a document we saved as ODT darkened to the point of ...

September 08, 2014 11:04 AM

September 05, 2014

Planet KDE

Workspace-wide services on non-file objects

As a user…

Have you ever copied some text from e.g. Okular, KMail or LibreOffice to Plasma KRunner, to invoke some service on it, ideally based on auto-recognition of the data? And wished, you could just have already got in the context menu on the selected text the respective service you were going for?
Or have looked in the context menu of an image in a PDF, a website in Firefox or a database in Kexi and wondered why the context menu does not show at least the “Send to” services from the Kipi plugins?

As a developer…

Have you ever written a parser for plain text which detects certain things like urls or telephone numbers, then tags those text parts, to be able to highlight them and to offer certain actions on them? Only to find out that other programs are better in detection, for more things, and offer more or other services on those, at least that other program in its new release when you just aligned yours with their old?

If so, then we share some frustration. And an itch to scratch :)

Workspace-wide services on non-file objects

So what I would like to propose and do is a workspace-wide service system. Actually two.

The first system would make potentially all services on objects available everywhere, based on the mimetypes the program can support on export (e.g. the ones it would offer for the object to the clipboard on copy). It would also allow 3rd-parties to add new services without touching any existing programs.

The second system would make all object recognition logic available to all programs. And be extendable by 3rd-party as well without touching existing programs.

Because, why only deal with objects in the filesystem (blobs of bytes commonly called “files” ;) ) in a generic way? Why not also with objects in the composed object structures the programs have made up at runtime in the working memory and which the user can clearly address as objects in the UI?

Of course this needs to be properly done, so we do not end up with crowdy and surely improvable menus (e.g. like IMHO the “Send to…” menu in KSnapshot). For that I am happy that in the next days at Akademy the good people from the Visual Design Group are willing to offer their input on what people come to them with… you will find me queueing up for them :)

Because…
I'm going to Akademy

Data recognition system

Often data is not completely enriched with all possible semantics, there is a final enrichment done only by a human looking at the presentation of the data. E.g.

  • items in a picture (like a cat, a flower or a QR code)
  • items in some plain text (like a phone number or the name of a person)
  • items in some partially enriched text (like an email address in a comment in source code)

Or think about items in a sound, while not that typically presented in spatial way on a screen, still there is data recognition going on there as well, like a spoken word, barking or a speaker (or a dog, if you are into dogs :) ).

Some programs have some hardcoded data recognition system, e.g. Digikam for faces of humans, Konsole for urls in console output, KMail for urls and email addresses. Their code is not shared with other programs, everyone would have to reimplement it. Kate and Okteta would have to write their own url detection code, even Rekonq, Okular and Calligra, for text not yet marked-up as url. And Gwenview will have to do its own thing for face detection.

So I imagine a set of globally installed data recognition plugins which can be called on some given data and would report where they detected which objects. They would also mark objects with a state, like just a guess or sure thing, and if there is one or multiple options for the semantic (e.g. for non-unique names of contacts matched in the addressbook).

For text, here a list of things that could be detected in plain text and where you surely can imagine some services on: geocoordinates, date, time, phone number, url, email address, irc/chat nickname, irc channel, name of person, calculation, currency amount, value with physical unit, RGB value, abbreviation, identifying names of objects (like cities, countries, buildings, satellites), program name, you-name-it…

For many of these there are already recognition parsers in Plasma KRunners (even for geocoordinates with the Marble Plasma Runner). Time to share them with the whole system!

Services system

Many of the services I think of are those you can already find offered by the Plasma KRunners: doing some action based on some data provided.
Now the system should be able more than that, I would like to have these four kind of service types:
* action based on data (read-only with regard to the original data)
* manipulating action based on data (data returning a substitute for the original data)
* action based on data combined with other data (e.g. triggered by drag’n’drop)
* manipulating action based on data combined with other data

When querying for services, the possible mimetypes of the data should be passed (like with clipboard). For some of the mentioned things above this will mean newly invented mimetypes (e.g. for irc nickname or value with physical unit), but this seems okay. Some services will want to inspect the actual data to see if they do support something. Also will context & some metadata information (like the container) be helpful as well (e.g. for a translation service). Some services are cheap/okay to be queried for support/run as often as wanted, some are not (e.g. public web services run by private). Some services can be data-risky (do profiling by the seen data or risk lacking private info). All that should be accounted for in some way.

Some semantics of the services will be needed, to assist in presentation in the UI (e.g. “send copy of data somewhere”, “show info about data”, etc.)

Programs would install context files, which could be used to configure when to offer which services (done by whitelist/blacklist of services). The UI should offer typically used services in quickly accessible/discoverable ways (like direct items in the context menu).

Perhaps there is even a fifth kind of service possible, something that feeds the tooltip or some infobox with data about the object (like a business card for person from addressbook or a map for a location).

All this should allow services like “Offer translation”, “Alternative word proposal”, “Correction proposals”, “Look up in Wikipedia/knowledge db and show mini info card”, “do calculation” (on data of type formular-data), “Convert to other unit” (on data of type value with unit), “Start program”, “Open file”, “Show color”, “Look for offers in internet shop”, you-get-the-idea.

This service system might be similar to something done in NeXTSTEP, at least I remember having read about that one day. And Android also possibly features something similar, from what I understood. If have you pointers to details about those, and other similar systems, please post them in the comments, so the concepts could be looked at and learned from as well. I still need to any research on pre-existing concepts, currently still busy with designing this proposal itself some more.

Ideally these systems are done with cross-desktop orientation in mind. At least for the services that should be doable, as service registration and service execution could be done via the abstraction layers of D-Bus, so the actual implementation does not matter. For the data recognition system I am not so sure yet, as multiple plugins all getting full data copies passed to do their special recognition on sounds rather heavy. No idea how shared memory would help here without introducing other problems?

Please give your input in the comments below, interested what you think of this.
I hope to also find a place for a BoF here at Akademy, for some proper feedback on the plan and hopefully implementation helpers :)


by Friedrich Kossebau (frinring) at September 05, 2014 10:28 PM

Google News

Debunking the top open source myths - Network World


Debunking the top open source myths
Network World
It's this very reason that governments, such as the Republic of Peru, are adopting “open source first” policies. The U.K.'s recent decision to mandate its agencies' office suites support Open Document Format (ODF) is another manifestation of this trend ...

September 05, 2014 08:27 PM

September 04, 2014

Planet KDE

Kexi: GSoC, JJ, Porting

KDE Project:

There were quite a few Kexi releases since my last blog entry. I tell you, the focus in this work was on improving stability. As an effect, reportedly, there can be a whole day of work without stability issues. Not bad..

Kexi is in fact a family of 5 or more apps integrated into one environment. Given the scope and ambitions it can be easily stated that we miss 20 to 30 engineers! Encouraging and educating new ones is a neverending activity. Out of the possible approaches these are well known: Google Summer of Code, Junior Jobs, non-coding contributors.

GSoC

Google Summer of Code brought Harshita Mistry to the Kexi project this year. It's now possible to import LibreOffice Base proprietary ODB files. Kexi is currently the only non-Java solution providing exit scenario from the Java Based HyperSQL database engine that LibreOffice Base employs. Currently table schema and data can be imported to Kexi. Much more can be done, if you're interested in joining, let me know.

But there's one more Google Summer of Code that I mentor. Amarvir Singh's application was accepted and I actually co-mentored him with Inge Wallin (thanks for convincing me!). Parley, a program that helps you memorize things, was obvious candidate for adding a database layer. The idea is to use an ordinary, usually file-based, database instead of a custom storage. Parley gets performant data storage solution for free and by the way, the file could be also opened by Kexi for modification.

Junior Jobs

Junior Jobs are sometimes available within the Season of KDE but are also present as a whole year offer.
Wojciech Kosowicz joined just before this summer and already contributed a number of useful improvements! Can a Junior be productive with a 160k-lines-of-code project in a week? Sure he can.

Great non-programming contributors

In addition, many great contributors offer their time and energy for testing and suggesting improvements. Among them, bookstore owner and hacker Ian Balchin joined the team. He moved to Linux for his book database needs and now uses Kexi 2.8 paired with a database server.

Porting to Qt 5, KF 5, and evolution of the UX

Finally, together with Calligra Kexi sails to the new ports of Qt 5 and KF5. This is rather very early stage for Kexi, Krita is much more ahead in this process. At technical level the code and app will be more compact and more accessible for final touches. That would hopefully lead to truly native experience on various platforms. I expect noticeable refresh of the visuals in many ways. For example, layouts, menus, as developed in the VDG's HIGs. Moreover, the great C++ based style will help in the transition.

For me this bit is a sign my personal change from developer who likes design and art to an amateur designer/creator who also program. You might remember this entry posted 18 months ago, probably before the new KDE visual/UX philosophy emerged. Now I see the building blocks fit.

Kexi 2.x already mixes of web user experience (just start Kexi to see its very own assistant, and removal of many K/QDialogs) and advantages of unmatched performance and offline capabilities. This happens without compromises like constriants of the traditional QStyle. Often I am thinking about application's appearance in the terms of its very own signature, program's DNA. I'll try to prepare new mockups.

And of course... find a guy wearing an old Kexi T-shirt, because:

by Jarosław Staniek (jstaniek) at September 04, 2014 09:41 PM

September 03, 2014

Google News

Sharing work is easier with an Open Document Format - BIT


Sharing work is easier with an Open Document Format
BIT
At another level ODF is a very complex format, as there is a lot of markup associated with an office document and the specification must capture all this. The document that specifies the OpenDocument standard (which includes other office formats ...

September 03, 2014 07:22 AM

September 01, 2014

Google News

Sharing work is easier with an Open Document Format - The Conversation AU


Sharing work is easier with an Open Document Format
The Conversation AU
The Open Document Format (ODF) is one such format. ODF was specified by the Organization for the Advancement of Structured Information Standards (OASIS), an industry consortium which aims to produce standards for e-business. Key players in OASIS ...

September 01, 2014 08:45 PM

5 tips on migrating to open-source software - TechRepublic


5 tips on migrating to open-source software
TechRepublic
The Open Document Format (ODF) is alive and well within LibreOffice. So, when you're using those tools, your best bet is to start saving in their native format, particularly when you're either not sharing documents or sharing them with other users who ...

September 01, 2014 12:18 PM

August 29, 2014

Google News

View Open Document Files With ODF Reader for BlackBerry 10 - N4BB


View Open Document Files With ODF Reader for BlackBerry 10
N4BB
OpenDocument files are XML based files that are mainly used for text documents, presentations, spreadsheets, and graphics. It's intention is to provide a more open file format for office documents. Many nations around the world have adopted ODF as the ...

August 29, 2014 11:46 PM

August 28, 2014

Google News

10 tips for easier collaboration between office suites - TechRepublic (blog)


10 tips for easier collaboration between office suites
TechRepublic (blog)
Yes, you are likely using the Microsoft formats for your documents. However, they don't always follow OpenDocument Format (ODF) standards. Instead of opting for the proprietary Microsoft formats, switch over to one that's welcomed by nearly all office ...

August 28, 2014 06:24 PM

China Promotes Linux-Based Operating System Against Windows, Android - The VAR Guy


The VAR Guy

China Promotes Linux-Based Operating System Against Windows, Android
The VAR Guy
That's one reason Microsoft has adopted the ODF file format in their office suite, even if poorly implemented as the EU has generally mandated ODF standards, not Microsoft Office formats for the entire continent going forward. reply. Anonymous (not ...

and more »

August 28, 2014 02:33 PM

August 26, 2014

Google News

Patent trolls and open document formats with open source thought leaders - opensource.com


Patent trolls and open document formats with open source thought leaders
opensource.com
Gordon: There's often issues the fidelity of the document formats and how they convertible they are. As you talk about presentations and the like, is there anything around how convertible things like the particular ODF implementation needs to be?

August 26, 2014 11:22 AM

Patent trolls and open document formats with open source thought leaders - opensource.com


Patent trolls and open document formats with open source thought leaders
opensource.com
To go in reverse order, the UK announced that it's standardizing an open document format this week, which means that all future UK government work is going to be using an open standard. .... The UK government now requires you use ODF. There is no ...

August 26, 2014 11:22 AM

August 25, 2014

Google News

Rural Sanitation Transformation in Himachal Pradesh - Hill Post


Rural Sanitation Transformation in Himachal Pradesh
Hill Post
More important, surveys show that in the country as a whole, NGP awardees continue to exhibit significant presence of open defecation and only a negligible number are actually Open Defecation Free (ODF)[6]. ..... The workshop format included the usual ...

and more »

August 25, 2014 08:45 AM

August 20, 2014

Planet KDE

The features I have implemented in my Google Summer Of Code project

Sadly, the official coding time for Google Summer of Code has come to an end. :( It was wonderful working with my mentor Jigar. So I have coded three features for Calligra Sheets.

1. View Splitter -
-> I have pushed the code in sheets-vs-mrupanjana.
The feature enables a particular sheet view to be split into two portions vertically. The
cursors are not synchronized. Different input data can be given in the two portions. We often do not need to work with lots of columns, so the sheet view is at times more than optimum. It can easily be split and we can continue our work on both the portions.

2. Highlighting changes in a cell -
-> Code is pushed in sheets-hc-mrupanjana
This is a really interesting one and is absent in other similar applications. The user begins a session, feeds some data in the sheet, makes some changes in the cells where already there has data. The cells which have undergone changes are highlighted with dark blue colour. This enhances readability and the user will be aware of the changes made in the present session.

3. Autocorrection of function name -
-> Code has been pushed in sheets-fName-mrupanjana
Often user forgets the exact function name for calculating cos of an angle, absolute value of a number and guesses the function names. The user makes a guess and inputs a function name which is supposedly wrong. As he or she presses enter, it gets automatically corrected.If the user does not want the change in name, he or she can escape to the next cell using tab.

I have coded the storage and the implementation of all the three features. Hope to see them merged soon. :)


by Rupanjana Mitra (mrupanjana) at August 20, 2014 04:20 AM