all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Caleb Herbert <csh@bluehome.net>
To: Julien Lepiller <julien@lepiller.eu>, 39080@debbugs.gnu.org
Subject: bug#39080: How do language packs work?
Date: Fri, 10 Jan 2020 22:58:35 -0600	[thread overview]
Message-ID: <3ab56e6a-b5b9-cf9c-5d91-113cdbb14395@bluehome.net> (raw)
In-Reply-To: <DFC7D28D-BCF0-4587-9A00-AB3B4ABF48DF@lepiller.eu>

[-- Attachment #1: Type: text/plain, Size: 925 bytes --]

On 1/10/20 10:31 PM, Julien Lepiller wrote:
> 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?

pdc

Examples:
https://pdc.wikipedia.org/wiki/Haaptblatt
https://www.jw.org/pdc/
https://iso639-3.sil.org/code/pdc

> 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).

I highly doubt a locale file for pdc_US exists.  I'd like to make one,
but the file for en_US and yi_US don't show the actual characters.  I
just see "<U####>", which I can't read or produce.

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

Thanks.

[-- Attachment #2: csh.vcf --]
[-- Type: text/x-vcard, Size: 288 bytes --]

begin:vcard
fn:Caleb Herbert
n:Herbert;Caleb
adr:;;PO box 234;East Lynne;Missouri;64743;United States of America
email;internet:csh@bluehome.net
tel;home:816-869-3111
tel;cell:816-892-9669
note:KE0VVT
x-mozilla-html:FALSE
url:https://bluehome.net/csh/
version:2.1
end:vcard


  reply	other threads:[~2020-01-11  4:59 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
2020-01-11  4:58   ` Caleb Herbert [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3ab56e6a-b5b9-cf9c-5d91-113cdbb14395@bluehome.net \
    --to=csh@bluehome.net \
    --cc=39080@debbugs.gnu.org \
    --cc=julien@lepiller.eu \
    /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.