[FM Discuss] Optimizing images for printing

Tomi Toivio tomi.olavi.toivio at gmail.com
Wed Nov 2 07:12:45 PDT 2011


Yeah, we haven't really been thinking so much about printing with most of
the manuals, but earlier this year we printed the Open Media Production
book since it was basically describing the workshops that were developed by
m-cult in the Medios project, and I had to do the HTML bit by bit and
always make a new version of the PDF to see how it would look there. Then I
didn't actually try to use CSS, which I might try next time.

Another thing about images is that I noticed that changing the name of
images would be very useful for collaborative writing, since many people
(me included) tend to name everything just Screenshot1 to Screenshot999.
And for collaborative writing it should be something like
ChapterName_ImageName, which I pretty much start to think about after I
have uploaded the screenshots.


2011/11/2 Aleksandar Erkalovic <aerkalov at gmail.com>

> we planned different versions for print and web from the start. it is
> just, we didn't implement it because we didn't have time. now we will
> have time to finally implement it, but we also have lots of books and
> existing code that will have to be changed..... arrrghhhh indeed  but
> at least we know better how to handle our workflows better and how to
> implement this feature.
>
> aco
>
> On Wed, Nov 2, 2011 at 10:13 AM, Cedric Gémy <cedric.gemy at gmail.com>
> wrote:
> > lo everyone
> >
> > trouble with pictures for web is that they are 2 small for print purpose.
> > I'm actually trying to layout Scribus manual in Scribus and get low res
> > pictures even at small size (only halt of the page width). I was wishing
> to
> > do an XSLT conversion Script, but this picture quality is a pb that
> actually
> > stops me.
> >
> > What we'd need is at least IMO :
> > - be able to upload full size pictures (which might not be enough, but
> > better)
> > - have an automatic resizing feature for the website, at least at
> display if
> > not applied to image itself (sources pictures could be stored in a
> different
> > directory PDF could une one directory and the screen formats another one)
> > - save as PNG for best quality. JPEG is very bad with lines. That might
> > affect text too
> > - the right size of an image for print process is :
> > (widthinpixels*(targetresolution/actualresolution)) idem for height, but
> it
> > depends of the workflow you have
> >
> > CU
> >
> > 2011/11/2 helen varley jamieson <helen at creative-catalyst.com>
> >>
> >> i'm not a graphics expert, & also i'm less often thinking about
> printing &
> >> more often about web so i tend to make everything as low-res as
> possible. i
> >> guess a guideline would be useful, especially including the standard
> >> printed-out size of the manual so that you can try to make the actual
> image
> >> the right size when you insert it.
> >>
> >> h : )
> >>
> >> On 2/11/11 9:05 AM, adam wrote:
> >>>
> >>> i think png is best...
> >>>
> >>> adam
> >>>
> >>> On 11/01/2011 10:25 PM, Tomi Toivio wrote:
> >>>>
> >>>> Hi,
> >>>>
> >>>> Does somebody have a procedure for optimizing manual images for
> >>>> printing?
> >>>> What is the best file format? What is the best way to reduce the image
> >>>> size
> >>>> without the quality being reduced? GIMP? Any guidelines for this?
> >>>>
> >>>> Actually there should probably be a manual on how to use pictures on
> >>>> FLOSS
> >>>> Manuals...
> >>>>
> >>>> There have been some timeout errors when trying to publish books on
> the
> >>>> Finnish site, after debugging this for a while it started to seem like
> >>>> the
> >>>> web hosting organization had just changed timeout settings when they
> >>>> updated the servers about a week ago. Now the timeout on our server is
> >>>> 120,
> >>>> which means that usually the book publishing process gets a timeout
> when
> >>>> trying to publish the PDF. Sometimes it manages to do it in less than
> >>>> 120
> >>>> seconds and the process finishes without error. So the timeout
> settings
> >>>> should be increased to at least 360 or more?
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> Discuss mailing list
> >>>> Discuss at lists.flossmanuals.net
> >>>> http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net
> >>>
> >>
> >>
> >> --
> >> ____________________________________________________________
> >>
> >> helen varley jamieson: creative catalyst
> >> helen at creative-catalyst.com
> >> http://www.creative-catalyst.com
> >> http://www.avatarbodycollision.org
> >> http://www.upstage.org.nz
> >> ____________________________________________________________
> >>
> >> _______________________________________________
> >> Discuss mailing list
> >> Discuss at lists.flossmanuals.net
> >> http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net
> >
> >
> >
> > --
> > Cédric Gémy
> > -----------------------------------------------------------------
> > Formationlibre.org
> > FlossManualsFrancophone
> > Association Francophone des Graphistes Libres
> >
> >
> > _______________________________________________
> > Discuss mailing list
> > Discuss at lists.flossmanuals.net
> > http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net
> >
> >
>
>
>
> --
>  http://www.binarni.net/
> _______________________________________________
> Discuss mailing list
> Discuss at lists.flossmanuals.net
> http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net
>



-- 
Best Regards
Tomi Toivio
Open Source Coordinator
http://fi.flossmanuals.net/
tomi at flossmanuals.net
+358453536625
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.flossmanuals.net/pipermail/discuss-flossmanuals.net/attachments/20111102/856e7935/attachment.htm>


More information about the Discuss mailing list