From: Bob Proulx <bob@proulx.com>
To: help-gnu-emacs@gnu.org
Subject: Re: bulk replacement on region, buffer, file?
Date: Thu, 10 Dec 2015 09:40:37 -0700 [thread overview]
Message-ID: <20151210093628551131702@bob.proulx.com> (raw)
In-Reply-To: <87vb87t55n.fsf@pobox.com>
Tom Roche wrote:
> I would appreciate pointers to code that enables "bulk replacement"
> of numerous string tuples ({to-replace, replace-with}) in a single
> call. What I mean, why I ask:
To handle the UTF-8 translations I like 'iconv'. It handles many
different types of transliterations.
$ echo '“foo”' | iconv -f UTF-8 -t ASCII//TRANSLIT
"foo"
If it were me I would do a first pass using iconv to transliterate
characters in the first pass and then perform the other replacements
you want in a second pass.
Bob
next prev parent reply other threads:[~2015-12-10 16:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 2:21 bulk replacement on region, buffer, file? Tom Roche
2015-12-10 3:21 ` Emanuel Berg
2015-12-10 16:40 ` Bob Proulx [this message]
[not found] <mailman.1767.1449714096.31583.help-gnu-emacs@gnu.org>
2015-12-10 3:13 ` Pascal J. Bourguignon
2015-12-15 4:16 ` Tom Roche
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151210093628551131702@bob.proulx.com \
--to=bob@proulx.com \
--cc=help-gnu-emacs@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).