ONLYOFFICE / DocumentServer

ONLYOFFICE Docs is a free collaborative online office suite comprising viewers and editors for texts, spreadsheets and presentations, forms and PDF, fully compatible with Office Open XML formats: .docx, .xlsx, .pptx and enabling collaborative editing in real time.
https://www.onlyoffice.com
GNU Affero General Public License v3.0
4.65k stars 1.06k forks source link

Images are blurry and not sharp #1603

Open AndiLeni opened 2 years ago

AndiLeni commented 2 years ago

This issue is unique.

Operating System

Windows 10 / 8.1 / 7

Version information

7

Expected Behavior

Hello,

inserted images (f.e. screenshots) should be sharp and easy to read.

Actual Behavior

I noticed, that screenshots I take and insert in OnlyOffice are not displayed as sharp as they are in MS Word or LibreOffice.

Reproduction Steps

No response

Additional information

What it looks like in MS word: grafik

What it looks like in OO: grafik

ShockwaveNN commented 2 years ago

Hi could you attach this sample file and also please describe your display setup - resolution, display scaling

AndiLeni commented 2 years ago

Dokument1.docx

It seems like it is an issue with high resolution images. My example document contains one hight-res screenshot and one low-res. The high-res one looks not as good as the one with lower resolution.

My screen is 1920x1080 and scaled to 125%.

ShockwaveNN commented 2 years ago

Oh, those are images, not text

Got it, I was able to reproduce it, it looks bad even in DocumentServer

We'll create an issue out of it

LuckySpecialist commented 2 years ago

This is a known Bug 19448 in our private tracker. We remind developers about it. Thank you.

ShockwaveNN commented 2 years ago

Moving this issue to DocumentServer repo, since it's our base product and problem actual there too

AndiLeni commented 2 years ago

Thank you for your attention!

majapavlo commented 1 year ago

Is there any work-around or progress on this issue? I am having the same problems with this

ShockwaveNN commented 1 year ago

@majapavlo Sorry, I don't think there is any workaround for this problem, the problem is very old, almost 10 years old, but fixing it required a lot of changes, so our developers still didn't fixed it