unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <contact.ng0@cryptolab.net>
To: Chris Marusich <cmmarusich@gmail.com>,
	Maxim Cournoyer <maxim.cournoyer@gmail.com>,
	26659@debbugs.gnu.org
Subject: bug#26659: [contact.ng0@cryptolab.net: Re: fonts bug in icecat?]
Date: Sun, 30 Apr 2017 22:18:11 +0000	[thread overview]
Message-ID: <20170430221811.dgum3c72fioplm2v@abyayala> (raw)
In-Reply-To: <20170430204722.jdkxylyjn535cvku@abyayala>

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

Well it is worse than icecat now that I have removed every WM/DM but Xfce4.

Most applications still display text, but libreoffice can be seen in the appended screenshot.
ng0 transcribed 3.4K bytes:
> Chris Marusich transcribed 237K bytes:
> > ng0 <contact.ng0@cryptolab.net> writes:
> > 
> > > Here is a visual display of some fonts: https://ptpb.pw/EQfV.png
> > >
> > > This is either related to icecat changes or to changes with font
> > > related packages.
> > 
> > The same page (presumably http://www.bbc.com/) renders fine for me; no
> > boxes, all glyphs appear to be rendered correctly.  In addition, system
> > fonts appear to be selectable for me in icecat.  See attached files for
> > screenshots.
> 
> Well this is odd. And you run GuixSD I assume? I wonder where the source for
> fonts being suddenly AWOL lies.
> I remember that they used to work.
> 
> > I have not run 'guix pull' in the last week or two.  Would you like me
> > to tell you anything about my system's configuration that might shed
> > light on the issue?  I'm going to update my system later today, so if
> > there are any problems (or not), I'll let you know.
> 
> Yes, that would be useful.
> 
> > Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
> > 
> > > 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
> > 
> > FWIW, Japanese fonts work for me in all applications I have tried so
> > far, which includes Icecat, GNOME terminal, graphical emacs, and Gedit,
> > all on GNOME.  I don't recall doing anything that wasn't described in
> > the manual.
> > 
> > If you're interested in troubleshooting it, I'd like to help you get
> > Japanese fonts working.  For starters, maybe this information will help:
> > 
> > --8<---------------cut here---------------start------------->8---
> > $ guix package --list-installed | grep font
> > font-gnu-freefont-ttf	20120503	out	/gnu/store/4yk3w5yk8rn2cxzw2kq3ih7l515cy32d-font-gnu-freefont-ttf-20120503
> > font-inconsolata	0.80	out	/gnu/store/pd23zma09d50ssdww2a3v5xjaafxc8pm-font-inconsolata-0.80
> > font-liberation	2.00.1	out	/gnu/store/2wp4n6nvzhs9i6cj5c760x3s4xk3lhrk-font-liberation-2.00.1
> > font-adobe-source-han-sans	1.004	out	/gnu/store/44kyy0nlm2jap3z60gh1bq9s4gpkq3mi-font-adobe-source-han-sans-1.004
> > font-terminus	4.40	out	/gnu/store/l59m8b44dyiydgf6i3ckgwafdxi2zllw-font-terminus-4.40
> > font-dejavu	2.37	out	/gnu/store/bs8ky224vljlclrv547k4alz7386lawi-font-dejavu-2.37
> > gs-fonts	8.11	out	/gnu/store/z0as6gp6grsqs4a8knbxkcwbyxriqmgc-gs-fonts-8.11
> > --8<---------------cut here---------------end--------------->8---
> > 
> > I see that I am not using the "jp" output of font-adobe-source-han-sans;
> > perhaps you can try again using the "out" output?
> > 
> > -- 
> > Chris
> 
> 
> 
> 
> 
> 
> -- 
> https://pragmatique.xyz
> PGP: https://people.pragmatique.xyz/ng0/

-- 
https://pragmatique.xyz
PGP: https://people.pragmatique.xyz/ng0/

[-- Attachment #2: libreoffice-bad-fonts.png --]
[-- Type: image/png, Size: 74810 bytes --]

  reply	other threads:[~2017-04-30 22:19 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
2017-04-30 20:37           ` Chris Marusich
2017-04-30 20:47             ` ng0
2017-04-30 22:18               ` ng0 [this message]
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

  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=20170430221811.dgum3c72fioplm2v@abyayala \
    --to=contact.ng0@cryptolab.net \
    --cc=26659@debbugs.gnu.org \
    --cc=cmmarusich@gmail.com \
    --cc=maxim.cournoyer@gmail.com \
    /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).