Re: tcsh, funkar inget vidare med 8bitars teckentabeller?

[Karl Hammar <karl@kalle.csb.ki.se>]

Prova och sätt LANG och/eller LC_CTYPE innan du startar tcsh:

  $ export LANG=sv_SE
  $ export LC_CTYPE=sv_SE
  $ tcsh 
  opal:~> echo aödksz-,möaksldqåioeur
  aödksz-,möaksldqåioeur
  opal:~>

  $ man tcsh
  ...
     Native Language System support (+)
	 The shell is eight bit clean (if so compiled; see the ver­
	 sion shell variable)  and  thus  supports  character  sets
	 needing this capability.  NLS support differs depending on
	 whether or not the shell was compiled to use the  system's
	 NLS  (again, see version).  In either case, 7-bit ASCII is
	 the default for character classification (e.g. which char­
	 acters  are  printable) and sorting, and changing the LANG
	 or LC_CTYPE environment variables causes a check for  pos­
	 sible changes in these respects.

	 When  using the system's NLS, the setlocale(3) function is
	 called to determine appropriate  character  classification
	 and  sorting.   This  function typically examines the LANG
	 and LC_CTYPE environment variables; refer  to  the  system
	 documentation  for  further  details.   When not using the
	 system's NLS, the shell simulates it by assuming that  the
	 ISO  8859-1  character  set is used whenever either of the
	 LANG and LC_CTYPE variables are set, regardless  of  their
	 values. Sorting is not affected for the simulated NLS.

	 In  addition, with both real and simulated NLS, all print­
	 able characters in the range \200-\377,  i.e.  those  that
	 have  M-char  bindings, are automatically rebound to self-
	 insert-command.  The corresponding binding for the escape-
	 char  sequence,  if  any, is left alone.  These characters
	 are not rebound if the NOREBIND  environment  variable  is
	 set.  This may be useful for the simulated NLS or a primi­
	 tive real NLS which assumes full  ISO  8859-1.  Otherwise,
	 all M-char bindings in the range \240-\377 are effectively
	 undone.  Explicitly rebinding the relevant keys with bind­
	 key is of course still possible.



  Astron 6.09.00            16 August 1999                       34





  TCSH(1)                                                   TCSH(1)


	 Unknown  characters (i.e. those that are neither printable
	 nor control characters) are printed in  the  format  \nnn.
	 If  the  tty  is not in 8 bit mode, other 8 bit characters
	 are printed by converting them to ASCII and using standout
	 mode.  The shell never changes the 7/8 bit mode of the tty
	 and tracks user-initiated changes of  7/8  bit  mode.  NLS
	 users  (or,  for that matter, those who want to use a meta
	 key) may need to explicitly set the  tty  in  8  bit  mode
	 through  the  appropriate  stty(1)  command  in, e.g., the
	 ~/.login file.

  ...
  $

Hälsningar,
/Karl

-----------------------------------------------------------------------
Karl Hammar                    Aspö Data           karl@kalle.csb.ki.se
Lilla Aspö 2340               0173 140 57                       Nätverk
S-742 94 Östhammar           070 511 97 84               PC/Sun datorer
Sweden                                            Linux/Unix konsulting
-----------------------------------------------------------------------

From: Fredrik Bjurenfors <ollesson@home.se>
Subject: tcsh, funkar inget vidare med 8bitars teckentabeller?
Date: Tue, 2 Jan 2001 02:54:47 +0100

> Hej!
> Jag har lite probelm med tcsh och 8bitars tecken.
> Jag har provat allt nästan för att få det att funka.
> Allt funkar perfekt i andra shell såsom bash, zsh.
> 
> stty pass8 funkar inte alls.
> 
> Det spelar ingen roll om man kör TERM som rxvt, linux.
> 
> när man kollar lite saker med "set" så ser man i versionraden att
> tcsh är kompilerat med 8bits chars (så det är mig det är fel på?)
> 
> 
> (Detta kommer från tcsh FAQ:en)
> 
> 1.  Why is the meta key broken in tcsh-5.20 and up? 
> 
>     On some machines the tty is not set up to pass 8 bit characters by
> default.
>     Tcsh 5.19 used to try to determine if pass8 should be set by looking at
>     the terminal's meta key. Unfortunately there is no good way of
> determining
>     if the terminal can really pass 8 characters or not. Consider if you
> are
>     logged in through a modem line with 7 bits and parity and your terminal
> 
>     has a meta key. Then tcsh 5.19 would set wrongly set pass8.
> 
>     If you did like the previous behavior you can add in /etc/csh.login, or
>     in .login:
> 
>     if ( $?tcsh && $?prompt ) then
>     if ( "`echotc meta`" == "yes" ) then
>          stty pass8
>     endif
>     endif
> 
>     If you don't have pass8, maybe something like
> 
>     stty -parity -evenp -oddp cs8 -istrip   (rs6000)
>     or
>     stty -parenb -istrip cs8 
>     
>     would work..
> 
> Vore tacksam för hjälp
> Hälsningar Fredrik Bjurenfors
> 
> 
> 
> 
> 
> --  
> To UNSUBSCRIBE, email to debian-user-swedish-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org