2
  "   ˆl–Ü4ý(&ÔËm
�ÆŸ¸ÓêbÑ¿¿927ÁÅ Ÿ    # bash completion for rfkill                               -*- shell-script -*-

# Use of this file is deprecated on systems with util-linux >= 2.31, which
# ships completion for the rfkill included with it.

_rfkill()
{
    local cur prev words cword
    _init_completion || return

    if [[ $cur == -* ]]; then
        COMPREPLY=($(compgen -W '--version' -- "$cur"))
    else
        case $cword in
            1)
                COMPREPLY=($(compgen -W "help event list block unblock" \
                    -- "$cur"))
                ;;
            2)
                if [[ $prev == block || $prev == unblock ]]; then
                    COMPREPLY=($(compgen -W "$($1 list | awk -F: \
                        '/^[0-9]/ {print $1}') all wifi bluetooth uwb wimax \
                        wwan gps" -- "$cur"))
                fi
                ;;
        esac
    fi
} &&
    complete -F _rfkill rfkill

# ex: filetype=sh
  +   ˆl–Ðz¾”d*j"Tâ�nãn\ ”Å£ÀƒxA_‡I|¥‰ÓMÃÇ      <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
 <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
 <TITLE>The Linux keyboard and console HOWTO: How to make other programs work with non-ASCII chars</TITLE>
 <LINK HREF="kbd.FAQ-13.html" REL=next>
 <LINK HREF="kbd.FAQ-11.html" REL=previous>
 <LINK HREF="kbd.FAQ.html#toc12" REL=contents>
</HEAD>
<BODY>
<A HREF="kbd.FAQ-13.html">Next</A>
<A HREF="kbd.FAQ-11.html">Previous</A>
<A HREF="kbd.FAQ.html#toc12">Contents</A>
<HR>
<H2><A NAME="s12">12. How to make other programs work with non-ASCII chars</A></H2>

<P>
<!--
non-ASCII characters, using
-->
<P>In the bad old days this used to be quite a hassle. Every separate
program had to be convinced individually to leave your bits alone.
Not that all is easy now, but recently a lot of gnu utilities have
learned to react to <CODE>LC_CTYPE=iso_8859_1</CODE> or <CODE>LC_CTYPE=iso-8859-1</CODE>.
Try this first, and if it doesn't help look at the hints below.
Note that in recent versions of libc the routine setlocale() only
works if you have installed the locale files (e.g. in
<CODE>/usr/lib/locale</CODE>).
<P>NOTE! The above was written years ago. Today locale stuff is a bit different.
Try the command <CODE>locale -a</CODE> to see which locales are available.
Then use one of these locale names instead of the <CODE>iso_8859-1</CODE>
mentioned above. For example, <CODE>LC_CTYPE=fr_FR.ISO-8859-1</CODE> or
<CODE>LC_CTYPE=fr_FR@euro</CODE>.
<P>NOTE! Some of the below may still be true. Most of it is outdated.
(Please report on what is incorrect today, so that it can be deleted.)
<P>First of all, the 8-th bit should survive the kernel input processing,
so make sure to have <CODE>stty cs8 -istrip -parenb</CODE> set.
<P>A. For <CODE>emacs</CODE> the details strongly depend on the version.
The information below is for version 19.34. Put lines
<BLOCKQUOTE><CODE>
<PRE>
        (set-input-mode nil nil 1)
        (standard-display-european t)
        (require 'iso-syntax)
</PRE>
</CODE></BLOCKQUOTE>

into your <CODE>$HOME/.emacs</CODE>.
The first line (to be precise: the final 1)
tells <CODE>emacs</CODE> not to discard the 8-th bit from input characters.
The second line tells <CODE>emacs</CODE> not to display non-ASCII characters
as octal escapes.
The third line specifies the syntactic properties
and case conversion table for the Latin-1 character set
These last two lines are superfluous if you have something like
<CODE>LC_CTYPE=ISO-8859-1</CODE> in your environment.
(The variable may also be <CODE>LC_ALL</CODE> or even <CODE>LANG</CODE>.
The value may be anything with a substring `88591' or `8859-1'
or `8859_1'.)
<P>This is a good start.
On a terminal that cannot display non-ASCII ISO 8859-1 symbols,
the command
<BLOCKQUOTE><CODE>
<PRE>
        (load-library "iso-ascii")
</PRE>
</CODE></BLOCKQUOTE>

will cause accented characters to be displayed comme {,c}a.
If your keymap does not make it easy to produce non-ASCII characters, 
then
<BLOCKQUOTE><CODE>
<PRE>
        (load-library "iso-transl")
</PRE>
</CO