From: Andrea Valle <valle@di.unito.it>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: XeTeX + ConTeXt in TeXShop
Date: Wed, 12 Sep 2007 09:55:37 +0200 [thread overview]
Message-ID: <E90736AF-BED3-437B-824A-ED504B39148B@di.unito.it> (raw)
In-Reply-To: <6faad9f00709120022g469caa63mb163fbcf8c5c617@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1842 bytes --]
On 12 Sep 2007, at 09:22, Mojca Miklavec wrote:
> 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.
I completely agree, but nobody replied to my post when I complained.
> . So my temporary workaround
> was to save the photos again in some other program. But it should be
> fixed.)
Ok, but this is not a better solution.
It's only cleaner from a ConTeXt point of view.
So you do not modify the sources but because of the bug you modify
200 jpgs.
In any case, as I have written, I had not output problems with
\externalfigure, but the rli generation needed many texexec calls to
be completed and was too slow
(even if only for the first time).
Instead, I had no luck at all with pdfs inclusion.
So, my idea would be to clearly specify in the wiki entry that it's a
momentary workaround.
-a-
--------------------------------------------------
Andrea Valle
--------------------------------------------------
CIRMA - DAMS
Università degli Studi di Torino
--> http://www.cirma.unito.it/andrea/
--> andrea.valle@unito.it
--------------------------------------------------
I did this interview where I just mentioned that I read Foucault. Who
doesn't in university, right? I was in this strip club giving this
guy a lap dance and all he wanted to do was to discuss Foucault with
me. Well, I can stand naked and do my little dance, or I can discuss
Foucault, but not at the same time; too much information.
(Annabel Chong)
[-- Attachment #1.2: Type: text/html, Size: 7523 bytes --]
[-- Attachment #2: Type: text/plain, Size: 487 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2007-09-12 7:55 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 [this message]
2007-09-12 8:50 ` 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=E90736AF-BED3-437B-824A-ED504B39148B@di.unito.it \
--to=valle@di.unito.it \
--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).