You are not logged in.
Hi,
I'm having trouble displaying Japanese characters in the mate-terminal.
Using my other builds of Linux (Sabayon and Fedora) I just needed to install the VLgothic and Monospace fonts in order to get them working.
I can't seem to find them in Arch however?
The: https://wiki.archlinux.org/index.php/Fonts guide also talks about them but doesn't instruct on how to install them....
pacman -Ss vlgothic - or similardoesn't show anything either.
I've attempted to use the terminus-fonts package and added the respective dir to my xorg.conf:
# cat 10-fonts.conf
# Let X.Org know about the custom font directories
Section "Files"
FontPath "/usr/share/fonts/100dpi"
FontPath "/usr/share/fonts/75dpi"
FontPath "/usr/share/fonts/cantarell"
FontPath "/usr/share/fonts/cyrillic"
FontPath "/usr/share/fonts/encodings"
FontPath "/usr/share/fonts/local"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/truetype"
FontPath "/usr/share/fonts/TTF"
FontPath "/usr/share/fonts/util"
FontPath "/usr/share/fonts/local"
EndSectionbut unfortunately that didn't work either, nor did adding the path to 'xset' in the '.xinitrc' file :-(
Would someone be able to help out on this?
Unless I manually have to transfer the .ttf files into the .../fonts/TTF directory...?
Thanks
Last edited by JohnnySSH (2013-05-19 06:23:19)
Offline
If something's not in the official repos, check the AUR: https://aur.archlinux.org/packages/ttf-vlgothic/
Offline
Thanks karol:
have looked at this:
https://wiki.archlinux.org/index.php/Ar … Repository
which then led to adding this into pacman.conf
[community]
Include = /etc/pacman.d/mirrorlistIs that the way to enable the AUR repo??
Or more Google'ing came up with this:
https://wiki.archlinux.org/index.php/Un … positories
so perhaps the top suggestion to a font repo?
Last edited by JohnnySSH (2013-05-16 15:55:57)
Offline
AUR and [community] are different things, pacman doesn't support AUR.
AUR doesn't contain prebuilt binary packages, it provides PKGBUILDs that can be used to build packages. You have to carefully read the article, https://wiki.archlinux.org/index.php/Ar … mmunity.5D talks about the difference between AUR and [community].
Offline
Hmm I see so it's more of a "user ports" based system....
Sorry for being a bit slow, just getting used to the distro :-)
Offline
Hi,
VLgothic font is available in the AUR (Arch User (or Unofficial) Repository) as ttf-vlgothic. The AUR has several monospace fonts as well.
From the AUR you can download tarballs ('taurballs'), each of which contains a PKGBUILD and possibly some other files, which allow you to build your own packages.
For help with building packages from the AUR, please follow this link.
Have a look at the .install files in the 'taurballs' for these fonts, you will find out how to correctly add any other fonts not in Arch or the AUR to your system.
Make sure to undo any (non-working) changes you made to your xorg.conf before installing, and everything should be fine. If not, let us know ;-)
Last edited by ackalker (2013-05-16 16:03:47)
Offline
Well the font package turned out to be a bunch of ttf's so I manually copied them to /usr/share/fonts/TTF/
I didn't see any 'build' specific files in order to create a package with. Just a bunch of unreadable README files (as need fonts that I don't have).
Am gona see if this works now.
Offline
You should use packages and PKGBUILDs instead of simply copying files or running 'make && make install' because pacman doesn't like files it doesn't know about and will throw errors if you later install package that provides the files you've just copied, see 'FILENAME exists in Filesystem' part: https://bbs.archlinux.org/viewtopic.php?id=130138
It's also easier to maintain a package in the long run - you run makepkg or use pacman and that's it :-)
Offline
Ah, I guess you downloaded the file listed under 'Sources'.
If you want to build a package (which you can then install and uninstall using pacman), you should choose "Download tarball" under "Package Actions", top right.
Last edited by ackalker (2013-05-16 16:23:38)
Offline
Oh oops!
I also tried to copy the fonts from my Sabayon build and run:
$ fc-cache -vfbut that didn't work either?
I'll try doing things the 'proper' way now and see if it takes effect.
Offline
Ok finally done things the proper way however, the fonts are still showing up as # symbols? - maybe I just need a different font?
Offline
Well that was weird??
I just installed all the fonts here:
Japanese
otf-ipafont - Formal style Japanese Gothic (sans-serif) and Mincho (serif) fonts set; one of the highest quality open source font. Default of openSUSE-ja. (AUR)
ttf-vlgothic - Japanese Gothic fonts. Default of Debian/Fedora/Vine Linux (AUR)
ttf-mplus - Modern Gothic style Japanese outline fonts. It includes all of Japanese Hiragana/Katakana, Basic Latin, Latin-1 Supplement, Latin Extended-A, IPA Extensions and most of Japanese Kanji, Greek, Cyrillic, Vietnamese with 7 weights (proportional) or 5 weights (monospace). (AUR)
ttf-ipa-mona, ttf-monapo - Japanese fonts to show 2channel Shift JIS art properly. (AUR)
ttf-sazanami - Japanese free TrueType font. This is outdated and not maintained any more, but may be defined as a fallback font on several environments. which automatically configures the font cache however, when run mate-terminal with Japanese kanji style fonts; the terminal still shows a bunch of #### signs where the Kanji should be displayed?
Now I'm lost :-S
Offline
Have you tried other terminals?
Offline
Hmm... no just the mate-term as that's the one I primraily use.
I know for a fact that it works as on other distros the characters display fine using the same terminal - I'm also running MATE version 1.6.0 on that distro too.
I could try xterm though, somehow it's either just a way of telling MATE, Xorg, or the Shell where the font files are .....I think!
Just checked with Xterm and Aterm but no luck :-(
Had a look here too:
http://home.roadrunner.com/~computertai … ninpt.html
which mentioned to install some new fonts from offiicial repos but still doesn't work; even while testing on vty2 (ctrl + atl + 2) - I'm at a loss!!
Last edited by JohnnySSH (2013-05-16 17:46:25)
Offline
I found the solution!!!
http://bitprison.net/gnome-terminal_cha … ding_utf-8
Add:
LANG="en_US.UTF-8"
LC_ALL="en_US.UTF-8"To the /etc/environment file. or whatever correspondng locale is desired.
The tell tail clue was that mate-term should have been starting up with locale set to UTF-8 unicode but instead was coming out with ANSI.....
Now I've got 2x UTF-8 shown in the term but at least the proper fonts are showing now :-)
Thanks everyone :-)
Last edited by JohnnySSH (2013-05-16 17:58:44)
Offline