From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: sometxt in mkiv
Date: Mon, 8 Sep 2008 09:22:12 +0200 [thread overview]
Message-ID: <412BE50D-3652-4602-A678-BE1D873B3813@uni-bonn.de> (raw)
In-Reply-To: <6faad9f00809071242n452c61c2l95e1f1949e244696@mail.gmail.com>
On Sep 7, 2008, at 9:42 PM, Mojca Miklavec wrote:
> Honestly, I don't think that we need this exact functionality. In mkiv
> textext works perfectly well to achieve the same goal, you don't
> really need \sometxt or \TeXtext. The only question is: do we care
> about backward compatibility? I can also remove the example from MyWay
> or write that it's a bit obscure. It really is an obscure application.
>
> OK, I just neglected the fact that I do use that in the gnuplot module
> (which is not mkiv ready for two tiny and obscure reasons that could
> be fixed long ago). In case that I won't be drawing the graphs for
> thesis in excell, I'll try to fix the module. I don't think that any
> other sane person uses \TeXtext. (I don't, and module should be fixed
> anyway.)
>
> Mojca
Mojca, Aditya,
thanks for your responses. I was aware that you can use textext
(that's what I do right now), but was under the impression that
sometxt was the way to go (faster and more flexible). Now I'm
confused :-) I was asking because I was working on my presentation
module. One of the metapost graphics for picture inclusion seems to
give problems when run under XeTeX, so I was wondering if I could
replace it with the clever sometxt mechanism Mojca mentions in her
MyWay. But then I saw that this doesn't work in mkiv... I find XeTeX
very hard to support in my module. I don't use it myself, I find fonts
deeply baffling (I still got the darned "mktextfm lmtypewriter-
blablabla" message a zillion times, and there is no way to stop a
XeTeX run; I still had to explicitly disable MKTEXTFM in texmf.cnf in
TeXLive 2008), so I'm considering just giving it up and tell people to
use mkiv instead.
Mojca: I appreciate you write "any other sane person" and not "any
sane person" :-)
All best
Thomas
___________________________________________________________________________________
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:[~2008-09-08 7:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-06 11:15 Thomas A. Schmitz
2008-09-07 13:43 ` Aditya Mahajan
2008-09-07 19:42 ` Mojca Miklavec
2008-09-08 7:22 ` Thomas A. Schmitz [this message]
2008-09-08 9:26 ` Hans Hagen
2008-09-08 18:43 ` Thomas A. Schmitz
2008-09-09 15:07 ` Mojca Miklavec
2008-09-09 15:13 ` Mojca Miklavec
2008-09-09 17:23 ` Thomas A. Schmitz
2008-09-08 8:16 ` Hans Hagen
2008-09-07 15:52 Thomas A. Schmitz
2008-09-07 23:32 ` Aditya Mahajan
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=412BE50D-3652-4602-A678-BE1D873B3813@uni-bonn.de \
--to=thomas.schmitz@uni-bonn.de \
--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).