From: Luca Ferrari <fluca1978@infinito.it>
To: linux-admin@vger.kernel.org
Subject: Re: graphic chars, set-font and sed
Date: Wed, 20 Apr 2005 18:46:07 +0200 [thread overview]
Message-ID: <200504201846.07602.fluca1978@infinito.it> (raw)
In-Reply-To: <16990.54990.383320.531930@gargle.gargle.HOWL>
On Thursday 14 April 2005 22:47 Glynn Clements's cat walking on the keyboard
wrote:
> > Second, I've noticed that sed regular expressions get
> > confused by the presence of multiple semigraphic chars, while a single
> > one seems to work ok. Does anybody knows a way to "escape" those chars,
> > in order to make them understandable to sed and other programs?
>
> sed itself should be 8-bit clean; are you sure that this isn't an
> encoding (e.g. ISO-8859-1 vs UTF-8) issue?
I don't know what you mean with "encoding issue". How can I discover it?
Luca
--
Luca Ferrari,
fluca1978@infinito.it
next prev parent reply other threads:[~2005-04-20 16:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-12 16:25 graphic chars, set-font and sed Luca Ferrari
2005-04-12 16:44 ` Jens Knoell
2005-04-14 20:47 ` Glynn Clements
2005-04-20 16:46 ` Luca Ferrari [this message]
2005-04-21 15:34 ` Glynn Clements
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=200504201846.07602.fluca1978@infinito.it \
--to=fluca1978@infinito.it \
--cc=linux-admin@vger.kernel.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 NNTP newsgroup(s).