The Document Foundation Planet

 

December 08, 2016

Cor Nouws

New LibreOffice comes with alternative for users of the Microsoft ribbon-interface

One of the big advantages of LibreOffice has been, for a long time, that it offered the well known menu based user interface to its users. Getting used to a ribbon was not necessary. However, currently there is a group users that is quite well used to a ribbon-interface. Now, for those too LibreOffice offers a solution: the Notebookbar!

Over the past one to two years LibreOffice worked on the concept of the Notebookbar. This finds its origin in work with Glade-designer for the user interface.

The Notebookbar itself also has multiple forms: Tabbed, Contextual Single and Contextual Groups. It can be activated if experimental features are turned on. It’s not clear yet what the status will be in the official 5.3-release (end of January).

LibreOffice now offers an ideal solution for people that prefer to work with either a menu, or with a side bar, or with a ribbon-based interface!

Settings

  • Tools > Options > LibreOffice General > Advanced … check Experimental features
  • View > Toolbar Layout > Default/Single toolbar/Sidebar/Notebookbar
  • View > Notebookbar > Tabbed/Contextual Single/Contextual Groups
  •   (activate from the setting Tabs the Menubar via the LibreOffice-icon top left)

    *) Info Glade-designer
    *) Download LibreOffice 5.3 bèta 1

    by Cor & OfficeBuzz (noreply@blogger.com) at December 08, 2016 11:47 AM

    Michael Meeks

    2016-12-08 Thursday.

    • Mail chew; really encouraged to see Kolab's lovely integration with Collabora Online announced and available for purchase. Wonderful to have them getting involved with LibreOffice, doing testing, filing and triaging bugs up-stream and so on, not to mention the polished marketing.

    December 08, 2016 10:52 AM

    December 07, 2016

    Official TDF Blog

    Advent Resource #7: Tutorials for Teachers by B.J. Poole

    pooleBernard John Poole has been an Associate Professor Emeritus of Computer Science, Education and Instructional Technology
    at the University of Pittsburgh at Johnstown, from 1996 to 2009.

    These tutorials for LibreOffice 5.x are designed to help pre-service and in-service teachers learn the suite of free productivity applications included in LibreOffice. But teachers at all levels who need to improve their skills in any of the LibreOffice applications will benefit from working their way through the tutorials. The tutorials are also being used effectively by people who are not teachers, as well as with elementary (5th grade up), middle school, and high school students.

    The tutorials, with skill consolidation exercises, cover the essential features of LibreOffice Writer (including mail merge), Calc (including formulas, graphing, charting and Lookup Tables), Base (including reporting), and Impress (including many of the relevant skills that apply to teachers) in the context of the teacher in the K-College classroom. They also include a lesson on LibreOffice Draw.

    by Italo Vignoli at December 07, 2016 09:00 PM

    Michael Meeks

    2016-12-07 Wednesday.

    • Prodded at mail, built ESC stats. Thrilled to have Collabora Online 2.0 released in conjunction with our partners. You can buy a LibreOffice based Collabora Online with collaborative editing and long term support now. We'll of course be releasing incremental improvements, updates and fixes approximately each month as we move forward. Thanks to all in the company & community - whose hard work & dedication made this possible.

    December 07, 2016 09:00 PM

    December 06, 2016

    Official TDF Blog

    Advent Resource #6: Getting Involved in Development

    downloadA step-by-step guide for new developers

    It is easy to be overwhelmed by the size and complexity of LibreOffice. The source is written in many different languages and formats — C, C++, Java, Bash, JavaScript, Python, Perl, SQL, Test, XML — and consist of roughly 102,000 files (excluding all localizations) with 36,000,000 lines of text (7,000,000 lines of source code).

    Nobody understands the whole code in detail, but we have many core developers who each know part of the code in detail. This step by step guide shows an easy way going from “wanting to contribute” to successfully have the first patch merged to master. If you want help or need more information, please do not hesitate to contact the developer mentoring lead.

    by Italo Vignoli at December 06, 2016 09:00 PM

    Michael Meeks

    2016-12-06 Tuesday.

    • To work early; mail chew; finance planning call with Tracie & Julie & latterly Kendy, lunch. Commercial call, wrote up notes, sync. with Philippe.

    December 06, 2016 09:00 PM

    Official TDF Blog

    Third Bug Hunting Session for LibreOffice 5.3

    bhs_5-3-0-beta2_largeLibreOffice 5.3 will be announced at the end of January 2017, with a large number of new features which are summarized on the release notes page: https://wiki.documentfoundation.org/ReleaseNotes/5.3. In order to find, report and triage bugs, the QA team is organizing a third bug hunting session on Friday, December 9, and Saturday, December 10, 2016.

    Tests will be performed on LibreOffice 5.3 Beta 2, which will be available on the pre-releases server (http://dev-builds.libreoffice.org/pre-releases/) in time for the event. Builds will be available for Linux (DEB and RPM), MacOS and Windows, and will run in parallel with the production version.

    Mentors will be available on December 9 and December 10, 2016, from 8AM UTC to 10PM UTC. Of course, hunting bugs will be possible also on other days, as the builds of LibreOffice 5.3.0 Beta 2 will be available until mid December.

    We would like to see the new font layout engine tested on MacOS in particular. Please drag all your MacOS friends and relatives into the testing effort! All details of the third bug hunting session are available on the specific wiki page: https://wiki.documentfoundation.org/QA/BugHuntingSession/5.3.0Beta2.

    During the dedicated sessions, we will concentrate all efforts to chase and reproduce the bugs, in order to confirm and file them in a more comprehensive way. Of course, the more comprehensive the bug report, the easier it will be for the developers to solve the bugs in time for the final release.

    by Italo Vignoli at December 06, 2016 12:01 PM

    December 05, 2016

    Official TDF Blog

    Advent Resource #5: LibreOffice Old Releases

    downloadLibreOffice uses a time-based release schedule, to produce the best quality free software. A time based release is one that does not wait for either features or bug fixes but is based (as much as possible) on time. This enforces discipline in introducing fixes, gives predictability, and allows more regular releasing. In addition, synchronizing a time-based release schedule with the wider free software ecosystem also offers huge advantages, by getting new features out to users as quickly as possible with a minimum of distribution cycle lag.

    As a result, users get new major version every six months with a wide range of features, fixes, and enhancements. In addition, they get many pure bugfix micro releases. The first X.Y.0 release is intended for early adopters. More conservative users are advised to wait for a later X.Y.Z bugfix release.

    TDF strongly suggests early adopters and tech savvy users to deploy the latest bleeding edge version (now LibreOffice 5.2.3, and soon LibreOffice 5.2.4), and more conservative individual users and enterprise users to deploy the longer tested previous version (LibreOffice 5.1.6, for enterprise users with the addition of professional support provided by the ecosystem). For testing and quality assurance purposes, though, the project maintains a repository of every older LibreOffice version: https://downloadarchive.documentfoundation.org/libreoffice/old/.

     

    by Italo Vignoli at December 05, 2016 10:42 PM

    Michael Meeks

    2016-12-05 Monday.

    • Mail chew; bug poke-age. Out to Colin Kavanah's funeral in Cambridge - a faithful and encouraging man of God; he will be missed. Played the Violin with Mick & John; to the wake for a fine lunch & to meet the family.
    • Back to work; customer call, TDF board call, dinner, put babes to bed, back to working on a contract.

    December 05, 2016 09:00 PM

    December 04, 2016

    Lera Goncharuk

    Command-line arguments in LibreOffice

    The last few weeks I've been doing a patch in the Help associated with the bug tdf#100836. It seems that there is a file that describes everything, and it need to only move into the code, but not everything is simple. First, this help appears in the console mode, and it had been very desolate. On Windows system, it opens in the window that does not have a scroll bar instead to show it in the console. Secondly, mistakes were found at the time of writing, and they should be corrected before placing in the Help. As a result, instead of a single patch was made already 3: I did two (1, 2) and one was done Mike Kaganski. And as a fact, it requires further improvement, but unfortunately, I already have tired from writing of it. And since this Help will appear only next summer in the LibreOffice 5.4, I give it here, as always, with minor explanations. I hope that someone else will improve this help to the release, and you can enjoy more good official Help.
    Read more »

    by Lera Goncharuk (noreply@blogger.com) at December 04, 2016 09:03 PM

    Michael Meeks

    2016-12-04 Sunday.

    • Up lateish; NCC - Tony spoke; back for lunch, relaxed through the afternoon. Julie over in the evening.

    December 04, 2016 09:00 PM

    December 03, 2016

    Eike Rathke

    Lesen! Big Data Psychometrik

    Es ist nicht so wie du denkst. Es ist schlimmer.
    Ich habe nur gezeigt, dass es die Bombe gibt über Psychometriken mit Hilfe von Big Data, den Big Five Persönlichkeitsdimensionen, das Ocean-Modell, und was die Strategic Communications Laboratories (SCL) und Cambridge Analytica mit Politmarketing, Microtargeting, Breitbart News und dem Brexit und Trump zu tun haben.

    Fake News war gestern, jetzt ist Dark Posts.

    by erAck (23@127.0.0.1) at December 03, 2016 07:47 PM

    >Marius Popa Adrian

    Firebird 3 by default in LibreOffice 5.4

    Lots of missing features & big bugs were fixed recently . All of the blockers that were initially mentioned on tracking bug are now fixed. Lionel mentioned that he added a few more blockers that needs to be fixed until Firebird will be switched by default : I went over https://bugs.documentfoundation.org/buglist.cgi?quicksearch=firebird and added a few open bugs to the blocker bug https://

    by Adrian Marius Popa (noreply@blogger.com) at December 03, 2016 03:30 PM

    Service for migrating Firebird 2.5 format to Firebird 3.0

    On Libreoffice Devel there is a thread about migration of the already created odb files with 2.5 databases inside (fdb) but also about the forward and backward compatibility of the Firebird backup archive (fbk). https://lists.freedesktop.org/archives/libreoffice/2016-November/075953.html Lionel added notes about upgrading in the wiki : People trade privacy for convenience or the other way

    by Adrian Marius Popa (noreply@blogger.com) at December 03, 2016 12:52 PM

    December 02, 2016

    Markus Mohrhard

    LibreOffice UI test tutorial (part 2): Improve the introspection library

    The last part of the UI test tutorial introduced the python part of the UI testing framework. In general most times you only need to care about the python part of the test but sometimes you actually need to extend the introspection part of the framework inside of the LibreOffice code. Many UI elements are already supported in the introspection library either directly or through one of its parent classes.

    This blog post will give a short summary of how the introspection code works and how support for new elements can be added. In contrast to the other three parts this blog post requires some understanding of the LibreOffice source code and an idea about VCL, our window toolkit.

    Overview

    The introspection library provides two simple UNO interfaces to the outside world. The XUITest interface provides access to static data in VCL. Currently this is limited to executing UNO commands and getting access to the current top level window. Access to this object is provided by UITestCase.xUITest in the python test code. In the future we might extend this interface to provide access to more VCL data that is not otherwise available and is useful for the UI testing.

    The more interesting one and the one that abstracts all the different UI objects is the XUIObject interface with the corresponding implementation on the LibreOffice side through UIObjectUnoObj, which just wraps a virtual class called UIObject.

    The two important methods are get_state and execute. The get_type and get_name methods should also be overridden but the other methods can often just be taken from the base class.

    Adding support for a new object

    For now we are just going to talk about UI elements that inherit from vcl::Window, so basically most of our GUI elements. On the introspection side the corresponding class is WindowUIObject, which provides the base class for all vcl::Window based introspection abstraction. All classes inheriting from vcl::Window provide the virtual method GetUITestFactory that returns a factory function for the introspection library.

    Adding support for a previously not well covered UI object – all have basic coverage through at least the WindowUIObject – normally requires three steps: First adding a GetUITestFactory method to the UI object class, secondly adding the corresponding factory method and finally implementing the introspection wrapper class.

    Most of the time the factory method just casts the passed in vcl::Window pointer to the correct type and create the introspection wrapper object. The actual work is in implementing the actual introspection class for the UI element, which should expose the properties that the tests need as well as the operations that can be done on the UI element.

    The inheritance from WindowUIObject or one of its subclasses already provides a number of properties as well as some common operations like typing text.

    An example for adding support for a previously unsupported object can be found at [1]. This one has a slightly more complicated factory method but does not add more than a basic property.

    Non vcl::Window UI objects

    Sometimes there are non-vcl::Window UI objects that need to be wrapped which makes everything a bit more complicated. Examples for this are e.g. tree lists or tables where we want to expose elements of the vcl::Window UI object like single tree entries as own objects. As these objects don’t correspond to actual UI objects in our code we have to employ some tricks to provide them to the introspection library. The basic idea behind supporting such pseudo objects is to hold a pointer to the corresponding vcl::Window based UI object through a VclPtr and a way to get the correct property that represents the object we want to cover. Additionally as these objects don’t have an ID we need to override the get_child and get_children methods inside of the the wrapper class for the vcl::Window. The get_children method should return all the IDs of descendants, and the get_child method should return for each of these IDs the corresponding wrapper object.

    Handling missing IDs

    As has been mentioned in the first part we identify UI elements through a locally unique ID. Normally this ID is loaded from the UI files that describe our dialogs. However for UI elements that are dynamically generated in the code we need to set the ID in the code. For this case the vcl::Window provides the set_id method.

    Next

    Hopefully this gave a short overview over the C++ part of the UI testing. The next tutorial will cover the directory layout of the python code together with some information about adding normal UNO code to the python tests.


    by Markus Mohrhard at December 02, 2016 02:51 AM

    December 01, 2016

    Lera Goncharuk

    Philosophical thinking about styles and templates, or "Where the iceberg basis is hidden?"

    Reading articles about working in LibreOffice on various websites, including blogs, I always meet with the lack of understanding, which makes these articles fit only for a basic use. However, for the office, and for people who often use LibreOffice and not want to think about how entry should be shown, but only what they are writing, the concept of styles and templates is very important. This article is not a lesson of use, but an attempt to give the rod, frame, idea, around which it will be possible to strengthen your knowledge. And I hope that it will help you to bring together existing and easier to accept new ones.
    Read more »

    by Lera Goncharuk (noreply@blogger.com) at December 01, 2016 08:42 PM

    Caolán McNamara

    Impress LibreOffice OpenGL Slide Transitions under Wayland via GTK3

    <iframe allowfullscreen="" frameborder="0" height="315" src="https://www.youtube.com/embed/mVVh_R7R2f8" width="560"></iframe>
    Impress LibreOffice OpenGL Slide Transitions under Wayland via GTK3 (GtkGlArea).

    So I've implemented enough to get this working on my machine now. I've demoed "static", "glitter" and "honeycomb" above from my -O0 debugging build. I'll work on merging this to master now, patches are in our gerrit instance. Porting from glew to epoxy is a necessary step, I know it builds on Windows and Mac, but that's utterly untested.

    by Caolán McNamara (noreply@blogger.com) at December 01, 2016 04:58 PM

    November 28, 2016

    Florian Effenberger

    LibreOffice am LinuxDay Vorarlberg 2016

    Jedes Jahr kurz vor Weihnachten, meistens am Samstag vor dem ersten Advent, findet in Dornbirn der LinuxDay Vorarlberg statt, der zahlreiche Besucher aus Deutschland, Österreich, der Schweiz und aus Liechtenstein anzieht.

    Auch LibreOffice war in diesem Jahr natürlich wieder mit einem eigenen Stand von der Partie, betreut von Robert, Alex, Lothar und mir. Neben der aktuellen LibreOffice-Version hatten wir auch Bücher, Broschüren, Flyer, Sticker, unseren Jahresbericht und zahlreiche weitere Materialien im Gepäck. Insbesondere die Kulis rissen uns die Besucher förmlich aus der Hand, manch einer nicht ohne die Frage, ob man damit auch im OpenDocument-Format schreiben kann. 😉

    Stefan hat zudem einen Workshop abgehalten, bei dem er Anwender in die Tiefen der Textverarbeitung eingeführt hat.

    <figure class="wp-caption aligncenter" id="attachment_291" style="width: 840px">LibreOffice-Stand am LinuxDay Vorarlberg 2016<figcaption class="wp-caption-text">LibreOffice-Stand am LinuxDay Vorarlberg 2016</figcaption></figure>

    Für mich gehört der LinuxDay zum Jahresausklang mittlerweile einfach dazu und ich bin jedes Jahr gerne in Dornbirn zu Gast. Vielen Dank an alle Organisatoren für euren großartigen Einsatz und eine tolle Veranstaltung und natürlich an alle Helfer am Stand für euer Engagement – es war ein toller Tag!

    Ich freu mich schon darauf, 2017 wieder in Dornbirn zu Besuch zu sein.

    by Florian Effenberger at November 28, 2016 08:05 AM

    November 27, 2016

    Andreas Mantke

    New Extensions And Templates Website On The Way

    I worked with a Plone service provider on the setup of a new LibreOffice extensions and templates website and the migration of the content from the current site to the new site. We are currently short before we will move over to the new website. The new site will contain extensions and templates. We will not have to Plone sites for this purpose. Thus LibreOffice extension or/and template contributors will need only one account in the future. We migrated the user account from the current sites to the new one too. Thus all contributors will be able to login with their current credentials to the new website.

    liboextensiontemplateshomepage

    Above the home page of the new LibreOffice extensions and templates website.

    liboextensiontemplatesextensionscenterAnd above the extension part of the new website.

    More news on the new LibreOffice extensions and templates website will follow here during the next days.

    by andreasma at November 27, 2016 06:11 PM

    November 25, 2016

    Tamas Zolnai

    New pivot table function in Calc: Median

    After have some work with a pivot table related performance issue, I've got a request to implement a new function for pivot tables. It seemed a useful feature to have and also an easy thing to implement at the first sight.

    Pivot table functions

    Pivot tables are used to analyse a larger amount of data using different statistic functions for that. Both LibreOffice Calc and Microsoft Office Excel have the same function palette with 11 functions like average, sum, count and so on. These aggregate functions can be used for data fields and for row/column fields. Data fields determines which source field would be summarized and which function would be used for that. Row/column fields don't have a function by default, but with setting one user can calculate subtotals too.

    Median

    Why median? In psychology research pivot tables can be a useful thing to analyze data of the participants. It depends on the type of the data which functions can be used for aggregation. When we have interval variables we can use average, but for ordinal variables we would need median, which was missing from the function list.

    This was the starting point, but I've also found some user posts about missing this feature from MS Excel (see links below). It seems Excel users had to face the very same problem again and again over the last ten years. Well, it has some advantages if a software is open source, I guess.

    Good news

    In LibreOffice 5.3, median is available for pivot tables:

    Thanks

    ... to my professor, Attila Krajcsi (Department of Cognitive Psychology, Eötvös Loránd University) for supporting the LibreOffice project, with the idea to have this new function and also with some course credits!

    by Zolnai Tamás (noreply@blogger.com) at November 25, 2016 11:31 PM

    Lera Goncharuk

    Protecting Content in LibreOffice Writer form unpremeditated changes

    On last week Mike Kaganski (one form Russian developers) asks me to correct a few things in the Help. In the fact, the speech was about addition a few strings in an article about protection of contents in LibreOffice Writer. But, when I started to work with the article, I understood that the article must be completely rewritten. I pushed the patch to gerryt. And I hope that the article will be available already in the Help of 5.3 version. In the blog, I would like to give additional explanations and at the same time to tell about some things which was not appropriate for the Help, in my opinion.
    Read more »

    by Lera Goncharuk (noreply@blogger.com) at November 25, 2016 10:22 PM

    David Ostrovsky

    Adding OAuth authentication scheme for Gerrit

    I gave a talk on last FOSDEM about Gerrit User Authentication. Here are the slides. It was a long and interesting journey to add OAuth authentication scheme support in Gerrit Code Review. Luca spent a lot of time trying to get GitHub OAuth support in Gerrit core. After almost 1 year work on this change and countless reviews and addressed comments (57 patch set) it was abandoned. But the work wasn’t in vane. The lessons learned form this attempt was:

    • There must be support for multiple authentication providers
    • Because of the nature of the OAuth providers, the support cannot be done in Gerrit core, and must be done as a plugin
    • To write a plugin extension point must be exposed first (tja, keine Arme, keine Kekse!)

    However, in the past there were quite some attempts to implement generic pluggable auth scheme extension point, but they all were abandoned. So it was more or less clear if we would revamp the attempt to introduce something totally generic it would require a lot of efforts and would take another couple of years of work. Instead we should try to add KISS extension point, just for OAuth. Sure, some folks in the wild were disappointed, because they would prefer to see a big generic pluggable auth extension point in Gerrit, but we just wanted to get the job done for this specific use case.

    Another thing to solve, after the extension point was extracted and plugin support for the following OAuth providers Google, GitHub, CAS and BitBucket was introduced, was OpenID providers. That why I also added Hybrid OAuth+OpenID auth scheme support.

    I would like to thank Norbert Thiebaud from The Document Foundation for invaluable help in many discussions we had during my work on Hybrid OAuth+OpenID authentication.

    by admin at November 25, 2016 12:58 AM

    November 23, 2016

    >Marius Popa Adrian

    Lionel Elie Mamane committed a patch related to this issue tdf#101789 : Firebird 3 - fails to build on OSX 10.11.x with clang

    Lionel Elie Mamane committed a patch related to this issue tdf#101789 Firebird 3 - fails to build on OSX 10.11.x with clang. It has been pushed to "master": tdf#101789 work around DYLD_LIBRARY_PATH limitations on newer MacOS X. An alternative fix has been in place ever since Stephan Bergmann commit " Allow external/firebird to be built with a custom SHELL under Mac OS X 10.11".

    by Adrian Marius Popa (noreply@blogger.com) at November 23, 2016 04:33 PM

    November 22, 2016

    >Marius Popa Adrian

    Bunth Tamás commited a few patches related to Firebird driver

    Tamás committed a patch related to tdf#74172 issue. Ensure prepared while setting numeric It has been pushed to "master": It will be available in 5.3.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected

    by Adrian Marius Popa (noreply@blogger.com) at November 22, 2016 04:32 PM

    November 20, 2016

    Mike Kaganski

    Integrating LibreOffice with SharePoint – part 2

    In my previous post, I discuss LibreOffice‘s CMIS integration with SharePoint. This post, as promised, is dedicated to WebDAV method of accessing SharePoint servers from LibreOffice.

    Basic WebDAV support is already present in LibreOffice, which inherits it from OpenOffice.org. You may put SharePoint URL into OS’s File Open dialog, and browse and open documents as if they were on local file system. But to claim SharePoint WebDAV support, LibreOffice should provide ease of use no less than its competitors.

    Existing users of MS Office are used to access the documents on SharePoint server using web browser integration. This allows to navigate to a document and open it in associated office program simply clicking on its link on web page, or using the page’s options to check-out document, open it for reading, etc. A document that is open this way isn’t downloaded by browser to be opened by application locally, but is open by office application via WebDAV, thus presenting easy way to work with document, including saving your work to proper place automatically. This integration is now available for all modern browsers (the level of feature support vary, though).

    sp-webdav1

    There are two mechanisms used to enable such integration. The first (and older) one is using ActiveX control/browser plugin. This method works for IE (classic mode) using OpenDocuments ActiveX control (and also used to work for Firefox and Chrome using NPAPI plugin, but since NPAPI was deprecated, it doesn’t work there anymore). In essence, a JavaScript click handler on the page instantiates the control, and then uses its methods to open the document with corresponding application in required mode. With all implied security considerations.

    The second (newer) method is using custom URI schemes. This requires that corresponding URI handler be registered in OS/browser, and the handler application be able to recognize these URIs and extract actual WebDAV URIs required to access the document on server from them.

    Both methods were lately addressed in LibreOffice development by Collabora Productivity. To implement first method, a custom ActiveX control was coded, and is now awaiting review on gerrit.

    To utilize SharePoint custom URIs, LibreOffice was taught to recognize MS Office’s existing custom URIs. This is required to allow using LibreOffice to open MS Office’s documents from SharePoint on those computers that don’t have MS Office installed. But that’s not enough; we should be able to treat ODF independently, e.g. to allow for configurations where both LibreOffice and MS Office co-exist on a workstation, and must handle their respective native formats. To achieve that, we introduced our own custom URI scheme, vnd.libreoffice.command. Now LibreOffice can accept any of these URIs, and successfully open the document in proper mode.

    But for LibreOffice to open them, these URIs must be passed to it from the SharePoint web page. We added registration of our own custom URI handler into installer for Windows OS, and also we now register LibreOffice as MS Office URIs handler if user chooses to register MS formats to open with LibreOffice.

    If you choose to use the second (custom URI) integration method, and you don’t need MS Office as handler for DOCXs, PPTXs etc., then you don’t need to configure your SharePoint server for that to work. All that you need is to install recent enough LibreOffice (v.5.3+), and configure it at installation time to open MS Office files.

    But if you choose either first method (ActiveX), or second method with coexisting LibreOffice/MS Office workstations, then you will need to configure SharePoint server for that. In both cases, you will need to edit DOCICON.xml file, that  may be found in server’s %ProgramFiles%\Common Files\Microsoft Shared\Web Server Extensions\XX\TEMPLATE\XML. This is an XML file, and we should edit sub-elements of ByExtension element. Such sub-element has the following syntax:

    <Mapping Key="odt" Value="icodt.png" EditText="LibreOffice" OpenControl="LOSPSupport.OpenDocuments" OpenApp="vnd.libreoffice.command"/>
    • Key = file extension
    • Value = icon file
    • EditText = Text on “Edit with application” UI button – required for edit option. Optional.
    • OpenControl = ActiveX OpenDocuments control name (currently IE 32-bit only). Optional.
    • OpenApp = custom URI scheme to handle this. Independent from and appears to have priority over OpenControl. Available in 2013 SP1. Optional.

    You should use either OpenControl or OpenApp, depending on which integration method you have chosen. Do it for those extensions that you want to be handled by LibreOffice. Of course, you should backup the file prior to modifying it.

    After you have made all necessary modifications, to activate the settings, you need to restart IIS. To do that, you may execute command iisreset from the server’s administrator command line.

    That’s it, if you did everything right, LibreOffice should now seamlessly integrate with SharePoint website, and be automatically launched when you choose to open files from there, without downloading the file to local machine first.

    This is the second of two posts that discuss the current state of SharePoint integration support in LibreOffice. Thank you for reading, and enjoy the best free office suite ever!


    by mikekaganski at November 20, 2016 04:13 PM

    November 17, 2016

    Lera Goncharuk

    SUM, AutoSum and some other secrets of LibreOffice Calc

    When I started to write this article, I thought it would be brief note for beginners. But in the process of writing, I found quite a lot of information that was illuminated within this theme. As a result, the article grew to pretty large size. And I hope that the material presented here will be useful not only to people beginning their way into Calc, but also for people who have long enjoyed a spreadsheet.


    Read more »

    by Lera Goncharuk (noreply@blogger.com) at November 17, 2016 03:08 PM

    November 14, 2016

    Naruhiko Ogasawara

    LibreOffice Kaigi 2016.12


    Short notice,

    We, Japanese LibreOffice community, are preparing the"LibreOffice Kaigi 2016.12" on 10th Dec. (Sat), the annual LibreOffice meetup in Japan.

    • Date/Time: 10th Dec. (Sat), 13:00-18:00 JST
    • Venue: Cybozu Inc. (Tokyo Nihonbashi Tower 27F, Nihonbashi, Tokyo)
    • Fee: free (NOT includes the party at the same night)

    The name of the event was renewed, from "LibreOffice mini Conference Japan", to emphasize it is not only "geographically local" but "language local."  "Kaigi" is a Japanese word means "conference" or "meeting."

    We will invite Mr. Franklin Weng, who leads Taiwan government's ODF / LibreOffice migration, as the keynote speaker.   We believe that his talk will be a perfect gift for Japanese LibreOffice users.

    The whole programs will be in Japanese (except the keynote; we will prepare the Japanese slide though), but of course, every non-Japanese speakers are welcome.

    We'll co-organize the party after the conference with Debian Japanese community; they'll also have a conference exact a same venue :).  And we'll have a HackFest on 11th Dec. (Sun) at the same venue.

    See you at Nihonbashi!

    by Naruhiko Ogasawara (noreply@blogger.com) at November 14, 2016 04:43 AM

    November 12, 2016

    Miklos Vajna

    LibreOffice session at DevTalks Jr.

    (via DevTalksRo)

    Today I gave a Getting involved with LibreOffice Online and Android session at DevTalks Jr, Bucharest. The event had two tracks in parallel, with a total attendees of about 200 developers.

    Some photos I took after the event are available.

    Thanks the organizers and sponsors for the great event! :-)

    November 12, 2016 03:22 PM

    November 11, 2016

    LibreOffice Design Blog

    Additions to LibreOffice

    Software in general is made for many users, one size fits none. Personal preferences have to be taken into consideration as well as different workflows with varying goals. The broader the scope the more features needs to be flexible making the product often bulky. And while configuration for a well-structured number of options adds satisfaction to the product it quickly can becomes a nuisance. This is not only true for fine-tuning of the appearance but also the workflow with templates, for instance.

    Get Hot New Stuff!

    Figure 1: External files as known from KDE’s ‘Get Hot New Stuff!’.

    Linux users know the solution from Gnome Look and, recently introduced, the KDE store that offers an easy way to enhance the user experience. Similarly to these platforms the idea of third-party software components enhancing an ordinary mobile phone has revolutionized the world. Google’s play store or the Apple’s app store integrated into iTunes are perfect examples.

    Integrated Extensions

    Extension Manager

    Figure 2: LibreOffice’ Extension Manager.

    LibreOffice offers today two sites for extensions and templates, being redesigned currently. The procedure requires to go to the extension manager (ctrl+alt+E) with options to add an extension via file on the local file system. Clicking the link to ‘get more extensions online’ opens the Internet browser that allows to search at the website and to download the file. Learn more at our help site.

    This procedure has obviously room for improvements. And that’s the goal of this posting, to make a proposal for a better integration of extensions into the daily work with LibreOffice.

    Issue

    • Extensions/Templates are installed in a laborious workflow that includes activities in the internet browser
    • The scope is limited to only extensions and templates
    • Simplicity first cannot be maintained with growing features and expanding options

    Requirements

    • Benjamin wants to browse the additions by name and author and get a short summary.
    • Benjamin wants to restrict the shown additions to the current context and the program version.
    • Benjamin wants to get information on the number of downloads and the average rating (or number of thumbs up) to find interesting additions.
    • Benjamin wants to see the number of comments with an option to read what other users think about this addition.
    • Benjamin wants to install new additions without any further interaction, at best without the need to restart the system. New additions have to integrate seamlessly into the program.
    • Benjamin wants to remove previously installed additions to keep the system clear.
    • Benjamin wants to up or down vote an addition and have the opportunity to comment, at best without the need to open the browser but he accepts this step.

    The following aspects regarding upload and distribution of extensions are out of scope here but should illustrate that different users have their stakes in the process.

    • Eve wants to upload additions in order to share what she made.
    • Eve wants to make sure that her extension is working by restricting it to a certain version.
    • Adrian wants to distribute additions for the users in his enterprise only.

    Mockup

    Mockup for the integrated extensions

    Figure 3: Mockup for the integrated extensions.

    Scope

    Typical scope is the personalization with icons (we offer only a limited number of icon sets to reduces the storage footprint), fonts (the idea has smuggled into the last posting about font management, here in figure 3 also illustrating the need to get forwarded sometimes), or various toolbar layouts (including the “legacy” layout in order to make users happy who want to stick to a familiar configuration).

    Also main and context menus (users can configure it but not easily), artwork and custom shapes (those are provided in extensions today), and almost every other feature can be made extendable.

    Discussion

    The proposal is to integrate extensions flawless into the program and to expand the scope. The user should find the interaction next to the place where the extension is going to be added, the list should be filtered by the required version and the current scope. Means to sort and find makes it easy to install the right object, which on the other hand requires voting (secured by email address or online account, or better simple technical measures).

    Of course, LibreOffice would still provide a good set of templates and extensions as not everyone is online. This idea is perfect suited for the Google Summer of Code, so best you join today and comment here.

    by The LibreOffice Design Team at November 11, 2016 02:44 PM

    >Marius Popa Adrian

    Bunth Tamás commited a patch for LibreOffice bug #74172 : use DECIMAL and NUMERIC data types

    Bunth Tamás commited  a patch for bug #74172 use DECIMAL and NUMERIC data types From the list a of Firebird integration blockers there are only a few left Listed blockers: bug 69949 - table editor should support the autoincrement bug 71009 - relationship management not implemented in GUI bug 71251 - Creating table from default choices via wizard fails bug 74019 - Any table or select

    by Adrian Marius Popa (noreply@blogger.com) at November 11, 2016 01:23 PM

    November 10, 2016

    Eike Rathke

    No.

    There was no pressure to take it down. Sometimes truth is blunt and needs to be said, but unnecessary to repeat it over and over again. (If you don't know what this is about: you missed it, don't worry.)

    by erAck (23@127.0.0.1) at November 10, 2016 11:42 AM

    November 09, 2016

    Eike Rathke

    You.Fucking.Idiots.

    People who voted D.T. in Alaska, Alabama, Arkansas, Arizona, Florida, Georgia, Iowa, Idaho, Indiana, Kansas, Kentucky, Louisiana, Michigan, Missouri, Mississippi, Montana, North Carolina, North Dakota, Nebraska, Ohio, Oklahoma, Pennsylvania, South Carolina, South Dakota, Tennessee, Texas, Utah, Wisconsin, West Virginia, Wyoming.

    by erAck (23@127.0.0.1) at November 09, 2016 08:40 AM

    November 07, 2016

    Jiri Eischmann

    OpenAlt 2016

    OpenAlt, a traditional open source conference in Brno, took place last weekend. I gave talks on Wayland and Flatpak, and organized a Fedora booth.

    logo-openalt-conference

     

    Originally, I planned to give a talk on Flatpak only, but then the organizers came to me if I could find someone who could give a talk on the status of Wayland because people ask for it. And because I couldn’t find anyone else, I had to do the talk myself. OpenAlt was promoted live on Czech Television (something like BBC) and the Wayland talk was featured as one of the hot talks for which people should attend OpenAlt.

    Both talks were in the main hall and both attracted quite a lot of people although Wayland was more popular in the end. Both topics also stirred quite a lot of interest and many people came to me afterwards to discuss the topics more in detail. LinuxEXPRES.cz has already released an article based on information from my Flatpak talk.

    There were other interesting desktop-related talks. Dan Vrátil, an ex-member of our team, gave a talk about the history of KDE and he ran the presentation on KDE 1 (in Fedora 25), so he literally went back in time🙂

    Jan Holešovský talked on LibreOffice Online and Katarina Brehens on LibreOffice adoption in Germany.

    Brno is a stronghold of Fedora mainly due to large presence of Red Hat, so OpenAlt is a lot about meeting our current users. We had some Fedora winter hats and t-shirts for them. Many users were happy to hear that Fedora 25 has much better and currently probably the best-among-distributions support for switchable graphics cards and much easier way to install nVidia drivers.

    I had an interesting chat with a guy from sledovanitv.cz, a local startup providing TV streaming. He mentioned that they originally wanted to install Fedora on their laptops, but WiFi didn’t work (missing Broadcom drivers) and they gave up. So we definitely have another major hardware PITA in line to fix.

    We also organized the 4th Linux Desktop Meetup. This time on Friday as “OpenAlt Edition”. And we had a special guest from Mozilla CZ who gave a talk on what’s going on in the Mozilla community. Some of the stuff was really exciting and Mozilla guys are interested in participating in future meetups even though they live in a different city.

    cwgczkkxcaqkgtc


    by eischmann at November 07, 2016 05:19 PM

    Stephan Bergmann

    LibreOffice.flatpak update

    New revisions of LibreOffice are routinely uploaded to http://www.libreoffice.org/download/flatpak/ by now. But things have changed slightly with the recent upload of LibreOffice 5.2.3:

    GNOME Software (at least the version available in Fedora 25 beta) can now handle .flatpak files, so throwing the downloaded LibreOffice.flatpak at it will allow you to install the flatpak onto your system without resorting to the command line. (Just remember, for now, to first install the GNOME 3.20 runtime as detailed at http://www.libreoffice.org/download/flatpak/, or GNOME Software might refuse to install the LibreOffice.flatpak with an odd error message like “Could not find ‘org.libreoffice.LibreOffice.destkop’”.)

    But for that to work the LibreOffice.flatpak had to be stripped down to advertise just a single application (a single org.libreoffice.LibreOffice.appdata.xml and a single org.libreoffice.LibreOffice.desktop). So when you have installed the flatpak, you’ll now only see a single application icon (the “generic” document icon) instead of the various sub-application icons for Writer, Calc, Impress, etc. (The upside being that you’ll thus no longer confuse your Linux distro’s LibreOffice installation with the flatpak one.) And opening new Writer, Calc, Impress, etc. documents still works from the “generic” application icon’s context menu.

    Another recent improvement is that flatpak’s xdg-desktop-portal (and GNOME-specific xdg-desktop-portal-gtk backend) is now available (again, at least in Fedora 25 beta), so that clicking on hyperlinks in LibreOffice documents (or requesting the LibreOffice online help, e.g. by pressing F1) will now forward those requests to your browser and open the links there.


    by stbergmann at November 07, 2016 03:47 PM

    November 04, 2016

    Björn Michaelsen

    LibreOffice 5.2.3 as snap from Day One

    Meist scheint manches auf den ersten Blick unmöglich.
    Manches ist es auch, doch es wäre tödlich, das selbst zu glauben solange noch nichts feststeht
    und die Party zu verlassen, bevor sie losgeht.

    — Die Sterne, Stell die Verbindung her

    Yesterday, two nice things happened: For one, LibreOffice 5.2.3 has been released and secondly Ubuntu Core 16 has been released. But beyond that, something in the middle between these two has happened: LibreOffice 5.2.3 has been released to the stable channel of the snap store at the same day. Now LibreOffice has been in the snap store for some time — and has also been on the stable channel since the Ubuntu 16.10 release. But this is the first time the LibreOffice snap is released in sync with The Document Foundation announcing the general availability of the final downloads. This was possible even though I was on vacation yesterday: LibreOffice snap packages are now being build on launchpad, which simplifies a lot, and launchpad can be asked to populate the edge channel of the store. This is making life very easy. Having smoketested the amd64 build from that channel before, to release LibreOffice 5.2.3 to the beta/candidate/stable channels too all I had to do was push three buttons on a web interface and it was available to all.

    Building on launchpad, I also had the opportunity to create builds for armhf and i386 along with the usual amd64 builds with little extra effort. If you are adventurous you are encouraged to test these builds too: Be aware though that these so far aren’t even smoketested, I havent looked at them at all yet, so use them at your own risk.

    All in all, this is great progress: LibreOffice 5.2.3 is available to users of Ubuntu 16.10 and Ubuntu 16.04 LTS as a snap on the day of the upstream release. And beyond that on all other distributions where snap is available — quite a few these days.

    Update: ICYMI here is how to get the LibreOffice snap: http://www.libreoffice.org/download/snap/ — although strictly speaking you dont need the --channel=beta option anymore now. I will fix that soon.


    by bmichaelsen at November 04, 2016 04:52 PM

    October 30, 2016

    Andreas Mantke

    Offene Verwaltung und offene Formate

    Das Land Nordrhein-Westfalen hat sich vor mehr als drei Jahren öffentlich auf den Weg zur offenen Verwaltung gemacht. Seitdem hat sich bereits einiges bewegt, wie auf dem OpenNRW-Kongress in dieser Woche im Landschaftspark Nord in Duisburg zu sehen und zu hören war. Auf der zentralen Plattform von OpenNRW, auf der auch offene Daten zur Verfügung gestellt werden, stellt man leider fest, dass weiterhin nicht alle Daten in einem offenen Datenformat zur Verfügung gestellt werden. So stellt beispielsweise das Ministerium für Arbeit, Integration und Soziales (MAIS) dort aktuell Daten zum Thema „Anteil abhängig Erwerbstätiger mit geringfügiger Beschäftigung“ in dem binären xls-Format bereit, wobei die Datei auch noch VBA-Makros enthält. Auch viele andere aktuelle Daten aus diesem Landesministerium werden in keinem offenen Datenformat angeboten. Damit werden leider unnötige Hürden für Bürger aufgebaut, die diese Daten nutzen, sich mit ihnen auseinandersetzen und an einer offenen Diskussion teilnehmen wollen. Gesteigert wird dies, wenn solche Dateien dann zusätzlich noch Makros oder ähnliches mit Funktionen enthalten.

    Auf dem Weg zur offenen Verwaltung ist es erforderlich, dass für alle Bereiche darauf gedrungen wird, dass Daten nur in offenen Dateiformaten bereit gestellt werden, damit jeder Bürger, egal wie viel Geld er für seine technische Ausstattung zur Verfügung hat oder ausgeben möchte, an dem gewünschten öffentlichen Dialog informiert teilhaben kann. Dazu könnte die OpenNRW-Plattform selbst einen Beitrag leisten, indem dort Daten nur in offenen Dateiformaten entgegen genommen und bereit gestellt werden.

    by andreasma at October 30, 2016 01:16 PM

    October 29, 2016

    Mike Kaganski

    Integrating LibreOffice with SharePoint – part 1

    LibreOffice is a productivity suite that is suited well for using in corporate environments with centralized document repositories, such as SharePoint. Of course, to use it there, program should offer required functionality in convenient fashion. So what is the current state of LibreOffice’s support for integration with SharePoint?

    LibreOffice has two ways to communicate with SharePoint servers:

    Lately, Collabora Productivity has made a number of improvements made to LibreOffice, and fixes for some existing problems, that made configuration and usage of both types of SharePoint integration more robust and easy.

    In this and the next post, I am discussing current status of support and the methods to setup (and limited usage examples) for both ways. This post is dedicated to CMIS, and the next one will be devoted to WebDAV.

    CMIS integration

    To use CMIS integration with SharePoint, you need to configure your SharePoint Server to offer the CMIS service, and add new CMIS service to LibreOffice.

    Configuring SharePoint Server for CMIS

    The following configuration steps are shown on a SharePoint Server 2013 instance taken as example.

    First, basic authentication should be enabled in SharePoint Central Administration.

    Go to Security, choose Specify authentication providers in General Security group:

    sp-auth1

    Choose required Web Application and click Zone that you want to configure, and enable Basic authentication:

    sp-auth2

    Of course, HTTPS should be enabled for proper security.

    Second, configure your site settings.

    Login to your site, go to Settings → Site settings and choose Manage site features in Site Actions group:

    sp-site1

    There you need to activate Content Management Interoperability Services (CMIS) Producer:

    sp-site2

    That’s it. Now it’s time to setup LibreOffice to access SharePoint via CMIS.

    Configuring LibreOffice for SharePoint CMIS access

    You will use LibreOffice’s Remote Files feature, that is accessible from Start Center, as well as from main menu:

    sp-lo1

    Click Add service and choose SharePoint 2013 as Type, replace with the address of your SharePoint site, supply SharePoint username and password, then click Refresh button to the right of Repository chooser, after which LibreOffice will connect SharePoint Server and populate the chooser with existing repositories:

    sp-lo2

    To make it easier to use the connection, you may put the directory you want to start from into the Root field, e.g. “/Shared Documents”. This will not prevent you to use other directories later.

    Now click OK and you will be prompted for password again. The username and password you entered at the previous step were used to get repositories list, so provide your credentials again. If you choose to save password at this stage, in case you didn’t yet saved passwords for web connections previously, LibreOffice will ask you to set Master Password that is used once per LibreOffice session:

    sp-lo3

    Entering this password first time you access any web connection with stored password, you will not be asked anymore for passwords until program closes. This password is separate from the site’s password, and should differ from it.

    Now you are able to navigate your SharePoint server documents, rename or delete them, open, edit and save back (or create new) each time you use the Remote Files feature or accessing last used files from the server. Here is how the Remote Files dialog looks like for a configured connection:

    sp-lo4

    LibreOffice will show you a warning if you have not checked out the document yet, and allows you to do that immediately:

    sp-lo5

    The Check-Out, Cancel Check-Out and Check-In functionality is also accessible from LibreOffice’s File menu. Checking in will bring the following window, where you may fill the required information for new version of the file:

    sp-lo6

    To see the file’s CMIS properties, you may use Properties window, also accessible from File menu. It has CMIS Properties tab, that allows to see and change those properties.

    That’s all I wanted to tell about LibreOffice integration with SharePoint using CMIS. The next post will cover WebDAW method to do (almost) the same.


    by mikekaganski at October 29, 2016 09:56 PM

    October 27, 2016

    Caolán McNamara

    Deckard and LibreOffice

    LibreOffice reuses the same ui format that gtk uses. This suggests that deckard could be used to preview translations of them.

    Testing this out shows (as above) that it can be made to work. A few problems though:

    1. We have various placeholder widgets which don't work in deckard because the widgets don't exist in gtk so dialogs that use them can't display as something falls over with e.g. "Invalid object type 'SvSimpleTableContainer'" I had hoped I'd get placeholders by default on failure.
    2. Our .po translation entries for the dialogs strings all have autogenerated msgctxt fields which don't correspond to the blank default of the .ui so the msgctxt fields have to be removed, then msguniq to remove duplicates, and the result can the be run through msgfmt to create a .mo that works with deckard to show web-previews

    by Caolán McNamara (noreply@blogger.com) at October 27, 2016 12:44 PM

    October 21, 2016

    LibreOffice Design Blog

    Dealing with Missing Fonts

    When documents are sent from one computer to the next or opened on the same computer in a different operating system, these documents may not look the same unless all the fonts used in the document are available on the other computer or operating system. For this reason, exporting documents as a PDFs is so popular as it renders the document exactly like how it would be printed without any reliance on fonts. This proposal attempts to provide users with a user friendly way in dealing with missing fonts.

    Open Notification

    The first step to fixing this issue is to notify users when they open a document that contains missing fonts and are being substituted. This can be achieved with LibreOffice’s existing infobar implementation, which is also used to notify a user that they are opening a read-only document. In order to limit the occurrence of this infobar to only when it is really needed, the infobar won’t appear when only metrically compatible fonts are being substituted, which LibreOffice bundles.

    Example on how the infobar could look in case of missing fonts.

    Figure 1: Example on how the infobar could look in case of missing fonts.

    The user has the option to dismiss the notice or click on the ‘View Font List’ button which opens the document properties dialog (or alternatively a completely new one). The dialog will lists all the fonts used in the document (both in styles and applied through direct formatting), as well as indicate which ones are missing and the font that it is being substituted with.

    Font Installation and Substitution

    The fonts used in a document can be considered general document information and therefore perfectly suited for the document properties dialog (File > Properties…). The dialog has a Font tab that only has the option to embed fonts into a document, so it can be enhanced by listing the fonts and their font substitutes. We made two mockups on how it can be presented, shown in figure 2.

    Two dialog variants of font substitution.

    Figure 2: Two dialog variants of font substitution.

    Both mockups display a font grid that lists all fonts in the document and gives an overview of which one are installed, which are being simulated due to a missing style of an installed font, or which font is being used as a substitute.

    In the left mockup, the font list identifies fonts that are not installed by having their names in italic. When a row is selected, an inline dropdown list appears in the substitution column and is populated with all installed fonts to provide a means to define another font to be used as a replacement. The sort order may be adjusted to what is going to be substituted. If the user wants to install an alternative font, they can click the ‘Install font’ button which opens a dialog that an access the extension site filtered for fonts (a proposal for a generic approach has been made and is in preparation for a blog post). Searching this list should be easy, here exemplified with “Comic”, and installing allows subsequently to select this font in the substitution table. (Not all fonts need to be hosted on the extensions site; links are sufficient to forward to the right place.)

    In the right mockup, the font list has an ‘Installed’ column to identify if a font is installed. When a row has been selected, a user can click the “Install” group button which opens a menu of items to install the missing font or an open source alternative. Linux users will also be able to install the original or alternative fonts through their package manager. The “Install All” menu item will iterate through the font list and install any missing fonts from their original sources. Additionally they can apply a different substitute font to the currently selected font grid row by clicking the ‘Apply substitute’ entry in the “Substitute” group button or replace all occurrences of a font with another font within the document with the “Replace font” entry.

    Behind the scenes

    In order to provide the necessary functionality to install a font and its alternative, as proposed in the right mockup, this functionality needs to reply on a configuration file. This configuration file will be XML based and will catalog fonts, their open source alternatives, and their download urls. The XML structure will possibly look like so.

    <font>
      <family>Times New Roman</family>
      <license>Proprietary</license>
      <style>serif</style>
      <bundled_with>Windows;Windows 3.1</bundled_with>
      <download_url>https://sourceforge.net/projects/corefonts/files/
        the%20fonts/final/times32.exe/download</download_url>
      <package>ttf-mscorefonts-installer</package>
      <substitute>
        <family>Liberation Serif</family>
        <metrical_compatible>Y</metrical_compatible>
        <download_url>http://downloadarchive.documentfoundation.org/
          libreoffice/old/fonts/liberation_serif.zip</download_url>
        <package>fonts-liberation</debian_package>
      </substitute>
    </font>

    Indication of Substitution

    Presently, the only visual indication in the font name combobox that a font is being substituted is that the font name is italic. There is another visual indicator in the form of additional text appearing in the tooltip, but this is easily ignored as the tooltip only appears for a second before the control is clicked.

    Figure 3In order to better indicate the substitution of the font, we have to make a bigger change to the displayed text, like changing it to red (tdf#96872), and also indicate the font that is being used for the substitution, both in the font name and the tooltip (tdf#61134).

    Figure 3b

    Fonts being substituted may get indicated better in future by either a highlight color or using an icon. Or both.

    Figure 3: Fonts being substituted may get indicated better in future by either a highlight color or using an icon. Or both.

    Figure 4Similar to the toolbar, the Font tab found in the character and style dialogs also need improvements. The text labels ‘This font style will be simulated or the closest matching style will be used.’ and ‘This font has not been installed. The closest available font will be used.’ that appear under the font family drop down listboxes in the dialogs need clearer indication than simply being in the same simple style as when it says ‘The same font will be used on both your printer and your screen’. Either the text style needs to be changed (italics, bold, or red) or a warning icon would appear at its start.

    Conclusion

    The styling of text with the use of fonts has been around since the invention of the Graphical User Interface (GUI) and thanks to the availability of the internet, documents with styled text are being seen and shared on an ever growing daily basis, so we need to make it easy for users to see the documents they open in the same format that the author created them in.

    <noscript>Take Our Poll</noscript><script type="text/javascript"> (function(d,c,j){if(!d.getElementById(j)){var pd=d.createElement(c),s;pd.id=j;pd.src='https://design.blog.documentfoundation.org/wp-content/plugins/polldaddy/js/polldaddy-shortcode.js';s=d.getElementsByTagName(c)[0];s.parentNode.insertBefore(pd,s);} else if(typeof jQuery !=='undefined')jQuery(d.body).trigger('pd-script-load');}(document,'script','pd-polldaddy-loader')); </script>

     

    by The LibreOffice Design Team at October 21, 2016 08:13 PM