ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Gentium Basic/Book (getting weird)
Date: Fri, 23 Nov 2007 14:44:01 +0100	[thread overview]
Message-ID: <6faad9f00711230544g6e383f3by958afd6c5bceebfd@mail.gmail.com> (raw)
In-Reply-To: <6358C294-A7FF-4606-9A6E-E60373BDBFB5@st.estfiles.de>

On Nov 23, 2007 11:53 AM, Steffen Wolfrum wrote:
> As this strange error makes me a bit nervous I checked an older file
> for its behavior: same result!
>
> A file that without problems was typeset in April now ends up with
> the same kind of freezing:
>
> \usetypescriptfile[type-gyr]

you don't need that one for XeTeX, I think.

> \usetypescript[times][ec]

It's still not clear to me how to make these definition
engine-independent, but for XeTeX use

\usetypescript[times]

else you'll get the old ec-encoded fonts instead of OpenType.

> \mainlanguage[de]
> \enableregime[utf]
>
> \setupbodyfont[times,10pt] \setupinterlinespace[line=12pt]
>
> \starttext
>
> Wort und Tat in 1906
>
> \stoptext
>
> When this is set with pdftext all is fine.
> With xetex (or xtx) the process stop at this line:
>
> (/usr/local/texlive/2007/../texmf-local/tex/context/base/type-
> gyr.tex))! unknown encoding "utf"; reading as raw bytes

Sorry, my fault again.

For you: to solve the problem temporary, remove \enableregime, or use

\beginOLDTEX
    \enableregime[utf]
\endOLDTEX

or try to fix this line in regi-ini.mkii (and test the behavior):
    \def\mkenableregime#1{\doifnot{#1}{utf}{\XeTeXinputencoding "#1"\relax}}


For Hans: There's a little problem in regi-ini:

    \def\mkenableregime#1{\XeTeXinputencoding "#1"\relax}

\def\enableregime[#1]%
  {\edef\currentregime{\trueregimename{#1}}%
   \doifelsenothing\currentregime
     {\disableregime}
     {\douseregime\currentregime
      \mkenableregime\currentregime}}

This passes \XeTeXinputencoding "utf" to XeTeX, even is someone says
\enableregime[utf-8], but XeTeX doesn't know what "utf" encoding is
(it expects at least "utf-8" or nothing).

The following fix helps, but is not the final answer:

\def\mkenableregime#1{\doifnot{#1}{utf}{\XeTeXinputencoding "#1"\relax}}

This has one weak point though:
    \enableregime[cp1250]
    \enableregime[utf-8]
will leave the current regime at cp1250, so perhaps

\def\mkenableregime#1{\doifelse{#1}{utf}%
{\XeTeXinputencoding "utf-8"\relax}{\XeTeXinputencoding "#1"\relax}}

Another option would be to rename utf to utf-8 internally (or to adapt
\trueregimename or regi-syn), but that would probably do more harm
than good unless tested well, and it's not worth the effort.

... Hmmm .... when thinking agin ... I know that you asked me which
regime name to pass to XeTeX and I said "don't worry, it should be
more or less the same", but "8859-1" isn't valid regime name either.
I'll take a look and report back.

Mojca
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2007-11-23 13:44 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-19 18:04 Gentium Basic/Book Joel C. Salomon
2007-11-19 21:57 ` Joel C. Salomon
2007-11-19 22:18   ` Hans Hagen
2007-11-20  0:57   ` Mojca Miklavec
2007-11-22 11:01     ` Steffen Wolfrum
2007-11-22 11:30       ` Mojca Miklavec
2007-11-22 12:52         ` Steffen Wolfrum
2007-11-22 18:31           ` Wolfgang Schuster
2007-11-22 19:57             ` Gentium Basic/Book (getting weird) Steffen Wolfrum
2007-11-22 20:23               ` Mojca Miklavec
2007-11-22 20:35                 ` Steffen Wolfrum
2007-11-23 10:53                   ` Steffen Wolfrum
2007-11-23 13:44                     ` Mojca Miklavec [this message]
2007-11-23 14:11                       ` Arthur Reutenauer
2007-11-23 15:51                         ` Mojca Miklavec
2007-11-23 16:33                           ` Gentium Basic/Book (getting even weirder) Steffen Wolfrum
2007-11-24  0:25                             ` Mojca Miklavec
2007-11-24 21:33                               ` Steffen Wolfrum
2007-11-25  1:30                                 ` Mojca Miklavec
2007-11-25 11:21                                   ` Steffen Wolfrum
2007-11-25 12:51                                     ` Mojca Miklavec
2007-11-23 19:28                           ` Gentium Basic/Book (getting weird) Arthur Reutenauer
2007-11-23 19:36                             ` Steffen Wolfrum
2007-11-23 22:15                               ` Arthur Reutenauer
2007-11-23 23:38                               ` Mojca Miklavec
2007-11-24 22:48                       ` Hans Hagen
2007-11-23 10:54                 ` Wolfgang Schuster
2007-11-25 20:27                 ` Gentium Basic/Book [solved] Steffen Wolfrum
2007-11-22 21:28             ` Gentium Basic/Book Joel C. Salomon
2007-11-22 15:10         ` 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=6faad9f00711230544g6e383f3by958afd6c5bceebfd@mail.gmail.com \
    --to=mojca.miklavec.lists@gmail.com \
    --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).