nmh-workers
[Top] [All Lists]

Re: [Nmh-workers] mhshow: unable to convert character set of...

2015-02-14 11:54:18
Thus said Ralph Corderoy on Sat, 14 Feb 2015 11:07:47 +0000:

I think I'm in that set too; regular ed and dc user. :-)

Excellent.  I  use  ed  on  occasion (when  vi  is  not  available)  but
definitely dc is  my calculator of choice. It's  disappointing that some
Linuxes  don't install  dc/ed by  default  anymore, but  they aren't  my
primary system anyway.

I think  most of us would  prefer the library,  and code to use  it is
already written. :-) Plus, with the world that matters, e.g. not Java,
moving evermore to UTF-8, a lot of the time it isn't needed.

I  didn't mean  to suggest  it as  an option  for everyone,  just as  an
option. This may be unnecessary,  however, if some of the aforementioned
improvements  were   made  (e.g.  try  encoding   change  and  character
substitution upon failure; though here again).

As a Unix fan, would it help you consider switching from C to UTF-8 if
you knew its history, if you  don't already. Ken Thompson and Rob Pike
cooked it up in  a cafe close to Murray Hill to  fix the problems with
the original UTF.

Actually, I  am familiar  with how  UTF-8 came  about---it really  was a
quite impressive arrangements of bit placement. I wont't mind reading it
again. :-)

so I can `C grep ...' when needed.

Wow,  yes, grep  was one  of the  primary reasons  why I  disabled UTF-8
support on  the systems  that I use.  One day grep  matched a  number of
things that I didn't  expect it to match and I  spent all morning trying
to figure  out why.  When I  discovered it was  because my  encoding was
en_US.UTF-8, I switched  to C. This is definitely  something to consider
(using a wrapper to help grep).

Thanks,

Andy
-- 
TAI64 timestamp: 4000000054df8be0



_______________________________________________
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

<Prev in Thread] Current Thread [Next in Thread>