Biblical Hebrew Forum

["Karl Randolph" <kwrandolph AT email.com>]

Peter:

Back on list.

I have been using this account for years, and only in B-Hebrew 
have I received complaints of mangled reception. But then it 
is also the only place where I have attempted extensive 
transmission of other than ASCII messages. The two may be 
related. I don't know if they are related.

Second, is the archiving software at ibiblio limited to 
correctly encoded MIME messages? State it right out, don't 
beat around the bush saying that html messages or other such 
are produced by buggy programs. Then it is a feature, not a 
bug, when it mangles non-MIME encoded messages, and non-MIME 
text strings within messages. State it clearly that a MIME 
complient mail program must be used and stop these bug 
accusations if MIME is a requirement. If MIME is not a 
requirement, then those are bugs.

Karl W. Randolph.

----- Original Message -----
From: "Peter Kirk" <peterkirk AT qaya.org>

> 
> On 16/07/2005 00:34, Karl Randolph wrote:
> 
> > Peter:
> >
> > For the last time, LOOK AT THE PAGE SOURCE. What you sent is NOT 
> > what is in the archive. Obviously you have not looked at the page 
> > source. ...
> >
> >
> 
> What page source do you want me to look at? If you mean the page 
> source of 
> https://lists.ibiblio.org/sympa/arc/b-hebrew/2005-July/023703.html, 
> there I see the following:
> 
> > Example of properly encoded Hebrew characters (in Windows-1255 encoding):
> > &#1488;&#1489;&#1490;&#1491;
> >
> >
> >
> The last line of this looks to me like ampersand, "#1488;" and 
> similar repeated four times, just in case your mail software messes 
> this up. And this is the correct way of encoding the Hebrew 
> characters which I sent, transformed from Windows-1255 encoding 
> which I originally sent into the HTML of the archives, for here, IN 
> HTML SOURCE, these are valid character entities.
> 
> And then a little further on I see:
> 
> > ampersand, hash, four digits and a semicolon:
> >
> >
> > &#1488;&#1489;&#1490;&#1491;
> >
> 
> The last line of this looks to me like ampersand, "amp;#1488;" and 
> similar repeated four times. And this last line is the correct way, 
> IN HTML SOURCE which this is, of encoding strings of characters 
> each consisting of ampersand, hash, four numbers and a semicolon. 
> The ampersand has to be replaced by ampersand followed by "amp;" as 
> otherwise IN HTML SOURCE this will be misunderstood as a character 
> entity, which it is not.
> 
> The encoding of what I sent has been changed, a valid operation for 
> an archiving program, but the content has not been changed.
> 
> > Karl W. Randolph.
> >
> >
> 
> 
> -- Peter Kirk
> peter AT qaya.org (personal)
> peterkirk AT qaya.org (work)
> http://www.qaya.org/