View | Details | Raw Unified
Collapse All | Expand All

(-) sgml/Versions.sgml (-13 / +67 lines)
 Lines 109-114   etc. Link Here  
</ItemizedList>
</ItemizedList>

        
</Para>
</Para>

            

              
              
</ListItem>

            

        
</VarListEntry>
</VarListEntry>

        
<VarListEntry>
<VarListEntry>

        
<Term>Types</Term>
<Term>Types</Term>

  

    

    

       Lines 118-123
      Types describe how the produced key is c 
    
  Link Here 
    

  

        
Shift, Control, Alt, ...). There are several predefined types which
Shift, Control, Alt, ...). There are several predefined types which

        
cover most of used combinations.
cover most of used combinations.

        
</Para>
</Para>

            

              
              
</ListItem>

            

        
</VarListEntry>
</VarListEntry>

        
<VarListEntry>
<VarListEntry>

        
<Term>Compat</Term>
<Term>Compat</Term>

  

    

    

       Lines 128-133
      compat component you can assign various  
    
  Link Here 
    

  

        
in xkb specification) to key events. This is also the place where
in xkb specification) to key events. This is also the place where

        
LED-indicators behaviour is defined.
LED-indicators behaviour is defined.

        
</Para>
</Para>

            

              
              
</ListItem>

            

        
</VarListEntry>
</VarListEntry>

        
<VarListEntry>
<VarListEntry>

        
<Term>Symbols</Term>
<Term>Symbols</Term>

  

    

    

       Lines 139-144
      symbolic name, see above). There may be  
    
  Link Here 
    

  

        
for each key and then it depends on a key type and on modifiers state
for each key and then it depends on a key type and on modifiers state

        
(respective compat component) which value will be the resulting one.
(respective compat component) which value will be the resulting one.

        
</Para>
</Para>

            

              
              
</ListItem>

            

        
</VarListEntry>
</VarListEntry>

        
<VarListEntry>
<VarListEntry>

        
<Term>Geometry</Term>
<Term>Geometry</Term>

  

    

    

       Lines 147-152
      for each key and then it depends on a ke 
    
  Link Here 
    

  

        
Geometry files aren't used by xkb itself but they may be used by some
Geometry files aren't used by xkb itself but they may be used by some

        
external programs to depict a keyboard image.
external programs to depict a keyboard image.

        
</Para>
</Para>

            

              
              
</ListItem>

            

        
</VarListEntry>
</VarListEntry>

        
</VariableList>
</VariableList>

        
All these components have the files located in xkb configuration tree
All these components have the files located in xkb configuration tree

  

    

    

       Lines 456-461
      The most used schemes are: 
    
  Link Here 
    

  

        
The key does not depend on any modifiers. The symbol from first level
The key does not depend on any modifiers. The symbol from first level

        
is always chosen.
is always chosen.

        
</Para>
</Para>

            

              
              
</ListItem>

            

        
</VarListEntry>
</VarListEntry>

        
<VarListEntry>
<VarListEntry>

        
<Term>TWO&lowbar;LEVEL</Term>
<Term>TWO&lowbar;LEVEL</Term>

  

    

    

       Lines 468-473
      system-specific capitalization rules. If 
    
  Link Here 
    

  

        
symbol from the second level is taken and capitalization rules are applied
symbol from the second level is taken and capitalization rules are applied

        
(and usually have no effect).
(and usually have no effect).

        
</Para>
</Para>

            

              
              
</ListItem>

            

        
</VarListEntry>
</VarListEntry>

        
<VarListEntry>
<VarListEntry>

        
<Term>ALPHABETIC</Term>
<Term>ALPHABETIC</Term>

  

    

    

       Lines 481-486
      modifier apply the symbol from the first 
    
  Link Here 
    

  

        
capitalization rules applied. This is often called shift-cancels-caps
capitalization rules applied. This is often called shift-cancels-caps

        
behaviour.
behaviour.

        
</Para>
</Para>

            

              
              
</ListItem>

            

        
</VarListEntry>
</VarListEntry>

        
<VarListEntry>
<VarListEntry>

        
<Term>THREE&lowbar;LEVEL</Term>
<Term>THREE&lowbar;LEVEL</Term>

  

    

    

       Lines 494-499
      the resulting level. Only Shift and Leve 
    
  Link Here 
    

  

        
consideration. If the Lock modifier is active capitalization rules
consideration. If the Lock modifier is active capitalization rules

        
are applied on the resulting symbol.
are applied on the resulting symbol.

        
</Para>
</Para>

            

              
              
</ListItem>

            

        
</VarListEntry>
</VarListEntry>

        
<VarListEntry>
<VarListEntry>

        
<Term>FOUR&lowbar;LEVEL</Term>
<Term>FOUR&lowbar;LEVEL</Term>

  

    

    

       Lines 502-507
      are applied on the resulting symbol. 
    
  Link Here 
    

  

        
Is the same as THREE&lowbar;LEVEL but unlike LEVEL&lowbar;THREE if both Shift+LevelThree
Is the same as THREE&lowbar;LEVEL but unlike LEVEL&lowbar;THREE if both Shift+LevelThree

        
modifiers apply the symbol is taken from the fourth level.
modifiers apply the symbol is taken from the fourth level.

        
</Para>
</Para>

            

              
              
</ListItem>

            

        
</VarListEntry>
</VarListEntry>

        
<VarListEntry>
<VarListEntry>

        
<Term>FOUR&lowbar;LEVEL&lowbar;ALPHABETIC</Term>
<Term>FOUR&lowbar;LEVEL&lowbar;ALPHABETIC</Term>

  

    

    

       Lines 513-518
      third level is taken and the capitalizat 
    
  Link Here 
    

  

        
If Lock+Shift+LevelThree apply the symbol from the third level is taken
If Lock+Shift+LevelThree apply the symbol from the third level is taken

        
and no capitalization rules are applied.
and no capitalization rules are applied.

        
</Para>
</Para>

            

              
              
</ListItem>

            

        
</VarListEntry>
</VarListEntry>

        
<VarListEntry>
<VarListEntry>

        
<Term>KEYPAD</Term>
<Term>KEYPAD</Term>

  

    

    

       Lines 525-530
      Shift or NumLock modifiers apply the sym 
    
  Link Here 
    

  

        
If both Shift+NumLock modifiers apply the symbol from the first level
If both Shift+NumLock modifiers apply the symbol from the first level

        
is taken. Again, shift-cancels-caps variant.
is taken. Again, shift-cancels-caps variant.

        
</Para>
</Para>

            

              
              
</ListItem>

            

        
</VarListEntry>
</VarListEntry>

        
<VarListEntry>
<VarListEntry>

        
<Term>FOUR&lowbar;LEVEL&lowbar;KEYPAD</Term>
<Term>FOUR&lowbar;LEVEL&lowbar;KEYPAD</Term>

  

    

    

       Lines 536-541
      If Shift+LevelThree or NumLock+LevelThre 
    
  Link Here 
    

  

        
level is taken. If all Shift+NumLock+LevelThree modifiers apply the symbol
level is taken. If all Shift+NumLock+LevelThree modifiers apply the symbol

        
from the third level is taken. This also, shift-cancels-caps variant.
from the third level is taken. This also, shift-cancels-caps variant.

        
</Para>
</Para>

            

              
              
</ListItem>

            

        
</VarListEntry>
</VarListEntry>

        
</VariableList>
</VariableList>

        
</Para>
</Para>

  

    

    

       Lines 552-557
      It is similar to TWO&lowbar;LEVEL scheme 
    
  Link Here 
    

  

        
modifier rather than Shift. That means, the symbol from the second level
modifier rather than Shift. That means, the symbol from the second level

        
is chosen by Control rather than by Shift.
is chosen by Control rather than by Shift.

        
</Para>
</Para>

            

              
              
</ListItem>

            

        
</VarListEntry>
</VarListEntry>

        
<VarListEntry>
<VarListEntry>

        
<Term>PC&lowbar;SYSRQ</Term>
<Term>PC&lowbar;SYSRQ</Term>

  

    

    

       Lines 561-566
      It is similar to TWO&lowbar;LEVEL scheme 
    
  Link Here 
    

  

        
than Shift. That means, the symbol from the second level
than Shift. That means, the symbol from the second level

        
is chosen by Alt rather than by Shift.
is chosen by Alt rather than by Shift.

        
</Para>
</Para>

            

              
              
</ListItem>

            

        
</VarListEntry>
</VarListEntry>

        
<VarListEntry>
<VarListEntry>

        
<Term>CTRL+ALT</Term>
<Term>CTRL+ALT</Term>

  

    

    

       Lines 571-576
      values. If only one modifier (Alt or Con 
    
  Link Here 
    

  

        
from the first level is chosen. Only if both Alt+Control modifiers apply
from the first level is chosen. Only if both Alt+Control modifiers apply

        
the symbol from the second level is chosen.
the symbol from the second level is chosen.

        
</Para>
</Para>

            

              
              
</ListItem>

            

        
</VarListEntry>
</VarListEntry>

        
<VarListEntry>
<VarListEntry>

        
<Term>SHIFT+ALT</Term>
<Term>SHIFT+ALT</Term>

  

    

    

       Lines 581-586
      If only one modifier (Alt or Shift) appl 
    
  Link Here 
    

  

        
from the first level is chosen. Only if both Alt+Shift modifiers apply
from the first level is chosen. Only if both Alt+Shift modifiers apply

        
the symbol from the second level is chosen.
the symbol from the second level is chosen.

        
</Para>
</Para>

            

              
              
</ListItem>

            

        
</VarListEntry>
</VarListEntry>

        
</VariableList>
</VariableList>

        
</Para>
</Para>

  

    

    

       Lines 181-186
      however a number of <Literal remap="tt"> 
    
  Link Here 
    

  

        
Both GCC, and the Sun Studio compilers are supported by X11R&relvers;.
Both GCC, and the Sun Studio compilers are supported by X11R&relvers;.

        
The minimum recommended GCC release is 2.7.2.
The minimum recommended GCC release is 2.7.2.

        
Some earlier GCC's are known to not work and should be avoided.
Some earlier GCC's are known to not work and should be avoided.

            

              
              
</Para>

            

        
<Para>
<Para>

        
You should also make certain your version of GCC predefines `sun'.
You should also make certain your version of GCC predefines `sun'.

        
If needed edit <Literal remap="tt">/usr/local/lib/gcc-lib/*/*/specs</Literal>, and modify the
If needed edit <Literal remap="tt">/usr/local/lib/gcc-lib/*/*/specs</Literal>, and modify the

  

    

    

       Lines 199-211
      Also on SPARCs, you may be able to build 
    
  Link Here 
    

  

        
older cg* graphics devices by adding "&num;define XsunServer YES" or "&num;define 
older cg* graphics devices by adding "&num;define XsunServer YES" or "&num;define 

        
Xsun24Server YES" or "&num;define XsunMonoServer YES" to &nbsp;xc/config/cf/host.def.
Xsun24Server YES" or "&num;define XsunMonoServer YES" to &nbsp;xc/config/cf/host.def.

        
These servers are no longer maintained nor supported and may not build in
These servers are no longer maintained nor supported and may not build in

            

              
this release.</ListItem>

              
this release.

            

            

              

              
</Para>

            

            

              

              
</ListItem>

            

        
<ListItem>
<ListItem>

        
<Para>
<Para>

        
A Threaded Xlib compiled with GCC has subtle problems.
A Threaded Xlib compiled with GCC has subtle problems.

        
It'll work 98&percnt; of the time, however clients will occasionally exhibit
It'll work 98&percnt; of the time, however clients will occasionally exhibit

        
strange hangs.
strange hangs.

        
Most notably image viewers such as xv-3.10 exhibit this problem.
Most notably image viewers such as xv-3.10 exhibit this problem.

            

              
              
</Para>

            

        
<Para>
<Para>

        
It is recommended that you set ThreadedX in <Literal remap="tt">&tilde;xc/config/cf/host.def</Literal> to
It is recommended that you set ThreadedX in <Literal remap="tt">&tilde;xc/config/cf/host.def</Literal> to

        
NO, if you are using GCC.
NO, if you are using GCC.

  

    

    

       Lines 218-223
      Whether this behaviour still exists with 
    
  Link Here 
    

  

        
To build X11R&relvers; with GCC you need gcc and (optionally) c++filt from GNU
To build X11R&relvers; with GCC you need gcc and (optionally) c++filt from GNU

        
binutils.
binutils.

        
Don't install gas or ld from GNU binutils, use the one provided by Sun.
Don't install gas or ld from GNU binutils, use the one provided by Sun.

            

              
              
</Para>

            

        
<Para>
<Para>

        
You might need to setup a /opt/SUNWspro/bin directory containing symbolic links
You might need to setup a /opt/SUNWspro/bin directory containing symbolic links

        
named <Literal remap="tt">cc</Literal>, <Literal remap="tt">CC</Literal>, and <Literal remap="tt">c++filt</Literal> pointing respectively to the actual
named <Literal remap="tt">cc</Literal>, <Literal remap="tt">CC</Literal>, and <Literal remap="tt">c++filt</Literal> pointing respectively to the actual

  

    

    

       Lines 228-234
      named <Literal remap="tt">cc</Literal>,  
    
  Link Here 
    

  

        
<Para>
<Para>

        
If you are using Sun compilers to compile the X11R&relvers; distribution, you need to
If you are using Sun compilers to compile the X11R&relvers; distribution, you need to

        
modify your PATH appropriately so the Sun compiler tools are available.
modify your PATH appropriately so the Sun compiler tools are available.

            

              
Normally, they should be in <Literal remap="tt">/opt/SUNWspro/bin</Literal></ListItem>

              
Normally, they should be in <Literal remap="tt">/opt/SUNWspro/bin</Literal>

            

            

              

              
</Para>

            

            

              

              
</ListItem>

            

        
<ListItem>
<ListItem>

        
<Para>
<Para>

        
You <Emphasis remap="bf">MUST</Emphasis> put <Literal remap="tt">/usr/ccs/bin</Literal> at the front of your PATH.
You <Emphasis remap="bf">MUST</Emphasis> put <Literal remap="tt">/usr/ccs/bin</Literal> at the front of your PATH.

  

    

    

       Lines 236-242
      There are known problems with some GNU r 
    
  Link Here 
    

  

        
there.
there.

        
So the <Literal remap="tt">/usr/ccs/bin</Literal> versions of these programs must be found before
So the <Literal remap="tt">/usr/ccs/bin</Literal> versions of these programs must be found before

        
any possible GNU versions.
any possible GNU versions.

            

              
(Most notably GNU '<Literal remap="tt">ar</Literal>' does not work during the build).</ListItem>

              
(Most notably GNU '<Literal remap="tt">ar</Literal>' does not work during the build).

            

            

              

              
</Para>

            

            

              

              
</ListItem>

            

        

        
</OrderedList>
</OrderedList>

        

  

    

    

       Lines 254-259
      any possible GNU versions. 
    
  Link Here 
    

  

        
<Para>
<Para>

        
Depending on the release or architecture of Solaris you are running, you might
Depending on the release or architecture of Solaris you are running, you might

        
need to install an OS driver for an aperture device.
need to install an OS driver for an aperture device.

            

              
              
</Para>

            

        
<Para>
<Para>

        
Under Solaris x86 2.5 and later, there's a system driver (<Literal remap="tt">/dev/xsvc</Literal>)
Under Solaris x86 2.5 and later, there's a system driver (<Literal remap="tt">/dev/xsvc</Literal>)

        
that provides this functionality.
that provides this functionality.

  

    

    

       Lines 278-283
      If you have not made the Virtual Termina 
    
  Link Here 
    

  

        
terminal device to run the Xserver on.
terminal device to run the Xserver on.

        
The correct device is vt00 so your <Literal remap="tt">xinit</Literal> command would look like
The correct device is vt00 so your <Literal remap="tt">xinit</Literal> command would look like

        
so:
so:

            

              
              
</Para>

            

        
<Para>
<Para>

        

        
<Screen>
<Screen>

  

    

    

       Lines 294-299
      For old releases of Solaris you will pro 
    
  Link Here 
    

  

        
<Literal remap="tt">/usr/X11R6/lib:/usr/openwin/lib:/usr/dt/lib</Literal>.
<Literal remap="tt">/usr/X11R6/lib:/usr/openwin/lib:/usr/dt/lib</Literal>.

        
Including <Literal remap="tt">/usr/X11R6/lib</Literal> in your LD&lowbar;LIBRARY&lowbar;PATH is probably not
Including <Literal remap="tt">/usr/X11R6/lib</Literal> in your LD&lowbar;LIBRARY&lowbar;PATH is probably not

        
necessary, however it doesn't hurt. :)
necessary, however it doesn't hurt. :)

            

              
              
</Para>

            

        
<Para>
<Para>

        
Including <Literal remap="tt">/usr/openwin/lib</Literal> in the LD&lowbar;LIBRARY&lowbar;PATH is recommended
Including <Literal remap="tt">/usr/openwin/lib</Literal> in the LD&lowbar;LIBRARY&lowbar;PATH is recommended

        
on older releases because some Sun supplied binaries were not compiled with LD&lowbar;RUN&lowbar;PATH set
on older releases because some Sun supplied binaries were not compiled with LD&lowbar;RUN&lowbar;PATH set

  

    

    

       Lines 310-323
      LD&lowbar;LIBRARY&lowbar;PATH too. 
    
  Link Here 
    

  

        
Xqueue is <Emphasis remap="bf">NOT</Emphasis> supported under Solaris.
Xqueue is <Emphasis remap="bf">NOT</Emphasis> supported under Solaris.

        
The includes necessary for Xqueue are available, however the driver does not
The includes necessary for Xqueue are available, however the driver does not

        
seem to be in the kernel.
seem to be in the kernel.

            

              
(Go figure)</ListItem>

              
(Go figure)

            

            

              

              
</Para>

            

            

              

              
</ListItem>

            

        
<ListItem>
<ListItem>

        
<Para>
<Para>

        
If you want to use xdm with Solaris, extract the files from the shar file in
If you want to use xdm with Solaris, extract the files from the shar file in

        
<Literal remap="tt">/usr/X11R6/lib/X11/etc/XdmConf.svr4</Literal> into a temporary directory.
<Literal remap="tt">/usr/X11R6/lib/X11/etc/XdmConf.svr4</Literal> into a temporary directory.

        
The <Literal remap="tt">README</Literal> file tells where the individual files need to be installed.
The <Literal remap="tt">README</Literal> file tells where the individual files need to be installed.

        
Be sure to read through each file and make any site-specific changes that you
Be sure to read through each file and make any site-specific changes that you

            

              
need.</ListItem>

              
need.

            

            

              

              
</Para>

            

            

              

              
</ListItem>

            

        

        
</OrderedList>
</OrderedList>

        

  

    

    

       Lines 337-342
      The Solaris 2.1 for x86 OpenWindows file 
    
  Link Here 
    

  

        
Xserver, it probably will also not work against a X11R6 Xserver.
Xserver, it probably will also not work against a X11R6 Xserver.

        
Attempting to 'Drag and Drop' a file causes the filemgr to abort with an
Attempting to 'Drag and Drop' a file causes the filemgr to abort with an

        
'X error'
'X error'

            

              
              
</Para>

            

        
<Para>
<Para>

        
Solaris x86 2.4 does not have this problem.
Solaris x86 2.4 does not have this problem.

        
</Para>
</Para>

  

    

    

       Lines 349-355
      There is no known work around. 
    
  Link Here 
    

  

        
<Para>
<Para>

        
The SPARC port is still quite new, so instability is to be expected (and
The SPARC port is still quite new, so instability is to be expected (and

        
reported!).
reported!).

            

              
It might even have broken some aspects of the x86 port.</ListItem>

              
It might even have broken some aspects of the x86 port.

            

            

              

              
</Para>

            

            

              

              
</ListItem>

            

        

        
</OrderedList>
</OrderedList>

        

  

    

    

       Lines 189-195
      The next section describes what is new i 
    
  Link Here 
    

  

        
            <row>
            <row>

        
                <entry>Driver Name</entry>
                <entry>Driver Name</entry>

        
                <entry>Description</entry>
                <entry>Description</entry>

            

              
                <entry>Further Information

              
				<entry>Further Information</entry>

            

        
            </row>
            </row>

        
            <row>
            <row>

        
                <entry><Literal remap="tt">apm</Literal></entry>
                <entry><Literal remap="tt">apm</Literal></entry>

  

    

    

       Lines 403-409
      The next section describes what is new i 
    
  Link Here 
    

  

        
            <row>
            <row>

        
                <entry><Literal remap="tt">vga</Literal></entry>
                <entry><Literal remap="tt">vga</Literal></entry>

        
                <entry>Generic VGA</entry>
                <entry>Generic VGA</entry>

            

              
                <entry><ulink URL="vga.4.html">vga(4)</ulink>

              
				<entry><ulink URL="vga.4.html">vga(4)</ulink></entry>

            

        
            </row>
            </row>

        
            <row>
            <row>

        
                <entry><Literal remap="tt">via</Literal></entry>
                <entry><Literal remap="tt">via</Literal></entry>

  

    

    

       Lines 488-494
      The next section describes what is new i 
    
  Link Here 
    

  

        
            <row>
            <row>

        
                <entry><Literal remap="tt">citron</Literal></entry>
                <entry><Literal remap="tt">citron</Literal></entry>

        
                <entry>Citron</entry>
                <entry>Citron</entry>

            

              
                <entry><ulink URL="citron.4.html">citron(4)</ulink>

              
				<entry><ulink URL="citron.4.html">citron(4)</ulink></entry>

            

        
            </row>
            </row>

        
            <row>
            <row>

        
                <entry><Literal remap="tt">digitaledge</Literal></entry>
                <entry><Literal remap="tt">digitaledge</Literal></entry>

  

    

    

       Lines 498-504
      The next section describes what is new i 
    
  Link Here 
    

  

        
            <row>
            <row>

        
                <entry><Literal remap="tt">dmc</Literal></entry>
                <entry><Literal remap="tt">dmc</Literal></entry>

        
                <entry>DMC</entry>
                <entry>DMC</entry>

            

              
                <entry><ulink URL="dmc.4.html">dmc(4)</ulink>

              
				<entry><ulink URL="dmc.4.html">dmc(4)</ulink></entry>

            

        
            </row>
            </row>

        
            <row>
            <row>

        
                <entry><Literal remap="tt">dynapro</Literal></entry>
                <entry><Literal remap="tt">dynapro</Literal></entry>

  

    

    

       Lines 523-529
      The next section describes what is new i 
    
  Link Here 
    

  

        
            <row>
            <row>

        
                <entry><Literal remap="tt">fpit</Literal></entry>
                <entry><Literal remap="tt">fpit</Literal></entry>

        
                <entry>Fujitsu Stylistic Tablet PCs</entry>
                <entry>Fujitsu Stylistic Tablet PCs</entry>

            

              
                <entry><ulink URL="fpit.4.html">fpit(4)</ulink>

              
				<entry><ulink URL="fpit.4.html">fpit(4)</ulink></entry>

            

        
            </row>
            </row>

        
            <row>
            <row>

        
                <entry><Literal remap="tt">hyperpen</Literal></entry>
                <entry><Literal remap="tt">hyperpen</Literal></entry>

  

    

    

       Lines 1372-1377
      The next section describes what is new i 
    
  Link Here 
    

  

        
            <ListItem>
            <ListItem>

        
            <Para>
            <Para>

        
            The LBX extension is has been removed in this release.
            The LBX extension is has been removed in this release.

            

              
              
            </Para>

            

            

              
              
			</ListItem>

            

        
        </VarListEntry> 
        </VarListEntry> 

        
        <VarListEntry>
        <VarListEntry>

        
            <Term>CID Fonts</Term>
            <Term>CID Fonts</Term>

  

    

    

       Lines 1380-1385
      The next section describes what is new i 
    
  Link Here 
    

  

        
            Support for CID fonts has been removed as of this release.
            Support for CID fonts has been removed as of this release.

        
            mkcfm has also been deprecated as a result.
            mkcfm has also been deprecated as a result.

        
            </Para>
            </Para>

            

              
              
			</ListItem>

            

        
        </VarListEntry>
        </VarListEntry>

        
        <VarListEntry>
        <VarListEntry>

        
            <Term>xkbdata</Term>
            <Term>xkbdata</Term>

  

    

    

       Lines 1390-1395
      The next section describes what is new i 
    
  Link Here 
    

  

        
            data provided by the xkeyboard-config project, which located in
            data provided by the xkeyboard-config project, which located in

        
            the xkbdesc CVS module.
            the xkbdesc CVS module.

        
            </Para>
            </Para>

            

              
              
			</ListItem>

            

        
        </VarListEntry>
        </VarListEntry>

        
      </VariableList>
      </VariableList>

        
    </Para>
    </Para>

  

    

    

       Lines 1478-1483
      The next section describes what is new i 
    
  Link Here 
    

  

        
    Thomas Winischhofer, 
    Thomas Winischhofer, 

        
    David Woodhouse, 
    David Woodhouse, 

        
    </Para>
    </Para>

            

              
              
	</ListItem>

            

        
    </VarListEntry>
    </VarListEntry>

        
    </VariableList>
    </VariableList>

        
    </Para>
    </Para>

  

    

    

       Lines 1893-1900
      The next section describes what is new i 
    
  Link Here 
    

  

        
    
    

        
    <Para>
    <Para>

        
    This product includes software developed by the X-Oz Technologies and its
    This product includes software developed by the X-Oz Technologies and its

            

              
    contributors.

              
	contributors.

            

            

              
    </Para>

              
	</Para>

            

            

              

              
	</ListItem>

            

        
    </VarListEntry>
    </VarListEntry>

        
    </VariableList>
    </VariableList>

        
    </Para>
    </Para>

  

    

    

       Lines 127-132
      development leading up to version 6.8: 
    
  Link Here 
    

  

        
<Para>
<Para>

        
The first snapshot of the pre-6.8 development branch.
The first snapshot of the pre-6.8 development branch.

        
</Para>
</Para>

            

              
              
</ListItem>

            

        
</VarListEntry>
</VarListEntry>

        
<VarListEntry>
<VarListEntry>

        
<Term><Literal remap="tt">6.7.99.23</Literal></Term>
<Term><Literal remap="tt">6.7.99.23</Literal></Term>

  

    

    

       Lines 134-139
      The first snapshot of the pre-6.8 develo 
    
  Link Here 
    

  

        
<Para>
<Para>

        
The twenty-third snapshot of the pre-6.8 development branch.
The twenty-third snapshot of the pre-6.8 development branch.

        
</Para>
</Para>

            

              
              
</ListItem>

            

        
</VarListEntry>
</VarListEntry>

        
<VarListEntry>
<VarListEntry>

        
<Term><Literal remap="tt">6.7.99.900</Literal></Term>
<Term><Literal remap="tt">6.7.99.900</Literal></Term>

  

    

    

       Lines 141-146
      The twenty-third snapshot of the pre-6.8 
    
  Link Here 
    

  

        
<Para>
<Para>

        
The start of the 6.8 feature freeze.
The start of the 6.8 feature freeze.

        
</Para>
</Para>

            

              
              
</ListItem>

            

        
</VarListEntry>
</VarListEntry>

        
<VarListEntry>
<VarListEntry>

        
<Term><Literal remap="tt">6.7.99.903</Literal></Term>
<Term><Literal remap="tt">6.7.99.903</Literal></Term>

  

    

    

       Lines 148-153
      The start of the 6.8 feature freeze. 
    
  Link Here 
    

  

        
<Para>
<Para>

        
The third 6.8 release candidate.
The third 6.8 release candidate.

        
</Para>
</Para>

            

              
              
</ListItem>

            

        
</VarListEntry>
</VarListEntry>

        
<VarListEntry>
<VarListEntry>

        
<Term><Literal remap="tt">6.8.0</Literal></Term>
<Term><Literal remap="tt">6.8.0</Literal></Term>

  

    

    

       Lines 155-160
      The third 6.8 release candidate. 
    
  Link Here 
    

  

        
<Para>
<Para>

        
The 6.8 release.
The 6.8 release.

        
</Para>
</Para>

            

              
              
</ListItem>

            

        
</VarListEntry>
</VarListEntry>

        
<VarListEntry>
<VarListEntry>

        
<Term><Literal remap="tt">6.8.99.1</Literal></Term>
<Term><Literal remap="tt">6.8.99.1</Literal></Term>

  

    

    

       Lines 163-168
      The 6.8 release. 
    
  Link Here 
    

  

        
The first pre-6.9 development snapshot, which  is the first main
The first pre-6.9 development snapshot, which  is the first main

        
branch snapshot after creating the 6.8 stable branch.
branch snapshot after creating the 6.8 stable branch.

        
</Para>
</Para>

            

              
              
</ListItem>

            

        
</VarListEntry>
</VarListEntry>

        
</VariableList>
</VariableList>

        
</Para>
</Para>

  

    

    

       Lines 196-201
      stable branch: 
    
  Link Here 
    

  

        
<Para>
<Para>

        
The 6.8 release.
The 6.8 release.

        
</Para>
</Para>

            

              
              
</ListItem>

            

        
</VarListEntry>
</VarListEntry>

        
<VarListEntry>
<VarListEntry>

        
<Term><Literal remap="tt">6.8.0.901</Literal></Term>
<Term><Literal remap="tt">6.8.0.901</Literal></Term>

  

    

    

       Lines 203-208
      The 6.8 release. 
    
  Link Here 
    

  

        
<Para>
<Para>

        
The first pre 6.8.1 snapshot.
The first pre 6.8.1 snapshot.

        
</Para>
</Para>

            

              
              
</ListItem>

            

        
</VarListEntry>
</VarListEntry>

        
<VarListEntry>
<VarListEntry>

        
<Term><Literal remap="tt">6.8.0.903</Literal></Term>
<Term><Literal remap="tt">6.8.0.903</Literal></Term>

  

    

    

       Lines 211-216
      The first pre 6.8.1 snapshot. 
    
  Link Here 
    

  

        
The third pre 6.8.1 snapshot, also known as the third 6.8.1 release
The third pre 6.8.1 snapshot, also known as the third 6.8.1 release

        
candidate.
candidate.

        
</Para>
</Para>

            

              
              
</ListItem>

            

        
</VarListEntry>
</VarListEntry>

        
<VarListEntry>
<VarListEntry>

        
<Term><Literal remap="tt">6.8.1</Literal></Term>
<Term><Literal remap="tt">6.8.1</Literal></Term>

  

    

    

       Lines 218-223
      candidate. 
    
  Link Here 
    

  

        
<Para>
<Para>

        
The 6.8.1 release.
The 6.8.1 release.

        
</Para>
</Para>

            

              
              
</ListItem>

            

        
</VarListEntry>
</VarListEntry>

        
<VarListEntry>
<VarListEntry>

        
<Term><Literal remap="tt">6.8.1.901</Literal></Term>
<Term><Literal remap="tt">6.8.1.901</Literal></Term>

  

    

    

       Lines 225-230
      The 6.8.1 release. 
    
  Link Here 
    

  

        
<Para>
<Para>

        
The first pre 6.8.2 snapshot.
The first pre 6.8.2 snapshot.

        
</Para>
</Para>

            

              
              
</ListItem>

            

        
</VarListEntry>
</VarListEntry>

        
<VarListEntry>
<VarListEntry>

        
<Term><Literal remap="tt">6.8.2</Literal></Term>
<Term><Literal remap="tt">6.8.2</Literal></Term>

  

    

    

       Lines 232-237
      The first pre 6.8.2 snapshot. 
    
  Link Here 
    

  

        
<Para>
<Para>

        
The 6.8.2 release.
The 6.8.2 release.

        
</Para>
</Para>

            

              
              
</ListItem>

            

        
</VarListEntry>
</VarListEntry>

        
</VariableList>
</VariableList>

        
</Para>
</Para>