Re: How to get tin pager to display 'extended' characters

On Wed, Nov 29, 2006 at 12:50:13PM +0000, [email protected] wrote:
> > done via: "apt-get update ; apt-get install locales ; dpkg-reconfigure
> > locales") this can be done via:
> > 
> > (sh-style)
> > 	export LC_CTYPE=en_US
> > 
> > (csh-style)
> > 	setenv LC_CTYPE en_US
> > 
> > in your profile/shell-rc/...
> > 
> Ah, of course, yes, I'd forgotten that side of it.  However it's not
> quite so simple because it's on a BSD system and it doesn't have (for
> example) the locale command to find what locales are valid.
> 
> Setting LC_CTYPE to en_UK doesn't work for a start, it just complains
> about an invalid locale.
> 
> I will have to dig around I suspect (this isn't my system so I can't
> install stuff, it's a shell login on www.gradwell.net).
> 
Hmmmm, that doesn't seem to help any.

I have set:-

    export LC_CTYPE=en_GB.ISO8859-1

Which doesn't cause any error messages (whereas export LC_CTYPE=en_GB
does), but I still get ???????? in tin when displaying extended
characters.

It's my own compiled version of tin that I'm running so I can
reconfigure and rebuild if necessary, the current version reports:-

    Version: tin 1.9.2 release 20061021 ("Benmore") Oct 22 2006 12:32:44
    Platform:
            OS-Name  = "linux-gnu"
    Compiler:
            CC       = "gcc"
            CFLAGS   = "-g -O2"
            CPP      = "gcc -E"
            CPPFLAGS = "-D_GNU_SOURCE"
    Linker and Libraries:
            LD       = "gcc"
            LDFLAGS  = ""
            LIBS     = "-lncursesw    -lidn"
            PCRE     = "6.7 04-Jul-2006"
    Characteristics:
            +NNTP_ABLE -NO_POSTING -BROKEN_LISTGROUP +XHDR_XREF
            -HAVE_FASCIST_NEWSADMIN +ENABLE_IPV6 -HAVE_COREFILE
            -NO_SHELL_ESCAPE -DISABLE_PRINTING -DONT_HAVE_PIPING -NO_ETIQUETTE
            +HAVE_LONG_FILE_NAMES +APPEND_PID +HAVE_MH_MAIL_HANDLING
            +HAVE_ISPELL +HAVE_METAMAIL +HAVE_SUM
            +HAVE_COLOR -HAVE_PGP -HAVE_PGPK +HAVE_GPG
            -MIME_BREAK_LONG_LINES +MIME_STRICT_CHARSET +CHARSET_CONVERSION
            +MULTIBYTE_ABLE -NO_LOCALE
            +USE_CANLOCK -EVIL_INSIDE -FORGERY -TINC_DNS -ENFORCE_RFC1034
            -REQUIRE_BRACKETS_IN_DOMAIN_LITERAL -FOLLOW_USEFOR_DRAFT

Would setting NO_LOCALE be a workaround?


-- 
Chris Green ([email protected])