Bug 158251 - Export the form as a PDF and thousands separators appear
Summary: Export the form as a PDF and thousands separators appear
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Printing and PDF export (show other bugs)
Version:
(earliest affected)
7.4.0.0 alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, regression
Depends on:
Blocks: Form-Controls
  Show dependency treegraph
 
Reported: 2023-11-16 22:49 UTC by Roger
Modified: 2024-01-02 15:18 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
PDF exported (30.97 KB, application/pdf)
2023-11-16 22:49 UTC, Roger
Details
Original form Writer (17.21 KB, application/vnd.oasis.opendocument.text)
2023-11-16 22:50 UTC, Roger
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Roger 2023-11-16 22:49:04 UTC
Created attachment 190884 [details]
PDF exported

Hello!
When I create a form in LO Writer and export it as a PDF form and then open it with Firefox, the font changes size and format (italic, Arial) seen in the original file. Acrobat Reader, Chrome, and Edge only changes size.
Firefox, Acrobat Reader, Chrome, and Edge also add thousands separators when I've specifically specified in the number field that they don't add them. The only reader that doesn't add thousands separators is One Drive.

Version: 7.5.8.2 (X86_64) / LibreOffice Community
Build ID: f718d63693263970429a68f568db6046aaa9df01
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: ca-ES (ca_ES); UI: ca-ES
Calc: threaded
Comment 1 Roger 2023-11-16 22:50:51 UTC
Created attachment 190885 [details]
Original form Writer
Comment 2 kdub 2023-11-22 13:57:23 UTC
Hey Roger,

I tested this on macOS and I'm getting mixed results. Specifically, I tested this bug with Firefox, Chrome, and Preview.app. Preview was the only one that did not change the anything in the PDF file (i.e., italics, thousands, etc) initially. However, once I edited and saved the file with Preview, I was getting similar changes found in Firefox and Chrome: font size change, italics removed, etc.

I'm wondering if this is perhaps not a bug with LibreOffice, but with the way different PDF viewers handle the exported PDF file.

Version: 7.6.2.1 (X86_64) / LibreOffice Community
Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333
CPU threads: 12; OS: Mac OS X 13.5; UI render: Skia/Metal; VCL: osx
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded
Comment 3 Buovjaga 2023-12-01 15:44:44 UTC
Bibisected with win64-7.4 to 5938db731bd5f74182acb890102deee813635513
tdf#105972: pdf form: export numeric and currency fields as number type

The result before the commit was the number without separators. An earlier result was no placeholder shown at all.
Comment 4 Roger 2023-12-01 21:08:58 UTC
(In reply to kdub from comment #2)
> Hey Roger,
> 
> I tested this on macOS and I'm getting mixed results. Specifically, I tested
> this bug with Firefox, Chrome, and Preview.app. Preview was the only one
> that did not change the anything in the PDF file (i.e., italics, thousands,
> etc) initially. However, once I edited and saved the file with Preview, I
> was getting similar changes found in Firefox and Chrome: font size change,
> italics removed, etc.
> 
> I'm wondering if this is perhaps not a bug with LibreOffice, but with the
> way different PDF viewers handle the exported PDF file.
> 
> Version: 7.6.2.1 (X86_64) / LibreOffice Community
> Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333
> CPU threads: 12; OS: Mac OS X 13.5; UI render: Skia/Metal; VCL: osx
> Locale: en-US (en_US.UTF-8); UI: en-US
> Calc: threaded

Thank you, kdub,
Perhaps the bug is in the viewers but if LO exports to PDF the results must be shown correctly in at least one viewer, should'n it? 
If not, how we will know the exportation is functioning correctly? It's LO the one that exports.

(In reply to Buovjaga from comment #3)
> Bibisected with win64-7.4 to 5938db731bd5f74182acb890102deee813635513
> tdf#105972: pdf form: export numeric and currency fields as number type
> 
> The result before the commit was the number without separators. An earlier
> result was no placeholder shown at all.

Thank you, Bouvjaga, but I don't understand the message. It's a solution? You are saying something to me?
Comment 5 Buovjaga 2023-12-02 08:56:19 UTC
(In reply to Roger from comment #4)
> (In reply to Buovjaga from comment #3)
> > Bibisected with win64-7.4 to 5938db731bd5f74182acb890102deee813635513
> > tdf#105972: pdf form: export numeric and currency fields as number type
> > 
> > The result before the commit was the number without separators. An earlier
> > result was no placeholder shown at all.
> 
> Thank you, Bouvjaga, but I don't understand the message. It's a solution?
> You are saying something to me?

It appears Xisco's code change caused the issue, so he will look into it.

If you want to learn more about how I did it:
https://wiki.documentfoundation.org/QA/Bibisect
https://wiki.documentfoundation.org/QA/Bibisect/Bibisecting_tutorial

Anyone is welcome to use this method to analyse found bugs.
Comment 6 Buovjaga 2023-12-04 12:42:18 UTC
Notable: despite what is said in the description, the separators do not appear when the PDF file is viewed in Firefox or Chrome. Xisco was asking about this, so I checked. I only see them in Acrobat Reader.
Comment 7 Roger 2024-01-02 15:18:42 UTC
(In reply to Buovjaga from comment #6)
> Notable: despite what is said in the description, the separators do not
> appear when the PDF file is viewed in Firefox or Chrome. Xisco was asking
> about this, so I checked. I only see them in Acrobat Reader.

Absolutely true! 
In Firefox 121.0 (64 bits), do not appear dots now. But the font format italic, it's changing yet.
In Chrome Version 120.0.6099.130 (Compilation official) (64 bits) the italics and thousands separators appears correctly now.
In Microsoft Edge Version 120.0.6099.130 it's the same as Chrome.
In Acrobat Reader 2023.006.20380, appears thousands separators yet.

The font size is correct in all readers.

Thank you for your help!