From: "Ulrich Dirr" <ud@art-satz.de>
To: "'mailing list for ConTeXt users'" <ntg-context@ntg.nl>
Subject: Re: extended dictionary / hyphenation patterns
Date: Wed, 12 Dec 2007 17:53:59 +0100 [thread overview]
Message-ID: <006901c83cdf$992b8980$14b2a8c0@DOMINUS> (raw)
In-Reply-To: <475FEF8C.3090907@wxs.nl>
> Steffen Wolfrum wrote:
>> Am 11.12.2007 um 16:16 schrieb Hans Hagen:
>>
>>> Steffen Wolfrum wrote:
>>>> Hi,
>>>>
>>>> I guess German is famous for its monstrous compound words ;o(
>>>>
>>>> So I have a manually collected lists of hyphenation patterns (like
>>>> "\hyphenation{Selbst-kon-troll-ein-rich-tung}").
>>>> This I'd like to keep as a two separate files: on for usage with
>>>> the body-text set in \mainlanguage[deo] and one for
>>>> \mainlanguage[de].
>>>>
>>>> Is there a handy way to automatically assign and include one of
>>>> these files (HyPold and HyPnew) to the usage of the respective
>>>> \mainlanguage [deo] and [de] ?
>>> you can copy them to lang-de.hyp
>>
>>
>> this looks like a clean way (assigns automatically with the chosen
>> \mainlanguage).
>>
>> by default lang-de.hyp is empty ... does this indicate that it is
>> actually meant for user entries?
>
> no, it means that the german patterns are perfect -)
>
> Hans
Will luatex go the standard TeX hyphenation way or will you try to do it
better? Especially for german the hyphenation based on those patterns
does not work very well (btw the same is true for british english). My
dream would be to see a solution where we have main/prefered break
points and optional break points (of course we will never find a
solution for everything, like semantically different words but with same
orthography) ...
btw another question: will luatex interpret ligature rules which are
language specific? At least from otf fonts?
Ulrich
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2007-12-12 16:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 13:52 Steffen Wolfrum
2007-12-11 15:16 ` Hans Hagen
2007-12-12 10:50 ` Steffen Wolfrum
2007-12-12 10:53 ` Taco Hoekwater
2007-12-12 12:17 ` Steffen Wolfrum
2007-12-12 13:31 ` Steffen Wolfrum
2007-12-12 14:26 ` Hans Hagen
2007-12-12 16:53 ` Ulrich Dirr [this message]
2007-12-12 19:35 ` Mojca Miklavec
2007-12-12 21:29 ` 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='006901c83cdf$992b8980$14b2a8c0@DOMINUS' \
--to=ud@art-satz.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).