Bug 127951 - PARAGRAPH TABS: Writer doesn't align numbers whose digits have been grouped using the apostrophe character
Summary: PARAGRAPH TABS: Writer doesn't align numbers whose digits have been grouped u...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.3.2.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Tab-Stops
  Show dependency treegraph
 
Reported: 2019-10-03 13:47 UTC by William Gathoye
Modified: 2024-12-05 03:12 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Screenshot in Writer (LibreOffice 6.3.2) Arch Linux KDE Plasma 5 (58.90 KB, image/png)
2019-10-03 13:49 UTC, William Gathoye
Details

Note You need to log in before you can comment on or make changes to this bug.
Description William Gathoye 2019-10-03 13:47:08 UTC
Description:
While the SI/ISO 31-0 norm seems to standardize digit grouping around non breaking space, standard space or no space at all, some countries like Switzerland is still widely using non standard characters to group them like the apostrophe.

While we could think this is a corner case, in practice, this isn't. In Calc for example, the default character used to group digits in a number is still defined to the apostrophe when French (Switzerland) is chosen.

Steps to Reproduce:
1. Set the document to the French language (or any other language actually, the problem is the same with other languages as well).
2. Type 1'250.60
3. Via Format > Paragraph..., add a tabulation whose type is set to "Decimal".
4. Press the Tab key to align the number you typed to the tabulation you defined.

Actual Results:
Realize the number is not aligned at the decimal separator, but rather at the apostrophe

Expected Results:
The number aligned at the decimal separator


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 William Gathoye 2019-10-03 13:49:25 UTC
Created attachment 154734 [details]
Screenshot in Writer (LibreOffice 6.3.2) Arch Linux KDE Plasma 5
Comment 2 Dieter 2020-02-28 07:39:23 UTC
I confirm it with

Version: 6.3.5.2 (x64)
Build-ID: dd0751754f11728f69b42ee2af66670068624673
CPU-Threads: 4; BS: Windows 10.0; UI-Render: Standard; VCL: win; 
Gebietsschema: de-DE (de_DE); UI-Sprache: de-DE
Calc: threaded
Comment 3 Dieter 2022-12-05 16:02:56 UTC
Still present in

Version: 7.4.3.2 (x64) / LibreOffice Community
Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890
CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: CL
Comment 4 QA Administrators 2024-12-05 03:12:23 UTC
Dear William Gathoye,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug