[l10n-russian CVS] release-notes/sgml release-notes.en.sgml, 1.8, 1.9

Yuri Kozlov yuray-guest at alioth.debian.org
Mon Mar 26 18:47:21 CET 2007


Update of /cvsroot/l10n-russian/release-notes/sgml
In directory alioth:/tmp/cvs-serv4841/sgml

Modified Files:
	release-notes.en.sgml 
Log Message:


Index: release-notes.en.sgml
===================================================================
RCS file: /cvsroot/l10n-russian/release-notes/sgml/release-notes.en.sgml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -d -r1.8 -r1.9
--- release-notes.en.sgml	22 Mar 2007 18:36:16 -0000	1.8
+++ release-notes.en.sgml	26 Mar 2007 17:47:19 -0000	1.9
@@ -361,16 +361,17 @@
              Languages dropped in this relase due to lack of translation
              updates include Persian and Welsh. 
 <![ %g-i [
-	     If the graphical user interface is used, an additional 11
+	     If the graphical user interface is used, an additional eleven
 	     languages are supported. These languages can only be selected
-             using this installer as their fonts cannot be presented
-             in non-graphical environments.
+	     using this installer as their character sets cannot be presented
+	     in a non-graphical environment. The new languages are:
+	     Bengali, Dzongkha, Gujarati, Hindi, Georgian, Khmer, Malayalam,
+	     Nepali, Punjabi, Tamil and Thai.
 ]]>
-             Users that do not wish to use any local can now select
-             <em/C/ as their preferred local in the installer's language
+             Users that do not wish to use any locale can now select
+             <em/C/ as their preferred locale in the installer's language
              selection.
-             More information on 
-             language coverage is available at the
+             More information on language coverage is available at the
              <url id="&url-d-i-i18n;" name="d-i languages list">.
 	     </p></item>
              
@@ -381,7 +382,7 @@
              what the system's country and timezone is based on the
              language selected, or will provide a limited selection
              if it cannot. Users can still introduce obscure 
-             combinations if needed be.</p></item>
+             combinations if need be.</p></item>
 ]]> <!-- not-s390 -->
 
 	   </taglist></p>
@@ -467,19 +468,27 @@
 
        <item>inetd: new default is OpenBSD's</item>
 
-       <item>portmap bound to loopback by default</item>
+       <item>vi: the variant installed by default is a compact version of
+       <prgn/vim/ (<package/vim-tiny/) instead of <package/nvi/
 
-       <item>mail server not listening to connections per default</item>
+       <item>mail server setup for local delivery per default (sarge users retain their config)</item>
 
-       <item>development packages now priority optional, will not get installed (#301138)</item>
+       <item>development packages now priority optional, will not get installed (#301138), sarge users need to manually remove gcc, binutils et al</item>
 
-       <item>new standard task in tasksel installs all standard and above</item>
+       <item>new standard task in tasksel installs all packages of priority
+       standard and higher</item>
 
-       <item>filesystem improvements</item>
+       <item>filesystem improvements, see wiki</item>
 
        <item>packages pulled in for laptops</item>
+       </list></p>
 
-       <item>localization-config NOT installed by d-i, needs to be run separately</item>
+      <sect id="regressions_in_etch"><heading>Regressions</heading>
+
+      <p>TODO: Things that are worst in etch than in sarge
+
+      <list>
+       <item>localization-config NOT installed by d-i, actually not available in etch (#402566). Some i18n/l10n steps need to be done manually (such as installing some packages based on locale).</item>
 
        </list></p>
 
@@ -944,7 +953,7 @@
 	  report. To start the recording, type:
 
           <example>
-# script -t -a ~/upgrade-to-&releasename;.typescript 2>~/upgrade-to-&releasename;.timing
+# script -t -a ~/upgrade-&releasename;.script 2>~/upgrade-&releasename;.time
           </example>
 
 	  or similar. Do not put the typescript file in a temporary
@@ -954,7 +963,7 @@
 
           <p>The typescript will also allow you to review information that has
           scrolled off-screen. Just switch to VT2 (using <tt/Alt-F2/) and, after
-          logging in, use <tt>less -R ~root/upgrade-to-&releasename;.typescript</tt>
+          logging in, use <tt>less -R ~root/upgrade-&releasename;.script</tt>
           to view the file.</p>
           
 
@@ -967,7 +976,7 @@
           you can use the <prgn/scriptreplay/ program to replay the whole session:
           
           <example>
-# scriptreplay ~/upgrade-to-&releasename;.timing 2>~/upgrade-to-&releasename;.typescript
+# scriptreplay ~/upgrade-&releasename;.time ~/upgrade-&releasename;.script
           </example>
 
           </p>
@@ -1355,6 +1364,9 @@
           linux-image-2.6-* metapackage.
           This package may be installed automatically by the dist-upgrade
           process. You can verify this by running:
+<!-- NOTE (jfs): Users using apt/aptitude might not have their available file
+     updated so '^ii' is really unnecesary, maybe dpkg -l 'linux-image*' would be
+     better here? -->
           <example>
 # dpkg -l | grep '^ii  linux-image'
           </example></p>
@@ -1398,7 +1410,7 @@
         <sect1 id="rerunlilo"><heading>Rerun lilo</heading>
 
           <p>If you are using <package/lilo/ as your bootloader (it is the
-          default bootloader for &oldreleasename;) it is strongly recommended
+          default bootloader for some installations of &oldreleasename;) it is strongly recommended
           that you rerun lilo after the upgrade:
           <example>
 # /sbin/lilo
@@ -1956,28 +1968,27 @@
         2.14 Release Notes">.</p>
       </sect>
 
-      <sect id="nano"> <heading>Default editor changed to nano</heading>
-        <p>The default editor for default installations in &releasename; is <package/nano/.
-        Previous Debian releases set the default editor for all users to
-        <package/vim/, in this release the default behaviour has changed and users
-        will get a more user-friendly editor.</p>
-        
-        <p>Users wishing to retain the previous behaviour can either define the
-        environment variable <em>EDITOR</em> by introducing the following lines
-        in their own profiles:
+<!-- FJP: Bug #398887 -->
+      <sect id="default-editor"> <heading>Default editor</heading>
+        <p>If you were using <prgn/vim/ as your default editor, this may
+	be changed to <prgn/nano/ during the upgrade.</p>
+
+        <p>Administrators that wish to change the default editor for all users
+        will have to update the alternatives system using:
 
           <example>
-EDITOR=vi
-export EDITOR
-alias editor=$EDITOR
+# update-alternatives --config editor
           </example>
         </p>
 
-        <p>Administrators that wish to change the behaviour for all users will have
-        to update the alternatives system using:
+        <p>Users wishing to change the default editor can define the
+        environment variable <em>EDITOR</em> by introducing the following lines
+        in their own profiles:
 
           <example>
-# update-alternatives --config editor
+EDITOR=vi
+export EDITOR
+alias editor=$EDITOR
           </example>
         </p>
 




More information about the l10n-russian-cvs-commits mailing list