9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: tlaronde@polynum.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Octets regexp
Date: Thu,  2 May 2013 17:08:29 +0200	[thread overview]
Message-ID: <20130502150829.GA435@polynum.com> (raw)
In-Reply-To: <d2252bd65147f2caa38a56333366f813@9srv.net>

On Thu, May 02, 2013 at 10:58:30AM -0400, a@9srv.net wrote:
>
> i think the answer is just "no, there's no way to do that today".
> and i'd strongly advise keeping that tool as far away from any
> discussion of localization or character sets or runes or the like.
> there's oughtn't be any mode switching or the like: it's utf-8
> encoded unicode runes, or it's binary, not characters at all.
>

But that is exactly my point: to have localization far from regexp.
Regexp taking simply a string of bytes and matching strings of bytes.
(The main advantage of UTF-8 is not, for me, Unicode (UTF-8 could
survive being an encoding for something else than Unicode), but
precisely that it is still strings of octets, and that the system
can be left alone, far from localization.)

This is a side effect of not Unicode (UTF-8) aware tools to be able to
be used with whatever string of bytes since no interpretation is done.

One could even imagine using regexp to find a pattern in an image (even
a sed like program, trying to math a first row pattern, and then looking
for the following rows if some patterns are matched too).

--
        Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
                      http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C



  reply	other threads:[~2013-05-02 15:08 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-02 12:38 tlaronde
2013-05-02 12:48 ` erik quanstrom
2013-05-02 13:25   ` tlaronde
2013-05-02 13:43     ` Tristan
2013-05-02 14:19       ` Tristan
2013-05-02 14:51       ` tlaronde
2013-05-02 15:02         ` Bence Fábián
2013-05-02 15:20           ` tlaronde
2013-05-02 15:27             ` erik quanstrom
2013-05-02 15:10         ` Kurt H Maier
2013-05-02 15:21           ` tlaronde
2013-05-02 13:44     ` erik quanstrom
2013-05-02 14:43       ` tlaronde
2013-05-02 14:58     ` a
2013-05-02 15:08       ` tlaronde [this message]
2013-05-02 15:19         ` erik quanstrom
2013-05-02 15:31           ` tlaronde
2013-05-02 16:53             ` erik quanstrom
2013-05-02 18:59               ` tlaronde
2013-05-02 18:45           ` dexen deVries
2013-05-02 19:04             ` tlaronde
2013-05-02 19:22               ` erik quanstrom
2013-05-02 19:39                 ` tlaronde
2013-05-02 20:13                   ` erik quanstrom
2013-05-02 20:17                   ` 9p-st
2013-05-03 11:16                     ` tlaronde
2013-05-03 13:15                       ` Tristan
2013-05-03 16:33                         ` tlaronde
2013-05-02 16:16 ` tlaronde

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=20130502150829.GA435@polynum.com \
    --to=tlaronde@polynum.com \
    --cc=9fans@9fans.net \
    /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).