[Gzz-commits] manuscripts/xupdf article.rst

[Benja Fallenstein]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Benja Fallenstein <address@hidden>      03/02/15 18:06:40

Modified files:
        xupdf          : article.rst 

Log message:
        twid

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/xupdf/article.rst.diff?tr1=1.179&tr2=1.180&r1=text&r2=text

Patches:
Index: manuscripts/xupdf/article.rst
diff -u manuscripts/xupdf/article.rst:1.179 manuscripts/xupdf/article.rst:1.180
--- manuscripts/xupdf/article.rst:1.179 Sat Feb 15 18:04:27 2003
+++ manuscripts/xupdf/article.rst       Sat Feb 15 18:06:40 2003
@@ -224,7 +224,7 @@
   ("once you get there, you should see how you can get back").
   This implies bidirectional links.
 
-Let us start form
+Let's start form
 one scrollable node ("current document").
 To be able to show all the link targets near the anchors,
 only the *relevant fragments* (the immediate surroundings of the other
@@ -238,10 +238,10 @@
 especially preattentively ("at-a-glance") [treismangelade]_.
 In order to let the user perceive the source of the fragment,
 we texture each node with a unique background texture
-generated procedurally from the identity of the node.
+generated procedurally from the node's id [ XXX ref proctext ].
 
-In the following subsections, we discuss the details
-of the main components of the interface: buoy placement, unique backgrounds, 
+In the following subsections, we discuss
+the main components of the interface, buoy placement and unique backgrounds, 
 and following that, some techniques which are not as essential but
 support this type of interface by clarifying the graphical appearance:
 break lines,
@@ -255,7 +255,8 @@
 all graphical objects are placed
 in either the coordinate system of the
 virtual paper (e.g., the margins of the web page being scrolled)
-or the external coordinate system, independent of the page.
+or an external coordinate system, independent of the page
+(e.g., in another window).
 This is originally because of performance: it is most efficient to update
 a single, rectangular (or rectangular, rectangularly obscured) area 
 of screen.