From: Ico Doornekamp <sup@zevv.nl>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Non-english outlook block quote regexp
Date: Fri, 28 Jan 2011 10:24:22 +0100 [thread overview]
Message-ID: <1296206571-sup-1285@pruts.nl> (raw)
In-Reply-To: <1296140298-sup-9582@midna.zekjur.net>
* On Thu Jan 27 16:00:10 +0100 2011, Michael Stapelberg wrote:
> Excerpts from Tero Tilus's message of 2011-01-27 14:29:22 +0100:
> > Prolly safe, but it misses german Outlook quote
> We also discussed this on IRC. Ico came up with a list of a few more
> (localized) messages. I suggested the most pragmatic solution: keeping
> this list around with a comment to send patches if anybody stumbles
> upon a new localized version of it.
Yes, that's probably the most pragmatic way to go. It's a shame that MUA
type A is forced to keep a list of possible ramblings of MUA type B to
do it's work, but that's the way it is.
--
:wq
^X^Cy^K^X^C^C^C^C
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2011-01-28 9:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 13:12 Ico Doornekamp
2011-01-27 13:29 ` Tero Tilus
2011-01-27 15:00 ` Michael Stapelberg
2011-01-28 9:24 ` Ico Doornekamp [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=1296206571-sup-1285@pruts.nl \
--to=sup@zevv.nl \
--cc=sup-talk@rubyforge.org \
/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