• Status Closed
  • Percent Complete
  • Task Type Bugs
  • Category Manual
  • Assigned To No-one
  • Operating System All players
  • Severity Low
  • Priority Defer
  • Reported Version
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Rockbox
Opened by rasher - 2006-06-05

FS#5498 - H300 image is huge

Is there any good reason for the H300 image being as large as it is?
$ identify *-front.png
h1xx-front.png PNG 390×460 390×460+0+0 DirectClass 98kb
h300-front.png[1] PNG 802×1311 802×1311+0+0 DirectClass 1003kb
ondio-front.png[2] PNG 300×408 300×408+0+0 DirectClass 84kb
player-front.png[3] PNG 300×407 300×407+0+0 DirectClass 101kb
recorderv2fm-front.png[4] PNG 300×408 300×408+0+0 DirectClass 105kb

That’s a whopping 900kb extra, which makes the resulting manual about 80% larger than Ipod Video manual (the largest of the rest). And as far as I can tell, this is not visible, at least not on screen. Is such a large image really needed?

I’ve attached a smaller version, more similar in size to the archos units (300×490, 187kb).

Closed by  tucoz
2006-06-05 10:17
Reason for closing:  Fixed
Additional comments about closing:   Warning: Undefined array key "typography" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 371 Warning: Undefined array key "camelcase" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 407

The h300 image is not _that_ huge anymore. Converted to jpg.

I just compiled a manual with this smaller version of the image, and there is of course a difference, but in my opinion it’s not worth the large increase in size. YMMV.

I already noticed the font page image being huge and was thinking about a better solution – converting the front page image from png to jpg gives me about 500kB file size decrease, and IMO the difference isn’t notable (I was able finding jpg artifacts at 800% magnification).
To decrease the file size I’d also vote for (a) converting the front page image to jpg and (b) scaling down the h300 image as you suggested. The most people will actually read the manual on-screen, so I think we won’t loose anything and manuals will get down to about 1 MiB. OTOH we could consider converting all non-screenshot images to jpg (which won’t gain much ATM, but maybe there will be some more non-screenshot images in the future)

tucoz commented on 2006-06-05 09:24

The reason for having large (huge) images, is the fact that we want a decent quality when printing the manual. The huge size of the h300 image will still be less than 300 dpi at the current size. I have tried to get pdflatex to generate a on-line version of the manual (less quality, less size). I failed. But, it is possible to get pdflatex to reduce the dpi for the images used in the manual. I think the proper solution is to have a print version, with as high resolution images as possible and an online version with 72dpi resolution for the images. That is, keep the source with high quality images and let pdflatex do the scaling.


Available keyboard shortcuts


Task Details

Task Editing