Re: utf-8 display problem index vs. pager
On Mon, Jan 07, 2002 at 08:50:16PM +0100, Michael Wagner wrote: On Sonntag, 06. Jan. 2002 at 20:53:24, MuttER wrote: On Tue, Dec 18, 2001 at 08:30:05PM +0530, Prahlad Vaidyanathan wrote: mailcap text/html; w3m -T text/html %s /mailcap You could also add a 'copiousoutput' at the end of that, and set auto_view text/html in your muttrc to put w3m's output into your pager. pv. ---end quoted text--- text/html; w3m -dump -T text/html %s; copiousoutput above works well for me (using auto_view) Hello MuttER, I have this in my mailcap file: text/html; html2text %s; copiousoutput; nametemplate=%s.html because the output is much better than this lynx or w3m. Try it. ---end quoted text--- I agree that SOME of the output is much better. I like the blank lines separating paragraphs that is retained by w3m better, though. I believe they it make the document easier to read. I will use html2text for a while (maybe for an extended period :^) ) and give it more than a cursory examination. tks -- Pat Shanahan Registered Linux User #207535 Registered at: http://counter.li.org
Re: utf-8 display problem index vs. pager
On Sonntag, 06. Jan. 2002 at 20:53:24, MuttER wrote: On Tue, Dec 18, 2001 at 08:30:05PM +0530, Prahlad Vaidyanathan wrote: mailcap text/html; w3m -T text/html %s /mailcap You could also add a 'copiousoutput' at the end of that, and set auto_view text/html in your muttrc to put w3m's output into your pager. pv. ---end quoted text--- text/html; w3m -dump -T text/html %s; copiousoutput above works well for me (using auto_view) Hello MuttER, I have this in my mailcap file: text/html; html2text %s; copiousoutput; nametemplate=%s.html because the output is much better than this lynx or w3m. Try it. CU Michael -- If God had intended Man to Watch TV, He would have given him Rabbit Ears. msg22515/pgp0.pgp Description: PGP signature
Re: utf-8 display problem index vs. pager
On Tue, Dec 18, 2001 at 08:30:05PM +0530, Prahlad Vaidyanathan wrote: Hi, On Tue, 18 Dec 2001 Stephan Seitz spewed into the ether: [-- snip --] PS: How do you call w3m to display html mails? mailcap text/html; w3m -T text/html %s /mailcap You could also add a 'copiousoutput' at the end of that, and set auto_view text/html in your muttrc to put w3m's output into your pager. pv. ---end quoted text--- text/html; w3m -dump -T text/html %s; copiousoutput above works well for me (using auto_view) -- Pat Shanahan Registered Linux User #207535 Registered at: http://counter.li.org
Re: utf-8 display problem index vs. pager
Hi! On Mon, Dez 17, 2001 at 08:37:24 +0100, Cristian wrote Accepts UTF-8 only if you set $LC_ALL correctly. My point was that all the programs I listed worked fine after I just set $LANG. vim works fine here. If I set LANG=de_DE.UTF-8 the other variables get the same value as well. Normaly I set LANG=de_DE.UTF-8 and LC_CTYPE=ja_JP.UTF-8 to get a working XIM. Hm, two problems exist until now: German gpg messages aren't display correctly, Is this problem generally known? If not, please provide details. Your mail (like others): [-- PGP-Ausgabe folgt (aktuelle Zeit: Die 18 Dez 2001 09:39:19 CET) --] gpg: Unterschrift vom Mon 17 Dez 2001 20:37:24 CET, RSA Schl\374ssel ID A1938DAD gpg: Schl\374ssel A1938DAD von wwwkeys.de.pgp.net wird angefordert ... gpg: Schl\374ssel ist beim Schl\374sselserver nicht erh\344ltlich: eof gpg: Unterschrift kann nicht gepr\374ft werden: \326ffentlicher Schl\374ssel nicht gefunden [-- Ende der PGP-Ausgabe --] I think, it is gnupg's fault for not being utf8-usable. But .gnupg/options contains the line charset utf-8. Shade and sweet water! Stephan PS: How do you call w3m to display html mails? -- | Stephan Seitz E-Mail: [EMAIL PROTECTED] | | WWW: http://fsing.fs.uni-sb.de/~stse/| | PGP Public Keys: http://fsing.fs.uni-sb.de/~stse/pgp.html | msg21704/pgp0.pgp Description: PGP signature
Re: utf-8 display problem index vs. pager
Hi, On Tue, 18 Dec 2001 Stephan Seitz spewed into the ether: [-- snip --] PS: How do you call w3m to display html mails? mailcap text/html; w3m -T text/html %s /mailcap You could also add a 'copiousoutput' at the end of that, and set auto_view text/html in your muttrc to put w3m's output into your pager. pv. -- Prahlad Vaidyanathan [EMAIL PROTECTED]What, me worry ? http://www.symonds.net/~prahladv/Don't Panic ! -- msg21727/pgp0.pgp Description: PGP signature
Re: utf-8 display problem index vs. pager
Hi! On Sat, Dec 15, 2001 at 04:00:03PM +0100, Cristian wrote browsers: w3m-m17n (with autoconversion from `any' other character set), lynx (works with UTF-8 and iso-8859-1, at least) Strange, never w3m nor lynx can correctly display http://fsing.fs.uni-sb.de/~stse/manga.html. But w3mmee does. editors: emacs-20.7 (oc-patched) (only as X app, not with -nw), mined, nano (partially), pico (but not 'pine -F' -- weird!) vim since 6.0. Edmund GRIMLEY EVANS had a Mutt-UTF-8 patch for earlier Mutt 1.3.x at http://www.rano.org/mutt.html which now seems to be obsolete, though some people may still need his patched slang-1.4.4 (I use ncurses 5.2, so I don't need slang). Do you have ncurses compiled with wide-char-support, and mutt is link againts libncursesw.so.5.2? The standard ncurses never really worked for me, but now Debian has the slang-utf8 package in testing, so it works fine with mutt. OK folks, time to switch to UTF-8! Hm, two problems exist until now: German gpg messages aren't display correctly, so are html mails (displayed with lynx, usr/bin/lynx -force_html -dump '%s'). w3mmee works (w3mmee %s), but links within the mail are lost. Any hints? Shade and sweet water! Stephan -- | Stephan Seitz E-Mail: [EMAIL PROTECTED] | | WWW: http://fsing.fs.uni-sb.de/~stse/| | PGP Public Keys: http://fsing.fs.uni-sb.de/~stse/pgp.html | msg21656/pgp0.pgp Description: PGP signature
Re: utf-8 display problem index vs. pager
Hi Stephan!
On Mon, Dec 17, 2001 at 11:38:45AM +0100, Stephan Seitz wrote:
Strange, never w3m nor lynx can correctly display
http://fsing.fs.uni-sb.de/~stse/manga.html. But w3mmee does.
Plain w3m had wide character support only the for Japanese character
sets Shift_JIS, EUC_JP, and ISO-2022-JP.
In order to view UTF-8, you need to get the w3m-m17n patch from
http://www2u.biglobe.ne.jp/%7Ehsaka/w3m/
w3mmee is an independent patch for the same purpose.
Lynx has a setting for this. My ~/.lynxrc contains the line,
character_set=UNICODE (UTF-8)
Though I hardly use it now that there's w3m.
vim since 6.0.
Accepts UTF-8 only if you set $LC_ALL correctly. My point was that all
the programs I listed worked fine after I just set $LANG.
Do you have ncurses compiled with wide-char-support, and mutt is link
againts libncursesw.so.5.2?
The standard ncurses never really worked for me, but now Debian has
the slang-utf8 package in testing, so it works fine with mutt.
I have ncurses compiled by SuSE for their distro v7.2. The Mutt I built
myself is linked against libncurses.so.5. I don't have libncursesw.so.5.2.
Hm, two problems exist until now:
German gpg messages aren't display correctly,
Is this problem generally known? If not, please provide details.
Greetings from Saarbruecken,
Cristian
--
}{ Cristian Pietsch
}{ http://www.interling.de
msg21692/pgp0.pgp
Description: PGP signature
Re: utf-8 display problem index vs. pager
On Mon, 17 Dec 2001, Cristian wrote: Hi Stephan! On Mon, Dec 17, 2001 at 11:38:45AM +0100, Stephan Seitz wrote: Strange, never w3m nor lynx can correctly display http://fsing.fs.uni-sb.de/~stse/manga.html. But w3mmee does. Plain w3m had wide character support only the for Japanese character sets Shift_JIS, EUC_JP, and ISO-2022-JP. In order to view UTF-8, you need to get the w3m-m17n patch from http://www2u.biglobe.ne.jp/%7Ehsaka/w3m/ w3mmee is an independent patch for the same purpose. Lynx has a setting for this. My ~/.lynxrc contains the line, character_set=UNICODE (UTF-8) Though I hardly use it now that there's w3m. That works better with the libncursesw. I added a few sample files for UTF-8 as I was testing. w3m itself doesn't do very well on those - you must be referring to one of the patched w3m packages. (I looked into setting one up, but it seemed geared solely toward CJK support). Do you have ncurses compiled with wide-char-support, and mutt is link againts libncursesw.so.5.2? The standard ncurses never really worked for me, but now Debian has It wasn't designed to do this (nor in fact is the standard slang package). the slang-utf8 package in testing, so it works fine with mutt. I have ncurses compiled by SuSE for their distro v7.2. The Mutt I built myself is linked against libncurses.so.5. I don't have libncursesw.so.5.2. I don't think anyone is packaging it. Debian may (it's mostly a matter of people finding time). -- T.E.Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: utf-8 display problem index vs. pager
Hi Mutt users,
now that Robert has brought up the issue, I'd like to describe my own
adventures in the field of Unicode/UTF-8. Short answer, try setting:
export LC_ALL=de_DE.UTF-8
export LANG=de_DE.UTF-8
(bash syntax). If you want your apps to `speak' German. Replace de_DE
by en_GB or en_US if you prefer English.
On Sat, Dec 15, 2001 at 02:26:57AM +0100, Robert Joop wrote:
i've got a utf-8 display problem.
in the pager, everything looks ok, but in the index, non-ASCII characters
don't show up (a space appears instead).
The thing that puzzled me for a long time was that setting $LANG was
enough to make many UTF-8 apps work perfectly in a wide-char enabled,
recent 'xterm -u8'. Except for Mutt. Some examples that worked for me:
browsers: w3m-m17n (with autoconversion from `any' other character set),
lynx (works with UTF-8 and iso-8859-1, at least)
pagers: less, more (partially)
editors: emacs-20.7 (oc-patched) (only as X app, not with -nw), mined,
nano (partially), pico (but not 'pine -F' -- weird!)
When all this already worked, my Mutt did not even display UTF-8 chars
in the index. Today I found out that I have to set LC_ALL=de_DE.UTF-8
as well. That did the trick. You do not have to set charset in your
~/muttrc.
Edmund GRIMLEY EVANS had a Mutt-UTF-8 patch for earlier Mutt 1.3.x at
http://www.rano.org/mutt.html
which now seems to be obsolete, though some people may still need his
patched slang-1.4.4 (I use ncurses 5.2, so I don't need slang).
I will tell him about today's success with an unpatched Mutt 1.3.24i
on Linux 2.4.4-4GB (SuSE 7.2).
The real cool thing about this Mutt in a UTF-8 locale is that even
those quirky Windows-1252 characters I complained about some time ago
are finally displayed correctly. So where iconv refused to make
approximating translations from Windows-1252 to ISO-8859-1, it
succeeds translating from Windows-1252 to Unicode (and on to UTF-8).
OK folks, time to switch to UTF-8!
Cristian
--
}{ Cristian Pietsch
}{ http://www.interling.de
msg21619/pgp0.pgp
Description: PGP signature
