[Alpine-info] Alpine is converting ? to ??

[M.RossARR]

This message uses email standard character set UTF-8 per RFC 2130!
------------------------------------------------------------------

> On Tue, 10 Mar 2009, Barry Landy wrote:

>

> > On Tue, 10 Mar 2009, Mark Crispin wrote:

> > I do my best to try to get the word out.  Death to ISO-8859-1.

> > Death to all charsets other than UTF-8.

>

> As one of the (many) people involved in the long slow and difficult

> argument that in the end resulted in Unicode (UTF-8) I can only applaud.

> ...

> Maybe US government agencies need to be tackled.


I hope you are not suggesting a gov't law, rule, regulation, policy,
etc. Please leave gov't out of it other than to get them to use
correct character sets & standards. At least the US Gov seems to use
US-ASCII for simple messages like we create here on the forum, &
even subscriptions - not one of the other sets. Which may not help
European languages or names, but .... Don't ask gov't for more laws,
rules, policy, or otherwise. Not for inet! Enough Tyranny! Please!

Good explanation from Mark - Thanks Again!

We Pine/Alpine users, the private sector, & whoever, can do it if we
spread the word. We contact every pubs house we subscribe to & any
we find as we go along. I did not know about this until Mark told
me!  Where would I learn this?  I do not find it in help files for
software setup & config! Not in Pine/Alpine docs anywhere I can
discover & this software suffers the most with the problem it seems!
It should be added to all communications software in a setup notice
anyway, with contingency of where to find any future updates! At
least a warning for the user to find out & learn!

With my many years experience on the inet, some computer programming
work, some communications work, webpage building, & many software
packages for communications, I was never informed to use standard
character sets for communications. Other than the obvious US-ASCII,
as opposed to some bazaar foreign set. Yet I knew the character sets
were there & different, use of them was never discussed in any
circle I entered.

I am contacting the source of every email I get, that is not UTF-8,
to notify them, & get them to convert. I doubt many know! I am set
for UTF-8 now, but I see US-ASCII in the header of the message I
reply to - no ref to UTF-8.

I would set notice on every webpage, in every email (like I just
added above via template) for a period of time anyway - not forever,
but to notice everybody, that the correct character set to use is
UTF-8 for email. Or somebody write up an appropriately written
notice & send it out. I will use it! And if somebody, Mark, holds a
copy of RFC 2130, & can please post the appropriate cite from
within, on this forum & Pine, notify everybody with the actual cited
document & quote! I will forward it! I am sure other Pine/Alpine
users would appreciate it!

Eventually with that standarized notice & complaining to all the
subscription pubs, or houses like Google, there will be a change! I
would bet it happens fast once notified by many People! Messed up
email & pubs is not what pubs houses want! They want readers happy!

I just though about the users that are blind! How does this effect
them - the speech box?  How does it convert weird characters?


> > > On Tue, 10 Mar 2009, M.RossARR wrote:

> > > Then there is the Windows-1252 crowd!

> >

> > Wenn ich "Windows-1252" hoere, entsichere ich meinen Browning!


That forbidden character set Mark wants to shoot me for mentioning -
so I won't (oops - too late!), I discover inside UTF-8 or ISO-8859-1
or whatever pubs I receive, quite a few. I hold numerous examples
here. Fix that problem? - Ha! People are sloppy mixing sets!

HTML document production & export from composer software of a Text
version for multipart seems questionable at best! Pine/Alpine cannot
handle that sloppiness. That is the big problem I see using
Pine/Alpine. Senders of email must be typing up their email in some
editor using a character set different from the email client/webpage
software, then porting it to the communications software in UTF-8 or
ISO-8859-1 or whatever, to send. So character sets are getting mixed
& the results is jibberish. Graphical communications software seems
to take anything, but usually the HTML version is default for them
anyway, so few People may see the Text jibberish! Pine/Alpine
exposes it! I cannot think of a work-around!

But No Gov't Intervention Please!

--
The Best to You & Yours,
M. Ross All Rights Reserved
mrossarr at nixsyspaus.org
subj-pw: tellross
mrossarr.nixsyspaus.org/

---end-of-message---