Bug Hunting Session
Bug 119871 - New feature “spell out” numbering doesn't work on Linux (Vanilla)
Summary: New feature “spell out” numbering doesn't work on Linux (Vanilla)
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.1.1.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-14 08:10 UTC by RGB
Modified: 2019-12-10 20:52 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments
Screenshot showing behaviour (60.98 KB, image/png)
2018-12-03 12:07 UTC, noreply+666192134234234
Details

Note You need to log in before you can comment on or make changes to this bug.
Description RGB 2018-09-14 08:10:14 UTC
This is a follow up of issue 118261

The new feature introduced in LibO 6 to "spell out" numbering still does not work on Linux.

For chapter numbering, when using "1º, 2º, 3º..." I obtain instead

   Ordinal-number 1

When using "Uno, Dos, Tres..." I obtain instead

   1

When using "Primero, Segundo, Tercero..." I obtain instead

   Ordinal 1

Tested with vanilla build in openSUSE Leap 15.0. I've also tested

6.2.0.0.alpha0+
Build ID: 18c5089df091bddeb8c2dc339776671964389040

with same results.
Comment 1 Mike Kaganski 2018-09-14 08:16:15 UTC
Not reproducible with ppa Version: 6.1.1.2
Build ID: 1:6.1.1~rc2-0ubuntu0.18.04.1~lo3
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 
Locale: en-US (en_US.UTF-8); Calc: group threaded

- so it must be a packaging problem.

Christian, could you please take a look?
Comment 2 RGB 2018-09-30 14:35:14 UTC
I confirm it's a packaging problem: the feature works with openSUSE Leap builds(1), but not with the vanilla builds: it fails on both 6.1.x and 6.2 alpha.

(1) http://download.opensuse.org/repositories/LibreOffice:/6.1/
Comment 3 László Németh 2018-10-10 06:34:43 UTC
(In reply to RGB from comment #2)
> I confirm it's a packaging problem: the feature works with openSUSE Leap
> builds(1), but not with the vanilla builds: it fails on both 6.1.x and 6.2
> alpha.
> 
> (1) http://download.opensuse.org/repositories/LibreOffice:/6.1/

By Suse developer Tomáš Chvátal (tchvatal at suse.com), a configuration option was added to libnumbertext to use regex support of system Boost instead of the native C++11 regexes, so maybe this is the background of the difference.

The upcoming C++ compiler update of the TDF builds will solve the missing C++11 regex support of the vanilla builds, too.
Comment 4 Xisco Faulí 2018-11-12 12:05:57 UTC
Moving to NEW as per comment 2

I think 6.2 uses the updated C++ compiler but I don't know about 6.1...
Comment 5 noreply+666192134234234 2018-12-03 12:07:20 UTC
Created attachment 147237 [details]
Screenshot showing behaviour
Comment 6 noreply+666192134234234 2018-12-03 12:09:35 UTC
Hi,

I have this problem, too, in LO Writer in LO version 6.1.3.2, which I downloaded yesterday from LO's web site, on my Debian 9.6 system.

Before I installed LO in version 6.1.3.2 on my machine, I removed the older LO version 5.x from the installed deb-packages. Version 5.x is part of the repositories of Debian version 9.x.

I noticed this behaviour when I wanted to create numbered entries in a table of contents.

So every entry in the TOC should look like "<Number 1> <Entry 1 in TOC>" and so on, corresponding to the appropriate <heading 1> in the text, and so on.

Instead, the TOC shows "Ordinal-number 1 Ordinal-number 1 Ordinal-number 1 Ordinal-number 1 Ordinal-number 1" in front of <entry 1>, "Ordinal-number 2 Ordinal-number 2 Ordinal-number 2 Ordinal-number 2 Ordinal-number 2" in front of <entry 2> and so on.

What did I do?

1. I created headings in my text by assigning the styles "Heading 1" and "Heading 2" to them.

2. I created a TOC

Everything is fine until here.

3. I opened Tools > Chapter Numbering, there I only edited the settings for level 1, i.e. there I only set the field "Number" to "1st, 2nd, 3rd" and clicked OK.

4. I updated the index of the TOC.

The result is the behaviour which I described above.

Regards,

Jens
Comment 7 noreply+666192134234234 2018-12-09 07:16:25 UTC
Update:

I am using Debian "Stretch" (stable release, version 9.6). 

The above-mentioned programme libnumbertext which probably would resolve the issue on my machine is not available as a Debian package for the currently stable release of Debian.

But libnumbertext is part of the Debian package python3-num2words (0.5.6-1), which is available for the currently unstable Debian release "Sid":

https://packages.debian.org/sid/python3-num2words

The Python section of all available Debian packages for the stable Debian release "Stretch" does not contain the package python3-num2words:

https://packages.debian.org/stable/python/

So I have to wait until appr. 2021 to resolve the issue reported in this bug entry. Then the currently unstable release "Sid" probably will have become stable, refer to: 

https://wiki.debian.org/DebianReleases

I do not like to use testing and unstable Debian releases.

By the way, as far as I can remember the behaviour described in this bug entry also occurs in LO version 5.x which is part of the Debian repositories for the stable Debian release 9.x

Regards,

Jens
Comment 8 QA Administrators 2019-12-10 04:09:05 UTC Comment hidden (obsolete)
Comment 9 RGB 2019-12-10 20:52:17 UTC
It's now working on both, 6.3.3.2.0 and 6.4.0.0.beta1