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

Bug#616397: marked as done (release-notes: Add an essential note for accessibility issues with charset different than UTF8 on Gnome)

Your message dated Sat, 26 Jan 2013 16:27:31 +0100
with message-id <20130126152731.GH28924@beskar.mdcc.cx>
and subject line Bug #616397: release-notes: Add an essential note for accessibility issues with charset different than UTF8 on Gnome
has caused the Debian Bug report #616397,
regarding release-notes: Add an essential note for accessibility issues with charset different than UTF8 on Gnome
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
616397: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616397
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release-notes
Severity: grave
Justification: renders package unusable


Hi,

I suggest you to add to the release notes the following paragraph. It is 
essential, because without such info, Gnome is not usable anymore for a blind 
people and the upgrade becomes a bad experience.

"4.5.8.2. gnome-orca (accessibility section)

gnome-orca is a screen reader which allows sight impaired users to access to the
GUI interface and the GNOME desktop environment. 

The users of this package should be aware of the fact that there is an important change between gnome
suite release 2.22 and 2.30. Indeed, gnome-orca is unable to read and analysing
the desktop and the window manager window (i.e. nautilus or gnome-panel) if you do not use a UTF-8 charset. It means that if you are not using the UTF-8 charset, gnome-orca will not read at all the menu at which you access to via alt-F1 or the desktop (alt-ctrl-d), or the Run bar (alt-F2). It can read other applications such as iceweasel or gnome-terminal, but it is not perfectly optimal (e.g. alt-tab is very slow with gnome-orca).

To workaround the issue, you must do, as root user, dpkg-reconfigure locale and choose the locale for your language which handles UTF-8 by default. Then, reboot the system so that the change would produce an effect."

Hope it will help. I submitted a bug about this, documented by a11y team. I 
repeat, but it's very important, because before this, I considered squeeze
unusable for blind people in graphic interface.

Regards,




-- System Information:
Debian Release: 5.0.8
  APT prefers oldstable
  APT policy: (500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-bpo.5-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR@euro, LC_CTYPE=fr_FR@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

--- End Message ---
--- Begin Message --- 
Hi,

Thanks for reporting this issue. I've just applied this patch:

-------

Index: en/old-stuff.dbk
===================================================================
--- en/old-stuff.dbk    (revision 9554)
+++ en/old-stuff.dbk    (working copy)
@@ -99,7 +99,12 @@
 The Nautilus file manager (and all glib-based programs, and likely all Qt-based
 programs too) assume that filenames are in UTF-8, while the shell assumes they
 are in the current locale’s encoding. In daily use, non-ASCII filenames are
-just unusable in such setups.</para></footnote> identified that manifest itself
+just unusable in such setups.
+Furthermore, the gnome-orca screen reader (which grants sight-impaired users
+access to the GNOME desktop environment) requires a UTF-8 locale since Squeeze;
+under a legacy characterset, it will be unable to read out window information
+for desktop elements such as Nautilus/GNOME Panel or the Alt-F1
+menu.</para></footnote> identified that manifest itself
 only when using a non-UTF-8 locale. On the desktop, such legacy locales are
 supported through ugly hacks in the libraries internals, and we cannot decently
 provide support for users who still use them.

----

Thanks, Bye,

Joost

--- End Message ---
Reply to: