<<< Date Index >>>     <<< Thread Index >>>

Re: Demoroniser (was: Display Filters)



On 2006-07-07, Alain Bench <veronatif@xxxxxxx> wrote:
>  On Thursday, July 6, 2006 at 11:15:45 -0700, Gary Johnson wrote:
> 
> > iconv: (stdin): cannot convert
> 
>     Argl! I think I maybe get what?s happening. You have libiconv
> installed, and any checks will for sure show it works OK. But Mutt
> doesn?t use it?

After sending my previous reply, I noticed some inconsistencies 
between the behavior of iconv on the command line and mutt's 
character conversion.  For one thing, after I 'set 
display_filter=""' for this list, the apostrophes in your recent 
replies (as in the paragraph quoted above) appear as '\222', even 
with 'charset="iso-8859-1//TRANSLIT"', and even though

    $ printf "\222\n" | iconv -f windows-1252 -t iso-8859-1//TRANSLIT

works (i.e., displays an apostrophe whose octal value is 264).  I 
did some further investigation and discovered, among other things, 
this:

$ ldd /home/garyjohn/bin/SunOS/mutt
        libsocket.so.1 =>        /usr/lib/libsocket.so.1
        libnsl.so.1 =>   /usr/lib/libnsl.so.1
        libc.so.1 =>     /usr/lib/libc.so.1
        libdl.so.1 =>    /usr/lib/libdl.so.1
        libmp.so.2 =>    /usr/lib/libmp.so.2
        /usr/platform/SUNW,Sun-Fire-V240/lib/libc_psr.so.1

No libiconv!

So I have built and installed locally GNU libiconv-1.9.2 and am in 
the process of building mutt-1.5.11, downloaded from www.mutt.org.  
I thought as long as I was going to reconfigure and rebuild mutt, I 
might as well get a more recent version, and if I build libiconv and 
iconv myself, I'll know what I have.

I also discovered that there are three iconv commands in my PATH:

    /opt/TWWfsw/bin/iconv
    /bin/iconv
    /usr/bin/iconv

(The last two are identical.)  So I have been using 
/opt/TWWfsw/bin/iconv for our tests, while I'm pretty sure that none 
of configure, make or mutt knew or know anything of the existence of 
the corresponding libraries /opt/TWWfsw/libiconv18/lib/ and 
/opt/TWWfsw/libiconv19/lib--neither is in $LD_LIBRARY_PATH.

I'll let you know what happens with this.  In the mean time...

>     Can you check? Temporarily add this to muttrc:
> 
> | set charset=iso-8859-1
> | charset-hook windows-1252 ansi-1252
> 
>     And describe and quote me back what you see here: ? ? ?

    And describe and quote me back what you see here: \200 \203 \211

I see the last three characters as their three-digit octal values, 
each preceded by a backslash.

>     The expected result is 3 question marks, if "ansi-1252" is really
> the SunOS-specific name for this charset.

Regards,
Gary

-- 
Gary Johnson                               | Agilent Technologies
garyjohn@xxxxxxxxxxxxxxx                   | Wireless Division
http://www.spocom.com/users/gjohnson/mutt/ | Spokane, Washington, USA