The research study on Global Wall Mount Optical Distribution Frame (ODF) Market report study includes significant data and also forecasts of the global market ...
The research study on Global Rack Mount Optical Distribution Frame (ODF) Market report study includes significant data and also forecasts of the global market ...
560 bugs have been reported by 347 people.
Top 10 Reporters
570 bugs have been triaged by 77 people.
Top 10 Triagers
208 bugs have been fixed by 49 people.
Top 10 Fixers
List of critical bugs fixed
97 bugs have been verified by 17 people.
Top 10 Verifiers
915 bugs have been categorized with a metabug by 35 people.
Top 10 Categorizers
93 bugs have been set as regressions by 18 people.
Top 10
76 bugs have been bisected by 10 people.
Top 10 Bisecters
Check the current list of unconfirmed bugs here
Check the current list of open regressions here
Check the current list of open bibisectrequests here
Check the current list of highest priority bugs here
Check the current list of high priority bugs here
Thank you all for making Libreoffice rock!
Join us and help to keep LibreOffice super reliable!
Check the Get Involved page out now!‌
The post QA Report: December 2018 appeared first on LibreOffice QA Blog.
How much do you know about LibreOffice – the software, the community and its history? We’ve made a little quiz for you to try out, so check out the questions below, and you’ll find the answers at the bottom. Good luck :-)
1 – LibreOffice is a successor to OpenOffice.org, which was based on the proprietary suite StarOffice. Which company was behind StarOffice?
A: Star Corp
B: Solar Sys
C: Star Division
2 – In which year was The Document Foundation (TDF), the non-profit entity behind LibreOffice, legally established?
A: 2009
B: 2012
C: 2014
3 – Who is the current chairperson of TDF?
A: Marina Latini
B: Michael Meeks
C: Thorsten Behrens
4 – LibreOffice includes a graphics editing tool – what is it called?
A: Create
B: Draw
C: Graphic
5 – If you don’t like the default icon set in LibreOffice, how can you change it?
A: Under the Format menu
B: Via Tools > Options > View
C: Using an extension
6 – What’s the standard document format of LibreOffice called?
A: OpenDocument Format
B: OpenXML Format
C: LibreDocument Format
7 – What is a “Hybrid PDF?”
A: It includes interactive elements and animations
B: It includes all fonts, to display properly everywhere
C: It includes the original source document, to allow editing
8 – LibreOffice includes a dockable window to help you move around complex documents. What is it called?
A: DocBrowser
B: Navigator
C: Overview
9 – If you want Writer to automatically add numbered captions when inserting objects, where do you go?
A: Tools > Options > Objects > Preferences
B: Insert > Image > tick “Add captions” box
C: Tools > Options > LibreOffice Writer > AutoCaption
10 – With which major LibreOffice release did the branding change to include cubes?
A: LibreOffice 4
B: LibreOffice 5
C: LibreOffice 6
11 – LibreOffice 6.2 will include a new (optional) user interface design. What’s its name?
A: TabBar
B: GroupedBar
C: NotebookBar
12 – Where did the 2013 LibreOffice Conference take place?
A: Berlin
B: Milan
C: Paris
13 – And where will the 2019 Conference be?
A: Almeria
B: Stockholm
C: Budapest
14 – Markus Mohrhard is a long-time LibreOffice developer, who has been involved in the project since its early years. What is his nickname?
A: Moggi
B: Marko
C: Maggi
15 – Another hard-working member of the community is “raal”, who helps out with events in the Czech Republic. But what’s his real name?
A: Stanislav Horáček
B: Zdeněk Crhonek
C: Jan Dvořák
16 – Finally, who can join the LibreOffice project and help to improve the software?
A: Experienced C++ developers
B: Members of The Document Foundation
C: Absolutely anybody
And now, the answers:
1: C
2: B
3: A
4: B
5: B
6: A
7: C
8: B
9: C
10: C
11: C
12: B
13: A
14: A
15: B
16: C, of course!
We in the community wish you all a great Christmas and festive time, and a happy new year. Here’s to a great 2019, with many more LibreOffice releases, events and fun to be had!
HTF MI broadcasted a new title “Global Floor Mount Optical Distribution Frame (ODF) Market Research Report 2018” with 127 pages and in-depth assessment ...
Gerlinda de Vries is sinds september 2018 als Rijkstrainee in dienst bij het Bureau Forum Standaardisatie (onderdeel van het ministerie Binnenlandse Zaken en Koninkrijksrelaties). Het bureau zet zich in voor open ICT-standaarden. De opdracht van De Vries? Bouw een community rondom documentstandaarden. In gesprek met de community manager ‘Open Documentstandaarden’.
‘Toen we deze website gingen bouwen had ik een online community voor ogen waar leden elkaar ondersteunen rondom de problematiek en veranderingen binnen de documentstandaarden’, vertelt de Vries. ‘De doelgroep hebben we expres zo breed mogelijk gehouden. Zo kan iedereen die geïnteresseerd is meelezen en meewerken aan de community. Dat maakt ook dat er vanuit verschillende kanten ervaringen gedeeld kunnen worden. We profileren ons niet als expertisecentrum maar juist als verbinder. Daar waar kan verwijzen we door naar bijvoorbeeld DigiToegankelijk.
‘We bieden leden nieuws, blogs, agenda en forums. Daarnaast plaatsen we ongeveer één keer per week een artikel over het laatste nieuws rondom toegankelijkheid of documentstandaarden. Op deze manier blijven de leden op de hoogte. Verder stimuleren we interactie zo veel als mogelijk. We schrijven zelf blogs of vragen anderen ze te schrijven. En leden kunnen natuurlijk zelf ook een blog plaatsen als ze bijvoorbeeld kennis willen delen over een specifieke standaard. Hier kan op gereageerd worden en zo ontstaat discussie. Verder staan we open voor input van de leden zelf. Als er veel behoefte is aan een specifiek onderwerp gaan we daar zeker iets mee doen. Zo zijn er vragen opgekomen rond marktpartijen en of we die ook moeten uitnodigen voor de community. Daar zijn we mee bezig’.
‘We profileren ons niet als expertisecentrum maar juist als verbinder’
Gerlinda de Vries, Community manager.
Op de forums pagina zijn vier groepen te vinden, elk gericht op een andere standaard: PDF, html, Markdown en ODF. De Vries licht toe: ‘Binnen deze groepen kunnen leden vragen stellen, bestanden uitwisselen en de wiki raadplegen. In de toekomst zullen we waarschijnlijk andere groepen toevoegen. Per groep kan er gezocht worden op de verschillende categorieën: organisatie, gebruiker en beleid. Wil je bijvoorbeeld alleen nieuws lezen over PDF en het beleid, dan kan je de categorieën daarop instellen.
Zonder Pleio-profiel kan de website alleen bekeken worden. ‘Om te kunnen reageren of content te schrijven of te delen is het noodzakelijk om een pleio-profiel aan te maken. In het eigen profiel kunnen leden interesses aangeven. Daarbij kunnen ze instellen of ze mail willen krijgen met een periodiek overzicht van alle ontwikkelingen en hoe vaak ze een overzicht willen ontvangen’.
Gevraagd naar waar de behoefte ligt van de leden, vertelt de Vries: ‘We zien dat er vooral veel vraag is naar ervaringen van anderen en manieren om de organisatie te betrekken. Het is niet alleen de verantwoordelijkheid van de communicatieafdeling. Iedereen die content produceert kan zijn steentje bijdragen’.
Een van de speerpunten van het huidige kabinet is ‘digitale inclusie: iedereen moet kunnen meedoen’. ‘In Nederland zijn er ongeveer vier miljoen mensen met een beperking. Deze groep mensen moet digitaal mee kunnen komen en hebben behoefte aan toegankelijke informatie. Zeker omdat de samenleving steeds verder digitaliseert’, aldus de Vries. ‘Toegankelijk zijn is dan ook eerder een hygiënekwestie, niet alleen een wettelijke verplichting.
De winst van de deze online community is dat we meer bekendheid kunnen geven aan het onderwerp. Niet alleen de bewustwording groeit. De kennis en ervaring die er gedeeld wordt, helpt andere organisaties bijvoorbeeld bij het kiezen van een strategie. Open Documentstandaarden heeft nu 50 leden en we hopen te blijven groeien.
‘Uiteraard proberen wij ook ons eigen hondenvoer te eten en we beseffen dat Pleio de toegankelijkheid nog niet helemaal op orde heeft. Pleio staat echter zeer open voor suggesties en verbeteringen en heeft al aangegeven dat ze hier zeker aan gaan werken’, besluit de Vries.
Foto’s: René de Gilde
Het bericht Community Open Documentstandaarden helpt overheden verscheen eerst op Digitale Overheid.
Software: Add Dropbox
| ← Previous revision | Revision as of 02:03, 18 December 2018 | ||
| Line 162: | Line 162: | ||
|title=Corel WordPerfect Office X4 - Standard Edition - Compatible |
|title=Corel WordPerfect Office X4 - Standard Edition - Compatible |
||
|accessdate=3 May 2008}}</ref> |
|accessdate=3 May 2008}}</ref> |
||
| + | * [[Dropbox (service)|Dropbox]] |
||
* [[Evince]] |
* [[Evince]] |
||
* [[Gnumeric]]<ref>{{cite web|url=https://help.gnome.org/users/gnumeric/stable/gnumeric.html#file-format-odf|title=File Formats|author=Eric Baudais & others|publisher=GNOME Documentation Project|work=The Gnumeric Manual, version 1.12|date=February 2014|accessdate=1 February 2018}}</ref> |
* [[Gnumeric]]<ref>{{cite web|url=https://help.gnome.org/users/gnumeric/stable/gnumeric.html#file-format-odf|title=File Formats|author=Eric Baudais & others|publisher=GNOME Documentation Project|work=The Gnumeric Manual, version 1.12|date=February 2014|accessdate=1 February 2018}}</ref> |
||
FOSDEM is one of the largest gatherings of Free Software contributors in the world and takes place each year in Brussels (Belgium) at the ULB Campus Solbosch. In 2019, it will be held on Saturday February 2, and Sunday February 3.
The Open Document Editors DevRoom is scheduled for Saturday, February 2 (from 10:30AM to 7:00PM, room UB2.147).
We are inviting proposals for talks about Open Document Editors or the ODF standard document format, on topics such as code, localization, QA, UX, tools, extensions and adoption-related cases. Please keep in mind that product pitches are not allowed at FOSDEM.
The length of talks should be limited to a maximum of 25 minutes, as we would like to have questions after each presentation, and to fit as many presenters as possible in the schedule. Exceptions must be explicitly requested and justified. You may be assigned LESS time than you request.
All submissions have to be made in the Pentabarf event planning tool: https://penta.fosdem.org/submission/FOSDEM19.
While filing your proposal, please provide the title of your talk, a short abstract (one or two paragraphs), some information about yourself (name, bio and photo, but please do remember that your profile might be already stored in Pentabarf).
To submit your talk, click on “Create Event”, then make sure to select the “Open Document Editors” devroom as the “Track”. Otherwise, your talk will not be even considered for any devroom at all.
If you already have a Pentabarf account from a previous year, even if your talk was not accepted, please reuse it. Create an account if, and only if, you don’t have one from a previous year. If you have any issues with Pentabarf, please contact ode-devroom-manager@fosdem.org.
The deadline is Monday, December 24, 2018. Accepted speakers will be notified by Thursday, December 27, 2018. The schedule will be published on Monday, December 31, 2018.
Recording Permission
We will record and stream all main tracks, devrooms and lightning talks live. The recordings will be published under the same licence as all FOSDEM content (CC-BY). If, exceptionally, you believe there is a legitimate reason why your presentation should not be streamed or recorded, you must seek our agreement before submitting it.
In the “Submission notes” field, please indicate that you agree to have your presentation recorded and published under the same license as all FOSDEM content (CC-BY). For example: “If my speech is accepted for FOSDEM, I hereby agree to be recorded and to have recordings – including slides and other presentation related documents – published under the Creative Commons Attribution (CC-BY) 4.0 International License. Sincerely, Name”.
New Delhi, Dec 13 (IANS): Around nine crore toilets have been built across the country since October 2014 under the Swachh Bharat Mission (Gramin) and a ...
A picture of contributors attending LibOCon in Tirana, during a break. Most of them could travel to Albania thanks to the economic resources made available by our generous donors. Consider a donation to LibreOffice, to support our contributors traveling to events to talk about LibreOffice and ODF: https://www.libreoffice.org/donate
Many companies around the world use free and open source software (FOSS) to reduce costs, improve reliability, and free themselves from vendor lock-in. Today we talk to Iwan Tahari from FANS, an Indonesian shoe manufacturer, which has migrated to GNU/Linux and LibreOffice:
Firstly, tell us about your company, and your role in it…
I work at the FANS shoes factory in Tangerang, Indonesia. Our company has produced FANS shoes since 2001. As an Operation Director, I have to maintain smooth operation in the whole process, to improve our product quality and services. Currently, we have remote offices in Medan, Palembang, Surabaya and Solo that connect directly to our factory in Tangerang. All of our offices use free and open source software for daily operations.
When did you decide to migrate to open source software – and why?
We started to introduce FOSS to our staff in 2007 by dual-booting MEPIS Linux and Microsoft Windows XP on one out of three PCs that we had. It was a complete failure; the users almost never booted into MEPIS. Learning from the past mistakes, in 2012 we did a partial migration with five new notebook PCs installed with Linux Mint 13, for all managers and some higher-level staff members. Seven old PCs were still running Windows XP.
In 2013, we migrated almost all of the PCs to FOSS – only one Windows PC was left in the research and development department, because it was still using Corel Draw. In March 2014, we had a special training for using Inkscape, a vector graphics program. After the training, we fully migrated to FOSS. As of today, we still use only FOSS in all of our operations.
The main reason we migrated to FOSS was to have reliable and stable operations. Around 2012-2013, there was a nasty computer virus in Indonesia called Brontok. The main anti-virus programs were not fast enough to handle the widespread attack, so the only way to fix it was to reinstall the operating system.
This was so bad because of the high downtime in the reinstallation process. The only PCs that were not affected were Linux-based PCs. Since we migrated to FOSS, we have never reinstalled the operating system because of viruses or malware, even though we never use anti-virus software on our Linux-based PCs.
The other reason we use FOSS is cost-saving. Proprietary licenses are very costly; for each application we have to purchase separate licenses for each machine, while with FOSS the programs are completely free and we can install them on as many machines as we want. Our company has saved 133 millions Rupiah by using FOSS (around USD 10,000).
Tell us about your initial experiences with FOSS…
My first experience with open source software as when I was a university student. I graduated from CalPoly (California Polytechnic State University) in San Luis Obispo. My major is MIS (Management of Information Systems). One of our computer classes introduced us to Red Hat Linux. Honestly, I didn’t have a good experience with it (I believe it was Red Hat 4.0).
It took a long time and it was very complicated just to install the OS on an early Pentium machine (just to get the display to work correctly, and the configuration was really difficult for a regular user too). Well, it had a GUI, and some applications like AbiWord and Gnumeric but it was painfully slow. So at that time I believed that open source software was not for a regular users.
After I graduated, I worked in the logistics department of PT. Rodamas Jakarta (a nation-wide distribution company). One day, I saw InfoLinux magazine (a local Indonesian magazine that focuses on open source software) in the IT department. The magazine had a lot of good articles, and it came with a CD/DVD that contained a variety of Linux distributions. I also subscribed to this magazine. I become more interested in the open source world, and tried several live distributions like Knoppix without installing the OS.
Some came with OpenOffice which was similar to Microsoft Office. I liked OpenOffice better than Gnumeric and Abiword. My wife used to work in Haga Bank (a local Indonesian bank now acquired by Rabobank). Her office was using Fedora Linux and OpenOffice for daily operations without any critical problems. Learning from her experiences, when I became Operation Director at FANS shoes, I started the FOSS migration.
Why did you choose LibreOffice?
Because most Linux distros thesedays come with LibreOffice. It’s better to use the office suite that comes with the distro; it saves us time, as we don’t have to install another suite. For our company, LibreOffice is the best replacement for Microsoft Office. If there were no LibreOffice, we would probably have never migrated to FOSS.
I have an interesting story about LibreOffice: one time, my brother called me to ask for some help with his computer. He said he had received a Microsoft Office document file (docx), but he couldn’t open it. Unfortunately, his computer had an outdated OS and MS Office (Windows XP and Office XP).
He said that it’s urgent, that he needed to read the content of this document now. Well, it was late at night, so he was not able to get the installer from the computer store. So I said to him, try downloading LibreOffice, and see if it can open the file. So, he installed LibreOffice in his PC. He was really fortunate that the docx file could be opened with just a little problem (the text was not aligned properly), but at least it was readable. Since then, his computer has LibreOffice, and he continues to use it.
How popular is FOSS in Indonesia?
Open source in Indonesia is getting more popular. In the server market, open source solutions are growing rapidly here because they are cheaper than proprietary software. Unfortunately, it is not the same for daily home or office use of FOSS. Proprietary software like Windows, Office, Adobe suite, Corel Draw etc. are so dominant here. People are already familiar with these proprietary programs and are hesitate to change. Piracy is the main cause of the slow growth of FOSS in Indonesia – currently, there are more people using pirated software than original legal software.
It is very easy to get pirated software in Indonesia. It can be acquired at many computer stores – and sometimes it is included for free when purchasing a PC. So in fact, it’s much easier to get pirated software than FOSS. Still, our government is a little bit strict with pirated software in medium and large companies. Because of that, some companies have adopted FOSS. So I believe Free Software will keep continue to grow in Indonesia, but the adoption rate of FOSS will depend on the how good its marketing is, and also how strict the law enforcement of pirated software is as well.
What were your personal experiences in the Indonesian open source community?
At the early stage of the FOSS migration, I pretty much did everything by myself. I learned FOSS mostly from the web. Fortunately, most FOSS literature is available in the English language, which I can understand. In our company, the LibreOffice migration was a lot easier compared with migrations to other programs like Inkscape and GIMP. At first, we were having trouble migrating to Inkscape until we met Sokhibi (owner of Istana Media, and writer of several open source books).
We invited him to train us using Inkscape. From there, he introduced us to Blankon Linux (a custom Indonesian Linux distro). He was the Documentation Coordinator of Blankon Linux. Then the Blankon community helped us a lot in our migration – we even have a custom version of Blankon Linux specifically for our company needs.
Together with Ahmad Haris (Blankon Public Relation Coordinator), we created a writing contest for using FOSS, and we released an Indonesian Inkscape guidebook. In 2015, we had the GNOME Asia Conference in Indonesia – this was my first time being a guest speaker at a FOSS conference. I met so many excellent people from around the world that were helping the FOSS movement! I was introduced to other local open source communities (such as openSUSE Indonesia, Ubuntu Indonesia, the Indonesian Linux User Group etc).
Since then, I have been active with our local FOSS community, and our company has sponsored several FOSS activities/projects. In 2018, we held an Indonesian conference for LibreOffice. It was a big success, so many people are eager to know about the software. Sokhibi also released an Indonesian LibreOffice Writer guide, which is sponsored by our company.
The LibreOffice project was born in Europe, and had strong roots in that continent. What should we do to increase the market penetration in Indonesia?
It should be easy for LibreOffice to become more widespread in Indonesia. Most Linux distributions already include LibreOffice, so it’s no problem for Indonesian Linux users. Now, the problem is that there are only a small amount of Linux users here. LibreOffice is not known to most Windows users. I think LibreOffice’s marketing community needs to learn/adopt the strategy of Mozilla Firefox in winning the browser war with Internet Explorer. VLC (VideoLan Client) is also another successful open source software that is widely adopted in Indonesia. So these things need to be done:
Thinking of the culture barrier and language barrier: which is the bigger one for open source?
With better technology, the language barrier will become smaller and smaller. We can now use many translation applications to help people adopt FOSS in many different languages. However, a culture barrier like the “piracy culture” I mentioned is not an easy thing to be solved. Probably it needs several generations of efforts to significantly reduce it. To end piracy, people need to change their mindset which I think is very difficult. We need to fight this piracy culture because it is bad for the whole community. For Indonesia, I believe this is number one enemy to the FOSS movement.
Finally, where do you see LibreOffice in five years from now?
I see great prospects for LibreOffice. In five years, I am sure LibreOffice will be gaining more and more users. The format war will be a long war, but in the end, the Open Document Format (ODF) will win the war. Like the web browser wars where the proprietary browsers are losing, I believe LibreOffice will one day win over MS Office. From version to version, LibreOffice is getting better and better while still retaining format compatibility, which is the key benefit of using LibreOffice. I believe LibreOffice will have a high chance to become the most-used in Indonesia with great efforts. When LibreOffice becomes the number one office suite here, I think all of the remaining South East Asia countries will follow.
Thanks to Iwan for his thoughts and feedback! One of the goals of LibreOffice is to be available in as many languages as possible, so if you’re reading this and want to help translate the interface into your native language see here to get started!
Consider a donation to LibreOffice to help the project produce even more gadgets for volunteer contributors, free software advocates and proud users, to raise the awareness of LibreOffice and Open Document Format (ODF)
Polish security services have launched an investigation into the Open Dialogue Foundation (ODF) following serious allegations about its funding, writes James ...
A regional review meeting of the North Eastern States was held here on Thursday held discussions on sustaining Open Defecation Free (ODF) status, solid and ...
Ranchi, Nov 15 (IANS): Jharkhand was declared Open Defecation Free (ODF) on its Statehood Day on Thursday and seven districts were announced to be fully ...
Ranchi, Nov 15 (IANS): Jharkhand was declared Open Defecation Free (ODF) on its Statehood Day on Thursday and seven districts were announced to be fully ...
The “2018 Future Of Global Wall Mount Optical Distribution Frame (ODF) Market to 2025 – Competition, Growth Opportunities, And Outlook Of Wall Mount ...
Ranchi, November 5: Jharkhand is all set to become an open defecation free (ODF) state by 15th November 2018. The day is also marked as the foundation day ...
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).
Read more of this story at Slashdot.
Software: add MS Office 2019
| ← Previous revision | Revision as of 18:29, 3 October 2018 | ||
| Line 173: | Line 173: | ||
* [[Microsoft Office 2010]] supports ODF 1.1 (Windows only) |
* [[Microsoft Office 2010]] supports ODF 1.1 (Windows only) |
||
* [[Microsoft Office 2013]] supports ODF 1.2 (Windows only) |
* [[Microsoft Office 2013]] supports ODF 1.2 (Windows only) |
||
| − | * [[Microsoft Office 2016]] |
+ | * [[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]] |
||
On the blessed occasion of Gandhi Jayanti, rural Nagaland was declared Open Defecation Free (ODF) on October 2.
The government event to mark the Open Defecation Free (ODF) tag achieved by Puducherry, was marred by an on-stage altercation between L-G Kiran Bedi ...
This year’s LibreOffice Annual Conference has been held in Tirana, Albania on September 25 to September 28, 2018. It was organized by a group of independent volunteers from the Open Labs Hackerspace in Tirana.
I will try to give some information about my talks, and share my experience.
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.
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
In this lightning talk, I tried to give a quick status report on: What has been done/improved/fixed in the Customize dialog after GSoC 2017 until now; what is the current status, what is left to do, and the future plans.
The slides of the presentation on Speaker Deck
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.
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.
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.
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.
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.
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.
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.
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.
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.
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
As per the government, India will lay claim to being an ODF nation by February 2019. Under the Swachh Bharat Abhiyan, 76 per cent of India's villages have ...
Prime Minister Narendra Modi had called the open defecation free (ODF) a movement of respect for motherhood and women. Swachh Sarvekshan Gramin 2018: ...
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. :-)
Prime Minister Narendra Modi's home state is lagging behind in implementation of his pet sanitation programme, with a report saying that 9.34 lakh households ...
Gandhinagar: The Comptroller and Auditor General (CAG) has said that the government's claim of Gujarat being 'Open Defecation Free' (ODF) appears to be ...
In September 2018 Friends of OpenDocument published the printed edition of the LibreOffice 6.0 Getting Started Guide, written by the LibreOffice Documentation Team. Free PDFs and ODTs are available from the LibreOffice website. Purchase printed copies from our store at Lulu.com.
STATE TIMES NEWS SRINAGAR: Governor Satya Pal Malik on Saturday declared the state Open Defecation Free (ODF) and launched the “Swachhta Hi Seva ...
Uttar Pradesh Chief Minister Yogi Adityanath on Saturday said that the state would become open defecation free by October 2, 2019, with his government ...
Read more of this story at Slashdot.
Rescuing 1 sources and tagging 1 as dead. #IABot (v2.0beta8)
| ← Previous revision | Revision as of 20:50, 2 September 2018 | ||
| Line 216: | Line 216: | ||
* Information technology companies like [[Apple Inc.]], [[Adobe Systems]], [[Google]], [[IBM]], [[Intel]], [[Microsoft]], [[Nokia]], [[Novell]], [[Red Hat]], [[Oracle Corporation|Oracle]] as well as other companies who may or may not be working inside the OASIS OpenDocument Adoption Technical Committee. |
* Information technology companies like [[Apple Inc.]], [[Adobe Systems]], [[Google]], [[IBM]], [[Intel]], [[Microsoft]], [[Nokia]], [[Novell]], [[Red Hat]], [[Oracle Corporation|Oracle]] as well as other companies who may or may not be working inside the OASIS OpenDocument Adoption Technical Committee. |
||
* Over 600 companies and organizations promote OpenDocument format through The [[OpenDocument Format Alliance]].<ref>{{cite web |url=http://www.odfalliance.org/members.php |title=ODF Alliance members |accessdate=24 May 2009 |work=ODF Alliance |deadurl=yes |archiveurl=https://web.archive.org/web/20090403055912/http://www.odfalliance.org/members.php |archivedate=3 April 2009 |df=dmy-all }}</ref> |
* Over 600 companies and organizations promote OpenDocument format through The [[OpenDocument Format Alliance]].<ref>{{cite web |url=http://www.odfalliance.org/members.php |title=ODF Alliance members |accessdate=24 May 2009 |work=ODF Alliance |deadurl=yes |archiveurl=https://web.archive.org/web/20090403055912/http://www.odfalliance.org/members.php |archivedate=3 April 2009 |df=dmy-all }}</ref> |
||
| − | * [[NATO]] with its 26 members uses ODF as a mandatory standard for all members.<ref>{{cite web|url=http://www.h-online.com/news/NATO-supports-ODF-open-document-format--/111127|title=NATO supports ODF open document format|first=Stefan|last=Krempl|publisher=The H Open|date=18 July 2008<!--, 15:28-->|accessdate=10 September 2012}}</ref> |
+ | * [[NATO]] with its 26 members uses ODF as a mandatory standard for all members.<ref>{{cite web|url=http://www.h-online.com/news/NATO-supports-ODF-open-document-format--/111127|title=NATO supports ODF open document format|first=Stefan|last=Krempl|publisher=The H Open|date=18 July 2008<!--, 15:28-->|accessdate=10 September 2012|archive-url=https://web.archive.org/web/20090924190030/http://www.h-online.com/news/NATO-supports-ODF-open-document-format--/111127|archive-date=24 September 2009|dead-url=yes|df=dmy-all}}</ref> |
* The TAC (Telematics between Administrations Committee), composed of e-government policy-makers from the 25 [[European Union]] Member States, endorsed a set of recommendations for promoting the use of open document formats in the public sector.<ref name="ec.europa.eu">{{cite web|url=http://ec.europa.eu/idabc/en/document/3197.html|title=IDA promotes the use of open document formats for e-government interoperability|work=IDA Report 22|date=June 2004|publisher=IDABC|accessdate=10 September 2012}}</ref> |
* The TAC (Telematics between Administrations Committee), composed of e-government policy-makers from the 25 [[European Union]] Member States, endorsed a set of recommendations for promoting the use of open document formats in the public sector.<ref name="ec.europa.eu">{{cite web|url=http://ec.europa.eu/idabc/en/document/3197.html|title=IDA promotes the use of open document formats for e-government interoperability|work=IDA Report 22|date=June 2004|publisher=IDABC|accessdate=10 September 2012}}</ref> |
||
* The free office suites [[Apache OpenOffice]], [[Calligra]], [[KOffice]], [[NeoOffice]] and [[LibreOffice]] all use OpenDocument as their default file format. |
* The free office suites [[Apache OpenOffice]], [[Calligra]], [[KOffice]], [[NeoOffice]] and [[LibreOffice]] all use OpenDocument as their default file format. |
||
| Line 274: | Line 274: | ||
** [[Portugal]]<ref>{{cite web |url=http://www.esop.pt/portugal-publishes-open-standards-catalogodf-pdf-and-several-other-standards-are-mandatory/ |title=ESOP » Portugal publishes open standards catalog. ODF, PDF and several other standards are mandatory |publisher=Esop.pt |date= |accessdate=2013-05-01 |archive-url=https://web.archive.org/web/20130402024414/http://www.esop.pt/portugal-publishes-open-standards-catalogodf-pdf-and-several-other-standards-are-mandatory/ |archive-date=2 April 2013 |dead-url=yes |df=dmy-all }}</ref> |
** [[Portugal]]<ref>{{cite web |url=http://www.esop.pt/portugal-publishes-open-standards-catalogodf-pdf-and-several-other-standards-are-mandatory/ |title=ESOP » Portugal publishes open standards catalog. ODF, PDF and several other standards are mandatory |publisher=Esop.pt |date= |accessdate=2013-05-01 |archive-url=https://web.archive.org/web/20130402024414/http://www.esop.pt/portugal-publishes-open-standards-catalogodf-pdf-and-several-other-standards-are-mandatory/ |archive-date=2 April 2013 |dead-url=yes |df=dmy-all }}</ref> |
||
** [[Slovakia]] |
** [[Slovakia]] |
||
| − | ** [[Sweden]]<ref>{{cite web |title=Öppna standarder - Programvaror och tjänster 2014 |url=https://www.avropa.se/contentassets/c5e98243c85f4ac997f905555e504f3b/oppna-standarder---programvaror-och-tjanster--v-1.00--20150617.pdf}}</ref> |
+ | ** [[Sweden]]<ref>{{cite web |title=Öppna standarder - Programvaror och tjänster 2014 |url=https://www.avropa.se/contentassets/c5e98243c85f4ac997f905555e504f3b/oppna-standarder---programvaror-och-tjanster--v-1.00--20150617.pdf }}{{Dead link|date=September 2018 |bot=InternetArchiveBot |fix-attempted=yes }}</ref> |
** [[United Kingdom]]<ref>{{cite web |url=https://www.gov.uk/government/publications/open-source-open-standards-and-re-use-government-action-plan |title=Open source, open standards and re-use: government action plan |publisher=[[Government of the United Kingdom]] |date=27 January 2010 }}</ref> |
** [[United Kingdom]]<ref>{{cite web |url=https://www.gov.uk/government/publications/open-source-open-standards-and-re-use-government-action-plan |title=Open source, open standards and re-use: government action plan |publisher=[[Government of the United Kingdom]] |date=27 January 2010 }}</ref> |
||
{{endflatlist}} |
{{endflatlist}} |
||
August was a big month for our project, with the release of a brand new version of LibreOffice! And surrounding the release, there was lots of activity in our development, documentation, design, QA and translation communities…
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.
If you accept this notice, your choice will be saved and the page will refresh.
This is the latest release of our powerful open-source Qt component, KD Chart, that allows you to create business charts and much more.
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.
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.
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 ...
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 ...
Community members from five different countries had a good time, and talked about holding a LibreOffice Asia Conference in the future
Event report by: Wally Lian, PR & Marketing Consultant, Software Liberty Association Taiwan
This summer is hot in Taiwan, and so are the FOSS (Free and Open Source Software) communities! From the end of July to the middle of August, there were several big FOSS events in Taiwan. The first one coming on stage was the Debian Conference, which was held in Taiwan and Asia for the first time, and lasted for two weeks. Then, this year three big Asian FOSS events of COSCUP, Gnome Asia Summit, and OpenSUSE Asia Summit decided to merge together and held an event at the National Taiwan University of Science and Technology on 11 and 12 August.
Besides these global and Asian FOSS events, there were also many interesting opportunities and plans going on. One of them was: LibreOffice community members in Asia planned to have a meetup during the joint COSCUP/Gnome Asia/OpenSUSE Asia event, and discussed holding a LibreOffice Asia Conference.
This meetup was held in the evening on 11 August in A+A space, which is a nice and friendly space for FOSS communities, also a community made up of several artists who use FOSS as their tools to create their artwork. The attendees included LibreOffice and other FOSS community members from Japan, Korea, Indonesia and Taiwan.
The organizer, Franklin Weng, the current President of Software Liberty Association Taiwan and current board member of The Document Foundation, said that this meetup was an important milestone. “Now the Taiwanese government is going on adopting the Open Document Format and related office suites. It is very important to link our government and our people with international communities. Besides sharing our experiences of adopting ODF and using LibreOffice, we can also learn from many different countries and help each other,” said Franklin.
At the meetup, Franklin introduced the 30-second animation for LibreOffice Android Viewer, which was generated by LibreOffice Taiwan and A+A Space. He explained that the original idea was to raise the awareness of visual design in FOSS communities. Then he explained the meaning and special Easter eggs hidden in the animation, and showed a “behind the scenes” documentary for it. Then, the host of A+A Space, Michael Wu, introduced the wonderful work from A+A Space, including 3D graphs, 3D models, VR work, classes in universities, and so on.
Then everyone started to share their work and experiences. Rania Amina, who was responsible for visual design in the LibreOffice Conference Indonesia, showed his wonderful artwork to attendees. Ahmad Haris also shared his experiences holding LibreOffice Conference Indonesia, which was a huge success. Shinji Enoki shared the current status of Japanese support in LibreOffice, and many events held in Japan. Daehyun Sung introduced himself and shared some interesting things in Korea, including the system North Korea is using.
Also, Bobby Tung, a senior FOSS member in Taiwan who also contributed a lot to W3C standards, shared the current status of Unicode support for CJK. Kevin Lin, a LibreOffice Migration Professional in Taiwan, showed his work on LibreOffice Online and Web form API usage. Shelandy Ting shared his interesting artwork using Gimp.
After sharing, attendees split into different groups and talked with each other. During this meetup, members from Japan and Indonesia showed interest in holding a LibreOffice Asia Conference. Besides conferences, attendees also exchanged experiences migrating to LibreOffice in organizations and public administrations. We believe that the adoption of the Open Document Format and migrations to LibreOffice will advance hugely in Asia.
A big thanks to the LibreOffice communities in Asia for organising this event! If you love LibreOffice and want to help spread the word in your location or language, check out our native language communities. Together we can help to spread the word about free software and open standards!
Under new norms, cities and towns wanting to be declared ODF+ (Open Defecation Free Plus) must also be free of public urination and not just open defecation.
The LibreOffice Documentation Team has published the Writer Guide for version 6.0. It is available for free download (PDF) from the LibreOffice website or can be purchased from the Friends of OpenDocument store at Lulu.com.
Read more of this story at Slashdot.
LibreOffice Documentation Team has just released the LibreOffice 6.0 Writer Guide, with a general Introduction to LibreOffice Writer followed by the following chapters: Working with Text (basics), Working with Text (advanced), Formatting Text, Formatting Pages (basics), Formatting Pages (advanced), Print Export Email, Introduction to Styles, Working with Styles, Templates, Images & Graphics, Lists, Tables of Data, Mail Merge, TOCs Indexes Biblios, Master Documents, Fields, Forms, Spreadsheets Charts Objects, Setting Up Writer and Customizing Writer, for a total of 448 pages.
LibreOffice 6.0 Writer Guide is available from TDF Wiki as ODT and PDF, both the complete book and individual chapters, and from ODF Authors as ODT of individual chapters.
LibreOffice 6.0 Writer Guide is also available as a printed book from Lulu, by Friends of Open Document Inc., an Australia-based volunteer organisation with members around the world which will be using profits from the sale to benefit the LibreOffice community.
Rescuing 1 sources and tagging 0 as dead. #IABot (v2.0beta5)
| ← Previous revision | Revision as of 06:07, 6 August 2018 | ||
| Line 272: | Line 272: | ||
** [[Netherlands]]<ref>{{cite web |title=ODF 1.2 on Dutch "apply or explain" list |url=https://lijsten.forumstandaardisatie.nl/open-standaard/odf12}}</ref> |
** [[Netherlands]]<ref>{{cite web |title=ODF 1.2 on Dutch "apply or explain" list |url=https://lijsten.forumstandaardisatie.nl/open-standaard/odf12}}</ref> |
||
** [[Poland]]<ref>{{cite web |url=http://isap.sejm.gov.pl/DetailsServlet?id=WDU20120000526 |title=Rozporządzenie Rady Ministrów z dnia 12 kwietnia 2012 r. w sprawie Krajowych Ram Interoperacyjności, minimalnych wymagań dla rejestrów publicznych i wymiany informacji w postaci elektronicznej oraz minimalnych wymagań dla systemów teleinformatycznych |publisher=Internetowy System Aktów Prawnych |date= |accessdate=2016-05-17}}</ref> |
** [[Poland]]<ref>{{cite web |url=http://isap.sejm.gov.pl/DetailsServlet?id=WDU20120000526 |title=Rozporządzenie Rady Ministrów z dnia 12 kwietnia 2012 r. w sprawie Krajowych Ram Interoperacyjności, minimalnych wymagań dla rejestrów publicznych i wymiany informacji w postaci elektronicznej oraz minimalnych wymagań dla systemów teleinformatycznych |publisher=Internetowy System Aktów Prawnych |date= |accessdate=2016-05-17}}</ref> |
||
| − | ** [[Portugal]]<ref>{{cite web |url=http://www.esop.pt/portugal-publishes-open-standards-catalogodf-pdf-and-several-other-standards-are-mandatory/ |title=ESOP » Portugal publishes open standards catalog. ODF, PDF and several other standards are mandatory |publisher=Esop.pt |date= |accessdate=2013-05-01}}</ref> |
+ | ** [[Portugal]]<ref>{{cite web |url=http://www.esop.pt/portugal-publishes-open-standards-catalogodf-pdf-and-several-other-standards-are-mandatory/ |title=ESOP » Portugal publishes open standards catalog. ODF, PDF and several other standards are mandatory |publisher=Esop.pt |date= |accessdate=2013-05-01 |archive-url=https://web.archive.org/web/20130402024414/http://www.esop.pt/portugal-publishes-open-standards-catalogodf-pdf-and-several-other-standards-are-mandatory/ |archive-date=2 April 2013 |dead-url=yes |df=dmy-all }}</ref> |
** [[Slovakia]] |
** [[Slovakia]] |
||
** [[Sweden]]<ref>{{cite web |title=Öppna standarder - Programvaror och tjänster 2014 |url=https://www.avropa.se/contentassets/c5e98243c85f4ac997f905555e504f3b/oppna-standarder---programvaror-och-tjanster--v-1.00--20150617.pdf}}</ref> |
** [[Sweden]]<ref>{{cite web |title=Öppna standarder - Programvaror och tjänster 2014 |url=https://www.avropa.se/contentassets/c5e98243c85f4ac997f905555e504f3b/oppna-standarder---programvaror-och-tjanster--v-1.00--20150617.pdf}}</ref> |
||
External links: Move {{Authority control}} to bottom.
| ← Previous revision | Revision as of 14:49, 3 August 2018 | ||
| Line 332: | Line 332: | ||
{{OpenOffice|state=collapsed}} |
{{OpenOffice|state=collapsed}} |
||
{{List of International Electrotechnical Commission standards}} |
{{List of International Electrotechnical Commission standards}} |
||
| ⚫ | |||
{{Document markup languages}} |
{{Document markup languages}} |
||
| + | |||
| ⚫ | |||
[[Category:OpenDocument]] |
[[Category:OpenDocument]] |
||
External links: Add {{Document markup languages}}.
| ← Previous revision | Revision as of 14:49, 3 August 2018 | ||
| Line 333: | Line 333: | ||
{{List of International Electrotechnical Commission standards}} |
{{List of International Electrotechnical Commission standards}} |
||
{{Authority control}} |
{{Authority control}} |
||
| + | {{Document markup languages}} |
||
[[Category:OpenDocument]] |
[[Category:OpenDocument]] |
||
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:
Windows:
(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. :-)
I looked into a migration of the ODFAuthors site to a current Plone version with the data from the website yesterday. It took me a lot of hours to figure out the most easy way to do this. I tried to migrate from LinguaPlone to the new multilingual Plone plug-in first, but without success. I could update the buildout inside a test environment with the new plug-in, but I wasn’t able to migrate the content to the new framework. And even I wasn’t able to get rid of LinguaPlone. I didn’t get the option to remove it. I got always a traceback and found some users that run into the same issue without a solution. Thus I had to change my strategy. I exported the content that I need to migrate, set up a new and clean Plone 4.3.x environment and tried to updated it to the latest version of 4.3. I had to do some editing on the buildout and had to drop some Plone add-ons from the current buildout script of ODFAuthors. Once I had done this the buildout runs fine and I got a clean new Plone environment. Then I added the plug-ins plone.app.contenttypes and Products.contentmigration to the buildout script and run buildout again. I started the Plone instance, created a new Plone site and imported the content (exported from the current ODFAuthors site).
I activated the plug-in plone.app.contenttypes and run the migration scripts from Products.contentmigration. I had to migrate more than 4200 content objects and took a fair amount of time. But in the end the migration from the old Archetype content types to the new Dexterity ones was successful.
The next step would be the migration of the instance from Plone 4.3.x to Plone 5.0.x or 5.1.x.
If the website ODFAuthors should be improved for the future use the first step would be the change of the localization framework from the old LinguaPlone to the current
plone.app.multilingual and migrate and reindex all content objects. It’s not possible to update the site to the latest Plone without that step.
I already created a Plone buildout for an upgraded ODFAuthors website that is based on version 5.1.x. This buildout is available from the Github repository of The Document Foundation: https://github.com/tdf/odfauthors.org
As of today, June 27th, I am no longer working for IBM. Last quarter’s widely-reported “resource actions” (lay-offs) hit my group and this time my number came up.
It was a good run, 27 years with one company, something that is not so common today.
Fresh out of Harvard I started working at Lotus Development Corporation in Cambridge, Massachusetts, initially doing technical support, including for the Lotus 1‑2-3 C-language developer toolkit. From there I worked in support’s application development team, developing and maintaining our internal information retrieval system, a hodgepodge of a DOS user-interface, a search engine (using a Bayesian inference network) and a fax-on-demand system, all over NetBIOS.
From support I transitioned over to development, to the SmartSuite team, where I first focused on Freelance Graphics, which was transitioning from C to C++, Windows and OS/2, then on a set of Windows ActiveX controls called eSuite DevPack, some Java components and attempts at an office suite running on a Java-based “thin client” or network computer (eSuite Workplace.) It was a time when the thinking, at least in my little part of the world, was that the traditional desktop applications were dead, and all future work would be done in Java running on your desktop web browser. From this came the browser wars.
Then, in 1995, IBM came a knocking and bought Lotus. Our focus, naturally, shifted from desktop to server-based computing, from Java applets to Java servlets. I worked on various projects, from the K-Station Portal (based initially on Domino) to the Apache Xalan XSLT engine to XForms to WebSphere Portal. I developed a framework for document conversions within WebSphere Portal that we called Document Conversion Services (DCS).
Then, one day, I got an odd call, out of the blue, a very senior person asking whether I was familiar with the file formats from SmartSuite and Microsoft Office. Evidently, no one else in the company would admit to having that arcane knowledge. So, I was drafted onto a “special project,” with a few other talented engineers, a real fun group working on various stealthy tasks, the details of which I am still not at liberty to discuss.
Somewhat overlapping the above, I worked on the things that readers of this blog will be more familiar with, the development of the OpenDocument Format (ODF) standard at OASIS and ISO, and the arguments against ISO ratification of Microsoft’s Office Open XML (OOXML) file format. This then overlapped, in part, with my work to establish the OpenOffice project at Apache, based on Oracle’s contribution, to get IBM Symphony contributed as well, and to bring those two efforts together.
Those years were among the most memorable of my career. I was able to work with a lot of talented and enthusiastic people, within IBM, of course, but also at other companies, with non-profits, with academia and government. I was able travel and see parts of the world I might never have otherwise seen, speak to a lot of audiences about the importance of open standards. I even testified to a few legislative committees. My business travels took me to Brussels, Berlin, Budapest, Barcelona, Granada, London, Paris, Lyon, Rome, Orvietto, Geneva, Amsterdam, the Hague, Beijing, Seoul and Johannesburg. It was a lot of hard work, but it was meaningful. Open standards and open source matter. I have many fond memories of those years.
Eventually, however, corporate interest in document editors, document standards, “social documents” and similar initiatives fizzled, and I no longer had support for remaining involved in ODF and OpenOffice. I needed to move on, to find a new gig.
I looked internally within IBM for something that would combine my hard technical skills and my soft skills, including working closely with attorneys, an ability to “meet them half way” when discussing complicated legal/technical topics. Since I’ve been an active inventor throughout my IBM career, with 54 patents to my name, and a good head for reading and analyzing patents, I spent a few years working as a patent engineer, helping to monetize IBM’s vast patent portfolio, developing technical evidence for infringement, identifying possibilities for patent licencing and assignment, etc.
That’s where things stood as of today, when I handed in my badge and laptop.
As for what is next, I honestly cannot yet say what “Rob 2.0” will be. I plan on taking some time to mull things over and explore my options.
One thing I do plan to do, relatively soon, is start a new blog, a fresh start, on a new path at this domain, preserving this older blog at its current (/blog) URL.
Donations to The Document Foundation are used for many purposes, such as organising events, maintaining our infrastructure, and paying a small team to handle QA, marketing, documentation and other tasks. But donations are also used to fund tenders, whereby companies and individuals improve LibreOffice in specific areas and share knowledge with the community.
One such tender was posted in May 2017: “improve image handling in LibreOffice (#201705-01)“. When images are used in LibreOffice documents, the software manages them in a “life-cycle” which includes importing, displaying, modifying, exporting and more. To save memory – especially with large documents – images that are not currently on screen are sometimes moved out of memory and saved onto disk in a technique known as “swapping” or “paging”. The goal of the tender was to improve LibreOffice in these areas, making it more efficient at handling images and modernising the code base.
Collabora was selected to implement the tender; the work is now complete, and it will benefit all users in the upcoming LibreOffice 6.1 (due to be released in early August). Here are some technical notes about what was improved in the source code of LibreOffice, and what was achieved.
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.
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 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.
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:
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.
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.
I worked very hard on the new Plone buildout for the ODFAuthors website during the last days. I nearly finished the buildout today. I created a new policy and a theming product for the site. I added a template for the frontpage of the new website and am waiting for the input about the content, that the new frontpage should show.
I also need some suggestions on the new publication workflow of the site. The Plone workflow tool is able to run very subtle grained ones. The Plone Content Management System is also able to send automatic messages on all events like changing the workflow state.
Re-inserting line which seems to have been deleted in error
| ← Previous revision | Revision as of 11:46, 17 June 2018 | ||
| Line 219: | Line 219: | ||
* The TAC (Telematics between Administrations Committee), composed of e-government policy-makers from the 25 [[European Union]] Member States, endorsed a set of recommendations for promoting the use of open document formats in the public sector.<ref name="ec.europa.eu">{{cite web|url=http://ec.europa.eu/idabc/en/document/3197.html|title=IDA promotes the use of open document formats for e-government interoperability|work=IDA Report 22|date=June 2004|publisher=IDABC|accessdate=10 September 2012}}</ref> |
* The TAC (Telematics between Administrations Committee), composed of e-government policy-makers from the 25 [[European Union]] Member States, endorsed a set of recommendations for promoting the use of open document formats in the public sector.<ref name="ec.europa.eu">{{cite web|url=http://ec.europa.eu/idabc/en/document/3197.html|title=IDA promotes the use of open document formats for e-government interoperability|work=IDA Report 22|date=June 2004|publisher=IDABC|accessdate=10 September 2012}}</ref> |
||
* The free office suites [[Apache OpenOffice]], [[Calligra]], [[KOffice]], [[NeoOffice]] and [[LibreOffice]] all use OpenDocument as their default file format. |
* The free office suites [[Apache OpenOffice]], [[Calligra]], [[KOffice]], [[NeoOffice]] and [[LibreOffice]] all use OpenDocument as their default file format. |
||
| + | * Several organisations, such as the [https://web.archive.org/web/20071027064136/http://opendocumentfellowship.com/ OpenDocument Fellowship] and [http://opendocsociety.org/ OpenDoc Society] were founded to support and promote OpenDocument. |
||
* The UK government has adopted ODF as the standard for all documents in the UK civil service<ref>{{cite web | url=https://www.gov.uk/government/news/open-document-formats-selected-to-meet-user-needs|title=Open document formats selected to meet user needs}}</ref> |
* The UK government has adopted ODF as the standard for all documents in the UK civil service<ref>{{cite web | url=https://www.gov.uk/government/news/open-document-formats-selected-to-meet-user-needs|title=Open document formats selected to meet user needs}}</ref> |
||
* The [[Wikimedia Foundation]] supports ODF export from [[MediaWiki]], which powers [[Wikipedia]] and a number of other Internet [[wiki]]-based sites.<ref>{{cite web | url= https://wikimediafoundation.org/wiki/Wikis_Go_Printable | title= Wikis Go Printable | work= [[Wikimedia Foundation]] | date= 13 December 2007 | accessdate= 31 December 2007}}</ref> |
* The [[Wikimedia Foundation]] supports ODF export from [[MediaWiki]], which powers [[Wikipedia]] and a number of other Internet [[wiki]]-based sites.<ref>{{cite web | url= https://wikimediafoundation.org/wiki/Wikis_Go_Printable | title= Wikis Go Printable | work= [[Wikimedia Foundation]] | date= 13 December 2007 | accessdate= 31 December 2007}}</ref> |
||
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]] |
||
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> |
||
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).
Outcomes of a government programme are limited to target achievements. Once a village is declared ODF, attention towards it is likely to reduce. This creates a ...
Outcomes of a government programme are limited to target achievements. Once a village is declared ODF, attention towards it is likely to reduce. This creates a ...
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:
Image with native data we don’t understand and just preserve.
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.
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. :-)
Read more of this story at Slashdot.
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:
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):
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…
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 Tomaž Vajngerl (noreply@blogger.com) at April 23, 2018 02:59 PM
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‌
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)
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:
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.
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.
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!
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.
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.
The post Using Collabora Online to accelerate document conversion appeared first on Collabora Productivity.
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.
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] |
+ | * 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 |
+ | ** [[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}} |
||
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.
(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!
Read more of this story at Slashdot.
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
{{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}}}} |
||
At last there is some Swachhta on ground. Rajasthan becomes Open Defecation Free (ODF) to join the select league of ODF states which include Gujarat, ...
Rajasthan, geographically the largest state in the country, is all set to keep up its date with the Open Defecation Free (ODF) declaration deadline of March 31.
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‌
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:
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]
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 |
|
|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 |
|
|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="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 |
|
|class="hlist" style="vertical-align:top;padding:0.25em 0.5em;"| |
|class="hlist" style="vertical-align:top;padding:0.25em 0.5em;"| |
||
* [[Brazil]] |
* [[Brazil]] |
||
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:
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 |
||
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= |
+ | * [[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= |
+ | * 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. |
||
NEW DELHI: The government today informed the Lok Sabha that till date 11 states and union territories (UTs) have been declared open defecation free (ODF) ...
NEW DELHI: The government today informed the Lok Sabha that till date 11 states and union territories (UTs) have been declared open defecation free (ODF) ...
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) ...
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) ...
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) ...
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= |
+ | * [[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> |
||
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 ...
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 ...
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 ...
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= |
+ | * [[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 |
||
Read more of this story at Slashdot.
by TomaĹž Vajngerl (noreply@blogger.com) at January 31, 2018 11:10 AM
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.
The latest news and commentary on OpenDocument Format (ODF) aggregated from a variety of blogs and other online services.
Do you blog about ODF? Do you have feedback? Contact us with your thoughts.
Also, join the OpenDocument Format group on Diigo to contribute links directly to this planet.
An Antic Disposition
Apache OpenOffice Blog
Charles H. Schulz
DocXpresso
Gary McGath
Google News
HackerNews
Jos van den Oever
Kickstarter
OASIS
OASIS news
ODF Diigo Group
ODF Software Recipes
ODF Translator Team
ODF Wikipedia Page
OpenDocument.xml.org
Planet AbiWord
Planet KDE
Slashdot
The Document Foundation Planet
WebODF blog
WebODF news
digitaleoverheid.nl]
www.opendocsociety.org
January 24, 2019 05:06 AM UTC