From: "Ludovic Courtès" <ludo@gnu.org>
To: sirgazil <sirgazil@zoho.com>
Cc: guix-devel@gnu.org
Subject: Re: Naming, hacking, and policies
Date: Sun, 31 Mar 2019 18:37:42 +0200 [thread overview]
Message-ID: <87imvzyp7t.fsf@gnu.org> (raw)
In-Reply-To: <502f27e8-00e7-8ca1-ba36-13d539b9eca3@zoho.com> (sirgazil's message of "Sat, 30 Mar 2019 08:54:42 -0500")
Hi sirgazil,
sirgazil <sirgazil@zoho.com> skribis:
> 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.
It’s a tricky topic indeed (and not specific to Guix).
There are i18n and accessibility (a11n) issues, I agree. The problem is
that those “system names” are essentially identifiers, pretty much like
Unix command names. Sometimes they’re abbreviations of common English
names, sometimes they’re proper names, etc. So not all of them are
subject to translation. I think they should really be treated like
identifiers in programming languages or command names.
Now, having synopses and descriptions that are actual text subject to
translation certainly helps. Maybe we could do better, but I wouldn’t
know how!
Thanks,
Ludo’.
next prev parent reply other threads:[~2019-03-31 16:37 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
2019-03-31 16:37 ` Ludovic Courtès [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87imvzyp7t.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=sirgazil@zoho.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).