From: "Ulrich Dirr" <ud@art-satz.de>
Cc: 'Hans Hagen Outside' <pragma@wxs.nl>
Subject: RE: Help with LaTeX -> ConTeXt & book typesetting
Date: Sun, 12 Sep 2004 19:13:32 +0200 [thread overview]
Message-ID: <E1C6Xux-0004H8-00@mrelayng.kundenserver.de> (raw)
In-Reply-To: <41440AE3.5090209@wxs.nl>
Hans Hagen wrote:
>> (BTW I've already produced all expanded version with fontinst)
>>
> wait for the new pdftex (or grab a test versions soemwhere): it has auto
> expansion included, and there i sno need any more to create the
> instances yourself (doen within pdftex)!
Yes, I know. Of course this is an improvement. But I've already set it up
-- so why not use it?
Nevertheless it seems to me that there're several problems still. I'm using
now:
This is pdfeTeXk, Version 3.141592-1.20a-rc7.2-2.2
ConTeXt ver: 2004.8.15 fmt: 2004.9.12 int: english mes: english
Sometimes the hyphen is not protruded at all. BTW where do I define in
ConTeXt my font specific microtypographic values? In LaTeX I wrote
\input{protcode-helvetica}
\input{efcode-helvetica}
\pdfprotrudechars=2
\pdfadjustspacing=2
\def\setupfont{\setprotcode\font}
\def\setupEFfont{
\setprotcode\font
\resetefcode\font
\pdffontexpand\font 20 20 5}
...
>> If ConTeXt is using the new german spelling & hyphenation rules then:
>> *§108* If ss stands for ß, then it will be hyphenated s-s. E.g., Grüs-se
>> (instead of Grü-ße), heis-sen (instead of hei-ßen).
>> *§109* The connection of consonants ch, ck, and sch, and also in foreign
>> words with ph, rh, sh, and th will not be hyphenated in between if they
>> stands for a single sound. E.g., Bü-cher, Zu-cker, ba-cken, Fla-sche,
>> Ma-che-te, Pro-phet, Myr-rhe, Ca-shew-nuss, ka-tho-lisch.
>>
>>
> so .. what are the proposed changes to the german language specifics in
> enco-fde.tex?
Mmh, I'm that familiar with ConTeXt ;-) Hopefully the patterns will do
most.
But of course
\installcompoundcharacter "ck {\discretionary {k-}{k}{ck}}
should be changed to
\installcompoundcharacter "ck {\discretionary {-}{ck}{ck}}
((ck should always stay as it is; maybe one even don't need this def
anymore))
Ulrich
next prev parent reply other threads:[~2004-09-12 17:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-10 15:15 Ulrich Dirr
2004-09-10 20:38 ` Hans Hagen Outside
2004-09-11 7:22 ` Ulrich Dirr
2004-09-12 8:37 ` Hans Hagen Outside
2004-09-12 9:01 ` XML in heads Martin Kolarík
2004-09-12 9:17 ` XML in heads -- correction Martin Kolarík
2004-09-12 17:13 ` Ulrich Dirr [this message]
2004-09-13 18:28 ` struts in \quotation{..} (was: Help with LaTeX -> ConTeXt & book typesetting) Patrick Gundlach
2004-09-14 5:13 ` Ulrich Dirr
2004-09-14 9:46 ` Hans Hagen
2004-09-14 9:52 ` struts in \quotation{..} Hans Hagen
2004-09-14 10:21 ` Patrick Gundlach
2004-09-14 16:25 ` Hans Hagen
2004-09-14 16:58 ` Patrick Gundlach
2004-09-15 8:17 ` Hans Hagen
2004-09-27 12:08 ` Christopher Creutzig
2004-09-12 6:20 ` Floats and captions difficulties Martin Kolarík
2004-09-12 8:00 ` Floats and captions difficulties -- correction Martin Kolarík
2004-09-15 18:43 ` Floats and captions difficulties Martin Kolarík
2004-09-16 7:43 ` Hans Hagen
2004-09-16 11:24 ` Martin Kolařík
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=E1C6Xux-0004H8-00@mrelayng.kundenserver.de \
--to=ud@art-satz.de \
--cc=ntg-context@ntg.nl \
--cc=pragma@wxs.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).