\begindata{text,1286272}
\textdsversion{12}
\template{default}
\center{

\bold{Installation Notes for the AUIS-63L4-WP Package

}
}
\bold{FORWARD}


This is the first of several planned versions of "packages" of the 
\bold{Andrew User Interface System} (\bold{\italic{AUIS}}).  AUIS can be 
difficult to describe fully since it encompasses such a large variety of 
applications and uses.  In an effort to break this into something more 
manageable, both in size and scope, I have created this particular package 
which is aimed principally at people interested in \bold{WORD PROCESSING}.


Please understand that a full AUIS distributed system would require close 
to 40 MB of space and consists of hundreds of distinct functional pieces. 
 Few make full use of all this functionality and it certainly is daunting 
for the novice.  However, providing a restricted set of AUIS has drawbacks 
because thousands of files are missing.  This will be most apparent in the 
help text which will refer to some files which you will not have.  This is 
the price I have chosen to pay for a simpler AUIS.


Do not mix versions of AUIS packages.  Always use packages at the same 
LEVEL (i.e. L1 with L1).  Mixing LEVELS can result in surprising and 
undesirable behavior.  You may be interested in a series of articles on 
AUIS that appeared in the Linux Journal in August 1994.



\flushright{Terry Gliedt	\


tpg@cfa.org	\


}

\bold{INTRODUCTION}


The Andrew User Interface System is an integrated set of tools that allow 
you to create, use, and mail documents and applications containing 
typographically formatted text and embedded objects.  AUIS has three 
principal components:


\indent{The \bold{Andrew User Environment} (\bold{\italic{AUE}}) is an 
integrated set of applications beginning with a 'generic object' editor 
(\italic{ez}), a help system, a system monitoring tool (\italic{console}), 
an editor-based shell interface (\italic{typescript}), and support for 
printing multi-media documents. \



The \bold{Andrew Toolkit} (\bold{\italic{ATK}}) is a portable 
user-interface toolkit.  It provides a dynamically-loadable, 
object-oriented environment wherein objects can be embedded in one-another. 
Thus, one could edit text that contains not only fonts and styles, but also 
embedded raster images, spreadsheets, drawing editors, equations, simple 
animations, etc. These embedded objects could themselves contain other 
objects, including text. ATK is an open system so programmers can create 
new objects that can be embedded as easily as those system-defined objects. 


The \bold{Andrew Message System} (\bold{\italic{AMS}}) provides a 
multi-media interface to mail and bulletin-boards.  AMS supports several 
mail management strategies and implements many advanced  features including 
authentication, return receipts, automatic sorting of mail, vote collection 
and tabulation, enclosures, audit trails of related messages, and 
subscription management. It also provides a variety of interfaces that 
support ttys and low-function personal computers in addition to the 
high-function workstations. }\



\{History: In 1982 Carnegie Mellon and IBM entered into a joint venture and 
formed the Information Technology Center to design a very powerful, 
advanced function workstation and distributed computing environment on 
campus.    This environment is known as the Andrew System, named for the 
university's two major benefactors, Andrew Carnegie and Andrew Mellon.  In 
1992, the School of Computer Science formed the Andrew Consortium to 
extend, support and distribute the Andrew User Interface System  (AUIS).\}


More details about the Andrew Consortium and AUIS in general can be found 
in /usr/andrew/AUIS-Finder.d.



\bold{INSTALLATION}


This packaged is distributed as a single tar file of approximately 1.4 MB 
(one diskette!) which will expand to approximately 4.5 MB of disk space. 
 To install this package, do the following as root:


\indent{cd /

tar xzf [path]/auis63L4-wp.tgz

}	/usr/andrew/etc/complete-setup wp


This will create a hierarchy of files under \italic{/usr/andrew}.  None of 
these files require root authority.  A set of binaries is distributed in 
\italic{/usr/andrew/bin}.  Add this path to your PATH so they can be 
executed:


\indent{setenv PATH $\{PATH\}:/usr/andrew/bin; rehash	# For csh/tcsh users

export PATH=$\{PATH\}:/usr/andrew/bin		# For bash/ksh users

}
AUIS is highly tailorable for your personal needs and preferences.  Some 
might say there is too much.  To get you started, I've done a great deal 
for you in this area.  Create a file called "\bold{preferences}" in your 
home directory for AUIS:


\indent{cp /usr/andrew/sample.preferences $HOME/preferences

}
This sample \italic{preferences} is aimed at folks with color displays.  If 
your system only supports monochrome, you'll want to remove the color 
settings in "\italic{preferences}" right away.  Edit your 
\italic{preferences} file and follow the comments.



\bold{YOUR FIRST AUIS SESSION}


AUIS requires that you be running the X Window System.  AUIS comes with a 
massive amount of help text.  Probably your first xterm command should be 
"\italic{\bold{auishelp}}" and begin with "\bold{A Guided Tour of Andrew}".


Your principle tool for word processing will be an editor named 
"\bold{ez}".  You might try this for your first practice session.


\indent{cp /usr/andrew/README.ez /tmp

chmod +w /tmp/README.ez

ez /tmp/README.ez

}
When you create your own new documents, use any of these extensions:

	.d  .doc  .ez  .letter  .memo  \


These extensions will default to use a style you'll find useful for word 
processing.  If the file has already been created by ez, then the data 
itself will determine the style to be used and you have nothing to do.



\bold{KEY BINDINGS}


As part of the customization provided for you, I have defined a number of 
F-key bindings to make word processing a bit easier:


\indent{F1	Copy	(After selecting an area, copy it)

F2	Paste	(Put copied data at cursor)

F3	Cut	(Remove selected data)

F4	Cycle-Copy-Buffer	(AUIS remembers previous copied data)

F5	Show selected text in an \italic{italics} font

F6	Show selected text in a \bold{bold} font

F7	Plainer selected area (Remove one level of styles)

F8	Plainest selected area (Remove all levels of styles)

F9	Show raw HTML+ (for .html files)

F10	Show normal HTML+ (for .html files)

}

\bold{CHANGELOG}



Release auis63L4-mail has the following changes:


\indent{- This was built on Slackware 2.1.0


- This version requires XFree 3.x shared libraries


- Functionally this has almost nothing new compared to auis63L3-wp


}Release auis63L3-wp has the following changes:


\indent{- This was built on Slackware 2.0.1


- AUIS now requires your system to support the QMAGIC executable

format.  This should be true for anyone using a kernel >= 1.0.0.


- This version requires XFree 2.x shared libraries


- Now based on AUIS 6.3.1 - which has only fixes to 6.2.


- A new WYSLRN HTML-editor is now available.  Finally a semi-decent 
interface for HTML documents.


- Notes added for the German .Xmodmap file added at the bottom of this 
document (thanks to Oliver Mai <mai@HP-Cluster.desy.de>)


- New comps file corrects printing large umlauts (thanks to Oliver Mai 
<mai@HP-Cluster.desy.de>)


}
Release auis63L2-wp has the following changes:

\indent{
}\indent{- Now based on AUIS 6.2.2 - which has only fixes to 6.2.


- Removed various unused pieces


- Added a filter on the Misc menu to "flow" text together


- Added a simple spreadsheet, table


- Stripped the binaries (thanks to mitchum.dsouza@mrc-apu.cam.ac.uk)


- This package now fits in one 3.5 inch diskette!

}
Release auis63L1-wp has the following changes:


\indent{- Now based on AUIS 6.2.1 - which has only fixes to 6.2.


- The AUIS help program can be invoked from the File menu.  Note this is 
not context sensitive help - just a means to invoke /usr/andrew/bin/help.


- Added auishelp shell


- Added support for html


- Added support for equations (eq)

}
Release auis63L0-wp has the following changes:


\indent{- Now based on AUIS 6.3 - which has only fixes to 6.2.


- Corrected atkprint and atkpreview so equations will work


- Minor changes made to some menus


- UseNewShadows enabled to provide better shadowing in scrollbars

}
Release auis63L1-wp has the following changes:


\indent{- Contains a very few fixes to AUIS 6.3


- This was built on Slackware 2.0


- Latest version of Nick Williams htmlview code, including many fixes. 
 Finally something pretty close to WYSIWYG HTML editting!

}
Release auis63L2-wp has the following changes:


\indent{- Contains a very few fixes to AUIS 6.3.1


- This was built on Slackware 2.0


- The default number of possible colors allocated for images was increased 
from 27 to 64.  This should provide better looking images in AUIS 
documents.


- Added new command \italic{setpapersize} to allow one to specify USA or A4 
paper for printing.  (Thanks to Klaus Fueller <klausf@softwks>)


- A substantially altered version of Nick Williams htmlview code.  This has 
lots of additional function and does a better overall job of providing 
WYSWIG editting for HTML documents.

}

\bold{SOME THINGS YOU MIGHT LIKE TO KNOW}


\description{When you enter the "\italic{ls}" command in a 
"\italic{\bold{typescript}}", you might see something like 
"[01;34mMail[0m/".  This is a result of the "colorful" version of ls 
adding escape sequences to its output.  Typescript does not support these 
sequences.  You can avoid this by setting an alias for \italic{ls} to 
\italic{/bin/ls}  (e.g. \italic{alias ls '/bin/ls -F}').


\italic{Typescript} file-completion is almost set for you. 
 \italic{Typescript} will attempt to complete a filename when you press 
Tab.  To enable this, do the following (or equivalent in your shell).  In 
\italic{csh}, include the following in your $HOME/.cshrc:


\example{if ("$?TERM") then

  switch ("$TERM")

    case "wm":

      alias cd 'cd \\!*; echo -n $cwd'

      alias pushd 'pushd \\!*; echo -n $cwd'

      alias popd 'popd \\!*; echo -n $cwd'

      breaksw

    default:

    breaksw

  endsw

endif

}
\italic{Typescript} is *\bold{not}* \italic{xterm}.  You cannot use 
\italic{vi} or \italic{telnet} directly from it, but you can make a little 
shell script like this version of \bold{/usr/local/bin/telnet}:


\example{#!/bin/csh -f

# Get all - options and pass these to xterm

set xopt = ""

while (.$1 =~ .-*)

  set xopt = "$xopt $1 $2"

  shift

  shift

end

if ("$TERM" == "wm") then

   exec xterm -sb -title "$1" $xopt -e /bin/telnet $1 &

else

   exec /bin/telnet $xopt $1

endif}


\italic{Typescript} is does not behave well with \italic{bash}.  It 
\bold{works just fine} with \italic{ksh} and \italic{tcsh}.  The problem is 
that \italic{bash} constantly is changing the state of the tty as each 
character is typed. The results in you not being able to see what you are 
typing until you press "Enter" when the line is displayed.


Use \italic{pipescript} as you would use \italic{more}.  It does not 
clutter up your \italic{xterm} window, has no limit of data it can hold and 
works with all the other AUIS components.  Try something like "\bold{tar 
tzvf [path]/auis63L?-wp.tgz | pipescript}".


In Slackware 1.2.0 the backspace key may not behave as you would expect. 
This can be corrected with a \italic{xmodmap} entry  "keycode 22 = 
BackSpace" in your \bold{$HOME/.xmodmaprc} file and then invoking 
"\bold{xmodmap $HOME/.xmodmaprc}" in your \italic{.xinitrc} file.  You can 
also edit "\bold{/usr/andrew/lib/global.atkinit"} and change the key 
bindings.  Look for the word "\italic{Remap}" and follow the comments.


The \italic{ez} popup menus have been reduced to just four menus, rather 
than the 15 that would normally be there.  That many popups just get in the 
way.  Everything is available from the menubar, however.


Users with some display adapters like the ATI GUP+ may not be able to see 
the mouse cursor in some cases.  In some cases the cursor is shown as a 
tiny white dot. These users need to add '\bold{Option "sw_cursor"}' in 
their Xconfig file.


The preference "\italic{print.printer}" is obsolete and will not work with 
this release.


This package has been set up to use \italic{\bold{ghostview}} to preview 
your output.  It is configured to use a shell found in 
\italic{/usr/andrew/etc/atkpreview}.  You could either modify this shell or 
change the command used to preview with a preference entry something like 
"*.previewcommand: yourpath/atkpreview /tmp/%s.n".  Look for this entry in 
your \italic{preferences}.


Yes, \italic{\bold{atkprint}} and \italic{\bold{atkpreview}} are written in 
C-shell.  That is a requirement for now until someone else rewrites them in 
\italic{bash} and sends them to me. \



The normal command for help in AUIS is "\italic{\bold{help}}" (found in 
/usr/andrew/bin/help) which conflicts with the \italic{bash} command of the 
same name.  To assist with this, I have provided a shell 
"\italic{\bold{auishelp}}" which will simply invoke the correct help.  You 
can also invoke this help by selecting "\bold{AUIS Help}" on the 
"\bold{File}" menu.


This package has been set up to use \italic{\bold{groff}} and 
\italic{\bold{ghostscript}} to generate a PostScript stream for the printer 
named $PRINTER.  It is configured to use a shell found in 
\italic{/usr/andrew/etc/atkprint}.  You could either modify this shell or 
change the command used to print with a preference entry something like 
"*.formatcommand: yourpath/atkprint /tmp/%s.n |" (yes, this ends with a 
pipe symbol).  More detail can be found by entering "\bold{auishelp 
preferences}" and searching for "\italic{formatcommand}", 
"\italic{previewcommand}", or "\italic{printcommand}".  Look for these same 
entries in your \italic{preferences}.


Sometimes the fonts look rather ugly.  Be sure you have all the common X 
fonts installed and that you have them specified in your Xconfig file. 
 Here's what I have in my Xconfig:

\indent{FontPath	"/usr/X386/lib/X11/fonts/misc/"

FontPath	"/usr/X386/lib/X11/fonts/Speedo/"

FontPath	"/usr/X386/lib/X11/fonts/75dpi/"

FontPath	"/usr/X386/lib/X11/fonts/100dpi/"}


Sometimes the fonts still look rather ugly.  This is because AUIS is asking 
the X-server to scale the fonts dynamically and sometimes this does not 
work out very well.  You can control whether AUIS asks for scaled fonts or 
not with the preferences entry: "\bold{*.ScaleXFonts}". If you do not scale 
fonts, then successive calls to "Bigger" (for instance) may not result in a 
font that you can SEE is different. When it prints, however, it will have 
the larger font.  This has been left to default so the fonts are scaled. 
 If/when we get better scalable fonts (like Adobe fonts), this will no 
longer be an issue.


Non-USA users will want to read about \bold{compchar} (issue 
"\italic{auishelp compchar}") to find out how to enter characters which are 
peculiar to their languages.  Most of the common characters should already 
be there and should print as expected.


You will need to have the C-shell (/bin/csh) installed to use all of this 
package.  This is most likely just a symbolic link to /bin/tcsh  (e.g. ln 
-sf /bin/tcsh /bin/csh).  If this is not installed you will see an error 
trying to execute the /usr/andrew/etc/complete-setup shell (command not 
found).


If you print/preview equations, you should modify 
/usr/andrew/etc/\{atkprint,atkpreview\} so that \italic{geqn} and 
\italic{gtbl} are invoked. See the comments in the shells for more details.


AUIS does not correctly generate color PostScript in this version.


The program rofftext should be able to format regular man pages which do 
not contain \italic{groff} extensions.  The command would normally be: 
\bold{rofftext -h -man -o XXXX.help XXXX.1}


If \italic{ez} comes up with a black window or one which is pretty messed 
up, it's pretty likely AUIS is not successfully adding the fonts in 
/usr/andrew/X11fonts to your fontpath.  This should be happening 
automatically.  Try to figure out if this is the case and why its 
happening.  ("\italic{xset -q"} will show you the fonts that X is trying to 
use.)


The \italic{sample.preferences} file now makes \bold{XStyleSelections} the 
default.  Selecting text in AUIS apps will now make the data available for 
copying (pressing the middle button) in other X-based applications.  On the 
other hand, this will make the use of PF4 a little more clumsy since you 
have one extra piece of data in the rotating cut buffer. ou may want to 
disable  this in your $HOME/preferences.

\italic{
Check Spelling} will not work completely with GNU Ispell, version 4.0. Even 
though the GNU-ispell supports the Accept and Insert commands  (save an 
"unknown" word in $HOME/.ispell_words), the low-level interface to 
GNU-ispell does not behave as expected.  It DOES work properly with the 
International Ispell which you can find at 
ftp.cs.ucla.edu:/pub/ispell/ispell-3.1.08.tar.gz. \



In \italic{chart}, if you select \italic{Rechart -> Dot}.  the "points" are 
denoted with "C".   This is possibly a font problem.  \



In \italic{chart}, select \italic{Rechart -> Do}t or \italic{Rechart -> 
Line} and then select \italic{Expose pallette}.  Select \italic{Delete} in 
the new pallette and then select any point on a  Line or Dot. Chart will 
fault with a segment violation.


\italic{Figure} does not prompt when you modify a figure and then select 
\italic{Quit}.  It just quits with no warning.


The image dynamic object fails when trying to import an Xpixmap.


A \italic{raster} cannot be imported into an \italic{image}.


\italic{Rasters} basically assume a dark on light color scheme, thus the 
more usual light on dark color schemes make them look like negatives.  To 
reverse these images, simple select Raster Ops->Negative and make them look 
"correct".


If \italic{ez} comes up with a cursor that is a letter, you have somehow 
not gotten the /usr/andrew/X11fonts directory added to your X fontpath. 
 This should have been added automatically.  Try to figure out if this is 
the case and why its happening.  ("\italic{xset -q"} will show you the 
fonts that X is trying to use.)  To add the the AUIS fonts, enter the 
command \italic{xset +fp /usr/andrew/X11fonts}.


}\description{If you should ever try to compile AUIS yourself from the 
source, beware that imake might fail to correctly build the top level 
Makefile from the AUIS Imakefile. The solution is to change all "all:" 
files to "all::".

}
\description{ \italic{ez} comes up with a cursor that is a letter, you have 
somehow not gotten the /usr/andrew/X11fonts directory added to your X 
fontpath.  This should have been added automatically.  Try to figure out if 
this is the case and why its happening.  ("\italic{xset -q"} will show you 
the fonts that X is trying to use.)  To add the the AUIS fonts, enter the 
command \italic{xset +fp /usr/andrew/X11fonts}.

}


\bold{TOWARDS A MORE COLORFUL AUIS}


Here are some ideas for colors.  You may not agree and that is just fine. 
 The intent of these lists is to give you some ideas of possible useful 
color names rather than have you spend hours and hours looking at colors.


These \italic{\bold{foreground}} colors work pretty well: Black, White, 
WhiteSmoke, Bisque, Ivory


These \italic{\bold{background}} colors that go well with a 
"\bold{whitish}" foreground:


\description{\indent{Red-ish: IndianRed3, IndianRed4, VioletRed3, 
VioletRed4, FireBrick, FireBrick3, FireBrick4, Red4, \



Brown-ish: Brown, Brown3, Sienna, Sienna3, GoldenRod4, Salmon4, Gold4, 
DarkOrange4, Coral4, Chocolate3, BurlyWood4


Yellow-ish: DarkGoldenRod, DarkGoldenRod4


Green-ish: ForestGreen, SeaGreen, PaleGreen4, SpringGreen4, AquaMarine4, 
DarkSlateGray4


Blue-ish: DarkSlateBlue, Turquoise4, CadetBlue, SlateBlue3, SlateBlue4, 
RoyalBlue4, DodgerBlue4, SteelBlue, SteelBlue4, SkyBlue4, LightSkyBlue4, 
LightBlue4, CadetBlue4, PaleTurquoise4, DeepSkyBlue4, Cyan4


Violet-ish: Maroon, Maroon4, DarkViolet, DeepPink4, Pink4, Thistle4, 
HotPink4, Plum4, Orchid4, PaleVioletRed


Gray-ish: Wheat4, SlateGray4, RosyBrown4

}}
These \italic{\bold{background}} colors that go well with a \bold{black} 
foreground:


\description{\indent{Brown-ish: Tan, BurlyWood, Sienna2, SandyBrown, 
DarkSalmon, Wheat, LightSalmon2, Salmon1, Salmon2


Yellow-ish: GoldenRod2, Khaki, LightGoldenRod


Green-ish: AquaMarine, MediumTurquoise, PaleGreen3, DarkSeaGreen2, 
DarkSeaGreen3, DarkOliveGreen3, DarkKhaki


Blue-ish: CornFlowerBlue, DeepBlueSky, SkyBlue, LightSkyBlue, CadetBlue3, 
PowderBlue, SkyBlue2, DeepSkyBlue2, Cyan3, PaleTurquoise, PaleTurquoise3, 
Turquoise3, Azure2


Violet-ish: RosyBrown2, Plum, Thistle, Thistle2, Thistle3, MediumPurple1, 
LightCoral, LightPink2, Pink2, Plum2, Orchid2


Gray-ish: DarkSlateGray3

}}

\bold{Example1}


Here is one person's selection for colors. To try this, remove all 
references in your \italic{$HOME/preferences} file to color and copy these 
into the file. \



\indent{EZ.BackgroundColor: DeepSkyBlue4

Typescript.BackgroundColor: SlateGray4

*.PopupForegroundColor: WhiteSmoke

*.ForegroundColor: WhiteSmoke

*.DialogBackground: Gray50

*.cursorforegroundcolor: FireBrick

*.MenubarCardBackgroundColor: SkyBlue4

*.MenubarGrayItemColor: PowderBlue

*.PopupBackgroundColor: SkyBlue4

*.ScrollBackground: VioletRed4

*.BackgroundColor: LightSkyBlue4

}
\bold{Example2}


Here is another selection for colors.  To try this, remove all references 
in your \italic{$HOME/preferences} file to color and copy these into the 
file. \



\indent{EZ.BackgroundColor: SlateGray

Typescript.BackgroundColor: SkyBlue4

*.MenubarForegroundColor: WhiteSmoke

*.MenubarItemColor: WhiteSmoke

*.PopupForegroundColor: WhiteSmoke

*.ForegroundColor: WhiteSmoke

*.DialogBackground: Gray50

*.cursorforegroundcolor: FireBrick

*.MenubarBackgroundColor: LightSkyBlue4

*.MessageLineBackgroundColor: LightSkyBlue4

*.BackgroundColor: LightBlue4

*.MenubarCardBackgroundColor: CadetBlue4

*.PopupBackgroundColor: CadetBlue4

*.MenubarGrayItemColor: Cyan

*.ScrollBackground: Cyan4

}

\bold{NON-USA USER NOTES}



\bold{Date}: Wed, 5 Oct 1994 11:17:04 +0100

\bold{From}: Oliver Mai <mai@HP-Cluster.desy.de>

\bold{To}: tpg@MR.Net

\bold{Subject}: Re: Umlauts etc


For me ez has accepted umlauts entered directly thru my german keyboard 
ever since I first installed the auis-wp package about half a year ago, so 
I was really surprised  when I read in the newsgroup that umlauts do not 
work for some people. I thought about what might be the cause of these 
people's problems, and I found two possible  reasons.



The first one is the possibility that they might not have a working german 
.Xmodmap file. Here I include the one that works for me:

----------------> Cut <--------------

clear    shift

clear    lock

clear    control

clear    mod1

clear    mod2

clear    mod3

clear    mod4

clear    mod5

keycode   8 =

keycode   9 = Escape

keycode  10 = 1 exclam

keycode  11 = 2 quotedbl twosuperior

keycode  12 = 3 paragraph threesuperior

keycode  13 = 4 dollar

keycode  14 = 5 percent

keycode  15 = 6 ampersand

keycode  16 = 7 slash braceleft

keycode  17 = 8 parenleft bracketleft

keycode  18 = 9 parenright bracketright

keycode  19 = 0 equal braceright

keycode  20 = ssharp question backslash

keycode  21 = apostrophe grave

keycode  22 = BackSpace

keycode  23 = Tab

keycode  24 = q Q at

keycode  25 = W

keycode  26 = E

keycode  27 = R

keycode  28 = T

keycode  29 = Z

keycode  30 = U

keycode  31 = I

keycode  32 = O

keycode  33 = P

keycode  34 = Udiaeresis

keycode  35 = plus asterisk asciitilde

keycode  36 = Return

keycode  37 = Control_L

keycode  38 = A

keycode  39 = S

keycode  40 = D

keycode  41 = F

keycode  42 = G

keycode  43 = H

keycode  44 = J

keycode  45 = k K Arabic_kaf

keycode  46 = l L Arabic_lam Greek_lambda

keycode  47 = Odiaeresis

keycode  48 = Adiaeresis

keycode  49 = asciicircum degree

keycode  50 = Shift_L

keycode  51 = numbersign apostrophe

keycode  52 = Y

keycode  53 = X

keycode  54 = C

keycode  55 = V

keycode  56 = B

keycode  57 = N

keycode  58 = m M mu

keycode  59 = comma semicolon

keycode  60 = period colon

keycode  61 = minus underscore

keycode  62 = Shift_R

keycode  63 = KP_Multiply

keycode  64 = Alt_L

keycode  65 = space

keycode  66 = Caps_Lock

keycode  67 = F1

keycode  68 = F2

keycode  69 = F3

keycode  70 = F4

keycode  71 = F5

keycode  72 = F6

keycode  73 = F7

keycode  74 = F8

keycode  75 = F9

keycode  76 = F10

keycode  77 = Num_Lock

keycode  78 = Scroll_Lock

keycode  79 = Home KP_7 KP_7 Home

keycode  80 = Up KP_8 KP_8 Up

keycode  81 = Prior KP_9 KP_9 Prior

keycode  82 = KP_Subtract

keycode  83 = Left KP_4 KP_4 Left

keycode  84 = Begin KP_5 KP_5 Begin

keycode  85 = Right KP_6 KP_6 Right

keycode  86 = KP_Add

keycode  87 = End KP_1 KP_1 End

keycode  88 = Down KP_2 KP_2 Down

keycode  89 = Next KP_3 KP_3 Next

keycode  90 = Insert KP_0 KP_0 Insert

keycode  91 = Delete KP_Decimal KP_Decimal Delete

keycode  92 = 0x1007ff00

keycode  93 =

keycode  94 = less greater bar

keycode  95 = F11

keycode  96 = F12

keycode  97 = Home

keycode  98 = Up

keycode  99 = Prior

keycode 100 = Left

keycode 101 = Begin

keycode 102 = Right

keycode 103 = End

keycode 104 = Down

keycode 105 = Next

keycode 106 = Insert

keycode 107 = Delete

keycode 108 = KP_Enter

keycode 109 = Control_R

keycode 110 = Pause

keycode 111 = Print

keycode 112 = KP_Divide

keycode 113 = Mode_switch

!nur bei XFree86 1.1 noetig

!clear mod1

!add mod1 = Alt_L

add	shift   = Shift_L Shift_R

add	lock    = Caps_Lock

add	control = Control_L Control_R

add	mod1    = Alt_L

add	mod2 = Mode_switch

!keycode 114 = Break

----------------> Cut <--------------


I don't know where I got my .Xmodmap file from; either it was included in 
the Slackware distribution or I copied it later from some german ftp site. 
I think there are some german .Xmodmap files on 
ftp.uni-erlangen.de:/pub/Linux/local (if I remember correctly).


The other possibility I thought of is the fact that the (PS) fonts ez uses 
for some people might not contain umlauts and other characters with codes 
larger than 127. I use the *.pfa fonts which come with the Adobe Type 
Manager where umlauts are included, but I think I heard that some PD or 
shareware PS fonts do not include them. I didn't check if e.g. the 
ghostscript font work.


There was just one problem concerning the _printing_ of umlauts with ez 
which I had to solve. In the standard /usr/andrew/lib/compchar/comps file 
umlauts are put together from several constituent characters. This doesn't 
work to well especially when printing with large fonts (that means the 
result looks quite ugly). The simple solution for me was to replace those 
lines in comps where the umlauts are defined with the following lines:

----------------> Cut <--------------

a: 228 \^{d}

A: 196 \^{D}

O: 214 \^{V}

o: 246 \^{v}

U: 220 \^{\\}

u: 252 \^{|}

SS 223 \^{_}

Ss 223 \^{_}

----------------> Cut <--------------


(In case you can't read the characters in the last column on your 
terminal/computer: These are just the characters with the codes 228, 196, 
214, ... respectively.)


Of course, this solutions requires that the PS fonts used for printing 
contain the umlauts at the appropriate places, but if this is the case it 
gives perfect results (at least if one uses groff, I don't know if there 
might arise problems if one uses troff).


That's all I know about umlauts and ez. Thank you very much for your 
efforts maintaining the AUIS packages for Linux, they really fill a large 
gap. For me there is only one major problem with ez: Within the editor font 
metrics seem to be different than they are for ghostscript, allthough I let 
X11 scale my fonts and (I think) I use the same (ATM) PS fonts for both X 
and ghostscript. This leads e.g. to the unconveniency that the way tabs are 
printed is unpredictable (quite disturbing particularly when printing 
source codes). Probably this has nothing to do with ez, but comes from some 
font scaling inconsistency between X and ghostscript. \




\bold{DISCLAIMER}


Permission to use, copy, modify, and distribute this software and its 
 documentation for any purpose is hereby granted without fee,  provided 
that the above copyright notice appear in all copies and that  both that 
copyright notice, this permission notice, and the following  disclaimer 
appear in supporting documentation, and that the names of  IBM, Carnegie 
Mellon University, and other copyright holders, not be  used in advertising 
or publicity pertaining to distribution of the software  without specific, 
written prior permission.


IBM, CARNEGIE MELLON UNIVERSITY, AND THE OTHER COPYRIGHT HOLDERS  DISCLAIM 
ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING  ALL IMPLIED 
WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT  SHALL IBM, CARNEGIE 
MELLON UNIVERSITY, OR ANY OTHER COPYRIGHT HOLDER  BE LIABLE FOR ANY 
SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY  DAMAGES WHATSOEVER 
RESULTING FROM LOSS OF USE, DATA OR PROFITS,  WHETHER IN AN ACTION OF 
CONTRACT, NEGLIGENCE OR OTHER TORTIOUS  ACTION, ARISING OUT OF OR IN 
CONNECTION WITH THE USE OR PERFORMANCE  OF THIS SOFTWARE.

\enddata{text,1286272}
