From: mor@xenon.lcs.mit.edu (Ralph Mor)
Newsgroups: comp.windows.x.pex
Subject: PEXlib Sample Implementation available from MIT
Date: 19 Nov 92 16:35:16 GMT
Organization: MIT X Consortium

The MIT X Consortium has recently made a public release of
the PEXlib Sample Implementation.  Below is information on
how to get the software.  I've also included information on
how to get the PEXlib document.

Feel free to ask me any questions.

  Ralph Mor
  MIT X Consortium
  mor@expo.lcs.mit.edu

----------------------------------------------------------------------------

Date: Mon, 16 Nov 92 15:25:21 -0500
To: xannounce@expo.lcs.mit.edu
Subject: X11R5 public fixes #18 and #19 now available on export
From: Bob Scheifler <rws@expo.lcs.mit.edu>

Patches for a variety of problems in R5 are now available via anonymous ftp
on export.lcs.mit.edu, and the xstuff mail archive server on expo.lcs.mit.edu.

Fixes are available via anonymous ftp to export.lcs.mit.edu (18.24.0.12),
in the directory /pub/R5/fixes/.  The files for the new fixes are "fix-18",
"fix-19", and "PEXlib.tar.Z".  PEXlib.tar.Z is part of fix #19.  Instructions
for applying the fixes are included in the files.  Fixes usually propagate
to other distribution sites as well, so it may pay to check at a nearer
site first.

WARNING:
Fix #18 was previously released as an optional patch, in support of the
X Test Suite, and was labeled "Release 5 XTEST Public Patch" (the file on
expo was "/pub/XTEST/R5fix-xtest-1").  If you have already applied that patch,
do not try to apply fix-18!  Proceed instead to apply fix-19.

For those without ftp access, individual fixes can be obtained by mail by
sending a message to xstuff@expo.lcs.mit.edu (18.24.0.11).  In the usual
case, the message should have a subject line and no body, or a single-line
body and no subject.  For example, make the line:
	send fixes 18
to get fix #18, and
	send fixes 19
to get fix #19.  To obtain PEXlib.tar.Z, you need to request the individual
parts "PEXlib.uu.1", "PEXlib.uu.2", "PEXlib.uu.3", and "PEXlib.uu.4", then
concatenate them together to create a file "PEXlib.uu" and then do
	uudecode PEXlib.uu
to produce "PEXlib.tar.Z".

To get a summary of all fixes, make the line:
	index fixes
If you need help, make the line:
	help
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 path, you can include a line like
	path foo%bar.bitnet@mitvma.mit.edu
or
	path zot!gzork!me@uunet.uu.net
in the body of your message, and the daemon will use it.


Brief notes on what patch 18 provides:

xtest: add implementation of XTEST extension

Brief notes on what patch 19 provides:

PEXlib: add implementation of PEXlib, a new X Consortium standard
Xlib: improve extension error reporting


-----------------------------------------------------------------------------

Date: Fri, 6 Nov 92 11:28:00 -0500
To: xannounce@expo.lcs.mit.edu
Subject: Release of X Consortium standard PEXlib specification
From: Bob Scheifler <rws@expo.lcs.mit.edu>


Release of Final PEXlib Document
Jeff Stevenson
November 5, 1992


    The Final PEXlib, Version 5.1, document is available.

    The files are available via anonymous ftp on export.lcs.mit.edu in the

	/pub/DOCS/PEXlib

    directory.  There are two files:

	PEXlib.doc.tar.Z	- the troff source files
	PEXlib.ps.tar.Z		- the PostScript output files

    I recommend that you get the PostScript files for hardcopy output.
    There is a known problem with creating the index in some environments.
    The PostScript tar includes two files: PEXlib.PS which is the main
    document and table of contents, and PEXlib.ndx.PS which is the index.

    The source tar contains all macros and sources files for building the
    document, table of contents and index.  The source tar also includes the
    standard header files.  Having the source makes searching for things in
    the document easier too.

    One note about building the document: there is a number register used to
    control the font used for code excerpts (a uniform courier font).  The
    default is to use the font name "C" (e.g. .ft C) which is believed to be
    correct for most ditroff and psroff implementations.  However, there is
    at least one known troff implementation that has the courier loaded in
    font position 8 and is not named "C".  So, to override the default, use
    the command line option "-rC8" to effect the correct font change (e.g.
    .ft 8).  If you have problems with getting the code excerpts to look
    correct, try overriding the default as shown above.  You can do this by
    modifying the troff command in the Imakefile.


    Finally, the following is included in this README as a reference to work
    still in progress.


    Locales and Internationalized Text
    ----------------------------------

    PEXlib provides functions for supporting international text and
    multibyte fonts, but this support is basic and difficult to use.  An
    effort to introduce more appropriate support for localization is in
    progress, but was too late for inclusion in this first release of PEXlib
    5.1.  A second release of PEXlib 5.1 is being considered in order to
    incorporate this support for internationalization.

    The proposal being worked on introduces locale management and
    internationalized text functions into PEXlib that are very similar to
    Xlib.

    A donation of sample code for these functions is expected, and is
    expected to be made public if donated.


    Additional PEXlib Utilities
    ---------------------------

    In addition to the internationalization work, there is also work in
    progress on additional utilities for PEXlib.  Most of these utilities
    are expected to be made available as contributed code from the X
    Consortium.  Once available, contributed code can be accessed via ftp to
    export.lcs.mit.edu.  Look in the /contrib/PEXlib/ directory.

    The work in progress includes utilities for double-buffering, visual
    selection and colormap initialization.  There will be a README file in
    the ftp directory, /contrib/PEXlib/, with more information.
Newsgroups: comp.windows.x.pex