Gnus development mailing list
 help / color / mirror / Atom feed
From: Mats Löfdahl <lofdahl@sag.space.lockheed.com>
Subject: Re: 8 bits in citations (Was: Re: sgnus -> rgnus -> qgnus?)
Date: 17 Oct 1996 22:42:29 +0000	[thread overview]
Message-ID: <sda9195b4bu.fsf@sunbow.space.lockheed.com> (raw)
In-Reply-To: <x6d8ylnuxs.fsf@eyesore.no>

Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:

> 
> Mats Löfdahl <lofdahl@sag.space.lockheed.com> writes:
>
> > ...The "v" is an "ö" where the eighth bit has been zeroed, and I
> > guess the two backslashes is an escape sequence that should tell
> > you that that is what has happened.
> 
> Right.  I haven't seen that kind of encoding before.  What's it
> called?

As I tried to make apparent, I don't know very much about these
things, but I think the only place I've seen it is when my last name
has been corrupted in mail headers.  Maybe one could write some code
that scans the headers (or just the From header?) and replaces all
\\<x> sequences to \\<sethighbit(x)>.  But I guess one would like some
safe-guard against false hits.  Or maybe, as Per Abrahamsen pointed
out, one should try to encourage people to get software that doesn't
do the corrupting in the first place.  Anyway, this is really a very
small problem that I can easily live with.

> The normal 7-bit representation of "Löfdahl" (with ISO-646-SE) is
> "L|fdahl", I think.

Yes, that is what is sometimes called Swedish ASCII.  There is a
number of swedish people (me included) who read text without problem,
where }{|][\ are used for a-ring, a-twodots, o-twodots, A-ring,
A-twodots, O-twodots.

-- 
  Mats Löfdahl, Research Scientist -- Temp. phone number:  +1 415/424-4001
  Lockheed Martin, Advanced Technology Center
  c/o O/H1-12, B/252, 3251 Hanover Street, Palo Alto, CA 94304
  lofdahl@sag.space.lockheed.com, mlofdahl@solar.stanford.edu


  reply	other threads:[~1996-10-17 22:42 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-10-09  9:51 sgnus -> rgnus -> qgnus? Wesley.Hardaker
1996-10-09  9:56 ` Lars Balker Rasmussen
1996-10-09 10:25   ` Ariel Scolnicov
1996-10-09 11:35 ` Hans de Graaff
1996-10-10  7:18   ` Wesley.Hardaker
1996-10-10 14:12     ` Brent B. Powers
1996-10-11 10:43       ` Lars Magne Ingebrigtsen
1996-10-11 12:34         ` qgnus pronounciation Andy Eskilsson
1996-10-11 20:41         ` sgnus -> rgnus -> qgnus? Michael R Cook
1996-10-11 19:08       ` Roderick Schertler
1996-10-10 16:07 ` Mats Löfdahl
1996-10-10 16:49   ` C. R. Oldham
1996-10-11  7:03     ` Qcumber Andy Eskilsson
1996-10-11  6:49   ` sgnus -> rgnus -> qgnus? Wesley.Hardaker
1996-10-11 16:00     ` 8 bits in citations (Was: Re: sgnus -> rgnus -> qgnus?) Mats Löfdahl
1996-10-11 18:31       ` Colin Rafferty
1996-10-12 18:51       ` Lars Magne Ingebrigtsen
1996-10-14 17:58         ` Mats Löfdahl
1996-10-14 18:23           ` Per Abrahamsen
1996-10-14 20:37           ` Lars Magne Ingebrigtsen
1996-10-17 22:42             ` Mats Löfdahl [this message]
1996-10-19 18:30               ` Juliusz Chroboczek
1996-10-11  6:50   ` sgnus -> rgnus -> qgnus? Wesley.Hardaker

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=sda9195b4bu.fsf@sunbow.space.lockheed.com \
    --to=lofdahl@sag.space.lockheed.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).