Planet ODF

December 04, 2018

The Document Foundation Planet

Official TDF Blog: Fundraising, December 4

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)

December 04, 2018 07:34 AM

October 25, 2018

The Document Foundation Planet

Official TDF Blog: Marketing Activities, January to September 2018

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

October 25, 2018 07:00 AM

October 11, 2018

Slashdot

Apache OpenOffice, the Schrodinger's Application: No One Knows If It's Dead or Alive, No One Really Wants To Look Inside

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.

by msmash at October 11, 2018 05:20 PM

October 03, 2018

ODF Wikipedia Page

Lonaowna: /* Software */ add MS Office 2019

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]]

by Lonaowna at October 03, 2018 06:29 PM

October 02, 2018

The Document Foundation Planet

Muhammet Kara: Recap: LibOCon18 & Tirana

Group photo from LibOCon18 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.

Screenshot of LibreOffice Customize Dialog

The slides of the presentation on Speaker Deck

The New MC

The new MC of TDF 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

Tirana

  • 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!

by Muhammet Kara (muhammetk@gmail.com) at October 02, 2018 12:00 AM

September 23, 2018

The Document Foundation Planet

Miklos Vajna: odfsig: an Open Document Format (ODF) digital signatures tool

I created a toy project to experiment with a few technologies I wanted to try out (cmake, googletest, xmlsec outside LibreOffice, libzip and AppVeyor). The result is a tool with a similar interface as pdfsig from poppler (for PDF files), just for ODF: a cmdline executable to verify the digital signature(s) in an ODF document.

The source code now has CI on Linux and Windows, so perhaps in a shape that is interesting for others to have a look as well. And if not, then no problem, it was interesting to put together these building blocks and see them working as expected. :-)

September 23, 2018 09:58 PM

September 19, 2018

The Document Foundation Planet

Jean Hollis Weber: LibreOffice 6.0 Getting Started Guide published

Cover of Getting Started with LibreOffice 6.0In 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.

September 19, 2018 09:06 AM

September 11, 2018

Slashdot

Linux Distro Elive Emerges Alive After 8-Year Hibernation

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.

by msmash at September 11, 2018 05:20 PM

September 02, 2018

ODF Wikipedia Page

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

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}}

by InternetArchiveBot at September 02, 2018 08:50 PM

August 30, 2018

The Document Foundation Planet

Official TDF Blog: LibreOffice monthly recap: August 2018

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:

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.

  • 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!

August 30, 2018 01:02 PM

August 28, 2018

Planet KDE

KD Chart 2.6.1 Released

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.

by KDAB on Qt at August 28, 2018 11:38 AM

August 26, 2018

Oregon Dept. of Forestry announces gate closures for hunting seasons - Tillamook County Pioneer

Oregon Dept. of Forestry announces gate closures for hunting seasons  Tillamook County Pioneer

The Oregon Department of Forestry (ODF) will resume road restrictions this fall in the western part of the Tillamook State Forest to improve deer and elk ...

August 26, 2018 07:00 AM

August 22, 2018

The Document Foundation Planet

Official TDF Blog: LibreOffice Asia Meetup in A+A Space, Taipei, Taiwan

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.

Before the meetup started, SLAT and A+A Space prepared a lot of food

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.

During the meetup

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.

Mark Hung (Left 1st), Bobby Tung (Left 2nd) from Taiwan, Shinji Enoki (Right 2nd) from Japan, and Daehyun Sung (Right 1st) from Korea.

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!

August 22, 2018 03:06 PM

August 21, 2018

The Document Foundation Planet

Jean Hollis Weber: Writer 6.0 Guide published

Writer Guide 6.0 coverThe 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.

August 21, 2018 01:41 AM

August 08, 2018

Slashdot

LibreOffice 6.1 Released

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.

by msmash at August 08, 2018 02:40 PM

HackerNews

August 06, 2018

The Document Foundation Planet

Official TDF Blog: LibreOffice 6.0 Writer Guide

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.

August 06, 2018 10:27 AM

ODF Wikipedia Page

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

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>

by InternetArchiveBot at August 06, 2018 06:07 AM

August 03, 2018

ODF Wikipedia Page

Skim: /* External links */ Move {{Authority control}} to bottom.

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]]

by Skim at August 03, 2018 02:49 PM

Skim: /* External links */ Add {{Document markup languages}}.

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]]

by Skim at August 03, 2018 02:49 PM

July 05, 2018

The Document Foundation Planet

Miklos Vajna: Improved ECDSA handling in LibreOffice

I wrote about ECDSA handling in LibreOffice last year, back then the target was to be able to verify signatures using the ECDSA algorithm on Linux.

Lots of things happened since then, this post is meant to summarize those improvements. My personal motivation is that Hungarian eID cards come with a gov-trusted ECDSA (x509) cert, so handling those in LibreOffice would be nice. My goals were:

  • platforms: handling Windows as well, not only Linux/macOS

  • operations: handling signing as well, not only verification

  • formats: cover all of ODF, OOXML and PDF

Let’s see what has happened:

  • Linux, ODF, sign: we had hardcoded RSA algorithm when generating a signature, now we infer the sign algorithm from the signing cert algorithm (commit)

  • Linux, OOXML, sign: same problem with hardcoded RSA (commit)

  • Windows, PDF, sign: the certificate chooser had to be ported to from CryptoAPI to CNG (commit)

  • Windows, ODF, verify / sign: this was the largest problem, this required a whole new libxmlsec backend (interface, implementation, all in C90) and also required conditionally using that new backend in LibreOffice (commit)

  • Windows, OOXML, sign: this was almost functional, except that the UI recently regressed, now fixed (commit)

  • Finally now that everything is ported on Windows to use CNG, I could enable it by default yesterday.

I could test hardware-based signing after this, which was fine out of the box on both platforms. Some screenshots:

  • Linux:

https://farm2.staticflickr.com/1784/29321634078_8818b2d7ba_o.png
  • Windows:

https://farm1.staticflickr.com/927/42288765505_db72ee48f2_o.png

(There is no reason why this would not work on macOS, but I did not test that.)

Thanks Gabor Kelemen who helped me to get a sane card reader that has reasonable driver support on Linux.

All this is available in master (towards LibreOffice 6.2), or you can grab a daily build and try it out right now. :-)

July 05, 2018 07:08 AM

July 02, 2018

HackerNews

June 30, 2018

The Document Foundation Planet

Andreas Mantke: First Research On The Migration Of ODFAuthors With Current Data

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.

June 30, 2018 09:51 AM

June 28, 2018

The Document Foundation Planet

Andreas Mantke: First Step To Improve ODFAuthors

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

June 28, 2018 09:45 PM

June 27, 2018

An Antic Disposition

Downsized

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.

by Rob at June 27, 2018 03:16 PM

June 19, 2018

The Document Foundation Planet

Official TDF Blog: Image handling rework for LibreOffice – Collabora’s tender results

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.

June 19, 2018 08:43 AM

June 17, 2018

The Document Foundation Planet

Andreas Mantke: New Buildout For ODFAuthors Nearly Finished

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.

June 17, 2018 07:00 PM

ODF Wikipedia Page

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

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>

by ClareTheSharer at June 17, 2018 11:46 AM

June 12, 2018

ODF Wikipedia Page

GermanJoe: /* Software */ rmv - nn / WP:EL

Software: rmv - nn / WP:EL

← Previous revision Revision as of 13:31, 12 June 2018
Line 155: Line 155:
 
* [[Adobe Buzzword]]<ref>{{cite web|url=http://labs.adobe.com/technologies/buzzword/ |title=Adobe Buzzword online word processor from Acrobat.com |publisher=Labs.adobe.com |date= |accessdate=19 May 2009}}</ref>
 
* [[Adobe Buzzword]]<ref>{{cite web|url=http://labs.adobe.com/technologies/buzzword/ |title=Adobe Buzzword online word processor from Acrobat.com |publisher=Labs.adobe.com |date= |accessdate=19 May 2009}}</ref>
 
* [[Apache OpenOffice]]
 
* [[Apache OpenOffice]]
* [[Atlantis Word Processor]]<ref>{{cite news|url=http://www.atlantiswordprocessor.com/en/news/1_6_5.htm|title=Atlantis Word Processor 1.6.5 release notes (at the Wayback Machine)|work=atlantiswordprocessor.com|accessdate=2018-02-01|deadurl=yes|archiveurl=https://web.archive.org/web/20160326160635/http://www.atlantiswordprocessor.com/en/news/1_6_5.htm|archivedate=26 March 2016|df=dmy-all}}</ref>
 
 
* [[Bean (software)]]
 
* [[Bean (software)]]
 
* [[Calibre (software)|Calibre]] [[E-book|ebook]] viewer, converter, editor, and manager
 
* [[Calibre (software)|Calibre]] [[E-book|ebook]] viewer, converter, editor, and manager
Line 182: Line 181:
 
* [[Scribus]] imports .odt and .odg
 
* [[Scribus]] imports .odt and .odg
 
* [[SoftMaker Office]]
 
* [[SoftMaker Office]]
* [http://www.SQLiQuery.com SQL iQuery for IBM i] (output support)
 
 
* [[Sun Microsystems]] [[StarOffice]]
 
* [[Sun Microsystems]] [[StarOffice]]
 
* [[TextEdit]]
 
* [[TextEdit]]

by GermanJoe at June 12, 2018 01:31 PM

GermanJoe: /* Support for OpenDocument */ rmv - unsourced spam / WP:EL

Support for OpenDocument: rmv - unsourced spam / WP:EL

← Previous revision Revision as of 13:29, 12 June 2018
Line 221: Line 221:
 
* 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 [http://www.oidi.org OIDI.org] (Open Interoperative Document Initiative) is committed to encouraging efforts by governments at all levels, around the globe, to implement changes necessary to ensure public documents are open and interoperable and thus available to all citizens/residents without the need for specific vendor software. -->
 
 
* The UK government has adopted ODF as the standard for all documents in the UK civil service<ref>{{cite web | url=https://www.gov.uk/government/news/open-document-formats-selected-to-meet-user-needs|title=Open document formats selected to meet user needs}}</ref>
 
* The UK government has adopted ODF as the standard for all documents in the UK civil service<ref>{{cite web | url=https://www.gov.uk/government/news/open-document-formats-selected-to-meet-user-needs|title=Open document formats selected to meet user needs}}</ref>
 
* The [[Wikimedia Foundation]] supports ODF export from [[MediaWiki]], which powers [[Wikipedia]] and a number of other Internet [[wiki]]-based sites.<ref>{{cite web | url= 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>

by GermanJoe at June 12, 2018 01:29 PM

June 08, 2018

The Document Foundation Planet

Andreas Mantke: Creating A New Plone Development Environment

I worked on the first bits for a new Plone development environment. I’ll use this to create a new website for the ODFAuthors team. The new site should run on Plone 5.1 or later. Maybe it is possible to upgrade the site to a Plone version that runs on Python 3.

I read already on a blog of a Plone developer that Core-Plone is already ported to Python 3, but that there are a big bunch of tests that are not yet ported and need some love (and work time).

June 08, 2018 09:04 PM

June 05, 2018

The Document Foundation Planet

Miklos Vajna: Editing ReqIF-XHTML fragments in LibreOffice Writer

I worked on a small feature to use Writer as an editor for the XHTML fragments inside Requirements Interchange Format (ReqIF) files. First, thanks to Vector for funding Collabora to make this possible.

Writer already supported XHTML import and export before (see my previous post) as a special mode of the HTML filter, this work builds on top of that. The main speciality around XHTML as used for fragments inside a ReqIF file is embedded objects.

The special mode to opt-in for ReqIF-XHTML behavior can actived like this:

  • during import: --infilter="HTML (StarWriter):xhtmlns=reqif-xhtml"

  • during export: -convert-to "xhtml:HTML (StarWriter):xhtmlns=reqif-xhtml"

Three different cases are handled:

  1. Image with native data we don’t understand and just preserve.

  2. Image with OLE2 data, which we hand out to external applications (at least on Windows). On the above video this is an embedded PPSX file, handled by PowerPoint.

  3. Image with ODF data, which we handle internally. This is a Draw document on the above video.

Regarding how it works, the import is a series of unwrapping containers till you get to the real data and the export is the opposite of this. Here are the layers:

  • Larger ReqIF files have the .reqifz extension, and are ZIP files containing an XML file, having the XHTML fragments. This is not relevant for this post, as Writer assumes that extracting the XHTML fragment from ReqIF is done before you load the content into Writer.

  • XHTML always has a PNG image for the object, and optionally it has RTF as native data for the object.

  • The RTF file is a fragment, containing just an embedded OLE1 container.

  • The OLE1 container is just a wrapper around the real OLE2 container.

  • The OLE2 container either has the data directly or MSO has a convention on how to include OOXML files in it (see the PPSX example above), and we handle that.

On export we do the opposite: save the file, put it into OLE2, then into OLE1, then into RTF, finally into XHTML.

There is no specification on how to put ODF files into OLE2, so I extracted the relevant code from LibreOffice’s binary MSO filters and now the Writer HTML filter uses that as well. This avoids code duplication and also could avoid inventing some new markup this way.

All this is available in master (towards LibreOffice 6.2), or you can grab a daily build and try it out right now. :-)

June 05, 2018 08:43 AM

May 24, 2018

Slashdot

Robin "Roblimo" Miller, a Long-Time Voice of the Linux Community, Has Passed Away

Reader rootmon writes: Our thoughts/prayers are with the family and friends of long time open source writer/journalist Robin "Roblimo" Miller who passed away this morning. Robin "Roblimo" Miller (born October 30, 1952) served as the Editor-in-Chief of Open Source Technology Group, the company which owned Slashdot, SourceForge.net, Freshmeat, Linux.com, NewsForge, and ThinkGeek between 2000 to 2008. Miller formerly owned Robin's Limousine, a small limo company based in Elkridge, Maryland, the origin of his online nickname. Miller is best known for his involvement with Slashdot, where he was not only the corporate editorial overseer but also Interview Editor. As a freelancer, Miller wrote for a number of print and online publications including Time.com, Baltimore City Paper, American Medical News, Innkeeping World, Machine Design, The Baltimore Sun, and Rewired.com. Miller is the author of three books: The Online Rules of Successful Companies, Point -- Click Linux!, and Point -- Click OpenOffice.org, all published by Prentice Hall. His most recent ventures revolved around Internet-delivered video, including video software "tours" and tutorials on Linux.com and his recent "side" venture, Internet Video Promotion, Inc. Miller has been a judge for the Lulu Blooker Prize and is on the online advisory board of the Online Journalism Review of the Annenberg Center for Communication at the University of Southern California. (Biographical Info Quoted in Part from Wikipedia) Further reading: Linux Journal: RIP Robin "Roblimo" Miller. Remembering Miller, ZDNet journalist S. Vaughan-Nichols wrote, "He was funny, bright, quick with a quip, caring, and wise. I, and many others who had the pleasure of knowing him, will miss him enormously." Paul Jones, Clinical Professor at the School of Information & Library Science, and Director of ibiblio.org, wrote, "Robin taught me many things, besides the immense gift of his friendship, including 'the way to make money on the internet is to take on more than you spend.' Both funny and accurate in context and very much true to roblimo." Writer and engineer Emmett Initiative said, "He was my editor, which means he was my best friend and worst enemy. He was a kind and thoughtful man that made every writer around him at least 300% better. I already miss him."

Read more of this story at Slashdot.

by msmash at May 24, 2018 05:55 PM

May 06, 2018

The Document Foundation Planet

Thorsten Behrens: LibreOffice Hamburg Hackfest – a retrospective

Let me join Mike, Miklos and Bjรถrn in the blog reporting on last month’s LibreOffice Hackfest in Hamburg (a good old tradition):

LibreOffice Python hacking

With a nice round number of 100000 (decimal 32) participants and surprisingly non-rainy and warm April weather in Hamburg, we met at very stylish freiheit.com offices that also generously provided us with food and beverages. Further shout-outs to TDF (and all its donors) for providing travel support for our volunteers and, equally importantly, sponsoring CIB’s very own Armin Le Grand fulltime mentoring on and off site.

You can find more details on contributions and work done on the event’s wiki page, and also for the simultaneous German community meetup (wiki, blog); just as much here: code-wise, we had 55 commits from hackfest participants over the weekend –

11  Zdenฤ�k Crhonek
 9  Stephan Bergmann
 5  Christian Lohmaier
 5  Katarina Behrens
 5  Sophia Schrรถder
 4  Armin Le Grand
 3  Michael Meeks
 3  Tamas Bunth
 3  Heiko Tietze
 2  Markus Mohrhard
 2  Miklos Vajna
 1  Linus Behrens
 1  Nithin Kumar Padavu

and probably another 15 or so landing in the weeks after, but with substantial work carried out during the hackfest. I’m really quite happy with the outcome, as well as with the number of new and old names in the above list!

I’d like to highlight one particular area of work (as it’s not reflected yet in the list above i.e. no commits on master yet), namely Regina’s ongoing endeavour to improve LibreOffice ODF conformance (or alternatively the ODF specification, if instead she believes LibreOffice gets it right and the spec has it wrong). This is especially noteworthy as it’s purely volunteer work, including weekly attendance and contribution to ODF technical committee phone meetings. Regina spent the weekend poring over LibreOffice drawing subsystem minutiae with CIB’s Armin Le Grand, and in the end wrote up a plan on making the layer functionality in Draw/Impress more useful and compliant to how ODF specifies layers: Make drawing layers ODF conform .

For myself, I (almost) didn’t get any hacking done but instead spent time mentoring, getting face time with many people, providing hackers with (mostly double) espressos, and had a handful of quite excellent discussions that only tend to happen with enough of smart people in the same room:

  • discussed opportunities around GPG signing and encryption for the public sector with Lothar Becker
  • pondered the future of application development (electron vs. browser-only vs. native ports – and all kinds of in-betweens) with Tim, Michael, and Benjamin
  • got the latest news around autocrypt, memory hole and delta.chat from Bjรถrn Petersen
  • went through a number of sticky problems TDF is facing with regard to upcoming GDPR end of May, with K-J, Uwe, Florian and Eike.
    • BTW for the record, I consider GDPR a broadly good thing & not an undue burden, and a useful motivation also for volunteer and charity organisations to live up to some data protection ideals.

And last but not least thanks to Armin, Bubli, Michael and Siegmund for being the local CIB posse on the ground for that hackfest; and of course thanks to CIB for letting us have such an outstanding LibreOffice team – and to all volunteers donating a full weekend to LibreOffice!

Here are some impressions from the event (thx to Sweetshark for sharing his pictures – that work is (C) 2018 Bjรถrn Michaelsen, as noted in the image description):

May 06, 2018 11:48 AM

April 30, 2018

The Document Foundation Planet

Official TDF Blog: LibreOffice monthly recap: April 2018

Lots of things are happening in the LibreOffice community – in development, documentation, design, QA, translations and much more. Here’s a summary of news and updates in April…

  • LibreOffice 6.0.3 was released on April 3. It includes over 70 bug and regression fixes – see the release announcement for more details.
  • From April 6 – 8, we had a LibreOffice community meeting and Hackfest in Hamburg. There were around 45 participants, who split into two groups. One group focused on a hackfest – a joint coding session. At the same time, a meeting of the German-speaking LibreOffice community took place. See here for the results of the hackfest, and what we discussed.

  • We talked to Edmund Laugasson from the Estonian LibreOffice community about his efforts to promote free and open source software in his country. “ODF is quite widely used in Estonia – for instance, educational institutions usually have LibreOffice installed, along with some local authorities.”Full interview here.
  • Preparation began for the Month of LibreOffice, May 2018 – crediting contributions all across the project. If you’re a proud user of LibreOffice and would like to join our community, get involved! (We’ll even send you a cool sticker pack.)

  • The next LibreOffice Conference will take place from September 26 – 28 in Tirana, Albania, and TDF put out a call for papers. All members and contributors are invited to submit talks, lectures and workshops for the conference – see here for more info.

  • Finally, we gave a warm welcome to our new Google Summer of Code 2018 students. We have a record off 11 students this year, and they will help to improve LibreOffice in many areas: the LOEclipse Plugin, Notebookbar, LibreOffice Viewer for Android and more. So a big hello to Daniel Silva, Ekansh Jha, Hrishabh Rajput, Kshitij Pathania, Manuj Vashist, Muammer Mert Tümer, Nickson Thanda, Raghav Lalvani, Saurav Chirania, Shobhan Mandal and Vikas Mahato!

Keep in touch – follow us on Twitter, Facebook and Google+. Like what we do? Support our community with a donation – or join us and get involved!

April 30, 2018 09:14 AM

April 29, 2018

ODF Wikipedia Page

1OH2: odt is actually zipped archived

odt is actually zipped archived

← Previous revision Revision as of 12:25, 29 April 2018
Line 106: Line 106:
 
}}
 
}}
   
The '''Open Document Format for Office Applications''' ('''ODF'''), also known as '''OpenDocument''', is an [[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]], 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>

by 1OH2 at April 29, 2018 12:25 PM

April 23, 2018

The Document Foundation Planet

Tomaž Vajngerl: Improving the image handling in LibreOffice - Part 3

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.

Regarding the UNO API of XGraphicObject - what is left to do here is to properly clean up the uniqueID, as it is not possible to use it anymore for anything else as a uniqueID (used only in filters for the image names, if the name is not yet known).

Managing memory used by images


Figure1: Hierarchy before refactoring


Previously the memory managing was done on the level of GraphicObjects, where a GraphicManager and GraphicCache (see figure 1) were responsible to create new instances from uniqueID and manage the memory usage that GraphicObject take. 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 ref. counted objects of ImpGraphic). 
Figure 2: Hierarchy after refactoring
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 (see Figure 2).

Graphic swapping and swapping strategy


In the To release the memory of graphic objects, we swap them out to a temp file and read back (swap-in) when we need them again. In the previous implementation this was partially directed by the SdrGrafObj (common image implementation) and SwGrfNode (Writer image implementation). For each graphic object there was a timer when to trigger an automatic swap-out + the swap-out that can happen when a memory limit is exceeded.

For the new code external swapping directed from SdrGrafObj and SwGrfNode was removed, so they can't influence when swapping will happen (maybe in the future they can provide hints when it is a good time to do swapping). There is now a global timer which triggers checking of all Graphic objects if any of them can be swapped out in case we exceed memory limit. Same code is triggered when a new object is created too. A object will be swapped out if it is not used for a certain amount of time. Each object tracks the timestamp when it was last used.

A swap-in happens if the object is swapped-out (obviously) and certain data is needed (under-laying bitmap, animation or metafile). This is checked at the same code-path where the timestamp updating happens.

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.

Other changes to Graphic


Another changes to Graphic done were related to lazy loading. When a document is loaded, we don't want to load Graphic into memory, if it is not needed yet (for example we display the first page but the graphic is on page 10). In document filters (ODF for example) we previously transported the URL of an external or internal graphic to the document model, where it was lazily loaded when it was actually needed. This is not possible now anymore as we need to create a XGraphic object already in the document filter. To overcome this we need to to have an unloaded Graphic, which is created already in a swapped-out state and swapped-in when needed.

The GraphicFilter didn't allow something like this, so I needed to add a new method, which doesn't actually load the image, but just gathers what kind of the image is loaded and its metadata (image size) and creates a GfxLink object that includes the (compressed) image data. The metadata is needed as we don't want to actually force a load when this basic information is requested. Actually we want to load the image as late as this is possible.

Another issue is also that we can have an external image (loaded from a file or even URL on the internet). The issue is similar to the lazy loading scenario, but it is different that a Graphic now must know the URL with which it was created and can be created completely empty (no loading of any kind). The reason for this is that loading is directed by the LinkManager, which is part of the document model. For security reasons the LinkManager can not allow that a Graphic is loaded so loading is directed by the LinkManager on demand (first usage). LinkManager also takes care of all URLs of various external resources. The user can look at those resources and change the URL of them or trigger an update. Changing URL and updating an object was previously done in SdrGrafObj and SwGrfNode, but now this is moved to the common code in Graphic object where SdrGrafObj and SwGrfNode only direct what to do. There are still rooms to improve things here, however not the scope of this work.

Next steps


Finishing up this work by revising the UNO API and fixing known bugs.

Credits


Many thanks to Collabora ProductivityTDF and users that support the foundation by providing donations, to make this work possible.

To be continued...

by Tomaž Vajngerl (noreply@blogger.com) at April 23, 2018 02:59 PM

April 17, 2018

The Document Foundation Planet

Official TDF Blog: LibreOffice Community Meeting and Hackfest in Hamburg: the results

The LibreOffice community communicates mainly over the internet, using our mailing lists, IRC channels and other services. But it’s often good to meet in person, to discuss ideas face-to-face, tackle problems together, and enjoy good company over food and drinks! And from April 6 – 8, in Hamburg, we did just that‌

Friday: Meet and Greet

Some participants arrived early and had a chance to explore the fascinating Hanseatic city of Hamburg, with its river, canals and lake in the centre (Binnenalster, shown below). In the evening we sampled local food at the Groeninger Privatbrauerei.


(Picture: Thomas Ulrich)

Saturday and Sunday: Hackfest

Starting on Saturday, we had around 45 participants, who split into two groups. One group focused on a hackfest – that is, a joint coding session for fixing bugs, working on new features and sharing information. Here’s a summary of the achievements from each participant:

  • Miklos Vajna: mostly mentored Patrick, Nithin, Linus and ZdenÄ›k (aka raal)
  • Michael Stahl: mentored Nithin and remote participant Heiko; worked with Christian Lohmeier to install a GUI text editor as an alternative to Emacs and Vim; reviewed some old Gerrit patches; and investigated regression tdf#77919 (it was already fixed on master but it wasn’t obvious how)
  • Regina Henschel: worked on the topic “Make drawing layers ODF conformant”
  • TamĂĄs Bunth: mostly worked on HSQLDB migration; also picked a random Firebird-related bug
  • Heiko Tietze: solved (remotely) issues with inline tooltips on tracked changes, with help from Michael Stahl
  • Michael Meeks: tweaked, reviewed and merged patch(es) for a 5-10x speedup for VLOOKUP
  • Xisco Fauli: spent most of his time trying to make LibreOffice Viewer work on Android emulator; also showed Marina Latini how to create a bisect repository from scratch
  • Markus Mohrhard: reviewed patches for ZdenÄ›k, and analysed a Calc memory corruption issue
  • Patrick Jaap: worked on tdf#115094, a bug relating to misplaced images in tables when importing .docx files
  • J-NA: worked on fixing up sw uitests with Linus
  • Marina Latini: fixed Italian translation typos; worked on fixing a GPG problem
  • Nithin: worked with Miklos on adding line feeds to section styles
  • Linus Behrens: improved sw uitests, making them more pythonic with J-NA; removing unused includes
  • Lothar Becker: explained the LibreOffice certification programme to Silva from the Albanian community
  • ZdenÄ›k Crhonek (raal): looked at building the LibreOffice Viewer app for Android
  • Jan-Marek Glogowski: worked on font problems in the Qt5 backend
  • Tim Janik: talked to people, discussing toolkits and technology
  • Sophia SchrĂśder: fixing up help, and some translation work
  • Stephan Bergmann: mentored people; worked on fixing regressions with UBSAN, and fixing repaint issue in basic IDE
  • Rheinhard: observed and interacted, as he’s writing about open source communities

So lots of great work from everyone involved – thanks so much for your contributions! The hackfest showed that meeting face-to-face is really effective for fixing issues and sharing information.

German community meeting

At the same time as the hackfest, a meeting of the German-speaking LibreOffice community took place. Last year we met in Berlin (text in German) to discuss various ideas and issues in the project, especially from a German-language perspective, and we followed them up this year to see what progress had been made.

Specifically, we talked about attending more conferences in the German-speaking region, with a more targeted focus: instead of just telling people what LibreOffice is (which most Linux users already know, for instance), we should focus more clearly on bringing in potential new contributors.

Then we turned to the topic of education. It was noted that the Citavi citation software no longer works with LibreOffice 6, and the community lacks materials that could be used to create courses (both online and in schools) about LibreOffice.

We also discussed having more regular face-to-face meetups. Silva Arapi from the Albanian community shared her experiences, but in a larger country like Germany, it’s difficult to get everyone together in the same place. So one idea was to organise more local events, like the Duisburg “Stammtisch” run by Andreas Mantke.

Finally, we set up some “action items”, including the creation of a new “Get involved” flyer for events, and a German translation of the “Get involved” page on the website.

Wrapping up

On the whole, it was a fun and productive event, with some familiar faces, some new faces, and lots of coding, ideas and proposals. Many thanks also to Bjoern Michaelsen and Thorsten Behrens for organising the event, serving up coffee and mentoring developers. And another big thanks to freiheit.com who generously hosted us – and even let us play on their pool table!

We plan to run more hackfests and local community events in the future, so keep an eye on this blog and our social media channels to hear about them: Twitter, Google+ and Facebook!

April 17, 2018 11:49 AM

Collabora Community: Using Collabora Online to accelerate document conversion

Nowadays we have different ways of converting our documents, using different tools that are available online. One option is JODConverter: (for Java OpenDocument Converter) a widely used tool that automates document conversions. Supported formats include OpenDocument, PDF, HTML, Microsoft Office formats (DOC/DOCX/RTF, XLS/XLSX, PPT/PPTX) and many others. Usage can be as a Java library, a command line tool, or a web application. Traditionally the JODConverter uses a LibreOffice process for its conversion but newer versions of JODConverter can use Collabora Online directly.*

We built a dedicated page on our website explaining why you should consider switching to either the Collabora Online backend or more simply talk directly to Collabora Online itself.

What are the main benefits of using Collabora Online for document conversion?

  • Improved performance compared to startup-convert-shutdown approach;
  • The REST API is more reliable than starting LibreOffice in server mode and communicating via remote UNO;
  • More secure because the conversion happens in an isolated environment and this layered approach protects your infrastructure (from outer to inner layers):
    • It is easy to run it in a Virtual Machine / Docker Container;
    • Document data isolation into per-document chroots;
    • Seccomp-bpf: inside that chroot (almost) no system calls are allowed;
    • Extremely sparse filesystem inside the chroot: no shell etc.

For more details checkout our page that explains more about the benefits, performance, and how to try out JODConverter with its Collabora Online backend. If you have questions, feel free to send us an email.

Check it out!

The post Using Collabora Online to accelerate document conversion appeared first on Collabora Productivity.

April 17, 2018 09:30 AM

April 12, 2018

The Document Foundation Planet

Official TDF Blog: Document Freedom Day 2018 in Cuba

The Document Foundation has supported the Cuban LibreOffice community, represented by Carlos Parra Zaldivar, for the Document Freedom Day 2018 in HolguĂ­n, on the opening day of the International Book Exhibition in the local library Biblioteca Provincial “Alex Urquiola”. LibreOffice is included in the Cuban GNU/Linux distribution Nova, and as such is part of the IT syllabus in all schools.

Below, some pictures shot during the event of Carlos Parra Zaldivar speaking about LibreOffice and ODF (Open Document Format) and some of the promotional materials produced by the Cuban LibreOffice community.

April 12, 2018 09:55 AM

April 11, 2018

ODF Wikipedia Page

GreenC bot: Rescued 1 archive link; reformat 1 link. Wayback Medic 2.1

Rescued 1 archive link; reformat 1 link. Wayback Medic 2.1

← Previous revision Revision as of 16:06, 11 April 2018
Line 221: Line 221:
 
* 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 [http://opendocumentfellowship.com/ OpenDocument Fellowship]{{dead link|date=March 2018 |bot=InternetArchiveBot |fix-attempted=yes }} and [http://opendocsociety.org/ OpenDoc Society] were founded to support and promote OpenDocument.
+
* 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 [http://www.oidi.org OIDI.org] (Open Interoperative Document Initiative) is committed to encouraging efforts by governments at all levels, around the globe, to implement changes necessary to ensure public documents are open and interoperable and thus available to all citizens/residents without the need for specific vendor software. -->
 
<!-- * The [http://www.oidi.org OIDI.org] (Open Interoperative Document Initiative) is committed to encouraging efforts by governments at all levels, around the globe, to implement changes necessary to ensure public documents are open and interoperable and thus available to all citizens/residents without the need for specific vendor software. -->
 
* The UK government has adopted ODF as the standard for all documents in the UK civil service<ref>{{cite web | url=https://www.gov.uk/government/news/open-document-formats-selected-to-meet-user-needs|title=Open document formats selected to meet user needs}}</ref>
 
* The UK government has adopted ODF as the standard for all documents in the UK civil service<ref>{{cite web | url=https://www.gov.uk/government/news/open-document-formats-selected-to-meet-user-needs|title=Open document formats selected to meet user needs}}</ref>
Line 278: Line 278:
 
** [[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>
** [[United Kingdom]]<ref>{{cite web |url=https://www.gov.uk/government/publications/open-source-open-standards-and-re-use-government-action-plan |title=Open source, open standards and re-use: government action plan |publisher=[[Government of the United Kingdom]] |date=27 January 2010 |deadurl=no<!--present in archive.com-->}}</ref>
+
** [[United Kingdom]]<ref>{{cite web |url=https://www.gov.uk/government/publications/open-source-open-standards-and-re-use-government-action-plan |title=Open source, open standards and re-use: government action plan |publisher=[[Government of the United Kingdom]] |date=27 January 2010 }}</ref>
 
{{endflatlist}}
 
{{endflatlist}}
 
{{startflatlist}}
 
{{startflatlist}}

by GreenC bot at April 11, 2018 04:06 PM

The Document Foundation Planet

Official TDF Blog: LibreOffice contributor interview: Edmund Laugasson

Edmund Laugasson

LibreOffice is being used in governments and companies around the world, and this is largely thanks to support and advocacy from local communities and developers. Today we’re talking to Edmund Laugasson, a member of the Estonian LibreOffice community, who is promoting the software and the Open Document Format (ODF) in his country‌

How popular is Free, Libre and Open Source Software (FLOSS) and LibreOffice in Estonia?

To be honest, it has not yet been deeply investigated, but the Estonian Ministry of Economic Affairs and Communications has published a “State Information System Interoperability Framework” (in Estonian) where clearly ODF is the main format suggested to use. The status of OOXML is only “allowed”. OOXML should not be confused with the file formats used by MS Office, which differs from OOXML by several proprietary changes. Even LibreOffice offers two different versions to save, e.g. docx – one is OOXML and the another one is used in MS Word. The same applies also to rest of OOXML, MS Office formats that coexist in LibreOffice. As the status of ODF is “suggested”, it is not mandatory. Despite that, ODF is quite widely used – for instance, educational institutions usually have LibreOffice installed, along with some local authorities.

Research is quite challenging as people usually do not respond to questionnaires, and researchers need to meet people directly in order to get reliable answers to questions.

What is your background and involvement in FLOSS?

I live in a small city called Rapla in Estonia, but I work as a lecturer at IT College, which is part of the Tallinn University of Technology. I am involved in FLOSS in many ways. When teaching, I use FLOSS as much as possible: the operating system in university is Ubuntu Linux, and I use derivates like Linux Mint MATE, all 64-bit and the latest LTS (Long Term Support) versions. The office suite is LibreOffice everywhere under GNU/Linux but under MS Windows next to MS Office. It is very important to have LibreOffice installed on every operating system that is used. Also, at least ODF file formats should be opened by LibreOffice by default. Then it would be much easier to deploy ODF in future when the ground is prepared properly. We have a dual-boot system (Microsoft Windows 10 and Ubuntu Linux 16.04.4), and in one classroom also a triple-boot (with macOS 10.12).

In addition I am involved as a board member of the Estonian Free and Open-Source Software Association, taking care of FLOSS in general in Estonia. Also I am involved in the Network of Estonian Teachers of Informatics and Computer Science (NETICS) as a board member. There I promote FLOSS – LibreOffice in particular – to encourage people to use it.
The next involvement is my doctoral studies at Tallinn University, where the current topic is “Technology approval as a factor of adopting a free software ecosystem”.

Further activities will come when I graduate and can focus more on wider deployments of FLOSS, particularly LibreOffice. I have serious plans to arrange all this, but as people in Estonia are not very cooperative, it takes more time – regardless of the fact that Estonia is small. Lots of people just do not believe in better future full of FLOSS, and those few who still believe, will act towards that goal. So to anyone who feels the FLOSS spark inside: do not hesitate to contact me.

What do you think are the biggest obstacles to wider FLOSS and LibreOffice adoption in Estonia?

My first paper in 2013 (published at the IFIP conference) showed that awareness of FLOSS is still relatively low, but interest in getting more information is quite high. Microsoft is doing relatively strong lobbying work, also in Estonia, and the government has quite weak power regarding FLOSS. There is also sometimes controversial behaviour: five state-arranged procurements in the FLOSS field (four state procurements relating to LibreOffice, one state procurement to create an interoperability framework), but weak activities around FLOSS in general. So I decided to start my doctoral studies to fix this situation in a scientific (weighted) way.

Thanks to Edmund for his time and effort helping the FLOSS cause. Click here to see many more interviews from LibreOffice contributors – and why not become one yourself! Build up skills, join a friendly community, and help to make LibreOffice better for everyone.

April 11, 2018 03:28 PM

April 10, 2018

The Document Foundation Planet

Miklos Vajna: LibreOffice Hamburg Hackfest 2018

(via Sweet5hark)

I arrived home from Hamburg yesterday where I participated in the LibreOffice hackfest over the weekend as a mentor. First, thanks to The Document Foundation — and all the donors for funding Collabora to make this possible.

There were a few topics I mentored:

  • Patrick was interested fixing tdf#116486, which required some background knowledge on the Writer document model and layout, so we explored the relevant details together towards providing an actual patch for the bug.

  • Nithin wanted to fix tdf#112384, which turned out to be an ideal task for a hackfest. On one hand, the scope is limited so that you can implement this mini-feature over a weekened. On the other hand, it required touching various parts of Writer (UI, document model, UNO API, ODF filter), so it allowed seeing the process of adding a new feature. The patch is merged to master.

  • Linus looked for a task that is relatively easy, still useful, we looked at tdf#42949, and he identified and removed a number of unused includes himself. This should especially help with slow incremental builds. Again, the patch is already in master.

  • ZdenÄ›k (raal) wanted to write a uitest for tdf#106280 so we were figuring out together how to select images from pyuno and how to avoid using graphic URLs in uitests in general.

The full list of achievements is on the wiki, if you were at the hackfest and you did not contribute to that section, please write a line about what did you hack on. :-)

Finally, thanks for the organizers and the sponsors of the hackfest, it was a really great event!

April 10, 2018 08:35 AM

April 06, 2018

Slashdot

Ubuntu Linux 18.04 LTS 'Bionic Beaver' Beta 2 Now Available

An anonymous reader writes: Ubuntu Linux 18.04 "Bionic Beaver" is almost here -- it is due on April 26. In the interim, today, the second -- and final -- beta becomes available. Bionic Beaver is very significant, as it is an LTS version, meaning "Long Term Support." This is important to those that prefer stability to bleeding edge and don't want to deal with the hassle of upgrades. In other words, you can install 18.04 and be confident that it will be supported for 5 years. In comparison, non-LTS Ubuntu versions get a mere 9 months. There is plenty to be excited about with Ubuntu Linux 18.04 LTS 'Bionic Beaver' Beta 2, including the GNOME 3.28 desktop environment -- Beta 1 did not include GNOME at all. Of course, all the other DE flavors are available too, such as KDE and Xfce. The kernel is at 4.15, which while not the most current version, is still quite modern. Also included is LibreOffice 6.0 -- an essential tool that rivals Microsoft Office. Wayland is available as a technical preview, although X remains the default display server -- for now.

Read more of this story at Slashdot.

by msmash at April 06, 2018 04:00 PM

The Document Foundation Planet

Official TDF Blog: Report of LibreOffice Conference Indonesia

I have attended LibreOffice Conference Indonesia on Saturday, March 25, and Sunday, March 26. The event, hosted by Politeknik Elektronika Negeri Surabaya (PENS), has been the first of its kind in South East Asia, and I hope it will be followed by many similar events in other countries in the region. Of course, the concept of local LibreOffice Conferences in Asia has been launched by the Japanese community, which is a leading example of commitment.

The day before the conference the Indonesia LibreOffice community has organized a localization workshop, led by Andika Triwidada, a long time contributor which has coordinated the Indonesia localization since almost forever.

The day after the conference we have visited the outskirts of Surabaya, with magnificent memories of the past. We have also visited the famous Sampoerna cigarette factory in Surabaya.

On Tuesday, in the morning we have had a meeting with a group of PENS’ IT professors, led by the university dean, with whom we have discussed the opportunity of increasing the presence of open source software in their syllabus. In addition, the university is going to evaluate the migration to open source software and LibreOffice, including the migration to ODF as a way to overcome vendor’s lock-in.

In the afternoon, Frankling Weng and me have keynoted in front of a large student audience about getting involved in open source, and have been followed by Ahmad Haris – the amazing conference coordinator – with a workshop in Indonesian on open source software. Haris has already provided a report in English about the conference, where he offers several insights on the organization. In addition, pictures of the entire event are available on Flickr.

The conference has been a fantastic learning opportunity for me, especially in terms of better understanding local communities in Asia. Last year, I started my full immersion in this topic when I visited Taiwan to attend COSCUP and meet the local community and the country’s Ministry of Innovation, Audrey Tang. Participating in local community events is very important to strengthen the ties between The Document Foundation core team – Board of Directors, Membership Committee and staff members – and LibreOffice incredible global community.

As I said several times during my talks, I have learned more about the community during the four days spent in Surabaya than in weeks of email and social media interactions. Of course, they are both important, but the human face-to-face relation is still invaluable in terms of relationship building. I hope to be able to attend similar events in the future, in other countries in Asia, South America and Africa.

The crowd at LibreOffice Conference Indonesia

Conference volunteers having fun on stage

LibreOffice t-shirts, backpacks and books

Andika Triwidada with conference team

April 06, 2018 10:07 AM

ODF Wikipedia Page

Anomalocaris: {{nowrap}} can't wrap {{longitem}}

{{nowrap}} can't wrap {{longitem}}

← Previous revision Revision as of 08:01, 6 April 2018
Line 10: Line 10:
 
| datastyle = line-height:1.35em;
 
| datastyle = line-height:1.35em;
 
| data4 = {{nowrap|'''[[Filename extension]]s'''<br/>{{mono|.odt{{nbsp|2}}.fodt}}}}
 
| data4 = {{nowrap|'''[[Filename extension]]s'''<br/>{{mono|.odt{{nbsp|2}}.fodt}}}}
| data5 = {{nowrap|'''[[Internet media type]]''' {{longitem|{{mono|application/vnd.oasis.<br/>opendocument.text}}}}}}
+
| data5 = {{nowrap|'''[[Internet media type]]'''}} {{longitem|{{mono|application/vnd.oasis.<br/>opendocument.text}}}}
 
| data7 = {{nowrap|'''[[Uniform Type Identifier|Uniform Type Identifier (UTI)]]'''<br/>{{mono|org.oasis.opendocument.text}}<ref name="uti">{{cite web |url=http://www.huw.id.au/filetypes.html#OpenDocument |title=Filetypes |author=Huw Alexander Ogilvie |accessdate=20 June 2008}}</ref>}}
 
| data7 = {{nowrap|'''[[Uniform Type Identifier|Uniform Type Identifier (UTI)]]'''<br/>{{mono|org.oasis.opendocument.text}}<ref name="uti">{{cite web |url=http://www.huw.id.au/filetypes.html#OpenDocument |title=Filetypes |author=Huw Alexander Ogilvie |accessdate=20 June 2008}}</ref>}}
 
| data8 = {{nowrap|'''UTI conformation'''<br/>{{mono|org.oasis-open.opendocument<br/>public.composite-content}}}}
 
| data8 = {{nowrap|'''UTI conformation'''<br/>{{mono|org.oasis-open.opendocument<br/>public.composite-content}}}}
Line 37: Line 37:
 
| datastyle = line-height:1.35em;
 
| datastyle = line-height:1.35em;
 
| data4 = {{nowrap|'''Filename extensions'''<br/>{{mono|.odp{{nbsp|2}}.fodp}}}}
 
| data4 = {{nowrap|'''Filename extensions'''<br/>{{mono|.odp{{nbsp|2}}.fodp}}}}
| data5 = {{nowrap|'''Internet media type''' {{longitem|{{mono|application/vnd.oasis.<br/>opendocument.presentation}}}}}}
+
| data5 = {{nowrap|'''Internet media type'''}} {{longitem|{{mono|application/vnd.oasis.<br/>opendocument.presentation}}}}
 
| data7 = {{nowrap|'''Uniform Type Identifier (UTI)'''<br/>{{mono|org.oasis.opendocument.presentation}}<ref name="uti"/>}}
 
| data7 = {{nowrap|'''Uniform Type Identifier (UTI)'''<br/>{{mono|org.oasis.opendocument.presentation}}<ref name="uti"/>}}
 
| data8 = {{nowrap|'''UTI conformation'''<br/>{{mono|org.oasis-open.opendocument<br/>public.composite-content}}}}
 
| data8 = {{nowrap|'''UTI conformation'''<br/>{{mono|org.oasis-open.opendocument<br/>public.composite-content}}}}
Line 62: Line 62:
 
| datastyle = line-height:1.35em;
 
| datastyle = line-height:1.35em;
 
| data4 = {{nowrap|'''Filename extensions'''<br/>{{mono|.ods{{nbsp|2}}.fods}}}}
 
| data4 = {{nowrap|'''Filename extensions'''<br/>{{mono|.ods{{nbsp|2}}.fods}}}}
| data5 = {{nowrap|'''Internet media type''' {{longitem|{{mono|application/vnd.oasis.<br/>opendocument.spreadsheet}}}}}}
+
| data5 = {{nowrap|'''Internet media type'''}} {{longitem|{{mono|application/vnd.oasis.<br/>opendocument.spreadsheet}}}}
 
| data7 = {{nowrap|'''Uniform Type Identifier (UTI)'''<br/>{{mono|org.oasis.opendocument.spreadsheet}}<ref name="uti"/>}}
 
| data7 = {{nowrap|'''Uniform Type Identifier (UTI)'''<br/>{{mono|org.oasis.opendocument.spreadsheet}}<ref name="uti"/>}}
 
| data8 = {{nowrap|'''UTI conformation'''<br/>{{mono|org.oasis-open.opendocument<br/>public.composite-content}}}}
 
| data8 = {{nowrap|'''UTI conformation'''<br/>{{mono|org.oasis-open.opendocument<br/>public.composite-content}}}}
Line 87: Line 87:
 
| datastyle = line-height:1.35em;
 
| datastyle = line-height:1.35em;
 
| data4 = {{nowrap|'''Filename extensions'''<br/>{{mono|.odg{{nbsp|2}}.fodg}}}}
 
| data4 = {{nowrap|'''Filename extensions'''<br/>{{mono|.odg{{nbsp|2}}.fodg}}}}
| data5 = {{nowrap|'''Internet media type''' {{longitem|{{mono|application/vnd.oasis.<br/>opendocument.graphics}}}}}}
+
| data5 = {{nowrap|'''Internet media type'''}} {{longitem|{{mono|application/vnd.oasis.<br/>opendocument.graphics}}}}
 
| data7 = {{nowrap|'''Uniform Type Identifier (UTI)'''<br/>{{mono|org.oasis.opendocument.graphics}}<ref name="uti"/>}}
 
| data7 = {{nowrap|'''Uniform Type Identifier (UTI)'''<br/>{{mono|org.oasis.opendocument.graphics}}<ref name="uti"/>}}
 
| data8 = {{nowrap|'''UTI conformation'''<br/>{{mono|org.oasis-open.opendocument<br/>public.composite-content}}}}
 
| data8 = {{nowrap|'''UTI conformation'''<br/>{{mono|org.oasis-open.opendocument<br/>public.composite-content}}}}

by Anomalocaris at April 06, 2018 08:01 AM

March 29, 2018

The Document Foundation Planet

Official TDF Blog: LibreOffice monthly recap: March 2018

There’s so much going on in the LibreOffice project – in development, documentation, design, QA, translations and much more. So at the end of each month we’ll be posting summaries of recent activities and updates, to help you get an overview of what’s going on. Here’s what happened in March‌

  • LibreOffice 5.4.6 was released, with almost 60 bug and regression fixes. This is part of the 5.4 branch, targeted at mainstream users and enterprises. More information in the press release.
  • The Indonesian community organised a three day conference, supported by The Document Foundation. The website has details (in Indonesian), and below is a video promoting the event – English subtitles are available:

  • Meanwhile, we’re already getting excited about the main LibreOffice Conference due later this year, in Tirana. But we’re looking even further ahead, and announced a call for locations for the LibreOffice Conference 2019. The deadline for sending proposals is June 30, so if you want to help out, let us know!
  • Buovjaga from the QA community wrote a blog post describing the importance of quality assurance in open source projects. “QA is acting like neurotransmitters in the body of the project”, he writes, explaining that QA is involved in many different areas.
  • This year’s Google Summer of Code (GSoC) is fast approaching, and we reached out to potential participants. In recent years, GSoC students have contributed many great features and updates to LibreOffice, so we look forward to seeing what will happen this year.

  • Olivier Hallot from the documentation community wrote about rich content arriving in the new help system. “The new help can now access external videos on YouTube or similar services, and also open or download OpenDocument files to support the textual explanations of LibreOffice features in the help pages.”
  • Also in blog news, Lera Goncharuk summarised migrations to LibreOffice in Russia on his blog. These include migrations at the federal government level, along with regional administrations.
  • Finally, development continues on LibreOffice 6.1, which is due to be released in early August. You can see some of the new features in the release notes, such as the ability to sort images anchored to cells in Calc:

Keep in touch – follow us on Twitter, Facebook and Google+. Like what we do? Support our community with a donation – or join us and get involved!

March 29, 2018 11:22 AM

March 27, 2018

The Document Foundation Planet

Official TDF Blog: Document Freedom Day 2018

Today is Document Freedom Day (DFD) 2018, an annual event to celebrate and raise awareness about Open Standards scheduled on the last Wednesday of March. Document Freedom Day was first celebrated on 26 March 2008. Since 2016, Document Freedom Day is organised by a team of volunteers of the Digital Freedom Foundation. It was previously organised by the Free Software Foundation Europe.

Document Freedom Day is a campaign about open standards and document formats, aimed at non-technical people. Open Standards ensure document interoperability, a pre-condition for knowledge sharing amongst individuals.

Document freedom addresses much more than just texts and spreadsheets, as it is about the control of any kind of digital data, which should be stored in open and standard ways to empower knowledge sharing by users. On the contrary, most digital data is normally stored in proprietary and closed formats, which constrain and manipulate users at enormous cost.

In fact, documents that are not free are locked to some particular software or company. Often, even their original author is not able to access their contents, as they are controlled by artificial technical restrictions.

Open Standards are essential for interoperability and freedom of choice, based on the merits of software applications. They provide freedom from data lock-in and the subsequent vendor lock-in. This makes Open Standards essential for governments, companies, organisations and individual users of information technology.

Open Standards must be:

  • Subject to full public assessment and use without constraints in a manner equally available to everyone
  • Without any components or extensions that have dependencies on formats or protocols that do not meet the definition of an open standard themselves
  • Free from legal or technical clauses that limit its utilisation by any party or in any business model
  • Managed and further developed independently of any single supplier in a process open to the equal participation of competitors and third parties
  • Available in multiple complete implementations by competing suppliers, or as a complete implementation equally available to all parties

Let’s celebrate Document Freedom Day 2018 to make Open Standards a reality. Open Document Standard (ODF), the native document format of LibreOffice and many more software applications, is the only Open Standard available in the domain of personal productivity for organizations and individuals. Every LibreOffice users should advocate, support and use ODF.

[Source of Informations: https://en.wikipedia.org/wiki/Document_Freedom_Day]

March 27, 2018 05:46 PM

March 26, 2018

ODF Wikipedia Page

Cedar101: /* Adoption */ !

Adoption: !

← Previous revision Revision as of 09:23, 26 March 2018
Line 248: Line 248:
   
 
!rowspan="4" style="padding:0.25em 1.0em;"| National
 
!rowspan="4" style="padding:0.25em 1.0em;"| National
|style="text-align:right;padding-right:0.5em;"| Africa
+
!style="text-align:right;padding-right:0.5em;"| Africa
 
|class="hlist" style="vertical-align:top;padding:0.25em 0.5em;"|
 
|class="hlist" style="vertical-align:top;padding:0.25em 0.5em;"|
 
* [[South Africa]]
 
* [[South Africa]]
 
|-
 
|-
|style="text-align:right;padding-right:0.5em;"| Asia
+
!style="text-align:right;padding-right:0.5em;"| Asia
 
|class="hlist" style="vertical-align:top;padding:0.25em 0.5em;"|
 
|class="hlist" style="vertical-align:top;padding:0.25em 0.5em;"|
 
* [[Japan]]
 
* [[Japan]]
Line 261: Line 261:
 
* [[Taiwan]]<ref>{{cite web |url=https://www.ndc.gov.tw/en/News_Content.aspx?n=0E2DCBAA6CB72F12&sms=B079565EECDD8520&s=33EF0883B81062FF |title=Promote Government’s Open Document Standards Develop New Value for Document Circulation |publisher=National Development Council Taiwan |date=9 June 2015}}</ref><ref>{{cite web |url=https://conference.libreoffice.org/assets/Conference/Aarhus/Slides/FranklinWeng.pdf |title=Successful Story: Migrating Libreoffice to I-Lan County Government |publisher=Franklin Weng |date=24 Sep 2015}}</ref><ref>{{cite web |url=https://conference.libreoffice.org/assets/Conference/Brno/weng-odf-migration-in-taiwan.pdf |title=Taiwan migration to ODF: progress, problems and what to do next |publisher=Franklin Weng |date=8 Sep 2016}}</ref>
 
* [[Taiwan]]<ref>{{cite web |url=https://www.ndc.gov.tw/en/News_Content.aspx?n=0E2DCBAA6CB72F12&sms=B079565EECDD8520&s=33EF0883B81062FF |title=Promote Government’s Open Document Standards Develop New Value for Document Circulation |publisher=National Development Council Taiwan |date=9 June 2015}}</ref><ref>{{cite web |url=https://conference.libreoffice.org/assets/Conference/Aarhus/Slides/FranklinWeng.pdf |title=Successful Story: Migrating Libreoffice to I-Lan County Government |publisher=Franklin Weng |date=24 Sep 2015}}</ref><ref>{{cite web |url=https://conference.libreoffice.org/assets/Conference/Brno/weng-odf-migration-in-taiwan.pdf |title=Taiwan migration to ODF: progress, problems and what to do next |publisher=Franklin Weng |date=8 Sep 2016}}</ref>
 
|-
 
|-
|style="text-align:right;padding-right:0.5em;"| Europe
+
!style="text-align:right;padding-right:0.5em;"| Europe
 
|style="vertical-align:top;padding:0.25em 0.5em;"|
 
|style="vertical-align:top;padding:0.25em 0.5em;"|
 
{{startflatlist}}
 
{{startflatlist}}
Line 288: Line 288:
 
{{endflatlist}}
 
{{endflatlist}}
 
|-
 
|-
|style="text-align:right;white-space:nowrap;padding-right:0.5em;"| South America
+
!style="text-align:right;white-space:nowrap;padding-right:0.5em;"| South America
 
|class="hlist" style="vertical-align:top;padding:0.25em 0.5em;"|
 
|class="hlist" style="vertical-align:top;padding:0.25em 0.5em;"|
 
* [[Brazil]]
 
* [[Brazil]]

by Cedar101 at March 26, 2018 09:23 AM

March 25, 2018

The Document Foundation Planet

Official TDF Blog: Rich Contents Arrives in New Help

Last week the new help system – online and offline – received enhancements to add multimedia and other resources for a richer user experience of LibreOffice Help. The new help can now access external videos stored in You Tube or similar services and also to open or download OpenDocument files to support the textual explanations of LibreOffice features in the help pages.

External videos can be displayed in New Help pages

The current textual contents of the help pages is an important legacy information because LibreOffice does not have a development method that requires “a priori” documentation  of the new feature specifications. LibreOffice Help pages will continue to have text contents and external videos shall be used to support this contents and will not replace it.

Imagine the situation where a user need help on Calc pivot tables. Besides the existing help pages on the subject, a companion tutorial video can be linked in the page to further explain pivot tables with examples and different wording. If well produced, the external video stored in a video service server can even display captions in the user language, although it depends on the browser language settings, the video file service host and the video production.

Actually, production of good multimedia contents in general is not a light task. A good video tutorial requires advanced (often professional) techniques and skills, and our users will appreciate quality and effectiveness of the videos. Normally good videos are short – less than 2 minutes – have a direct communication with the user and must be rendered in low resolutions monitors.

The new help also has OpenDocument files available for download in the help pages. For the moment only ODF files allowed are of MIME type application/vnd.oasis.opendocument. prefix and “text”, “spreadsheet”, “drawing”, “presentation”, “formula” or “database” as suffix. It can be extended for other cases such as CSV, TXT or HTML if necessary. The purpose of the companion files is to offer to the Help user a working case of the feature or a starting point for a bigger work around the feature.

Files can be downloaded from New Help pages

Adding Help contents for LibreOffice is not an easy task. Besides knowledge of Extensive Markup Language (XML) and some developments skills for patch submission, the Help contents, unlike a book or a guide,  must be factual and as much accurate as possible. Poor multimedia or companion files can turn into counterproductive resources.

Are you interested in helping us to make our Help a rich experience? Do you want to improve our help contents? Join the Documentation Team!

For more information on how to add files or external videos, visit our wiki page

Happy Help Rich Contents!

Sources:

March 25, 2018 11:22 AM

March 18, 2018

ODF Wikipedia Page

Fweng322: /* Adoption */ Add Taiwan in the adoption list and provide references

Adoption: Add Taiwan in the adoption list and provide references

← Previous revision Revision as of 13:13, 18 March 2018
Line 259: Line 259:
 
* [[Russia]]
 
* [[Russia]]
 
* [[South Korea]]
 
* [[South Korea]]
  +
* [[Taiwan]]<ref>{{cite web |url=https://www.ndc.gov.tw/en/News_Content.aspx?n=0E2DCBAA6CB72F12&sms=B079565EECDD8520&s=33EF0883B81062FF |title=Promote Government’s Open Document Standards Develop New Value for Document Circulation |publisher=National Development Council Taiwan |date=9 June 2015}}</ref><ref>{{cite web |url=https://conference.libreoffice.org/assets/Conference/Aarhus/Slides/FranklinWeng.pdf |title=Successful Story: Migrating Libreoffice to I-Lan County Government |publisher=Franklin Weng |date=24 Sep 2015}}</ref><ref>{{cite web |url=https://conference.libreoffice.org/assets/Conference/Brno/weng-odf-migration-in-taiwan.pdf |title=Taiwan migration to ODF: progress, problems and what to do next |publisher=Franklin Weng |date=8 Sep 2016}}</ref>
 
|-
 
|-
 
|style="text-align:right;padding-right:0.5em;"| Europe
 
|style="text-align:right;padding-right:0.5em;"| Europe

by Fweng322 at March 18, 2018 01:13 PM

March 04, 2018

ODF Wikipedia Page

InternetArchiveBot: Rescuing 6 sources and tagging 2 as dead. #IABot (v1.6.4)

Rescuing 6 sources and tagging 2 as dead. #IABot (v1.6.4)

← Previous revision Revision as of 04:27, 4 March 2018
Line 132: Line 132:
 
The OpenDocument standard was developed by a Technical Committee (TC) under the OASIS ([[Organization for the Advancement of Structured Information Standards]]) industry consortium. The ODF-TC has members from a diverse set of companies and individuals. Active TC members have voting rights. Members associated with Sun and IBM have sometimes had a large voting influence.<ref>{{cite web | url=http://www.oasis-open.org/committees/membership.php?wg_abbrev=office | title=OpenDocument TC's {{Sic|hide=y|publicly|-}}visible membership roster | accessdate=3 November 2007}}</ref> The standardization process involved the developers of many office suites or related document systems. The first official ODF-TC meeting to discuss the standard was 16 December 2002; OASIS approved OpenDocument as an OASIS standard on 1 May 2005. OASIS submitted the ODF specification to [[ISO/IEC JTC1|ISO/IEC Joint Technical Committee 1]] (JTC 1) on 16 November 2005, under Publicly Available Specification (PAS) rules. ISO/IEC standardization for an open document standard including text, spreadsheet and presentation was proposed for the first time in [[DKUUG]] 28 August 2001.<ref>{{cite web | url=http://www.open-std.org/keld/iso26300-odf/dkuug-std-010828.pdf | title=Meeting agenda for DKUUG STD 2001-08-28 – item 5.6 | accessdate=13 March 2015}}</ref>
 
The OpenDocument standard was developed by a Technical Committee (TC) under the OASIS ([[Organization for the Advancement of Structured Information Standards]]) industry consortium. The ODF-TC has members from a diverse set of companies and individuals. Active TC members have voting rights. Members associated with Sun and IBM have sometimes had a large voting influence.<ref>{{cite web | url=http://www.oasis-open.org/committees/membership.php?wg_abbrev=office | title=OpenDocument TC's {{Sic|hide=y|publicly|-}}visible membership roster | accessdate=3 November 2007}}</ref> The standardization process involved the developers of many office suites or related document systems. The first official ODF-TC meeting to discuss the standard was 16 December 2002; OASIS approved OpenDocument as an OASIS standard on 1 May 2005. OASIS submitted the ODF specification to [[ISO/IEC JTC1|ISO/IEC Joint Technical Committee 1]] (JTC 1) on 16 November 2005, under Publicly Available Specification (PAS) rules. ISO/IEC standardization for an open document standard including text, spreadsheet and presentation was proposed for the first time in [[DKUUG]] 28 August 2001.<ref>{{cite web | url=http://www.open-std.org/keld/iso26300-odf/dkuug-std-010828.pdf | title=Meeting agenda for DKUUG STD 2001-08-28 – item 5.6 | accessdate=13 March 2015}}</ref>
   
After a six-month review period, on 3 May 2006, OpenDocument unanimously passed its six-month DIS (Draft International Standard) ballot in [[JTC 1]] ([[ISO/IEC JTC1/SC34]]), with broad participation,<ref>{{cite web | url=http://www.jtc1sc34.org/repository/0728revc.htm | title=<!--what the title actually says: "ISO/IEC JTC 1/SC 34 Information Technology -->Document Description and Processing Languages-->Summary of Voting on DIS ISO/IEC 26300 – Open Document Format for Office Applications (OpenDocument) v1.0 | date=13 June 2006 | accessdate=24 August 2006 | author=ISO/IEC SC34 Secretariat | work=ISO/IEC JTC 1/SC 34 Document Repository | archiveurl=https://web.archive.org/web/20061001180333/http://www.jtc1sc34.org/repository/0728revc.htm | archivedate = 1 October 2006}}</ref> after which the OpenDocument specification was "approved for release as an ISO and IEC International Standard" under the name ISO/IEC 26300:2006.<ref>{{cite web | url=http://www.iso.org/iso/en/commcentre/pressreleases/2006/Ref1004.html | title=ISO and IEC approve OpenDocument OASIS standard for data interoperability of office applications | date=8 May 2006 | accessdate=24 August 2006 | work=ISO Press Releases | publisher=[[International Organization for Standardization|ISO]]}}</ref>
+
After a six-month review period, on 3 May 2006, OpenDocument unanimously passed its six-month DIS (Draft International Standard) ballot in [[JTC 1]] ([[ISO/IEC JTC1/SC34]]), with broad participation,<ref>{{cite web | url=http://www.jtc1sc34.org/repository/0728revc.htm | title=<!--what the title actually says: "ISO/IEC JTC 1/SC 34 Information Technology -->Document Description and Processing Languages-->Summary of Voting on DIS ISO/IEC 26300 – Open Document Format for Office Applications (OpenDocument) v1.0 | date=13 June 2006 | accessdate=24 August 2006 | author=ISO/IEC SC34 Secretariat | work=ISO/IEC JTC 1/SC 34 Document Repository | archiveurl=https://web.archive.org/web/20061001180333/http://www.jtc1sc34.org/repository/0728revc.htm | archivedate = 1 October 2006}}</ref> after which the OpenDocument specification was "approved for release as an ISO and IEC International Standard" under the name ISO/IEC 26300:2006.<ref>{{cite web | url=http://www.iso.org/iso/en/commcentre/pressreleases/2006/Ref1004.html | title=ISO and IEC approve OpenDocument OASIS standard for data interoperability of office applications | date=8 May 2006 | accessdate=24 August 2006 | work=ISO Press Releases | publisher=[[International Organization for Standardization|ISO]] | deadurl=yes | archiveurl=https://web.archive.org/web/20060519180809/http://www.iso.org/iso/en/commcentre/pressreleases/2006/Ref1004.html | archivedate=19 May 2006 | df=dmy-all }}</ref>
   
 
After responding to all written ballot comments, and a 30-day default ballot, the OpenDocument [[international standard]] went to publication in ISO, officially published 30 November 2006.
 
After responding to all written ballot comments, and a 30-day default ballot, the OpenDocument [[international standard]] went to publication in ISO, officially published 30 November 2006.
Line 155: Line 155:
 
* [[Adobe Buzzword]]<ref>{{cite web|url=http://labs.adobe.com/technologies/buzzword/ |title=Adobe Buzzword online word processor from Acrobat.com |publisher=Labs.adobe.com |date= |accessdate=19 May 2009}}</ref>
 
* [[Adobe Buzzword]]<ref>{{cite web|url=http://labs.adobe.com/technologies/buzzword/ |title=Adobe Buzzword online word processor from Acrobat.com |publisher=Labs.adobe.com |date= |accessdate=19 May 2009}}</ref>
 
* [[Apache OpenOffice]]
 
* [[Apache OpenOffice]]
* [[Atlantis Word Processor]]<ref>{{cite news|url=https://web.archive.org/web/20160326160635/http://www.atlantiswordprocessor.com:80/en/news/1_6_5.htm|title=Atlantis Word Processor 1.6.5 release notes (at the Wayback Machine)|work=atlantiswordprocessor.com|accessdate=2018-02-01}}</ref>
+
* [[Atlantis Word Processor]]<ref>{{cite news|url=http://www.atlantiswordprocessor.com/en/news/1_6_5.htm|title=Atlantis Word Processor 1.6.5 release notes (at the Wayback Machine)|work=atlantiswordprocessor.com|accessdate=2018-02-01|deadurl=yes|archiveurl=https://web.archive.org/web/20160326160635/http://www.atlantiswordprocessor.com/en/news/1_6_5.htm|archivedate=26 March 2016|df=dmy-all}}</ref>
 
* [[Bean (software)]]
 
* [[Bean (software)]]
 
* [[Calibre (software)|Calibre]] [[E-book|ebook]] viewer, converter, editor, and manager
 
* [[Calibre (software)|Calibre]] [[E-book|ebook]] viewer, converter, editor, and manager
Line 166: Line 166:
 
* [[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>
 
* [[Google Docs]]
 
* [[Google Docs]]
* [[IBM Lotus Symphony]]<ref name="register" /><ref>{{cite web|url=http://blogs.msdn.com/dmahugh/archive/2009/05/09/1-2-1.aspx |title=1 + 2 = 1?|author=Doug Mahugh|publisher=MSDN Blogs|date=10 May 2009<!-- 2:26 AM-->|accessdate=10 September 2012}}</ref><ref>{{cite web|url=http://symphony.lotus.com/software/lotus/symphony/help.nsf/ReleaseNotes|title=Symphony.lotus.com|work=symphony.lotus.com}}</ref>
+
* [[IBM Lotus Symphony]]<ref name="register" /><ref>{{cite web|url=http://blogs.msdn.com/dmahugh/archive/2009/05/09/1-2-1.aspx |title=1 + 2 = 1?|author=Doug Mahugh|publisher=MSDN Blogs|date=10 May 2009<!-- 2:26 AM-->|accessdate=10 September 2012}}</ref><ref>{{cite web|url=http://symphony.lotus.com/software/lotus/symphony/help.nsf/ReleaseNotes|title=Symphony.lotus.com|work=symphony.lotus.com|deadurl=yes|archiveurl=https://web.archive.org/web/20090710011646/http://symphony.lotus.com/software/lotus/symphony/help.nsf/ReleaseNotes|archivedate=10 July 2009|df=dmy-all}}</ref>
 
* [[Inkscape]] exports .odg
 
* [[Inkscape]] exports .odg
* [[KOffice]]<ref>{{cite web|url=http://koffice.org/filters/1.6/|title=Koffice.org|work=koffice.org}}</ref>
+
* [[KOffice]]<ref>{{cite web|url=http://koffice.org/filters/1.6/|title=Koffice.org|work=koffice.org|deadurl=yes|archiveurl=https://web.archive.org/web/20080513125754/http://koffice.org/filters/1.6/|archivedate=13 May 2008|df=dmy-all}}</ref>
 
* [[LibreOffice]]<ref name="register" />
 
* [[LibreOffice]]<ref name="register" />
 
* [[Microsoft Office 2003]] and [[Microsoft Office XP|Office XP]] (with the Open Source OpenXML/ODF Translator Add-in for Office)<ref>{{cite web|url=http://odf-converter.sourceforge.net/download.html#hRequirements|title=OpenXML/ODF Translator Add-ins for Office|accessdate=31 January 2014}}</ref>
 
* [[Microsoft Office 2003]] and [[Microsoft Office XP|Office XP]] (with the Open Source OpenXML/ODF Translator Add-in for Office)<ref>{{cite web|url=http://odf-converter.sourceforge.net/download.html#hRequirements|title=OpenXML/ODF Translator Add-ins for Office|accessdate=31 January 2014}}</ref>
Line 217: Line 217:
 
** The toolkit also includes a single page graphical image<ref>https://web.archive.org/web/20150620003502/http://www.openforumeurope.org/library/ODF/odf-toolkit-folder/OFE-COIS-ODF-infographic-release-02150325-by-sa.jpeg</ref> designed to articulate the consequences of not choosing Open Document Format. The illustration has now been translated into more than 10 languages.
 
** The toolkit also includes a single page graphical image<ref>https://web.archive.org/web/20150620003502/http://www.openforumeurope.org/library/ODF/odf-toolkit-folder/OFE-COIS-ODF-infographic-release-02150325-by-sa.jpeg</ref> designed to articulate the consequences of not choosing Open Document Format. The illustration has now been translated into more than 10 languages.
 
* 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 }}</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}}</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.
* Several organisations, such as the [http://opendocumentfellowship.com/ OpenDocument Fellowship] and [http://opendocsociety.org/ OpenDoc Society] were founded to support and promote OpenDocument.
+
* Several organisations, such as the [http://opendocumentfellowship.com/ OpenDocument Fellowship]{{dead link|date=March 2018 |bot=InternetArchiveBot |fix-attempted=yes }} and [http://opendocsociety.org/ OpenDoc Society] were founded to support and promote OpenDocument.
 
<!-- * The [http://www.oidi.org OIDI.org] (Open Interoperative Document Initiative) is committed to encouraging efforts by governments at all levels, around the globe, to implement changes necessary to ensure public documents are open and interoperable and thus available to all citizens/residents without the need for specific vendor software. -->
 
<!-- * The [http://www.oidi.org OIDI.org] (Open Interoperative Document Initiative) is committed to encouraging efforts by governments at all levels, around the globe, to implement changes necessary to ensure public documents are open and interoperable and thus available to all citizens/residents without the need for specific vendor software. -->
 
* The UK government has adopted ODF as the standard for all documents in the UK civil service<ref>{{cite web | url=https://www.gov.uk/government/news/open-document-formats-selected-to-meet-user-needs|title=Open document formats selected to meet user needs}}</ref>
 
* The UK government has adopted ODF as the standard for all documents in the UK civil service<ref>{{cite web | url=https://www.gov.uk/government/news/open-document-formats-selected-to-meet-user-needs|title=Open document formats selected to meet user needs}}</ref>
Line 230: Line 230:
   
 
*Different applications using ODF as a standard document format have different methods of providing macro/scripting capabilities. There is no [[macro language]] specified in ODF. Users and developers differ on whether inclusion of a standard scripting language would be desirable.<ref>{{cite web | url=http://www.linux.com/archive/articles/47935 | archiveurl=https://web.archive.org/web/20110521183559/http://www.linux.com/archive/articles/47935 | archivedate=21 May 2011 | title=Macros an obstacle to office suite compatibility | author=Marco Fioretti | accessdate=11 May 2008}}</ref>
 
*Different applications using ODF as a standard document format have different methods of providing macro/scripting capabilities. There is no [[macro language]] specified in ODF. Users and developers differ on whether inclusion of a standard scripting language would be desirable.<ref>{{cite web | url=http://www.linux.com/archive/articles/47935 | archiveurl=https://web.archive.org/web/20110521183559/http://www.linux.com/archive/articles/47935 | archivedate=21 May 2011 | title=Macros an obstacle to office suite compatibility | author=Marco Fioretti | accessdate=11 May 2008}}</ref>
* The ODF specification for tracked changes is limited and does not fully specify all cases, resulting in implementation-specific behaviors.<ref>{{cite web | url=http://blogs.msdn.com/dmahugh/archive/2009/05/13/tracked-changes.aspx | title=Tracked Changes | author=Doug Mahugh (Microsoft) | date=13 May 2009}}</ref> In addition, OpenDocument does not support change tracking in elements like tables or [[MathML]].<ref name="doyourmath">{{cite web | url=https://web.archive.org/web/20160326225935/http://idippedut.dk/post/Do-your-math-OOXML-and-OMML | title=Do your math - OOXML and OMML (Updated 2008-02-12) | author=Jesper Lund Stocholm (Danish ISO/IEC representative) | date=12 December 2008}}</ref>
+
* The ODF specification for tracked changes is limited and does not fully specify all cases, resulting in implementation-specific behaviors.<ref>{{cite web | url=http://blogs.msdn.com/dmahugh/archive/2009/05/13/tracked-changes.aspx | title=Tracked Changes | author=Doug Mahugh (Microsoft) | date=13 May 2009}}</ref> In addition, OpenDocument does not support change tracking in elements like tables or [[MathML]].<ref name="doyourmath">{{cite web | url=http://idippedut.dk/post/Do-your-math-OOXML-and-OMML | title=Do your math - OOXML and OMML (Updated 2008-02-12) | author=Jesper Lund Stocholm (Danish ISO/IEC representative) | date=12 December 2008 | deadurl=bot: unknown | archiveurl=https://web.archive.org/web/20160326225935/http://idippedut.dk/post/Do-your-math-OOXML-and-OMML | archivedate=26 March 2016 | df=dmy-all }}</ref>
 
* It is not permitted to use generic ODF formatting style elements (like font information) for the MathML elements.<ref name="doyourmath"/>
 
* It is not permitted to use generic ODF formatting style elements (like font information) for the MathML elements.<ref name="doyourmath"/>
   
Line 323: Line 323:
 
* [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/ 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] 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.

by InternetArchiveBot at March 04, 2018 04:27 AM

February 09, 2018

HackerNews

February 05, 2018

6 ways to implement Swachh Bharat Mission in a district to make villages open defecation free - YourStory.com

6 ways to implement Swachh Bharat Mission in a district to make villages open defecation free  YourStory.com

Swachh Bharat Mission was initiated by Prime Minister Narendra Modi on October 2, 2014, when he resolved to bring about an Open Defecation Free (ODF) ...

February 05, 2018 08:44 AM

February 01, 2018

ODF Wikipedia Page

MetaManFromTomorrow: /* Software */ Fixed link to Gnumeric reference

Software: Fixed link to Gnumeric reference

← Previous revision Revision as of 21:06, 1 February 2018
Line 164: Line 164:
 
|accessdate=3 May 2008}}</ref>
 
|accessdate=3 May 2008}}</ref>
 
* [[Evince]]
 
* [[Evince]]
* [[Gnumeric]]<ref>{{cite web|url=http://projects.gnome.org/gnumeric/doc/sect-file-formats.shtml|title=File Formats|author=Eric Baudais & others|publisher=GNOME Documentation Project|work=The Gnumeric Manual, version 1.10|date=February 2010|accessdate=10 September 2012}}</ref>
+
* [[Gnumeric]]<ref>{{cite web|url=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>
 
* [[Google Docs]]
 
* [[Google Docs]]
 
* [[IBM Lotus Symphony]]<ref name="register" /><ref>{{cite web|url=http://blogs.msdn.com/dmahugh/archive/2009/05/09/1-2-1.aspx |title=1 + 2 = 1?|author=Doug Mahugh|publisher=MSDN Blogs|date=10 May 2009<!-- 2:26 AM-->|accessdate=10 September 2012}}</ref><ref>{{cite web|url=http://symphony.lotus.com/software/lotus/symphony/help.nsf/ReleaseNotes|title=Symphony.lotus.com|work=symphony.lotus.com}}</ref>
 
* [[IBM Lotus Symphony]]<ref name="register" /><ref>{{cite web|url=http://blogs.msdn.com/dmahugh/archive/2009/05/09/1-2-1.aspx |title=1 + 2 = 1?|author=Doug Mahugh|publisher=MSDN Blogs|date=10 May 2009<!-- 2:26 AM-->|accessdate=10 September 2012}}</ref><ref>{{cite web|url=http://symphony.lotus.com/software/lotus/symphony/help.nsf/ReleaseNotes|title=Symphony.lotus.com|work=symphony.lotus.com}}</ref>

by MetaManFromTomorrow at February 01, 2018 09:06 PM

6 Steps to Make a Village Open Defecation Free - The Better India

6 Steps to Make a Village Open Defecation Free  The Better India

The Swachh Bharat Mission was initiated by Prime Minister Narendra Modi on 2 October 2014, with a resolution to achieve Open Defecation Free (ODF) India by ...

February 01, 2018 08:00 AM

MetaManFromTomorrow: /* Software */ Fixed link on Atlantis Word Processor reference

Software: Fixed link on Atlantis Word Processor reference

← Previous revision Revision as of 07:11, 1 February 2018
Line 155: Line 155:
 
* [[Adobe Buzzword]]<ref>{{cite web|url=http://labs.adobe.com/technologies/buzzword/ |title=Adobe Buzzword online word processor from Acrobat.com |publisher=Labs.adobe.com |date= |accessdate=19 May 2009}}</ref>
 
* [[Adobe Buzzword]]<ref>{{cite web|url=http://labs.adobe.com/technologies/buzzword/ |title=Adobe Buzzword online word processor from Acrobat.com |publisher=Labs.adobe.com |date= |accessdate=19 May 2009}}</ref>
 
* [[Apache OpenOffice]]
 
* [[Apache OpenOffice]]
* [[Atlantis Word Processor]]<ref>{{cite news|url=http://www.atlantiswordprocessor.com/en/news/1_6_5.htm|title=Atlantis Word Processor 1.6.5 release notes|work=atlantiswordprocessor.com|accessdate=2010-01-28}}</ref>
+
* [[Atlantis Word Processor]]<ref>{{cite news|url=https://web.archive.org/web/20160326160635/http://www.atlantiswordprocessor.com:80/en/news/1_6_5.htm|title=Atlantis Word Processor 1.6.5 release notes (at the Wayback Machine)|work=atlantiswordprocessor.com|accessdate=2018-02-01}}</ref>
 
* [[Bean (software)]]
 
* [[Bean (software)]]
 
* [[Calibre (software)|Calibre]] [[E-book|ebook]] viewer, converter, editor, and manager
 
* [[Calibre (software)|Calibre]] [[E-book|ebook]] viewer, converter, editor, and manager

by MetaManFromTomorrow at February 01, 2018 07:11 AM

January 31, 2018

Slashdot

LibreOffice 6.0 Released: Features Superior Microsoft Office Interoperability, OpenPGP Support

prisoninmate writes: LibreOffice 6.0 comes two and a half years after the LibreOffice 5.x series, and it's the biggest release of the open-source and cross-platform office suite so far. It introduces a revamped design with new table styles, improved Notebookbars, new gradients, new Elementary icons, menu and toolbar improvements, and updated motif/splash screen. LibreOffice 6.0 offers superior interoperability with Microsoft Office documents and compatibility with the EPUB3 format by allowing users to export ODT files to EPUB3. It also lets you import your AbiWord, Microsoft Publisher, PageMaker, and QuarkXPress documents and templates thanks to the implementation of a set of new open-source libraries contributed by the Document Liberation project. Many great improvements were made to the OOXML and ODF filters, as well as in the EMF+, Adobe Freehand, Microsoft Visio, Adobe Pagemaker, FictionBook, Apple Keynote, Pages, and Numbers, as well as Quattro Pro import functionality, and to the XHTML export. LibreOffice Online received numerous improvements as well in this major release of LibreOffice.

Read more of this story at Slashdot.

by msmash at January 31, 2018 02:40 PM

HackerNews

The Document Foundation Planet

TomaĹž Vajngerl: Improving the image handling in LibreOffice - Part 1

Prologue

It is known for some time that the image life-cycle in LibreOffice is problematic and can potentially lead to image loss, but to make the life-cycle more robust against loss, a lot of refactoring would need to be done. Another issue is also the mechanism of images swapping in and out of the memory. Keeping images in memory takes a lot of space so when a certain amount is hit, the images get swapped to disk and memory is freed. The problem is that it can happen that the cache handler starts constantly to swap images in and out (especially with with multi-megapixel images that are the norm today) and LibreOffice stalls to halt.

Because of this issues, TDF put up a tender to improve the situation with image handling and Collabora Productivity was selected to implement it, and I will do the development work.


Problems with the image life-cycle - detailed

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 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 reference counting technique, where we pass a objects 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 of unique ID the idea is to use the usual reference counting technique, that is normally used in this situation. The GraphicObject in 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, ...). It also has the implementation of swapping-in and out (but I'll explain this another time). 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, but the problem is that there are many many places this needs to be changed.
I will do the work as much incrementally as possible, with ensuring that the test cover the code and if needed add new tests or extend the existing ones. 

Currently almost finished is refactoring of the bitmap table (a list of named bitmaps, mostly used for shape fills or backgrounds) to use XBitmap instead of string based unique ID in the table. For this I needed to change OOXML (oox) and especially the ODF (xmloff) filter, and the document model.


Credits

Many thanks to TDF and users that support the foundation by providing donations, to make this work possible. 


To be continued...

by TomaĹž Vajngerl (noreply@blogger.com) at January 31, 2018 11:10 AM

Official TDF Blog: The Document Foundation announces LibreOffice 6.0: power, simplicity, security and interoperability from desktop to cloud

Berlin, January 31, 2018 – The Document Foundation announces LibreOffice 6.0, a major release and a dramatically improved free office suite, which celebrates the 7th anniversary of the availability of the very first version of LibreOffice. Today LibreOffice is more powerful, simple and secure, and offers superior interoperability with Microsoft Office documents.

LibreOffice 6.0 is immediately available for Windows, macOS and Linux, and for the cloud. The new major release adds a large number of significant new features to the core engine and to individual modules (Writer, Calc and Impress/Draw), with the objective of providing users with the best in terms of personal productivity.

A video summarizing the top new features of LibreOffice 6.0 is available on YouTube: https://www.youtube.com/watch?v=YHBve8v13VY.

Power

The Notebookbar, although still an experimental feature, has been enriched with two new variants: Grouped Bar Full for Writer, Calc and Impress, and Tabbed Compact for Writer. The Special Characters dialog has been reworked, with the addition of lists for Recent and Favorite characters, along with a Search field. The Customize dialog has also been redesigned, and is now more modern and intuitive.

In Writer, a Form menu has been added, making it easier to access one of the most powerful – and often unknown – LibreOffice features: the ability to design forms, and create standards-compliant PDF forms. The Find toolbar has been enhanced with a drop-down list of search types, to speed up navigation. A new default table style has been added, together with a new collection of table styles to reflect evolving visual trends.

The Mail Merge function has been improved, and it is now possible to use either a Writer document or an XLSX file as data source.

In Calc, ODF 1.2-compliant functions SEARCHB, FINDB and REPLACEB have been added, to improve support for the ISO standard format. Also, a cell range selection or a selected group of shapes (images) can be now exported in PNG or JPG format.

In Impress, the default slide size has been switched to 16:9, to support the most recent form factors of screens and projectors. As a consequence, 10 new Impress templates have been added, and a couple of old templates have been updated.

Simplicity

The old WikiHelp has been replaced by the new Help Online system, with attractive web pages that can also be displayed on mobile devices. In general, LibreOffice Help has been updated both in terms of contents and code, with other improvements due all along the life of the LibreOffice 6 family.

User dictionaries now allow automatic affixation or compounding. This is a general spell checking improvement in LibreOffice which can speed up work for Writer users. Instead of manually handling several forms of a new word in a language with rich morphology or compounding, the Hunspell spell checker can automatically recognize a new word with affixes or compounds, based on a “Grammar By” model.

Security

OpenPGP keys can be used to sign ODF documents on all desktop operating systems, with experimental support for OpenPGP-based encryption. To enable this feature, users will have to install the specific GPG software for their operating systems.

Document classification has also been improved, and allows multiple policies (which are now exported to OOXML files). In Writer, marking and signing are now supported at paragraph level.

Interoperability

OOXML interoperability has been improved in several areas: import of SmartArt and import/export of ActiveX controls, support of embedded text documents and spreadsheets, export of embedded videos to PPTX, export of cross-references to DOCX, export of MailMerge fields to DOCX, and improvements to the PPTX filter to prevent the creation of broken files.

New filters for exporting Writer documents to ePub and importing QuarkXPress files have also been added, together with an improved filter for importing EMF+ (Enhanced Metafile Format Plus) files as used by Microsoft Office documents. Some improvements have also been added to the ODF export filter, making it easier for other ODF readers to display visuals.

LibreOffice Online

LibreOffice Online is fundamentally a server service, and should be installed and configured by adding cloud storage and an SSL certificate. It might be considered an enabling technology for the cloud services offered by ISPs or the private cloud of enterprises and large organizations.

New features introduced with LibreOffice 6.0 aim to align the functionality of the desktop and cloud versions, especially in areas where users expect similar behavior. For instance, a Save As feature has been added, while the amount of rows managed by Calc has been increased to half a million. In addition, a Find and Replace dialog and spell checking support have been added to Writer, Calc and Impress.

Builds of the latest LibreOffice Online source code are available as Docker images: https://hub.docker.com/r/libreoffice/online/. Background on LibreOffice Online: https://nextcloud.documentfoundation.org/s/scDjtQPATAzpeyE.

LibreOffice Viewer for Android

The upcoming release of LibreOffice Viewer for Android will be able to create new documents, will offer a tab-based toolbar with formatting options, and will let users add pictures either from the camera or from a file stored locally or in the cloud. In addition, the Calc user interface will be improved with column headers, while Impress will offer a presentation mode. The release is planned during the first quarter of 2018.

Enterprise deployments

LibreOffice 6.0 represents the bleeding edge in term of features for open source office suites, and as such is targeted at technology enthusiasts, early adopters and power users.
For enterprise class deployments, TDF maintains the more mature 5.4 family – now at 5.4.4 – which should always be supported by certified professionals (a list is available here: http://www.libreoffice.org/get-help/professional-support/).

Several companies sitting in TDF Advisory Board (http://www.documentfoundation.org/governance/advisory-board/) are providing either value added Long Term Supported versions of LibreOffice or consultancy services for migrations and trainings, based on best practices by The Document Foundation.

LibreOffice is deployed by large organizations in every continent. A list of the most significant migrations announced in the media is available on TDF wiki: https://wiki.documentfoundation.org/LibreOffice_Migrations.

Availability of LibreOffice 6.0

LibreOffice 6.0 is immediately available from the following link: https://www.libreoffice.org/download/. Minimum requirements for proprietary operating systems are Microsoft Windows 7 SP1 and Apple macOS 10.9.

LibreOffice users, free software advocates and community members can support The Document Foundation with a donation at https://www.libreoffice.org/donate.

LibreOffice 6.0 is built with document conversion libraries from the Document Liberation Project: https://www.documentliberation.org.

Press Kit

The press kit, with background documents – Hybrid PDF, opened from within LibreOffice can be edited as normal ODT files – and high-resolution images, is here: https://nextcloud.documentfoundation.org/s/0hAzrnp6ecLJwbe.

January 31, 2018 11:06 AM

January 30, 2018

HackerNews

January 29, 2018

Planet KDE

KEXI 3.1.0 Beta & Frameworks

KDE Project:

Today is the release day for KEXI 3.1.0 Beta & its frameworks: https://community.kde.org/Kexi/Releases#3.1.0_Beta_1

Since version 3 it becomes KEXI not Kexi to suggest becoming a standalone app. It's standalone status includes being first-class app also outside of KDE Plasma. To make this real things such as useful yet simple file widget are developed or single click mode is really single click mode "even" on XFCE. Actually implementing optimal experience for Windows is quite similar to supporting XFCE.

KEXI Frameworks are now prepared for backward compatibility rules within the series >=3.1. So I would encourage to try KProperty if you need powerful property editing features in your app in place of tedious Qt list or tree views. There's KPropertyExample in the same repository. Then there's KDb if you actually expect more (something low or high-level) than QtSql, that is also need to create database or SQLite-based documents, what seems to be very popular container in our times. Then try KReport if you want escape from generating (ODF/HTML/whatever) documents "by hand", or QPainting them by hand, just to be able to print your application's data in a structured way with nice title, header, footer. Try KReportExample to see KReport in action with "a few lines of code" app.

Finally, try KEXI to create designs of reports mentioned above, design data-driven apps (lots of features are missing before you're able to desing, say, a JIRA like app but it IS coming), integrate data, perform some analysis (again, lots of these features are not shipped as stability was, again, the goal).

I trust stability makes KEXI and its frameworks pretty competitive already. The codebase was tested with Coverity, works with gcc, clang, msvc. Critical parts are autotested much more than in the 2.9 or 3.0 times. Much of the 220 improvements since 3.0.2 is stability, usability or API fixes.

We expect stable release in one month. And here's one request: if you're packager or know one, please send link to available 3.1 packages so we can eventually have a Download page. If you are able to create AppImage or Flatpak packages or work on Craft support for Windows, or test existing source or binary packages once they are published, we are looking for help.

by Jarosław Staniek (jstaniek) at January 29, 2018 08:20 PM

January 28, 2018

Slashdot

Should Apps Replace Title Bars with Header Bars?

Gnome contributor Tobias Bernard is on a crusade against title bars -- "the largely empty bars at the top of some application windows [that] contain only the window title and a close button." Instead he wants to see header bars -- "a newer, more flexible pattern that allows putting window controls and other UI elements in the same bar." Tobias Bernard writes: Header bars are client-side decorations (CSD), which means they are drawn by the app rather than the display server. This allows for better integration between application and window chrome. All GNOME apps (except for Terminal) have moved to header bars over the past few years, and so have many third-party apps. However, there are still a few holdouts. He's announcing the CSD Initiative, "an effort to get apps (both GNOME and third-party) to drop title bars and adopt GNOME-style client-side decorations... The only way to solve this problem long-term is to patch applications upstream to not use title bars. So this is what we'll have to do." Talk to the maintainers and convince them that this is a good idea Do the design work of adapting the layout and make mockups Figure out what is required at a technical level Actually implement the new layout and get it merged Implementation is already in progress for Firefox, though it has not yet been started for other high-priority apps like LibreOffice, GNOME Terminal, and Skype. "If you want to help with any of the above tasks," writes Tobias, "come talk to us on #gnome-design on IRC/Matrix."

Read more of this story at Slashdot.

by EditorDavid at January 28, 2018 02:34 PM

January 18, 2018

HackerNews

January 15, 2018

Slashdot

City of Barcelona Dumps Windows For Linux and Open Source Software

An anonymous reader quotes Open Source Observatory: The City of Barcelona is migrating its computer systems away from the Windows platform, reports the Spanish newspaper El País. The City's strategy is first to replace all user applications with open-source alternatives, until the underlying Windows operating system is the only proprietary software remaining. In a final step, the operating system will be replaced with Linux... According to Francesca Bria, the Commissioner of Technology and Digital Innovation at the City Council, the transition will be completed before the current administration's mandate ends in spring 2019. For starters, the Outlook mail client and Exchange Server will be replaced with Open-Xchange. In a similar fashion, Internet Explorer and Office will be replaced with Firefox and LibreOffice, respectively. The Linux distribution eventually used will probably be Ubuntu, since the City of Barcelona is already running 1,000 Ubuntu-based desktops as part of a pilot... Barcelona is the first municipality to have joined the European campaign 'Public Money, Public Code'. This campaign is an initiative of the Free Software Foundation Europe (FSFE) and revolves around an open letter advocating that publicly funded software should be free. Currently, this call to public agencies is supported by more than 100 organisations and almost 15,000 individuals. With the new open-source strategy, Barcelona's City Council aims to avoid spending large amounts of money on licence-based software and to reduce its dependence on proprietary suppliers through contracts that in some cases have been closed for decades.

Read more of this story at Slashdot.

by EditorDavid at January 15, 2018 05:39 AM

January 09, 2018

The Document Foundation Planet

Official TDF Blog: LibreOffice community focus: Documentation

Earlier this month we talked to the localisation community about the preparations they are making for LibreOffice 6.0, which is due to be released in late January (or early February). Now we turn to the documentation project, and Olivier Hallot, who is coordinating updates to guidebooks and a new help system…

olivier_hallot_07062010_964x1036What has the documentation community been working on in preparation for LibreOffice 6.0?

The community is engaged in delivering two major features for the 6.0 release: the first is a new and updated Getting Started Guide, a book targeted at new users of LibreOffice 6.0. We included the latest developments that are in the scope of an introductory text for LibreOffice 6.0. For 2018 we are assembling a team of writers to update our other guides, starting with the Calc Guide.

The other major feature is the new LibreOffice help system, a completely redesigned help system that now uses the operating system’s web browser to display help pages. Here’s a screenshot from the LibreOffice 6.0 release notes, showing how it looks in a mobile web browser:

What are your favourite new features in this release?

I always appreciate applications that have beautiful aesthetics. When choosing between two applications or desktop environments with the same features, I take the one that’s good-looking and has a well-crafted user interface. There are so many excellent programs with clumsy interfaces or ugly aesthetics struggling to survive. It is purely subjective but in the end, beauty pays. So my take for 6.0 are the features that bring a better and nicer UI: new icons, toolbars and redesigned dialogs. Here’s a preview of the Elementary icon set, which will be included in 6.0:

Aesthetics, together with essential technology evolutions, were the drive to develop our new help system based on web technology. We expect to open an avenue for improving the contents of our help with multimedia, animations and better navigation – altogether bringing a modern web experience for our users who are reading the help.

What tools and services do you use in the documentation community?

At the moment we use Plone as our document repository, and we have a workflow for editing, revision and publication. Released documents are available on our documentation website for download, and some l10n (localisation) communities prefer to use the TDF wiki.

With the recent developments in LibreOffice Online, I am planning to use it for document editing and production, in a simpler way than using Plone. LibreOffice Online is by far the best online editor for OpenDocument formatted files, and is an essential feature for preserving our current documents and making editing easier.

For 2018, we will work to develop an special online editor for help files, making it easier for occasional contributors to make changes to the content.

Finally, how can people get involved with the documentation community?

The first step is to read this page and follow the instructions there. We need good software documenters, along with people who really know how an office suite works, and who are capable of writing about new features with authority.

Thanks Olivier, and thanks to the whole documentation community for their work in LibreOffice 6.0. Over the next few weeks, we’ll be talking to other projects, including QA and development – keep checking this blog for updates.

January 09, 2018 12:11 PM

December 25, 2017

ODF Wikipedia Page

Janvlug: /* Support for OpenDocument */

Support for OpenDocument

← Previous revision Revision as of 09:46, 25 December 2017
Line 213: Line 213:
 
Several governments, companies, organizations and software products support the OpenDocument format. For example:
 
Several governments, companies, organizations and software products support the OpenDocument format. For example:
   
* The OpenDoc Society run frequent [[ODF Plugfest]]s in association with industry groups and Public Sector organisations. The 10th Plugfest<ref>[http://plugfest.opendocumentformat.org/2014-london/ 10th Plugfest hosted by the UK Cabinet Office December 2014]</ref> was hosted by the UK [[Government Digital Service]] in conjunction with industry associations including the [[OpenForum Europe]] and [[OpenUK | OpenUK (formerly Open Source Consortium)]].
+
* The OpenDoc Society runs frequent [[ODF Plugfest]]s in association with industry groups and Public Sector organisations. The 10th Plugfest<ref>[http://plugfest.opendocumentformat.org/2014-london/ 10th Plugfest hosted by the UK Cabinet Office December 2014]</ref> was hosted by the UK [[Government Digital Service]] in conjunction with industry associations including the [[OpenForum Europe]] and [[OpenUK | OpenUK (formerly Open Source Consortium)]].
 
** An output of the 10th Plugfest was an ODF toolkit<ref>http://www.openforumeurope.org/library/odf-toolkit-2/</ref> which includes "Open Document Format principles for Government Technology" that has the purpose of simply explaining the case for ODF directed at the "average civil servant" and includes an extract from the UK Government policy relating to Open Document Format.
 
** An output of the 10th Plugfest was an ODF toolkit<ref>http://www.openforumeurope.org/library/odf-toolkit-2/</ref> which includes "Open Document Format principles for Government Technology" that has the purpose of simply explaining the case for ODF directed at the "average civil servant" and includes an extract from the UK Government policy relating to Open Document Format.
 
** The toolkit also includes a single page graphical image<ref>https://web.archive.org/web/20150620003502/http://www.openforumeurope.org/library/ODF/odf-toolkit-folder/OFE-COIS-ODF-infographic-release-02150325-by-sa.jpeg</ref> designed to articulate the consequences of not choosing Open Document Format. The illustration has now been translated into more than 10 languages.
 
** The toolkit also includes a single page graphical image<ref>https://web.archive.org/web/20150620003502/http://www.openforumeurope.org/library/ODF/odf-toolkit-folder/OFE-COIS-ODF-infographic-release-02150325-by-sa.jpeg</ref> designed to articulate the consequences of not choosing Open Document Format. The illustration has now been translated into more than 10 languages.

by Janvlug at December 25, 2017 09:46 AM

December 18, 2017

The Document Foundation Planet

Official TDF Blog: Document Liberation Project: 2017 in review


While most of the posts on this blog are about LibreOffice, another project overseen by The Document Foundation is DLP – the Document Liberation Project. Whereas LibreOffice is an end-user application, DLP is a collection of free and open source software libraries that help to convert document formats. Developers can use these libraries in their programs, in order to import and export a large variety of files – including proprietary formats. Many well-known applications use DLP libraries, including Inkscape, Scribus, Calligra and of course LibreOffice.

So, what happened in DLP throughout 2017? Read on for our round-up of the year’s news…

New import filter: QuarkXPress

Aleksas Pantechovskis, as part of the Google Summer of Code, worked on a new import filter for QuarkXPress documents: libxqp. It currently supports QuarkXPress 3.1 – 4.1 documents, and this image shows it in action (original QuarkXPress file on the left, and how it’s converted into OpenDocument on the right):

Big improvements to Lotus 123 import

Laurent Alonso made some major improvements to the Lotus 123 filter, adding support for many formatting and layout options. Check out these pictures as an example – the top shows a Lotus 123 file in LibreOffice 5.3, missing almost all of its formatting. Underneath, however, you can see how it’s rendered in LibreOffice 5.4, with much more of the formatting present (click for bigger):

New library releases

Throughout the year, many libraries were updated as well. Here’s a summary:

  • 2 Aug – libepubgen 0.0.1 – This fixes escaping of HTML entities, and the code has been updated to C++11
  • 12 Sep – libwpd 0.10.2X – Also updated to C++11, and includes various fixes from OSS-Fuzz
  • 12 Sep – libwpg 0.3.2 – Improves performance of reading image data from WPG2 files
  • 14 Sep – libzmf 0.0.2 – Minor code cleanups and some fixes from OSS-Fuzz
  • 15 Sep – libcdr 0.1.4 – Fixes issues found by Coverity, and require C++11 for build
  • 16 Sep – libfreehand 0.1.2 – Parses more features, including text on paths, stroke patterns, arrows, and custom line and fill styles
  • 21 Oct – libvisio 0.1.6 – Various improvements to import of MS Visio files, plus Coverity and OSS-Fuzz fixes
  • 23 Oct – libetonyek 0.1.7 – Improves support for gradients, cell styles, non-RGB colours, and table border lines
  • 13 Dec – libepubgen 0.1.0 – EPUB3 support, plus support for embedded fonts, cover images and footnotes
  • 13 Dec – writerperfect 0.9.6 – Adds support for StarOffice Writer and Zoner Draw documents, and includes universal conversion tools

Find out more!

For details on the libraries mentioned above, see the projects page on the site. And check out the contribute page to see how you can help – because even if you’re not a developer, you can prepare sample documents for testing. Oh, and to learn more about DLP, watch this short video!

December 18, 2017 01:56 PM

December 15, 2017

The Document Foundation Planet

Official TDF Blog: Update about Marketing Activities in 2nd Half of 2017

LibreOffice has turned seven on September 28, 2017. When we launched our first press release on September 28, 2010, our entire mailing list was quite small: 200 recipients gathered from different sources with journalists and media contacts from all over the world.

During these seven years, my main task has been media relations. One of the most important objectives has been the improvement of the mailing lists, both in terms of quantity and quality.

Today, after seven years, the size of the database has changed dramatically, as we have almost 19,000 email address in our mailing lists, which are targeted based on country, platform (desktop, iOS, Android, mobile, cloud) and focus (security and reviews). In 2017, we have started to target industry analysts, but this list is far from being complete.

Based on geography, we have 6 global lists (journalists, analysts, teams), 70 lists for Europe, 30 lists for the Americas, 5 lists for Pacific, 21 lists for Africa, 18 lists for Asia Middle East, 17 lists for Asia, and 24 lists for Asia Far East. In addition, around 5,000 records are updated and 2,500 are added each year.

Lists are global by country, plus each country – when possible – has a specific list of people who opened a previous press release. Thanks to this targeted database, we have a hit rate around 30%, twice as much as the global PR industry.

For major announcements, individual emails are sent to friendly journalists with a specific angle. I am connected to over 2,000 journalists via LinkedIn, and I have regular contacts with many of them.

Of course, taking care of mailing lists would not be enough without a monthly average of 50 personal contacts with editors, via email and/or phone, and over 100 answers to specific requests (pictures, statistics, review related questions and other info about TDF and LibreOffice).

Another project I have been working at is the production of basic slide decks on different subjects, which can be used by community members to create their own slide decks for presentations. At the moment I am working at updating the following slide decks: Project History & Background, LibreOffice & Competitive Presentation, Document Standards & Open Document Format, Advantages of ODF vs OOXML, Migration Protocol & Training Protocol, plus Useful Slides for Presentations. I also have less organized slides about Digital Citizenship, or the relationship between Technology and Individual Freedom of Choice.

Community members are warmly invited to send me an email to check if I have something which can help them to add some beef to their presentations. In fact, in some cases I test slide decks – adding new angles and concepts – in front of small audiences, before releasing them “officially” on the wiki.

Looking forward, I plan to bring analyst relations up to speed (as media), and improve community-focused activities, supporting the organization of local events and participate when it makes sense budget wise. I would also like to facilitate NLP (native language projects) involvement in the project, helping the integration of local communities within TDF and fostering their growth when they are small or even completely missing.

December 15, 2017 10:30 AM

December 05, 2017

The Document Foundation Planet

Miklos Vajna: EPUB3 export improvements in Libreoffice Writer

I worked on improving the EPUB3 export filter in LibreOffice recently. First, thanks to Nou&Off in cooperation with a customer who made this work possible. Since the previous blog entry there have been a number of improvements around 4 topics.

https://farm5.staticflickr.com/4540/38847800651_d5271ced3a_o.png

The character properties of link text is now handled correctly, in the above example you can see that the text is red, and this comes from a character style.

Improved table support

Previously the support for tables was there just to not loose content, now all kinds cell, row and table properties are handled correctly. A few samples

  • custom cell width:

https://farm5.staticflickr.com/4566/38847800611_38b8483d7f_o.png
  • custom row height:

https://farm5.staticflickr.com/4580/38847800521_26285a9152_o.png
  • row span:

https://farm5.staticflickr.com/4540/38847800461_359651bc3d_o.png

So the table support should be now decent, covering row and column spanning and various cell border properties.

Improved image support

Previously only the simplest as-character anchoring was supported. Now much more cases are handled. Two examples:

  • image borders:

https://farm5.staticflickr.com/4541/24975193838_94818bd1ed_o.png
  • image with a caption:

https://farm5.staticflickr.com/4568/24975193608_83239bf287_o.png

This includes various wrap types (to the extent HTML5 allows representing ODF wrap types).

Font embedding

If the user chooses to embed fonts (via File → Properties → Font → Embed), then the EPUB export now handles this. Here is a custom font that is typically not available:

https://farm5.staticflickr.com/4561/38847800811_613d6fbbd2_o.png

(The screenshot is from the Calibre ebook reader.)

All this is available in master (towards LibreOffice 6.1), or you can grab a daily build and try it out right now. :-)

December 05, 2017 10:11 AM

November 30, 2017

HackerNews

November 28, 2017

ODF Wikipedia Page

201.217.145.162: Update Agesic reference

Update Agesic reference

← Previous revision Revision as of 15:21, 28 November 2017
Line 290: Line 290:
 
|class="hlist" style="vertical-align:top;padding:0.25em 0.5em;"|
 
|class="hlist" style="vertical-align:top;padding:0.25em 0.5em;"|
 
* [[Brazil]]
 
* [[Brazil]]
* [[Uruguay]]<ref>{{cite web |url=http://www.agesic.gub.uy/innovaportal/file/497/1/estandares_ofimatica_v20.pdf |title=Estándares de ofimática |publisher=Agestic.gub.uy |date= |accessdate=2013-05-01}}</ref>
+
* [[Uruguay]]<ref>{{cite web |url=http://www.agesic.gub.uy/innovaportal/file/497/1/estandares_ofimatica_v20.pdf |title=Estándares de ofimática |publisher=Agencia de Gobierno Electrónico y Sociedad de la Información y del Conocimiento |date= |accessdate=2017-11-28}}</ref>
 
* [[Venezuela]]
 
* [[Venezuela]]
 
|-
 
|-

by 201.217.145.162 at November 28, 2017 03:21 PM

November 27, 2017

Apache OpenOffice Blog

Open Document Editors Devroom at FOSDEM 18, Brussels FOSDEM is 3-4 Feb 2018

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

As usual, the Open Document Editors DevRoom will be jointly organized by Apache OpenOffice and LibreOffice, on Saturday, February 3 (from 10:30AM to 6:30PM, room AW1.120). The shared devroom gives every project in this area a chance to present ODF related developments and innovations.

We are now inviting proposals for talks about Open Document Editors or the ODF standard document format, on topics such as code, localization, QA, UX, extensions, tools and adoption related cases. This is a unique opportunity to show new ideas and developments to a wide technical audience. Please do keep in mind, though, that product pitches are not allowed at FOSDEM.

Length of talks should be limited to a maximum of 30 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/FOSDEM18

While filing your proposal, please provide the title of your talk, a short abstract (one or two paragraphs), some information about yourself (name, bio and photo, but please do remember that your profile might be already stored at Pentabarf).

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-AT-fosdem.org

The deadline is Monday, December 4th, 2017. Accepted speakers will be notified by Monday, December 11th, 2017. The schedule will be published before Friday, December 15, 2017.

Recording Permission

The talks in the Open Document Editors DevRoom will be audio and video recorded, and possibly streamed live too.

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”.

by pescetti at November 27, 2017 07:40 AM

November 23, 2017

The Document Foundation Planet

Naruhiko Ogasawara: REPORT: LibreOffice mini-conference 2017 Japan (in openSUSE.Asia Summit 2017 Tokyo)



On Oct 22nd, 2017, we hosted an event titled "LibreOffice mini-conference 2017 Japan," as a sub-event of "openSUSE.Asia Summit 2017 Tokyo."
openSUSE.Asia Summit is:
"one of the great events for openSUSE community (i.e., both contributors, and users) in Asia. Those who usually communicate online can get together from all over the world, talk face to face, and have fun. Members of the community will share their most recent knowledge, experiences, and learn FLOSS technologies surrounding openSUSE."
This year hosted this event at the University of Electro-Communications (UEC) in Chofu, Tokyo, and I was honored to be a committee member.
In spite of the bad weather immediately before the hit of the huge typhoon Lan, over 150 participants from nine countries gathered in two days (Oct 21st and 22nd), and we enjoyed various talks and workshops on openSUSE and various open source software (including LibreOffice, of course) and were able to interact with each other.

Thanks to The Document Foundation for helping the travel cost, we could invite 3 speakers from cities far from Tokyo, then we had 6 speakers from 3 countries (Taiwan, Indonesia, and Japan).
Sponsor board and event board.  See "LibreOffice: The Document Foundation" logo!

Talk highlight

Let's see each talk in our mini-conference!

Opening Talk: LibreOffice: The Office Suite with Mixing Bowl Culture, by Naruhiko Ogasawara


My talk :)
Introducing LibreOffice to use the keyword "Mixing bowl," taken from TDF official slide provided as a marketing material.
I love LibreOffice because everyone in the community is kind to anyone who acts to do something.  I aimed to convey a message that anyone can participate LibreOffice project in the same opportunities, and I could do (hope so).

The Interoperability of Documents, by Franklin Weng

Not only the full talk in mini-conference, but he also had a lightning talk on 21st Oct evening. by hisa_x.  Flickr link


Franklin, who leads ODF migration in Taiwan, talked about the importance of creating interoperable documents and how to do it.  "Document interoperability = Working together better" in this talk was a simple and strong, important message.
One of the keys is "document format," so we must choose ODF instead of OOXML to make interoperable documents (and of course LibreOffice is the best office suite to generate ODF ;).
I thought "interoperability" was a keyword of the mini-conference (coincidentally, many talks mentioned that).

State of CJK issues of LibreOffice, by Shinji Enoki

Shinji wearing Rome conference T-shirt. Cool! by hisa_x. Flickr link
https://speakerdeck.com/enoki/state-of-cjk-issues-of-libreoffice-libreoffice-miniconf

Shinji Enoki is a member of LibreOffice Japanese Team (Japanese NLP), same as mine.  He continuously attended LibreOffice Conference for years, and this talk was "replay" of last global conference talk in Rome.
In The Next Decade Manifesto,
WE COMMIT OURSELVES:  to support the preservation of mother tongues by encouraging all peoples to translate, document, support, and promote our office productivity tools in their mother tongue
Then, not only UI/document translations but language-dependent features work well is also important.   But sometimes it is quite hard for developers to understand what is "work well" in language which is not his/her mother tongue.  Especially CJK, RTL for a developer who uses latin language.  So we, Asian users have to improve LibreOffice by ourselves and to help developers to go the right way.
He introduced current status of CJK issues with examples such as IVS problem, and several resources provided by the project:

Introduction to Japanese Darkness "Excel Houganshi," by Rin Nakamura

Rin Nakamura talking about Excel Houganshi. by hisa_x. Flickr link
Hmm... it is quite hard to explain what the talk means because it very tied to Japanese culture... but I'm trying.
"Houganshi (方眼紙)" means "graph paper," paper with pre-printed square grids.  In Japan, it is common to use Excel like as Houganshi, to make all cell width and height exactly same.  You can easily see so many "Excel Houganshi" via google images.
Nakamura-san claimed "You don't do this (to create "Excel Houganshi"), then introduced an example that he was bothered by such Excel Houganshi, and demonstrated the trick to make it a proper document based on it.
His message was "use tools (like office suite) with proper way."   Excel Houganshi has been a good technic in "print to paper" era, but in the digital era, it became "Japanese Darkness" culture.  No one wants to maintain Excel Houganshi document.  So, the talk was strongly related to Franklin's talk;  Excel Houganshi is exchangeable, but NOT interoperable.

Write Your Story with OpenSource, by Umul Sidikoh

Umul talking with demonstrations. by Edwin Zakaria. Flickr link

Umul from Indonesia told us how to write a document using Writer style features, with lots of demonstrations.  Live demo sometimes makes us very frustrated, but she tried well :).
This talk also related to interoperability.  Using style feature makes documents more interoperable.  It is "right way" to use Writer, instead of insert new line, white space or specify font directly, as Franklin mentioned.
I heard that this was her first overseas trip and she seemed to enjoy both the conference and Tokyo.  I believe it was a great step for her to move forward to contributing LibreOffice, and she'll continue to contribute us, with contacting other LibreOffice people.

How to build LibreOffice on your desktop, by Masataka Kondo

(Oops, I couldn't find out his photo... ><)


LibreOffice is open source software.  It means, we could build LibreOffice from source code by ourselves.  Kondo-san, another member of LibreOffice Japanese Team, introduced LibreOffice building-how-to with openSUSE and Linux Mint.
Franklin commented we also could try with Docker (and he let us know the link).  I never tried to use Docker to build LibreOffice, then I would like to try near future.

Lightning Talks

openSUSE.Asia Summit has 2 lightning talk sessions in evening each of day.
In day 1 session, Franklin presented "Become a TDF Member."  It was fantastic!  Everyone was bursting laughing :).

In day 2 (the day of LibreOffice mini-conference) session, two interns from iCraft, the company which provides LibreOffice support in Japan and sponsored openSUSE.Asia Summit, had talks related their home country (Tunisia and Ethiopia) and LibreOffice.  They are also very interested.
TRABELSI Mohamed talking about Tunisia and LibreOffice, by hisa_x, Flickr link
Aschalew Arega Ademe talking about Ethiopian IT / FLOSS includes LibreOffice, by hisa_x, Flickr link

What is a "LibreOffice mini-conference"?  Is this different from LibreOffice Kaigi?

Anyway, I would like to explain that ;)
In my personal opinion, since LibreOffice is a consumer product, it is important that there are events where users can participate it by their mother tongue. That's why there is LibreOffice Kaigi. "Kaigi" is taken from a Japanese word "会議" means "conference," which means that it is the event for Japanese speakers by Japanese speakers. Of course, it is respect for RubyKaigi (the annual conference of the programming language Ruby), too.
Nonetheless, for the community members, of course, international exchange is also very important. We already have an annual event called LibreOffice Conference which is a wonderful opportunity to exchange information and opinions. However, the LibreOffice Conference is held in Europe (I do not want to say that is a bad thing), it is a bit difficult for Asian "neighbors" to gather. We use different mother tongues, but we live in a similar time zone, similar culture, so there should be something we can do together. Therefore, I think that it is better to have an "international, regional" conference. That is a "mini-conference."

Conclusion

I could say that our "mini-conference" this year was a huge success.  Everyone enjoyed lots of interesting talks and spent a great time to talk each other.

Thanks to all attendees, speakers, sponsors (includes The Document Foundation) and excellent volunteer staffs of openSUSE.Asia Summit.  Hope others will host another mini-conference (or any title, means "international, regional") and we will meet there!
Speakers group photo in our booth, by Edwin Zakaria. Flickr link 


Note:

I believe all videos of openSUSE.Asia Summit 2017 will be published soon.  I will inform you here when it's done immediately.


by Naruhiko Ogasawara (noreply@blogger.com) at November 23, 2017 04:22 AM

November 22, 2017

ODF Wikipedia Page

MetaManFromTomorrow: Fixed word processing and graphics link

Fixed word processing and graphics link

← Previous revision Revision as of 04:41, 22 November 2017
Line 117: Line 117:
 
The most common [[filename extension]]s used for OpenDocument documents are:<ref>{{cite web|url=http://www.ua.es/en/rua/formatos.html |title=UA.es |work=ua.es |language=es |deadurl=yes |archiveurl=https://web.archive.org/web/20090615185541/http://www.ua.es/en/rua/formatos.html |archivedate=15 June 2009 }}</ref><ref name="hg flat opendocument">{{cite web |url=http://www.ensode.net/roller/dheffelfinger/entry/openoffice_documents_version_control_with |title=OpenOffice.org Document Version Control With Mercurial |accessdate=7 June 2010}}</ref>
 
The most common [[filename extension]]s used for OpenDocument documents are:<ref>{{cite web|url=http://www.ua.es/en/rua/formatos.html |title=UA.es |work=ua.es |language=es |deadurl=yes |archiveurl=https://web.archive.org/web/20090615185541/http://www.ua.es/en/rua/formatos.html |archivedate=15 June 2009 }}</ref><ref name="hg flat opendocument">{{cite web |url=http://www.ensode.net/roller/dheffelfinger/entry/openoffice_documents_version_control_with |title=OpenOffice.org Document Version Control With Mercurial |accessdate=7 June 2010}}</ref>
   
* <code>.odt</code> and <code>.fodt</code> for [[word processing]] (text) documents
+
* <code>.odt</code> and <code>.fodt</code> for [[word processor|word processing]] (text) documents
 
* <code>.ods</code> and <code>.fods</code> for [[spreadsheet]]s
 
* <code>.ods</code> and <code>.fods</code> for [[spreadsheet]]s
 
* <code>.odp</code> and <code>.fodp</code> for [[presentation]]s
 
* <code>.odp</code> and <code>.fodp</code> for [[presentation]]s
* <code>.odg</code> and <code>.fodg</code> for [[graphic]]s
+
* <code>.odg</code> and <code>.fodg</code> for [[graphics]]
 
* <code>.odf</code> for [[formula]]e, mathematical equations
 
* <code>.odf</code> for [[formula]]e, mathematical equations
   

by MetaManFromTomorrow at November 22, 2017 04:41 AM

November 14, 2017

Slashdot

Fedora 27 Released

The Fedora Project has announced the general availability of Fedora 27 Workstation and Fedora 27 Atomic editions. Fedora 27 brings with it "thousands of improvements" from both the Fedora Community and various upstream software projects, the team said on Tuesday. From a post on Fedora Magazine: The Workstation edition of Fedora 27 features GNOME 3.26. In the new release, both the Display and Network configuration panels have been updated, along with the overall Settings panel appearance improvement. The system search now shows more results at once, including the system actions. GNOME 3.26 also features color emoji support, folder sharing in Boxes, and numerous improvements in the Builder IDE tool. The new release also features LibreOffice 5.4.

Read more of this story at Slashdot.

by msmash at November 14, 2017 04:00 PM

November 13, 2017

Slashdot

Munich Council: To Hell With Linux, We're Going Full Windows in 2020

The German city of Munich, which received much popularity back in the day when it first ditched Microsoft's services in favor of open-source software, has now agreed to stop using Linux and switch back to Windows. If the decision is ratified by the full council in two weeks, Windows 10 will start rolling out across the city in 2020. From a report: A coalition of Social Democrats and Conservatives on the committee voted for the Windows migration last week, Social Democrat councillor Anne Hubner told The Register. Munich rose to fame in the open-source world for deciding to use Linux and LibreOffice to make the city independent from the claws of Microsoft. But the plan was never fully realised -- mail servers, for instance, eventually wound up migrating to Microsoft Exchange -- and in February the city council formally voted to end Linux migration and go back to Microsoft. Hubner said the city has struggled with LiMux adoption. "Users were unhappy and software essential for the public sector is mostly only available for Windows," she said. She estimated about half of the 800 or so total programs needed don't run on Linux and "many others need a lot of effort and workarounds." Hubner added, "in the past 15 years, much of our efforts were put into becoming independent from Microsoft," including spending "a lot of money looking for workarounds" but "those efforts eventually failed." A full council vote on Windows 10 2020 migration is set for November 23, Hubner said. However, the Social Democrats and Conservatives have a majority in the council, and the outcome is expected to be the same as in committee.

Read more of this story at Slashdot.

by msmash at November 13, 2017 05:25 PM

November 10, 2017

ODF Wikipedia Page

50.196.224.125: IBM i (formerly AS/400) SQL tool provides XMLX support for output only.

IBM i (formerly AS/400) SQL tool provides XMLX support for output only.

← Previous revision Revision as of 14:37, 10 November 2017
Line 182: Line 182:
 
* [[Scribus]] imports .odt and .odg
 
* [[Scribus]] imports .odt and .odg
 
* [[SoftMaker Office]]
 
* [[SoftMaker Office]]
  +
* [http://www.SQLiQuery.com SQL iQuery for IBM i] (output support)
 
* [[Sun Microsystems]] [[StarOffice]]
 
* [[Sun Microsystems]] [[StarOffice]]
 
* [[TextEdit]]
 
* [[TextEdit]]

by 50.196.224.125 at November 10, 2017 02:37 PM

The Document Foundation Planet

Miklos Vajna: Basic EPUB3 export in Libreoffice

https://farm5.staticflickr.com/4577/37588898064_117dc4a933_o_d.png

I worked on a new EPUB3 export filter in LibreOffice recently. First, thanks to Nou&Off in cooperation with a customer who made this work possible. The current state is that basic features work nicely to the extent that the filter is probably usable for most books (they typically mostly have just text with minimal formatting), so this post aims to explain the architecture, how the various pieces fit together.

The above picture shows the building blocks. The idea is that nominally EPUB is a complete export filter, but instead of doing all the work, we offload various sub-tasks to other modules:

  • First we invoke the existing (flat) ODT export, so we can work with ODF instead of with the UNO API directly. This will be useful in the next step.

  • Then we feed the SAX events from the ODT export to a new librevenge text export. Given that the librevenge API is really close to ODF (and xmloff/ has quite some code to map the UNO API to ODF), here it pays off to work with ODF and not with the UNO API directly.

  • The librevenge text export talks to a librevenge generator, which is David Tardon’s excellent libepubgen in this case.

  • Finally libepubgen calls back to LibreOffice, and our package code does the ZIP compression.

The setup is a bit complicated, but it has a number of advantages:

  • Instead of reinventing the wheel, LO and DLP now shares code, libepubgen is now a dependency of LibreOffice.

  • libepubgen doesn’t bring its own ZIP writer code, it can nicely reuse our existing one.

  • This is a great opportunity to finally write an ODT→librevenge bridge, so other DLP-based export libs can be added in the future (e.g. librvngabw).

  • If we ever want to export to EPUB from Draw/Impress, libepubgen will help us there as well.

As a user, here is a list of features you can expect working:

  • plain text should work fine (formatting may be lost, but content should be fine)

  • table of contents, as long as you properly use headings or you separate chapters by page breaks

  • export options: EPUB3 vs EPUB2, split on headings vs page breaks

  • basic set of character and paragraph properties should work

During development I regularly used epubcheck, so hopefully the export result is usually valid.

All this is available in master (towards LibreOffice 6.0), or you can grab a daily build and try it out right now. :-)

November 10, 2017 10:19 AM

November 07, 2017

Slashdot

Apache OpenOffice: We're OK With Not Being Super Cool

The Register's Thomas Claburn, interviews Jim Jagielski, Apache Software Foundation President and Apache OpenOffice project mentor. From the story: Despite being the subject of a deathwatch -- perhaps mainly by fans of rival LibreOffice -- AOO appears to be rather popular, with the 4.1.4 update racking up at least 1.6 million downloads. [...] While AOO and the ASF formulate a formal statement of direction for the project, Jagielski said more or less that all's well. "AOO is not, and isn't designed to be, the 'super coolest open source office suite with all the latest bells and whistles,'" Jagielski continued. "Our research shows that a 'basic,' functional office suite, which is streamlined with a 'simple' and uncluttered, uncomplicated UI, serves an incredible under-represented community. "Other office suites are focusing on the 'power user' which is a valuable market, for sure, but the real power and range for an open-source office suite alternative is the vast majority which is the 'rest of us. Sometimes we all forget how empowering open source is to the entire world."

Read more of this story at Slashdot.

by msmash at November 07, 2017 08:40 PM

November 06, 2017

ODF Wikipedia Page

Mikeywil: Updated link as previous was 404-ing

Updated link as previous was 404-ing

← Previous revision Revision as of 16:45, 6 November 2017
Line 213: Line 213:
   
 
* The OpenDoc Society run frequent [[ODF Plugfest]]s in association with industry groups and Public Sector organisations. The 10th Plugfest<ref>[http://plugfest.opendocumentformat.org/2014-london/ 10th Plugfest hosted by the UK Cabinet Office December 2014]</ref> was hosted by the UK [[Government Digital Service]] in conjunction with industry associations including the [[OpenForum Europe]] and [[OpenUK | OpenUK (formerly Open Source Consortium)]].
 
* The OpenDoc Society run frequent [[ODF Plugfest]]s in association with industry groups and Public Sector organisations. The 10th Plugfest<ref>[http://plugfest.opendocumentformat.org/2014-london/ 10th Plugfest hosted by the UK Cabinet Office December 2014]</ref> was hosted by the UK [[Government Digital Service]] in conjunction with industry associations including the [[OpenForum Europe]] and [[OpenUK | OpenUK (formerly Open Source Consortium)]].
** An output of the 10th Plugfest was an ODF toolkit<ref>http://www.openforumeurope.org/library/ODF/odf-toolkit-folder/</ref> which includes "Open Document Format principles for Government Technology" that has the purpose of simply explaining the case for ODF directed at the "average civil servant" and includes an extract from the UK Government policy relating to Open Document Format.
+
** An output of the 10th Plugfest was an ODF toolkit<ref>http://www.openforumeurope.org/library/odf-toolkit-2/</ref> which includes "Open Document Format principles for Government Technology" that has the purpose of simply explaining the case for ODF directed at the "average civil servant" and includes an extract from the UK Government policy relating to Open Document Format.
 
** The toolkit also includes a single page graphical image<ref>https://web.archive.org/web/20150620003502/http://www.openforumeurope.org/library/ODF/odf-toolkit-folder/OFE-COIS-ODF-infographic-release-02150325-by-sa.jpeg</ref> designed to articulate the consequences of not choosing Open Document Format. The illustration has now been translated into more than 10 languages.
 
** The toolkit also includes a single page graphical image<ref>https://web.archive.org/web/20150620003502/http://www.openforumeurope.org/library/ODF/odf-toolkit-folder/OFE-COIS-ODF-infographic-release-02150325-by-sa.jpeg</ref> designed to articulate the consequences of not choosing Open Document Format. The illustration has now been translated into more than 10 languages.
 
* 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.

by Mikeywil at November 06, 2017 04:45 PM

November 02, 2017

ODF Wikipedia Page

FrescoBot: Bot: link syntax

Bot: link syntax

← Previous revision Revision as of 08:27, 2 November 2017
Line 212: Line 212:
 
Several governments, companies, organizations and software products support the OpenDocument format. For example:
 
Several governments, companies, organizations and software products support the OpenDocument format. For example:
   
* The OpenDoc Society run frequent [[ODF Plugfest]]s in association with industry groups and Public Sector organisations. The 10th Plugfest<ref>[http://plugfest.opendocumentformat.org/2014-london/ 10th Plugfest hosted by the UK Cabinet Office December 2014]</ref> was hosted by the UK [[Government Digital Service]] in conjunction with industry associations including the [[OpenForum Europe]] and [[OpenUK | OpenUK (formerly Open Source Consortium]].
+
* The OpenDoc Society run frequent [[ODF Plugfest]]s in association with industry groups and Public Sector organisations. The 10th Plugfest<ref>[http://plugfest.opendocumentformat.org/2014-london/ 10th Plugfest hosted by the UK Cabinet Office December 2014]</ref> was hosted by the UK [[Government Digital Service]] in conjunction with industry associations including the [[OpenForum Europe]] and [[OpenUK | OpenUK (formerly Open Source Consortium)]].
 
** An output of the 10th Plugfest was an ODF toolkit<ref>http://www.openforumeurope.org/library/ODF/odf-toolkit-folder/</ref> which includes "Open Document Format principles for Government Technology" that has the purpose of simply explaining the case for ODF directed at the "average civil servant" and includes an extract from the UK Government policy relating to Open Document Format.
 
** An output of the 10th Plugfest was an ODF toolkit<ref>http://www.openforumeurope.org/library/ODF/odf-toolkit-folder/</ref> which includes "Open Document Format principles for Government Technology" that has the purpose of simply explaining the case for ODF directed at the "average civil servant" and includes an extract from the UK Government policy relating to Open Document Format.
 
** The toolkit also includes a single page graphical image<ref>https://web.archive.org/web/20150620003502/http://www.openforumeurope.org/library/ODF/odf-toolkit-folder/OFE-COIS-ODF-infographic-release-02150325-by-sa.jpeg</ref> designed to articulate the consequences of not choosing Open Document Format. The illustration has now been translated into more than 10 languages.
 
** The toolkit also includes a single page graphical image<ref>https://web.archive.org/web/20150620003502/http://www.openforumeurope.org/library/ODF/odf-toolkit-folder/OFE-COIS-ODF-infographic-release-02150325-by-sa.jpeg</ref> designed to articulate the consequences of not choosing Open Document Format. The illustration has now been translated into more than 10 languages.

by FrescoBot at November 02, 2017 08:27 AM

HackerNews

October 31, 2017

The Document Foundation Planet

Official TDF Blog: Call for Papers Open Document Editors DevRoom at FOSDEM 2018

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

As usual, the Open Document Editors DevRoom will be jointly organized by Apache OpenOffice and LibreOffice, on Saturday, February 3 (from 10:30AM to 6:30PM, room AW1.120). The shared devroom gives every project in this area a chance to present ODF related developments and innovations.

We are now inviting proposals for talks about Open Document Editors or the ODF standard document format, on topics such as code, localization, QA, UX, extensions, tools and adoption related cases. This is a unique opportunity to show new ideas and developments to a wide technical audience. Please do keep in mind, though, that product pitches are not allowed at FOSDEM.

Length of talks should be limited to a maximum of 30 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/FOSDEM18.

While filing your proposal, please provide the title of your talk, a short abstract (one or two paragraphs), some information about yourself (name, bio and photo, but please do remember that your profile might be already stored at Pentabarf).

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 4th, 2017. Accepted speakers will be notified by Monday, December 11th, 2017. The schedule will be published by Friday, December 15, 2017.

Recording Permission

The talks in the Open Document Editors DevRoom will be audio and video recorded, and possibly streamed live too.

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”.

October 31, 2017 07:19 PM

October 27, 2017

The Document Foundation Planet

Official TDF Blog: LibreOffice contributor interview: Franklin Weng

At the recent LibreOffice Conference in Rome, we took the opportunity to meet up and talk to various contributors to the project, like Franklin Weng from Taiwan. Franklin is helping to get LibreOffice and the Open Document Format (ODF) adopted by governments and enterprises. In this interview, he talks about his strategy and experiences. (English subtitles available – click the Settings cog.)

October 27, 2017 07:29 AM

October 09, 2017

Jos van den Oever

OpenDocument Format Plugfest and test site

ODF Plugfest 2017

Tomorrow, Tuesday 10th of October, we will be having the 13th ODF Plugfest. It is being held in Rome and on-line.

October 09, 2017 12:00 AM

October 03, 2017

'Cases of diarrhoea 46% higher in non-ODF areas' - India - ReliefWeb

'Cases of diarrhoea 46% higher in non-ODF areas' - India  ReliefWeb

English News and Press Release on India about Health and Water Sanitation Hygiene; published on 03 Oct 2017 by Times of India.

October 03, 2017 07:00 AM

October 01, 2017

ODF Wikipedia Page

82.29.90.82: /* Support for OpenDocument */

Support for OpenDocument

← Previous revision Revision as of 10:17, 1 October 2017
Line 212: Line 212:
 
Several governments, companies, organizations and software products support the OpenDocument format. For example:
 
Several governments, companies, organizations and software products support the OpenDocument format. For example:
   
* The OpenDoc Society run frequent [[ODF Plugfest]]s in association with industry groups and Public Sector organisations. The 10th Plugfest<ref>[http://plugfest.opendocumentformat.org/2014-london/ 10th Plugfest hosted by the UK Cabinet Office December 2014]</ref> was hosted by the UK [[Government Digital Service]] in conjunction with industry associations including the [[OpenForum Europe]] and the [[Open Source Consortium]].
+
* The OpenDoc Society run frequent [[ODF Plugfest]]s in association with industry groups and Public Sector organisations. The 10th Plugfest<ref>[http://plugfest.opendocumentformat.org/2014-london/ 10th Plugfest hosted by the UK Cabinet Office December 2014]</ref> was hosted by the UK [[Government Digital Service]] in conjunction with industry associations including the [[OpenForum Europe]] and [[OpenUK | OpenUK (formerly Open Source Consortium]].
 
** An output of the 10th Plugfest was an ODF toolkit<ref>http://www.openforumeurope.org/library/ODF/odf-toolkit-folder/</ref> which includes "Open Document Format principles for Government Technology" that has the purpose of simply explaining the case for ODF directed at the "average civil servant" and includes an extract from the UK Government policy relating to Open Document Format.
 
** An output of the 10th Plugfest was an ODF toolkit<ref>http://www.openforumeurope.org/library/ODF/odf-toolkit-folder/</ref> which includes "Open Document Format principles for Government Technology" that has the purpose of simply explaining the case for ODF directed at the "average civil servant" and includes an extract from the UK Government policy relating to Open Document Format.
 
** The toolkit also includes a single page graphical image<ref>https://web.archive.org/web/20150620003502/http://www.openforumeurope.org/library/ODF/odf-toolkit-folder/OFE-COIS-ODF-infographic-release-02150325-by-sa.jpeg</ref> designed to articulate the consequences of not choosing Open Document Format. The illustration has now been translated into more than 10 languages.
 
** The toolkit also includes a single page graphical image<ref>https://web.archive.org/web/20150620003502/http://www.openforumeurope.org/library/ODF/odf-toolkit-folder/OFE-COIS-ODF-infographic-release-02150325-by-sa.jpeg</ref> designed to articulate the consequences of not choosing Open Document Format. The illustration has now been translated into more than 10 languages.

by 82.29.90.82 at October 01, 2017 10:17 AM

Xezbeth: Reverted edits by 121.181.198.200 (talk) to last version by 82.29.90.82

Reverted edits by 121.181.198.200 (talk) to last version by 82.29.90.82

← Previous revision Revision as of 08:06, 1 October 2017
Line 212: Line 212:
 
Several governments, companies, organizations and software products support the OpenDocument format. For example:
 
Several governments, companies, organizations and software products support the OpenDocument format. For example:
   
* The OpenDoc Society run frequent [[Plugfest]]s in association with industry groups and Public Sector organisations. The 10th Plugfest<ref>[http://plugfest.opendocumentformat.org/2014-london/ 10th Plugfest hosted by the UK Cabinet Office December 2014]</ref> was hosted by the UK [[Government Digital Service]] in conjunction with industry associations including the [[OpenForum Europe]] and the [[Open Source Consortium]].
+
* The OpenDoc Society run frequent [[ODF Plugfest]]s in association with industry groups and Public Sector organisations. The 10th Plugfest<ref>[http://plugfest.opendocumentformat.org/2014-london/ 10th Plugfest hosted by the UK Cabinet Office December 2014]</ref> was hosted by the UK [[Government Digital Service]] in conjunction with industry associations including the [[OpenForum Europe]] and the [[Open Source Consortium]].
 
** An output of the 10th Plugfest was an ODF toolkit<ref>http://www.openforumeurope.org/library/ODF/odf-toolkit-folder/</ref> which includes "Open Document Format principles for Government Technology" that has the purpose of simply explaining the case for ODF directed at the "average civil servant" and includes an extract from the UK Government policy relating to Open Document Format.
 
** An output of the 10th Plugfest was an ODF toolkit<ref>http://www.openforumeurope.org/library/ODF/odf-toolkit-folder/</ref> which includes "Open Document Format principles for Government Technology" that has the purpose of simply explaining the case for ODF directed at the "average civil servant" and includes an extract from the UK Government policy relating to Open Document Format.
 
** The toolkit also includes a single page graphical image<ref>https://web.archive.org/web/20150620003502/http://www.openforumeurope.org/library/ODF/odf-toolkit-folder/OFE-COIS-ODF-infographic-release-02150325-by-sa.jpeg</ref> designed to articulate the consequences of not choosing Open Document Format. The illustration has now been translated into more than 10 languages.
 
** The toolkit also includes a single page graphical image<ref>https://web.archive.org/web/20150620003502/http://www.openforumeurope.org/library/ODF/odf-toolkit-folder/OFE-COIS-ODF-infographic-release-02150325-by-sa.jpeg</ref> designed to articulate the consequences of not choosing Open Document Format. The illustration has now been translated into more than 10 languages.

by Xezbeth at October 01, 2017 08:06 AM

121.181.198.200: Undid revision 803230618 by 82.29.90.82 (talk)

Undid revision 803230618 by 82.29.90.82 (talk)

← Previous revision Revision as of 08:05, 1 October 2017
Line 212: Line 212:
 
Several governments, companies, organizations and software products support the OpenDocument format. For example:
 
Several governments, companies, organizations and software products support the OpenDocument format. For example:
   
* The OpenDoc Society run frequent [[ODF Plugfest]]s in association with industry groups and Public Sector organisations. The 10th Plugfest<ref>[http://plugfest.opendocumentformat.org/2014-london/ 10th Plugfest hosted by the UK Cabinet Office December 2014]</ref> was hosted by the UK [[Government Digital Service]] in conjunction with industry associations including the [[OpenForum Europe]] and the [[Open Source Consortium]].
+
* The OpenDoc Society run frequent [[Plugfest]]s in association with industry groups and Public Sector organisations. The 10th Plugfest<ref>[http://plugfest.opendocumentformat.org/2014-london/ 10th Plugfest hosted by the UK Cabinet Office December 2014]</ref> was hosted by the UK [[Government Digital Service]] in conjunction with industry associations including the [[OpenForum Europe]] and the [[Open Source Consortium]].
 
** An output of the 10th Plugfest was an ODF toolkit<ref>http://www.openforumeurope.org/library/ODF/odf-toolkit-folder/</ref> which includes "Open Document Format principles for Government Technology" that has the purpose of simply explaining the case for ODF directed at the "average civil servant" and includes an extract from the UK Government policy relating to Open Document Format.
 
** An output of the 10th Plugfest was an ODF toolkit<ref>http://www.openforumeurope.org/library/ODF/odf-toolkit-folder/</ref> which includes "Open Document Format principles for Government Technology" that has the purpose of simply explaining the case for ODF directed at the "average civil servant" and includes an extract from the UK Government policy relating to Open Document Format.
 
** The toolkit also includes a single page graphical image<ref>https://web.archive.org/web/20150620003502/http://www.openforumeurope.org/library/ODF/odf-toolkit-folder/OFE-COIS-ODF-infographic-release-02150325-by-sa.jpeg</ref> designed to articulate the consequences of not choosing Open Document Format. The illustration has now been translated into more than 10 languages.
 
** The toolkit also includes a single page graphical image<ref>https://web.archive.org/web/20150620003502/http://www.openforumeurope.org/library/ODF/odf-toolkit-folder/OFE-COIS-ODF-infographic-release-02150325-by-sa.jpeg</ref> designed to articulate the consequences of not choosing Open Document Format. The illustration has now been translated into more than 10 languages.

by 121.181.198.200 at October 01, 2017 08:05 AM

82.29.90.82: /* Response */

Response

← Previous revision Revision as of 08:05, 1 October 2017
Line 212: Line 212:
 
Several governments, companies, organizations and software products support the OpenDocument format. For example:
 
Several governments, companies, organizations and software products support the OpenDocument format. For example:
   
* The OpenDoc Society run frequent [[Plugfest]]s in association with industry groups and Public Sector organisations. The 10th Plugfest<ref>[http://plugfest.opendocumentformat.org/2014-london/ 10th Plugfest hosted by the UK Cabinet Office December 2014]</ref> was hosted by the UK [[Government Digital Service]] in conjunction with industry associations including the [[OpenForum Europe]] and the [[Open Source Consortium]].
+
* The OpenDoc Society run frequent [[ODF Plugfest]]s in association with industry groups and Public Sector organisations. The 10th Plugfest<ref>[http://plugfest.opendocumentformat.org/2014-london/ 10th Plugfest hosted by the UK Cabinet Office December 2014]</ref> was hosted by the UK [[Government Digital Service]] in conjunction with industry associations including the [[OpenForum Europe]] and the [[Open Source Consortium]].
 
** An output of the 10th Plugfest was an ODF toolkit<ref>http://www.openforumeurope.org/library/ODF/odf-toolkit-folder/</ref> which includes "Open Document Format principles for Government Technology" that has the purpose of simply explaining the case for ODF directed at the "average civil servant" and includes an extract from the UK Government policy relating to Open Document Format.
 
** An output of the 10th Plugfest was an ODF toolkit<ref>http://www.openforumeurope.org/library/ODF/odf-toolkit-folder/</ref> which includes "Open Document Format principles for Government Technology" that has the purpose of simply explaining the case for ODF directed at the "average civil servant" and includes an extract from the UK Government policy relating to Open Document Format.
 
** The toolkit also includes a single page graphical image<ref>https://web.archive.org/web/20150620003502/http://www.openforumeurope.org/library/ODF/odf-toolkit-folder/OFE-COIS-ODF-infographic-release-02150325-by-sa.jpeg</ref> designed to articulate the consequences of not choosing Open Document Format. The illustration has now been translated into more than 10 languages.
 
** The toolkit also includes a single page graphical image<ref>https://web.archive.org/web/20150620003502/http://www.openforumeurope.org/library/ODF/odf-toolkit-folder/OFE-COIS-ODF-infographic-release-02150325-by-sa.jpeg</ref> designed to articulate the consequences of not choosing Open Document Format. The illustration has now been translated into more than 10 languages.

by 82.29.90.82 at October 01, 2017 08:05 AM

September 28, 2017

The Document Foundation Planet

Official TDF Blog: LibreOffice community celebrates 7th anniversary

Results of survey amongst desktop users confirm project’s momentum

Berlin, September 28, 2017 – Today, the LibreOffice community celebrates the 7th anniversary of the leading free office suite, adopted by millions of users in every continent. Since 2010, there have been 14 major releases and dozens of minor ones, fulfilling the personal productivity needs of both individuals and enterprises, on Linux, macOS and Windows.

LibreOffice deployments are supported by certified developers and professionals (list available at: https://www.libreoffice.org/get-help/professional-support/). Many are employed by companies sitting in TDF’s Advisory Board (https://www.documentfoundation.org/governance/advisory-board/), who provide either value-added Long Term Supported versions of LibreOffice or consultancy services for development, migrations and training.

LibreOffice is available in over 100 native languages, and as such is contributing to the preservation of native cultural heritages, as in the case – for instance – of the Guarani language in South America, and the Venitian language in Northern Italy. All localizations are managed by local volunteers.

LibreOffice is also a reference implementation of the Open Document Format (ODF) ISO standard for office documents, which today represents the only choice in the market for true interoperability.

Results of Ubuntu 18.04 LTS Default Desktop Applications Survey

LibreOffice’s leadership amongst office suites has been recently confirmed by the survey of Ubuntu users for desktop productivity software, with 85.52% of the votes. The closest competitors were Google Docs with 4.29%, WPS Office with 3.22% and Apache OpenOffice with 1.96%.

The Ubuntu 18.04 LTS Default Desktop Applications Survey produced over 15,000 responses in total, with over 6,400 for the office suite category. LibreOffice received the largest margin of preference of the entire survey. Results are available here: http://blog.dustinkirkland.com/2017/09/results-of-ubuntu-desktop-applications.html (video and slides).

Download LibreOffice

Current versions of LibreOffice are available for download from the following link: https://www.libreoffice.org/download/.

LibreOffice users, free software advocates and community members can support The Document Foundation with a donation at https://www.libreoffice.org/donate/. Donations help TDF to maintain its infrastructure, share knowledge, and organise events such as the LibreOffice Conference, with the next one taking place in October in Rome (https://conference.libreoffice.org).

September 28, 2017 09:05 AM

September 20, 2017

The Document Foundation Planet

Official TDF Blog: Document Liberation Project: New releases


LibreOffice’s native file format is the fully standardised OpenDocument Format. This is ideal for long-term storage of data, but many of us have to work with other file formats as well, including those generated by proprietary software. The Document Liberation Project (DLP) develops libraries to help us access these files, and there have been various updates in the last two weeks, so let’s see what’s new:

  • libfreehand 0.1.2 – This is a library for importing Aldus/Macromedia/Adobe FreeHand documents. In this release, the library can import more elements, such as text on paths, text effects, stroke patterns, arrows and paragraph attributes.
  • libzmf 0.0.2 and libcdr 0.1.4 – libzmf is a library for importing Zoner drawing and bitmap files, currently supporting Callisto/Draw 4-5 and Bitmap, while libcdr is a library that parses the file format of CorelDRAW documents of all versions. Both have been made more secure thanks to OSS-Fuzz, which we talked about recently, and there have been build fixes as well.
  • libwpg 0.3.2 and libwpd 0.10.2 – The former is for importing WordPerfect Graphics images, and has performance improvements when reading image data from WPG2 files, while the latter has had build system improvements and also fixes from the aforementioned OSS-Fuzz.

These improvements will be included in future major releases of LibreOffice, and indeed other open source programs that use Document Liberation Project libraries.

Meanwhile, DLP developer Laurent Alonso sent us this great before-and-after picture, showing recent improvements to the import of Lotus 123 spreadsheets. At the top you can see a Lotus 123 file (that contains lots of formatting) being displayed in LibreOffice 5.3 – but the formatting is missing. Thanks to improvements in DLP libraries, though, LibreOffice 5.4 can read and display the spreadsheet much more accurately, as you can see underneath (click for bigger):

The DLP community appreciates all contributions, and even if you’re not a coder, there are many ways to help – such as documenting file formats, or preparing sample documents. To learn more about DLP, check out our short video:

September 20, 2017 01:35 PM

September 17, 2017

ODF Wikipedia Page

Jon Kolbert: Updating PCWorld article link

Updating PCWorld article link

← Previous revision Revision as of 17:24, 17 September 2017
Line 186: Line 186:
 
* [[WordPad]] 6.1 (Windows 7) partial support.
 
* [[WordPad]] 6.1 (Windows 7) partial support.
 
* [[Zoho Office Suite]]<ref name="register" />
 
* [[Zoho Office Suite]]<ref name="register" />
Various organizations have announced development of conversion software (including ''plugins'' and ''filters'') to support OpenDocument on [[Microsoft]]'s products.<ref>{{cite web | url=http://www.groklaw.net/article.php?story=20060504015438308 | title=OpenDocument Foundation to MA: We Have a Plugin | date=4 May 2006 | accessdate=23 August 2006 | publisher=Groklaw}}</ref><ref>{{cite news | url=http://www.zdnet.com.au/news/software/soa/Microsoft_Office_to_get_a_dose_of_OpenDocument/0,130061733,139255766,00.htm | title=Microsoft Office to get a dose of OpenDocument | date=5 May 2006 | accessdate=6 December 2006|publisher=CNet}}</ref> {{asof|July 2007}}, there are nine packages of conversion software.<!--Commented out invalid reference<ref name="odf20070727"/>--> Microsoft first released support for the OpenDocument Format in Office 2007 SP2.<ref>{{cite web | title=Office 2007 SP2 Supports ODF | url=http://www.pcworld.com/businesscenter/article/164015/office_2007_sp2_supports_odf.html | date=28 April 2009 | publisher=PC World}}</ref> However, the implementation faced [[OpenDocument software#Microsoft Office 2007 SP2 support controversy|substantial criticism]] and the [[ODF Alliance]] and others claimed that the third party plugins provided better support.<ref name="sp2-fact-sheet">{{cite web|url=http://www.odfalliance.org/resources/fact-sheet-Microsoft-ODF-support.pdf |title=Fact-sheet Microsoft ODF support |accessdate=24 May 2009 |quote=''MS Excel 2007 will process ODF spreadsheet documents when loaded via the Sun Plug-In 3.0 for MS Office or the SourceForge “OpenXML/ODF Translator Add-in for Office,” but will fail when using the “built-in” support provided by Office 2007 SP2.'' |publisher=odfalliance |deadurl=yes |archiveurl=https://web.archive.org/web/20090611181719/http://www.odfalliance.org/resources/fact-sheet-Microsoft-ODF-support.pdf |archivedate=11 June 2009 }}</ref> Microsoft Office 2010 can open and save OpenDocument Format documents natively, although not all features are supported.<ref>{{cite web|url=http://office.microsoft.com/en-us/starter-help/differences-between-the-opendocument-text-odt-format-and-the-word-docx-format-HA010355788.aspx|title=Differences between the OpenDocument Text (.odt) format and the Word (.docx) format|work=office.microsoft.com}}</ref>
+
Various organizations have announced development of conversion software (including ''plugins'' and ''filters'') to support OpenDocument on [[Microsoft]]'s products.<ref>{{cite web | url=http://www.groklaw.net/article.php?story=20060504015438308 | title=OpenDocument Foundation to MA: We Have a Plugin | date=4 May 2006 | accessdate=23 August 2006 | publisher=Groklaw}}</ref><ref>{{cite news | url=http://www.zdnet.com.au/news/software/soa/Microsoft_Office_to_get_a_dose_of_OpenDocument/0,130061733,139255766,00.htm | title=Microsoft Office to get a dose of OpenDocument | date=5 May 2006 | accessdate=6 December 2006|publisher=CNet}}</ref> {{asof|July 2007}}, there are nine packages of conversion software.<!--Commented out invalid reference<ref name="odf20070727"/>--> Microsoft first released support for the OpenDocument Format in Office 2007 SP2.<ref>{{cite web | title=Office 2007 SP2 Supports ODF | url=https://www.pcworld.com/article/164015/office_2007_sp2_supports_odf.html | date=28 April 2009 | publisher=PC World}}</ref> However, the implementation faced [[OpenDocument software#Microsoft Office 2007 SP2 support controversy|substantial criticism]] and the [[ODF Alliance]] and others claimed that the third party plugins provided better support.<ref name="sp2-fact-sheet">{{cite web|url=http://www.odfalliance.org/resources/fact-sheet-Microsoft-ODF-support.pdf |title=Fact-sheet Microsoft ODF support |accessdate=24 May 2009 |quote=''MS Excel 2007 will process ODF spreadsheet documents when loaded via the Sun Plug-In 3.0 for MS Office or the SourceForge “OpenXML/ODF Translator Add-in for Office,” but will fail when using the “built-in” support provided by Office 2007 SP2.'' |publisher=odfalliance |deadurl=yes |archiveurl=https://web.archive.org/web/20090611181719/http://www.odfalliance.org/resources/fact-sheet-Microsoft-ODF-support.pdf |archivedate=11 June 2009 }}</ref> Microsoft Office 2010 can open and save OpenDocument Format documents natively, although not all features are supported.<ref>{{cite web|url=http://office.microsoft.com/en-us/starter-help/differences-between-the-opendocument-text-odt-format-and-the-word-docx-format-HA010355788.aspx|title=Differences between the OpenDocument Text (.odt) format and the Word (.docx) format|work=office.microsoft.com}}</ref>
   
 
Starting with [[Mac OS X 10.5]], the [[TextEdit]] application and [[Quick Look]] preview feature support the OpenDocument Text format.
 
Starting with [[Mac OS X 10.5]], the [[TextEdit]] application and [[Quick Look]] preview feature support the OpenDocument Text format.

by Jon Kolbert at September 17, 2017 05:24 PM

September 07, 2017

ODF Wikipedia Page

KolbertBot: Bot: HTTP→HTTPS

Bot: HTTP→HTTPS

← Previous revision Revision as of 04:47, 7 September 2017
Line 132: Line 132:
 
The OpenDocument standard was developed by a Technical Committee (TC) under the OASIS ([[Organization for the Advancement of Structured Information Standards]]) industry consortium. The ODF-TC has members from a diverse set of companies and individuals. Active TC members have voting rights. Members associated with Sun and IBM have sometimes had a large voting influence.<ref>{{cite web | url=http://www.oasis-open.org/committees/membership.php?wg_abbrev=office | title=OpenDocument TC's {{Sic|hide=y|publicly|-}}visible membership roster | accessdate=3 November 2007}}</ref> The standardization process involved the developers of many office suites or related document systems. The first official ODF-TC meeting to discuss the standard was 16 December 2002; OASIS approved OpenDocument as an OASIS standard on 1 May 2005. OASIS submitted the ODF specification to [[ISO/IEC JTC1|ISO/IEC Joint Technical Committee 1]] (JTC 1) on 16 November 2005, under Publicly Available Specification (PAS) rules. ISO/IEC standardization for an open document standard including text, spreadsheet and presentation was proposed for the first time in [[DKUUG]] 28 August 2001.<ref>{{cite web | url=http://www.open-std.org/keld/iso26300-odf/dkuug-std-010828.pdf | title=Meeting agenda for DKUUG STD 2001-08-28 – item 5.6 | accessdate=13 March 2015}}</ref>
 
The OpenDocument standard was developed by a Technical Committee (TC) under the OASIS ([[Organization for the Advancement of Structured Information Standards]]) industry consortium. The ODF-TC has members from a diverse set of companies and individuals. Active TC members have voting rights. Members associated with Sun and IBM have sometimes had a large voting influence.<ref>{{cite web | url=http://www.oasis-open.org/committees/membership.php?wg_abbrev=office | title=OpenDocument TC's {{Sic|hide=y|publicly|-}}visible membership roster | accessdate=3 November 2007}}</ref> The standardization process involved the developers of many office suites or related document systems. The first official ODF-TC meeting to discuss the standard was 16 December 2002; OASIS approved OpenDocument as an OASIS standard on 1 May 2005. OASIS submitted the ODF specification to [[ISO/IEC JTC1|ISO/IEC Joint Technical Committee 1]] (JTC 1) on 16 November 2005, under Publicly Available Specification (PAS) rules. ISO/IEC standardization for an open document standard including text, spreadsheet and presentation was proposed for the first time in [[DKUUG]] 28 August 2001.<ref>{{cite web | url=http://www.open-std.org/keld/iso26300-odf/dkuug-std-010828.pdf | title=Meeting agenda for DKUUG STD 2001-08-28 – item 5.6 | accessdate=13 March 2015}}</ref>
   
After a six-month review period, on 3 May 2006, OpenDocument unanimously passed its six-month DIS (Draft International Standard) ballot in [[JTC 1]] ([[ISO/IEC JTC1/SC34]]), with broad participation,<ref>{{cite web | url=http://www.jtc1sc34.org/repository/0728revc.htm | title=<!--what the title actually says: "ISO/IEC JTC 1/SC 34 Information Technology -->Document Description and Processing Languages-->Summary of Voting on DIS ISO/IEC 26300 – Open Document Format for Office Applications (OpenDocument) v1.0 | date=13 June 2006 | accessdate=24 August 2006 | author=ISO/IEC SC34 Secretariat | work=ISO/IEC JTC 1/SC 34 Document Repository | archiveurl=http://web.archive.org/web/20061001180333/http://www.jtc1sc34.org/repository/0728revc.htm | archivedate = 1 October 2006}}</ref> after which the OpenDocument specification was "approved for release as an ISO and IEC International Standard" under the name ISO/IEC 26300:2006.<ref>{{cite web | url=http://www.iso.org/iso/en/commcentre/pressreleases/2006/Ref1004.html | title=ISO and IEC approve OpenDocument OASIS standard for data interoperability of office applications | date=8 May 2006 | accessdate=24 August 2006 | work=ISO Press Releases | publisher=[[International Organization for Standardization|ISO]]}}</ref>
+
After a six-month review period, on 3 May 2006, OpenDocument unanimously passed its six-month DIS (Draft International Standard) ballot in [[JTC 1]] ([[ISO/IEC JTC1/SC34]]), with broad participation,<ref>{{cite web | url=http://www.jtc1sc34.org/repository/0728revc.htm | title=<!--what the title actually says: "ISO/IEC JTC 1/SC 34 Information Technology -->Document Description and Processing Languages-->Summary of Voting on DIS ISO/IEC 26300 – Open Document Format for Office Applications (OpenDocument) v1.0 | date=13 June 2006 | accessdate=24 August 2006 | author=ISO/IEC SC34 Secretariat | work=ISO/IEC JTC 1/SC 34 Document Repository | archiveurl=https://web.archive.org/web/20061001180333/http://www.jtc1sc34.org/repository/0728revc.htm | archivedate = 1 October 2006}}</ref> after which the OpenDocument specification was "approved for release as an ISO and IEC International Standard" under the name ISO/IEC 26300:2006.<ref>{{cite web | url=http://www.iso.org/iso/en/commcentre/pressreleases/2006/Ref1004.html | title=ISO and IEC approve OpenDocument OASIS standard for data interoperability of office applications | date=8 May 2006 | accessdate=24 August 2006 | work=ISO Press Releases | publisher=[[International Organization for Standardization|ISO]]}}</ref>
   
 
After responding to all written ballot comments, and a 30-day default ballot, the OpenDocument [[international standard]] went to publication in ISO, officially published 30 November 2006.
 
After responding to all written ballot comments, and a 30-day default ballot, the OpenDocument [[international standard]] went to publication in ISO, officially published 30 November 2006.
Line 214: Line 214:
 
* The OpenDoc Society run frequent [[Plugfest]]s in association with industry groups and Public Sector organisations. The 10th Plugfest<ref>[http://plugfest.opendocumentformat.org/2014-london/ 10th Plugfest hosted by the UK Cabinet Office December 2014]</ref> was hosted by the UK [[Government Digital Service]] in conjunction with industry associations including the [[OpenForum Europe]] and the [[Open Source Consortium]].
 
* The OpenDoc Society run frequent [[Plugfest]]s in association with industry groups and Public Sector organisations. The 10th Plugfest<ref>[http://plugfest.opendocumentformat.org/2014-london/ 10th Plugfest hosted by the UK Cabinet Office December 2014]</ref> was hosted by the UK [[Government Digital Service]] in conjunction with industry associations including the [[OpenForum Europe]] and the [[Open Source Consortium]].
 
** An output of the 10th Plugfest was an ODF toolkit<ref>http://www.openforumeurope.org/library/ODF/odf-toolkit-folder/</ref> which includes "Open Document Format principles for Government Technology" that has the purpose of simply explaining the case for ODF directed at the "average civil servant" and includes an extract from the UK Government policy relating to Open Document Format.
 
** An output of the 10th Plugfest was an ODF toolkit<ref>http://www.openforumeurope.org/library/ODF/odf-toolkit-folder/</ref> which includes "Open Document Format principles for Government Technology" that has the purpose of simply explaining the case for ODF directed at the "average civil servant" and includes an extract from the UK Government policy relating to Open Document Format.
** The toolkit also includes a single page graphical image<ref>http://web.archive.org/web/20150620003502/http://www.openforumeurope.org/library/ODF/odf-toolkit-folder/OFE-COIS-ODF-infographic-release-02150325-by-sa.jpeg</ref> designed to articulate the consequences of not choosing Open Document Format. The illustration has now been translated into more than 10 languages.
+
** The toolkit also includes a single page graphical image<ref>https://web.archive.org/web/20150620003502/http://www.openforumeurope.org/library/ODF/odf-toolkit-folder/OFE-COIS-ODF-infographic-release-02150325-by-sa.jpeg</ref> designed to articulate the consequences of not choosing Open Document Format. The illustration has now been translated into more than 10 languages.
 
* 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 }}</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 }}</ref>
Line 223: Line 223:
 
<!-- * The [http://www.oidi.org OIDI.org] (Open Interoperative Document Initiative) is committed to encouraging efforts by governments at all levels, around the globe, to implement changes necessary to ensure public documents are open and interoperable and thus available to all citizens/residents without the need for specific vendor software. -->
 
<!-- * The [http://www.oidi.org OIDI.org] (Open Interoperative Document Initiative) is committed to encouraging efforts by governments at all levels, around the globe, to implement changes necessary to ensure public documents are open and interoperable and thus available to all citizens/residents without the need for specific vendor software. -->
 
* The UK government has adopted ODF as the standard for all documents in the UK civil service<ref>{{cite web | url=https://www.gov.uk/government/news/open-document-formats-selected-to-meet-user-needs|title=Open document formats selected to meet user needs}}</ref>
 
* The UK government has adopted ODF as the standard for all documents in the UK civil service<ref>{{cite web | url=https://www.gov.uk/government/news/open-document-formats-selected-to-meet-user-needs|title=Open document formats selected to meet user needs}}</ref>
* The [[Wikimedia Foundation]] supports ODF export from [[MediaWiki]], which powers [[Wikipedia]] and a number of other Internet [[wiki]]-based sites.<ref>{{cite web | url= http://wikimediafoundation.org/wiki/Wikis_Go_Printable | title= Wikis Go Printable | work= [[Wikimedia Foundation]] | date= 13 December 2007 | accessdate= 31 December 2007}}</ref>
+
* The [[Wikimedia Foundation]] supports ODF export from [[MediaWiki]], which powers [[Wikipedia]] and a number of other Internet [[wiki]]-based sites.<ref>{{cite web | url= https://wikimediafoundation.org/wiki/Wikis_Go_Printable | title= Wikis Go Printable | work= [[Wikimedia Foundation]] | date= 13 December 2007 | accessdate= 31 December 2007}}</ref>
 
* The default text processing applications in Windows 10 ([[WordPad]]) and Mac OS 10.9 ([[TextEdit]]) support OpenDocument Text.
 
* The default text processing applications in Windows 10 ([[WordPad]]) and Mac OS 10.9 ([[TextEdit]]) support OpenDocument Text.
   
Line 229: Line 229:
   
 
*Different applications using ODF as a standard document format have different methods of providing macro/scripting capabilities. There is no [[macro language]] specified in ODF. Users and developers differ on whether inclusion of a standard scripting language would be desirable.<ref>{{cite web | url=http://www.linux.com/archive/articles/47935 | archiveurl=https://web.archive.org/web/20110521183559/http://www.linux.com/archive/articles/47935 | archivedate=21 May 2011 | title=Macros an obstacle to office suite compatibility | author=Marco Fioretti | accessdate=11 May 2008}}</ref>
 
*Different applications using ODF as a standard document format have different methods of providing macro/scripting capabilities. There is no [[macro language]] specified in ODF. Users and developers differ on whether inclusion of a standard scripting language would be desirable.<ref>{{cite web | url=http://www.linux.com/archive/articles/47935 | archiveurl=https://web.archive.org/web/20110521183559/http://www.linux.com/archive/articles/47935 | archivedate=21 May 2011 | title=Macros an obstacle to office suite compatibility | author=Marco Fioretti | accessdate=11 May 2008}}</ref>
* The ODF specification for tracked changes is limited and does not fully specify all cases, resulting in implementation-specific behaviors.<ref>{{cite web | url=http://blogs.msdn.com/dmahugh/archive/2009/05/13/tracked-changes.aspx | title=Tracked Changes | author=Doug Mahugh (Microsoft) | date=13 May 2009}}</ref> In addition, OpenDocument does not support change tracking in elements like tables or [[MathML]].<ref name="doyourmath">{{cite web | url=http://web.archive.org/web/20160326225935/http://idippedut.dk/post/Do-your-math-OOXML-and-OMML | title=Do your math - OOXML and OMML (Updated 2008-02-12) | author=Jesper Lund Stocholm (Danish ISO/IEC representative) | date=12 December 2008}}</ref>
+
* The ODF specification for tracked changes is limited and does not fully specify all cases, resulting in implementation-specific behaviors.<ref>{{cite web | url=http://blogs.msdn.com/dmahugh/archive/2009/05/13/tracked-changes.aspx | title=Tracked Changes | author=Doug Mahugh (Microsoft) | date=13 May 2009}}</ref> In addition, OpenDocument does not support change tracking in elements like tables or [[MathML]].<ref name="doyourmath">{{cite web | url=https://web.archive.org/web/20160326225935/http://idippedut.dk/post/Do-your-math-OOXML-and-OMML | title=Do your math - OOXML and OMML (Updated 2008-02-12) | author=Jesper Lund Stocholm (Danish ISO/IEC representative) | date=12 December 2008}}</ref>
 
* It is not permitted to use generic ODF formatting style elements (like font information) for the MathML elements.<ref name="doyourmath"/>
 
* It is not permitted to use generic ODF formatting style elements (like font information) for the MathML elements.<ref name="doyourmath"/>
   

by KolbertBot at September 07, 2017 04:47 AM

August 28, 2017

www.opendocsociety.org

13th ODF Plugfest in Rome

The thirteenth ODF plugfest will be hosted by the City of Rome, with support from Logius and organised by OpenDoc Society.

Logo for the 13th plugfest - a mashup of the logo of the plugfest with the Creation of Adam

For more information, please visit: http://odfplugfest.org

August 28, 2017 02:49 PM

August 25, 2017

The Document Foundation Planet

Cor Nouws: LibreOffice at Tilburg University Orientation Program

At the beginning of the new year, the Tilburg University organizes the Tilburg Orientation Program (TOP) presenting all kind of interesting and cool stuff for the new students. So at August 22, a nice and sunny day, there was a huge event in a park with lots of plays and booths and music and beer. And: three people from the Dutch LibreOffice team were there!
We had a nice booth and prepared both flyers and small cards. Especially the cards were handsome to reach out to people: "want a free card for free software" is a short and appealing message. Thus we handed out a six to seven hundred of the cards. Of course we had good talks too: dozens of individuals and groups wanted more information. And there are people that know and use open source. Or were just in need for a good office-suite for their new bought Mac book ;)
It's always interesting to see how people react. For example if you tell that Microsoft doesn't really loves students, when they offer software very cheap, but that they just want to make you very well used to it, so that they can charge high prices when you've finished your study.. And compare that to LibreOffice: free always, at school, home, office. And of course free choice for donations or paid support if desired! Was fun to hear some of the students call the way Microsoft does this "the drugs dealer method" ;) Anyways: Pieter Kristensen, Freek de Kruijf and me had great fun with the people and the music and showing LibreOffice. To be continued next years, as far as I'm concerned.. :) Not the least since universities are an excellent place to support the importance of ODF as sustainable and durable document standard.

by Cor & OfficeBuzz (noreply@blogger.com) at August 25, 2017 03:25 PM

August 10, 2017

ODF Wikipedia Page

Jon Kolbert: updated reference link from using http to https

updated reference link from using http to https

← Previous revision Revision as of 13:25, 10 August 2017
Line 140: Line 140:
 
* The [[Organization for the Advancement of Structured Information Standards|OASIS]] Committee Specification [http://www.oasis-open.org/committees/download.php/19274/OpenDocument-v1.0ed2-cs1.pdf '''OpenDocument 1.0''' (second edition)] corresponds to the published ISO/IEC 26300:2006 standard. The content of ISO/IEC 26300 and OASIS OpenDocument v1.0 2nd ed. is identical.<ref name="odf10">{{citation |url=http://standards.iso.org/ittf/PubliclyAvailableStandards/c043485_ISO_IEC_26300_2006(E).zip |title=ISO/IEC 26300:2006 |format=ZIP, PDF |publisher=ISO |accessdate=22 November 2009}}</ref> It includes the editorial changes made to address JTC1 ballot comments. It is available in ODF, HTML and PDF formats.
 
* The [[Organization for the Advancement of Structured Information Standards|OASIS]] Committee Specification [http://www.oasis-open.org/committees/download.php/19274/OpenDocument-v1.0ed2-cs1.pdf '''OpenDocument 1.0''' (second edition)] corresponds to the published ISO/IEC 26300:2006 standard. The content of ISO/IEC 26300 and OASIS OpenDocument v1.0 2nd ed. is identical.<ref name="odf10">{{citation |url=http://standards.iso.org/ittf/PubliclyAvailableStandards/c043485_ISO_IEC_26300_2006(E).zip |title=ISO/IEC 26300:2006 |format=ZIP, PDF |publisher=ISO |accessdate=22 November 2009}}</ref> It includes the editorial changes made to address JTC1 ballot comments. It is available in ODF, HTML and PDF formats.
 
* '''[http://docs.oasis-open.org/office/v1.1/OS/OpenDocument-v1.1.pdf OpenDocument 1.1]''' includes additional features to address accessibility concerns.<ref>{{cite web | url=http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office#odf11 | title=OpenDocument 1.1 Specifications | year=2006 | accessdate=31 October 2006 | publisher=[[OASIS (organization)|OASIS]]}}</ref> It was approved as an OASIS Standard on 2007-02-01 following a call for vote issued on 2007-01-16.<ref>{{cite web | title=Approval of OpenDocument v1.1 as OASIS Standard | url=http://lists.oasis-open.org/archives/office/200702/msg00003.html | accessdate=6 February 2007 | publisher=[[OASIS (organization)|OASIS]]}}</ref> The public announcement was made on 2007-02-13.<ref>{{cite web | title=Members Approve OpenDocument Version 1.1 as OASIS Standard | url=http://www.oasis-open.org/news/oasis-news-2007-02-14.php | accessdate=15 February 2007 | publisher=[[OASIS (organization)|OASIS]]}}</ref> This version was not initially submitted to ISO/IEC, because it is considered to be a minor update to ODF 1.0 only, and OASIS were working already on ODF 1.2 at the time ODF 1.1 was approved.<ref>{{cite web|url=http://www.zdnet.co.uk/talkback/0,1000001161,39409700-39001068c-20093634o,00.htm|title=OOXML expert: ODF standard is broken|author=Peter Judge|publisher=ZDNet|date=2 May 2008|accessdate=10 September 2012}}</ref> However it was later submitted to ISO/IEC (as of March 2011, it was in "enquiry stage" as Draft Amendment 1{{snd}} ISO/IEC 26300:2006/DAM 1) and published in March 2012 as "ISO/IEC 26300:2006/Amd 1:2012 – Open Document Format for Office Applications (OpenDocument) v1.1".<ref name="iso.org"/><ref name="http"/>
 
* '''[http://docs.oasis-open.org/office/v1.1/OS/OpenDocument-v1.1.pdf OpenDocument 1.1]''' includes additional features to address accessibility concerns.<ref>{{cite web | url=http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office#odf11 | title=OpenDocument 1.1 Specifications | year=2006 | accessdate=31 October 2006 | publisher=[[OASIS (organization)|OASIS]]}}</ref> It was approved as an OASIS Standard on 2007-02-01 following a call for vote issued on 2007-01-16.<ref>{{cite web | title=Approval of OpenDocument v1.1 as OASIS Standard | url=http://lists.oasis-open.org/archives/office/200702/msg00003.html | accessdate=6 February 2007 | publisher=[[OASIS (organization)|OASIS]]}}</ref> The public announcement was made on 2007-02-13.<ref>{{cite web | title=Members Approve OpenDocument Version 1.1 as OASIS Standard | url=http://www.oasis-open.org/news/oasis-news-2007-02-14.php | accessdate=15 February 2007 | publisher=[[OASIS (organization)|OASIS]]}}</ref> This version was not initially submitted to ISO/IEC, because it is considered to be a minor update to ODF 1.0 only, and OASIS were working already on ODF 1.2 at the time ODF 1.1 was approved.<ref>{{cite web|url=http://www.zdnet.co.uk/talkback/0,1000001161,39409700-39001068c-20093634o,00.htm|title=OOXML expert: ODF standard is broken|author=Peter Judge|publisher=ZDNet|date=2 May 2008|accessdate=10 September 2012}}</ref> However it was later submitted to ISO/IEC (as of March 2011, it was in "enquiry stage" as Draft Amendment 1{{snd}} ISO/IEC 26300:2006/DAM 1) and published in March 2012 as "ISO/IEC 26300:2006/Amd 1:2012 – Open Document Format for Office Applications (OpenDocument) v1.1".<ref name="iso.org"/><ref name="http"/>
* '''[http://docs.oasis-open.org/office/v1.2/OpenDocument-v1.2.pdf OpenDocument 1.2]''' includes additional accessibility features, [[Resource Description Framework|RDF]]-based metadata,<ref name="register">{{cite web|accessdate=18 April 2012|publisher=The Register|url=http://www.theregister.co.uk/2011/09/12/libreoffice_extensions_and_templates_store_open/|date=3 October 2011|title=Open Document Format updated to fix spreadsheets|first=Gavin|last=Clarke}}</ref> a spreadsheet formula specification based on [[OpenFormula]],<ref name="register" /> support for [[digital signature]]s and some features suggested by the public. It consists of three parts: Part 1: OpenDocument Schema, Part 2: Recalculated Formula (OpenFormula) Format and Part 3: Packages. Version 1.2 of the specification was approved as an OASIS Standard on 29 September 2011.<ref name="odf12">{{citation |url=http://www.oasis-open.org/news/pr/odf-1-2-approval |title=Members Approve OpenDocument Format (ODF) Version 1.2 as OASIS Standard |date=5 October 2011 |accessdate=12 April 2012}}</ref> It was submitted to the relevant ISO committee under the Publicly Available Specification (PAS) procedure in March 2014.<ref>{{cite web | url=http://isotc.iso.org/livelink/livelink?func=ll&objId=16678620&objAction=Open | format=PDF | title=Minutes of ISO/IEC JTC 1/SC 34/WG 6 teleconference meeting, 2014-04-16 | date=2014-04-24 | accessdate=2014-10-13}}</ref> As of October 2014, it has been unanimously approved as a Draft International Standard, some comments have been raised in process that need to be addressed before OpenDocument 1.2 can proceed to become an International Standard.<ref>{{cite web | url=http://isotc.iso.org/livelink/livelink?func=ll&objId=16810106&objAction=Open | format=PDF | title=ISO/IEC JTC 1/SC 34/WG 6 N 103 Minutes of teleconference meeting of ISO/IEC JTC 1/SC 34/WG 6 2014-09-24, 23:00-00:00 UTC | date=2014-09-25 | accessdate=2014-10-13}}</ref> OpenDocument 1.2 was published as ISO/IEC standard on 17 June 2015.<ref name="odf12-part1">{{cite web | url=http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=66363 | title=ISO/IEC 26300-1:2015 – Information technology – Open Document Format for Office Applications (OpenDocument) v1.2 – Part 1: OpenDocument Schema | date=2015-05-13 | accessdate=2015-06-02}}</ref><ref name="odf12-part2">{{cite web | url=http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=66375 | title=ISO/IEC 26300-2:2015 – Information technology – Open Document Format for Office Applications (OpenDocument) v1.2 – Part 2: Recalculated Formula (OpenFormula) Format | date=2015-05-13 |accessdate=16 February 2016}}</ref><ref name="odf12-part3">{{cite web | url=http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=66376 | title=ISO/IEC 26300-3:2015 – Information technology – Open Document Format for Office Applications (OpenDocument) v1.2 – Part 3: Packages | date=2015-05-13 | accessdate=2015-06-02}}</ref>
+
* '''[http://docs.oasis-open.org/office/v1.2/OpenDocument-v1.2.pdf OpenDocument 1.2]''' includes additional accessibility features, [[Resource Description Framework|RDF]]-based metadata,<ref name="register">{{cite web|accessdate=18 April 2012|publisher=The Register|url=https://www.theregister.co.uk/2011/09/12/libreoffice_extensions_and_templates_store_open/|date=3 October 2011|title=Open Document Format updated to fix spreadsheets|first=Gavin|last=Clarke}}</ref> a spreadsheet formula specification based on [[OpenFormula]],<ref name="register" /> support for [[digital signature]]s and some features suggested by the public. It consists of three parts: Part 1: OpenDocument Schema, Part 2: Recalculated Formula (OpenFormula) Format and Part 3: Packages. Version 1.2 of the specification was approved as an OASIS Standard on 29 September 2011.<ref name="odf12">{{citation |url=http://www.oasis-open.org/news/pr/odf-1-2-approval |title=Members Approve OpenDocument Format (ODF) Version 1.2 as OASIS Standard |date=5 October 2011 |accessdate=12 April 2012}}</ref> It was submitted to the relevant ISO committee under the Publicly Available Specification (PAS) procedure in March 2014.<ref>{{cite web | url=http://isotc.iso.org/livelink/livelink?func=ll&objId=16678620&objAction=Open | format=PDF | title=Minutes of ISO/IEC JTC 1/SC 34/WG 6 teleconference meeting, 2014-04-16 | date=2014-04-24 | accessdate=2014-10-13}}</ref> As of October 2014, it has been unanimously approved as a Draft International Standard, some comments have been raised in process that need to be addressed before OpenDocument 1.2 can proceed to become an International Standard.<ref>{{cite web | url=http://isotc.iso.org/livelink/livelink?func=ll&objId=16810106&objAction=Open | format=PDF | title=ISO/IEC JTC 1/SC 34/WG 6 N 103 Minutes of teleconference meeting of ISO/IEC JTC 1/SC 34/WG 6 2014-09-24, 23:00-00:00 UTC | date=2014-09-25 | accessdate=2014-10-13}}</ref> OpenDocument 1.2 was published as ISO/IEC standard on 17 June 2015.<ref name="odf12-part1">{{cite web | url=http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=66363 | title=ISO/IEC 26300-1:2015 – Information technology – Open Document Format for Office Applications (OpenDocument) v1.2 – Part 1: OpenDocument Schema | date=2015-05-13 | accessdate=2015-06-02}}</ref><ref name="odf12-part2">{{cite web | url=http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=66375 | title=ISO/IEC 26300-2:2015 – Information technology – Open Document Format for Office Applications (OpenDocument) v1.2 – Part 2: Recalculated Formula (OpenFormula) Format | date=2015-05-13 |accessdate=16 February 2016}}</ref><ref name="odf12-part3">{{cite web | url=http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=66376 | title=ISO/IEC 26300-3:2015 – Information technology – Open Document Format for Office Applications (OpenDocument) v1.2 – Part 3: Packages | date=2015-05-13 | accessdate=2015-06-02}}</ref>
   
 
===Future===
 
===Future===

by Jon Kolbert at August 10, 2017 01:25 PM

August 09, 2017

EC Joinup

Italy’s Trento province to boost open source in schools

The autonomous province of Trento (Italy) is revitalising its promotion of the use of free and open source software in education. In the coming months, the province will provide schools with training on free software and open standards.

In July, the province’s Institute for Educational Research (Istituto provinciale per la ricerca e la sperimentazione educativa, IPRASE) teamed up with LibreItalia, an organisation advocating the use of free software and open standards, in particular the use of the LibreOffice suite of office productivity tools.

read more

by Gijs Hillenius at August 09, 2017 09:18 AM