From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?Q?Ludovic_Court=C3=A8s?= Subject: Re: Naming, hacking, and policies Date: Sun, 31 Mar 2019 18:37:42 +0200 Message-ID: <87imvzyp7t.fsf@gnu.org> References: <875zs3pg5b.fsf@ambrevar.xyz> <87wokhhj8n.fsf@nckx> <20190329151636.GA5681@jurong> <87wokh638t.fsf_-_@gnu.org> <502f27e8-00e7-8ca1-ba36-13d539b9eca3@zoho.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([209.51.188.92]:36867) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hAdSs-0005uy-Tj for guix-devel@gnu.org; Sun, 31 Mar 2019 12:37:47 -0400 In-Reply-To: <502f27e8-00e7-8ca1-ba36-13d539b9eca3@zoho.com> (sirgazil's message of "Sat, 30 Mar 2019 08:54:42 -0500") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: sirgazil Cc: guix-devel@gnu.org Hi sirgazil, sirgazil 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=E2=80=99s a tricky topic indeed (and not specific to Guix). There are i18n and accessibility (a11n) issues, I agree. The problem is that those =E2=80=9Csystem names=E2=80=9D are essentially identifiers, pret= ty much like Unix command names. Sometimes they=E2=80=99re abbreviations of common Engl= ish names, sometimes they=E2=80=99re 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=E2=80= =99t know how! Thanks, Ludo=E2=80=99.