.\" $XConsortium: RELNOTES.ms,v 1.6 94/05/16 14:35:14 gildea Exp $
.\" X11R6 Release Notes.  Use troff -ms macros
.\"
.ie t \{
.nr LL 6.5i
.\}
.el \{
.nr LL 76n
.na
.\}
.nr FL \n(LLu
.nr LT \n(LLu
.ll \n(LLu
.nr PS 11
.de nH
.NH \\$1
\\$2
.XS
\\*(SN \\$2
.XE
.LP
..
.de Ip
.IP "\fB\\$1\fP" \\$2
..
.\"
.ds CH \" as nothing
.sp 8
.TL
\s+2\fBX Window System, Version 11, Release 6\fP\s-2

\s+1\fBRelease Notes\fP\s-1
.AU
.sp 6
\fIStephen Gildea\fP
.AI

X Consortium
.sp 6
May 16, 1994
.LP
.bp
.sp 8
Copyright \(co 1994 X Consortium
.nr PS 9
.nr VS 11
.LP
Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and associated documentation files (the
\*QSoftware\*U), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:
.LP
The above copyright notice and this permission notice shall be included
in all copies or substantial portions of the Software.
.LP
THE SOFTWARE IS PROVIDED \*QAS IS\*U, WITHOUT WARRANTY OF ANY KIND, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE X CONSORTIUM BE LIABLE FOR ANY CLAIM, DAMAGES OR
OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE SOFTWARE.
.LP
Except as contained in this notice, the name of the X Consortium shall
not be used in advertising or otherwise to promote the sale, use or
other dealings in this Software without prior written authorization
from the X Consortium.
.LP
\fIX Window System\fP is a trademark of X Consortium, Inc.
.\"
.if t \{
.OH 'X Version 11, Release 6''X Window System Release Notes'
.EH 'X Window System Release Notes''X Version 11, Release 6'
.bp 1
.ds CF \\n(PN
.\}
.nr PS 11
.nr VS 13

.nH 1 "Easy Build Instructions"
.\"
This quick summary is no substitute for reading the full build
instructions later in this document.
.LP
Edit \fBxc/config/cf/site.def\fP for local preferences.
If you want to build with \fIgcc\fP
uncomment the \fBHasGcc2\fP line.
If you want to install somewhere other than \fB/usr/X11R6\fP,
change
\fBProjectRoot\fP.  (Do \fInot\fP use \fBDESTDIR\fP.)
.LP
If any fixes have been released by the X Consortium, 
stop here and follow the instructions at the top of each patch,
but don't do any of the \fImake\fP
commands suggested in the patches.  Then continue here.
.LP
Check the appropriate \fBxc/config/cf/\fP\fIvendor\fP\fB.cf\fP file to
make sure that \fBOSMajorVersion\fP and \fBOSMinorVersion\fP are
set correctly for your system (change them if necessary).
.LP
See if there is a \fBBootstrapCFlags\fP mentioned in the comments
in the \fIvendor\fP\fB.cf\fP file.
If there isn't one, \fIcd\fP to the \fBxc\fP directory and type:
.ID
make World >& world.log
.DE
.LP
If there is a \fBBootstrapCFlags\fP, take its value
and type:
.ID
make World BOOTSTRAPCFLAGS="\fIvalue\fP" >& world.log
.DE
.LP
Do not call the output file \*Qmake.log\*U.
If the build is successful, you can install most of it with:
.ID
make install >& install.log
.DE
.LP
You can install manual pages with:
.ID
make install.man >& man.log
.DE
.LP
While the system is building (or if things fail), read the rest of
these Release Notes.

.nH 1 "What Is Release 6"

This is the 6th release of X Window System software from the X Consortium.
X is a network-transparent window system which runs
on a wide range of computing and graphics machines.
.LP
The X Consortium is an independent, not-for-profit corporation,
the successor to the MIT X Consortium, which was part of the MIT
Laboratory for Computer Science.
See the \fIXConsortium\fP manual page for details.

.nH 2 "Overview of the X Consortium Release"

There are two parts to Release 6: X Consortium software and
documentation, and user-contributed software and documentation.
The X Consortium part contains the following:
.Ip "X Consortium Standards"
The X Consortium produces standards:  documents which define
network protocols, programming interfaces, and other aspects of
the X environment.  See the \fIXStandards\fP manual page for a
list of standards.
.Ip "Sample Implementations"
For most of our standards, we provide \fIsample\fP implementations
to demonstrate proof of concept.  These are not \fIreference\fP
implementations; the written specifications define the standards.
.Ip "Fonts"
.br
A collection of bitmap and outline fonts are included in the
distribution, contributed by various individuals and companies.
.Ip "Utility Libraries"
A number of libraries, such as the \fIAthena Widget Set\fP, are
included.  These are not standards, but are used in building
X Consortium applications and may be useful in building other applications.
.Ip "Sample Programs"
We also provide a number of application programs.
A few of these programs, such as \fIxdm\fP,
should be considered essential in almost all environments.
The rest of the applications carry no special status; they
are simply programs that have been developed and/or maintained
by X Consortium staff.
In some cases, you will find better substitutes for these
programs in the user-contributed part.
.LP
The user-contributed part contains whatever people contribute.
You'll find a variety of software and documentation here:
programs, demos, games, libraries,
X server extensions, etc.

.nH 2 "Supported Systems"

We built and tested this release on the following systems:

.ID
A/UX 3.0.1
AIX 3.2.5
BSD/386 1.0
HP-UX 9.1
IRIX 5.2
Mach 2.5 Vers 2.00.1
Microsoft Windows NT 3.1
NCR Unix System V Release 4/MP-RAS
NEWS-OS 6.0
OSF/1 1.3
OSF/1 1.0
SunOS 4.1.3
SunOS 5.3
UNICOS 8.0
UNIX System V/386 Release 4.2 Version 1
Unix System V/860 Release 4.0 Version 3
Ultrix-32 4.3
.DE

On NT, most of the release builds with the Microsoft SDK.  Missing are
\fIFresco\fP, \fItwm\fP, \fIxterm\fP, \fIxdm\fP, \fIxconsole\fP,
\fIxinit\fP, \fIxhost\fP, \fIxsm\fP, and the X server.  Xt, Xaw, and
Xmu libraries are not built as DLLs.  Imake works, albeit with some
restrictions.

.nH 2 "The XC Tree"

The first thing you may notice is that you can't find anything.
The source tree has undergone a major reorganization since R5.
The top-level directory has been renamed from \fBmit/\fP to \fBxc/\fP.

The general layout under \fBxc/\fP is now as
follows:

.DS L
.ta 2i
config/ 	config files, \fIimake\fP, \fImakedepend\fP, build utilities
doc/    	all documentation other than per-program manual pages
fonts/  	BDF, Speedo, Type1 fonts
include/	include files shared by multiple directories
lib/    	all libraries
nls/    	localization files
programs/	all programs, including the X server and \fIrgb\fP
test/   	X Test Suite and other test suites
util/   	\fIpatch\fP, \fIcompress\fP, other utilities
workInProgress/	snapshots of work in progress
bug-report	bug reporting template
registry	X Registry
.DE

.nH 3 "config/"

The \fBxc/config\fP directory now has subdirectories:
.LD
.ta 2i
config/cf/	all the config files: Imake.tmpl, Project.tmpl, etc.
config/imake/	the \fIimake\fP program
config/makedepend/	the \fImakedepend\fP program
config/util/	other configuration utility programs and scripts
.DE

.nH 3 "lib/"

Xlib sources are in \fBxc/lib/X11\fP; we've renamed directories to match the
lib\fIname\fP.a names.

.nH 3 "doc/"

.LD
.ta 2i
doc/specs/	X Consortium standards and other specifications 
doc/man/		manual pages for libraries and general manual pages
doc/util/	macro packages and utilities for formatting
doc/hardcopy/	PostScript versions of the documentation
.DE
.LP
The \fBxc/doc/hardcopy\fP directory contains compressed, pre-formatted
PostScript versions of documentation elsewhere in the
\fBdoc\fP tree and the program manual pages, which are in each
program's source directory.  These files can be uncompressed with the
\fIcompress\fP program, which is included in \fBxc/util/compress\fP.

.nH 3 "extensions"

There is no longer a top-level extensions directory.  Extension
libraries are now under \fBxc/lib/\fP, server extension code is
under \fBxc/programs/Xserver/Xext/\fP, and extension header files are
under \fBxc/include/extensions/\fP.

.nH 2 "Extensions supported"

The core distribution includes the following extensions:
BIG-REQUESTS,
LBX,
MIT-SHM,
MIT-SUNDRY-NONSTANDARD,
Multi-Buffering,
RECORD,
SHAPE,
SYNC,
X3D-PEX,
XC-MISC,
XIE,
XInputExtension,
XKEYBOARD,
XTEST, and
XTestExtension1.

.nH 2 "Implementation Parameters"

Some of the specifications define some behavior as
implementation-dependent.
Implementations of X Consortium standards need to document how those
parameters are implemented; this section does so.
.IP "XFILESEARCHPATH default"
This default can be set at build time by setting the \fIimake\fP variables
.hw XAppLoadDir
XFileSearchPathDefault, XAppLoadDir, XFileSearchPathBase, and
ProjectRoot in \fBsite.def\fP.  See \fBxc/config/cf/Project.tmpl\fP
for how they are used.
.IP
By default, XFILESEARCHPATH has these components:
.ID
/usr/X11R6/lib/X11/%L/%T/%N%C%S
/usr/X11R6/lib/X11/%l/%T/%N%C%S
/usr/X11R6/lib/X11/%T/%N%C%S
/usr/X11R6/lib/X11/%L/%T/%N%S
/usr/X11R6/lib/X11/%l/%T/%N%S
/usr/X11R6/lib/X11/%T/%N%S
.DE
.IP "XUSERFILESEARCHPATH default"
If the environment variable XAPPLRESDIR is defined, the default value
of XUSERFILESEARCHPATH has the following components:
.ID
$XAPPLRESDIR/%L/%N%C
$XAPPLRESDIR/%l/%N%C
$XAPPLRESDIR/%N%C
$HOME/%N%C
$XAPPLRESDIR/%L/%N
$XAPPLRESDIR/%l/%N
$XAPPLRESDIR/%N
$HOME/%N
.DE
Otherwise it has these components:
.ID
$HOME/%L/%N%C
$HOME/%l/%N%C
$HOME/%N%C
$HOME/%L/%N
$HOME/%l/%N
$HOME/%N
.DE
.IP "XKEYSYMDB default"
Defaults to \fB/usr/X11R6/lib/X11/XKeysymDB\fP, assuming
\fBProjectRoot\fP is set to \fB/usr/X11R6\fP.
.IP "XCMSDB default"
Defaults to \fB/usr/X11R6/lib/X11/Xcms.txt\fP, assuming
\fBProjectRoot\fP is set to \fB/usr/X11R6\fP.
.IP "XLOCALEDIR default"
Defaults to the directory \fB/usr/X11R6/lib/X11/locale\fP, assuming
\fBProjectRoot\fP is set to \fB/usr/X11R6\fP.
.IP "XErrorDB location"
The Xlib error database file is \fB/usr/X11R6/lib/X11/XErrorDB\fP, assuming
\fBProjectRoot\fP is set to \fB/usr/X11R6\fP.
.IP "XtErrorDB location"
The Xt error database file is \fB/usr/X11R6/lib/X11/XtErrorDB\fP, assuming
\fBProjectRoot\fP is set to \fB/usr/X11R6\fP.
.IP "Supported Locales"
For a list of locales supported, see the files \fBlocale.dir\fP and
\fBlocale.alias\fP in the \fBxc/nls/X11/locale/\fP directory.
.IP "Input Methods supported"
The core distribution does not include any input methods servers.
However, in
Latin-1 locales, a default method that supports European compose
processing is enabled.  See \fBxc/nls/X11/locale/Compose/iso8859-1\fP
for the supported compositions.
There are input method servers in contrib.

.nH 1 "Building X"

This section gives detailed instructions for building Release 6:
getting it off the
distribution medium, configuring,
compiling, installing, running, and updating.
.LP
More recent information about newly-discovered problems may be found
in the \fIFrequently Asked Questions\fP posting appearing monthly on
the comp.windows.x newsgroup and xpert mailing list.  It is also
available via anonymous FTP
on \fBftp.x.org\fP in the file \fBcontrib/faqs/FAQ.Z\fP,
or on your local X mirror site.

.nH 2 "Unpacking the Distribution"

The distribution normally comes as multiple tar files, either on
tape or across a network, or as a CD-ROM.
.LP
If you are unpacking tar files, you will need about 150 megabytes to
hold the \fBxc/\fP part.

.nH 3 "Unpacking a Compressed FTP Distribution"

If you have obtained compressed tar files over the network,
create a directory to hold the sources and \fIcd\fP into it:
.ID
mkdir \fIsourcedir\fP
cd \fIsourcedir\fP
.DE
Then for each tar file \fBxc\-*.tar.Z\fP, execute this:
.ID
zcat\0\fIftp-dir\fP/xc\-\fIN\fP.tar.Z | tar xpf\0\-
.DE
.LP
For each tar file \fBcontrib\-*.tar.Z\fP, execute this:
.ID
zcat\0\fIftp-dir\fP/contrib\-\fIN\fP.tar.Z | tar xpf\0\-
.DE

.nH 3 "Unpacking a gzipped FTP Distribution"

If you have obtained gzipped tar files over the network,
create a directory to hold the sources and \fIcd\fP into it:
.ID
mkdir \fIsourcedir\fP
cd \fIsourcedir\fP
.DE
Then for each tar file \fBxc\-*.tar.gz\fP, execute this:
.ID
gunzip\0\-c\0\fIftp-dir\fP/xc\-\fIN\fP.tar.gz | tar xpf\0\-
.DE
.LP
For each tar file \fBcontrib\-*.tar.gz\fP, execute this:
.ID
gunzip\0\-c\0\fIftp-dir\fP/contrib\-\fIN\fP.tar.gz | tar xpf\0\-
.DE

.nH 3 "Unpacking a Split Compressed FTP Distribution"

If you have obtained compressed and split tar files over the network,
create a directory to hold the sources:
.ID
mkdir \fIsourcedir\fP
.DE
Then for each directory \fBxc\-*\fP:
.ID
cd \fIftp-dir\fP/xc\-\fIN\fP
cat xc\-\fIN\fP.?? | uncompress | (cd \fIsourcedir\fP\|; tar xpf\0\-\|)
.DE
.LP
For each directory \fBcontrib\-*\fP, execute this:
.ID
cd \fIftp-dir\fP/contrib\-\fIN\fP
cat contrib\-\fIN\fP.?? | uncompress | (cd \fIsourcedir\fP\|; tar xpf\0\-\|)
.DE

.nH 3 "Unpacking the Tape Distribution"

If you have obtained a tape,
create a directory to hold the sources and untar everything into that
directory:
.ID
mkdir \fIsourcedir\fP
cd \fIsourcedir\fP
tar xpf \fItape-device\fP
.DE

.nH 3 "Using the CD-ROM"

If you have obtained a CD-ROM, you don't have to do anything to unpack
it.  However, you will have to create a symbolic link tree to build X.
See the next section.

.nH 2 "Apply Patches"

If there are fixes released, apply them now.
Follow the instructions at the top
of each patch, but don't do any make commands.  Then
continue here.

.nH 2 "Symbolic Link Trees"

If you expect to build the distribution on more than one machine using
a shared source tree,
or you are building from CD-ROM,
or you just want to keep the source tree pure,
you may want to use the program \fBxc/config/util/lndir.c\fP to create
a symbolic link tree on each build machine.
The links may use an additional 10 megabytes, but it is cheaper
than having multiple copies of the source tree.
.LP
It may be tricky to compile \fIlndir\fP before the distribution is
built.  If you have a copy from Release 5, use that.
\fBMakefile.ini\fP can be used for building \fIlndir\fP the first time.
You may have to specify \fBOSFLAGS=\-D\fP\fIsomething\fP to
get it to compile.
What you would pass as \fBBOOTSTRAPCFLAGS\fP might work.
The command line looks something like this:
.ID
make\0\-f\0Makefile.ini\0OSFLAGS=\-D\fIflag\fP
.DE
.LP
To use a symbolic link tree, create a directory for the build, \fIcd\fP
to it, and type this:
.ID
lndir \fIsourcedir\fP
.DE
.LP
where \fIsourcedir\fP is the pathname of the
directory where you stored the sources.  All of the build instructions
given below should then be done in the build directory on each machine,
rather than in the source directory.
.LP
\fBxc/config/util/mkshadow/\fP contains \fImkshadow\fP, an alternative
program to \fIlndir\fP.

.nH 2 "Configuration Parameters"

Build information for each source directory is in files called
\fBImakefile\fP.  An \fBImakefile\fP, along with local configuration
information in \fBxc/config/cf/\fP, is used by the program \fIimake\fP
to generate a \fBMakefile\fP.
.LP
Most of the configuration work prior to building the release is to
set parameters so that \fIimake\fP will generate correct files.
Most of those parameters are set in \fBxc/config/cf/site.def\fP.
You will also need to check the appropriate
\fBxc/config/cf/\fP\fIvendor\fP\fB.cf\fP file to make sure that
OSMajorVersion, OSMinorVersion, and OsTeenyVersion are set correctly
for your system (change them if necessary).
.LP
The \fBsite.def\fP file has two parts, one protected with
\*Q#ifdef BeforeVendorCF\*U and one with \*Q#ifdef AfterVendorCF\*U.
The file is actually processed twice, once before the \fB.cf\fP file
and once after.  About the only thing you need to set in the \*Qbefore\*U
section is \fBHasGcc2\fP; just about everything else can be set in the
\*Qafter\*U section.
.LP
The sample \fBsite.def\fP also has commented out support to include another 
file, \fBhost.def\fP.  This scheme may be useful if you want to set most
parameters site-wide, but some parameters vary from machine to machine.
If you use a symbolic link tree, you can share \fBsite.def\fP across
all machines, and give each machine its own copy of \fBhost.def\fP.
.LP
The config parameters are listed in \fBxc/config/cf/README\fP, but
here are some of the more common parameters that you may wish to set in
\fBsite.def\fP.
.Ip "ProjectRoot"
The destination where X will be installed.  This variable needs to be
set before you build, as some programs that read files at run-time
have the installation directory compiled in to them.  Assuming you
have set the variable to some value /\fIpath\fP, files will be
installed into /\fIpath\fP/bin, /\fIpath\fP/include/X11,
/\fIpath\fP/lib, and /\fIpath\fP/man.
.Ip "HasGcc"
Set to \fBYES\fP to build with \fIgcc\fP version 1.
.Ip "HasGcc2"
Set to \fBYES\fP to build with \fIgcc\fP version 2.
Both this option and \fBHasGcc\fP look for a compiler named \fIgcc\fP,
but \fBHasGcc2\fP will cause the build to use more features of
\fIgcc\fP 2, such as the ability to compile shared libraries.
.Ip "HasCplusplus"
Declares the system has a C++ compiler.  C++ is necessary to build
\fIFresco\fP.  On some systems, you may also have to set additional
variables to say what C++ compiler you have.
.Ip "DefaultUsrBin"
This is a directory where programs will be found even if PATH
is not set in the environment.
It is independent of ProjectRoot and defaults to \fB/usr/bin\fP.
It is used, for example, when connecting from a remote system via \fIrsh\fP.
The \fIrstart\fP program installs its server in this directory.
.Ip "InstallServerSetUID"
Some systems require the X server to run as root to access the devices
it needs.  If you are on such a system and will not be using
\fIxdm\fP, you can set this variable to \fBYES\fP to install the X
server setuid to root.  Note that the X server has not been analyzed
by the X Consortium for security in such an installation;
talk to your system manager before setting this variable.
.Ip "MotifBC"
Causes Xlib and Xt to work around some bugs in older versions of Motif.
Set to \fBYES\fP only if you will be linking with Motif version 1.1.1,
1.1.2, or 1.1.3.
.Ip "GetValuesBC"
Setting this variable to \fBYES\fP allows illegal XtGetValues requests
with NULL ArgVal to usually succeed, as R5 did.  Some applications
erroneously rely on this behavior.  Support for this will be removed
in a future release.
.LP
The following \fIvendor\fP\fB.cf\fP files are in the release but have
not been tested recently and hence probably need changes to work:
\fBDGUX.cf\fP, \fBMips.cf\fP, \fBapollo.cf\fP, \fBbsd.cf\fP,
\fBconvex.cf\fP, \fBmoto.cf\fP, \fBpegasus.cf\fP, \fBx386.cf\fP.
\fBAmoeba.cf\fP is known to require additional patches.
.LP
The file \fBxc/lib/Xdmcp/Wraphelp.c\fP, for XDM-AUTHORIZATION-1, is not
included in this release.  The file is available within the US;
for details get
\fB/pub/R6/xdm-auth/README\fP from ftp.x.org via anonymous FTP.

.nH 2 "System Notes"

This section contains hints on building X with specific compilers and
operating systems.

.nH 3 "gcc"

\fIgcc\fP version 2 is in regular use at the X Consortium.
You should have no
problems using it to build.  Set the variable \fBHasGcc2\fP.
X will not compile on some systems with \fIgcc\fP version 2.5, 2.5.1, or
2.5.2 because of an incorrect declaration of memmove() in a gcc
include file.

.nH 3 "SparcWorks 2.0"

If you have a non-threaded
program and want to debug it with the old SparcWorks 2.0 dbx,
you will need to use the thread stubs library in
\fBxc/util/misc/thr_stubs.c\fP.
Compile it as follows:
.ID
cc -c thr_stubs.c
ar cq libthr_stubs.a thr_stubs.o
ranlib libthr_stubs.a
.DE
Install libthr_stubs.a in the same directory with your X libraries
(e.g., \fB/usr/X11R6/lib/libthr_stubs.a\fP).
Add the following line to \fBsite.def\fP:
.ID
#define ExtraLibraries\0\-lsocket\0\-lnsl $(CDEBUGFLAGS:\-g=\-lthr_stubs)
.DE
This example uses a \fImake\fP macro substitution; not all \fImake\fP
implementations support this feature.

.nH 3 "CenterLine C under Solaris 2.3"

If you are using the CenterLine C compiler to compile the distribution
under Solaris 2.3,
place the following line in your \fBsite.def\fP:
.ID
#define HasCenterLineC YES
.DE
If clcc is not in your default search path, add this line to \fBsite.def\fP:
.ID
#define CcCmd /path/to/your/clcc
.DE
.LP
If you are using CodeCenter 4.0.4 or earlier, the following files 
trigger bugs in the \fIclcc\fP optimizer:
.ID
xc/programs/Xserver/cfb16/cfbgetsp.c
xc/programs/Xserver/cfb16/cfbfillsp.c
xc/programs/Xserver/cfb/cfbgetsp.c
.DE
.LP
Thus to build the server, you will have to compile these files by hand
with the \fB\-g\fP flag:
.ID
% cd xc/programs/Xserver/cfb16
% make CDEBUGFLAGS="\-g" cfbgetsp.o cfbfillsp.o
% cd ../cfb 
% make CDEBUGFLAGS="\-g" cfbgetsp.o
.DE
This optimizer bug appears to be fixed in CodeCenter 4.0.6.

.nH 3 "Microsoft Windows NT"

The set of operating systems that the client-side code will run on has been
expanded to include Microsoft Windows NT.  All of the base libraries are
supported, including multi-threading in Xlib and Xt, but some of the more
complicated applications, specifically \fIxterm\fP and \fIxdm\fP,
are not supported.
.LP
There are also some other rough edges in the
implementation, such as lack of support for non-socket file descriptors as Xt
alternate inputs and not using the registry for configurable parameters like
the system filenames and search paths.

.nH 2 "The Build"

On NT, type
.ID
nmake World.Win32 > world.log
.DE
On other systems, find the BootstrapCFlags line, if any, in the
\fIvendor\fP\fB.cf\fP file.  If there isn't one, type
.ID
make World >& world.log
.DE
otherwise type
.ID
make World BOOTSTRAPCFLAGS="value" >& world.log
.DE
.LP
You can call the output file something other than \*Qworld.log\*U, but
do not call it \*Qmake.log\*U because files with this name are
automatically deleted during the \*Qcleaning\*U stage of the build.
.LP
Because the build can take several hours to complete, you will probably
want to run it in the background and keep a watch on the output.
For example:
.ID
make World >& world.log &
tail\0\-f\0world.log
.DE
.LP
If something goes wrong, the easiest thing is to just start over
(typing \*Qmake World\*U again) once you have corrected the problem.
It is possible that a failure will corrupt the top-level \fBMakefile\fP.
If that happens, simply delete the file and recreate a workable
substitute:
.ID
cp Makefile.ini Makefile
.DE

.nH 2 "Installing X"

If everything is built successfully, you can install the software
by typing the following as root:
.ID
make install >& install.log
.DE
.LP
Again, you might want to run this in the background and use \fItail\fP
to watch the progress.
.LP
You can install the manual pages by typing the following as root:
.ID
make install.man >& man.log
.DE

.nH 2 "Shared Libraries"

Except on SunOS 4, the version number of all the shared libraries has
changed to \fB6.0\fP.  If you want programs linked against previous
versions of the libraries to use the R6 libraries, create a link from
the old name to the new name.

.nH 2 "Setting Up xterm"

If your \fB/etc/termcap\fP and \fB/usr/lib/terminfo\fP databases do
not have correct entries for \fIxterm\fP, use the sample entries
provided in the directory \fBxc/programs/xterm/\fP.  System V users
may need to compile and install the \fBterminfo\fP entry with the
\fItic\fP utility.
.LP
Since each \fIxterm\fP will need a separate pseudoterminal,
you need a reasonable number of them for normal execution.
You probably will want at least 32 on a small, multiuser system.
On most systems, each pty has two devices, a master and a slave,
which are usually named /dev/tty[pqrstu][0-f] and /dev/pty[pqrstu][0-f].
If you don't have at least the \*Qp\*U and \*Qq\*U sets configured
(try typing \*Qls /dev/?ty??\*U), you should have your system administrator
add them.  This is commonly done by running the \fIMAKEDEV\fP script in
the \fB/dev\fP directory with appropriate arguments.

.nH 2 "Starting Servers at System Boot"

The \fIxfs\fP and \fIxdm\fP programs are designed to be run
automatically at system startup.  Please read the manual pages for
details on setting up configuration files; reasonable sample files are
in \fBxc/programs/xdm/config/\fP and \fBxc/programs/xfs/\fP.
.LP
If your system uses an \fB/etc/rc\fP file at boot time, you can
usually enable these programs by placing the following at or near the end
of the file:
.ID
if [ \-f /usr/X11R6/bin/xfs ]; then
        /usr/X11R6/bin/xfs &; echo \-n ' xfs'
fi

if [ \-f /usr/X11R6/bin/xdm ]; then
        /usr/X11R6/bin/xdm; echo \-n ' xdm'
fi
.DE
.LP
Since \fIxfs\fP can serve fonts over the network,
you do not need to run a font server on every machine with
an X display.  You should start \fIxfs\fP before \fIxdm\fP, since
\fIxdm\fP may start an X server which is a client of the font server.
.LP
The examples here use \fB/usr/X11R6/bin\fP, but if you have installed into
a different directory by setting (or unsetting) \fBProjectRoot\fP then you
need to substitute the correct directory.
.LP
If you are unsure about how system boot works, or if your system does
not use \fB/etc/rc\fP, consult your system administrator for help.

.nH 2 "Using OPEN LOOK applications"

You can use the X11R6 Xsun server with OPEN LOOK applications, but you
must pass the new \fB\-swapLkeys\fP flag to the server on startup, or the 
OPEN LOOK Undo, Copy, Paste, Find, and Cut keys may not work correctly.
For example, to run Sun's OpenWindows 3.3 desktop environment with an
X11R6 server, use the command:
.ID
% openwin\0\-server\0/usr/X11R6/bin/Xsun\0\-swapLkeys
.DE
.LP
The keysyms reported by keys on the numeric keypad have also changed 
since X11R5; if you find that OpenWindows applications do not respond 
to keypad keys and cursor control keys when using the R6 server, you 
can remap the keypad to generate R5 style keysyms using the following 
\fIxmodmap\fP commands:
.ID
keysym Pause = F21
keysym Print = F22
keysym Break = F23
keysym KP_Equal = F24
keysym KP_Divide = F25
keysym KP_Multiply = F26
keysym KP_Home = F27
keysym KP_Up = Up
keysym KP_Prior = F29
keysym KP_Left = Left
keycode 100 = F31
keysym KP_Right = Right
keysym KP_End = F33
keysym KP_Down = Down
keysym KP_Next = F35
keysym KP_Insert = Insert
keysym KP_Delete = Delete
.DE

.nH 2 "Rebuilding after Patches"

You shouldn't need this right away, but eventually you are probably
going to make changes to the sources, for example by applying
X Consortium public patches.
.LP
Each patch comes with explicit instructions at the top of it saying
what to do.  Thus the procedure here is only an overview of the types
of commands that might be necessary to rebuild X after changing it.
.LP
If you are building from CD-ROM, apply the patches to the symbolic
link tree.  The links to changed files will be replaced with a local
file containing the new contents.
.LP
If only source files are
changed, you should be able to rebuild just by going to the \fBxc\fP
directory in your build tree and typing:
.ID
make >& make.log
.DE
.LP
If configuration files are changed, the safest thing to do is type:
.ID
make Everything >& every.log
.DE
.LP
\*QEverything\*U is similar to \*QWorld\*U in that it rebuilds every
\fBMakefile\fP, but unlike \*QWorld\*U it does not delete the
existing objects, libraries, and executables, and only rebuilds
what is out of date.
.LP
Note that in both kinds of rebuilds you do not need to supply the
\fBBootstrapCFlags\fP value any more; the information is already recorded.

.nH 2 "Building Contributed Software"

The software in \fBcontrib\fP is not set up to have everything
built automatically.  It is assumed that you will build individual
pieces as you find the desire, time, and/or disk space.  You need
to have the X Consortium part built and installed before building the
contributed software.  To build a program or library in \fBcontrib\fP,
look in its directory for any special build instructions (for example,
a \fBREADME\fP file).  If there are none, and there is an \fBImakefile\fP,
\fIcd\fP to the directory and type:
.ID
xmkmf\0\-a
make >& make.log
.DE
.LP
This will build a \fBMakefile\fP in the directory and all subdirectories,
and then build the software.  If the build is successful, you should be
able to install it using the same commands used for the \fBxc\fP
software:
.ID
make install >& install.log
make install.man >& man.log
.DE

.nH 1 "What Is New in Release 6"

This section describes changes in the X Consortium distribution since
Release 5.  Release 6 contains much new functionality in many areas.
In addition, many bugs have been fixed.  However, in the effort to
develop the new technology in this release, some bugs, particularly in
client programs, did not get fixed.
.LP
Except where noted, all libraries, protocols, and servers are upward
compatible with Release 5.  That is, R5 clients and applications should
continue to work with R6 libraries and servers.

.nH 2 "New Standards"

The following are new X Consortium standards in Release 6.
Each is described in its own section below.
.ID
X Image Extension
Inter-Client Communications Conventions Manual (update)
Inter-Client Exchange Protocol
Inter-Client Exchange Library
X Session Management Protocol
X Session Management Library
Input Method Protocol
X Logical Font Descriptions (update)
SYNC extension
XTEST extension
PEX 5.1 Protocol (released after R5)
PEXlib (released after R5)
BIG-REQUESTS extension
XC-MISC extension
.DE

.nH 2 "XIE (X Image Extension)"

The sample implementation in Release 6 is a complete implementation of
full XIE 5.0 protocol, except for the
following techniques that are excluded from the SI:
.ID
.ta 2i
ColorAlloc:	Match, Requantize
Convolve:	Replicate
Decode:		JPEG lossless
Encode:		JPEG lossless
Geometry:	AntialiasByArea, AntialiasByLowpass
.DE
.LP
\fIxieperf\fP exercises the server functionality; it provides unit testing and
a reasonable measure of multi-element photoflo testing.
.LP
A draft standard of the XIElib specification is included in this
release and is open for Public Review.
The XIElib code matches the 5.0 protocol.
.LP
The JPEG compression and decompression code is based on the Independent JPEG
Group's (IJG) JPEG software, Release 4.  This software provides baseline
Huffman DCT encoding as defined by ISO/IEC DIS 10918-1, \*QDigital Compression
and Coding of Continuous-tone Still Images, Part 1: Requirements and
guidelines\*U, and was chosen as a basis for our implementation of JPEG
compression and decompression primarily because the IJG's design goals matched
ours for the implementation of the XIE SI: achieve portability and flexibility
without sacrificing performance.  Less than half of the files distributed by
the IJG have been incorporated into the XIE SI.  The IJG's software is made
available with restrictions; see
\fBxc/programs/Xserver/XIE/mixie/jpeg/README\fP.

.nH 2 "Inter-Client Communications Conventions Manual"

Release 6 includes version 2.0 of the ICCCM.  This version contains a
large number of changes and clarifications in the areas of window
management, selections, session management, and resource sharing.

.nH 3 "Window Management"

The circumstances under which the window manager is required to send
synthetic ConfigureNotify events have been clarified to ensure that
any ConfigureWindow request issued by the
client will result in a ConfigureNotify event, either from the server
or from the window manager.  We have also added advice about how a
client should inspect events so as to minimize the number of
situations where it is necessary to use the TranslateCoordinates
request.
.LP
The window_gravity field of WM_NORMAL_HINTS has a
new value, StaticGravity, which specifies that the
window manager should not shift the client window's location when reparenting
the window.
.LP
The base size in
the WM_NORMAL_HINTS property is now to be included in the aspect ratio
calculation.
.LP
The WM_STATE property now has a formal definition (it was previously
only suggested).

.nH 3 "Selections"

We have clarified the CLIENT_WINDOW, LENGTH, and MULTIPLE
targets.  We have also added a number of new targets for Encapsulated
PostScript and for the Apple Macintosh PICT structured graphics format.  We
have also defined a new selection property type C_STRING, which is a string of
non-zero bytes.  (This is in contrast to the STRING type, which excludes many
control characters.)
.LP
A selection requester can now pass parameters in with the request.
.LP
Another new facility is manager selections.  This use of the selection
mechanism is not to transfer data, but to allow clients known as \fImanagers\fP
to provide services to other clients.  Version 2.0 also specifies that window
managers should hold a manager selection.  At present, the only service
defined for window managers is to report the ICCCM version number to which the
window manager complies.  Now that this facility is in place, additional
services can be added in the future.

.nH 3 "Resource Sharing"

A prominent new addition in version 2.0 is the ability of clients to take
control of colormap installation under certain circumstances.  Earlier
versions of the ICCCM specified that the window manager had exclusive control
over colormap installation.  This proves to be inconvenient for certain
situations, such as when a client has the server grabbed.  Version 2.0 allows
clients to install colormaps themselves after having informed the window
manager.  Clients must hold a pointer grab for the entire time they are doing
their own colormap installation.
.LP
Version 2.0 also clarifies a number of rules about how clients can exchange
resources.  These rules are important when a client places a resource ID into
a hints property or passes a resource ID through the selection mechanism.

.nH 3 "Session Management"

Some of the properties in section 5 of ICCCM 1.1 are now obsolete, and
new properties for session management have been defined.

.nH 2 "ICE (Inter-Client Exchange)"

ICE provides a
common framework to build protocols on.  It supplies authentication, byte order
negotiation, version negotiation, and error reporting
conventions.  It supports multiplexing multiple protocols over a single
transport connection.  ICElib provides a common interface to these mechanisms
so that protocol implementors need not reinvent them.
.LP
An \fIiceauth\fP program was written to manipulate an ICE authority
file; it is very similar to the \fIxauth\fP program.

.nH 2 "SM (Session Management)"

The X Session Management Protocol (XSMP) provides a
uniform mechanism for users to save and restore their sessions
using the services of a network-based session manager.
It is built on ICE.  SMlib is the C interface to the protocol.
There is also support for XSMP in Xt.
.LP
A simple session manager, \fIxsm\fP is included in
\fBxc/workInProgress/xsm\fP.
.LP
A new protocol, rstart, greatly simplifies the task of starting applications
on remote machines.  It is built upon already existing remote execution
protocols such as \fIrsh\fP.  The most important feature that it adds is the 
ability to pass environment variables and authentication data to the 
applications being started.

.nH 2 "Input Method Protocol"
Some languages need complex pre-editing input methods, and such an
input method may be implemented separately from applications in a
process called an Input Method (IM) Server.  The IM Server handles the
display of pre-edit text and the user's input operation.  The Input
Method (IM) Protocol standardizes the communication between the IM
Server and the IM library linked with the application.
.LP
The IM Protocol is a completely new protocol, based on experience with R5's
sample implementations.  The following new features are added, beyond the
mechanisms in the R5 sample implementations:
.IP \(bu
The IM Server can support any of several transports for connection with
the IM library.
.IP \(bu
Both the IM Server and clients can authenticate each other for security.
.IP \(bu
A client can connect to an IM Server without restarting even if 
it starts up before the IM Server.
.IP \(bu
A client can initiate string conversion to the IM Server for re-conversion
of text.
.IP \(bu
A client can specify some keys as hot keys, which can be used to escape
from the normal input method processing regardless of the input method state.
.LP
The R6 sample implementation for the internationalization support in Xlib has
a new pluggable framework, with the capability of loading and switching locale
object modules dynamically.  For backward compatibility, the R6 sample
implementation can support the R5 protocols by switching to IM modules
supporting those protocols.  In addition, the framework provides the following
new functions and mechanisms:
.IP "X Locale database format:
An X Locale database format is defined, and the
subset of a user's environment dependent on language is provided as a plain
ASCII text file.  You can customize the behavior of Xlib without changing
Xlib itself.
.IP "ANSI C and non-ANSI C bindings"
The common set of methods and structures
are defined, which bind the X locale to the system locales within libc, and
a framework for implementing this common set under non-ANSI C base system is
provided.
.IP "Converters"
The sample implementation has a mechanism to support various 
encodings by pluggable converters, and provides the following converters:
.ID
   - Light weight converter for C and ISO 8859
   - Generic converter (relatively slow) for other encoding
   - High performance converter for Shift-JIS and EUC
   - Converter for UCS-2 defined in ISO/IEC 10646-1
.DE
You can add your converter using this mechanism for your
specific performance requirement. 
.IP "Locale modules"
The library is implemented such that input methods and
output methods are separated and are independent of each other.  Therefore,
an output-only client does not link with the IM code, and an input-only
client does not link with the OM code.  Locale modules can be loaded
on demand if the platform supports dynamic loading.
.IP "Transport Layer"
There are several kinds of transports for connection between the IM
library and the IM Server.  The IM Protocol is independent of a
specific transport layer protocol, and the sample implementation has a
mechanism to permit an IM Server to define the transports which the
IM Server is willing to use.  The sample implementation supports
transport over the X protocol, TCP/IP and DECnet.
.LP
There are IM Servers for Japanese and for Korean, internationalized
clients using IM services, and an IM Server developer's kit in
contrib.  The IM Server developer's kit hides the details of the IM
Protocol and the transport layer protocols, and hides the differences
between the R5 and R6 protocols from the IM Server developer, so that
an IM developer has an easier task in developing new IM Servers.

.nH 2 "X Logical Font Description"

The X Logical Font Description has been enhanced to include general 2D
linear transformations, character set subsets, and support for
polymorphic fonts.
See \fBxc/doc/specs/XLFD/xlfd.tbl.ms\fP for details.

.nH 2 "SYNC extension"

The Synchronization extension lets clients synchronize via the X server.
This eliminates the network delays and the differences in synchronization
primitives between operating systems.  The extension provides a general
Counter resource; clients can alter the value of a Counter, and can block
their execution until a Counter reaches a specific threshold.  Thus, for
example, two clients can share a Counter initialized to zero, one client can
draw some graphics and then increment the Counter, and the other client can
block until the Counter reaches a value of one and then draw some additional
graphics.

.nH 2 "BIG-REQUESTS extension"

The standard X protocol only allows requests up to
.ie t 2\s-3\v'-1n'18\v'1n'\s0
.el 2^18
bytes long.
A new protocol extension, BIG-REQUESTS, has been added that allows a
client to extend the length field in protocol requests to be a 32-bit
value.  This useful for PEX and other extensions that transmit complex
information to the server.

.nH 2 "XC-MISC extension"

A new extension, XC-MISC, allows clients to get back ID ranges from the
server.  Xlib handles this automatically under the covers.  This is useful for
long-running applications that use many IDs over their lifetime.

.nH 2 "XTEST extension"

The XTEST extension, which first shipped as a patch to Release 5, is included.

.nH 2 "Tree Reorganization"

Many of the directories under \fBxc/\fP (renamed from \fBmit/\fP) have
been moved.
See the section \fBThe XC Tree\fP for the new layout.
The reorganization has simplified
dependencies in the build process.
Once you get used to the new
layout, things will be easier to find.
.LP
Various filenames have been changed to minimize name conflicts on
systems
that limit file names to eight characters, a period, and three more
characters.  Conflicts remain for various header (.h) files.

.nH 2 "Configuration Files"

The configuration files have changed quite a bit, we hope in a mostly
compatible fashion.  The main config files are now in
\fBxc/config/cf\fP, imake sources are in \fBxc/config/imake\fP, and
makedepend sources are in \fBxc/config/makedepend\fP.  The \fIlndir\fP
program (for creating link trees) is in \fBxc/config/util\fP; there is
a \fBMakefile.ini\fP in that directory that may be useful to get
\fIlndir\fP built the first time (before you build the rest of the
tree).
.LP
The rules for building libraries have changed a lot; it is now much easier
to add a new library to the system.
.LP
The selection of \fIvendor\fP\fB.cf\fP file has moved from
\fBImake.tmpl\fP to a new \fBImake.cf\fP.
.LP
The config variable that was called ServerOSDefines in R5 has been renamed
to ServerExtraDefines, and applies globally to all X server sources.  The
variable ServerOSDefines now applies just to the os directory of the server.
.LP
There are a number of new config
variables dealing with C++, all of which have \*QCplusplus\*U in their names.
.LP
\*Q#\*U should no longer be thought of as a valid comment character in
Imakefiles; use \*QXCOMM\*U instead.
.LP
There are new variables (e.g., HasPoll, HasBSD44Sockets,
ThreadedX) and rules (SpecialCObjectRule).
Read \fBxc/config/cf/README\fP for details.
.LP
The way libraries get built has changed: the unshared library .o's are now
placed in a subdirectory rather than the shared library .o's.
.LP
Multi-threaded programs can often just include \fBThreads.tmpl\fP in their
\fBImakefile\fP to get the correct compile-time defines and libraries.

.nH 2 "Kerberos"

There is a new authorization scheme for X clients, MIT-KERBEROS-5.  It
implements MIT's Kerberos Version 5 user-to-user authentication.  See
the \fIXsecurity\fP manual page for details on how Kerberos works in X.
As with any other authentication protocol, \fIxdm\fP sets it up at
login time, and Xlib uses it to authenticate the client to the X server.
.LP
If you have Kerberos 5 on your system, set the HasKrb5 config variable
in \fBsite.def\fP to YES to enable Kerberos support.

.nH 2 "X Transport Library (xtrans)"

The X Transport Library is intended to combine all system and transport
specific code into a single place in the source tree.  This API should be used
by all libraries, clients and servers of the X Window System.
Note that this API is \fInot\fP an X Consortium standard;
it is merely in internal part of our implementation.
Use of this API
should allow the addition of new types of transports and support for new
platforms without making any changes to the source except in the X Transport
Interface code.
.LP
The following areas have been updated to use xtrans:
.ID
lib/X11 (including the Input Method code)
lib/ICE
lib/font/fc
lib/FS
XServer/os
xfs/os
.DE
.LP
The XDMCP code in xdm and the X server has not been modified to use xtrans.
.LP
No testing has been done for DECnet.

.nH 2 "Xlib"

Xlib now supports multi-threaded access to a single display
connection.  Xlib functions lock the display structure, causing other
threads calling Xlib functions to be suspended until the first thread
unlocks.  Threads inside Xlib waiting to read to or write from the X
server do not keep the display locked, so for example a thread hanging
on XNextEvent will not prevent other threads from doing output to the
server.
.LP
Multi-threaded Xlib runs on SunOS 5.3, DEC
OSF/1 1.3, Mach 2.5 Vers 2.00.1, AIX 2.3, and Microsoft Windows NT 3.1.
Locking for Xcms and I18N support has not been reviewed.  A version
of ico that can be compiled to use threads is in \fBcontrib/programs/ico\fP.
.LP
The Display and GC structures have been made opaque to normal application
code; references to private fields will get compiler errors.  You can work
around some of these by compiling with \-DXLIB_ILLEGAL_ACCESS, but better to
fix the offending code.
.LP
The Xlib implementation has been changed to support a form of
asynchronous replies, meaning that a request can be sent off to the
server, and then other requests can be generated without
waiting for the first reply to come back.  This is used to advantage in two
new functions, XInternAtoms and XGetAtomNames, which reduce what would
otherwise require multiple round trips to the server down to a single round
trip.  It is also used in some existing functions, such as
XGetWindowAttributes, to reduce two round trips to just one.
.LP
Lots of Xlib source files were renamed to fit better on systems
with short filenames.
The \*QX\*U prefix was dropped from most file names, and \*QCIE\*U and
\*QTekHVC\*U prefixes were dropped.
.LP
Support for using poll() rather than select() is implemented, selected by the
HasPoll config option.
.LP
The BIG-REQUESTS extension is supported.
.LP
The following Xlib functions are new in Release 6:
.ID
XInternAtoms, XGetAtomNames
XExtendedMaxRequestSize
XInitImage
XReadBitmapFileData
IsPrivateKeypadKey
XConvertCase
XAddConnectionWatch, XRemoveConnectionWatch, XProcessInternalConnection
XInternalConnectionNumbers
XInitThreads, XLockDisplay, XUnlockDisplay

XOpenOM, XCloseOM
XSetOMValues, XGetOMValues
XDisplayOfOM, XLocaleOfOM
XCreateOC, XDestroyOC
XOMOfOC
XSetOCValues, XGetOCValues
XDirectionalDependentDrawing, XContextualDrawing
XRegisterIMInstantiateCallback, XUnregisterIMInstantiateCallback
XSetIMValues

XAllocIDs
XESetBeforeFlush
_XAllocTemp, _XFreeTemp
.DE
.LP
Support for MIT-KERBEROS-5 has been added.

.nH 2 "Internationalization

Internationalization (also known as I18N, there being 18 letters between the
\fIi\fP and \fIn\fP) of the X Window System,
which was originally introduced in
Release 5, has been significantly improved in R6.  The R6 I18N architecture
follows that in R5, being based on the locale model used in ANSI C and POSIX,
with most of the I18N capability provided by Xlib.  R5 introduced a
fundamental framework for internationalized input and output.  It could enable
basic localization for left-to-right, non-context sensitive, 8-bit or
multi-byte codeset languages and cultural conventions.  However, it did not
deal with all possible languages and cultural conventions.  R6 also does not
cover all possible languages and cultural conventions, but R6 contains
substantial new Xlib interfaces to support I18N enhancements, in order to
enable additional language support and more practical localization.
.LP
The additional support is mainly in the area of text display.  In order to
support multi-byte encodings, the concept of a FontSet was introduced in R5.
In R6, Xlib enhances this concept to a more generalized notion of output
methods and output contexts.  Just as input methods and input contexts support
complex text input, output methods and output contexts support complex and
more intelligent text display, dealing not only with multiple fonts but also
with context dependencies.  The result is a general framework to enable
bi-directional text and context sensitive text display.

.nH 2 "Xt"

Support has been added for participation in session
management, with callbacks to application functionality in response to
messages from the session manager.
.LP
The entire library is now
thread-safe, allowing one thread at a time to enter the library and
protecting global data as necessary from concurrent use.
.LP
Support is
provided for registering event handlers for events generated by X
protocol extensions, and for dispatching those events to the
appropriate widget.
.LP
A mechanism has also been added for dispatching
events for non-widget drawables (such as pixmaps used within a widget)
to a widget.
.LP
Two new widget methods for instance allocation and
deallocation allow widgets to be treated as C++ objects in a C++
environment.
.LP
A new interface allows bundled changes to the managed set of children
of a Composite, reducing the visual disruption of multiple changes to
geometry layout.
.LP
Several new resources have been added to Shell
widgets, making the library compliant with the Release 6 ICCCM.
Parameterized targets of selections (new in Release 6) and the
MULTIPLE target are supported with new APIs.
.LP
Safe handling of POSIX
signals and other asynchronous notifications is now provided.
.LP
A hook
has been added to give notification of blocking in the event manager.
.LP
The client will be able to register callbacks on a per-display basis
for notification of a large variety of operations in the X Toolkit.
This feature is useful to external agents such as screen readers.
.LP
New String resource converters: XtStringToGravity and
XtCvtStringToRestartStyle.
.LP
The file search path
syntax has a new %D substitution that inserts
the default search path, making it easy
to prepend and append to the default search path.
.LP
The Xt implementation allows a configuration choice of poll or select for I/O
multiplexing, selectable at compile time by the HasPoll config option.
.LP
The Release 6 Xt implementation requires Release 6 Xlib.
Specifically, it uses the following new Xlib features:
XInternAtoms instead of multiple XInternAtom calls where possible,
input method support (Xlib internal connections), and
tests for the XVisibleHint in the flags of XWMHints.
.LP
When linking with Xt, you now need to also link with SMlib and ICElib.  This
is automatic if you use the XTOOLLIB make variable or XawClientLibs \fIimake\fP
variable in your \fBImakefiles\fP.
.LP
This implementation no longer allows NULL to be passed as the value in
the name/value pair in a request to XtGetValues.  The default behavior
is to print the error message \*QNULL ArgVal In XtGetValues\*U and
exit.  To restore the R5 behavior, set the config variable
\fBGetValuesBC\fP in \fBsite.def\fP.  The old behavior was never part
of the Xt specification, but some applications erroneously rely on it.
.LP
Motif 1.2 defines the types XtTypedArg and XtTypedArgList in VaSimpleP.h.
These types are now defined in IntrinsicP.h.
To work around the conflict, in Motif VaSimple.c, if IntrinsicP.h is
not already included before VaSimpleP.h, do so.  In VaSimpleP.h, fence
off the type declarations with #if (XT_REVISION < 6) and #endif.
.LP
See Chapter 13 of the Xt specification for more details.

.nH 2 "Xaw"

Some minor bugs have been fixed.  Please note that the Athena Widgets have
been and continue to be low on our priority list; therefore many bugs remain 
and many requests for enhancements have not been implemented.
.LP
Text and Panner widget translations have been augmented to include keypad 
cursor keysyms in addition to the normal cursor keysyms.
.LP
The Clock, Logo, and Mailbox widgets have moved to their respective
applications.
.LP
Internationalization support is now included.  Xaw uses native
widechar support when available, otherwise it uses the Xlib widechar routines.
Per system specifics are set in XawI18n.h.
.LP
The shared library major version number on SunOS 4 has been incremented
because of these changes.

.nH 3 "AsciiText"

The name AsciiText is now a misnomer, but has been retained for backward
compatibility.  A new resource, XtNinternational, has been added.  If the
value of the XtNinternational resource is False (the default) AsciiSrc 
and AsciiSink source and sink widgets are created, and the widget behaves
as it did for R5.  If the value is True, MultiSrc and MultiSink source and
sink widgets are created.  The MultiSrc widget will connect to an Input
Method Server if one is available, or if one isn't available, it will
use an Xlib internal pseudo input method that, at a minimum, does compose
processing.  Application programmers who wish to use this feature will need 
to add a call to XtSetLanguageProc to their programs.
.LP
The symbolic constant
FMT8BIT has been changed to XawFmt8Bit to be consistent with the new 
symbolic constant XawFmtWide.  FMT8BIT remains for backwards compatibility, 
however its use is discouraged as it will eventually be removed from the 
implementation.  See the Xaw manual for details.

.nH 3 "Command, Label, List, MenuButton, Repeater, SmeBSB, and Toggle"

Two new resources have been added, XtNinternational and XtNfontSet.  If 
XtNinternational is set to True the widget displays its text using the
specified fontset.  See the Xaw manual for details.    

.nH 2 "PEX"

In discussing PEX it is important to understand the nature of 3D graphics
and the purpose of the existence of the PEX SI.  The type of graphics for
which PEX provides support, while capable of being done in software, is
most commonly found in high performance hardware.  Creation and maintenance
of software rendering code is costly and resource consumptive.  The original
Sample Implementation for the PEX Protocol 5.0 was primarily intended for
consumption by vendors of the X Consortium who intended to provide PEX
products for sale.  This implementation was intended to be fairly complete
however it was understood that vendors who intended to commercialize it
would dispose of portions of it, often fairly substantial ones.  It was
therefore understood that functionality most likely to be disposed of by
them might be neglected in the development of a Sample Implementation.
As PEX is now a fairly mature standard distributed by most if not all major
vendors, and the standard itself has evolved from the 5.0 protocol level
to the 5.1 protocol level, the X Consortium and its supporting vendors have
recognized a need to focus on certain portions of the PEX technology while
deemphasizing others.
.LP
This release incorporates PEX functionality based upon the PEX 5.1
level protocol.  The PEX Sample Implementation (SI) is composed of
several parts.  The major components are the extension to the X
Server, which implements the PEX 5.1 protocol, and the client side
API, which provides a mechanism by
which clients can generate PEX protocol.
.LP
The API now provided with the PEX-SI is called PEXlib.  This is a
change from R5 which shipped an API based upon the ISO IS PHIGS and
PHIGS PLUS Bindings.  That API has been moved to contrib
in favor of the PEXlib API based upon the PEXlib 5.1
binding, which itself is an X Consortium standard.  The PEXlib binding
is a lower-level interface than the previous PHIGS binding was and
maps more closely to the PEX protocol itself.  It supports immediate
mode rendering functionality as well as the previous PHIGS workstation
modes and is therefore suited to a wider range of applications.  It is
also suited for the development of higher level APIs.  There are in
fact commercial implementations of the PHIGS API which utilize the
PEXlib API.
.LP
The PHIGS API based verification tool called InsPEX is moved to contrib.
A prototype of a possible new tool called
suspex is in the directory \fBcontrib/test/suspex\fP.  Suspex is PEXlib based.
.LP
Demo programs are no longer supported and have moved to contrib.

.nH 3 "PEX Standards and Functionality"

This release conforms to the PEX Protocol Specification 5.1 though it
does not implement all the functionality specified therein.
.LP
The release comes with 2 fonts, Roman and Roman_M (see the \fIUser's
Guide\fP for more details).
.LP
As discussed briefly above certain functionality is not implemented in this
Sample Implementation.  Most notably Hidden Line, Hidden Surface Removal is
not implemented.  This is a result of both architectural decisions and the
fact that it surely would have been replaced by vendors with proprietary
code.  A contributed implementation which supports some of the HLHSR
functionality utilizing a Z buffer based technique is available for ftp
from ftp.x.org in the directory contrib/PEX_HLHSR.
.LP
This release does not support monochrome displays, though it does support 8
bit and 24 bit color. 
.LP
Other functionality not complete in this release is:
.ID
Backface Attributes and Distinguish Flag
Font sharing between clients
Patterns, Hatches and associated attributes
Transparency
Depth Cueing for Markers
.DE
.LP
Double Buffering is available for the PHIGS Workstation subsets directly
through the workstation.  The buffer mode should be set on when creating the
workstation.  For immediate mode users double buffering is achieved via the
Multi Buffering Extension (aka MBX) found in the directory \fBxc/lib/Xext\fP.
.LP
PEX 5.1 protocol adds certain functionality to the Server extension,
accessible directly via the PEXlib API.  This functionality includes
Picking via the Immediate Mode Renderer (Render Elements and
Accumulate State commands in Chapter 6, all of Chapter 7); new Escape
requests to allow vendors to support optional functionality; a Match
Rendering Targets request to return information about visuals, depth
and drawables the server can support; a noop Output command;
Hierarchical HLHSR control (i.e., during traversals); and renderer
clearing controls are the most important features.

.nH 2 "Header Files"

Two new macros are defined in \fBXos.h\fP: X_GETTIMEOFDAY and strerror.
X_GETTIMEOFDAY is like gettimeofday() but takes one argument on all
systems.  strerror is defined only on systems that don't already have it.
.LP
A new header file \fBXthreads.h\fP provides a platform-independent
interface to threads functions on various systems.
Include it instead of the system threads header file.  Use the macros
defined in it instead of the system threads functions.


.nH 2 "Fonts"

There are three new Chinese bdf fonts in \fBxc/fonts/bdf/misc\fP
(\fBgb16fs.bdf\fP, \fBgb16st.bdf\fP, \fBgb24st.bdf\fP).
.LP
Bitmap Charter fonts that are identical to the output generated from
the outline font have been moved to
\fBxc/fonts/bdf/unnec_\fP{\fB75\fP,\fB100\fP}\fBdpi\fP.
.LP
The Type 1 fonts contributed by Bitstream, IBM, and Adobe that shipped
in contrib in Release 5 have been moved into the core.
.LP
Some of the \fBmisc\fP fonts, mostly in the \fIClean\fP family, have
only the ASCII characters, but were
incorrectly labeled \*QISO8859-1\*U.  These fonts have been renamed to
be \*QISO646.1991-IRV\*U.  Aliases have been provided for the Release
5 names.
.LP
The \fB9x15\fP font has new shapes for some characters.  The
\fB6x10\fP font has the entire ISO 8859-1 character set.

.nH 2 "Font library"

The Type1 rasterizer that shipped in contrib in Release 5 is now part
of the core.
.LP
There is an
option to have the X server request glyphs only as it needs them.
The X server then caches the glyphs for future use.
.LP
Aliases in a \fBfonts.alias\fP file can allow one scalable alias name to
match all instances of another font.  The \*Q!\*U character introduces
a comment line in \fBfonts.alias\fP files.
.LP
A sample font authorization protocol, \*Qhp-hostname-1\*U has been added.
It is
based on host names and is non-authenticating.  The client requesting
a font from a font server provides (or passes through from its client)
the host name of the ultimate client of the font.  There is no check
that this host name is accurate, as this is a sample protocol only.
.LP
The Speedo rasterizer can now read fonts with retail encryption.
This means that fonts bought over-the-counter at a computer store can
be used by the font server and X server.
.LP
Many, many bugs have been fixed.

.nH 2 "Font server"

The font server has been renamed from \fIfs\fP to \fIxfs\fP to avoid
confusion with an AFS program.  The default port has changed from 7000
(used by AFS) to 7100 and has been registered with the Internet
Assigned Numbers Authority.
.LP
The font server now implements a new major protocol version, version 2.
This change was made only to correct errors in the implementation of
version 1.  Version 1 is still accepted by \fIxfs\fP.
.LP
You can now connect to \fIxfs\fP using the \fBlocal/\fP transport.
.LP
Many, many bugs have been fixed.

.nH 2 "X server"

The server sources have moved to \fBxc/programs/Xserver\fP.
Server-side extension code exists as subdirectories.  The \fBddx\fP
directory is gone; \fBmi\fP, \fBcfb\fP, and \fBmfb\fP are at the top
level, and a \fBhw\fP (hardware) subdirectory now exists for holding
vendor-specific ddx code.  Note: the absence of a ddx directory does
not imply that the conceptual split between dix and ddx is gone.
.LP
Function prototypes have been added to header files in
\fBxc/programs/Xserver/include\fP, \fBcfb\fP, \fBmfb\fP, \fBmi\fP, and
\fBos\fP.
.LP
Support for pixmap privates has been added.  It is turned off by default, but
can be activated by putting \-DPIXPRIV in the ServerExtraDefines parameter in
your \fIvendor\fP\fB.cf\fP file.  See the porting layer document for details.
.LP
New screen functions, called primarily by code in window.c, have been added to
make life easier for vendors with multi-layered framebuffers.  Several
functions and some pieces of functions have moved from window.c to miwindow.c.
See the porting layer document for details.  Also, the contents of union
_Validate (validate.h) are now device dependent; mivalidate.h contains a
sample definition.
.LP
An implementation of the SYNC extension is in
\fBxc/programs/Xserver/Xext/sync.c\fP.
As part of this work, client priorities
have also been implemented; see the tail end of WaitForSomething() in
WaitFor.c.  The priority scheme is \fIstrict\fP in that the client(s)
with the highest priority always runs.  \fItwm\fP has been modified to
provide simple facilities for setting client priorities.
.LP
The server can now fetch font glyphs on demand instead of loading them
all at once.  See \fBxc/programs/Xserver/dix/dixfonts.c\fP,
\fBxc/lib/font/fc/fserve.c\fP, and \fBxc/lib/font/fc/fsconvert.c\fP.  A new
X server command line option, \fB\-deferglyphs\fP, controls which types of
fonts (8 vs. 16 bit) to demand load; see the X manual page for details.
.LP
The os layer now uses sigaction on POSIX systems; a new function OsSignal was
added for convenience, which you should use in your ddx code.
.LP
A new timer interface has been added to the os layer; see the functions in
os/WaitFor.c.  This interface is used by XKB, but we haven't tried to use it
anywhere else (such as Xext/sleepuntil.c) yet.
.LP
Redundant code for GC funcs was moved from cfbgc.c and mfbgc.c to migc.c.
This file also contains a few utility functions such as miComputeCompositeClip,
which replaces the chunk of code that used to appear near the top of most
versions of ValidateGC.
.LP
The cfb code can now be compiled multiple times to provide support for
multiple depths in the same server, e.g., 8, 12, and 24.
See \fBImakefile\fP and
\fBcfb/cfbmskbits.h\fP under the \fBxc/programs/Xserver/\fP directory
for starters.
.LP
The cfb and mfb code have been modified to perform 64 bit reads and writes of
the framebuffer on the Alpha AXP.  These modifications should be usable on
other 64 bit architectures as well, though we have not tested it on any
others.  There are a few hacks in dix, notably ProcPutImage and ProcGetImage,
to work around the fact that the protocol doesn't allow you to specify 64 bit
padding.  Note that the server will still not run on a machine such as a Cray
that does not have a 32 bit data type.
.LP
For performance, all region operations are now invoked via macros which by
default make direct calls to the appropriate mi functions.  You can
conditionally compile them to continue calling through the screen structure.
The following change was made throughout the server:
.ID
\*Q(*pScreen->RegionOp)(...)\*U changes to \*QREGION_OP(pScreen, ...)\*U
.DE
.LP
Some of the trivial region ops have been inlined in the macros.  For
compatibility, the region function pointers remain in the screen structure
even if the server is compiled to make direct calls to mi.  See
include/regionstr.h.
.LP
A generic callback manager is included and can be used to add
notification-style hooks anywhere in the server.  See dixutils.c.  The
callback manager is now being used to provide notification of when the
server is grabbed/ungrabbed, when a client's state changes, and when
an event is sent to a client.  The latter two are used by the RECORD
extension.
.LP
A new option has been added, \fB\-config\fP \fIfilename\fP.  This lets
you put server options in a file.  See \fBos/utils.c\fP.
.LP
Xtrans has been installed into the os layer.  See os/connection.c, io.c, and
transport.c.  As a result, the server now supports the many flavors of SVR4
local connections.
.LP
The client structure now has privates like windows, pixmaps, and GCs.  See
include/dixstruct.h, dix/privates.c, and dispatch.c.
.LP
Thin line pixelization is now consistent across cfb, mfb, and mi.  It
is also reversible, meaning the same pixels are touched when drawing
from point A to point B as are touched when drawing from point B to
point A.  A new header file, miline.h, consolidates some miscellaneous
line drawing utilities that had previously been duplicated in a number
of places.

.nH 3 "Xnest"

A new server, Xnest, uses Xlib to implement ddx rendering.  See
xc/programs/Xserver/hw/xnest.  Xnest lets you run an X server in a window on
another X server.  Uses include testing dix and extensions, debugging client
protocol errors, debugging grabs, and testing interactive programs in a
hardware-starved environment.

.nH 3 "Xvfb"

Another new server, Xvfb, uses cfb or mfb code to render into a
framebuffer that is allocated in virtual memory.  See
\fBxc/programs/Xserver/hw/vfb\fP.  The framebuffer can be allocated in
normal memory, shared memory, or as a memory mapped file.  Xvfb's
screen is normally not visible; however, when allocated as a memory
mapped file, \fIxwd\fP can display the screen by specifying the framebuffer
file as its input.

.nH 3 "ddx"

.Ip "Sun ddx"
Expanded device probe table finds multiple frame buffers of the same
type.  Expanded keymap tables provide support for European and Asian
keyboards.  Added per-key autorepeat support.  Considerable cleanup and
duplicate code eliminated.  Deletion of SunView support.  GX source code now
included.
.Ip "HP ddx"
cfb-based sources included as \fBxc/programs/Xserver/hw/hp\fP.
.Ip "svga ddx"
new svga ddx for SVR4 included as
\fBxc/programs/Xserver/hw/svga\fP.
.Ip "xfree86 ddx"
ddxen from XFree86, Inc. included as
\fBxc/programs/Xserver/hw/xfree86\fP.
.Ip "Amoeba ddx"
ddx for Sun server on the Amoeba operating system included
as \fBxc/programs/Xserver/hw/sunAmoeba\fP.  The server will require
additional patches for this to be usable.

.nH 2 "New Programs"

\fBxc/config/util/mkshadow/\fP, a replacement for \fIlndir\fP.

.nH 2 "Old Software"

We have dropped support for the following libraries and programs
and have moved them to \fBcontrib\fP:
CLX library,
PHIGS library,
\fIMacFS\fP,
\fIauto_box\fP,
\fIbeach_ball\fP,
\fIgpc\fP,
\fIico\fP,
\fIlistres\fP,
\fImaze\fP,
\fIpuzzle\fP,
\fIshowfont\fP,
\fIviewres\fP,
\fIxbiff\fP,
\fIxcalc\fP,
\fIxditview\fP,
\fIxedit\fP,
\fIxev\fP,
\fIxeyes\fP,
\fIxfontsel\fP,
\fIxgas\fP,
\fIxgc\fP,
\fIxload\fP,
\fIxman\fP, and
\fIxpr\fP.

.nH 2 "xhost"

Two new families have been registered: LocalHost, for connections over a
non-network transport, and Krb5Principal, for Kerberos V5 principals.
.LP
To distinguish between different host families, a new xhost syntax
\*Qfamily:name\*U has been introduced.  Names are as before; families are
as follows:
.ID
.ta 1i
inet:	Internet host
dnet:	DECnet host
nis:	Secure RPC network name
krb:	Kerberos V5 principal
local:	contains only one name, \*Q\^\*U
.DE
The old-style syntax for names is still supported when the name does not
contain a colon.

.nH 2 "xrdb"

Many new symbols are defined to tell you what extensions and visual
classes are available.

.nH 2 "twm"

An interface for setting client priorities with the Sync extension has been
added.
.LP
Many bugs have not been fixed yet.

.nH 2 "xdm"

There is a new resource, \fBchoiceTimeout\fP, that controls how long
to wait for a display to respond after the user has selected a host
from the chooser.
.LP
Support has been added for a modular, dynamically-loaded greeter
library.  This feature allows different dynamic libraries to by loaded
by \fIxdm\fP at run-time to provide different login window interfaces
without access to the \fIxdm\fP sources.  It works on DEC OSF/1 and SVR4.
The name of the greeter library is controlled by another new resource,
\fBgreeterLib\fP.
.LP
When you log in via \fIxdm\fP, \fIxdm\fP will use your password to
obtain the initial Kerberos tickets and store them in a local
credentials cache file.  The credentials cache is
destroyed when the session ends.

.nH 2 "xterm"

Now supports a few escape sequences from HP terminals, such as memory
locking.  See \fBxc/doc/specs/xterm/ctlseqs.ms\fP for details.
.LP
The \fBtermcap\fP and \fBterminfo\fP files have been updated.
.LP
\fBctlseqs.ms\fP has moved out of the xterm source directory into
\fBxc/doc/specs/xterm\fP.
.LP
The logging mis-feature of xterm is removed.  This change first appeared as
a public patch to Release 5.
.LP
Many bugs have not been fixed yet.

.nH 2 "xset"

The screen saver control option has two new sub-options
to immediately activate or deactivate the screen saver:
\fBxset s activate\fP and \fBxset s reset\fP.

.nH 2 "X Test Suite"

The X Test Suite, shipped separately from R5, is now part of the core
distribution in R6.
.LP
The code has been fixed to work on Alpha AXP.  The Xi tests contributed by HP
and XIM tests contributed by Sun are integrated.

.nH 2 "Work in Progress"

Everything under \fBxc/workInProgress\fP represents a work in progress
of the X Consortium.
.LP
Fresco, Low Bandwidth X (LBX), the Record extension, and the X Keyboard
extension (Xkb, which logically belongs here but was too tightly coupled
into Xlib and the server to extract) are neither standards nor draft
standards, are known to need design and/or implementation work, are
still evolving, and will not be compatible with any final standard should
such a standard eventually be agreed upon.
We are making them available in early form in order
to gather broader experimentation and feedback from those willing to
invest the time and energy to help us produce better standards.
.LP
Any use of these interfaces in commercial products runs the risk of
later source and binary incompatibilities.

.nH 3 "Fresco"

R6 includes the first sample implementation of Fresco, a user interface
system specified using CORBA IDL and implemented in C++.  Fresco is not
yet a Consortium standard or draft standard, but is being distributed as
a work in progress to demonstrate our current directions and to gather
feedback on requirements for a Fresco standard.
.LP
The Fresco Sample Implementation has been integrated into the X11R6
build process, and will be built automatically if you have a C++
compiler available.  Documentation on Fresco can be found in
\fBxc/doc/specs/Fresco\fP.  The Fresco and Xtf libraries are found in
\fBxc/workInProgress/Fresco\fP and \fBxc/workInProgress/Xtf\fP,
respectively.  There are some simple Fresco example programs in
\fBcontrib/examples/Fresco\fP, and a number of related programs in
\fBcontrib/programs\fP, including:
.Ip ixx
An IDL to C++ translator
.Ip i2mif
A program to generate FrameMaker MIF documents from comments in an IDL
specification
.Ip fdraw
A simple Fresco drawing editor
.Ip dish
A TCL interpreter with hooks to Fresco
.LP
Working Imakefiles are provided for all of the utilities and examples.
.LP
A demo program (dish) is included that shows how a scripting language (Tcl)
can rather easily be bound to Fresco through the CORBA dynamic invocation
mechanism.  A copy of Tcl is included in \fBcontrib/lib/tcl\fP.
.LP
To build Fresco you must define HasCplusplus in \fBsite.def\fP; in
addition, you may have to set CplusplusCmd and/or
CplusplusDependIncludes to invoke the appropriate C++ compiler and
find the required header files during make depend.  Finally, you
should check the \fIvendor\fP\fB.cf\fP to see if there are any other
configuration variables you should set to provide information about
your C++ compiler.
.LP
Fresco requires a C++ compiler that implements version 3 of the C++ language
(as approximately defined by USL cfront version 3).  While Fresco does 
not currently use templates or exceptions, it does make extensive use 
of nested types, which were inadequately supported in earlier versions of 
the language.
.LP
Fresco has been built with the following platforms and C++ compilers:
.ID
.ta 1.7i 3i
SPARCstation  	SunOS 4.1.3	CenterLine C++
SPARCstation	Solaris 2.3	CenterLine C++ (requires v2.0.6)
SPARCstation	Solaris 2.3	SPARCCompiler C++ v4.0
HP 9000/700	HPUX 9.0.1	CenterLine C++
SGI Indy	IRIX 5.2	SGI C++
IBM RS/6000	AIX 3.2.5	IBM xlC
Sony NEWS	NEWSOS 6.0	Sony C++
.DE
.LP
Fresco has also been compiled on the DEC Alpha under OSF/1 version 2.0 using
a beta test version of DEC C++ 1.3.  Fresco cannot be built with the Gnu C++ 
compiler (version 2.5.8 or earlier) due to bugs and limitations in g++.
.LP
Building Fresco with CenterLine C++ requires that you pass 
the \fB\-Xa\fP flag to the C++ compiler.  Place the following lines
in your site.def:
.ID
#define HasCenterLineCplusplus YES
#define CplusplusOptions\0\-Xa
.DE
If CC is not in your default search path, add this line to \fBsite.def\fP:
.ID
#define CplusplusCmd \fI/path/to/your/CC\fP
.DE
.LP
If you are building under Solaris 2, you must use ObjectCenter 
version 2.0.6 or later; the C++ compiler in ObjectCenter 2.0.4 
will produce Fresco applications that dump core on startup.
.LP
Fresco does not yet build under Microsoft Windows/NT.

.nH 3 "XKB (X Keyboard Extension)"

Support for XKB is not compiled in to Xlib by default.
It is compiled in the X server by default only on Sun and Omron Luna
machines.
You can compile it in by setting
.ID
.ta 3i
#define BuildXKB YES	/* for support in the X server */
#define BuildXKBLib YES	/* for support in the X library */
.DE
in the file \fBxc/config/cf/site.def\fP.  Note that enabling XKB in
the X server is a pervasive change; you need to clean the server and
rebuild everything if you change this option.
.LP
Turning on XKB in the X server usually requires changes to the vendor ddx
keyboard handling.  There is currently support only in the Sun and
Omron ddx.
.LP
If you turn on \fBBuildXKBLib\fP, additional functions are added to
Xlib.  Since the resulting library is non-standard, it is given a
different name: \fBlibX11kb\fP instead of \fBlibX11\fP.  All Makefiles
produced by \fIimake\fP will use \fB\-lX11kb\fP to link Xlib.
.LP
The library changes for XKB are known not to work on the Cray; 
many other systems have been tested, including the Alpha AXP.
.LP
There are some XKB test programs in \fBcontrib/test/Xkb\fP.
.LP
The XKB support in Xlib is still at an early stage of formal review
and could change.  We expect some additions in an eventual standard,
but few changes to the interfaces provided in this implementation.
A working draft of the protocol is in \fB/xc/doc/specs/Xkb/\fP.

.nH 3 "LBX (Low Bandwidth X)"

The X Consortium is working to define a standard for running X
applications over serial lines, wide area networks, and other slow
links.  This effort, called Low Bandwidth X (LBX), aims to improve the
startup time, performance, and interactive feel of X applications run
over low bandwidth transports.
.LP
LBX does this by interposing a \fIpseudo-server\fP (called the \fIproxy\fP)
between the X clients and the X server.  The proxy caches data flowing
between the server and the clients, merges the X protocol streams, and
compresses the data that is sent over the low bandwidth wire.  The X
server at the other end uncompresses the data and splits it back out
into separate request streams.  The target is to make
many X applications transparently usable over 9600 bps modems.
.LP
A snapshot of the code for this effort
is included in \fBxc/workInProgress/lbx/\fP for people to examine and begin
experimenting with.  It contains the following features:
.IP \(bu
LZW compression of the binary data stream.  Since commercial use
of LZW requires licensing patented technology, we are also looking
for an unencumbered algorithm and implementation to provide as well.
.IP \(bu
Delta compression of X packets (representing packets as differences
from previously sent packets).
.IP \(bu
Re-encoding of some graphics requests (points, lines, segments,
rectangles, and arcs).
.IP \(bu
Motion event throttling (to keep from flooding the wire).
.IP \(bu
Caching of data in the proxy for large data objects that otherwise
would be transmitted over the wire multiple times (e.g., properties,
font metrics, keyboard mappings, connection startup data, etc.).
.IP \(bu
Short-circuiting of requests for constant data (e.g., atoms,
colorname/rgb mappings, and read-only color cells).
.LP
However, the following items have yet to be implemented (which is why it
isn't a standard yet):
.IP \(bu
Re-encoding of a number of requests (e.g., QueryFont), events, etc.
.IP \(bu
Support for BIG-REQUESTS extension.
.IP \(bu
A non-networked serial protocol for environments which cannot
support os-level networking over serial lines.
.IP \(bu
A full specification needs to be written describing the network
protocol used between the proxy and the server.
.LP
The X Consortium is continuing to work on both the implementation of the
remaining items and the full specification.  The goal is to have all of the
pieces ready for public review later this year.  Since the
specification for LBX \fIwill\fP change,
we strongly recommend against anyone incorporating LBX into a product
based on this prototype.  But, they are encouraged to start looking
at the code, examining the concepts, and providing feedback on its design.

.nH 3 "RECORD extension"

RECORD is an X protocol extension that supports the recording of all
core X protocol and arbitrary X extension protocol.
.LP
A version of the extension is included in \fBxc/workInProgress/record\fP.
The implementation does not quite match the version 1.2 draft
specification, but the spec is going to change anyway; the version 1.3
draft is in \fBxc/doc/specs/Xext/record.ms\fP.
The GetConfig request is not fully implemented.
A test program is in \fBcontrib/test/record\fP.

.nH 3 "Simple Session Manager"

A simple session manager has been developed to test the new Session Management
protocol.
At the moment, it does not exercise the complete XSMP protocol and the user
interface is rather simple.
While it does have enough functionality to make it
useful, it needs more work before we would want
people to depend on it or use it as a good example of how to implement
the session protocol.
.IP \(bu
Handles accepting connections from clients
.IP \(bu
Handles graceful or unexpected termination of clients
.IP \(bu
Maintains database of all properties set by clients
.IP \(bu
User interface provides a way to issue checkpoint and shutdown
messages to clients
.IP \(bu
Manages client interaction with the user
.IP \(bu
Can restart clients.  Clients running on remote machines
are handled using the new \fIrstart\fP protocol.
.IP \(bu
Requires MIT-MAGIC-COOKIE-1 authentication from clients.
.LP
We have not yet written a proxy for
connecting ICCCM 1.0 clients to the session manager.
.LP
A sample client, \fIxsmclient\fP, has been written to demonstrate the
session support in Xt.

.nH 3 "Multi-Threaded X Server"

An attempt has been made to merge the multi-threaded server source
with the single-threaded source.  The result is in the
\fBxc/workInProgress/MTXserver\fP directory.
The sources here include only files that
were changed from the single-threaded server.
The multi-threaded server may not compile.
Unfortunately, the
single-threaded server sources have continued to evolve since this
snapshot of the MTXserver was produced, so there is work to be done to
get the MTXserver sources back into a state where they can be compiled.

.nH 2 "ANSIfication"

We've changed our sources to stop using the BSD function names index, rindex,
bcopy, bcmp; we now use strchr, strrchr, memcpy/memmove, and memcmp.  We still
use the name bzero (because there is no BSD equivalent for the general case of
memset) but it is translated to memset via a #define in <X11/Xfuncs.h>.  The
BSD function names are still supported in <X11/Xos.h> and <X11/Xfuncs.h>.
.LP
Most client-side uses of caddr_t should now be gone from our sources.
.LP
Explicit declarations of errno are now only used on
non-ANSI systems.
.LP
The libraries use more standard POSIX *_t types.

.nH 2 "Miscellaneous"

A new version of the \fIpatch\fP program is in \fBxc/util/patch\fP; it
understands the unified diff format produced by GNU \fIdiff\fP.

.nH 1 "Filing Bug Reports"

If you find a reproducible bug in software in the \fBxc\fP directory,
or find bugs in the \fBxc\fP documentation, please send a bug report
to the X Consortium using the form in the file \fBxc/bug-report\fP and
this destination address:
.ID
xbugs@x.org
.DE
.LP
Please try to provide all of the information requested on the form if it is
applicable; the little extra time you spend on the report will make it
much easier for us to reproduce, find, and fix the bug.  Receipt of bug
reports is generally acknowledged, but sometimes it can be delayed by a
few weeks.
.LP
Bugs in \fBcontrib\fP software should not be reported to the X
Consortium.  Consult the documentation for the individual software to
see where (if anywhere) to report the bug.

.nH 1 "Public Fixes"

We occasionally put out patches to X Consortium software, to fix any
serious problems that are discovered.  Such fixes (if any) can be found
on \fBftp.x.org\fP in the directory \fBpub/R6/fixes\fP,
or on your local X mirror site,
using anonymous FTP.
.LP
For those without FTP access, individual fixes can be obtained by
electronic mail by sending a message to
.ID
xstuff@x.org
.DE
.LP
In the usual case,
the message should have a subject line and no body, or a single-line body and
no subject, in either case the line looking like:
.ID
send fixes \fInumber\fP
.DE
.LP
where \fInumber\fP is a decimal number, starting from one.  To get a
summary of available fixes, make the line:
.ID
index fixes
.DE
.LP
If you need help, make the line:
.ID
help
.DE
.LP
Some mailers produce mail headers that are unusable for extracting return
addresses.  If you use such a mailer, you won't get any response.  If you
happen to know an explicit return path, you can include include one in the
body of your message, and the daemon will use it.  For example:
.ID
path \fIuser\fP%\fIhost\fP.bitnet@mitvma.mit.edu
.DE

.nH 1 "Acknowledgements"

Release 6 of X Version 11 is brought to you by X Consortium, Inc:
Bob Scheifler,
Janet O'Halloran,
Ralph Swick,
Matt Landau,
Donna Converse,
Stephen Gildea,
Jay Hersh,
Kaleb Keithley,
Ralph Mor,
Dave Wiggins,
and Gary Cutbill.
.LP
Many companies and individuals have cooperated and worked extremely hard to
make this release a reality, and our thanks go out to them.  You will find
many of them listed in the acknowledgements in the individual specifications.
Major implementation contributions come from
Data General, Digital, Fujitsu, HP, NCD, NCR, Omron, SGI, Sony, SunSoft,
and XFree86.
.LP
Contributions were received from the follow people at various
X Consortium member companies.
Each X Window System release is the work of many, many people, and
this list is surely incomplete.
.IP "Fresco"
.br
Mark Linton (Silicon Graphics);
Chuck Price (SunSoft);
Charles Brauer (Fujitsu);
Steve Churchill (Fujitsu);
Steve Tang (Stanford University);
Douglas Pan (Fujitsu);
Jean-Daniel Fekete (2001 S.A.)
.IP "Xlib"
.br
Courtney Loomis (Hewlett-Packard Company);
Daniel Dardailler (Open Software Foundation)
.\"
.IP "Xlib internationalization"
The manager of the internationalization project is
Masahiko Narita (Fujitsu).
The principal authors of Input Method Protocol document are
Hideki Hiura (SunSoft) and Masahiko Narita (Fujitsu).
The principal authors of Xlib specification Chapter 13 are
Hideki Hiura (SunSoft) and Shigeru Yamada (Fujitsu OSSI).
The principal producers of the sample implementation of the 
internationalization facilities are
Jeffrey Bloomfield (Fujitsu OSSI), Takashi Fujiwara (Fujitsu),
Hideki Hiura (SunSoft), Yoshio Horiuchi (IBM), 
Makoto Inada (Digital), Hiromu Inukai (Nihon SunSoft), 
Song JaeKyung (KAIST), Riki Kawaguchi (Fujitsu), 
Franky Ling (Digital), Hiroyuki Miyamoto (Digital), 
Hidetoshi Tajima (HP), Toshimitsu Terazono (Fujitsu), 
Makoto Wakamatsu (Sony), Masaki Wakao (IBM), 
Shigeru Yamada (Fujitsu OSSI) and Katsuhisa Yano (Toshiba).
The coordinators of the integration, testing, and release of this 
implementation are
Nobuyuki Tanaka (Sony) and Makoto Wakamatsu (Sony).
Others who have contributed on the architectural design or
the testing of sample implementation are
Hector Chan (Digital), Michael Kung (IBM), Joseph Kwok (Digital),
Hiroyuki Machida (Sony), Nelson Ng (SunSoft), Frank Rojas (IBM), 
Yoshiyuki Segawa (Fujitsu OSSI), Makiko Shimamura (Fujitsu), 
Shoji Sugiyama (IBM), Lining Sun (SGI), Masaki Takeuchi (Sony),
Jinsoo Yoon (KAIST) and Akiyasu Zen (HP).
.\"
.IP "Xt Intrinsics"
Douglas Rand (Open Software Foundation), parameterized selections;
Paul Asente (Adobe Systems Incorporated), extension event handling;
Ajay Vohra (SunSoft), support for multithreading;
Sam Chang (Novell), widget caching research;
Larry Cable (SunSoft), object allocation and change managed set;
Vania Joloboff (Open Software Foundation);
Courtney Loomis (Hewlett-Packard Company);
Daniel Dardailler (Open Software Foundation);
and Ellis Cohen (Open Software Foundation).
The following people at Georgia Tech contributed the
extensions for disability access:
Keith Edwards,
Susan Liebeskind,
Beth Mynatt, and
Tom Rodriguez.
.\"
.IP "Athena Widget Set"
Frank Sheeran (Omron Data General)
.IP "X Logical Font Description"
Paul Asente (Adobe Systems Incorporated);
Nathan Meyers (Hewlett-Packard Company);
Jim Graham (Sun);
Perry A. Caro (Adobe Systems Incorporated)
.IP "Font Support Enhancments"
Nathan Meyers (Hewlett-Packard Company), implementation of matrix
enhancement, glyph caching, scalable aliases, sample
authorization protocol
.IP "X Transport Library"
Stuart R. Anderson (AT&T Global Information Solutions)
.IP "X Keyboard Extension"
Erik Fortune (Silicon Graphics), design and sample implementation;
Jordan Brown (Quarterdeck Office Systems);
Will Walker (Digital Equipment Corporation), AccessX portion;
Mark Novak (Trace Center), AccessX portion
.IP "Low-Bandwidth X"
Jim Fulton (Network Computing Devices);
Dave Lemke (Network Computing Devices);
Dale Tonogai (Network Computing Devices);
Keith Packard (Network Computing Devices);
Chris Kantarjiev (Xerox PARC)
.IP "X Image Extension"
Bob Shelley (AGE Logic), protocol architect, lead implementation architect;
Larry Hare (AGE Logic), server implementation;
Dean Verheiden (AGE Logic), server implementation;
Syd Logan (AGE Logic), xieperf;
Gary Rogers (AGE Logic), JPEG code, XIElib documentation;
Ben Fahy (AGE Logic), client and server implementation
.IP "ICCCM"
Stuart Marks (SunSoft);
Gabe Beged-Dov (Hewlett-Packard Company);
Chan Benson (Hewlett-Packard Company);
Jordan Brown (Quarterdeck Office Systems);
Larry Cable (SunSoft);
Ellis Cohen (Open Software Foundation);
Brian Cripe (Hewlett-Packard Company);
Susan Dahlberg (Silicon Graphics);
Peter Daifuku (Silicon Graphics);
Andrew deBlois (Open Software Foundation);
Clive Feather (IXI);
Christian Jacobi (Xerox PARC);
Bill Janssen (Xerox PARC);
Vania Joloboff (Open Software Foundation);
Phil Karlton (Silicon Graphics);
Mark Manasse (Digital Equipment Corporation);
Todd Newman (Silicon Graphics);
Keith Taylor (Hewlett-Packard Company);
Jim VanGilder (Digital Equipment Corporation);
Mike Wexler (Kubota Pacific);
Michael Yee (Apple Computer)
.IP "ICE"
.br
Jordan Brown (Quarterdeck Office Systems);
Vania Joloboff (Open Software Foundation);
Stuart Marks (SunSoft)
.IP "XSMP"
.br
Mike Wexler (Kubota Pacific);
Jordan Brown (Quarterdeck Office Systems);
Ellis Cohen (Open Software Foundation);
Vania Joloboff (Open Software Foundation);
Stuart Marks (SunSoft)
.IP "SYNC Extension"
Tim Glauert (Olivetti Research Limited);
Dave Carver (Digital Equipment Corporation);
Jim Gettys (Digital Equipment Corporation);
Pete Snider (Digital Equipment Corporation)
.IP "RECORD"
Martha Zimet (Network Computing Devices);
Robert Chesler (Absol-puter);
Kieron Drake (UniSoft);
Marc Evans (Synergytics);
Jim Fulton (Network Computing Devices);
Ken Miller (Digital Equipment Corporation)
.IP "X Input Extension tests"
George Sachs (Hewlett-Packard Company)
.IP "PEX"
Ken Garnett (Shographics);
Cheryl Huntington (Sun Microsystems);
Karl Schultz (IBM);
Jeff Stevenson (Hewlett-Packard Company);
Paula Womack (Digital Equipment Corporation)
.IP "Multi-Buffering Extension"
Eng-Shien Wu (IBM);
John Marks (Hewlett-Packard Company);
Ian Elliott (Hewlett-Packard Company)
.IP "X server"
Milind Pansare (SunSoft), pixmap privates;
Peter Daifuku (SGI), layered window support;
David Lister (Adobe Systems Incorporated), callback manager;
Ken Whaley (Kubota Pacific), thin line pixelization;
Joel McCormack (Digital Equipment Corporation), 64-bit mfb and cfb;
Rob Lembree (Digital Equipment Corporation), 64-bit mfb and cfb;
Davor Matic (MIT), xnest ddx;
Nathan Meyers (Hewlett-Packard Company), font support;
Jordan Brown (Quarterdeck Office Systems), -config option;
Michael Brenner (Apple Computer), macII ddx;
Thomas Roell, svga ddx
.IP "Multi-Threaded X Server"
John A. Smith (while at Data General), team leader;
H. Chiba (Omron), ddx;
Akeio Harada (Omron), ddx;
Mike Haynes (Data General), dix;
Hidenobu Kanaoka (Omron), ddx;
Paul Layne (Data General), dix and ddx;
Takayuki Miyake (Omron), ddx;
Keith Packard (Network Computing Devices), design;
Richard Potts (Data General), dix;
Sid Manning (IBM), integration with core server;
Rob Chesler (Absol-puter), integration with core server
.IP "xdm modular loadable greeter"
Peter Derr (Digital Equipment Corporation)
.IP "x11perf"
Joel McCormack (Digital Equipment Corporation);
Graeme Gill (Labtam Australia);
Mark Martin (CETIA)
.IP "config"
Stuart R. Anderson (AT&T Global Information Solutions);
David Brooks (Open Software Foundation);
Kendall Collett (Motorola);
John Freeman (Cray);
John Freitas (Digital Equipment Corporation);
Patrick E. Kane (Motorola);
Mark Kilgard (Silicon Graphics);
Akira Kon (NEC);
Masahiko Narita (Fujitsu);
Paul Shearer (Sequent);
Mark Snitily (SGCS)
.IP "XFree86 port"
Stuart R. Anderson (AT&T Global Information Solutions);
Doug Anson; Gertjan Akkerman; Mike Bernson; David Dawes; Marc Evans;
Pascal Haible; Matthieu Herrb; Dirk Hohndel; David Holland; Alan Hourihane;
Jeffrey Hsu; Glenn Lai; Ted Lemon; Rich Murphey; Hans Nasten; Mark Snitily;
Randy Terbush; Jon Tombs; Kees Verstoep; Paul Vixie; Mark Weaver;
David Wexelblat; Philip Wheatley; Thomas Wolfram; Orest Zborowski
.IP "fonts"
.br
Under \fBxc/fonts/\fP, the \fBmisc/\fP directory
contains a family of fixed-width fonts from Dale Schumacher,
several Kana fonts from Sony Corporation,
two Hangul fonts from Daewoo Electronics,
two Hebrew fonts from Joseph Friedman,
two cursor fonts from
Digital Equipment Corporation, and cursor and glyph fonts
from Sun Microsystems.
The \fBSpeedo\fP directory contains outline fonts contributed by
Bitstream, Inc.
The \fB75dpi\fP and \fB100dpi\fP directories contain
bitmap fonts contributed by Adobe Systems, Inc.,
Digital Equipment Corporation, Bitstream, Inc.,
Bigelow and Holmes, and Sun Microsystems, Inc.
.if t \{
.\"
.\" print Table of Contents
.if o .bp \" blank page to make count even
.bp 1
.af PN i
.PX
.\}