From: Volker RW Schaa <v.r.w.schaa@gsi.de>
Subject: Re: error with \hyphenation after update
Date: Sun, 30 Apr 2006 21:17:32 +0200 [thread overview]
Message-ID: <44550D4C.5050306@gsi.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0604301926300.4422@gaston.pm>
Peter Münster wrote:
> Hello Hans, Taco and Mojca,
> thanks for your fast efforts for me! I just wanted to send a zip-file...
>
> Just still one small problem: where should I apply this patch? Wherever I
> try (in cont-new.tex, enco-ini.tex or in the document), I get
> "Undefined control sequence: \everypathypsettings"
for Hans, who's learning Polish right now by attending the Polish membershio
meeting, see below for the line
>> \the\everypathypsettings
> On Sun, 30 Apr 2006, Hans Hagen wrote:
>
>> ? wrote:
>>> Hello,
>>> this used to work about 3 weeks ago. With version 2006.04.27, I get an
>>> error:
>>>
>>> \enableregime[il1]
>>> \hyphenation{Di-sul-fid-br?cken}
>>> \starttext
>>> Error: \type{Improper \hyphenation will be flushed.}
>>> \stoptext
>>>
>> with the help of mojca (who was able to recover your funny char) and
>> taco (who was willing to enter tracingmode):
>>
>> \def\pathypsettings
>> {\ifx \enablepatterntokens\undefined
>> \defineactivecharacter [ {\handlepatterntoken}%
>> \else
>> \enablepatterntokens
>> \fi
>> \the\everypathypsettings
please remove this line
>> \let\dochar\thechr
>> \lccode16=16 % brrr, extra quote in ec (turkish)
>> \lccode17=17 % brrr, extra quote in ec (turkish)
>> \lccode`\-=`\-
>> \lccode`\'=`\'
>> \lccode`\"=`\"
>> \relax}
>
>
> Cheers, Peter
>
Cheers,
Volker
prev parent reply other threads:[~2006-04-30 19:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-30 7:15 Peter Münster
2006-04-30 13:14 ` Hans Hagen
2006-04-30 13:25 ` Hans Hagen
2006-04-30 14:27 ` Hans Hagen
2006-04-30 17:33 ` Peter Münster
2006-04-30 19:17 ` Volker RW Schaa [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=44550D4C.5050306@gsi.de \
--to=v.r.w.schaa@gsi.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).