cygwin-x-doc/faq config.xml, 1.8, 1.9 cygwin-x-faq.xml, 1.8, 1.9 general.xml, 1.5, 1.6 remote.xml, 1.9, 1.10

Committed by: ago

Update of /cvs/xserver/cygwin-x-doc/faq
In directory gabe:/tmp/cvs-serv31737/faq

Modified Files:
	config.xml cygwin-x-faq.xml general.xml remote.xml 
Log Message:
2004-10-02  Alexander Gottwald  <[email protected]>

        * faq/config.xml:
        * faq/cygwin-x-faq.xml:
        * faq/general.xml:
        * faq/remote.xml:
        General revision. Fixed some formatting, added glossary links


Index: config.xml
===================================================================
RCS file: /cvs/xserver/cygwin-x-doc/faq/config.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -d -r1.8 -r1.9
--- config.xml	1 Oct 2004 18:39:46 -0000	1.8
+++ config.xml	2 Oct 2004 22:06:01 -0000	1.9
@@ -11,14 +11,14 @@
 extra dependencies it was removed again.  But most of the options
 which were configurable in the configfile are now available as
 commandline options.  For more information on configuring other
-keyboard layout see <xref
+keyboard layouts see <xref
 linkend="q-non-U.S.-keyboard-layout"></xref></para> </answer>
 </qandaentry>
 
 
 <qandaentry>
 <question id="q-command-line-args">
-<para>What are the command line arguments for &file-server-exe;?</para>
+<para>What are the command line arguments for &XWin;?</para>
 </question>
 
 <answer>
@@ -30,15 +30,15 @@
 
 <qandaentry>
 <question id="q-display-depth-ignored"> 
-<para>Why does &file-server-exe; ignore the display depth that I pass
+<para>Why does &XWin; ignore the display depth that I pass
 on the command line?</para>
 </question>
 
 <answer>
 <para>When running in windowed mode or GDI-based fullscreen mode,
-&file-server-exe; must run the X Server at whatever display depth
+&XWin; must run the X Server at whatever display depth
 Windows is currently using; in these cases the display depth passed on
-the command line is ignored.  &file-server-exe; only uses the display
+the command line is ignored.  &XWin; only uses the display
 depth parameter when running in a DirectDraw-based fullscreen mode, as
 DirectDraw allows applications to change the display resolution and
 depth when running in fullscreen mode.</para>
@@ -54,7 +54,7 @@
 <answer>
 <para>Yes.  Pass the <parameter>-emulate3buttons <replaceable
 class="option">timeout_in_milliseconds</replaceable></parameter>
-parameter to &file-server-exe;, where <replaceable
+parameter to &XWin;, where <replaceable
 class="option">timeout_in_milliseconds</replaceable> is the, optional,
 maximum number of milliseconds between a button release and opposite
 button press that will trigger an emulated third button press.</para>
@@ -73,6 +73,9 @@
 <screen>Focus FocusFollowsMouse
 </screen>
 Other windowmanagers (eg. windowmaker) have similar features too.</para>
+<para>If you are using the &multiwindow; mode you can not set this behaviour
+in the windowmanager but you can use the TweakUI tool to enable this feature
+for all windows, not limited to &project; windows.</para> 
 </answer>
 </qandaentry>
 

Index: cygwin-x-faq.xml
===================================================================
RCS file: /cvs/xserver/cygwin-x-doc/faq/cygwin-x-faq.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -d -r1.8 -r1.9
--- cygwin-x-faq.xml	1 Oct 2004 18:39:46 -0000	1.8
+++ cygwin-x-faq.xml	2 Oct 2004 22:06:01 -0000	1.9
@@ -73,6 +73,10 @@
 <!ENTITY multiplemonitors "<parameter>-multiplemonitors</parameter>">
 
 <!ENTITY DISPLAY "<parameter>DISPLAY</parameter>">
+
+<!ENTITY XDMCP "<glossterm linkend='gloss-xdmcp'>XDMCP</glossterm>">
+<!ENTITY X11Forwarding "<glossterm linkend='gloss-x11forwarding'>X11Forwarding</glossterm>">
+<!ENTITY UNIX "<acronym>UNIX</acronym>">
 ]>
 
 <article class="faq" id="cygwin-x-faq">

Index: general.xml
===================================================================
RCS file: /cvs/xserver/cygwin-x-doc/faq/general.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -d -r1.5 -r1.6
--- general.xml	24 Sep 2004 12:37:25 -0000	1.5
+++ general.xml	2 Oct 2004 22:06:01 -0000	1.6
@@ -7,8 +7,10 @@
 </question>
 
 <answer>
-<para>&project; is a port of the &x-window-system; to &cygwin;;
-&cygwin; provides a UNIX-like API on the Win32 platform.</para>
+<para>
+&project; is a port of the &x-window-system; to &cygwin;. 
+&cygwin; provides a &UNIX;-like API on the Win32 platform.
+</para>
 </answer>
 
 </qandaentry>
@@ -20,11 +22,11 @@
 </question>
 
 <answer>
-<para>Cygwin tools are, in the words of the <ulink
+<para>&cygwin; tools are, in the words of the <ulink
 url="&cygwin-home;">&cygwin; homepage</ulink>, <quote>ports of the
 popular GNU development tools and utilities for Windows 95, 98, and
 NT.  They function by using the &cygwin; library which provides a
-<acronym>UNIX</acronym>-like API on top of the Win32 API.</quote>
+&UNIX;-like API on top of the Win32 API.</quote>
 &cygwin; provides the compiler (gcc), libraries, headers, and other
 utilities which build and support the operation of &project;.</para>
 </answer>
@@ -39,7 +41,7 @@
 <answer>
 <blockquote>
 <attribution><citation>ScheiflerGettys92</citation></attribution>
-<para>The X Window System, or X, is a network-transparent window system.
+<para>The &x-window-system;, or X, is a network-transparent window system.
 With X, multiple applications can run simultaneously in windows,
 generating text and graphics in monochrome or color on a bitmap
 display.  Network transparency means that application programs can run
@@ -88,16 +90,19 @@
 <answer>
 <para>The <replaceable>:0.0</replaceable> part of the &DISPLAY; variable denote
 the display and the screen of an X server.</para>
+
 <para>The display is the first number and equals to a running instance of an 
 X server. If it is using TCP/IP for communication it listens on port 6000 + 
 <replaceable>display-number</replaceable> for connections.
 With local (UNIX domain sockets) it uses the socket 
 <filename>/tmp/.X11-unix/X<replaceable>display-number</replaceable></filename>
 </para>
+
 <para> The screen denotes different output devices of the X server. You could 
 start &XWin; with two <parameter>-screen</parameter> options and would end up 
 with two X11 windows. Each of them is a different screen. Other X servers open
 different screens for different monitors connected to the computer.</para>
+
 <para>&project; supports different formats of the &DISPLAY; variable
 <itemizedlist>
 <listitem>
@@ -138,12 +143,12 @@
 
 <listitem>
 <para>An X Server on Windows may be used to display the output of
-programs running on remote <acronym>UNIX</acronym> machines.</para>
+programs running on remote &UNIX; machines.</para>
 </listitem>
 
 <listitem>
 <para>&project;, in conjunction with &cygwin;, provides a complete
-compatibility layer for compiling and running <acronym>UNIX</acronym>
+compatibility layer for compiling and running &UNIX;
 applications on Microsoft Windows.</para>
 </listitem>
 </itemizedlist>
@@ -175,7 +180,7 @@
 online archive of the mailing list traffic.</para> <tip><para>Post
 your X-related inquires to &project-ml; only; do not post nor cross
 post your inquires to the &cygwin-ml; mailing list.  &cygwin;'s
-mailing list is only for &cygwin; API related inquires that are not
+mailing list is only for &cygwin; related inquires that are not
 handled by another more-specific list.</para></tip>
 </answer>
 </qandaentry>

Index: remote.xml
===================================================================
RCS file: /cvs/xserver/cygwin-x-doc/faq/remote.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -d -r1.9 -r1.10
--- remote.xml	30 Sep 2004 21:05:52 -0000	1.9
+++ remote.xml	2 Oct 2004 22:06:01 -0000	1.10
@@ -10,20 +10,20 @@
 <label>A1:</label>
 
 <para>OpenSSH 3.8 enables untrusted X11 forwarding by default when
-connecting to an ssh server that supports untrusted X11 forwarding.
+connecting to an ssh server that supports untrusted &X11Forwarding;.
 Most ssh servers for &linux; are versions of OpenSSH that do support
-untrusted X11 forwarding, so using OpenSSH 3.8 from Cygwin will result
-in a connection that uses untrusted X11 forwarding by default.  You will
+untrusted X11Forwarding, so using OpenSSH 3.8 from Cygwin will result
+in a connection that uses untrusted X11Forwarding by default.  You will
 quickly notice that this is the case if most of your X applications
 are now killed when you try to copy and paste or if
 <command>xdpyinfo</command> returns only a fraction of the supported
 extensions that it does if run locally.</para>
 
-<para>It is easiest to just override untrusted X11 forwarding by passing
+<para>It is easiest to just override untrusted X11Forwarding by passing
 <parameter>-Y</parameter> to <command>ssh</command> in place of
 <parameter>-X</parameter>.  The <parameter>-Y</parameter> does the
-same thing as <parameter>-X</parameter>, but it enables trusted X11
-forwarding for the current connection.</para>
+same thing as <parameter>-X</parameter>, but it enables trusted X11Forwarding 
+for the current connection.</para>
 </answer>
 
 
@@ -31,7 +31,7 @@
 <label>A2:</label>
 
 <para>Before establishing the ssh connection the xserver must be
-started and the environment variable <parameter>DISPLAY</parameter>
+started and the environment variable &DISPLAY;
 must be set for ssh.
 
 <screen>
@@ -45,7 +45,7 @@
 <screen>
 $ DISPLAY=<replaceable>localhost:0.0</replaceable> ssh -Y <replaceable>remotehost</replaceable>
 </screen>
-The parameter <parameter>-Y</parameter> enables trusted X11 Forwarding. 
+The parameter <parameter>-Y</parameter> enables trusted X11Forwarding. 
 This is available since OpenSSH 3.8. If you have an older version of ssh
 you will have to use <parameter>-X</parameter>.
 </para>
@@ -56,8 +56,7 @@
 <label>A3:</label>
 <para>
 Make sure you're not starting ssh with the parameter <parameter>-x</parameter> 
-(lowercase). This disables <glossterm linkend="gloss-x11forwarding">
-X11Forwarding</glossterm>. 
+(lowercase). This disables X11Forwarding. 
 </para>
 </answer>
 
@@ -136,11 +135,10 @@
 
 <answer>
 <para>&project; is sometimes unable to determine which local network
-interface's address should be reported to the <glossterm
-linkend="gloss-xdmcp">XDMCP</glossterm> server; in these cases you
-need to pass <parameter>-from</parameter> <replaceable
+interface's address should be reported to the &XDMCP; server; in these 
+cases you need to pass <parameter>-from</parameter> <replaceable
 class="option">local_host_name_or_ip_address</replaceable> to
-&file-server-exe; to specify which interface address to report.</para>
+&XWin; to specify which interface address to report.</para>
 </answer>
 </qandaentry>
 
@@ -157,7 +155,7 @@
 <screen>
 192.168.26.1 myhost
 </screen>
-to /etc/hosts on the XDMCP server with the IP address and the hostname 
+to /etc/hosts on the &XDMCP; server with the IP address and the hostname 
 of your windows host the name resolution should work.
 </para>
 </answer>
@@ -170,7 +168,7 @@
 </question>
 
 <answer>
-<para>[Mika Laitio] For security reasons, XDMCP is not enabled by
+<para>[Mika Laitio] For security reasons, &XDMCP; is not enabled by
 default on most Linux/UNIX/*NIX/*BSD distributions (RedHat, Mandrake,
 SuSE, FreeBSD, NetBSD, etc.) by default.  You have to manually enable
 remote logins to your X Display Manager (<command>xdm</command>,
@@ -232,7 +230,7 @@
 </answer>
 
 <answer>
-<para>XDMCP will not work correctly if you have a personal firewall installed
+<para>&XDMCP; will not work correctly if you have a personal firewall installed
 or the built-in firewall of Windows is activated.</para>
 <para>The XDMCP protocol will send and receive data on port 177/UDP. But the 
 actual connections will be made to the local port 6000/TCP. It is safe to 
@@ -294,7 +292,7 @@
 XDM login prompt will never appear.  The simplest solution is to point
 &project; at the font server that is usually running on the Solaris
 machine.  You'll need a command line similar to the following to start
-your XDMCP session and to connect to the Solaris font server:</para>
+your &XDMCP; session and to connect to the Solaris font server:</para>
 
 <para>
 <userinput>&file-server-exe; -query
@@ -344,7 +342,7 @@
 
 <qandaentry>
 <question id="q-cde-via-xdmcp-hangs">
-<para>Login to <acronym>CDE</acronym> on &sun-solaris; via XDMCP hangs
+<para>Login to <acronym>CDE</acronym> on &sun-solaris; via &XDMCP; hangs
 &project;.</para>
 </question>