|
From: | sirgazil |
Subject: | Re: Naming, hacking, and policies |
Date: | Sun, 31 Mar 2019 13:03:56 -0500 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 |
El 31/03/19 a las 11:37 a. m., Ludovic Courtès escribió:
Hi sirgazil, sirgazil <address@hidden> 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.
Oh yeah, I'm not suggesting to translate "system names", but have both "system names" and "pretty names", and only the latter would be internationalized :)
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’.
-- Luis Felipe López Acevedo http://sirgazil.bitbucket.io/
[Prev in Thread] | Current Thread | [Next in Thread] |