Bug 165799 - Issue with Decimal and Thousand Separators in PDF Export
Summary: Issue with Decimal and Thousand Separators in PDF Export
Status: RESOLVED DUPLICATE of bug 158251
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2025-03-18 09:06 UTC by matthias.hein
Modified: 2025-11-21 12:23 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
The original ODT-File (22.82 KB, application/vnd.oasis.opendocument.text)
2025-03-18 09:10 UTC, matthias.hein
Details
The exported PDF-File (51.81 KB, application/pdf)
2025-03-18 09:10 UTC, matthias.hein
Details

Note You need to log in before you can comment on or make changes to this bug.
Description matthias.hein 2025-03-18 09:06:17 UTC
Description:
I have created a document with form fields in LibreOffice, including numeric fields with decimal places. When I export this form as a fillable PDF, the decimal places are separated by a dot and the thousand places by a comma. In LibreOffice, the separation is correctly done with a comma for decimal places and a dot for thousand places. It seems that the formatting changes during the export process. I created a similar form a few years ago, and it worked perfectly back then.


Thank you for your assistance in resolving this issue.

Steps to Reproduce:
Create a document with numeric form fields in LibreOffice.
Set the numeric fields to use a comma for decimal places and a dot for thousand places.
Export the document as a fillable PDF.
Open the exported PDF and check the formatting of the numeric fields.


Actual Results:
The numeric fields in the exported PDF use a dot for decimal places and a comma for thousand places.

Expected Results:
The numeric fields in the exported PDF should use a comma for decimal places and a dot for thousand places, as set in LibreOffice.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
LibreOffice Version: 24.8.5.2 (X86_64)
Operating System: Win11Home 24H2 26100.3476
Language Settings: German
Comment 1 matthias.hein 2025-03-18 09:10:02 UTC
Created attachment 199859 [details]
The original ODT-File
Comment 2 matthias.hein 2025-03-18 09:10:59 UTC
Created attachment 199860 [details]
The exported PDF-File

The numeric fields in the exported PDF should use a comma for decimal places and a dot for thousand places, as set in LibreOffice.
Comment 3 Sarah Lim 2025-11-20 13:00:22 UTC
Testing on builds as early as 7.0 shows that Writer does not retain the locale formatting of numeric fields when exporting to PDF. There are values in the fields but the exported PDF shows blank. Though users can edit and still able to type commas as decimal separators or in other formats.
Version: 7.0.7.0.0+ (x64)
Build ID: 626ea4e62a3e5005fe9825923a1c0c5bdb61cc08
CPU threads: 12; OS: Windows 10.0 Build 26100; UI render: Skia/Raster; VCL: win
Locale: de-DE (en_FI); UI: en-US
Calc: threaded

In version 7.3, the exported PDF has the values in the fields but also did not show the correct format. Users could still edit and enter numbers in any format. 
Version: 7.3.8.0.0+ (x64) / LibreOffice Community
Build ID: e1ad83ddb2f39419fb5d7c69eba51e2b9f49c788
CPU threads: 12; OS: Windows 10.0 Build 26100; UI render: Skia/Vulkan; VCL: win
Locale: de-DE (en_FI); UI: en-US
Calc: threaded

In more recent builds (7.4 and later), the exported PDF also does not reflect the correct format but numeric fields now enforce stricter validation, rejecting commas as decimal separators.
Version: 7.4.8.0.0+ (x64) / LibreOffice Community
Build ID: f8ba7c6f77497e2dc7bfef8378511e2074ce01f9
CPU threads: 12; OS: Windows 10.0 Build 26100; UI render: Skia/Vulkan; VCL: win
Locale: de-DE (en_FI); UI: en-US
Calc: threaded

It appears that even in previous versions Writer did not preserve the numeric locale formatting in PDF exports.
Comment 4 Buovjaga 2025-11-21 12:23:31 UTC

*** This bug has been marked as a duplicate of bug 158251 ***