Hi, Cor,
Cor Nouws <oolst@nouenoff.nl> ezt írta (időpont: 2018. szept. 12., Sze,
22:43):
Hi László,
Németh László wrote on 03-05-18 18:57:
LibreOffice 6.1 will support “spell out” numbering styles of OOXML (One,
Two...; First, Second..., 1st, 2nd...),
as you can see in the following screen cast (only English, French and
German examples):
https://youtu.be/c0j4Sjie8t4 <https://youtu.be/c0j4Sjie8t4>
My questions to the native language speakers:
1. Are these numbers correct in your language?
LibreOffice Versie: 6.1.0.3
Build ID: efb621ed25068d70781dc026f7e9c5187a4decd1
CPU-threads: 4; Besturingssysteem: Linux 4.15; UI-render: standaard;
VCL: gtk2;
Locale: nl-NL (nl_NL.UTF-8); Calc: group threaded
The numbering styles appear fine in the list 'Number'
But the result in the document is broken/wrong.
Such as Ordinal 1, Ordinal 2... and not 1e / eerste, 2e / tweede, etc.
What is the status of this currently?
Missing data file installation was fixed on Windows, so version 6.1.1 will
work well on it, see
https://bugs.documentfoundation.org/show_bug.cgi?id=118261.
But it's possible, this won't fix the problems of the TDF build on Linux.
That uses older GCC, unfortunately, without the requested C++11 regex
support, so it's possible, only LibreOffice versions packaged by the recent
Linux distributions will show "spell out" numbering correctly for a while.
Maybe it's worth to change the fall-back formats of ordinal and ordinal
indicator numbers to simple numbers, as in the case of the cardinal
numbers, to avoid to show "ordinal 1" or "ordinal-number 1" in TDF builds.
What is your opinion?
Best regards,
László
Cheers,
Cor
You can check here, too: https://numbertext.github.io/
index.html#testimonials
2. Do we need to change the default format etc. according to the normal
usage of your country/language variant?
For example, in the recent implementation, British English and American
English differ with the “and”
101 -> “One hundred and one”: en-AU, en-GB, en-IE, en-NZ
101 -> “One hundred one”: en-US etc.
3. Is it enough to support only a single gender in Spanish etc. languages
to cover common outline and page number usage in publishing?
Book/Part/Chapter/Section/Page/Paragraph One, or simply One (normal usage
in English outline numbering)
First Book/Part/Chapter/Section/Page/Paragraph (less common in English,
but
default numbering styles cover this, too)
Note: there is a plan to use similar spell out formats in currency and
date
formats of Writer, typical in contracts and invoices in several
languages. These formats are only supported in Calc yet by the NUMBERTEXT
Calc extension (or also in Writer macros via the new
com.sun.star.linguistic2.NumberText
service).
Best regards,
László
P.S: A recent question (comes from Rene Engelhard) for Hebrew
contributors:
Is the Hebrew correct in the next line of resource file of the Numbertext
Calc extension:
<name lang="he">NUMBERTEXT() וMONEYTEXT() פונקציות גליון Calc</name>
--
Cor Nouws
GPD key ID: 0xB13480A6 - 591A 30A7 36A0 CE3C 3D28 A038 E49D 7365 B134 80A6
- vrijwilliger https://nl.libreoffice.org
- volunteer https://www.libreoffice.org
- Member Board The Document Foundation
- http://www.nouenoff.nl / https://www.mijnclouoffice.nl
--
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/l10n/
Privacy Policy: https://www.documentfoundation.org/privacy
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: 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.