--- Begin Message ---
- To: Mario Lang <mlang@teleweb.at>
- Subject: (see attach): Mini howto : Gnome 2 + Gnopernicus + other
- From: info@brlspeak.net
- Date: Sun, 6 Oct 2002 10:54:56 +0200
- Message-id: <20021006105456.E452@torvalds>
- In-reply-to: <871y74si6m.fsf@lexx.delysid.org>; from mlang@teleweb.at on Sat, Oct 05, 2002 at 11:13:21PM +0200
- References: <200210030959120630.0212F053@smtp.ifrance.com> <871y74si6m.fsf@lexx.delysid.org>
Hi Mario,
I send you in private what I downloaded from Nath's site (she is using
her own dyndns, but that computer is normally up 23/7).
Osvaldo La Rosa - http://www.brlspeak.net/
(see attach).
Installing Gnome 2 and Gnopernicus
Written by Nath (10/01/2002)
INTRODUCTION
Before beginning I suggest that you visit the Gnome Accessibility
Project (GAP) web page in order to have a global vision of the
project. Visit the web page at:
[1]http://developer.gnome.org/projects/gap/ In this howto I will
explain the steps required to build Gnome 2 and gnopernicus, and how
to get them up and operating on your computer.
You will need to complete these steps before you can use gnopernicus :
[2]SECTION 1 : Building and installing Gnome 2 [3]SECTION 2 : Building
and installing some extra packages [4]SECTION 3 : Building and
installing Festival TTS [5]SECTION 4 : Building and installing
gnome-mag, gnome-speech and gnopernicus [6]SECTION 5 : Starting to use
Gnopernicus
Building and Installing Gnome 2
In this section the goal is to build and install the Gnome 2
environment using available tarball source packages from gnome.org.
I used the Garnome script which should download, build, and install
the Gnome 2 environment in any directory that you specify. You can
obtain the Garnome script from :
[7]http://www.gnome.org/~jdub/garnome/ You should read all the
instructions given on this web page. After doing so you should have no
problems building and installing the Gnome 2 environment.
A note to the reader : Make sure that you have built and installed all
the required libraries. Also, remember to modify the line beginning
with the word "prefix..." in the "gar.conf.mk" file to set the
location where you wish to build and install the Gnome 2 environment.
Building and installing some extra packages
Once you have installed the Gnome 2 environment using Garnome you will
need to download and install some additional packages that Garnome
doesn't include by default.
Download and install the following packages :
* intltool
* gnome-common
* libgail-gnome
* at-spi
* sawfish
I have forgotten a few packages, but if you have any problems don't
hesitate to contact me. Perhaps, together we can figure it out.
To get the missing packages you must go to the GARNOME directory and
for each package execute the following commands followed by the enter
key :
$ cd gnome/package_name/
$ make install
Building and installing Festival TTS
At this point you will need to download and install the Festival TTS
packages for speech. I will give you the instructions for Debian,
because I personally use Debian. For other distributions you will need
to download and build Festival TTS in the traditional way.
For Debian users use the following command :
$ apt-get install festival festlex-cmu festlex-poslex festvox-kdlpc16k
For users not using Debian you can always retrieve the festival source
from :
[8]http://www.festvox.org/ Download all the source tarballs, extract
them to a single directory, and run the following commands :
$ ./configure
$ make
$ make install
Building and installing Gnome-mag, Gnome-speech and Gnopernicus
Finally, we have come to the last step. You should visit the
Gnopernicus web site, and read and follow all the instructions on this
web page. You can visit the gnopernicus web page at:
[9]http://www.baum.ro/gnopernicus.html At this point if you have not
already done so you should remember to run the "go_gnome" script which
will initialize some required environment variables.
Regarding all the things that has been done before, running this last
step, downloading, building and installing gnome-mag, gnome-speech and
gnopernicus should be the only things left to do now.
I checked out the gnome-speech, gnome-mag, and gnopernicus packages,
and I installed these packages in my Gnome 2 tree using the
"--prefix=/repertoire_gnome2/" option when running the "./autogen.sh"
script.
While building gnome-mag you may receive an error message. In such a
case, just check out an older gnome-mag release in the CVS tree using
the following command :
cvs -z3 checkout -r gnome-2-0 gnome-mag
Starting to use gnopernicus
First of all, we will need to set some environment/initialization
variables. You should open the bash_profile file in your favorite text
editor and add the following lines to it. Feel free to change the
lines to fit your personal needs.
export MAGNIFIER=0
export FESTIVAL=1
export VIAVOICE=0
export PATH=/gnome_directory/bin:$PATH
export LD_LIBRARY_PATH=/gnome2_directory/lib
export PKG_CONFIG_PATH=/gnome2_directory/lib/pkgconfig
export GTK_MODULES="gail:atk-bridge"
export GDK_USER_XFT=1
Save your changes, and exit the file. In order to have these
environment variables properly initialized you must logout and then
login again.
Now, using your favorite text editor we must create a file named,
"xinitrc," in your home directory. This file will be used when
invoking the "startx" command so we can run Gnome 2. For example my
".xinitrc" file contains the following lines :
festival --server &
gnopernicus &
sawfish &
gnome-terminal &
exec gnome-session
Ah, last point : In order to run the Gnome 2 environment and to be
able to use assistive technology, we must enable accessibility support
which is disabled by default. To do this type the following line :
$ gconftool-2 -s -t bool /desktop/gnome/interface/accessibility true
Now, the moment we all have been waiting for. Type the command :
$ startx
If all went well Gnopernicus should speak to you. If it doesn't don't
worry I am sure we will be able to help you. I am certain we will
succeed. See the contact information further down in this document.
APPENDIX A : Installing X
If you are blind like me you probably do not know how to install the
X-windows system. It's normal because until now we were unable to use
it. Back then, what was the point installing X knowing it was not
something we could use ?
I am going to show you how to install X on a Debian system. I
apologize that I can not tell you how to install X on other Linux
distributions.
In Debian we are going to use the traditional "apt-get" command. Type
the following line :
$ apt-get install xserver-xfree86 xfree86-common xserver-common
xbase-clients xfonts-base xutils xfonts-100dpi xfonts-75dpi
The debconf utility will ask you some questions. Answer these
questions the best you can so you can obtain a properly working
X-Windows system.
It's necessary to know your hardware characteristics : graphic card,
keyboard, mouse and monitor. Knowing these things and with a little
patience you can succeed.
If you wish to reconfigure the X server simply type the following
command :
$ dpkg-reconfigure xserver-xfree86
APPENDIX B : Contacts
If you need help or you wish to discuss Gnome Accessibility and
assistive technologies, join the gnome-accessibility-list. To
subscribe go to the following URL :
[10]http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
You can also contact me by sending an email to: [11]Nath Comments and
suggestions about this page are welcome
APPENDIX C : Thanks
Particular thanks to the Gnome Accessibility team (Bill, Michael and
all the others) who help me to build and install this environment.
Thanks to Thomas for his corrections and tests.
References
1. http://developer.gnome.org/projects/gap/
2. http://tux31.homelinux.net/linux/inst_gnome2_accessibility.htm#SECTION1
3. http://tux31.homelinux.net/linux/inst_gnome2_accessibility.htm#SECTION2
4. http://tux31.homelinux.net/linux/inst_gnome2_accessibility.htm#SECTION3
5. http://tux31.homelinux.net/linux/inst_gnome2_accessibility.htm#SECTION4
6. http://tux31.homelinux.net/linux/inst_gnome2_accessibility.htm#SECTION5
7. http://www.gnome.org/~jdub/garnome/
8. http://www.festvox.org/
9. http://www.baum.ro/gnopernicus.html
10. http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
11. mailto:nath31@ifrance.com
GARNOME
GARNOME - the bad-ass, bleeding edge GNOME distribution for testers
and tweakers everywhere - is finally released unto the teeming
masses. If you're dying to try the GNOME 2.0 Desktop, but don't
want to fall into the depraved addictions and co-dependencies of
testing from anonymous CVS, then GARNOME is for you.
What is GARNOME?
It's a bad-ass, bleeding edge GNOME distribution for testers and
tweakers everywhere. Those not paying attention can stay after
class.
GARNOME is a new distribution of GNOME, based on the [1]GAR ports
system by Nick Moffitt. Right now, it builds from the recent GNOME
2.0 Desktop tarball releases, and includes some extra software that
has been ported to the GNOME 2.0 platform.
GARNOME will be updated regularly throughout the GNOME 2.0 Desktop
testing process, and possibly thereafter depending on interest.
Join our [2]mailing list!
What do I need to install GARNOME?
First you'll have to [3]download GARNOME! Please read the
[4]ChangeLog.
A sane GNU tool chain (gcc, make, flex, bison, gettext, etc).
gzip and bzip2
The following basic libraries that GNOME depends on; every
distribution should have these available or installed already. Here
are the Debian package names as a reference:
Libraries:
libpng2-dev
libjpeg-dev
libtiff-dev
xlibs-dev
libpopt-dev
libgdbmg1-dev (librep)
libgmp3-dev (librep)
texinfo (librep)
libgnome-dev (rep-gtk - that's libgnome 1.x, believe it or not)
libdb3-dev (GConf)
libbz2-dev, zlib1g-dev (gnome-vfs, others)
python2.2 + python2.2-xml (libglade)
sp + sgml-data + docbook-xml (Docbook DTD 4.1.2) + docbook-xsl
(Docbook XSL Stylesheets)
libncurses5-dev (gnome-utils)
How do I use GARNOME?
Unpack the tarball, and optionally tweak the settings to your
liking. The defaults should work without problems, but please read
the [5]configuration guide for tips. Once that's done:
cd meta/gnome-desktop/
make install
That's all there is to it; your GNOME 2.0 system will begin to
build and install immediately.
If you want to build packages individually, just cd to their
garball directory and type make install.
How do I configure GARNOME?
All the local settings are kept in gar.conf.mk. Here are the most
useful ones:
FILE_SITES: If you've downloaded the tarball collection already,
add a standard file URL to them here. Your FILE_SITES line should
look like this:
FILE_SITES = file://$(FILEDIR)/
file:///home/user/downloads/garnome/
MASTER_SITES: If you'd prefer to use an ftp, http, scp or rsync
mirror closer to you, add them to the beginning of this line
(mirrors are tried in order).
prefix: Currently the default install location is $(HOME)/garnome.
If you'd prefer to install GNOME 2.0 elsewhere, change this entry.
FAQ
1. Can I install GARNOME without breaking my current GNOME 1.4 setup?
Sure, that's part of what GARNOME is for! By default, it will
install to ~/garnome/ and not effect any of your GNOME 1.4
packages. It may affect your configuration files though, so you
ought to back them up or use a totally different user to run
GARNOME.
2. How long does GARNOME take to build?
On my Athlon 750, 512MB RAM system, building the GARNOME 0.7.0
meta-gnome-desktop garball with time(1) returns:
real 178m29.196s
user 74m51.320s
sys 20m6.170s
3. How much space does GARNOME require to build?
On my x86 system, GARNOME 0.9.6 requires 1.2GB as build space, and
215MB once installed.
4. GARNOME always fails on the checksums, are my tarballs broken?
Probably not - are you using a non-English system and GARNOME
0.5.x? If so, please upgrade to a more recent version, as there is
a fix for this suggested by Rafael Rigues from Conectiva. Thanks
Rafael!
5. My build fails saying it can't find libglade-convert, but I've
already built libglade successfully. What's all that about?
You really do need Python 2 and its XML modules to build libglade!
It only offers a warning at the moment, but without these
installed, it will not build the libglade-convert script.
6. My build fails when /etc/xml/catalog or the Docbook DTD can't be
found. How do I fix that?
Please install GARNOME 0.8.5, which fixes this issue. For older
versions of GARNOME, you can follow these directions:
First, make sure you have the Docbook XML DTD 4.1.2 installed. Then
run the buildDocBookCatalog script provided in the scrollkeeper
garball, like so:
cd gnome/scrollkeeper
PATH=$HOME/garnome/bin:$PATH files/buildDocBookCatalog
It will create $HOME/xmlcatalog, copy this to /etc/xml/catalog once
it's built.
7. Now scrollkeeper fails with: find: /usr/share/xml: No such file or
directory
could not locate chunk-common.xsl of DocBook XSLT stylesheets,
what do I do?
Sure you've got the Docbook XSL Stylesheets installed?
8. Scrollkeeper seems to hang when running scrollkeeper-update. Is
this normal?
Yes, it's okay. You just have to wait a while for it to finish
processing (sometimes a long while). Nothing to be alarmed about.
9. My gnome-applets build fails with:
mini-commander_applet.o(.text+0x375): undefined reference to
`terminal_init', what's wrong?
This was a bug in gnome-applets some time ago (pre-0.6.0), which
could be fixed by compiling with -O2, because it happens in a dead
code area. (After an if(1) statement! Holy cow!) You can either
add CFLAGS = -O2 to the gnome-applets Makefile, or upgrade to
0.6.0.
10. It's finished building, so... Now what?
It depends on how you normally log in. With Debian's gdm, I can
add the following lines to my .xsession file, and choose Xsession
from the Sessions menu:
PATH=$HOME/garnome/bin:$PATH
LD_LIBRARY_PATH=$HOME/garnome/lib:$LD_LIBRARY_PATH GDK_USE_XFT=1
export PATH LD_LIBRARY_PATH GDK_USE_XFT
exec $HOME/garnome/bin/gnome-session
Alternatively, you can use an Xnest within your existing session,
but be aware that Xnest doesn't support the RENDER extension.
Here's how:
Xnest :1 -ac -geometry 800x600 &
export PATH=$HOME/garnome/bin:$PATH
export LD_LIBRARY_PATH=$HOME/garnome/lib:$LD_LIBRARY_PATH
export GDK_USE_XFT=1
DISPLAY=:1 $HOME/garnome/bin/gnome-session &
You can also just run the individual applications within your
current session. Make sure you set PATH and LD_LIBRARY_PATH,
however.
11. My gnome-session and Nautilus segfault immediately, what's wrong?
See [6]bug 70351 at bugzilla.gnome.org.
12. How do I use anti-aliased fonts?
Set the GDK_USE_XFT environment variable. eg.: export
GDK_USE_XFT=1
13. When I run anything, it complains about gdkxft, and won't run. Why
is that?
Get rid of gdkxft, please! It doesn't work at runtime with GTK+
1.3, and can barf up your builds too.
14. Where's Sawfish? and Where's Metacity?
Sawfish is currently the GARNOME default window manager as it
needs lots of testing love for the GNOME 2.0 Desktop release.
Earlier versions of GARNOME used Havoc Pennington's metacity
(which is pronounced like opacity, according to Havoc) window
manager by default, but for the moment, it's just built as part of
the gnome-desktop meta garball. You can change to it within your
GNOME 2.0 session like this:
killall sawfish ; sleep 1 ; metacity &
Make sure you save your session when logging out.
15. Who do I talk to about GARNOME?
Join our [7]mailing list, or visit #garnome on irc.gnome.org.
ChangeLog
0.18.0
* Updated to GNOME Development Series Snapshot 2.1.0!
* New: gnome-icon-theme, vte, gnome-themes, Jacob Berkman's launcher
properties patch for Nautilus.
* Fixed: makesum hang in file-less garballs (such as meta garballs).
* Fixed: freetype font crasher, patch pointed out by Frederic
Crozat.
0.17.1
* Fixed: gal2, for silly broken package name (*spanks Jody for being
norty*), thanks to Simon Wong.
* Fixed: gst-plugins, pull the patch and update checksums to new
0.4.1 tarball, because it was re-released (*spanks Thomas for
being norty*), thanks to Simon Wong.
0.17.0
* New: Balsa! [ Should have been added a while back, but I waited
for a new release as the previous one wasn't very G2Dish... But,
um, I guess they're just not going for G2D-ish after all. :-) ]
* New: gworldclock - a very simple multiple-timezone clock
* New: Fresh acme release with more support for PCs. Yay!
* Updated: New GStreamer release!
* Fixed: Splashscreen no longer refers to Preview 8. ;-) [ Needed
checksum, thanks to Jan Schmidt. ]
* Fixed: Point to new FTP directories.
* Fixed: Remove our gimp-print brain damage.
* No longer include bzipped patch for redhat-artwork, because we
want to keep binary files out of the tree.
0.16.2
* Roll a new tarball, don't include stupid diffs. This must be the
buggiest release ever. And they're just dumb bugs, not useful
ones.
0.16.1
* Fixed: Use 2.0.1 FTP source too.
0.16.0
* Updated to GNOME 2.0.2.
* Added: koffice - the KDE office suite, mergeant - what used to be
gnome-db.
* Fixed: Mess in category files.
* Fixed: gimp-print's CUPS stuff was attempting to install out of
prefix. Fixed the hard way.
* Fixed: quick-lounge-applets uncommented. ;-)
* Fixed: Disabled -Werror -Wall on rhythmbox and gst-plugins, thanks
to ajmitch.
0.15.0
* Updated to GNOME 2.0.2 RC 1.
* Updated GAR system to latest upstream version. HOORAY!
* Moved compiler settings out of category files and into
gar.conf.mk.
* Fixed: memprof should be in gnome-hacker-tools meta garball.
* Fixed: gimp-print now configures with --without-cups, to avoid
out-of-GARNOME-prefix installation borkage.
* Fixed: Remove upstream's glibc workarounds. They just cramp our
elite cross-platform stylin's. Thanks to ajmitch.
* Fixed: gst-plugins -Werror removal fixes some issues, thanks again
to ajmitch.
0.14.1
* Updated: gdm.
* Fixed: rpm2cpio wasn't executable, KDE category file pointed to
the wrong download location, both bugreports thanks to Martijn
Anthonissen.
0.14.0
* Update to what will most likely be GNOME 2.0.2 RC 1.
* Added: goats - a sticky notes applet, gcalctool - a scientific
calculator, quick-lounge-applet - a launcher applet, and
redhat-artwork - some cool stuff from Red Hat's (null) beta
(without the trademarked shadowman stuff).
0.13.1
* Update to GNOME 2.0.1.
* Added: GnomeICU - a great IM client, gnet, memprof - a cool memory
profiling app, and pygtk, orbit-python and gnome-python - Python
bindings for GTK+ and GNOME!
* Fixed: Another bashism, thanks to Jamie Wilkinson.
* Updated: eel, gnome-games, gnome-panel, gnome-vfs-extras (with
awesome SMB support!), gnumeric, gthumb, libgsf, (lib)mrproject,
nautilus and yelp.
0.13.0
* Update to what will most likely be GNOME 2.0.1 RC1.
* Added: gnome-audio, thanks to Aschwin van der Woude, gnome-db
framework and application, totem media player (requires Xine
libraries), gimp-freetype, libgsf, monkey-media, Frank Worsley's
cool Nautilus status dialogue patch - very nice.
* Updated just about everything, but in particular: freetype,
rhythmbox, gst-player and pan.
0.12.2
* Apologies to the GStreamer dudes, I managed to leave the Athlon
optimisations enabled in gstreamer/category.mk. Which was silly.
* Updated libxml2 and libxslt as well. :-)
0.12.1
* Update to KDE 3.0.2.
* Added: kdeaddons, kdeartwork, kdebindings, kdenetwork, kdesdk,
kdevelop, mostfet-liquid. Not entirely sure if the depends are
right for some of these. ;-)
* Added buildclean rule and accompanying BUILD_CLEAN variable in
gar.conf.mk. If you need to build on a small drive, or in tmpfs
([8]!!!), set BUILD_CLEAN to 1. Off by default, because it will
confuse people unfamiliar with GAR.
* Enforced -j1 in some garballs, so that complete parallel builds of
at least the GNOME stuff will build. This effects: GConf, ORBit2,
gnome-panel, libgtkhtml, libgtop, libxml2, sawfish.
* Added Intel and AMD optimised build hints to the category.mk
files. Just go in and swap the comments. AMD hints designed for
GCC 3.1.
* Updated a few GNOME garballs, and included the GStreamer 0.4.0
release. Rhythmbox and gst-player not yet updated for it, don't
expect these to work. :-)
0.12.0
* Update to GNOME 2.0 Desktop Final
0.11.0
* Update to GNOME 2.0 Desktop Release Candidate 1. WOOO!
* Updated lots of other stuff too, such as GIMP, X-Chat, etc.
* Spiffy new splash screen.
0.10.6
* Herman Webley pointed out that the download.us.kde.org mirror had
removed their packages, and it seems that the download.kde.org
redirector adds path components to the URL incorrectly. So, we
have a very fast point release for GARNOME, and a bug report for
the KDE dudes. Just our luck! :-)
0.10.5
* Update to latest weekly snapshot.
* New: gthumb, by Paolo Bacchilega, now ported to the GNOME 2
platform! Very spiffy.
* New: gnome-hacker-tools meta garball, currently just for Glade,
but there'll be more there soon.
* Updated: KDE 3.0.1 (KDE 3.0 was the surprise in the previous
release, for those who don't look at their directory listings
close enough). Try it out!
* Fixed: Added some bits to gar.lib.mk for future use.
0.10.1
* Update to latest weekly snapshot.
* New: magicdev preview, ported by Bastien Nocera and including his
kickarse control panel. Run magicdev, and it will add itself to
your session. Great stuff!
* Fixed: Added Thomas Vander Stichele's gnome-panel and libwnck
patches for tasklists on vertical panels.
* Fixed: Add slightly cleaned up patch from Alvaro Lopez Ortega for
machines without system-prefix GConf.
* Added a little surprise. :-)
0.10.0
* GARNOME Preview 7, incorporating the GNOME 2.0 Desktop Beta 5
release.
* New: glade, Damon Chaplin's user interface design tool for GNOME
2.0.
* Fixed: GARNOME's GConf now refers to out-of-prefix schemas in
/etc/gconf, which makes distribution-installed software such as
Galeon 1.x work correctly.
* Fixed: The meta garballs now include gar.mk correctly. Thanks to
Nick Moffitt.
0.9.8
* New: crux, Seth Nickell's port of the GTK+ theme to GTK+ 2.0;
gtk-cleanice-engine, Bastien Nocera's reinterpretation of Thinice.
* Updated: X-Chat, libglade.
* Fixed: Disabled capplet build in crux, not correct in upstream
tarball.
* Fixed: Replaced Nautilus 1.1.15's libbackground with 1.1.14's, so
you don't get the yucky black background anymore.
* Fixed: Sawfish xterm build issue.
* Fixed: post-install problem with gnome-desktop meta garball, as
per Nick's bug report.
0.9.7
* Based on G2D Snapshot 20020509.
* New: ggv and file-roller!
* New: gnome-fifth-toe and gnome-office meta garballs instead of
gnome-other. They are certainly not official lists of what will be
in those releases, just an educated guess, and a handy way of
separating things out for the time being.
* Fixed: gdm now uses PAM in /etc, although it is still unsupported
in GARNOME. Works fine with some additional set up.
0.9.6
* New: acme, by Bastien Nocera. A keyboard shortcuts daemon, mostly
useful for Apple portable owners, but will soon include
configurable hotkeys and actions and run on multiple platforms.
* Updated: metacity, gnome-terminal, librep, rep-gtk, sawfish.
* Fixed: Included patches from the GStreamer project to allow the
new version of gst-player to run.
* Fixed: Checksumming in non-C locales fixed again. Should have done
it this way the first time!
* Fixed: Run scrollkeeper-update and gst-register as appropriate.
* Fixed: Now using a SourceForge mirror to fix all garballs relying
on SourceForge downloads.
* Fixed: XSETTINGS issue on big endian machines.
0.9.5
* Based on G2D Snapshot 20020501.
* Includes gnome-vfs-extras and gtk-engines as of 0.9.0, plus new
releases of X-Chat, GStreamer and Rhythmbox.
0.9.1
* Fixed up gnome-other's gstreamer depends, as pointed out by Ben
Gamari. Thanks!
0.9.0
* Based on G2D Beta 4. Too many updates to list. :-)
0.8.6
* Brown paper bag release. --disable-gtk-doc is back, and I don't
want to get umpteen million emails about it. ;-)
0.8.5
* Based on G2D Beta 3. Too many updates to list. :-)
* Now includes GIMP 1.3.x and MrProject! Hurrah!
* Some fixes to the buildDocBookCatalog script, first reported by
Uri David Akavia. It now works completely within GARNOME, and you
do not need to modify anything outside your chosen prefix.
* We now build gtk-doc before glib to fix up some libglade errors
for people who have an older version installed on their system
already. Thanks to James Henstridge and the guy who would not tell
me his name (you know who you are).
* Dan Nicolaescu submitted a fix to allow parallel builds of
garballs, but safely disabling it for the GAR system itself.
Thanks Dan!
0.8.0
* Based on Beta 2, plus a couple of snapshot releases.
* The meta garballs are now in a hierarchy of their own, under
meta/. The previous meta packages now exist under that directory.
* Updates to: ORBit2, atk, bonobo-activation, control-center, eel,
gail, gal2, gedit, glib, gnome-applets, gnome-desktop,
gnome-games, gnome-mime-data, gnome-panel, gnome-terminal,
gnome-utils, gnome-vfs, gnumeric, gst-plugins, gstreamer, gtk+,
gtk-doc, intltool, libbonoboui, libglade, libgnome,
libgnomecanvas, libgnomeui, libgtkhtml, librsvg, libwnck, libxml2,
libxslt, libzvt, linc, metacity, metatheme, nautilus, pango,
xchat, yelp.
* It would take far too long to describe the fantastic updates in
this release. Just build it and see for yourself. Nautilus 1.1.9
is beautiful.
* Added: gst-player, a media player for gstreamer;
gtk-thinice-engine, a theme engine for GTK+ and GNOME programs;
monkey-sound, a bonobo component for gstreamer; rhythmbox, a music
player modelled on iTunes that uses gstreamer.
* Removed gst-oldplayer, which is no longer relevant to gstreamer
development.
* We now point to sources/$(GARNAME)/ to make life easier, and build
with -O2.
* GAR: Synched with upstream (GAR is prettier, and a lot less noisy
now), added a check for dist files in makesum so GAR wouldn't sit
waiting for md5sum, added FreeBSD fix for tar stdin usage from
Anthony Taranto.
0.7.5
* Updates to eel, gedit2, gnome-applets, gnome-desktop, gnome-media,
gnome-mime-data, gnome-panel, gnome-session, gnome-system-monitor,
gnome-utils, gnome-vfs, libglade and nautilus.
* Points to snapshot directory on ftp.gnome.org, because pointing to
latest/sources is silly!
* Added aclocaldir patch to librep garball from Dan Nicolaescu.
Thanks!
0.7.0
* All packages updated to GNOME 2.0 Beta status or later, including
the gnome-core split, GTK+ family 1.3.15, and Sawfish as GARNOME
default.
* Added Gnumeric, GStreamer and X-Chat garballs, and created a
gnome-other meta garball to build them all at once. gnome-desktop
will only include the GNOME 2.0 Desktop packages.
* GAR: More compatible tarball extraction, resumes downloads for
ftp, includes scp support, and supports autogen.sh.
* Build with all correct debugging info, which I could have sworn
went quietly into the last release. Silly mans.
0.6.0
* Now uses bz2 archives where available. This cuts the size of the
download significantly.
* Removed 'if !' bashisms for our Solaris users. Please report
further bashisms if found.
* Fix for checksum failure issue on localised systems suggested by
Rafael Rigues from Conectiva.
* Several build issues fixed, GAR files updated with better
comments.
0.5.1
* Brown paper bag release. s/gnome2/gnome/ in garball Makefiles.
0.5.0
* Initial release. Replaced with 0.5.1 tarball.
References
1. http://www.lnx-bbc.org/garchitecture.html
2. http://mail.gnome.org/mailman/listinfo/garnome-list
3. http://www.gnome.org/~jdub/garnome/download/?N=D
4. http://www.gnome.org/~jdub/garnome/#changelog
5. http://www.gnome.org/~jdub/garnome/#configure
6. http://bugzilla.gnome.org/show_bug.cgi?id=70351
7. http://mail.gnome.org/mailman/listinfo/garnome-list
8. http://mail.gnome.org/archives/garnome-list/2002-July/msg00013.html
[festvox.png] |
[1]CMU Speech Software | [2]CMU Speech Group |
_________________________________________________________________
[3]Home
[4]Document
[5]FestVox Download
[6]Festival Download
[7]Voice Demos
[8]Limited Domain
[9]Example Databases
[10]Mailing Lists
[11]Search Documents
[12]Contributed parts
[13]Links
[14]Contact
_________________________________________________________________
Welcome to festvox.org
This project is part of the work at [15]Carnegie Mellon University's
speech group aimed at advancing the state of Speech Synthesis.
The Festvox project aims to make the building of new synthetic voices
more systemic and better documented, making it possible for anyone to
build a new voice. Specifically we offer:
* [16]Documentation, including scripts explaining the background and
specifics for building new voices for speech synthesis in new and
supported languages.
* Specific scripts to build new voices in supported languages, such
as US and UK English.
* Aids to building synthetic voices for [17]limited domains
* [18]Example speech databases to help building new voices.
* Links, demos and a repository for new voices
The documentation, tools and dependent software are all free without
restriction (commercial or otherwise). Licencing of voices built by
these techniques are the responsibility of the builders.
This work is firmly grounded within Edinburgh University's
[19]Festival Speech Synthesis System and Carnegie Mellon University's
[20]small footprint Flite synthesis engine
Requirements for building a voice
Note the techniques and processes described here do not guarantee that
you'll end up with a high quality acceptable voice, but with a little
care you can likely build a new synthesis voice in a supported
language in a few days, or in a new language in a few weeks (more or
less depending on the complexity of the language, and the desired
quality).
You will need:
* To read the [21]documentation
* A Unix machine (e.g. Linux, FreeBSD, Solaris, etc) with working
audio i/o. This may work on other platforms but many scripts,
perhaps unnecessarily, depend on Unix utilties like, awk, sed etc.
* Installed versions of Edinburgh University's [22]Festival Speech
Synthesis System and [23]Edinburgh Speech Tools (distributed with
Festival).
* A waveform viewing/labeling program like emulabel distributed as
part of Macquarie University's [24]EMU speech database system.
Although automatic labeling software is included in festvox, a
display tool is necessary for diagnosis and debugging.
* Patience and care, and a little interest in the subject of speech
technology.
[25]CMU/LTI This page is maintained by [26]Alan W Black
[27](awb@cs.cmu.edu)
and [28]Kevin A. Lenzo [29](lenzo@cs.cmu.edu)
Festvox is a project within [30]LTI at Carnegie Mellon University
festvox.org is hosted on a machine donated by [31]VA Linux Systems
[32]VA Linux Systems
References
1. http://www.speech.cs.cmu.edu/hephaestus.html
2. http://www.speech.cs.cmu.edu/
3. http://www.festvox.org/index.html
4. http://www.festvox.org/festvox/festvox_toc.html
5. http://www.festvox.org/download.html
6. http://www.festvox.org/festival/index.html
7. http://www.festvox.org/voicedemos.html
8. http://www.festvox.org/ldom/index.html
9. http://www.festvox.org/dbs/index.html
10. http://www.festvox.org/maillists.html
11. http://www.festvox.org/search.html
12. http://www.festvox.org/contrib.html
13. http://www.festvox.org/links.html
14. http://www.festvox.org/contact.html
15. http://www.speech.cs.cmu.edu/
16. http://www.festvox.org/festvox/festvox_toc.html
17. http://www.festvox.org/ldom/index.html
18. http://www.festvox.org/dbs/index.html
19. http://www.cstr.ed.ac.uk/projects/festival/
20. http://cmuflite.org/
21. http://www.festvox.org/festvox/festvox_toc.html
22. http://festvox.org/festival/downloads.html
23. http://festvox.org/festival/downloads.html
24. http://www.shlrc.mq.edu.au/emu/
25. http://www.lti.cs.cmu.edu/
26. http://www.cs.cmu.edu/~awb/
27. mailto:awb@cs.cmu.edu
28. http://www.cs.cmu.edu/~lenzo/
29. mailto:lenzo@cs.cmu.edu
30. http://www.lti.cs.cmu.edu/
31. http://www.valinux.com/
32. http://www.valinux.com/
Baum Engineering - GNOME logo
Product information
Name
Gnopernicus
Current Version
0.0.2
Operating system
Linux, Solaris
Language versions
English
Speech Synthesizers
Via Voice, Festival
Braille devices supported
DM80p, VARIO, VARIO20, VARIO40, VARIO80, ALVA 544
Sound Output Device
All sound cards
Gnopernicus information
[1]Product information
[2]Summary
[3]What is gnopernicus ?
[4]Gnopernicus architecture
[5]SRCore component
[6]SRUtil component
[7]SRLow component
[8]SRConf component
[9]Braille component
[10]Magnifier
[11]Speech
[12]Libke component
[13]Gnopi component
[14]BrlMon component
[15]Free software
[16]Download gnopernicus
[17]Dependencies
[18]GNOME libraries:
[19]Non-GNOME packages
[20]Using GNOME's CVS
[21]Building and installing/uninstalling gnopernicus
[22]Building gnopernicus
[23]Installing/uninstalling gnopernicus
[24]Using gnopernicus
[25]How to use gnopernicus (general)
[26]How to use gnopernicus application
[27]1. The main menu's features
[28]2. Current gnopernicus features mapping
[29]How to use brlmonitor
[30]How to use braille
[31]How to use magnifier
[32]How to use speech
[33]Screen Shots
[34]Development
[35]Reporting bugs
Summary
The "gnopernicus" project will enable users with limited vision, or no
vision, to use the Gnome 2 desktop and Gnome/GTK+-2 applications
effectively. By providing automated focus tracking and fullscreen
magnification, Gnopernicus will aid low-vision Gnome users, and its
screen reader features will allow low-vision and blind users access to
standard GTK+2 and Java-based GUI applications via speech and Braille
output. By leveraging Gnome 2's built-in accessibility framework,
Gnopernicus will make interacting with applications more efficient for
these users, and enable use of the Gnome 2 desktop for some users who
otherwise would have no access to Gnome.
______________________________________________________________________
What is gnopernicus?
Gnopernicus provides Assistive Technologies (AT) for blind and
visually impaired person. Gnopernicus is built from more modules,
which are shown in the following picture.
Gnopernicus architecture
[image004.jpg]
Figure 1. "gnopernicus" architecture
Note: The main architecture. (picture above has to be updated)
SRCore component
SRCore is the component of Gnopernicus Screen Reader, that gathers
information from all input sources, organize it and then present it to
the three outputs: Braille, Speech, Magnifier. It is also aware about
user settings and configuration, and notifies the other modules about
any change that occurs. Also, the user can use the braille displays
sensors, and SRCore knows how to react to this, and to offer the
requested information.
SRUtil component
SRUtil is designed to provide a uniform way to communicate between
modules. Modules are communicating one with other via events. This
module defines all event types that can appear and provides a
structure, which encapsulates all necessary dates for processing an
event.
SRLow component
SRLow component is module that listens all the systems events and
generates its own events as response to the user actions. For every of
generated events it provides information for the object with which
user interact. All these information let the user get a feedback from
the UI of an application.
SRConf component
It has a role of communication proxy between CORE and Gnopi. It make
possible that the two packages could be communicate with each other.
Braille component
The Braille component is a SO (shared object) which accepts input in
BML (Braille Markup Language, a XML dialect developed at Baum) and
many known Braille devices (currently just a couple of Baum devices
are supported). Braille is a medium, which allows a non-sighted person
to read text by touch, is also a method for writing tactile text. This
component makes a translation from a screen object in to the readable
Braille code set. The braille code is physically presented as raised
dots, usually arranged in cells of up to 6 dots. The module can be
configured from a Gnopi user interface.
Magnifier
Screen Magnifiers are assistive technologies that enable users with
low vision to enlarge the computer screen and interact with the
magnified portion of the screen they are accessing, such as menus,
toolbars, graphics, and text.
In the gnopernicus project the magnifier technology is offered through
the magnifier-named module. The magnifier can be used by user
(visually impaired) with the help of the GUI (Graphical User
Interface), SRCore being not just a proxy, but a logic component that
helps interaction between the two components and takes decisions in
how the information will be presented. At least one font smoothing
algorithm will be present in this component.
Speech
Screen readers are for people who are blind, but they can be useful
even to the visually impaired. These aids make on-screen information
available as synthesized speech or a refreshable Braille display. They
can only translate text-based information. Graphics can be translated
if there is alternative text describing the visual images.
The synthesized speech makes use of TTS (Text To Speech) Engines. TTS
is the creation of audible speech from computer readable text. The
information that is important for the blind user can be splited into
two parts (from the presentation point of view): some information can
be provided throw the Braille displays or can be spoken by an engine.
These parts can be combined for a better presentation.
In the gnopernicus project the speech feature of the Screen Reader is
offered through the speech-named module. In the following image it can
be seen the interaction with the other modules of gnopernicus: the
speech can be used by user (blind or even visually impaired) with the
help of the GUI (Graphic User Interface), SRCore being not just a
proxy, but a logic component that helps interaction between the two
components and takes decisions in how the information will be
presented.
Libke component
Libke contains the keylistener code. The key listener translates the
key or key-combinations to a string. There are three operation modes
available: letter mode, word mode and auto mode. At the moment it
listens only to normal characters and by default is set to auto mode.
The key listener settings can be changed via GConf by using either
gnopi or the test from SRConf.
Gnopi component
Gnopi is the configuration user interface for Gnopernicus. Like
functionality the component has a role to configure and to save the
own settings for a different component. The module is in GUI (Graphic
User Interface) package, and this module gives the executable file for
the whole Gnopernicus.
BrlMon component
It is the Braille device debugger and simulator. It shows in character
text format the list of symbols from Braille device. This component
makes part from GUI package. It works like a client/server program, at
which the client is the CORE and the server is the BrlMon.
______________________________________________________________________
Free software
gnopernicus is free; this means that everyone is free to use and
redistribute it on a free basis. gnopernicus is not in the public
domain; it is copyrighted and there are restrictions on its
distribution, but these restrictions are designed to permit everything
that a good cooperating citizen would want to do. What is not allowed
is to try to prevent others from further sharing any version of
gnopernicus that they might get from you. The precise conditions are
found in the GNU General Public License that comes with gnopernicus;
See License in COPYING file, in sources.
______________________________________________________________________
Download gnopernicus
Source is currently available via anonymous CVS, simply follow the
instructions from the next section or, for more details see
[36]http://developer.gnome.org/tools/cvs.html The module name is
"gnopernicus", but you will have to download several dependencies, too
(if you don't have GNOME2 installed)
Dependencies
In order to get gnopernicus installed on your system, you need to have
the following libraries installed as well:
GNOME libraries:
o cspi-1.0
o gconf-2.0
o gtk+-2.0
o gtk-doc (optional-necessary just for docs generation)
o libglade-2.0
o libgnome-2.0
o libgnomeui-2.0
o libxml-2.0
o gnome-speech
o gnome-mag (optional - if you don't install it, you will not
have magnifier support in gnopernicus; if you do, you will have
magnifier)
Non-GNOME packages
o [37]festival
o ViaVoice
You must have the GNOME libraries if you have GNOME2 installed, but if
you don't you will have to download and build the following GNOME
packages: at-spi, gconf, gtk+, [gtk-doc], libglade, libgnome,
libgnomeui, gnome-xml, gnome-speech, [gnome-mag]; these will provide
the libraries above.
Note : "[]" means optional.
Using GNOME's CVS
The goal of this step is to download the gnopernicus package and its
dependencies.
First you need to setup a few environmental variables. The first
command you need is:
$ export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'
You might want to put this in your login script. Then run the command:
$ cvs login
(There is no password, so just press `Return'.) You only need to run
this command once, not every time you access CVS.
Now grab the package(s) you need. Use something like this to pull for
the gnopernicus module:
$ cvs -z3 checkout gnopernicus or
$ cvs -z3 co gnopernicus
If you don't have the dependencies you can get it with a command like
this:
$ cvs -z3 co at-spi gconf gtk+ libglade libgnome libgnomeui gnome-xml gnome-spe
ech gnome-mag
Please use the -z3 option to minimize network bandwidth (-z9 eats too
much CPU time - please don't use it).
Now you will want to go through and build and install the packages.
After you have checked the code out, you can use:
$ cvs -z3 update -Pd gnopernicus
to update your personal copy of gnopernicus to the latest version from
the CVS server. So to have the latest of the above packages, just run
the command:
$ cvs -z3 update -Pd gnopernicus at-spi gconf gtk+ libglade libgnome libgnomeui
gnome-xml gnome-speech gnome-mag
and rebuild.
______________________________________________________________________
Building and installing/uninstalling gnopernicus
Building & Installing (summarize): run autogen.sh, make, make install
To compile gnopernicus on your system, you will need to take several
steps to setup the tree for compilation. First you have to set some
environment variables. You can use the following script, if you have
GNOME2 stack installed in "/opt/gnome2"(if you don't have it there
just modify the script). In the go_gnome script it is assumed that you
have automake, autoconfig and libtool installed in /usr/local, and the
other GNUTools (gettext and pkgconfig) in the GNOME stack. Note :
These GNUTools are needed for the configuration, compilation and
installation. Normally you will have them already installed in your
system. So, download the script [38]here and then run:
$ source go_gnome
You can do all steps that setup the tree for compilation at once by
running:
$ ./autogen.sh
Basically this does the following for you:
$ aclocal; automake; autoconf
The above commands create the "configure" script. Now you can run the
configure script to create all the Makefiles. Before running
autogen.sh or configure, make sure you have GNUTools in your path.
(GNUTools = automake, autoconf, libtool etc. For more information
visit [39]www.gnu.org)
Note that autogen.sh runs configure for you. If you wish to pass
options like--prefix=/opt/gnome-2.0 to configure you can give those
options to autogen.sh and they will be passed on to configure.
Read more about building/installation in the INSTALL file.
Building gnopernicus
Building implies :
$ autogen.sh--prefix=/directory_where_you_want_sources_installed
$ make
Note: If you have no prefix, you will need to make yourself root for
the installation phase. (You can become root by : su-)
Installing /uninstalling gnopernicus
In order to install the binaries you created in the previous step
(building), you'll have to type
$ make install
In order to uninstall the binaries you installed in the previous step:
$ make uninstall
______________________________________________________________________
Using gnopernicus
How to use gnopernicus (general)
After installation you can launch :
· gnopernicus
· srcore ( this is the same application but without GUI)
· brlmonitor
How to use gnopernicus application
1. The main menu's features
· General Settings. The user can activate or deactivate the
Speech, Magnifier and Braille output facilities.
· Speech Settings. Used to configure the Speech Engine. ( See
· Braille Settings. can set the type of Braille device, the
port number where the device is linked, we can select the specified
Braille translation table, or we can select the type of representation
on Braille device (dot7, dot78, dot8 or dotnone). You can also set to
have a device cursor in Braille.
· Magnifier Settings. Here we can create a new zoomer and set
different settings for zoomers from a list of zoomers.
· Keyboard Settings. Here we can set the kind of keyboard hook
(letter, word, auto or none) and we can also specify the active short
keys.
· User Properties. Here we will be associate different
commands with switches on Braille display, or with voice command.
· Language Settings. Here we will be set the language that
will be use Gnopernicus and the display language. This has not been
implemented yet.
· Load default Settings. We can load the default settings for
modules. We can do this without this menu, if we will lunch in
execution with "default" parameter.
· Minimize menu. This option minimizes the Gnopernicus menu.
Gnopernicus has gconf files where the user can set the IP (Internet
Protocol) address and the socket port numbers for Braille Monitor, for
the remote Braille device and for Gnopernicus. The user can also
specify if she/he wants to launch the Gnopernicus automatically
minimized or not. This can be done in the gconf file in
/$(home)/.gconf2/apps/gnopernicus/config section. To edit these files,
it can use gconf-editor application (can be downloaded from CVS : cvs
-z3 co gconf-editor). With this program the user can modify manually
the settings for different modules from gnopernicus. Note that this is
just for the development stage (such things will be configurable from
the GUI).
Note : for the moment the GUI functionality is :.
X- marks what works in the current stage
Gnopi Options Works
============= =====
1.General Settings
- Braille X
- Magnifier X
- Speech X
2.Speech settings
-Source
-Volume
-Priority
-Rate
-Pitch
-Preempt
3.Braille settings
3.1 Braille Device
- Device X
- Port
3.2 Transaltion Table
3.3 Cursor settings
3.4 Attribute settings
3.5 Braille fill char
3.6 Status cells
3.7 Position sensors X
3.8 Optical sensors X
4.Magnifier settings
5.Keyboard settings
- Mode X
- Delay Time X
- Key Categories X
6.User properties
7.Help
8.Load default settings
- Load Default Braille X
- Load Default Speech X
- Load Default Magnifier
- Load Default Keyboard X
- Load Default General X
- Load Default All X (without the magnifier settings)
9.Minimize menu X
0.Exit X
2. Current gnopernicus features mapping
Besides focus tracking, there is more functionality users should be
aware of:
2.1. Touch sensors reaction
The action that takes place when a touch sensor is pressed is working
according with the Gnopernicus configuration (Braille
Settings/Position Sensors dialog). As for now, these following actions
are available:
- mouse move
- mouse move and left click
- mouse move and right click
The text attributes are presented on speech all the time.
2.2. Keypad Layers
Gnopernicus functions are mapped on fixed keys on numeric keypad.
Because the number of keys on numeric keypad is limted, the "layer
concept" is introduced. That means that a key can have multiple
meanings, depending on which layer is the user is.
Now there are 11 layers available, from 0 to 10. To switch between
them you have to press 0 key from numeric keypad, folowed in 5 seconds
by the layer number, or DEL key for layer 10 (For laptops you can
access the keypad by pressing the "Fn" key. Example: for "8" from the
keypad - press "Fn" and "8", for "*" from keypad - press "Fn" and
"0").
NOTE: NumLock key must not be pressed!!!
If you don't press a layer number in 5 seconds, then gnopernicus will
not change the current layer.
For now, proposal mapped layers are:
(X --- means that this function is working)
(* --- this function is just mapped. It has no real effect)
(c --- use it carefully. Seems to have secondary effects)
LAYER 0: (most used functions)
LAYER 1: (navigation layer)
8 - goto parent X
2 - goto child X
4 - goto previous X
6 - goto next X
5 - repeat last presented object X
DEL - goto focused object X
7 - goto title X
9 - goto menubar X
1 - goto toolbar X
3 - goto statusbar X
LAYER 2: (mouse layer)
1 - left mouse press Xc
2 - left mouse click X
3 - left mouse release Xc
4 - middle mouse press Xc
5 - middle mouse click X
6 - middle mouse release Xc
7 - right mouse press Xc
8 - right mouse click X
9 - right mouse release Xc
LAYER 3:
LAYER 4:
LAYER 5:
LAYER 6:
LAYER 7: (magnifier layer)
6 - increase x factor X
4 - decrease x factor X
8 - increase y factor X
2 - decrease y factor X
7 - default setings
DEL - invert X (not supported in gnome-mag YET)
5 - toggle cursors type X (not supported in gnome-mag YET)
LAYER 8: (sppech layer)
1 - decrease volume X*
2 - default volume X*
3 - increase volume X*
4 - decrease rate X*
5 - default rate X*
6 - increase rate X*
7 - decrease pitch X*
8 - default pitch X*
9 - increase pitch X*
DEL - default settings X*
LAYER 9:
LAYER 10:
2.3. Repeat last utterance is also implemented, and it is mapped on
Left Shift key.
2.4. Shut up speech - mapped on Left Control key.
How to use brlmonitor
Execution:
brlmonitor [options]
Options:
-p --port=port_no UDP port number [1025 - 30000] (default 7000)
-l --line=line_no Number of line on display [line_no >= 2] (defau
lt 2)
-c --column=column_no Number of column in line [column_no >= 1] (def
ault 40)
-m --mode=modetype Display mode [normal|braille|dual]
normal - show with courier font
braille - show with braille font
dual - show with both font
Obs: line * column can not be bigger then 128 [128 - max cells on display]
Command keys:
CTRL-F Change edit mode (normal font, braille font, with both fonts)
CTRL-Q Exit application
F1 Help
How to use braille
In order to make gnopernicus to "command" your braille device, there
have to be rights, in your system, to access (read/write) the serial
port. In order to do that:
for Linux
$ su -
$ chmod 777 /dev/ttyS0
$ chmod 777 /dev/ttyS1
$ exit
for Solaris
$ su -
$ chmod 777 /cua/a
$ chmod 777 /cua/b
$ exit
How to use magnifier
How to use speech
Speech's main target is the blind person, so first of all it is
important that they can configure the product as they feel
comfortable. For this, our GUI is accessible, so when the user
launches gnopernicus application (simply type gnopernicus in the
command line) for the first time, a default voice will read the main
menu as the user starts key-navigation ( It is important to say that
blind people finds it hard or even impossible to use the mouse; we can
say that they use entirely the keybord). The reading is made with a
default setting : first it is read the name of the object that is
focused and then, with a different voice or different parameters of
the same voice, the role of the widget.
[image006.jpg]
Figure 2. The main menu of "gnopernicus"
The first menu item in the main menu is the General Settings. Entering
here (using the space key in a default Red Hat installation, which
runs a Sawfish window manager[40][1].) a submenu will allow the user
to select what assistive technologies needs: magnifier, braille and
speech. If the user were a visually impaired maybe he would like to
deactivate the speech; simply unchecking the Speech checkbox can do
this.
[image008.jpg]
Figure 3. General Settings dialog in "gnopernicus"
There is another menu, named "Speech settings" that is related to
speech configuration. Here can be chosen the engine, the choice being
made between ViaVoice, Festival and gnome-speech. There are other
parameters that can be set for the current speaking voice :
q Volume : how loud the voice will talk.
q Rate: as the name of the parameter says, it represents the
rate of the talking ( bigger the value is, more words will be read in
a time unit)
q Pitch
q Preempt
q Priority
[image010.jpg]
Figure 4. Speech settings dialog
______________________________________________________________________
Screen Shots
[41]Figure 1. "gnopernicus" architecture
[42]Figure 2. The main menu of "gnopernicus"
[43]Figure 3. General Settings dialog in "gnopernicus"
[44]Figure 4. Speech settings dialog
______________________________________________________________________
Development
[45]Speech development documentation
______________________________________________________________________
Reporting bugs
In order to report the bugs, please use the bugzilla tool,
[46]http://bugzilla.gnome.org. Before filing in a bug please read the
[47]Bug Writing HOWTO.
______________________________________________________________________
_______________________
[48][1] This note is important because different Linux Window Manger
behave different and even can be configurated in various ways. So
please check what are the shortcuts for this kind of actions. In the
future probably the Metacity window manager will be default in GNOME2
so there will be a standard.
References
1. http://www.baum.ro/gnopernicus.html#_Toc15444274
2. http://www.baum.ro/gnopernicus.html#_Toc15444275
3. http://www.baum.ro/gnopernicus.html#_Toc15444276
4. http://www.baum.ro/gnopernicus.html#_Toc15444277
5. http://www.baum.ro/gnopernicus.html#_Toc15444278
6. http://www.baum.ro/gnopernicus.html#_Toc15444279
7. http://www.baum.ro/gnopernicus.html#_Toc15444280
8. http://www.baum.ro/gnopernicus.html#_Toc15444281
9. http://www.baum.ro/gnopernicus.html#_Toc15444282
10. http://www.baum.ro/gnopernicus.html#_Toc15444283
11. http://www.baum.ro/gnopernicus.html#_Toc15444284
12. http://www.baum.ro/gnopernicus.html#_Toc15444285
13. http://www.baum.ro/gnopernicus.html#_Toc15444286
14. http://www.baum.ro/gnopernicus.html#_Toc15444287
15. http://www.baum.ro/gnopernicus.html#_Toc15444288
16. http://www.baum.ro/gnopernicus.html#_Toc15444289
17. http://www.baum.ro/gnopernicus.html#_Toc15444290
18. http://www.baum.ro/gnopernicus.html#_Toc15444291
19. http://www.baum.ro/gnopernicus.html#_Toc15444292
20. http://www.baum.ro/gnopernicus.html#_Toc15444293
21. http://www.baum.ro/gnopernicus.html#_Toc15444294
22. http://www.baum.ro/gnopernicus.html#_Toc15444295
23. http://www.baum.ro/gnopernicus.html#_Toc15444296
24. http://www.baum.ro/gnopernicus.html#_Toc15444297
25. http://www.baum.ro/gnopernicus.html#_Toc15444298
26. http://www.baum.ro/gnopernicus.html#_Toc15444299
27. http://www.baum.ro/gnopernicus.html#_Toc15444300
28. http://www.baum.ro/gnopernicus.html#_Toc15444301
29. http://www.baum.ro/gnopernicus.html#_Toc15444302
30. http://www.baum.ro/gnopernicus.html#_Toc15444303
31. http://www.baum.ro/gnopernicus.html#_Toc15444304
32. http://www.baum.ro/gnopernicus.html#_Toc15444305
33. http://www.baum.ro/gnopernicus.html#_Toc15444306
34. http://www.baum.ro/gnopernicus.html#_Toc15444307
35. http://www.baum.ro/gnopernicus.html#_Toc15444308
36. http://developer.gnome.org/tools/cvs.html
37. http://www.cstr.ed.ac.uk/projects/festival/download.html
38. http://www.baum.ro/gnopernicus_files/go_gnome
39. http://www.gnu.org/
40. http://www.baum.ro/gnopernicus.html#_ftn1
41. http://www.baum.ro/gnopernicus.html#_Toc15444417
42. http://www.baum.ro/gnopernicus.html#_Toc15444418
43. http://www.baum.ro/gnopernicus.html#_Toc15444419
44. http://www.baum.ro/gnopernicus.html#_Toc15444420
45. http://www.baum.ro/speech_dev.htm
46. http://bugzilla.gnome.org/
47. http://bugzilla.gnome.org/bug-HOWTO.html
48. http://www.baum.ro/gnopernicus.html#_ftnref1
--- End Message ---