Odoo is the world's easiest all-in-one management software.
It includes hundreds of business apps:
I've configured a logo on my company details. Although the logo is a high resolution image, it appears highly pixelized when resized and displayed on my website menu. BTW, looking at it on a Mac with retina display.
Is there any way to have high resolution logo to display correctly ?
Hi, we used to import a .png file and it is great on all devices.
Hope it will help.
P.
I think that if your image is say 3200x4800 px, odoo compresses the image to a small size so it would fit on the navi bar; thereby altering the properties of the image, so it looks like pixelized. I suggest you resize your logo to say, 145x85 px before uploading it to odoo.
Thanks Pierre,
Unfortunately, mine is actually a PNG and it is a high resolution image; but it remains highly pixelized on retina displays. Don't know how resizing is performed and how it should be...
V.
Create an account today to enjoy exclusive features and engage with our awesome community!
Sign up| Related Posts | Replies | Views | Activity | |
|---|---|---|---|---|
|
0
Oct 23
|
1178 | ||
|
4
Jul 16
|
2191 | ||
|
1
Jan 21
|
14691 | ||
|
1
Jun 16
|
7979 | ||
|
2
Jan 25
|
1006 |
1. Use the live chat to ask your questions.
2. The operator answers within a few minutes.
What is high resolution to you? Pixel size? DPI ?
@Ray : Well, for the image, it's all about size in pixels. I've used different size png logos (from 136x30 to 600x265) that all look sharp when rendered on a retina screen using, say, osx "preview" app; but the result is always pixelized when the image is finally displayed on my odoo website top left corner. So called retina displays have (at least) twice as much dpi as "classic" screens. In the past, I've used CMS where you could upload 2 different sized logo images in order to cope with high dpi rendering devices. However, I don't know whet has to be done in the page code. BTW, the odoo logo itself also looks pixelized here...
@Taz : unfortunately, this doesn't work. See my comment to Ray.