For Dave Balderstone - encoding format mac-roman

Dave, for some reason every time I try to read one of your postings, it tells me

Invalid coding system: mac-roman

Aparently, the Mac uses a non-standard encoding for the upper 128 single-byte characters.

I have to research this and try to find a solution. I just wanted you to know, because others may have similar issues.

Reply to
Maxwell Lol
Loading thread data ...

No, not true

Reply to
Ralph E Lindberg

Just checked the news spool on my system. Dave's posts don't include "mac-roman" anywhere in them. I'd guess that your newsreader is trying to make a guess and getting it wrong.

His key details seem to be: Content-Type: text/plain; charset=Macintosh Content-Transfer-Encoding: 8bit which don't raise any flags in my weary brain.

Reply to
Drew Lawson

Same thing - According to

formatting link
>The Internet Assigned Numbers Authority identifies this encoding >using the string "macintosh." The MIME Content-Type for this encoding >is therefore "text/plain; charset=macintosh". Mac OS Roman is also >referred to as MacRoman or the Apple Standard Roman character set. >With the release of Mac OS X, Mac OS Roman was replaced by UTF-8 as >the standard character encoding for the Macintosh operating system. It's a special font, and I don't have that font on my computer.

Reply to
Maxwell Lol

Why don't your headers reveal your newsreader?

I'd suggest the problem's at your end/ It certainly isn't at mine. And with you hiding everything, there's no way for anyone to troubleshoot it.

And, sorry, I have no interest in troubleshooting your unknown news reader for you.

Reply to
Dave Balderstone

Maxwell, if your newsreader shows something other than that, it's because your newsreader is AFU.

Roger that.

Reply to
Doug Miller

I use GNUS on a Linux system.

That's glorb that is doing it. On my old NNTP server (rr.com), it published the version of emacs/GNUS I use. emacs 22.1.1 GNUS v5.11

Reply to
Maxwell Lol

I posted a question on gnu.emacs.gnus today - hoping for a response. I tried to find a solution a few months ago. No luck. I'll try again. Apparently it's not a common problem

Reply to
Maxwell Lol

So both your news provider and your newsreader are hooped.

Good luck sorting it out.

Reply to
Dave Balderstone

The only problem is that I can't read your posts using emacs in a text window. (I don't always have access to a remote XWindows client). I have to be on the local LAN and use Xemacs. So it's not that big a deal.

Reply to
Maxwell Lol

The rest of us can read his posts just fine; suggest you evaluate the implications of that regarding *your* difficulty. :-)

Reply to
Doug Miller

It's not really that important to me. I only mentioned it in case others had the problem.

Reply to
Maxwell Lol

With this client I have four options for transliteration:

None (my current setting) ISO 8559-1 ISO 8559-15 UTF8

I've set this message to UTF8. Let me know if it makes a difference.

Reply to
Dave Balderstone

UTF8 is fine! It's one of the standards. If it makes no difference to you, it would improve your readability by others (I may be the only one.....). Thanks!

Reply to
Maxwell Lol

Everything's going unicode anyway, it's no problem for me to switch the defaults here.

Merry Christmas!

Reply to
Dave Balderstone

Got to love that editor!

Been in use for 20 years or thereabouts. I finally got a manual one day when I needed to cut columns and then paste.

Win tools are great for rows or lines.

I got the 6th versi> Dave Balderst>

Reply to
Martin H. Eastburn

InspirePoint website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.