[Bf-docboard] less graphics
Alex Heizer
bf-docboard@blender.org
Fri, 03 Jan 2003 08:49:38 -0600
--------------010405050801030802070908
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Stefano Selleri wrote:
>>>The thing I was concerned about was more about establishing a few
>>>standards before everyone makes their 20 million screenshots and
>>>renders. In the last PDF I downloaded from the sources, there were
>>>already around 70 images, and most of the pages don't have their
>>>images yet. Once the standards are set, you can make whatever format
>>>you want. It's a lot easier to make a 5k PNG from a 10MB EPS than the
>>>other way around, so you make printable images the default, then scale
>>>and compress a version from that for Web or a PDF.
>>>
>>You're absolutely right. I'm not sure yet on how to proceed with that.
>>Do you think that a combination between Stefano's styleguide and your
>>remarks earlier would be enough for the time being?
>>
>
>waitwaitwait...
>
>The bunch of images is already there, kindly provided by Carsten,
>I'm personally on my way to update the outdated (i.e. re-taking screenshots
>where interface has changed (Rendering buttons, etc)
>
I was wondering what happened to the original pics from the book...
>There are guidelines in the styleguide to make screenshots
>consistent. This doesn't mean they cannot be improved, of course,
>but a starting point is there ;)
>
So I've heard! I still need to download that, because I can't wait to
see it. :)
>Formats MUST be decide together with standard,
>PNG is great for bitmaps, EPS for vector graphics. We should use
>both formats, IMHO, actually all three (JPGs for Renderings) since
>
>renderings -> lossy compression is OK -> JPG
>buttons/screenshots -> lossy compression is not OK -> PNG
>graphs/flocharts -> vectorial in nature -> EPS
>
>storing screenshots in EPS or a flowchart in PNG is
>mostly inappropriate ;)
>
Storing screenshots and renders in EPS is actually what needs to happen
for anything that you'll want to print. Any graphic that comes out of
QuarkXpress for a press needs to be converted at some point to a 300dpi
CMYK EPS. If we don't do it here, we'll be charged by the printer to
have them do it for us at print time. EPSes are also good for vector
images, but if there is even the most remote possibility that something
will be printed, you will save time and money by making a high-res TIFF,
and convert it to an EPS from the very beginning.
I guarantee that if you send a bunch of 72dpi PNGs to a printer, they
will charge you $60/hr (in the US) to convert them all to CMYK EPSes for
printing, and a lot of them still won't look as good as if they started
out as high-res TIFFs. That's just how print works. It's totally
different than for Web or PDFs.
Alex
--------------010405050801030802070908
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<html>
<head>
</head>
<body>
<br>
<br>
Stefano Selleri wrote:<br>
<blockquote type="cite" cite="mid:007601c2b302$be8c2fc0$080ea8c0@agave">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">The thing I was concerned about was more about establishing a few<br>standards before everyone makes their 20 million screenshots and<br>renders. In the last PDF I downloaded from the sources, there were<br>already around 70 images, and most of the pages don't have their<br>images yet. Once the standards are set, you can make whatever format<br>you want. It's a lot easier to make a 5k PNG from a 10MB EPS than the<br>other way around, so you make printable images the default, then scale<br>and compress a version from that for Web or a PDF.<br></pre>
</blockquote>
<pre wrap="">You're absolutely right. I'm not sure yet on how to proceed with that.<br>Do you think that a combination between Stefano's styleguide and your<br>remarks earlier would be enough for the time being? <br></pre>
</blockquote>
<pre wrap=""><!----><br>waitwaitwait...<br><br>The bunch of images is already there, kindly provided by Carsten,<br>I'm personally on my way to update the outdated (i.e. re-taking screenshots<br>where interface has changed (Rendering buttons, etc)</pre>
</blockquote>
I was wondering what happened to the original pics from the book...<br>
<br>
<blockquote type="cite" cite="mid:007601c2b302$be8c2fc0$080ea8c0@agave">
<pre wrap="">There are guidelines in the styleguide to make screenshots<br>consistent. This doesn't mean they cannot be improved, of course,<br>but a starting point is there ;)<br></pre>
</blockquote>
So I've heard! I still need to download that, because I can't wait to see
it. :) <br>
<br>
<blockquote type="cite" cite="mid:007601c2b302$be8c2fc0$080ea8c0@agave">
<pre wrap="">Formats MUST be decide together with standard, <br>PNG is great for bitmaps, EPS for vector graphics. We should use<br>both formats, IMHO, actually all three (JPGs for Renderings) since<br><br>renderings -> lossy compression is OK -> JPG<br>buttons/screenshots -> lossy compression is not OK -> PNG<br>graphs/flocharts -> vectorial in nature -> EPS<br><br>storing screenshots in EPS or a flowchart in PNG is<br>mostly inappropriate ;)</pre>
</blockquote>
<br>
Storing screenshots and renders in EPS is actually what needs to happen for
anything that you'll want to print. Any graphic that comes out of QuarkXpress
for a press needs to be converted at some point to a 300dpi CMYK EPS. If
we don't do it here, we'll be charged by the printer to have them do it for
us at print time. EPSes are also good for vector images, but if there is
even the most remote possibility that something will be printed, you will
save time and money by making a high-res TIFF, and convert it to an EPS from
the very beginning.<br>
<br>
I guarantee that if you send a bunch of 72dpi PNGs to a printer, they will
charge you $60/hr (in the US) to convert them all to CMYK EPSes for printing,
and a lot of them still won't look as good as if they started out as high-res
TIFFs. That's just how print works. It's totally different than for Web or
PDFs.<br>
<br>
Alex<br>
</body>
</html>
--------------010405050801030802070908--