[Libreoffice-commits] core.git: Branch 'distro/mimo/mimo-6-1' - mimo+linagora.png README.md
Andrés Maldonado (via logerrit)
logerrit at kemper.freedesktop.org
Wed Jul 17 09:01:16 UTC 2019
README.md | 176 ++++++++++++++++--------------------------------------
mimo+linagora.png |binary
2 files changed, 54 insertions(+), 122 deletions(-)
New commits:
commit 6322b2abbf1187ad0026c1834295a0caa353b5c9
Author: Andrés Maldonado <amaldonado at linagora.com>
AuthorDate: Wed Jul 17 10:55:16 2019 +0200
Commit: Jean-Sebastien BEVILACQUA <jsbevilacqua at linagora.com>
CommitDate: Wed Jul 17 11:00:17 2019 +0200
Replace README.md
Change-Id: I908d3050718d82e56743318af84f06662563a596
diff --git a/README.md b/README.md
index c59f68122473..9cfaabb4d5b2 100644
--- a/README.md
+++ b/README.md
@@ -1,122 +1,54 @@
-# LibreOffice
-[![Coverity Scan Build Status](https://scan.coverity.com/projects/211/badge.svg)](https://scan.coverity.com/projects/211) [![CII Best Practices](https://bestpractices.coreinfrastructure.org/projects/307/badge)](https://bestpractices.coreinfrastructure.org/projects/307)
-
-LibreOffice is an integrated office suite based on copyleft licenses
-and compatible with most document formats and standards. Libreoffice
-is backed by The Document Foundation, which represents a large
-independent community of enterprises, developers and other volunteers
-moved by the common goal of bringing to the market the best software
-for personal productivity. LibreOffice is open source, and free to
-download, use and distribute.
-
-A quick overview of the LibreOffice code structure.
-
-## Overview
-
-You can develop for LibreOffice in one of two ways, one
-recommended and one much less so. First the somewhat less recommended
-way: it is possible to use the SDK to develop an extension,
-for which you can read the API docs [here](https://api.libreoffice.org/)
-and [here](https://wiki.openoffice.org/wiki/Documentation/DevGuide).
-This re-uses the (extremely generic) UNO APIs that are also used by
-macro scripting in StarBasic.
-
-The best way to add a generally useful feature to LibreOffice
-is to work on the code base however. Overall this way makes it easier
-to compile and build your code, it avoids any arbitrary limitations of
-our scripting APIs, and in general is far more simple and intuitive -
-if you are a reasonably able C++ programmer.
-
-## The build chain and runtime baselines
-
-These are the current minimal operating system and compiler versions to
-run and compile LibreOffice, also used by the TDF builds:
-
-* Windows:
- * Runtime: Windows 7
- * Build: Cygwin + Visual Studio 2015 Update 3
-* macOS:
- * Runtime: 10.9
- * Build: 10.12 + Xcode 8
-* Linux:
- * Runtime: RHEL 6 or CentOS 6
- * Build: GCC 4.8.1 or Clang
-* iOS (only for LibreOfficeKit):
- * Runtime: 11.3 (only support for newer i devices == 64 bit)
- * Build: Xcode 9.3 and iPhone SDK 11.3
-
-At least Clang 3.4.2 is known to be too old to pass the configure.ac check "whether $CXX supports
-C++17, C++14, or C++11" in its current form (due to the #pragma GCC diagnostic ignored "-Wpragmas"
-that it does not understand).
-
-If you want to use Clang with the LibreOffice compiler plugins, the minimal
-version of Clang is 3.8. Since Xcode doesn't provide the compiler plugin
-headers, you have to compile your own Clang to use them on macOS.
-
-You can find the TDF configure switches in the distro-configs/ directory.
-
-To setup your initial build environment on Windows and macOS, we provide
-the LibreOffice Development Environment
-([LODE](https://wiki.documentfoundation.org/Development/lode)) scripts.
-
-For more information see the build instructions for your platform in the
-[TDF wiki](https://wiki.documentfoundation.org/Development).
-
-## The important bits of code
-
-Each module should have a `README` file inside it which has some
-degree of documentation for that module; patches are most welcome to
-improve those. We have those turned into a web page here:
-
-https://docs.libreoffice.org/
-
-However, there are two hundred modules, many of them of only
-peripheral interest for a specialist audience. So - where is the
-good stuff, the code that is most useful. Here is a quick overview of
-the most important ones:
-
-Module | Description
-----------|-------------------------------------------------
-sal/ | this provides a simple System Abstraction Layer
-tools/ | this provides basic internal types: 'Rectangle', 'Color' etc.
-vcl/ | this is the widget toolkit library and one rendering abstraction
-framework | UNO framework, responsible for building toolbars, menus, status bars, and the chrome around the document using widgets from VCL, and XML descriptions from */uiconfig/* files
-sfx2/ | legacy core framework used by Writer/Calc/Draw: document model / load/save / signals for actions etc.
-svx/ | drawing model related helper code, including much of Draw/Impress
-
-Then applications
-
-Module | Description
-----------|-------------------------------------------------
-desktop/ | this is where the 'main' for the application lives, init / bootstrap. the name dates back to an ancient StarOffice that also drew a desktop
-sw/ | Writer
-sc/ | Calc
-sd/ | Draw / Impress
-
-There are several other libraries that are helpful from a graphical perspective:
-
-Module | Description
-----------|-------------------------------------------------
-basegfx/ | algorithms and data-types for graphics as used in the canvas
-canvas/ | new (UNO) canvas rendering model with various backends
-cppcanvas/ | C++ helper classes for using the UNO canvas
-drawinglayer/ | View code to render drawable objects and break them down into primitives we can render more easily.
-
-## Rules for #include directives (C/C++)
-
-Use the `"..."` form if and only if the included file is found next to the
-including file. Otherwise, use the `<...>` form. (For further details, see the
-mail [Re: C[++]: Normalizing include syntax ("" vs
-<>)](https://lists.freedesktop.org/archives/libreoffice/2017-November/078778.html).)
-
-The UNO API include files should consistently use double quotes, for the
-benefit of external users of this API.
-
-
-## Finding out more
-
-Beyond this, you can read the `README` files, send us patches, ask
-on the mailing list libreoffice at lists.freedesktop.org (no subscription
-required) or poke people on IRC `#libreoffice-dev` on irc.freenode.net -
-we're a friendly and generally helpful mob. We know the code can be
-hard to get into at first, and so there are no silly questions.
+# LibreOffice - MIMO version
+
+
+<img src="mimo+linagora.png" alt="mimo+linagora" width="600"/>
+
+This is the [MIMO](https://www.journal-officiel.gouv.fr/mimo/) version of LibreOffice, developed by [LINAGORA](https://linagora.com/).
+
+## Download
+
+We make Windows builds in 32 and 64 bits.
+
+The most recent version reviewed by MIMO can be downloaded at <https://www.mim.ovh/mimo/>
+
+
+## Release notes
+
+### `6.1.6.3.M11`
+
+* Revert `tosca#24996: Recolor the shadow in the renderer`: the patch generated regressions
+* Fix [acim#1404: Publipostage et Barre d'outils Mailing (problématique numérotation)](https://acim.08000linux.com/issues/1404) by reverting:
+ - `tdf#121606: displaying Mail Merge toolbar shouldn't activate connection`
+ - `tdf#121607 defer other requests until password dialog is dismissed`
+
+### `6.1.6.3.M10`
+
+* `acim#1271: Fix publipostage` replaced by a fix from upstream: `tdf#122198 don't remove db after close`
+* `tosca#24347: Pb ombrage dans impress` replaced by `tosca#24996: Recolor the shadow in the renderer`
+
+### `6.1.6.3.M9`
+
+MIMO doesn't yet want to switch to LibreOffice `6.2.x`. They want the patches from Fiducial in a `6.1.x` version, excluding the patch for acim#1133 #1290 and #1311: <https://acim.08000linux.com/issues/1311#note-19>. Therefore we can't ship the same version to MIMO and to the other clients.
+
+**Patches from `6.1.5.2.M8` (MIMO):**
+
+* `acim#1026: Fix with commit af11abf3`
+ - Cherry-picked
+* `acim#1271: Fix publipostage`
+ - Cherry-picked
+* `acim#910: Fix text color when printing`
+ - Cherry-picked
+* `ACIM1319: Clean SQL string`
+ - Cherry-picked
+
+**Patches from `6.2.3.2` (Fiducial):**
+
+* `tdf#124824 FILEOPEN: Error rendering page break between two tables in a RTF`
+ - Cherry-picked
+* `tosca#24347: Fix shadow impress` and `tosca#24347: Fix shadow impress 2/2`
+ - Cherry-picked
+ - Squashed into `tosca#24347: Pb ombrage dans impress`
+* `tosca#24253: souci décalage RTF sous Writer`
+ - Cherry-picked
+* Patches related to acim#1133 #1290 and #1311
+ - Not cherry-picked
diff --git a/mimo+linagora.png b/mimo+linagora.png
new file mode 100644
index 000000000000..e633a793c04a
Binary files /dev/null and b/mimo+linagora.png differ
More information about the Libreoffice-commits
mailing list