On 3/10/2015 2:33 AM, Harald Koenig wrote:
On Mar 10, Hans Hagen wrote:
anyway, i need to think a bit about it but we do have all the info
available, like
- needed width/height
- original width/height
and from that we can calculate some conversion parameters
if you start thinking/working
Hallo Harald, lange nicht gesehen! ;)
Am 2015-03-10 um 07:33 schrieb Harald Koenig
koe...@tat.physik.uni-tuebingen.de:
if you start thinking/working on this, some data from EXIF
might be interesting and helpful too, esp. the Orientation.
using that data, automatic rotation to the correct
On Mon, Mar 09 2015, Harald Koenig wrote:
is it possible that context (lua?) will shrink all \externalfigure jpegs
automatically to some specified dpi resolution and quality
(e.g. 300 dpi with 95% jpeg 'quality' for print and
100 dpi and 75% for screen quality) ?
Hi,
Does this work:
On Mar 10, Peter Münster wrote:
Does this work: http://modules.contextgarden.net/grph-downsample ?
(I did not test it with the latest context version...)
There is no support for changing the quality, but it should be easy to
add it.
that should great!
but how do I use it ?
problems with
On Tue, Mar 10 2015, Harald Koenig wrote:
but how do I use it ?
- Copy grph-downsample.lua to
.../context/tex/texmf-local/tex/context/third/grph-downsample/grph-downsample.lua
- context --generate
- Copy hacker.jpg to your directory.
- Write this to test.tex:
--8---cut
Hi,
so here's my very generic question #1 for my India book:
is it possible that context (lua?) will shrink all \externalfigure jpegs
automatically to some specified dpi resolution and quality
(e.g. 300 dpi with 95% jpeg 'quality' for print and
100 dpi and 75% for screen quality) ?
since I'm
Hi,
is it possible that context (lua?) will shrink all \externalfigure jpegs
automatically to some specified dpi resolution and quality
(e.g. 300 dpi with 95% jpeg 'quality' for print and
100 dpi and 75% for screen quality) ?
[]
any hints to read the original large JPGs, but only write
On 03/09/2015 10:12 PM, Harald Koenig wrote:
any hints to read the original large JPGs, but only write print quality
300dpi images,
or low quaity 75dpi images for speed (and saving net bandwidth when mailing
PDFs
to co-workers of the group)?
Hi Harald,
how about converting the JPEG files
Harald,
I use ImageMagick/GraphicsMagick to resample HUGE high resolution tiff
images to something more manageable to work with. Using a script, I
converted hundreds of images to lower resolution copies. Then it was
simply a question of pointing ConTeXt to use the appropriate directory
to find
On Mar 09, Hans Hagen wrote:
On 3/9/2015 10:50 PM, Alan BRASLAU wrote:
This can be done once and is much better than getting ConTeXt to
convert every time on the fly.
Do you really think that we let context convert a big file each run
in a critical workflow? Context will only resample
On 3/9/2015 10:50 PM, Alan BRASLAU wrote:
This can be done once and is much better than getting ConTeXt to
convert every time on the fly.
Do you really think that we let context convert a big file each run in a
critical workflow? Context will only resample when an image file changed
(which
On Mar 09, Aditya Mahajan wrote:
Why not eliminate the orignal high quality jpegs altogether? Use
one reason is that the jpgs are not in final shape either.
the selected pictures will be reworked from raw files,
maybe some brightness/contrast correction, clipped, etc.
whenever the images are
On 3/10/2015 12:33 AM, Harald Koenig wrote:
ACK -- sort of:
have a look for my next mail jpeg problem: Dimension too large
as I'm running into a strange problem exactly using imagemagick to shrink the
images...
that is often an indication that the image lacks tags describing the
resolution
On Mon, Mar 9, 2015 at 10:50 PM, Alan BRASLAU alan.bras...@cea.fr wrote:
Harald,
I use ImageMagick/GraphicsMagick to resample HUGE high resolution tiff
images to something more manageable to work with. Using a script, I
converted hundreds of images to lower resolution copies. Then it was
On 3/10/2015 12:18 AM, Harald Koenig wrote:
On Mar 09, Hans Hagen wrote:
On 3/9/2015 10:50 PM, Alan BRASLAU wrote:
This can be done once and is much better than getting ConTeXt to
convert every time on the fly.
Do you really think that we let context convert a big file each run
in a
On Mar 10, Hans Hagen wrote:
anyway, i need to think a bit about it but we do have all the info
available, like
- needed width/height
- original width/height
and from that we can calculate some conversion parameters
if you start thinking/working on this, some data from EXIF
might be
16 matches
Mail list logo
