From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \externalfigure and file size
Date: Fri, 20 Jan 2012 02:03:21 +0100 [thread overview]
Message-ID: <CALBOmsb1dvGgNoOd5hc2YkX693G8vxGVecT=MxRfzdkfng08pQ@mail.gmail.com> (raw)
In-Reply-To: <1327020690.5532.105.camel@kip-laptop>
On Fri, Jan 20, 2012 at 01:51, Kip Warner wrote:
> On Thu, 2012-01-19 at 21:49 -0300, Wagner Macedo wrote:
>> Well, as I can see, the "problem" is inkscape switch --export-dpi which in
>> grph-inc.lua has the value 600. I get same file size using inkscape -A
>> --export-dpi=600.
>>
>> But exporting this file (Pic.svg) without a great dpi (minimum 300) I get
>> an ugly file, very sharpened where has filters.
>
> But why should there be any implicit DPI specified with a vector
> graphic? Isn't the whole point of them to allow, theoretically, infinite
> resolution?
Yes, but this is only true as long as your graphic can be represented
reliably in the target format. And yours cannot.
It is like asking for conversion of a vector image of a circle into a
target format that only supports straight lines (also vector format,
but without support for splines).
http://www.inkscapeforum.com/viewtopic.php?f=6&t=9551
If this is your own graphic, you need to alter it in such a way that
it will be representable with what PDF is capable of doing. See the
chapter on smooth shading. You can do a lot with that, but it might
require a bit of extra effort (and then maybe hunting developers to
fix rendering bugs; Apple doesn't know how to render smooth shading
properly and even used to crash).
Mojca
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2012-01-20 1:03 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 0:25 Kip Warner
2012-01-19 7:56 ` Mojca Miklavec
2012-01-19 23:51 ` Kip Warner
2012-01-19 8:23 ` luigi scarso
2012-01-19 23:52 ` Kip Warner
2012-01-20 0:51 ` Marco
2012-01-20 1:02 ` Kip Warner
2012-01-20 9:08 ` Hans Hagen
2012-01-20 23:05 ` Kip Warner
2012-01-21 0:07 ` Hans Hagen
2012-01-21 0:12 ` luigi scarso
2012-01-21 0:15 ` Hans Hagen
2012-01-24 23:28 ` Kip Warner
2012-01-21 0:21 ` Marco
[not found] ` <20120121012234.1553b814@homerow>
2012-01-21 0:27 ` Kip Warner
2012-01-21 0:40 ` Marco
2012-01-21 0:55 ` Hans Hagen
2012-01-21 13:32 ` Marco
2012-01-24 0:33 ` Kip Warner
[not found] ` <20120121014245.794d515b@homerow>
2012-01-21 0:45 ` Kip Warner
2012-01-21 0:54 ` Hans Hagen
2012-01-21 3:31 ` Wagner Macedo
2012-01-21 9:40 ` Hans Hagen
2012-01-24 0:44 ` Kip Warner
2012-01-24 0:17 ` Kip Warner
2012-01-24 11:13 ` Marco
[not found] ` <20120124121433.57a167f4@homerow>
2012-01-24 23:20 ` Kip Warner
2012-01-21 1:46 ` luigi scarso
2012-01-20 23:48 ` Wagner Macedo
2012-01-19 10:58 ` Peter Rolf
2012-01-20 0:01 ` Kip Warner
2012-01-20 0:07 ` Pontus Lurcock
2012-01-20 0:23 ` Kip Warner
2012-01-20 0:45 ` Mojca Miklavec
2012-01-20 0:50 ` Pontus Lurcock
2012-01-20 1:26 ` Kip Warner
2012-01-20 0:13 ` Wagner Macedo
2012-01-20 0:23 ` Kip Warner
2012-01-20 0:43 ` Pontus Lurcock
[not found] ` <CAKGY2Pk_pXNNcks+EaEg0fLYh2ENtb3Cas13duoxihr654vQnQ@mail.gmail.com>
2012-01-20 0:51 ` Kip Warner
[not found] ` <CAKGY2Pk8TC8cJUEDvy5HhaS0NvbLmFcYvS3d6Es7vzUpa63ADg@mail.gmail.com>
2012-01-20 1:01 ` Kip Warner
2012-01-20 1:03 ` Mojca Miklavec [this message]
2012-01-20 1:30 ` Kip Warner
2012-01-20 8:55 ` luigi scarso
2012-01-20 23:04 ` Kip Warner
2012-01-20 23:36 ` luigi scarso
2012-01-20 0:14 ` Wolfgang Schuster
2012-01-20 1:24 ` Kip Warner
2012-01-20 0:21 ` Marco
2012-01-20 1:21 ` Kip Warner
2012-01-20 10:18 ` Marco
2012-01-20 10:26 ` Hans Hagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALBOmsb1dvGgNoOd5hc2YkX693G8vxGVecT=MxRfzdkfng08pQ@mail.gmail.com' \
--to=mojca.miklavec.lists@gmail.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).