unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: Caleb Herbert <csh@bluehome.net>, 39080@debbugs.gnu.org
Subject: bug#39080: How do language packs work?
Date: Fri, 10 Jan 2020 23:31:49 -0500	[thread overview]
Message-ID: <DFC7D28D-BCF0-4587-9A00-AB3B4ABF48DF@lepiller.eu> (raw)
In-Reply-To: <9f00b4c7-4c03-2114-d392-cfb31cc8803a@bluehome.net>

Le 10 janvier 2020 22:54:28 GMT-05:00, Caleb Herbert <csh@bluehome.net> a écrit :
>How do language packs work in Guix?  I would like to translate my
>future
>system to Pennsylvania Dutch.

Hi Caleb,

Thanks for your interest in localisation! I'm unfortunately unable to find a language code for your language. That is necessary for software to recognise it and speak it. I may not have searched correctly, so maybe you can find the correct code? Something like ll_LL (fr_BE for Belgium French) or maybe a code like ll-x-something (fr-x-gallo for a minority language in France that doesn't have its own iso-639 code, although I'm not sure it is technically accepted by software).

Once you have that code, you can use it in the guix system in the locale field of your os declaration. If you are on a foreign distro, then check with them how to set a language (or set $LANG temporarily).

If your question is how to help translating, and not just how to have software speak your language, you'll have to note that we do not translate any of the software we package, apart from guix itself: each package upstream is responsible for their translations.

To help translate guix, please have a look at the translation project: https://translation-project.org

To help translate other projects, you'll have to find what their process is to accept translations. Usually you can find this information by navigating from their home page, which you can find with the command `guix show the-package`.

In either case, there might already be a community of translators for your language. I encourage you to go and find them, they will probably have a lot of info, guidelines that will be very helpful to you.

I hope this answered some of your questions.

  reply	other threads:[~2020-01-11  4:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-11  3:54 bug#39080: How do language packs work? Caleb Herbert
2020-01-11  4:31 ` Julien Lepiller [this message]
2020-01-11  4:58   ` Caleb Herbert
2020-01-11 13:54     ` Julien Lepiller
2022-10-18 16:11       ` zimoun

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=DFC7D28D-BCF0-4587-9A00-AB3B4ABF48DF@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=39080@debbugs.gnu.org \
    --cc=csh@bluehome.net \
    /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).