Red Hat Bugzilla – Bug 589906
Default monospace font characters are overlapping in gnome-terminal
Last modified: 2013-06-17 00:07:07 EDT
Created attachment 412272 [details]
overlapping with monospace font
Description of problem:
Default monospace font characters are overlapping in gnome-terminal. The problem goes away with Dejavu-Sans-Mono.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Select any indic locale
3.observer shell prompt
character next to @ is overlapped with @.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
What *is* your default monospace font? It's supposed to be dejavu-sans-mono, AFAIK.
Created attachment 412427 [details]
Bill, System > Appearance > Font says:
gnome-terminal has the default "Used the system fixed width font" checked
Choosing DejaVu Sans and using any of those fonts does not fix this for me.
# rpm -qa | grep dejavu
James: that implies you don't have the proper monospace font installed. dejavu-sans-mono-fonts would be required. It's installed as part of the fonts group.
(In reply to comment #4)
> What *is* your default monospace font? It's supposed to be dejavu-sans-mono,
No, it is not. When I manually select Dejavu Sans Mono, this problem goes away.
Created attachment 412497 [details]
gnome terminal with Dejavu Sans Mono manually selected
Bill, Ok. I suppose the reason I tacked onto this report was because I did a next->next->next install and didn't have dejavu-sans-mono-fonts installed and as such had a font issue...
I'll try a fresh nightly install to make sure this is still the case.
I also did a "next->next->next" install of RHEL6, and also have the same issues. dejavu-sans-mono-fonts package includes a font that does not have the same overlap issues.
# rpm -qa | grep font | sort
What's the output of "fc-match Monospace"?
[pravi@savannah-test ~]$ fc-match "Monospace"
Meera_04.ttf: "Meera" "Regular"
[pravi@savannah-test ~]$ LANG=en_IN fc-match "Monospace"
DejaVuSansMono.ttf: "DejaVu Sans Mono" "Book"
Dejavu Sans Mono is currently set as default Monospace font only for en* locales.
So I would like to have it as default Monospace font for Malayalam, and possibly other Indic languages as well.
If a font package claims installs itself as the default font for monospace and it's NOT monospace, not my fault really...
pravi@savannah:~$ rpm -ql smc-meera-fonts
pravi@savannah:~$ cat /etc/fonts/conf.d/66-smc-meera.conf
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<edit name="family" mode="prepend">
Meera font claims it is only a sans-serif font, not a monospace font. So fault is not with the font also. Could it be an issue with fontconfig falling back to default font when it does not get a Monospace font for a language?
I'm not testing at all since I don't have any environments to confirm right now, but according to all of the information the above, I guess getting rid of "<family>Meera<?family>" for _monospace_ in 65-nonlatin.conf may fixes this issue.
Now we have the certain fontconfig config files. I'd suggest to drop 65-nonlatin.conf to avoid the unexpected behaviour.
false alarm. ignore my comment #15. actually it didn't help. fontconfig seems picking up Meera to satisfy the requirements anyway since Meera is only the font available on RHEL6 for Malayalam.
So my suggestion to get this fixed in a timely manner then is:
a) drop latin glyphs from Meera font
b) add DejaVu Sans Mono as the strong binding prior to Meera for Malayalam
c) add another Malayalam fonts not problematic for monospace if there are.
BTW b) gives us similar issue to Bug#589974.
Some of the Indian language fonts (like Lohit) does not contain latin glyphs, so it fall back to latin fonts. Can it be done for Monospace too?
If a language does not have a monospace font can it fall back to Dejavu Sans Mono (for latin glyphs)?
(In reply to comment #17)
> Some of the Indian language fonts (like Lohit) does not contain latin glyphs,
> so it fall back to latin fonts. Can it be done for Monospace too?
If we drop the latin glyphs from Meera, yes. and that's a) idea.
> If a language does not have a monospace font can it fall back to Dejavu Sans
> Mono (for latin glyphs)?
AFAICS no; at least on current implementation. this may be because trying to obtain the real font name with the language but not glyphs one requires. and may be hard to figure out all of requirements when requesting.
(In reply to comment #15)
> I'm not testing at all since I don't have any environments to confirm right
> now, but according to all of the information the above, I guess getting rid of
> "<family>Meera<?family>" for _monospace_ in 65-nonlatin.conf may fixes this
if i follow this step, it is taking Lohit Malayalam font for monospace
malayalam, and it is solving mentioned problem
in other words setting Lohit Malayalam as a defualt for monospace solves the problem
added strong binding for Dejavu Sans Mono
fixed in smc-fonts-04.2-9.el6
Created attachment 443228 [details]
currently Default behaviour of Terminal
tested package: smc-kalyani-fonts-04.2-11.el6.noarch
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.