From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: maxim.cournoyer@gmail.com, 26659@debbugs.gnu.org
Subject: bug#26659: [contact.ng0@cryptolab.net: Re: fonts bug in icecat?]
Date: Wed, 26 Apr 2017 14:29:06 -0700 [thread overview]
Message-ID: <CAN-vT6T++On+nRDvcx3riaizZBhGS9NyTHzgjQ9DMMhXqEundg@mail.gmail.com> (raw)
In-Reply-To: <20170426210509.6lzdmj5isiqbrooi@abyayala>
On Wed, Apr 26, 2017 at 2:05 PM, ng0 <contact.ng0@cryptolab.net> wrote:
[...]
>> >ng0 transcribed 1.1K bytes:
>> >> Were you (or someone else) able to reproduce this?
>>
>> I never got the Japanese fonts working on GuixSD by following our info manual, and this was before those updates.
>
> Can you tell me exactly or roughly what you tried and what errors (not specific, in general) you
> see in the current functioning system? It would be useful to get a clear view on
> languages / localization specific issues to improve the system.
I don't recall seeing any particular errors, I had simply followed
section 2.6.3 X11 Fonts [1] and installed the suggested fonts using:
"guix package -i font-adobe-source-han-sans:jp".
Japanese characters were still displayed as boxes (with unicode? in
them) in any software I tried following a system reboot (gnucash,
icecat, etc.).
[1]: https://www.gnu.org/software/guix/manual/guix.html
next prev parent reply other threads:[~2017-04-26 21:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-25 20:18 bug#26659: [contact.ng0@cryptolab.net: Re: fonts bug in icecat?] Leo Famulari
2017-04-25 20:52 ` ng0
2017-04-26 8:54 ` ng0
2017-04-26 17:17 ` Maxim Cournoyer
2017-04-26 21:05 ` ng0
2017-04-26 21:29 ` Maxim Cournoyer [this message]
2017-04-30 20:37 ` Chris Marusich
2017-04-30 20:47 ` ng0
2017-04-30 22:18 ` ng0
2017-04-30 22:28 ` ng0
2017-04-30 22:58 ` ng0
2017-05-08 17:22 ` Adonay Felipe Nogueira
2017-05-08 18:29 ` Adonay Felipe Nogueira
2017-05-08 18:34 ` Adonay Felipe Nogueira
2017-05-09 8:46 ` ng0
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=CAN-vT6T++On+nRDvcx3riaizZBhGS9NyTHzgjQ9DMMhXqEundg@mail.gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=26659@debbugs.gnu.org \
/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.