From: "Berend de Boer" <berend@pobox.com>
Subject: RE: Expand cont-ger.tex
Date: Mon, 15 Nov 1999 20:23:15 +0100 [thread overview]
Message-ID: <00ae01bf2f9e$de183590$0321a8c0@bmach.nederware.nl> (raw)
> If I would make it default
> for dutch, it could break existing documents with normal "'s.
> Although, as long as one never uses " '' `` but \quote and
> \quotation instead, making " active is pretty safe.
What do people on this list think? I've used it for a few days now, and are
quite happy with it (now if I only could get the emacs spelling mode to
recognize "e life would be perfect).
Groetjes,
Berend. (-:
next reply other threads:[~1999-11-15 19:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-15 19:23 Berend de Boer [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-11-15 18:34 Karsten Tinnefeld
[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='00ae01bf2f9e$de183590$0321a8c0@bmach.nederware.nl' \
--to=berend@pobox.com \
/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).