From: David Antos <xantos@informatics.muni.cz>
Subject: Re: Czech compound word handling
Date: Wed, 2 Feb 2005 17:26:43 +0100 [thread overview]
Message-ID: <20050202162643.GA4247@erik.fi.muni.cz> (raw)
In-Reply-To: <4200EF97.7060507@seznam.cz>
On Wed, Feb 02, 2005 at 04:19:51PM +0100, Vit Zyka wrote:
> This mechanism is already present in the ConTeXt: use |_| like
> "bude|_|li". Unfortunately, AFAIK there are two drawbacks:
Hello,
this ispired an idea: would it be possible to make the characters
configurable? I.e. to have in fact || configurable for pre-break,
post-break, and no-break character? I think it might be generic enough
for most languages.
Say, we would have
\setuphyphenmark[.. = ..]
sign ... (for backwards compatibility, would set up all the following)
presign ...
postsign ...
nosign ...
D.A.
--
I am not a researcher, I am a key researcher!
prev parent reply other threads:[~2005-02-02 16:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-02 13:16 David Antos
2005-02-02 14:46 ` Hans Hagen
2005-02-02 14:59 ` David Antos
2005-02-02 15:21 ` Hans Hagen
2005-02-02 16:42 ` Vit Zyka
2005-02-02 15:19 ` Vit Zyka
2005-02-02 16:26 ` David Antos [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=20050202162643.GA4247@erik.fi.muni.cz \
--to=xantos@informatics.muni.cz \
--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).