From: Steffen Wolfrum <context@st.estfiles.de>
Subject: french hyphenation after l-apostrophe doesn't work
Date: Thu, 20 Jan 2005 17:38:50 +0100 [thread overview]
Message-ID: <a06002000be158aa7cc36@[83.176.134.91]> (raw)
Hi,
when, in a french project, the line ends with e.g. l'int\'{e}r^{e}t
then context doesn't hyphenate "l'interet" and the line gets stretched.
(If I wouldn't have the l-apostroph construction then the word is hyphenated "in-teret", so its hyphenation is know to TeX.)
But for I have a lot of this "l-apostroph" constructions at line endings in my document it is impossible to type individually \- at the best breaking points (here after "in-"). I need to have a global option that re-activates the hyphenation even if the word starts with l-apostroph.
When I typeset the apostrophe like a slash: l|'|int\'{e}r^{e}t
then the line gets broken, but after "l'" and I was told this is wrong in french.
So what else could be done to automatically break int\'{e}r^{e}t again but *not* after l' ?
Thank you for any help,
Steffen
next reply other threads:[~2005-01-20 16:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-20 16:38 Steffen Wolfrum [this message]
2005-01-20 18:08 ` Peter Münster
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='a06002000be158aa7cc36@[83.176.134.91]' \
--to=context@st.estfiles.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).