From: Karsten Tinnefeld <tinne@goedel.cs.uni-dortmund.de>
Subject: Re: Expand cont-ger.tex
Date: Mon, 15 Nov 1999 19:34:11 +0100 [thread overview]
Message-ID: <199911151834.TAA13046@goedel.cs.uni-dortmund.de> (raw)
> >These shorthands seem to be the only ones from german/babel not
> >implemented in cont-ger - why?
>
> Since I don't use latex, I just implemented what tobias told me to
> implement. BTW, the shortcut mechanism is available for other purposes
> too, just take a look at supp-lan.tex
My first impression is that a few and may be the most important
breakpoint issues are
met.
> >"- allow hyphenation here, but do not disallow elsewhere, as \"
>
> ||
My typo, sorry: "- contrasts to \- and does not produce anything when
not at a line break. || always produces a hyphen glyph.
> > does, used in OT1 encoded text containing e.g. umlauts
> >"" insert \discretionary{}{}{} (empty breakpoint) here,
> > used after solidi (/)
>
> |/| |)| |(|
Ahem, I meant only the solidus, not the parens. Taking the german.sty
example, I want Ein"~/""Ausgang to become Ein-/¦Ausgang (the ¦
indicating the only breakpoint).
> || |-| |~| |--| |hello world|
The active vertical bar trick seems to be rather flexible, but I am not
yet sure if I can do a simple mapping that supports all features
(deepingly hidden in quite some texts). I'll try to dig into
supp-lan.tex later, 'though it does not seem to have typesettable docs.
In case you're interested, germanb.dtx in babel provides English
documentation to what I was talking about.
Something like this may be right, but it produces a lot of errors (I
inserted before \starttext, maybe just catcode problems:
\installcompoundcharacter "-
{\prewordbreak\discretionary{-}{}{}\postwordbreak}
\installcompoundcharacter ""
{\prewordbreak\allowbreak\postwordbreak}
\installcompoundcharacter "|
{\prewordbreak\discretionary{-}{}{\thinspace}\postwordbreak}
\installcompoundcharacter "~
{\hbox{\compoundhyphen}}
\installcompoundcharacter "=
{\prewordbreak\hbox{\compoundhyphen}\allowbreak\postwordbreak}
Karsten
--
Karsten Tinnefeld tinnefeld@ls2.cs.uni-dortmund.de
Fachbereich Informatik, Lehrstuhl 2 T +49 231 755-4737
Universität Dortmund, D-44221 Dortmund, Deutschland F +49 231 755-2047
next reply other threads:[~1999-11-15 18:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-15 18:34 Karsten Tinnefeld [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-11-15 19:23 Berend de Boer
[not found] <Your message of "Mon, 15 Nov 1999 12:40:31 +0100." <3.0.6.32.19991115124031.010f2a90@pop.wxs.nl>
1999-11-15 14:31 ` Karsten Tinnefeld
1999-11-15 17:28 ` Hans Hagen
1999-11-13 15:01 Berend de Boer
1999-11-15 11:40 ` Hans Hagen
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=199911151834.TAA13046@goedel.cs.uni-dortmund.de \
--to=tinne@goedel.cs.uni-dortmund.de \
/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).