Planet ODF

This is the first ever LibreOffice conference covering Latin America, a rapidly-growing area for free and open source software.

Berlin, April 2nd, 2019 – The Document Foundation announces the LibreOffice Latin America Conference 2019, held at the Facultad Politécnica de Universidad Nactional de Assunción (FPUNA) in Asunción, Paraguay on July 19th (Friday) and 20th (Sat).

LibreOffice Latin America Conference will be the first event gathering LibreOffice users, advocates and contributors (not only development, but also localization, PR/marketing, documentation, quality assurance, … etc.) from different countries in Latin America, to exchange and share experiences and knowledge.

An exclusive translation sprint to Guarani will be held in parallel during the event with supervision of LibreOffice volunteer developers.

During the conference, we will discuss LibreOffice related business such as supporting and training, migrating to LibreOffice and the ODF true standard format, developing, and any other community activity in Latin America. In addition, we will have guests from the core team at The Document Foundation, which is a charitable foundation and the home of LibreOffice.

“The event will be an important opportunity for the consolidation of LibreOffice and free open source software in the region, bringing experiences from other countries for discussions and software development in Latin America” commented Alcides Javier Torres Gutt, professor at FPUNA. “FPUNA is proud to host the event for the Paraguayan FOSS communities, as well as advancing in the creation of a real LibreOffice with Guarani user interface”.

“The Document Foundation is a global organization, and as such wants to tighten the relationship with local communities in areas like Latin America, where there are huge growth opportunities for free open source software. A conference is the best way of putting together LibreOffice advocates, and sharing experiences and best practices at continental level” said Italo Vignoli, Marketing and Communication specialist at the Document Foundation.

Contact the conference organizers at mail address latinoamerica@global.libreoffice.org.

Dating maintenance tags: {{Cn}}

← Previous revision		Revision as of 13:34, 27 March 2019
Line 205:		Line 205:
	A second contributor to ODF development, [[IBM]]&nbsp;– 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>&nbsp;– 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]]&nbsp;– 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>&nbsp;– 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.{{cn}}	+	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.{{cn|date=March 2019}}
	==Response==		==Response==

Licensing

← Previous revision		Revision as of 11:33, 27 March 2019
Line 199:		Line 199:
	===Additional royalty-free licensing===		===Additional royalty-free licensing===
−	Obligated [http://www.oasis-open.org/committees/daycount/tc/office.html members] of the OASIS ODF TC have agreed to make deliverables available to implementors under the OASIS Royalty Free with Limited Terms [http://www.oasis-open.org/who/intellectualproperty.php policy].	+	Obligated members<ref>[http://www.oasis-open.org/committees/daycount/tc/office.html office members]</ref> of the OASIS ODF TC have agreed to make deliverables available to implementors under the OASIS Royalty Free with Limited Terms [http://www.oasis-open.org/who/intellectualproperty.php policy].
	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>
Line 205:		Line 205:
	A second contributor to ODF development, [[IBM]]&nbsp;– 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>&nbsp;– 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]]&nbsp;– 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>&nbsp;– 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.{{cn}}
	==Response==		==Response==

← Previous revision		Revision as of 11:32, 27 March 2019
Line 143:		Line 143:
	===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 [[Collaborative real-time editor|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 [[Collaborative real-time editor|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><ref>[https://www.kahootz.com/document-management/ Document collaboration]</ref>
	==Application support==		==Application support==

Comments

Berlin, February 28, 2019 – Call for Papers for LibreOffice Asia Conference 2019, held at the Nihonbashi Tokyo Tower (at Cyboze, Inc., Tokyo Office) on May 25th (Sat) and 26th (Sun), is now open.

LibreOffice Asia Conference will be the first event gathering LibreOffice users, advocates and contributors (not only development, but also localization, PR/marketing, documentation, quality assurance, ‌ etc.) from different countries in Asia, to exchange and share experiences and knowledge.

During the conference, we will discuss LibreOffice related business such as supporting and training, migrating to LibreOffice and the ODF true standard format, developing, and any other community activity in Asia. In addition, we will have guests from the core team at The Document Foundation, which is a charitable foundation and the home of LibreOffice.

LibreOffice Kaigi, the traditional local event for Japanese speakers, will be held in parallel with the conference. So, there will be an English track and a Japanese track.

Any topic related to LibreOffice and ODF, such as LibreOffice user cases, contribution experiences in different areas, technical analisys of LibreOffice code development, success stories of migrations from proprietary software, or tips and tricks about LibreOffice usage, and so on, are all welcome. All talks will be 25 minutes long, including Q&A.

We are planning to reimburse expenses to accepted speakers, based on TDF reimbursement rules, including:

• Flight or bullet train tickets (please note that tickets for local trains will NOT be reimbursed)
• Accommodations for two nights in a hotel (please note that luxury hotels will NOT be reimbursed)

Do not hesitate to send your proposals, even if you live far from Tokyo or in another country in Asia.

To submit your talk proposal, please send an e-mail to libo-asia-contact@libreoffice.jp with:

Subject: [CFP] Title of your Talk

Your Name:
Your e-mail address:
Your profile:
Title of the Talk:
Abstract: (around 300 words)
Estimate of expenses to be reimbursed (if you will be asking for reimbursement)

In order to allow everyone to plan in advance their travels and accommodations, the deadline for the call for papers is on March 10th (Sun) 23:59:59 JST (UTC+9).

We will inform all approved speakers by March 22nd (Fri) JST.

An anonymous reader quotes a report from ZDNet: A team of academics from the Ruhr-University Bochum in Germany say they've managed to break the digital signing system and create fake signatures on 21 of 22 desktop PDF viewer apps and five out of seven online PDF digital signing services. This includes apps such as Adobe Acrobat Reader, Foxit Reader, and LibreOffice, and online services like DocuSign and Evotrust --just to name the most recognizable names. The five-person research team has been working since early October 2018 together with experts from Germany's Computer Emergency Response Team (BSI-CERT) to notify impacted services. The team went public with their findings over the weekend after all affected app makers and commercial companies finished patching their products. In research published today, the Ruhr-University Bochum team described three vulnerabilities that they found in the digital signing process used by several desktop and web-based PDF signing services. Summarized, they are: 1. Universal Signature Forgery (USF) -- vulnerability lets attackers trick the signature verification process into showing users a fake panel/message that the signature is valid. 2. Incremental Saving Attack (ISA) -- vulnerability lets attackers add extra content to an already signed PDF document via the "incremental saving (incremental update)" mechanism, but without breaking the already-existing signature. 3. Signature Wrapping (SWA) -- vulnerability is similar to ISA, but the malicious code also contains extra logic to fool the signature validation process into "wrapping" around the attacker's extra content, effectively digitally signing the incremental update. Additional details about the three vulnerabilities are available in this PDF research paper [1, 2], this blog post, and this dedicated website.

Read more of this story at Slashdot.

Rescuing 0 sources and tagging 1 as dead. #IABot (v2.0beta10ehf1)

← Previous revision		Revision as of 10:55, 21 February 2019
Line 322:		Line 322:
	* [http://documentfreedom.org/index.en.html Document Freedom Day]		* [http://documentfreedom.org/index.en.html Document Freedom Day]
	* [http://opendocsociety.org/ OpenDoc Society] Association with members around the world that promote best practices in office productivity such as OpenDocument format.		* [http://opendocsociety.org/ OpenDoc Society] Association with members around the world that promote best practices in office productivity such as OpenDocument format.
−	* [http://opendocumentfellowship.com/{{dead link|date=March 2018 |bot=InternetArchiveBot |fix-attempted=yes }} OpenDocument Fellowship] Volunteer organization with members around the world to promote the adoption, use and development of the OpenDocument format.	+	* [http://opendocumentfellowship.com/{{dead link|date=March 2018 |bot=InternetArchiveBot |fix-attempted=yes }} OpenDocument Fellowship]{{Dead link|date=February 2019 |bot=InternetArchiveBot |fix-attempted=yes }} Volunteer organization with members around the world to promote the adoption, use and development of the OpenDocument format.
	* [http://opendocument.xml.org/ OpenDocument XML.org] The official community gathering place and information resource for the OpenDocument OASIS Standard (ISO/IEC 26300).		* [http://opendocument.xml.org/ OpenDocument XML.org] The official community gathering place and information resource for the OpenDocument OASIS Standard (ISO/IEC 26300).
	* [http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office OASIS OpenDocument Technical Committee] coordinates the OpenDocument development and is the official source for specifications, schemas, etc.		* [http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office OASIS OpenDocument Technical Committee] coordinates the OpenDocument development and is the official source for specifications, schemas, etc.

LibreOffice developers and other community members were present at FOSDEM 2019, the biggest European meetup of free and open source software developers. Check out the talks that they gave! Click a link to find out more and watch the videos‌

• Relaunching the ODF Adoption TC at OASIS (Italo Vignoli)
• Server side solution for generating ODF reports (Franklin Weng)
• Resurrecting Mozilla Themes for LibreOffice (Muhammet Kara)
• Quo vadis, LibreOffice extensions? (Heiko Tietze)
• Improving LibreOffice quality together (Xisco Fauli)
• Collabora Office on iOS (Tor Lillqvist)
• Preventing OOXML interoperability problems in LibreOffice (Gabor Kelemen)
• New interoperability, i18n and LibreLogo improvements of LibreOffice (LĂĄszlĂł NĂŠmeth)
• MySQL connector and other databases in LibreOffice (TamĂĄs Bunth)
• How to bring LibreOffice to your web app (Michael Meeks)
• Vereign toolbar in LibreOffice Online (Andras Timar)
• Improving SmartArt import in LibreOffice Impress (Miklos Vajna)
• Do you know “layers”? (Regina Henschel)
• Clang plugins in LibreOffice – global analyses across a large codebase (Noel Grandin)
• Native GTK Dialogs – current status and future work (CaolĂĄn McNamara)
• Are we optimiert yet? (Michael Stahl)
• Lightning Talks

A big thanks to the FOSDEM organisers for their great work!

The First LibreOffice Asia Conference Will Be Held On May 25-26, 2019 In Nihonbashi, Tokyo, Japan

This is the first ever LibreOffice conference covering Asia, a rapidly-growing area for free and open source software. The call for papers will be launched soon.

Berlin, February 18, 2019 – After the huge success of the LibreOffice Conference Indonesia in 2018, members of the Asian communities have decided to raise the bar in 2019 with the first ever LibreOffice Asia Conference in Nihonbashi – the very center of Tokyo, Japan – on May 25-26.

One of the main organizers, Naruhiko Ogasawara, a member of the Japanese LibreOffice community and The Document Foundation, can’t hide his excitement: “When we launched the LibreOffice Mini Conference Japan in 2013 as a local event, we knew little about communities in other parts of Asia. In recent years we have attended the LibreOffice Conference and other Asian events like OpenSUSE Asia, COSCUP etc. We have realized that many of our colleagues are active and that our community should learn a lot from them. We are proud to be able to hold the first Asia Conference with our colleagues to further strengthen that partnership.”

“It’s a real leap of faith,” says Franklin Weng, an Asian member in the Board of Directors of The Document Foundation. “Asia is a rapidly-growing area in adoptions of ODF and LibreOffice, but our ecosystem for LibreOffice and FOSS has not been good enough yet. In this conference we’re not only trying to make the FOSS ecosystem in Asia more healthy, but also to encourage Asian community members to show their potential.”

Several core members from The Document Foundation will attend this conference, including Italo Vignoli, leader of the marketing and public relations community (and co-chairman of LibreOffice Certification Committee), along with Lothar Becker, who is also co-chairman of the Certification Committee. In addition, there will be community members from Indonesia, South Korea, Taiwan, Japan and probably China attending.

The main focus areas of this conference include:

• Business workshop – which will be hosted by Lothar Becker and Italo Vignoli. Lothar and Italo will discuss business services: what are the fundamentals of LibreOffice business services, the current status of LibreOffice business in Europe, Asia and other geographies, and how we can support each other, etc.
• CJK Hackfest – which will be led by Mark Hung, a LibreOffice Certified Developer in Taiwan, to discuss and hack CJK issues in LibreOffice.
• Certification Interview – the second LibreOffice Certification Interview in Asia will be held during the LibreOffice Asia Conference, hosted by Italo Vignoli and Lothar Becker. So far total four or five candidates will be interviewed for LibreOffice Certified Migration Professionals and LibreOffice Certified Trainers.
• Asia Local Certification for LibreOffice – which will be hosted by Franklin Weng and Eric Sun, two TDF members from Taiwan, to introduce the concept of having LibreOffice skills and trainer certifications in Asia.

The call for proposals will be launched soon in February. Besides the topics above, other LibreOffice and ODF-related topics are also welcome.

top: +references to LibreOffice, StarOffice

← Previous revision		Revision as of 08:00, 15 February 2019
Line 108:		Line 108:
	The '''Open Document Format for Office Applications''' ('''ODF'''), also known as '''OpenDocument''', is a [[Zip_(file_format)|ZIP]]-compressed<ref>Extract an odt file with unzip on Linux to see the actual resource hierarchy</ref> [[XML]]-based [[file format]] for [[spreadsheet]]s, [[chart]]s, [[Presentation program|presentations]] and [[word processor|word processing]] documents. It was developed with the aim of providing an open, XML-based file format specification for office applications.<ref>{{cite web |url=https://www.oasis-open.org/committees/office/charter.php |title=OASIS Open Document Format for Office Applications (OpenDocument) TC |publisher=Organization for the Advancement of Structured Information Standards |date=19 January 2005 |accessdate=6 October 2013}}</ref>		The '''Open Document Format for Office Applications''' ('''ODF'''), also known as '''OpenDocument''', is a [[Zip_(file_format)|ZIP]]-compressed<ref>Extract an odt file with unzip on Linux to see the actual resource hierarchy</ref> [[XML]]-based [[file format]] for [[spreadsheet]]s, [[chart]]s, [[Presentation program|presentations]] and [[word processor|word processing]] documents. It was developed with the aim of providing an open, XML-based file format specification for office applications.<ref>{{cite web |url=https://www.oasis-open.org/committees/office/charter.php |title=OASIS Open Document Format for Office Applications (OpenDocument) TC |publisher=Organization for the Advancement of Structured Information Standards |date=19 January 2005 |accessdate=6 October 2013}}</ref>
−	The standard was developed by a technical committee in the [[OASIS (organization)|Organization for the Advancement of Structured Information Standards]] (OASIS) consortium.<ref>{{cite web |url=http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office |title=OASIS Open Document Format for Office Applications (OpenDocument) TC |publisher=[[OASIS (organization)|Organization for the Advancement of Structured Information Standards]]}}</ref> It was based on the [[Sun Microsystems]] specification for [[OpenOffice.org XML]], the default format for [[OpenOffice.org]], which had been specifically intended "to provide an open standard for office documents."<ref>{{citation |url=http://xml.coverpages.org/openoffice-xml_specification_draft200012.pdf |format=PDF |title=StarOffice XML File Format Working Draft, Technical Reference Manual, Draft 9, December 2000 |date=December 2000 |accessdate=2010-08-08}}</ref>	+	The standard was developed by a technical committee in the [[OASIS (organization)|Organization for the Advancement of Structured Information Standards]] (OASIS) consortium.<ref>{{cite web |url=http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office |title=OASIS Open Document Format for Office Applications (OpenDocument) TC |publisher=[[OASIS (organization)|Organization for the Advancement of Structured Information Standards]]}}</ref> It was based on the [[Sun Microsystems]] specification for [[OpenOffice.org XML]], the default format for [[OpenOffice.org]] and [[LibreOffice]]. It was originally developed for [[StarOffice]] "to provide an open standard for office documents."<ref>{{citation |url=http://xml.coverpages.org/openoffice-xml_specification_draft200012.pdf |format=PDF |title=StarOffice XML File Format Working Draft, Technical Reference Manual, Draft 9, December 2000 |date=December 2000 |accessdate=2010-08-08}}</ref>
	In addition to being an OASIS standard, it was published as an [[International Organization for Standardization|ISO]]/[[International Electrotechnical Commission|IEC]] international standard ISO/IEC 26300{{snd}} Open Document Format for Office Applications (OpenDocument).<ref name="odf12-part1"/><ref name="odf12-part2"/><ref name="odf12-part3"/><ref name="odf10"/><ref name="iso.org">{{citation |url=http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=59302 |title=ISO/IEC 26300:2006/Amd 1:2012 – Open Document Format for Office Applications (OpenDocument) v1.1 |date=8 March 2012 |accessdate=12 April 2012}}</ref><ref name="http">{{cite web |url=http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=59302 |title=ISO/IEC 26300:2006/DAM 1 – OpenDocument v1.1 |accessdate=29 March 2011}}</ref>		In addition to being an OASIS standard, it was published as an [[International Organization for Standardization|ISO]]/[[International Electrotechnical Commission|IEC]] international standard ISO/IEC 26300{{snd}} Open Document Format for Office Applications (OpenDocument).<ref name="odf12-part1"/><ref name="odf12-part2"/><ref name="odf12-part3"/><ref name="odf10"/><ref name="iso.org">{{citation |url=http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=59302 |title=ISO/IEC 26300:2006/Amd 1:2012 – Open Document Format for Office Applications (OpenDocument) v1.1 |date=8 March 2012 |accessdate=12 April 2012}}</ref><ref name="http">{{cite web |url=http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=59302 |title=ISO/IEC 26300:2006/DAM 1 – OpenDocument v1.1 |accessdate=29 March 2011}}</ref>

External links: fsf

← Previous revision		Revision as of 12:33, 12 February 2019
Line 327:		Line 327:
	* [http://www.robweir.com/blog/2009/06/odf-lies-and-whispers.html Technical disputes regarding ODF vs. OOXML]		* [http://www.robweir.com/blog/2009/06/odf-lies-and-whispers.html Technical disputes regarding ODF vs. OOXML]
	* [http://office.microsoft.com/en-us/word-help/differences-between-the-opendocument-text-odt-format-and-the-word-docx-format-HA010355788.aspx Microsoft Office (2007, 2010 and 2013), Differences between the OpenDocument Text (.odt) format and the Word (.docx) format]		* [http://office.microsoft.com/en-us/word-help/differences-between-the-opendocument-text-odt-format-and-the-word-docx-format-HA010355788.aspx Microsoft Office (2007, 2010 and 2013), Differences between the OpenDocument Text (.odt) format and the Word (.docx) format]
		+	* [https://www.fsf.org/campaigns/opendocument fsf.org] The Free Software Foundation's campaign to support OpenDocument.
	{{OASIS Standards}}		{{OASIS Standards}}

Controversial think-tank #ODF in Brussels move  EU Reporter

Despite being banned from the EU, Lyudmila Kozlovska (pictured), president of the Open Dialogue Foundation, has relocated her HQ to Brussels, writes James ...

An anonymous reader shares a report: New interface styles and feature improvements are available in version 6.2 of LibreOffice -- the most popular open-source office suite -- released Thursday by The Document Foundation. As with any software update, bug fixes and feature enhancements are present, making this release a significant upgrade, particularly for users coming from Microsoft Office, or working with files created with those programs. LibreOffice now supports SVG-based icons for toolbars in the Breeze, Colibre, and Elementary icon sets as an experimental feature, to better support HiDPI displays increasingly found in notebook PCs. The Elementary icon set was also improved significantly, adding a 32px PNG version, and fixing inconsistencies between the 16, 24, and 32px versions, as well as adding more icons across the set to prevent reverting to defaults. In LibreOffice 6.2, the "Tabbed" interface is now available for Writer, Calc, Impress, and Draw, and is considered sufficiently stable to be a default option. This interface mimics the oft-maligned "Ribbon interface" in Office 2007. The "traditional" Office-style toolbar is default, though the Tabbed interface can be enabled through the "View > User Interface" menus.

Read more of this story at Slashdot.

Govt launches 'Darwaza Band-Part 2' campaign to promote ODF sustainability  Indiantelevision.com

The Swachh Bharat Mission Grameen launched the 'Darwaza Band -Part 2' campaign focusing on sustaining the open defecation free status of villages across ...

Today we’re chatting with a member of the French-speaking LibreOffice community, Pierre-Yves Samyn, who helps our marketing and documentation projects with videos and translations:

Where do you live, and what do you enjoy in your spare time?

I live in metropolitan France. Outside of LibreOffice, I like to read, listen and play music.

In which areas of the LibreOffice project are you active?

Thesedays, my main activities for the project are:

1. Following up the French part of the wiki (translation of the release notes mainly)
2. The creation of videos, posted on the French TDF channel (click the playlist button in the top-left to see other videos):

    

   Please confirm that you want to play a YouTube video. By accepting, you will be accessing content from YouTube, a service provided by an external third party.

   YouTube privacy policy

   If you accept this notice, your choice will be saved and the page will refresh.

   Accept YouTube Content

   I started with a more-or-less weekly rhythm, with the idea of making “videos of the week”, like the tips of the week we have on the Twitter account. I have kept that pace for around three to four years. Today, I make videos more according to the inspiration of the moment, or following a question that was asked. I also try to add English subtitles.

3. The other thing I do in the project is to respond punctually to questions on English-speaking Ask LibreOffice site (not as often as I would like).

How did you get involved with LibreOffice?

I get involved through my work, at the time with OpenOffice.org version 1.1.3 if my memory is good. The software imported less than the ODF format for this project, consisting (in part) of using the software conversion features. I was immediately seduced, and reported to the project my experience in creating training support, user support, etc.

What was your initial experience of contributing to LibreOffice like?

Helping first: I was active member on the OpenOffice.org forum, then on all the French mailing lists (discuss, users, QA etc.) Then I moved on to testing new versions (reports or comment on Bugzilla). I also participated in making content for the wiki (creation/update of FAQs, macros, release notes…). And I participated in the documentation project (proofreading).

What tools do you use for your work?

Eclipse, Vim, Notepad++, Atom, VLC…

Finally, what does LibreOffice need most right now?

I probably do not have a sufficient overall vision of the project, but here are some topics that resonate in me (in no order of priority):

• More women on group photos…
• Develop and publicize the big and beautiful Document Liberation Project
• Compatibility
• Work on the mobile apps
• Automatic updates
• Accessibility

Many thanks to Pierre-Yves Samyn for all his help and contributions! Learn more about the French LibreOffice community here, and then get to know us – we’re a friendly, growing free software project, so by taking part you can meet new people and build up valuable experience. Join us today!

General Activities

• LibreOffice 6.1.4 was announced on December 18
• LibreOffice 6.2 RC1 was released and it’s ready for testing
• On December 21, the bug hunting session for LibreOffice 6.2 RC1 took place
• bibisect repositories for LibreOffice 6.3 were created
• Katarina Behrens (CIB) fixed some Drag&Drop problems on KDE5
• Drew Jensen tested the Firebird assistant migration with an assembled group of test files
• Luboš Luňák (Collabora) did lots of OpenCL fixes
• New Bugzilla component “iOS”
• Moggi wrote a blogpost about automated testing in LibreOffice
• NISZ LibreOffice Team reported many Conditional formatting issues
• LibreOffice 6.1.4.2 and 6.2.0.1 for macOS have been rebuilt to solve crashes and freezes affecting many users on MacOS Mojave
• Jens Carl moved dozens of Java tests to C++
• Balázs Varga fixed a bunch of chart issues
• Justin Luth fixed an old annoying issue, where clearing direct formatting would damage the document styles
• Andreas Kainz made dozens of Notebookbar and icon improvements
• New team member Durgapriyanka continued to do a significant amount of triaging
• KDE4 support was removed in master
• Eike Rathke (Red Hat) reworked the Statistics dialog
• Mike Kaganski (Collabora) added Scan support for LibreOffice x64 on Windows
• Vasily Melenchuk (CIB) added support for exporting to .xltx and .dotx
• Michael Stahl (CIB) reimplemented the hiding tracked changes mechanism
• László Németh (NISZ) added support for native copy&paste of spreadsheet data in Writer tables
• Many new features and improvements in LibreOffice Online

Reported Bugs

560 bugs have been reported by 347 people.

Top 10 Reporters

1. NISZ LibreOffice Team ( 22 )
2. Xisco Faulí ( 21 )
3. Regina Henschel ( 12 )
4. Michael Weghorn ( 12 )
5. Drew Jensen ( 10 )
6. Vera Blagoveschenskaya ( 10 )
7. Mike Kaganski ( 9 )
8. Robert Großkopf ( 8 )
9. Markus Elfring ( 7 )
10. Roman Kuznetsov ( 7 )

Triaged Bugs

570 bugs have been triaged by 77 people.

Top 10 Triagers

1. Xisco Faulí ( 105 )
2. Dieter Praas ( 51 )
3. raal ( 36 )
4. durgapriyanka.arun ( 35 )
5. Timur ( 35 )
6. Roman Kuznetsov ( 30 )
7. Oliver Brinzing ( 22 )
8. Heiko Tietze ( 22 )
9. Alex Thurgood ( 21 )
10. V Stuart Foote ( 20 )

Fixed Bugs

208 bugs have been fixed by 49 people.

Top 10 Fixers

1. Caolán McNamara ( 37 )
2. Mike Kaganski ( 29 )
3. andreas kainz ( 12 )
4. Xisco Fauli ( 7 )
5. Eike Rathke ( 6 )
6. Roman Kuznetsov ( 5 )
7. Michael Weghorn ( 5 )
8. Katarina Behrens ( 5 )
9. László Németh ( 4 )
10. Balazs Varga ( 4 )

List of critical bugs fixed

1. tdf#120576 CRASH: Base crash without any notice with the option to migrate the embedded database from HDBSQL to FIREBIRD. ( Thanks to Caolán McNamara )
2. tdf#122116 LibreOffice 6.1.* crashes by recovering file at start over and over on Linux ( Thanks to Michael Weghorn )
3. tdf#120454 kde5: Sporadic crash when right-clicking items in toolbar ( Thanks to Katarina Behrens )
4. tdf#122059 ReportBuilder: GTK3: Crash in: Wallpaper::operator= Format -> Page crashes ( Thanks to Caolán McNamara )
5. tdf#121935 Cancelling database wizard at step ‘Set up connection to text files’ crashes ( Thanks to Caolán McNamara )
6. tdf#121810 Crash in: libgobject-2.0.so.0.5600.3 when selecting more on error dialog ( Thanks to Caolán McNamara )
7. tdf#121555 GTK3: Crash displaying menus with new elements ( Thanks to Caolán McNamara )
8. tdf#121838 Firebird: Mirgration: Certain ODB crashes application during Migration Assistant execution ( Thanks to Caolán McNamara )
9. tdf#121815 Crash in: FreetypeFont::GetFtFace ( Thanks to Jan-Marek Glogowski )
10. tdf#122136 clicking on class path make LO crash ( Thanks to Julien Nabet )
11. tdf#122020 CRASH in SvTreeList::InvalidateEntry(SvTreeListEntry *) ( Thanks to Caolán McNamara )
12. tdf#122127 Crash in: libmergedlo.so FORM EDIT using drag drop to move control from one dataform to another causes crash ( Thanks to Noel Grandin )
13. tdf#121180 Crash restarting LibreOffice after applying an option (no crash if going via “OK”) ( Thanks to Mike Kaganski )
14. tdf#122269 CRASH: Closing LibreOffice after installing an extension with the extension manager open ( Thanks to Caolán McNamara )
15. tdf#121247 KDE5: Impress crashes at starting Slide show (presentation with animation and audio) ( Thanks to Aleksei Nikiforov )
16. tdf#122016 GTK3: Crash closing LibreOffice in full screen mode with notebookbar enabled ( Thanks to Caolán McNamara )
17. tdf#121892 gtk3_kde5: Impress presentation minimizer crashes ( Thanks to Michael Weghorn )
18. tdf#122152 CRASH closing LibreOffice while Sort dialog is open ( Thanks to Caolán McNamara )
19. tdf#122153 CRASH closing LibreOffice while XML filter settings dialog is open ( Thanks to Caolán McNamara )
20. tdf#122219 CRASH: closing Base while XML filter settings dialog is open ( Thanks to Caolán McNamara )
21. tdf#120750 Crash applying bold to textbox control ( Thanks to Xisco Fauli )
22. tdf#121266 KDE5: Impress crashes after selecting some of Slide Transitions ( Thanks to Aleksei Nikiforov )
23. tdf#120885 nice Crash on choosing ‘more styles’ from dropdown ‘Apply Style ‘with graphic selected ( Thanks to Caolán McNamara )
24. tdf#122038 Crash modifying several options each requiring restart ( Thanks to Mike Kaganski )
25. tdf#121399 [gtk3_kde5] 6.1 stable branch: within Plasma-5 session w/ drkonqi: lo_kde5filepicker crashes every time on close (OK/Cancel regardless) ( Thanks to Michael Weghorn )
26. tdf#122042 CRASH KDE5 backend crashes writer on close with selected text ( Thanks to Katarina Behrens )
27. tdf#122335 Crash in debug build, when save a pptx file with custom shape to strict ODF 1.2 ( Thanks to Julien Nabet )
28. tdf#121022 Contour editor crashes ( Thanks to Armin Le Grand )

Verified bug fixes

97 bugs have been verified by 17 people.

Top 10 Verifiers

1. Xisco Faulí ( 62 )
2. Michael Weghorn ( 9 )
3. BogdanB ( 8 )
4. Balázs Varga ( 3 )
5. Vera Blagoveschenskaya ( 2 )
6. Jean-Baptiste Faure ( 2 )
7. Justin L ( 1 )
8. Mike Kaganski ( 1 )
9. Aron Budea ( 1 )
10. m.a.riosv ( 1 )

Categorized Bugs

915 bugs have been categorized with a metabug by 35 people.

Top 10 Categorizers

1. Roman Kuznetsov ( 603 )
2. Thomas Lendo ( 91 )
3. Dieter Praas ( 59 )
4. andreas_k ( 32 )
5. Xisco Faulí ( 18 )
6. Aron Budea ( 14 )
7. Buovjaga ( 14 )
8. Michael Weghorn ( 12 )
9. V Stuart Foote ( 10 )
10. Vera Blagoveschenskaya ( 9 )

Regression Bugs

93 bugs have been set as regressions by 18 people.

Top 10

1. Xisco Faulí ( 46 )
2. raal ( 10 )
3. Telesto ( 7 )
4. Timur ( 6 )
5. Robert Großkopf ( 5 )
6. Alex Thurgood ( 5 )
7. Roman Kuznetsov ( 3 )
8. MM ( 1 )
9. Aron Budea ( 1 )
10. Terrence Enger ( 1 )

Bisected Bugs

76 bugs have been bisected by 10 people.

Top 10 Bisecters

1. Xisco Faulí ( 37 )
2. raal ( 22 )
3. Oliver Brinzing ( 4 )
4. Aron Budea ( 4 )
5. Roman Kuznetsov ( 2 )
6. Terrence Enger ( 2 )
7. Buovjaga ( 2 )
8. Michael Weghorn ( 1 )
9. Telesto ( 1 )
10. Luke ( 1 )

Evolution of Unconfirmed Bugs

Check the current list of unconfirmed bugs here

Evolution of Open Regressions

Check the current list of open regressions here

Evolution of Open bibisectRequests

Check the current list of open bibisectrequests here

Evolution of Highest Priority Bugs

Check the current list of highest priority bugs here

Evolution of High Priority Bugs

Check the current list of high priority bugs here

Thank you all for making Libreoffice rock!
Join us and help to keep LibreOffice super reliable!
Check the Get Involved page out now!…

The post QA Report: December 2018 appeared first on LibreOffice QA Blog.

How much do you know about LibreOffice – the software, the community and its history? We’ve made a little quiz for you to try out, so check out the questions below, and you’ll find the answers at the bottom. Good luck :-)

1 – LibreOffice is a successor to OpenOffice.org, which was based on the proprietary suite StarOffice. Which company was behind StarOffice?

A: Star Corp
B: Solar Sys
C: Star Division

2 – In which year was The Document Foundation (TDF), the non-profit entity behind LibreOffice, legally established?

A: 2009
B: 2012
C: 2014

3 – Who is the current chairperson of TDF?

A: Marina Latini
B: Michael Meeks
C: Thorsten Behrens

4 – LibreOffice includes a graphics editing tool – what is it called?

A: Create
B: Draw
C: Graphic

5 – If you don’t like the default icon set in LibreOffice, how can you change it?

A: Under the Format menu
B: Via Tools > Options > View
C: Using an extension

6 – What’s the standard document format of LibreOffice called?

A: OpenDocument Format
B: OpenXML Format
C: LibreDocument Format

7 – What is a “Hybrid PDF?”

A: It includes interactive elements and animations
B: It includes all fonts, to display properly everywhere
C: It includes the original source document, to allow editing

8 – LibreOffice includes a dockable window to help you move around complex documents. What is it called?

A: DocBrowser
B: Navigator
C: Overview

9 – If you want Writer to automatically add numbered captions when inserting objects, where do you go?

A: Tools > Options > Objects > Preferences
B: Insert > Image > tick “Add captions” box
C: Tools > Options > LibreOffice Writer > AutoCaption

10 – With which major LibreOffice release did the branding change to include cubes?

A: LibreOffice 4
B: LibreOffice 5
C: LibreOffice 6

11 – LibreOffice 6.2 will include a new (optional) user interface design. What’s its name?

A: TabBar
B: GroupedBar
C: NotebookBar

12 – Where did the 2013 LibreOffice Conference take place?

A: Berlin
B: Milan
C: Paris

13 – And where will the 2019 Conference be?

A: Almeria
B: Stockholm
C: Budapest

14 – Markus Mohrhard is a long-time LibreOffice developer, who has been involved in the project since its early years. What is his nickname?

A: Moggi
B: Marko
C: Maggi

15 – Another hard-working member of the community is “raal”, who helps out with events in the Czech Republic. But what’s his real name?

A: Stanislav Horáček
B: Zdeněk Crhonek
C: Jan Dvořák

16 – Finally, who can join the LibreOffice project and help to improve the software?

A: Experienced C++ developers
B: Members of The Document Foundation
C: Absolutely anybody

And now, the answers:

1: C
2: B
3: A
4: B
5: B
6: A
7: C
8: B
9: C
10: C
11: C
12: B
13: A
14: A
15: B
16: C, of course!

We in the community wish you all a great Christmas and festive time, and a happy new year. Here’s to a great 2019, with many more LibreOffice releases, events and fun to be had!

Comments

Floor Mount Optical Distribution Frame (ODF) Market Data Tables, Pie Chat, Graphs & Figures of Key Players | Hua Wei, 3M, Huber + Suhner  The Future Gadgets

HTF MI broadcasted a new title “Global Floor Mount Optical Distribution Frame (ODF) Market Research Report 2018” with 127 pages and in-depth assessment ...

Gerlinda de Vries is sinds september 2018 als Rijkstrainee in dienst bij het Bureau Forum Standaardisatie (onderdeel van het ministerie Binnenlandse Zaken en Koninkrijksrelaties). Het bureau zet zich in voor open ICT-standaarden. De opdracht van De Vries? Bouw een community rondom documentstandaarden. In gesprek met de community manager ‘Open Documentstandaarden’.

Verbindende rol

‘Toen we deze website gingen bouwen had ik een online community voor ogen waar leden elkaar ondersteunen rondom de problematiek en veranderingen binnen de documentstandaarden’, vertelt de Vries. ‘De doelgroep hebben we expres zo breed mogelijk gehouden. Zo kan iedereen die geïnteresseerd is meelezen en meewerken aan de community. Dat maakt ook dat er vanuit verschillende kanten ervaringen gedeeld kunnen worden. We profileren ons niet als expertisecentrum maar juist als verbinder. Daar waar kan verwijzen we door naar bijvoorbeeld DigiToegankelijk.

Stimuleren van interactie

‘We bieden leden nieuws, blogs, agenda en forums. Daarnaast plaatsen we ongeveer één keer per week een artikel over het laatste nieuws rondom toegankelijkheid of documentstandaarden. Op deze manier blijven de leden op de hoogte. Verder stimuleren we interactie zo veel als mogelijk. We schrijven zelf blogs of vragen anderen ze te schrijven. En leden kunnen natuurlijk zelf ook een blog plaatsen als ze bijvoorbeeld kennis willen delen over een specifieke standaard. Hier kan op gereageerd worden en zo ontstaat discussie. Verder staan we open voor input van de leden zelf. Als er veel behoefte is aan een specifiek onderwerp gaan we daar zeker iets mee doen. Zo zijn er vragen opgekomen rond marktpartijen en of we die ook moeten uitnodigen voor de community. Daar zijn we mee bezig’.

‘We profileren ons niet als expertisecentrum maar juist als verbinder’
Gerlinda de Vries, Community manager.

Elke standaard zijn eigen groep

Op de forums pagina zijn vier groepen te vinden, elk gericht op een andere standaard: PDF, html, Markdown en ODF. De Vries licht toe: ‘Binnen deze groepen kunnen leden vragen stellen, bestanden uitwisselen en de wiki raadplegen. In de toekomst zullen we waarschijnlijk andere groepen toevoegen. Per groep kan er gezocht worden op de verschillende categorieën: organisatie, gebruiker en beleid. Wil je bijvoorbeeld alleen nieuws lezen over PDF en het beleid, dan kan je de categorieën daarop instellen.

Pleio-profiel

Zonder Pleio-profiel kan de website alleen bekeken worden. ‘Om te kunnen reageren of content te schrijven of te delen is het noodzakelijk om een pleio-profiel aan te maken. In het eigen profiel kunnen leden interesses aangeven. Daarbij kunnen ze instellen of ze mail willen krijgen met een periodiek overzicht van alle ontwikkelingen en hoe vaak ze een overzicht willen ontvangen’.

Behoefte

Gevraagd naar waar de behoefte ligt van de leden, vertelt de Vries: ‘We zien dat er vooral veel vraag is naar ervaringen van anderen en manieren om de organisatie te betrekken. Het is niet alleen de verantwoordelijkheid van de communicatieafdeling. Iedereen die content produceert kan zijn steentje bijdragen’.

Hygiënekwestie

Een van de speerpunten van het huidige kabinet is ‘digitale inclusie: iedereen moet kunnen meedoen’. ‘In Nederland zijn er ongeveer vier miljoen mensen met een beperking. Deze groep mensen moet digitaal mee kunnen komen en hebben behoefte aan toegankelijke informatie. Zeker omdat de samenleving steeds verder digitaliseert’, aldus de Vries. ‘Toegankelijk zijn is dan ook eerder een hygiënekwestie, niet alleen een wettelijke verplichting.

De winst van de deze online community is dat we meer bekendheid kunnen geven aan het onderwerp. Niet alleen de bewustwording groeit. De kennis en ervaring die er gedeeld wordt, helpt andere organisaties bijvoorbeeld bij het kiezen van een strategie. Open Documentstandaarden heeft nu 50 leden en we hopen te blijven groeien.

Hondenvoer

‘Uiteraard proberen wij ook ons eigen hondenvoer te eten en we beseffen dat Pleio de toegankelijkheid nog niet helemaal op orde heeft. Pleio staat echter zeer open voor suggesties en verbeteringen en heeft al aangegeven dat ze hier zeker aan gaan werken’, besluit de Vries.

Foto’s: René de Gilde

Het bericht Community Open Documentstandaarden helpt overheden verscheen eerst op Digitale Overheid.

Software: Add Dropbox

← Previous revision		Revision as of 02:03, 18 December 2018
Line 162:		Line 162:
	|title=Corel WordPerfect Office X4 - Standard Edition - Compatible		|title=Corel WordPerfect Office X4 - Standard Edition - Compatible
	|accessdate=3 May 2008}}</ref>		|accessdate=3 May 2008}}</ref>
		+	* [[Dropbox (service)|Dropbox]]
	* [[Evince]]		* [[Evince]]
	* [[Gnumeric]]<ref>{{cite web|url=https://help.gnome.org/users/gnumeric/stable/gnumeric.html#file-format-odf|title=File Formats|author=Eric Baudais & others|publisher=GNOME Documentation Project|work=The Gnumeric Manual, version 1.12|date=February 2014|accessdate=1 February 2018}}</ref>		* [[Gnumeric]]<ref>{{cite web|url=https://help.gnome.org/users/gnumeric/stable/gnumeric.html#file-format-odf|title=File Formats|author=Eric Baudais & others|publisher=GNOME Documentation Project|work=The Gnumeric Manual, version 1.12|date=February 2014|accessdate=1 February 2018}}</ref>

FOSDEM is one of the largest gatherings of Free Software contributors in the world and takes place each year in Brussels (Belgium) at the ULB Campus Solbosch. In 2019, it will be held on Saturday February 2, and Sunday February 3.

The Open Document Editors DevRoom is scheduled for Saturday, February 2 (from 10:30AM to 7:00PM, room UB2.147).

We are inviting proposals for talks about Open Document Editors or the ODF standard document format, on topics such as code, localization, QA, UX, tools, extensions and adoption-related cases. Please keep in mind that product pitches are not allowed at FOSDEM.

The length of talks should be limited to a maximum of 25 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. You may be assigned LESS time than you request.

All submissions have to be made in the Pentabarf event planning tool: https://penta.fosdem.org/submission/FOSDEM19.

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 in Pentabarf).

To submit your talk, click on “Create Event”, then make sure to select the “Open Document Editors” devroom as the “Track”. Otherwise, your talk will not be even considered for any devroom at all.

If you already have a Pentabarf account from a previous year, even if your talk was not accepted, please reuse it. Create an account if, and only if, you don’t have one from a previous year. If you have any issues with Pentabarf, please contact ode-devroom-manager@fosdem.org.

The deadline is Monday, December 24, 2018. Accepted speakers will be notified by Thursday, December 27, 2018. The schedule will be published on Monday, December 31, 2018.

Recording Permission

We will record and stream all main tracks, devrooms and lightning talks live. The recordings will be published under the same licence as all FOSDEM content (CC-BY). If, exceptionally, you believe there is a legitimate reason why your presentation should not be streamed or recorded, you must seek our agreement before submitting it.

In the “Submission notes” field, please indicate that you agree to have your presentation recorded and published under the same license as all FOSDEM content (CC-BY). For example: “If my speech is accepted for FOSDEM, I hereby agree to be recorded and to have recordings – including slides and other presentation related documents – published under the Creative Commons Attribution (CC-BY) 4.0 International License. Sincerely, Name”.

A picture of contributors attending LibOCon in Tirana, during a break. Most of them could travel to Albania thanks to the economic resources made available by our generous donors. Consider a donation to LibreOffice, to support our contributors traveling to events to talk about LibreOffice and ODF: https://www.libreoffice.org/donate

Many companies around the world use free and open source software (FOSS) to reduce costs, improve reliability, and free themselves from vendor lock-in. Today we talk to Iwan Tahari from FANS, an Indonesian shoe manufacturer, which has migrated to GNU/Linux and LibreOffice:

Firstly, tell us about your company, and your role in it…

I work at the FANS shoes factory in Tangerang, Indonesia. Our company has produced FANS shoes since 2001. As an Operation Director, I have to maintain smooth operation in the whole process, to improve our product quality and services. Currently, we have remote offices in Medan, Palembang, Surabaya and Solo that connect directly to our factory in Tangerang. All of our offices use free and open source software for daily operations.

When did you decide to migrate to open source software – and why?

We started to introduce FOSS to our staff in 2007 by dual-booting MEPIS Linux and Microsoft Windows XP on one out of three PCs that we had. It was a complete failure; the users almost never booted into MEPIS. Learning from the past mistakes, in 2012 we did a partial migration with five new notebook PCs installed with Linux Mint 13, for all managers and some higher-level staff members. Seven old PCs were still running Windows XP.

In 2013, we migrated almost all of the PCs to FOSS – only one Windows PC was left in the research and development department, because it was still using Corel Draw. In March 2014, we had a special training for using Inkscape, a vector graphics program. After the training, we fully migrated to FOSS. As of today, we still use only FOSS in all of our operations.

The main reason we migrated to FOSS was to have reliable and stable operations. Around 2012-2013, there was a nasty computer virus in Indonesia called Brontok. The main anti-virus programs were not fast enough to handle the widespread attack, so the only way to fix it was to reinstall the operating system.

This was so bad because of the high downtime in the reinstallation process. The only PCs that were not affected were Linux-based PCs. Since we migrated to FOSS, we have never reinstalled the operating system because of viruses or malware, even though we never use anti-virus software on our Linux-based PCs.

The other reason we use FOSS is cost-saving. Proprietary licenses are very costly; for each application we have to purchase separate licenses for each machine, while with FOSS the programs are completely free and we can install them on as many machines as we want. Our company has saved 133 millions Rupiah by using FOSS (around USD 10,000).

Tell us about your initial experiences with FOSS…

My first experience with open source software as when I was a university student. I graduated from CalPoly (California Polytechnic State University) in San Luis Obispo. My major is MIS (Management of Information Systems). One of our computer classes introduced us to Red Hat Linux. Honestly, I didn’t have a good experience with it (I believe it was Red Hat 4.0).

It took a long time and it was very complicated just to install the OS on an early Pentium machine (just to get the display to work correctly, and the configuration was really difficult for a regular user too). Well, it had a GUI, and some applications like AbiWord and Gnumeric but it was painfully slow. So at that time I believed that open source software was not for a regular users.

After I graduated, I worked in the logistics department of PT. Rodamas Jakarta (a nation-wide distribution company). One day, I saw InfoLinux magazine (a local Indonesian magazine that focuses on open source software) in the IT department. The magazine had a lot of good articles, and it came with a CD/DVD that contained a variety of Linux distributions. I also subscribed to this magazine. I become more interested in the open source world, and tried several live distributions like Knoppix without installing the OS.

Some came with OpenOffice which was similar to Microsoft Office. I liked OpenOffice better than Gnumeric and Abiword. My wife used to work in Haga Bank (a local Indonesian bank now acquired by Rabobank). Her office was using Fedora Linux and OpenOffice for daily operations without any critical problems. Learning from her experiences, when I became Operation Director at FANS shoes, I started the FOSS migration.

Why did you choose LibreOffice?

Because most Linux distros thesedays come with LibreOffice. It’s better to use the office suite that comes with the distro; it saves us time, as we don’t have to install another suite. For our company, LibreOffice is the best replacement for Microsoft Office. If there were no LibreOffice, we would probably have never migrated to FOSS.

I have an interesting story about LibreOffice: one time, my brother called me to ask for some help with his computer. He said he had received a Microsoft Office document file (docx), but he couldn’t open it. Unfortunately, his computer had an outdated OS and MS Office (Windows XP and Office XP).

He said that it’s urgent, that he needed to read the content of this document now. Well, it was late at night, so he was not able to get the installer from the computer store. So I said to him, try downloading LibreOffice, and see if it can open the file. So, he installed LibreOffice in his PC. He was really fortunate that the docx file could be opened with just a little problem (the text was not aligned properly), but at least it was readable. Since then, his computer has LibreOffice, and he continues to use it.

How popular is FOSS in Indonesia?

Open source in Indonesia is getting more popular. In the server market, open source solutions are growing rapidly here because they are cheaper than proprietary software. Unfortunately, it is not the same for daily home or office use of FOSS. Proprietary software like Windows, Office, Adobe suite, Corel Draw etc. are so dominant here. People are already familiar with these proprietary programs and are hesitate to change. Piracy is the main cause of the slow growth of FOSS in Indonesia – currently, there are more people using pirated software than original legal software.

It is very easy to get pirated software in Indonesia. It can be acquired at many computer stores – and sometimes it is included for free when purchasing a PC. So in fact, it’s much easier to get pirated software than FOSS. Still, our government is a little bit strict with pirated software in medium and large companies. Because of that, some companies have adopted FOSS. So I believe Free Software will keep continue to grow in Indonesia, but the adoption rate of FOSS will depend on the how good its marketing is, and also how strict the law enforcement of pirated software is as well.

What were your personal experiences in the Indonesian open source community?

At the early stage of the FOSS migration, I pretty much did everything by myself. I learned FOSS mostly from the web. Fortunately, most FOSS literature is available in the English language, which I can understand. In our company, the LibreOffice migration was a lot easier compared with migrations to other programs like Inkscape and GIMP. At first, we were having trouble migrating to Inkscape until we met Sokhibi (owner of Istana Media, and writer of several open source books).

We invited him to train us using Inkscape. From there, he introduced us to Blankon Linux (a custom Indonesian Linux distro). He was the Documentation Coordinator of Blankon Linux. Then the Blankon community helped us a lot in our migration – we even have a custom version of Blankon Linux specifically for our company needs.

Together with Ahmad Haris (Blankon Public Relation Coordinator), we created a writing contest for using FOSS, and we released an Indonesian Inkscape guidebook. In 2015, we had the GNOME Asia Conference in Indonesia – this was my first time being a guest speaker at a FOSS conference. I met so many excellent people from around the world that were helping the FOSS movement! I was introduced to other local open source communities (such as openSUSE Indonesia, Ubuntu Indonesia, the Indonesian Linux User Group etc).

Since then, I have been active with our local FOSS community, and our company has sponsored several FOSS activities/projects. In 2018, we held an Indonesian conference for LibreOffice. It was a big success, so many people are eager to know about the software. Sokhibi also released an Indonesian LibreOffice Writer guide, which is sponsored by our company.

The LibreOffice project was born in Europe, and had strong roots in that continent. What should we do to increase the market penetration in Indonesia?

It should be easy for LibreOffice to become more widespread in Indonesia. Most Linux distributions already include LibreOffice, so it’s no problem for Indonesian Linux users. Now, the problem is that there are only a small amount of Linux users here. LibreOffice is not known to most Windows users. I think LibreOffice’s marketing community needs to learn/adopt the strategy of Mozilla Firefox in winning the browser war with Internet Explorer. VLC (VideoLan Client) is also another successful open source software that is widely adopted in Indonesia. So these things need to be done:

1. Win the format war with MS Office
2. Local content (tutorial, books for using LibreOffice in Indonesian language) – LibreOffice’s Help needs to be properly translated to Indonesian too
3. LibreOffice videos. We need a lot of videos about LibreOffice tutorials in Indonesian language. LibreOffice Promotion videos. All LibreOffice videos should be available on popular streaming media.
4. Active Indonesian LibreOffice social media (Facebook, Twitter, Instagram,etc) that are helping new users
5. Indonesian LibreOffice ambassadors that are active within the community
6. Reach out program toward schools and companies, and other institutions
7. LibreOffice events, like the 2018 conference in Indonesia are good to penetrate the Indonesian market. Smaller events like release parties or mini conferences are also good. We could have join events with other FOSS projects
8. LibreOffice marketing attribute like stickers, banners, T-shirts, etc
9. Support for other platforms. Fully working LibreOffice for other platforms (ARM, RISC V, MIPS) should be available. The current LibreOffice viewer in Android is not enough. LibreOffice should also be available on emerging market of single-board computer platforms like Rasberry Pi, etc.

Thinking of the culture barrier and language barrier: which is the bigger one for open source?

With better technology, the language barrier will become smaller and smaller. We can now use many translation applications to help people adopt FOSS in many different languages. However, a culture barrier like the “piracy culture” I mentioned is not an easy thing to be solved. Probably it needs several generations of efforts to significantly reduce it. To end piracy, people need to change their mindset which I think is very difficult. We need to fight this piracy culture because it is bad for the whole community. For Indonesia, I believe this is number one enemy to the FOSS movement.

Finally, where do you see LibreOffice in five years from now?

I see great prospects for LibreOffice. In five years, I am sure LibreOffice will be gaining more and more users. The format war will be a long war, but in the end, the Open Document Format (ODF) will win the war. Like the web browser wars where the proprietary browsers are losing, I believe LibreOffice will one day win over MS Office. From version to version, LibreOffice is getting better and better while still retaining format compatibility, which is the key benefit of using LibreOffice. I believe LibreOffice will have a high chance to become the most-used in Indonesia with great efforts. When LibreOffice becomes the number one office suite here, I think all of the remaining South East Asia countries will follow.

Thanks to Iwan for his thoughts and feedback! One of the goals of LibreOffice is to be available in as many languages as possible, so if you’re reading this and want to help translate the interface into your native language see here to get started!

Consider a donation to LibreOffice to help the project produce even more gadgets for volunteer contributors, free software advocates and proud users, to raise the awareness of LibreOffice and Open Document Format (ODF)

The new year at The Document Foundation starts with FOSDEM, where many LibreOffice contributors gather for the largest Free and Open Source Software (FOSS) meeting in Europe. In 2018 we had a booth in the main hall of building K, where most of the largest projects are based, and a devroom focused on OpenDocument Format (ODF) editing software.

The marketing team at TDF was in charge of the booth and the devroom, and also of logistics for the internal meetings and the hackfest organized at ICAB just after FOSDEM. I also helped to cook some real Italian pasta for the social dinner on Saturday, where the community gathered together with some friends.

Just before FOSDEM, we announced LibreOffice 6.0. We coordinated the announcement, drafting the documents for the press kit and organizing several pre briefings with journalists. As usual, thanks to the efforts of localization volunteers we were able to distribute the press release in some local languages.

We then followed up with announcements of minor releases, with a reduced emphasis in comparison with the major announcement.

After FOSDEM, we started working on TDF’s Annual Report, drafting most of the content and illustrations, and collecting images from community events for the final version. We have managed the final layout, using only free software (LibreOffice for drafting text and drawings, GIMP for tweaking images, and Scribus for creating the final layout, using the free fonts Carlito and Caladea).

After releasing the Annual Report, we started to concentrate on the next major announcement, preparing journalist mailing lists. We have a large number of contacts in media outlets around the world, which we have to update regularly.

Mailing lists are key to maintaining regular contacts with journalists. Of course, relationships must be nurtured over time, and the fact that we have always been proactive and responsive has increased our reputation. We have always replied to requests in due time, and pitched new article ideas as often as possible.

We also increased TDF and LibreOffice presence on social media, by increasing the number of tweets and posts. This will further grow in the next few months, as an increasing number of journalists are shifting to social media as the main source of information for news stories.

In early August we announced LibreOffice 6.1, with a test of the increased Twitter activity, based on a policy document that we drafted and shared with community members. We duplicated step-by-step most of the activities from the previous announcement, but we managed to organize a smaller number of pre-briefings.

In addition to these “major” marketing activities, we also managed several background tasks which are useful to keep TDF engine in good shape. The first is keeping track of donations, which provide the economic resources for the project. We are closely following donation trends, and have been implementing A/B testing for the donation page.

Starting from the month of November, this will include fundraising. If we want to bring the project to the next level, we need to raise money to increase the level of support for local communities, and for marketing and education activities behind the OpenDocument Format.

Last, but not least, we warmly invite community members to attend marketing calls. If the schedule is not the right one please let us know, and we will change it to suit your needs. If necessary, we can schedule two different calls to talk with people in different time zones (Asia and the Americas are hard to fit into the same time slot, but we have active community members in both continents).

British IT news outlet The Register looks at the myriad of challenges Apache OpenOffice faces today. From the report: Last year Brett Porter, then chairman of the Apache Software Foundation, contemplated whether a proposed official blog post on the state of Apache OpenOffice (AOO) might discourage people from downloading the software due to lack of activity in the project. No such post from the software's developers surfaced. The languid pace of development at AOO, though, has been an issue since 2011 after Oracle (then patron of the project) got into a fork-fight with The Document Foundation, which created LibreOffice from the OpenOffice codebase, and asked developers backing the split to resign. Back in 2015, Red Hat developer Christian Schaller called OpenOffice "all but dead." Assertions to that effect have continued since, alongside claims to the contrary. Almost a year ago, Jim Jagielski, a member of the Apache OpenOffice Project Management Committee, insisted things were going well and claimed there was renewed interest in the project. For all the concern about AOO, no issues have been raised recently before the Apache Foundation board to suggest ongoing difficulties. The project is due to provide an update this month, according to a spokesperson for the foundation.

Read more of this story at Slashdot.

Software: add MS Office 2019

← Previous revision		Revision as of 18:29, 3 October 2018
Line 173:		Line 173:
	* [[Microsoft Office 2010]] supports ODF 1.1 (Windows only)		* [[Microsoft Office 2010]] supports ODF 1.1 (Windows only)
	* [[Microsoft Office 2013]] supports ODF 1.2 (Windows only)		* [[Microsoft Office 2013]] supports ODF 1.2 (Windows only)
−	* [[Microsoft Office 2016]] supports ODF 1.2 (Windows: read/write; OS X: read-only after online conversion<ref>{{cite web|title=View OpenDocument Format (ODF) files in Office 2016 for Mac|url=https://support.office.com/en-us/article/View-OpenDocument-Format-ODF-files-in-Office-2016-for-Mac-97644726-c089-487c-aac4-07b19fe92cc0|website=Office Support|publisher=Microsoft|accessdate=17 February 2016}}</ref>)	+	* [[Microsoft Office 2016]] and [[Microsoft Office 2019|2019]] support ODF 1.2 (Windows: read/write; OS X: read-only after online conversion<ref>{{cite web|title=View OpenDocument Format (ODF) files in Office for Mac|url=https://support.office.com/en-us/article/view-opendocument-format-odf-files-in-office-for-mac-97644726-c089-487c-aac4-07b19fe92cc0|website=Office Support|publisher=Microsoft|accessdate=3 October 2018}}</ref>)
	* [[Microsoft OneDrive]] / [[Office Web Apps]]<ref>{{cite web|last=Foley |first=Mary Jo |url=http://www.zdnet.com/blog/microsoft/microsoft-adds-odf-support-url-shortening-to-its-skydrive-storage-service/12480 |title=Microsoft adds ODF support, URL shortening to its SkyDrive storage service |publisher=ZDNet |date=17 April 2012 |accessdate=13 August 2012}}</ref>		* [[Microsoft OneDrive]] / [[Office Web Apps]]<ref>{{cite web|last=Foley |first=Mary Jo |url=http://www.zdnet.com/blog/microsoft/microsoft-adds-odf-support-url-shortening-to-its-skydrive-storage-service/12480 |title=Microsoft adds ODF support, URL shortening to its SkyDrive storage service |publisher=ZDNet |date=17 April 2012 |accessdate=13 August 2012}}</ref>
	* [[NeoOffice]]		* [[NeoOffice]]

All rural 1,122 Villages In Nagaland Declared Open Defecation Free  The Sentinel Assam

On the blessed occasion of Gandhi Jayanti, rural Nagaland was declared Open Defecation Free (ODF) on October 2.

Asked to Cut His Speech Short, Puducherry MLA Shouts Back at L-G Kiran Bedi  News18

The government event to mark the Open Defecation Free (ODF) tag achieved by Puducherry, was marred by an on-stage altercation between L-G Kiran Bedi ...

This year’s LibreOffice Annual Conference has been held in Tirana, Albania on September 25 to September 28, 2018. It was organized by a group of independent volunteers from the Open Labs Hackerspace in Tirana.

I will try to give some information about my talks, and share my experience.

Talk Less, Listen More

In these kind of events, I usually tend to propose multiple talks and/or workshops, trying to do as much as possible in a limited time; but since the conference program was full of interesting talks and workshops, I wanted to watch & learn more, and talk less this time. :)

I have attended this year’s conference with two talks, one regular and one lightning.

Talk 1: ODF and LibreOffice Adoption in Turkey: a Status Report

Migration of public institutions to LibreOffice and ODF is going on in Turkey, backed by Turkish Academic Network And Information Center (TUBITAK ULAKBIM). Some ministries, public institutions and municipalities have already completed their migrations to LibreOffice and ODF. Migrations in some institutions are in progress. And many public institutions are waiting in the line. I talked about the history, current status, problems and the future plans of Turkey’s migration to ODF, LibreOffice, GNU/Linux (particularly Pardus) and open source software in general; and tried to answer the questions of the audience.

The reaction of the audience was very positive and encouraging. I got various help/support offers. We have also discussed/brainstormed on ways to ensure the success of the migrations in Turkey, during the Certification Workshop with Lothar Becker, Italo Vignoli, and the other fellow community members. This seems like one of the upsides of having such a great community full of fantastic people. :)

The slides of the presentation on Speaker Deck

Talk 2 (Lightning): Customize Dialog: The Road So Far and the Next Steps

In this lightning talk, I tried to give a quick status report on: What has been done/improved/fixed in the Customize dialog after GSoC 2017 until now; what is the current status, what is left to do, and the future plans.

The slides of the presentation on Speaker Deck

The New MC

I have run for membership of the new Membership Committee of the Document Foundation, and has been elected as a deputy for the next term. It was a pleasure being introduced to the community as part of the MC.

We had a joint meeting with the Board of Directors, and also some private MC meetings.

Must Do’s in Tirana and Some Tips

Tirana is nice and small Balkan city. You can go everywhere on foot or via a bike. Although there are more to do (like a walk to the mountains, or a bike tour to the north), I’ll try to give just a few tips.

Attend a Free Walking Tour

In my last day in Tirana, I attended a free walking tour. It took about 2 hours, and was guided by a nice Albanian named Eri. He showed all of the significant places in the city center, and gave extensive information about these places and the history of Albania & Tirana.

The tour starts at 10am and 6am every day, and the starting point is in front of the Opera house at the Skanderbeg Square. You may give some tip at the end, but there is no pressure to do so; the guide was super polite. You can find more info on their web site.

Eat Traditional Food

They have delicious food, mostly meat, and they use pork extensively; but you also have a lot of other options if you are a vegan or vegetarian.

You might try Era for some traditional food in a small and calm environment.

Bike Sharing

There some bike sharing services in Tirana (like Mobike). You may download their app to your phone, and see/rent the nearest bike. There are separate bike lanes in the main roads.

Buy Tourist SIM

If your GSM service provider also has high roaming prices like the most, then you should definitely get a tourist pack from a Vodafone store as soon as you arrive at Tirana. It costs around 10 EUR for 5GB data plan, 10 min international and plenty of domestic call minutes; and it will be valid for 2 weeks. There is a Vodafone store at the airport.

Avoid Exchange at the Airport

The exchange office at the airport (in the arrival hall) has a bad rate. Try to do your EUR <->LEKE exchanges in one of the offices in the city center. Many stores and taxis will also accept EUR.

Try Daily Tours

If you are going to stay for a longer period, then you might get bored after a while. So taking some daily tours to nearby cities might be a good idea in such a case.

Berat is one of the several options. This 2,413 years-old city, the pride of Albanian architecture which is under the protection of UNESCO, is located 120 km from Tirana.

Some Points of Interest

• Skanderbeg Square
• Opera
• Clock Tower
• Bunkers
• Pyramid
• Et’hem Bey Mosque

The Language

You can speak in English with the most of the younger people in Tirana. Their language (Albanian) is called Shqip. Po means Yes, Yo means No. And here is a survival dictionary.

Overall

It was a great experience overall, with many interesting and illuminating talks from different parts of the world. We have met new friends, and had a good time with the old ones also.

Looking forward to the next LibOCon in Spain!

Despite ‘Open Defecation Free’ status, rural Gujarat still needs lakhs of toilets  The Financial Express

Months after being declared as 'Open Defecation Free' (ODF), Gujarat still has requirement of lakhs of toilets in rural households, according to a reply to an RTI ...

In September 2018 Friends of OpenDocument published the printed edition of the LibreOffice 6.0 Getting Started Guide, written by the LibreOffice Documentation Team. Free PDFs and ODTs are available from the LibreOffice website. Purchase printed copies from our store at Lulu.com.

Designed to run on minimal hardware, Elive is very much a passion project of its leader, Samuel F Baggen. Based on Debian, the first version took a bow in 2005. The second stable version made an appearance in 2010 and it has been a long eight years for the third stable version to become available. The Register: Elive has an impressively low bar to entry, with hardware requirements for the distribution coming in at 256 MB RAM and a 500 MHz CPU, meaning that some very elderly silicon is theoretically going to be able to enjoy the highly polished Enlightenment desktop. "Theoretically" because after The Register took Elive 3.0.0 out for a spin on a relatively low-powered laptop, we'd frankly baulk at running it on anything much slower than a 533MHz Core 2 with at least 512 MB RAM. However, the Enlightenment UI is undeniably an attractive desktop, particularly if a macOS-alike dock is your thing, and runs at an impressive lick even on hardware that lacks graphics acceleration. At its core, Elive is based on the Debian 8 distribution (aka Jessie), using the 3.16 kernel and version 0.17.6 of the Enlightenment X11 Window Manager. It comes replete with a full set of applications, including the ubiquitous LibreOffice and Gimp, along with a variety of productivity and entertainment tools, some of which are Elive's own. Unlike the previous version of Elive, 3.0.0 removes the requirement of donating to the project in order to install the thing locally (although Baggen was quick to tell The Reg that cost-free alternatives existed, but often with annoying processes).

Read more of this story at Slashdot.

Rescuing 1 sources and tagging 1 as dead. #IABot (v2.0beta8)

← Previous revision		Revision as of 20:50, 2 September 2018
Line 216:		Line 216:
	* Information technology companies like [[Apple Inc.]], [[Adobe Systems]], [[Google]], [[IBM]], [[Intel]], [[Microsoft]], [[Nokia]], [[Novell]], [[Red Hat]], [[Oracle Corporation|Oracle]] as well as other companies who may or may not be working inside the OASIS OpenDocument Adoption Technical Committee.		* Information technology companies like [[Apple Inc.]], [[Adobe Systems]], [[Google]], [[IBM]], [[Intel]], [[Microsoft]], [[Nokia]], [[Novell]], [[Red Hat]], [[Oracle Corporation|Oracle]] as well as other companies who may or may not be working inside the OASIS OpenDocument Adoption Technical Committee.
	* Over 600 companies and organizations promote OpenDocument format through The [[OpenDocument Format Alliance]].<ref>{{cite web |url=http://www.odfalliance.org/members.php |title=ODF Alliance members |accessdate=24 May 2009 |work=ODF Alliance |deadurl=yes |archiveurl=https://web.archive.org/web/20090403055912/http://www.odfalliance.org/members.php |archivedate=3 April 2009 |df=dmy-all }}</ref>		* Over 600 companies and organizations promote OpenDocument format through The [[OpenDocument Format Alliance]].<ref>{{cite web |url=http://www.odfalliance.org/members.php |title=ODF Alliance members |accessdate=24 May 2009 |work=ODF Alliance |deadurl=yes |archiveurl=https://web.archive.org/web/20090403055912/http://www.odfalliance.org/members.php |archivedate=3 April 2009 |df=dmy-all }}</ref>
−	* [[NATO]] with its 26 members uses ODF as a mandatory standard for all members.<ref>{{cite web|url=http://www.h-online.com/news/NATO-supports-ODF-open-document-format--/111127|title=NATO supports ODF open document format|first=Stefan|last=Krempl|publisher=The H Open|date=18 July 2008<!--, 15:28-->|accessdate=10 September 2012}}</ref>	+	* [[NATO]] with its 26 members uses ODF as a mandatory standard for all members.<ref>{{cite web|url=http://www.h-online.com/news/NATO-supports-ODF-open-document-format--/111127|title=NATO supports ODF open document format|first=Stefan|last=Krempl|publisher=The H Open|date=18 July 2008<!--, 15:28-->|accessdate=10 September 2012|archive-url=https://web.archive.org/web/20090924190030/http://www.h-online.com/news/NATO-supports-ODF-open-document-format--/111127|archive-date=24 September 2009|dead-url=yes|df=dmy-all}}</ref>
	* The TAC (Telematics between Administrations Committee), composed of e-government policy-makers from the 25 [[European Union]] Member States, endorsed a set of recommendations for promoting the use of open document formats in the public sector.<ref name="ec.europa.eu">{{cite web|url=http://ec.europa.eu/idabc/en/document/3197.html|title=IDA promotes the use of open document formats for e-government interoperability|work=IDA Report 22|date=June 2004|publisher=IDABC|accessdate=10 September 2012}}</ref>		* The TAC (Telematics between Administrations Committee), composed of e-government policy-makers from the 25 [[European Union]] Member States, endorsed a set of recommendations for promoting the use of open document formats in the public sector.<ref name="ec.europa.eu">{{cite web|url=http://ec.europa.eu/idabc/en/document/3197.html|title=IDA promotes the use of open document formats for e-government interoperability|work=IDA Report 22|date=June 2004|publisher=IDABC|accessdate=10 September 2012}}</ref>
	* The free office suites [[Apache OpenOffice]], [[Calligra]], [[KOffice]], [[NeoOffice]] and [[LibreOffice]] all use OpenDocument as their default file format.		* The free office suites [[Apache OpenOffice]], [[Calligra]], [[KOffice]], [[NeoOffice]] and [[LibreOffice]] all use OpenDocument as their default file format.
Line 274:		Line 274:
	** [[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 |archive-url=https://web.archive.org/web/20130402024414/http://www.esop.pt/portugal-publishes-open-standards-catalogodf-pdf-and-several-other-standards-are-mandatory/ |archive-date=2 April 2013 |dead-url=yes |df=dmy-all }}</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 |archive-url=https://web.archive.org/web/20130402024414/http://www.esop.pt/portugal-publishes-open-standards-catalogodf-pdf-and-several-other-standards-are-mandatory/ |archive-date=2 April 2013 |dead-url=yes |df=dmy-all }}</ref>
	** [[Slovakia]]		** [[Slovakia]]
−	** [[Sweden]]<ref>{{cite web |title=Öppna standarder - Programvaror och tjänster 2014 |url=https://www.avropa.se/contentassets/c5e98243c85f4ac997f905555e504f3b/oppna-standarder---programvaror-och-tjanster--v-1.00--20150617.pdf}}</ref>	+	** [[Sweden]]<ref>{{cite web |title=Öppna standarder - Programvaror och tjänster 2014 |url=https://www.avropa.se/contentassets/c5e98243c85f4ac997f905555e504f3b/oppna-standarder---programvaror-och-tjanster--v-1.00--20150617.pdf }}{{Dead link|date=September 2018 |bot=InternetArchiveBot |fix-attempted=yes }}</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 }}</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 }}</ref>
	{{endflatlist}}		{{endflatlist}}

August was a big month for our project, with the release of a brand new version of LibreOffice! And surrounding the release, there was lots of activity in our development, documentation, design, QA and translation communities…

• LibreOffice 6.1 was announced early in the month, with many new features and updates including new icon themes, improved EPUB support, a revamped image handling engine, and the ability to sort anchored images in Calc. Check out the announcement for more details, and this video for a demonstration of the new features:

• The day after the release, we organised an “Ask us Anything” session on Reddit. TDF team and board members, along with community participants, answered questions, responded to ideas, and shared feedback about the new release. The Reddit post has over 33,000 views at the time of writing, so a big thanks to everyone who took part!

• One week later, we looked at some statistics relating to the new version. LibreOffice 6.1 had been downloaded 373,758 times (for comparison, it’s 649,158 now). We had 274,916 visits to our website, 192,232 visits to our blog, and 21,347 impressions of the announcement tweet.

• Meanwhile, the LibreOffice 6.0 branch continues to be maintained, and is recommended for enterprise deployments. Our hard-working documentation community released the LibreOffice 6.0 Writer Guide, with a general introduction to Writer followed by chapters about specific features. It’s available in ODT and PDF formats, and also in hard-copy (printed). If you find the documentation useful, you can give the community a hand!

• Also in August, we showcased the results of the tender to implement of a HSQLDB binary format import in LibreOffice. Tenders are aimed at improving LibreOffice in several strategic areas, and documenting the approach and work carried out, to foster sharing of knowledge and inclusion of the wider volunteer community. Collabora was assigned this specific tender, and our blog post links to technical explanations from developer Tamás Bunth.

• In the middle of the month, we chatted to Sam Tuke, a long-time Free Software supporter and campaigner, who helps the LibreOffice project in marketing and QA (quality assurance). We plan to post regular “Community Member Monday” interviews on this blog, so stay tuned!

• Finally, our Taiwanese community reported back from the “LibreOffice Asia Meetup”, an event held in Taipei. The attendees included LibreOffice and other Free Software community members from Japan, Korea, Indonesia and Taiwan. Franklin Weng, TDF board member and one of the organisers, said: “Besides sharing our experiences of adopting ODF and using LibreOffice, we can also learn from many different countries and help each other”.

Keep in touch – follow us on Twitter, Facebook and Google+. Like what we do? Support our community with a donation – or join us and help us to make LibreOffice even better!

This is the latest release of our powerful open-source Qt component, KD Chart, that allows you to create business charts and much more.

Release Highlights

• Builds with modern Qt versions, at least up to Qt 5.10
• Improves tooltip handling
• Fixes horizontal bar chart
• Uses @rpath for OSX dynamic libraries
• Fixes build on Qt4/ARM

KD Chart makes use of the Qt Model-View programming model that allows re-use of existing data models to create charts. KD Chart is a complete implementation of the ODF (OpenDocument) Chart specification. It now includes Stock Charts, Box & Whisker Charts and the KD Gantt module for implementing ODF Gantt charts into applications.

Read more about KD Chart…

Get KD Chart here.

KD Chart is available under both a free software license (GPL) and a commercial license. The code is exactly the same under both licenses, so which license type you should choose depends on the project you want to use it for.

The post KD Chart 2.6.1 Released appeared first on KDAB.

Community members from five different countries had a good time, and talked about holding a LibreOffice Asia Conference in the future

Event report by: Wally Lian, PR & Marketing Consultant, Software Liberty Association Taiwan

This summer is hot in Taiwan, and so are the FOSS (Free and Open Source Software) communities! From the end of July to the middle of August, there were several big FOSS events in Taiwan. The first one coming on stage was the Debian Conference, which was held in Taiwan and Asia for the first time, and lasted for two weeks. Then, this year three big Asian FOSS events of COSCUP, Gnome Asia Summit, and OpenSUSE Asia Summit decided to merge together and held an event at the National Taiwan University of Science and Technology on 11 and 12 August.

Besides these global and Asian FOSS events, there were also many interesting opportunities and plans going on. One of them was: LibreOffice community members in Asia planned to have a meetup during the joint COSCUP/Gnome Asia/OpenSUSE Asia event, and discussed holding a LibreOffice Asia Conference.

This meetup was held in the evening on 11 August in A+A space, which is a nice and friendly space for FOSS communities, also a community made up of several artists who use FOSS as their tools to create their artwork. The attendees included LibreOffice and other FOSS community members from Japan, Korea, Indonesia and Taiwan.

The organizer, Franklin Weng, the current President of Software Liberty Association Taiwan and current board member of The Document Foundation, said that this meetup was an important milestone. “Now the Taiwanese government is going on adopting the Open Document Format and related office suites. It is very important to link our government and our people with international communities. Besides sharing our experiences of adopting ODF and using LibreOffice, we can also learn from many different countries and help each other,” said Franklin.

At the meetup, Franklin introduced the 30-second animation for LibreOffice Android Viewer, which was generated by LibreOffice Taiwan and A+A Space. He explained that the original idea was to raise the awareness of visual design in FOSS communities. Then he explained the meaning and special Easter eggs hidden in the animation, and showed a “behind the scenes” documentary for it. Then, the host of A+A Space, Michael Wu, introduced the wonderful work from A+A Space, including 3D graphs, 3D models, VR work, classes in universities, and so on.

Then everyone started to share their work and experiences. Rania Amina, who was responsible for visual design in the LibreOffice Conference Indonesia, showed his wonderful artwork to attendees. Ahmad Haris also shared his experiences holding LibreOffice Conference Indonesia, which was a huge success. Shinji Enoki shared the current status of Japanese support in LibreOffice, and many events held in Japan. Daehyun Sung introduced himself and shared some interesting things in Korea, including the system North Korea is using.

Also, Bobby Tung, a senior FOSS member in Taiwan who also contributed a lot to W3C standards, shared the current status of Unicode support for CJK. Kevin Lin, a LibreOffice Migration Professional in Taiwan, showed his work on LibreOffice Online and Web form API usage. Shelandy Ting shared his interesting artwork using Gimp.

After sharing, attendees split into different groups and talked with each other. During this meetup, members from Japan and Indonesia showed interest in holding a LibreOffice Asia Conference. Besides conferences, attendees also exchanged experiences migrating to LibreOffice in organizations and public administrations. We believe that the adoption of the Open Document Format and migrations to LibreOffice will advance hugely in Asia.

A big thanks to the LibreOffice communities in Asia for organising this event! If you love LibreOffice and want to help spread the word in your location or language, check out our native language communities. Together we can help to spread the word about free software and open standards!

Swachh to target open urination too  The Hindu

Under new norms, cities and towns wanting to be declared ODF+ (Open Defecation Free Plus) must also be free of public urination and not just open defecation.

The LibreOffice Documentation Team has published the Writer Guide for version 6.0. It is available for free download (PDF) from the LibreOffice website or can be purchased from the Friends of OpenDocument store at Lulu.com.

The Document Foundation said on Wednesday it is releasing LibreOffice 6.1, the latest major update to its productivity suite. It is available to download for Linux, Windows, and macOS platforms. The new version offers, among other features, Colibre, a new icon theme for Windows based on Microsoft's icon design guidelines, which it says, makes the office suite visually appealing for users coming from the Microsoft environment. The Document Foundation also reworked the image handling feature on LibreOffice to make it "significantly faster and smoother thanks to a new graphic manager and an improved image lifecycle, with some advantages also when loading documents in Microsoft proprietary formats." Other new features and changes include: The reorganization of Draw menus with the addition of a new Page menu, for better UX consistency across the different modules. A major improvement for Base, only available in experimental mode: the old HSQLDB database engine has been deprecated, though still available, and the new Firebird database engine is now the default option (users are encouraged to migrate files using the migration assistant from HSQLDB to Firebird, or by exporting them to an external HSQLDB server). Significant improvements in all modules of LibreOffice Online, with changes to the user interface to make it more appealing and consistent with the desktop version. An improved EPUB export filter, in terms of link, table, image, font embedding and footnote support, with more options for customizing metadata. Online Help pages have been enriched with text and example files to guide the users through features, and are now easier to localize. LibreOffice 6.1's new features have been developed by a large community of code contributors: 72% of commits are from developers employed by companies sitting in the Advisory Board like Collabora, Red Hat and CIB and by other contributors such as SIL and Pardus, and 28% are from individual volunteers. In addition, there is a global community of individual volunteers taking care of other fundamental activities such as quality assurance, software localization, user interface design and user experience, editing of help system text and documentation, plus free software and open document standards advocacy at a local level. You can read the full changelog here. Here's a video that walks through the new features and changes that LibreOffice is receiving with v6.1.

Read more of this story at Slashdot.

Comments

LibreOffice Documentation Team has just released the LibreOffice 6.0 Writer Guide, with a general Introduction to LibreOffice Writer followed by the following chapters: Working with Text (basics), Working with Text (advanced), Formatting Text, Formatting Pages (basics), Formatting Pages (advanced), Print Export Email, Introduction to Styles, Working with Styles, Templates, Images & Graphics, Lists, Tables of Data, Mail Merge, TOCs Indexes Biblios, Master Documents, Fields, Forms, Spreadsheets Charts Objects, Setting Up Writer and Customizing Writer, for a total of 448 pages.

LibreOffice 6.0 Writer Guide is available from TDF Wiki as ODT and PDF, both the complete book and individual chapters, and from ODF Authors as ODT of individual chapters.

LibreOffice 6.0 Writer Guide is also available as a printed book from Lulu, by Friends of Open Document Inc., an Australia-based volunteer organisation with members around the world which will be using profits from the sale to benefit the LibreOffice community.

Rescuing 1 sources and tagging 0 as dead. #IABot (v2.0beta5)

← Previous revision		Revision as of 06:07, 6 August 2018
Line 272:		Line 272:
	** [[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>
	** [[Poland]]<ref>{{cite web |url=http://isap.sejm.gov.pl/DetailsServlet?id=WDU20120000526 |title=Rozporządzenie Rady Ministrów z dnia 12 kwietnia 2012 r. w sprawie Krajowych Ram Interoperacyjności, minimalnych wymagań dla rejestrów publicznych i wymiany informacji w postaci elektronicznej oraz minimalnych wymagań dla systemów teleinformatycznych |publisher=Internetowy System Aktów Prawnych |date= |accessdate=2016-05-17}}</ref>		** [[Poland]]<ref>{{cite web |url=http://isap.sejm.gov.pl/DetailsServlet?id=WDU20120000526 |title=Rozporządzenie Rady Ministrów z dnia 12 kwietnia 2012 r. w sprawie Krajowych Ram Interoperacyjności, minimalnych wymagań dla rejestrów publicznych i wymiany informacji w postaci elektronicznej oraz minimalnych wymagań dla systemów teleinformatycznych |publisher=Internetowy System Aktów Prawnych |date= |accessdate=2016-05-17}}</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>	+	** [[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 |archive-url=https://web.archive.org/web/20130402024414/http://www.esop.pt/portugal-publishes-open-standards-catalogodf-pdf-and-several-other-standards-are-mandatory/ |archive-date=2 April 2013 |dead-url=yes |df=dmy-all }}</ref>
	** [[Slovakia]]		** [[Slovakia]]
	** [[Sweden]]<ref>{{cite web |title=Öppna standarder - Programvaror och tjänster 2014 |url=https://www.avropa.se/contentassets/c5e98243c85f4ac997f905555e504f3b/oppna-standarder---programvaror-och-tjanster--v-1.00--20150617.pdf}}</ref>		** [[Sweden]]<ref>{{cite web |title=Öppna standarder - Programvaror och tjänster 2014 |url=https://www.avropa.se/contentassets/c5e98243c85f4ac997f905555e504f3b/oppna-standarder---programvaror-och-tjanster--v-1.00--20150617.pdf}}</ref>

External links: Move {{Authority control}} to bottom.

← Previous revision		Revision as of 14:49, 3 August 2018
Line 332:		Line 332:
	{{OpenOffice|state=collapsed}}		{{OpenOffice|state=collapsed}}
	{{List of International Electrotechnical Commission standards}}		{{List of International Electrotechnical Commission standards}}
⚫	{{Authority control}}
	{{Document markup languages}}		{{Document markup languages}}
		+
		⚫	{{Authority control}}
	[[Category:OpenDocument]]		[[Category:OpenDocument]]

External links: Add {{Document markup languages}}.

← Previous revision		Revision as of 14:49, 3 August 2018
Line 333:		Line 333:
	{{List of International Electrotechnical Commission standards}}		{{List of International Electrotechnical Commission standards}}
	{{Authority control}}		{{Authority control}}
		+	{{Document markup languages}}
	[[Category:OpenDocument]]		[[Category:OpenDocument]]

Comments

I looked into a migration of the ODFAuthors site to a current Plone version with the data from the website yesterday. It took me a lot of hours to figure out the most easy way to do this. I tried to migrate from LinguaPlone to the new multilingual Plone plug-in first, but without success. I could update the buildout inside a test environment with the new plug-in, but I wasn’t able to migrate the content to the new framework. And even I wasn’t able to get rid of LinguaPlone. I didn’t get the option to remove it. I got always a traceback and found some users that run into the same issue without a solution. Thus I had to change my strategy. I exported the content that I need to migrate, set up a new and clean Plone 4.3.x environment and tried to updated it to the latest version of 4.3. I had to do some editing on the buildout and had to drop some Plone add-ons from the current buildout script of ODFAuthors. Once I had done this the buildout runs fine and I got a clean new Plone environment. Then I added the plug-ins plone.app.contenttypes and Products.contentmigration to the buildout script and run buildout again. I started the Plone instance, created a new Plone site and imported the content (exported from the current ODFAuthors site).
I activated the plug-in plone.app.contenttypes and run the migration scripts from Products.contentmigration. I had to migrate more than 4200 content objects and took a fair amount of time. But in the end the migration from the old Archetype content types to the new Dexterity ones was successful.
The next step would be the migration of the instance from Plone 4.3.x to Plone 5.0.x or 5.1.x.

If the website ODFAuthors should be improved for the future use the first step would be the change of the localization framework from the old LinguaPlone to the current
plone.app.multilingual and migrate and reindex all content objects. It’s not possible to update the site to the latest Plone without that step.
I already created a Plone buildout for an upgraded ODFAuthors website that is based on version 5.1.x. This buildout is available from the Github repository of The Document Foundation: https://github.com/tdf/odfauthors.org

As of today, June 27th, I am no longer working for IBM.  Last quarter’s widely-reported “resource actions” (lay-offs) hit my group and this time my number came up.

It was a good run, 27 years with one company, something that is not so common today.

Fresh out of Harvard I started working at Lotus Development Corporation in Cambridge, Massachusetts, initially doing technical support, including for the Lotus 1‑2-3 C-language developer toolkit.  From there I worked in support’s application development team, developing and maintaining our internal information retrieval system, a hodgepodge of a DOS user-interface, a search engine (using a Bayesian inference network) and a fax-on-demand system, all over NetBIOS.

From support I transitioned over to development, to the SmartSuite team, where I first focused on Freelance Graphics, which was transitioning from C to C++, Windows and OS/2, then on a set of Windows ActiveX controls called eSuite DevPack, some Java components and attempts at an office suite running on a Java-based “thin client” or network computer (eSuite Workplace.)  It was a time when the thinking, at least in my little part of the world, was that the traditional desktop applications were dead, and all future work would be done in Java running on your desktop web browser. From this came the browser wars.

Then, in 1995, IBM came a knocking and bought Lotus.  Our focus, naturally, shifted from desktop to server-based computing, from Java applets to Java servlets.  I worked on various projects, from the K-Station Portal (based initially on Domino) to the Apache Xalan XSLT engine to XForms to WebSphere Portal.  I developed a framework for document conversions within WebSphere Portal that we called Document Conversion Services (DCS).

Then, one day, I got an odd call, out of the blue, a very senior person asking whether I was familiar with the file formats from SmartSuite and Microsoft Office.  Evidently, no one else in the company would admit to having that arcane knowledge.  So, I was drafted onto a “special project,” with a few other talented engineers, a real fun group working on various stealthy tasks, the details of which I am still not at liberty to discuss.

Somewhat overlapping the above, I worked on the things that readers of this blog will be more familiar with, the development of the OpenDocument Format (ODF) standard at OASIS and ISO, and the arguments against ISO ratification of Microsoft’s Office Open XML (OOXML) file format.  This then overlapped, in part, with my work to establish the OpenOffice project at Apache, based on Oracle’s contribution, to get IBM Symphony contributed as well, and to bring those two efforts together.

Those years were among the most memorable of my career.  I was able to work with a lot of talented and enthusiastic people, within IBM, of course, but also at other companies, with non-profits, with academia and government.  I was able travel and see parts of the world I might never have otherwise seen, speak to a lot of audiences about the importance of open standards.  I even testified to a few legislative committees.  My business travels took me to Brussels, Berlin, Budapest, Barcelona, Granada, London, Paris, Lyon, Rome, Orvietto, Geneva, Amsterdam, the Hague, Beijing, Seoul and Johannesburg.  It was a lot of hard work, but it was meaningful. Open standards and open source matter.  I have many fond memories of those years.

Eventually, however, corporate interest in document editors, document standards, “social documents” and similar initiatives fizzled, and I no longer had support for remaining involved in ODF and OpenOffice.  I needed to move on, to find a new gig.

I looked internally within IBM for something that would combine my hard technical skills and my soft skills, including working closely with attorneys, an ability to “meet them half way” when discussing complicated legal/technical topics.  Since I’ve been an active inventor throughout my IBM career, with 54 patents to my name, and a good head for reading and analyzing patents, I spent a few years working as a patent engineer, helping to monetize IBM’s vast patent portfolio, developing technical evidence for infringement, identifying possibilities for patent licencing and assignment, etc.

That’s where things stood as of today, when I handed in my badge and laptop.

As for what is next, I honestly cannot yet say what “Rob 2.0” will be.  I plan on taking some time to mull things over and explore my options.

One thing I do plan to do, relatively soon, is start a new blog, a fresh start, on a new path at this domain, preserving this older blog at its current (/blog) URL.

Donations to The Document Foundation are used for many purposes, such as organising events, maintaining our infrastructure, and paying a small team to handle QA, marketing, documentation and other tasks. But donations are also used to fund tenders, whereby companies and individuals improve LibreOffice in specific areas and share knowledge with the community.

One such tender was posted in May 2017: “improve image handling in LibreOffice (#201705-01)“. When images are used in LibreOffice documents, the software manages them in a “life-cycle” which includes importing, displaying, modifying, exporting and more. To save memory – especially with large documents – images that are not currently on screen are sometimes moved out of memory and saved onto disk in a technique known as “swapping” or “paging”. The goal of the tender was to improve LibreOffice in these areas, making it more efficient at handling images and modernising the code base.

Collabora was selected to implement the tender; the work is now complete, and it will benefit all users in the upcoming LibreOffice 6.1 (due to be released in early August). Here are some technical notes about what was improved in the source code of LibreOffice, and what was achieved.

Problems with the image life-cycle

Currently, when an image is read from a document, a GraphicObject is created for the image and handled over to the GraphicManager which manages the life-cycle. When this happens we usually get back the string based unique ID of the GraphicObject with which we can always get access the image by creating a new GraphicObject with the unique ID (GraphicManager will look for the image with that unique ID).

Usually the unique ID is the one that is passed on between layers in LibreOffice (for example, from the ODF filter when loaded, to the model, where it is manipulated and then to the OOXML filter when saving) but the unique ID itself is just a “reference” to the image and by itself it doesn’t have any control over when the image can safely be removed and when not. It could happen that in a certain situation we would still have the unique ID referenced somewhere in the model, but the image would already be removed. This is dangerous and needs to be changed.

Usually for this kind of object we use a reference counting technique, where we pass an object around that holds a reference to the object resource. When the object is created, the reference count is increased; when destroyed, the reference count is decreased; when the reference count reaches zero, the resource object is destroyed.

The solution for the life-cycle

So instead of passing around a unique ID, the idea is to use the usual reference counting technique, which is normally used in this situation. The GraphicObject is mainly a wrapper around Graphic (which then holds a pixel-based image, or animated image, or possibly a vector image), and in addition it keeps additional attributes (gamma, crop, transparency etc.). It also has the implementation of swapping-in and out.

On the other hand, Graphic is properly reference-counted already (Graphic objects are reference counting the private ImpGraphic) so the solution to the life-cycle problem is that instead of GraphicObject unique ID, we would just pass along the Graphic object instead, or XGraphic, XBitmap which are just UNO wrappers around Graphic. Potentially we could also pass along the GraphicObject or XGraphicObject (UNO wrapper for the GraphicObject) when we would need to take into account the graphic attributes too. This should make the life-cycle much more manageable.

GraphicObject refactoring

GraphicObject and the implementation of XGraphicObject (UnoGraphicObject) and XGraphic (UnoGraphic) were located in module svtools, which is hierarchically above vcl. This is problematic when creating new instances like in Graphic.GetXGraphic method, which needs to bend backward to make it even work (ugly hack by sending the pointer value as URL string to GraphicProvider). The solution to this is to move all GraphicObject related things to vcl, which surprisingly didn’t cause a lot problem and once done, it looks like a much more “natural” place.

Managing memory used by images

Previously, the memory managing was done on the level of GraphicObjects, where a GraphicManager and Graphic-Cache were responsible to create new instances from uniqueID and manage the memory usage that GraphicObject take. Here’s the hierarchy before refactoring:

This is not possible anymore as we don’t operate with uniqueIDs anymore, but always use Graphic and XGraphic objects (in UNO), so we need to manage the creation of Graphic object or more precisely – ImpGraphic (Graphic objects are just reference-counted objects of ImpGraphic).

So to make this possible GraphicManager and GraphicCache need to be decoupled and removed from GraphicObject and a new manager needs to be introduced between Graphic and ImpGraphic, where the manager controls the creation and accounts for the memory usage:

Graphic swapping and swapping strategy

The new swapping strategy is relatively simple – if a lot of memory is needed by graphic objects in a certain time, we let it use it and don’t try to over-aggressively try to free it. In the past this cased swap-out and swap-in cycle that made the application completely unusable. In the future, external hints when a certain Graphic object can be swapped out may be added, so we can perform swapping more effectively. There are also several other ideas which will increase performance and reduce memory usage that can be implemented now with the new hierarchy where most all of the swapping is contained inside the Graphic itself, but all of this is currently out of the scope of this work.

In conclusion

Thanks to Collabora and TomaĹž Vajngerl for their work on this. Although the details are highly technical, the end result is a faster and more robust office suite. If you’re an end user of LibreOffice and your documents include lots of images, you will be able to enjoy the benefits of this work in future releases, starting with LibreOffice 6.1.

From worst performer to best, Uttar Pradesh now aims to achieve ODF status a year before the national target  OpIndia

from 47% a year ago to 74% now in rural household toilet coverage, UP had literally turned its swachhta mission achievements around.

I worked very hard on the new Plone buildout for the ODFAuthors website during the last days. I nearly finished the buildout today. I created a new policy and a theming product for the site. I added a template for the frontpage of the new website and am waiting for the input about the content, that the new frontpage should show.

I also need some suggestions on the new publication workflow of the site. The Plone workflow tool is able to run very subtle grained ones.  The Plone Content Management System is also able to send automatic messages on all events like changing the workflow state.

Re-inserting line which seems to have been deleted in error

← Previous revision		Revision as of 11:46, 17 June 2018
Line 219:		Line 219:
	* The TAC (Telematics between Administrations Committee), composed of e-government policy-makers from the 25 [[European Union]] Member States, endorsed a set of recommendations for promoting the use of open document formats in the public sector.<ref name="ec.europa.eu">{{cite web|url=http://ec.europa.eu/idabc/en/document/3197.html|title=IDA promotes the use of open document formats for e-government interoperability|work=IDA Report 22|date=June 2004|publisher=IDABC|accessdate=10 September 2012}}</ref>		* The TAC (Telematics between Administrations Committee), composed of e-government policy-makers from the 25 [[European Union]] Member States, endorsed a set of recommendations for promoting the use of open document formats in the public sector.<ref name="ec.europa.eu">{{cite web|url=http://ec.europa.eu/idabc/en/document/3197.html|title=IDA promotes the use of open document formats for e-government interoperability|work=IDA Report 22|date=June 2004|publisher=IDABC|accessdate=10 September 2012}}</ref>
	* The free office suites [[Apache OpenOffice]], [[Calligra]], [[KOffice]], [[NeoOffice]] and [[LibreOffice]] all use OpenDocument as their default file format.		* The free office suites [[Apache OpenOffice]], [[Calligra]], [[KOffice]], [[NeoOffice]] and [[LibreOffice]] all use OpenDocument as their default file format.
		+	* Several organisations, such as the [https://web.archive.org/web/20071027064136/http://opendocumentfellowship.com/ OpenDocument Fellowship] and [http://opendocsociety.org/ OpenDoc Society] were founded to support and promote OpenDocument.
	* 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= https://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= https://wikimediafoundation.org/wiki/Wikis_Go_Printable | title= Wikis Go Printable | work= [[Wikimedia Foundation]] | date= 13 December 2007 | accessdate= 31 December 2007}}</ref>