[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#514009: Release notes: section about Braille displays in installing.dbk/installing.po


Christian Perrier, le Wed 04 Feb 2009 20:00:32 +0100, a écrit :
> > > Eventually, a section about voice synthesis devices could be added,
> > > but I don't have written material for this.
> > 
> > You can probably just pick up the text from my patch.
> I'm not sure I can meet the freeze deadline for the release notes,
> which is upcoming week-end....

Here is a patch.

Index: release-notes.ent
--- release-notes.ent	(révision 6251)
+++ release-notes.ent	(copie de travail)
@@ -63,6 +63,7 @@
 <!ENTITY url-wiki-selinux "&url-wiki;SELinux">
 <!ENTITY url-wiki-newinlenny "&url-wiki;NewInLenny">
 <!ENTITY url-ftpmaster "http://ftp-master.debian.org";>
+<!ENTITY url-speakup-driver-codes "http://www.linux-speakup.org/spkguide.txt";>
 <!ENTITY architecture "<phrase arch='alpha'>alpha</phrase><!--
 		    --><phrase arch='amd64'>amd64</phrase><!--
Index: en/installing.dbk
--- en/installing.dbk	(révision 6251)
+++ en/installing.dbk	(copie de travail)
@@ -273,7 +273,28 @@
+<section id="install-with-speech">
+  <title>Install &debian; with a hardware speech synthesis</title>
+  <para>
+    Support for hardware speech syntheses is enabled only along support for
+    graphical installer.  You thus need to select the <computeroutput>Graphical
+    install</computeroutput> entry in the boot menu.
+  </para>
+  <para>
+    Hardware speech syntheses can not be automatically detected.  You thus need
+    to append the <userinput>speakup.synth=driver</userinput> boot parameter
+    to tell Speakup which driver it should use. <userinput>driver</userinput>
+    should be replaced by the driver code for your device, see <ulink
+    url="&url-speakup-driver-codes;"></ulink> for a list.  The textual version
+    of the installer will then be automatically selected, and support for the
+    speech synthesis will be automatically installed on the target system.
+  </para>

Reply to: