Bug ID: 61467
Summary: The new LO 4.0 "splash" pages could benefit from NL
The text on the LO 4.0 "splash" pages of the libreoffice.org website could use
revision for grammatical content in English. These pages appear to be have been
translated from another language and do not scan smoothly.
As these pages serve as very prominent marketing tools for LO, I think that we
should fine-tune them for each NL whenever possible.
Below are some noticeable changes brought by this version and you can get the
full list in the release notes.
You'll find several of our most important improvements listed below. For a full
list of changes, please peruse the Release Notes.
Gerrit is used for our code review and easy contribution --- close to 1500 code
changes reviewed and merged with it!
We now use Gerrit for both code contributions and code review -- we've reviewed
and merged nearly 1500 changes with this invaluable tool!
Conversion with non-natives formats, like RTF or DOCX have significantly
We've significantly improved our support for non-native formats such as RTF and
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe instructions: E-mail to email@example.com
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/website/
All messages sent to this list will be publicly archived and cannot be deleted
- [libreoffice-website] [Bug 61467] New: The new LO 4.0 "splash" pages could benefit from NL copy editing · bugzilla-daemon
Impressum (Legal Info)
: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (MPLv2
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our trademark policy