Remove a couple of tags unparseable by doclifter.

1 files changed, 2 insertions, 11 deletions

diff --git a/specs/Xi/protocol.ms b/specs/Xi/protocol.ms
index 8a5da05..87c7b87 100644
--- a/specs/Xi/protocol.ms
+++ b/specs/Xi/protocol.ms
@@ -1,6 +1,3 @@
-.\" $Xorg: protocol.ms,v 1.3 2000/08/17 19:42:40 cpqbld Exp $
-.\" $XdotOrg: xc/doc/specs/Xi/protocol.ms,v 1.2 2004/04/23 18:42:18 eich Exp $
-.\" Input Extension
 .EH ''''
 .OH ''''
 .EF ''''
@@ -146,13 +143,12 @@ events they generate (\fBKeyPress\fP, \fBKeyRelease\fP, \fBButtonPress\fP,
 \fBMotionNotify\fP) are known as the \fIcore input events\fP.  All other
 input devices are referred to as \fIextension input devices\fP and the 
 input events they generate are referred to as \fIextension input events\fP.
-.NT
+.LP
 This input extension does not change the behavior or functionality of the
 core input devices, core events, or core protocol requests, with the
 exception of the core grab requests.  These requests may affect the
 synchronization of events from extension devices.  See the explanation
 in the section titled "Event Synchronization and Core Grabs".
-.NE
 .LP
 Selection of the physical devices to be initially used by the server as the 
 core devices is left implementation-dependent.  Requests are defined that
@@ -1157,7 +1153,7 @@ Changing The Core Devices
 .LP
 These requests are provided to change which physical device is used
 as the X pointer or X keyboard.
-.NT
+.LP
 Using these requests may change the characteristics of the core devices.
 The new pointer device may have a different number of buttons than the 
 old one did, or the new keyboard device may have a different number of
@@ -1167,7 +1163,6 @@ program could allocate an array based on the number of buttons on the
 pointer device, and then use the button numbers received in button events
 as indicies into that array.  Changing the core devices could cause
 such client programs to behave improperly or abnormally terminate.
-.NE
 .LP
 These requests change the X keyboard or X pointer device and generate
 an \fBChangeDeviceNotify\fP event and a \fBMappingNotify\fP event.  
@@ -2807,7 +2802,6 @@ detail: <see below>
 state: SETofKEYBUTMASK
 .br
 time: TIMESTAMP
-.TE
 .in -.5i
 .LP
 These events are generated when a key, button, or valuator logically changes state.
@@ -2887,7 +2881,6 @@ num_valuators: CARD8
 first_valuator: CARD8
 .br
 valuators: LISTofINT32
-.TE
 .in -.5i
 .LP
 DeviceValuator events are generated to contain valuator information for which
@@ -3007,7 +3000,6 @@ keys: LISTofCARD8
 .br
 valuators: LISTofCARD32
 .br
-.TE
 .in -.5i
 .LP
 This event reports the state of the device just as in the 
@@ -3129,7 +3121,6 @@ first-axis: CARD8
 axis-data: LISTofINT32
 .br
 .in -.5i
-.TE
 .LP
 These events are generated by some devices (such as graphics tablets or 
 touchscreens) to indicate that a stylus has moved into or out of contact