yoswink     06/01/16 01:10:29

  Modified:    xml/htdocs/doc/en faq.xml
  Log:
  Fixed a broken link to guide-localization.xml

Revision  Changes    Path
1.103     +5 -5      xml/htdocs/doc/en/faq.xml

file : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/faq.xml?rev=1.103&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/faq.xml?rev=1.103&content-type=text/plain&cvsroot=gentoo
diff : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/faq.xml.diff?r1=1.102&r2=1.103&cvsroot=gentoo

Index: faq.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/faq.xml,v
retrieving revision 1.102
retrieving revision 1.103
diff -u -r1.102 -r1.103
--- faq.xml     6 Jan 2006 16:06:31 -0000       1.102
+++ faq.xml     16 Jan 2006 01:10:29 -0000      1.103
@@ -1,5 +1,5 @@
 <?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/faq.xml,v 1.102 2006/01/06 
16:06:31 flammie Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/faq.xml,v 1.103 2006/01/16 
01:10:29 yoswink Exp $ -->
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
 <guide link="/doc/en/faq.xml">
@@ -44,8 +44,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>3.4</version>
-<date>2006-01-06</date>
+<version>3.5</version>
+<date>2006-01-16</date>
 
 <chapter>
 <title>Questions:</title>
@@ -813,8 +813,8 @@
 console working correctly with extended characters in your keymap you might
 also need to set up variables <c>CONSOLETRANSLATION</c> and <c>CONSOLEFONT</c>
 in your <path>/etc/conf.d/consolefont</path> (for further information on
-localising your environment, refer to <uri link="/doc/en/guide-localization">
-our localisation guide</uri>.).
+localising your environment, refer to <uri 
+link="/doc/en/guide-localization.xml">our localisation guide</uri>).
 Then, either <c>reboot</c>, or restart the keymaps and consolefont scripts:
 </p>
 



-- 
[email protected] mailing list

Reply via email to