ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: XeTeX + ConTeXt in TeXShop
Date: Wed, 12 Sep 2007 10:50:06 +0200	[thread overview]
Message-ID: <46E7A83E.6060805@wxs.nl> (raw)
In-Reply-To: <6faad9f00709120022g469caa63mb163fbcf8c5c617@mail.gmail.com>

Mojca Miklavec wrote:
> On 9/12/07, Andrea Valle wrote:
>> PS: I wikified some of the previous xetex infos. Please someone check I
>> didn't write silly stuff...
> 
> The information that \externalfigure should be replaced by
> \XeTeXpicfile is misleading. It is a temporary solution for the bug (I
> didn't test recently, but I had serious prolems with inclusion of
> binary figures and newer PDF file versions), but not a general rule.
> The bug should be fixed if it still exists, rather than asking people
> to rewrite their sources to low-level commands.
> 
> (The problems I had were the following: all the photos taken with my
> camera resulted in way too big images in the final PDF (width=,
> height= had absolutely no effect). It worked OK with pdfTeX & LuTeX
> though, and if I took that picture, modified it a bit in some external
> program and saved it again, it worked OK. So my temporary workaround
> was to save the photos again in some other program. But it should be
> fixed.)

you get that kind of effects when an image has no info about the 
resolution; pdftex/luatex can be told what the resolution is but even 
that can be a mismatch; there is no safeguard against faulty graphics 
and indeed reprocessing them may help;

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


      parent reply	other threads:[~2007-09-12  8:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-10 15:12 Andrea Valle
2007-09-10 15:32 ` Andrea Valle
2007-09-10 15:49 ` Arthur Reutenauer
2007-09-10 16:18   ` Andrea Valle
2007-09-10 17:26     ` Henning Hraban Ramm
2007-09-11  9:14       ` Andrea Valle
2007-09-11 10:44         ` Arthur Reutenauer
2007-09-11 12:05           ` Andrea Valle
2007-09-11 21:20           ` Henning Hraban Ramm
2007-09-11 23:51             ` Andrea Valle
2007-09-12  7:22               ` Mojca Miklavec
2007-09-12  7:55                 ` Andrea Valle
2007-09-12  8:50                 ` Hans Hagen [this message]

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=46E7A83E.6060805@wxs.nl \
    --to=pragma@wxs.nl \
    --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).