From: Steffen Wolfrum <context@st.estfiles.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: xetext-pdftex differences
Date: Wed, 11 Apr 2007 11:09:17 +0200 [thread overview]
Message-ID: <20070411110917406329.47c0f948@st.estfiles.de> (raw)
In-Reply-To: <6faad9f00704101227u1fd43e52wf55050e5cc918374@mail.gmail.com>
Moica, thanks for your detailed support!
On Tue, 10 Apr 2007 21:27:47 +0200, Mojca Miklavec wrote:
>> Where do I go when I experience differences between context/pdftext
>> and context/xetex?
>
> What do you mean?
these:
>> For example with context/xetex I get ...
>>
>> ! Undefined control sequence.
>> \stopframedtext ->\dostopframedtext
>
...
>> ... and I do get "SS" instead of eszett ("ß") with the following:
>
> Interesting effect ... (as if the encoding was unknown)
I have to admit that it I never understood which encoding to use when....
if, for example, I just write english/german/french then I could also use texnansi, this works perfect :
\usetypescriptfile[type-gyr]
\usetypescript[times][texnansi]
\mainlanguage[de]
\enableregime[utf]
\setupbodyfont[times,9pt]
> Which version of ConTeXt? It works OK here with 2007.03.22, but I need
> to try the new beta. In principle this should not happen, it's
> probably a bug or some other local problem.
it is version 2007.01.12 (didn't you recommend to stay with the january version?)
>> Whom to tell this?
>
> Mailing list is the perfect place.
I was wondering whether the xetex or the context list is better as it is a mixed xetex/context-topic
and for Adam is in "paternity leave" I had no idea on which list someone continues.
> At the beginning I had problems with XeTeX as well since Times
> resolved to 'Times Roman:mapping=tex-text', which resolved to the name
> 'mapping=tex-text' (a side effect of recent that should probably be
> fixed somehow in the near future), but that problem disappeared later.
> I had to temporary fix this (leftovers before TeXGyre family managed
> to overload everything perhaps?):
right, "Times Roman:mapping=tex-text": This also happened to me when using ...
\usetypescriptfile[type-gyr]
\usetypescript[times][uc]
... that's why I used ...
\usetypescriptfile[type-gyr]
\usetypescript[times][ec]
... but probably I should have used "texnansi" (see above).
Steffen
next prev parent reply other threads:[~2007-04-11 9:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-08 20:16 Steffen Wolfrum
2007-04-10 19:27 ` Mojca Miklavec
2007-04-11 9:09 ` Steffen Wolfrum [this message]
2007-04-11 15:44 ` Mojca Miklavec
2007-04-11 17:22 ` Hans Hagen
2007-04-12 7:37 ` Steffen Wolfrum
2007-04-12 10:41 ` Hans Hagen
2007-04-12 7:53 ` Steffen Wolfrum
2007-04-12 10:46 ` Hans Hagen
2007-04-12 13:53 ` Steffen Wolfrum
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=20070411110917406329.47c0f948@st.estfiles.de \
--to=context@st.estfiles.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).