Created attachment 153742 [details]
Example odg with QR code

Created attachment 153743 [details]
PNG result

Reproduced in

Version: 6.4.0.0.alpha0+
Build ID: c9336bfb6bbf6d73d3f23c124262ade30133448d
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: x11; 
Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US
Calc: threaded

but not in

Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a)

(In reply to Xisco Faulí from comment #3)
> Reproduced in
> 
> Version: 6.4.0.0.alpha0+
> Build ID: c9336bfb6bbf6d73d3f23c124262ade30133448d
> CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: x11; 
> Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US
> Calc: threaded
> 
> but not in
> 
> Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a)

Xisco from where QR generator in 4.1?

No need to generate a QR code, use can use the file attached

Started in 4.2, but I can't start a lot of builds in that repo now, I get the following error message, and it quits:
javaldx: Could not find a Java Runtime Environment!
Warning: failed to read path from javaldx

All I can say, the exported PNG is already bad at this commit: 6c3a09b3b3ca9ad0c81a55efaaedad35c39de767

Example: www.qrcode-generator.ch 
/1.) Select text icon and enter text 
/2.) create qr code 
/3.) PNG and open with IrfanView 64-bit (downolad www.irfanview.com) 
/4.) Edit/copy 
/5.) insert in Libre-Office document

I am unable to open attachment 153742 [details] in the older commits of Linux 42max repo. However, going backwards from the commit mentioned by Áron, I can say that the bad result is already in source commit ed87e4c4b09d0f623c350528a4f6a6d049735bd1

I'm calling this notBibisectable.

(In reply to päde from comment #7)
> Example: www.qrcode-generator.ch 
> /1.) Select text icon and enter text 
> /2.) create qr code 
> /3.) PNG and open with IrfanView 64-bit (downolad www.irfanview.com) 
> /4.) Edit/copy 
> /5.) insert in Libre-Office document

This is not equivalent. With this, there is no problem in the latest commit of Linux 42max repo.

As landed at bug 51510 with pretty much the same issue (see duplicate & response Justin L)

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

(In reply to Telesto from comment #9)
> As landed at bug 51510 with pretty much the same issue (see duplicate &
> response Justin L)
> 
> *** This bug has been marked as a duplicate of bug 51510 ***

I'm not sure. Where is a link between saving embedded SVG as PNG into DOC/DOCX and bad PNG quality after saving QR code (OLE object) as different PNG file?

(In reply to Roman Kuznetsov from comment #10)
> (In reply to Telesto from comment #9)
> > As landed at bug 51510 with pretty much the same issue (see duplicate &
> > response Justin L)
> > 
> > *** This bug has been marked as a duplicate of bug 51510 ***
> 
> I'm not sure. Where is a link between saving embedded SVG as PNG into
> DOC/DOCX and bad PNG quality after saving QR code (OLE object) as different
> PNG file?

Apparently QR is generated as SVG. SVG not supported by DOCX/DOC format and converted to PNG which goes wrong. I reported the same thing: see bug 135746.

(In reply to Telesto from comment #11)

> 
> Apparently QR is generated as SVG. SVG not supported by DOCX/DOC format and
> converted to PNG which goes wrong. I reported the same thing: see bug 135746.

Where in this bug report do you see anything about DOC/DOCX?

(In reply to Roman Kuznetsov from comment #12)
> (In reply to Telesto from comment #11)
> 
> > 
> > Apparently QR is generated as SVG. SVG not supported by DOCX/DOC format and
> > converted to PNG which goes wrong. I reported the same thing: see bug 135746.
> 
> Where in this bug report do you see anything about DOC/DOCX?

I don't, but all this stuff is tied together.. The DOCX filter utilizes the same conversion SVG to PNG as used for export. At least this would 'proper' coding style entail; re-use the same function instead of duplicate the code (copy/paste). With single place you can 'fix'. With the downside that it's broken all over the place. 

And this should be the case in my observations. There is something seriously broken in the file-format to file format conversion area (not only SVG -> PNG). Across all components (Writer/Draw/Impress/Calc). 

But well, if you prefer to leave this separate, also fine. But I prefer directing all relevant bugs to bug 51510, to give it more priority [old + plenty duplicates + big CC list). And I believe this one would be fixed with bug 51510. However that's my take; no warrantees.

I leave it up to you.. [and sorry for marking it as duplicate in rude manner]

The problem is antialiased pixel processor created in drawinglayer::convertToBitmapEx (drawinglayer/source/tools/converters.cxx). If anti-aliasing is disabled, the result will be sharp.

We possibly need to pass "do not use AA" to the function somehow when we save SVGs to PNG.

Additional (or maybe the main) problem is that the bitmap is generated in getVectorGraphicReplacement, where it has the dimensions defined in the SVG; and then this bitmap is scaled to the wanted dimensions in GraphicHelper::ExportGraphic. This is very sub-optimal for a vector image format like SVG.

Even ImpGraphic::getBitmapEx has the logic to get the replacement, and then scale it. Odd.

No repro in

Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: b5c3a7502f7ff6ccf0f829c1f3a2ba50b8584c41
CPU threads: 16; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: ru-RU (ru_RU); UI: ru-RU
Calc: CL threaded

Very Nice!
Closed as WFM