From: sirgazil <sirgazil@zoho.com>
To: guix-devel@gnu.org
Subject: Re: Naming, hacking, and policies
Date: Sat, 30 Mar 2019 08:54:42 -0500 [thread overview]
Message-ID: <502f27e8-00e7-8ca1-ba36-13d539b9eca3@zoho.com> (raw)
In-Reply-To: <87wokh638t.fsf_-_@gnu.org>
El 29/03/19 a las 11:42 a. m., Ludovic Courtès escribió:
[...]
> Packages usually have a “system name” (that’s the terminology used on
> Savannah) and a “pretty name”, like ‘guix’ and ‘GNU Guix’. I believe
> the intent of those guidelines was to suggest keeping the system name,
> not the fancy name. Perhaps this is what should be clarified?
>
> Thanks,
> Ludo’.
A comment on the accessibility of names:
Last time I tried browsing packages in a GTK+ application on Debian
using a screen reader, I didn't like the experience. The screen reader
read in Spanish (my system language) all the names of the packages, most
of them in "system name" format and made of English words. No good.
Also, if I recall correctly, the screen reader didn't read initialisms
correctly.
I bet there are things to improve in screen readers, accessibility of
GUI toolkits, and package definitions. At that time, for example, Orca
could not read multilingual HTML documents that used explicitly the LANG
attribute in elements. I don't know if GTK+ offers something similar to
the HTML LANG attribute for GUI components. Package definitions I've
seen don't indicate in which language a package name is written so that
a screen reader could switch its voice if necessary, nor they provide a
way to know if a package name is an initialism, so that the screen
reader can read it as such.
I don't know exactly what should be done in Guix, though, but I think
having a "system name" and a "pretty name" that is translatable could
help a little bit.
I hope libre screen readers get so smart they will figure all these
things by themselves :)
My 2¢
--
Luis Felipe López Acevedo
http://sirgazil.bitbucket.io/
next prev parent reply other threads:[~2019-03-30 13:56 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190326131842.7363.84034@vcs0.savannah.gnu.org>
[not found] ` <20190326131845.1B177209E3@vcs0.savannah.gnu.org>
2019-03-26 14:54 ` 06/15: gnu: wesnoth-server: Rename package to the-battle-for-wesnoth-server Tobias Geerinckx-Rice
2019-03-26 14:20 ` Pierre Neidhardt
2019-03-26 15:18 ` Ricardo Wurmus
2019-03-26 15:32 ` Pierre Neidhardt
2019-03-26 17:53 ` Andreas Enge
2019-03-26 18:25 ` Pierre Neidhardt
2019-03-27 11:11 ` Ludovic Courtès
2019-03-27 11:36 ` Pierre Neidhardt
[not found] ` <20190326131844.C73EC209E3@vcs0.savannah.gnu.org>
2019-03-27 11:07 ` 05/15: gnu: wesnoth: Rename package to the-battle-for-wesnoth Ludovic Courtès
2019-03-27 11:46 ` Pierre Neidhardt
2019-03-27 13:20 ` swedebugia
2019-03-27 15:00 ` Ricardo Wurmus
2019-03-27 16:42 ` Pierre Neidhardt
2019-03-28 7:59 ` Ricardo Wurmus
2019-03-28 8:09 ` Pierre Neidhardt
2019-03-29 13:27 ` swedebugia
2019-03-27 15:15 ` Ludovic Courtès
2019-03-27 18:34 ` Tobias Geerinckx-Rice
2019-03-27 18:26 ` Pierre Neidhardt
2019-03-27 18:44 ` Daniel Jiang
2019-03-27 21:15 ` Tobias Geerinckx-Rice
2019-03-28 8:17 ` Pierre Neidhardt
2019-03-29 14:02 ` Tobias Geerinckx-Rice
2019-03-29 15:16 ` Andreas Enge
2019-03-29 16:42 ` Naming, hacking, and policies Ludovic Courtès
2019-03-29 19:23 ` Ricardo Wurmus
2019-03-31 16:33 ` Ludovic Courtès
2019-03-30 13:54 ` sirgazil [this message]
2019-03-31 16:37 ` Ludovic Courtès
2019-03-31 18:03 ` sirgazil
2019-03-31 20:31 ` Ludovic Courtès
2019-03-31 22:59 ` sirgazil
2019-04-01 0:07 ` Tobias Geerinckx-Rice
2019-03-29 19:57 ` 05/15: gnu: wesnoth: Rename package to the-battle-for-wesnoth swedebugia
2019-03-27 15:13 ` Ludovic Courtès
2019-03-27 16:25 ` Pierre Neidhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=502f27e8-00e7-8ca1-ba36-13d539b9eca3@zoho.com \
--to=sirgazil@zoho.com \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.