https://wiki.archlinux.org/api.php?action=feedcontributions&user=Jgwak&feedformat=atomArchWiki - User contributions [en]2024-03-29T06:24:39ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Fonts&diff=565033Fonts2019-01-28T10:04:17Z<p>Jgwak: New Korean fonts</p>
<hr />
<div>[[Category:Fonts]]<br />
[[cs:Fonts]]<br />
[[de:Schriftarten]]<br />
[[es:Fonts]]<br />
[[it:Fonts]]<br />
[[ja:フォント]]<br />
[[ru:Fonts]]<br />
[[zh-hans:Fonts]]<br />
[[zh-hant:Fonts]]<br />
{{Related articles start}}<br />
{{Related|Font configuration}}<br />
{{Related|Linux console#Fonts}}<br />
{{Related|Java Runtime Environment fonts}}<br />
{{Related|Metric-compatible fonts}}<br />
{{Related|Microsoft fonts}}<br />
{{Related articles end}}<br />
<br />
From [[Wikipedia:Computer font]]: "A computer font (or font) is an electronic data file containing a set of glyphs, characters, or symbols such as dingbats."<br />
<br />
Note that certain font licenses may impose some legal limitations.<br />
<br />
== Font formats ==<br />
<br />
Most computer fonts used today are in either ''bitmap'' or ''outline'' data formats. <br />
;Bitmap fonts: Consist of a matrix of dots or pixels representing the image of each glyph in each face and size.<br />
;Outline or ''vector'' fonts: Use Bézier curves, drawing instructions and mathematical formulae to describe each glyph, which make the character outlines scalable to any size.<br />
<br />
=== Bitmap formats ===<br />
<br />
* [[Wikipedia:Glyph Bitmap Distribution Format|Bitmap Distribution Format]] (BDF) by Adobe<br />
* [[Wikipedia:Portable Compiled Format|Portable Compiled Format]] (PCF) by Xorg<br />
* [[Wikipedia:PC Screen Font|PC Screen Font]] (PSF) used by the Kernel for console fonts, not supported by Xorg (for Unicode PSF files the extension is {{ic|psfu}})<br />
<br />
These formats can also be gzipped. See [[#Bitmap]] for the available bitmap fonts.<br />
<br />
=== Outline formats ===<br />
<br />
* [[Wikipedia:PostScript fonts|PostScript fonts]] by Adobe – has various formats, e.g: Printer Font ASCII (PFA) and Printer Font Binary (PFB)<br />
* [[Wikipedia:TrueType|TrueType]] by Apple and Microsoft (file extension: {{ic|ttf}})<br />
* [[Wikipedia:OpenType|OpenType]] by Microsoft, built on TrueType (file extensions: {{ic|otf}}, {{ic|ttf}})<br />
<br />
For most purposes, the technical differences between TrueType and OpenType can be ignored.<br />
<br />
=== Other formats ===<br />
<br />
The typesetting application, ''TeX,'' and its companion font software, ''Metafont,'' render characters using their own methods. Some of the file extensions used for fonts by these two programs are {{ic|*pk}}, {{ic|*gf}}, {{ic|mf}} and {{ic|vf}}.<br />
<br />
[https://fontforge.github.io/en-US/ FontForge] ({{Pkg|fontforge}}), a font editing application, can store fonts in its native text-based format, {{ic|sfd}}, ''s''pline ''f''ont ''d''atabase.<br />
<br />
The [http://www.w3.org/TR/SVG/fonts.html SVG] format also has its own font description method.<br />
<br />
== Installation ==<br />
<br />
There are various methods for installing fonts.<br />
<br />
=== Pacman ===<br />
<br />
Fonts and font collections in the enabled repositories can be installed using [[pacman]].<br />
<br />
Available fonts may be found by [[pacman#Querying package databases|querying packages]] (e.g. for {{ic|font}} or {{ic|ttf}}).<br />
<br />
=== Creating a package ===<br />
<br />
You should give pacman the ability to manage your fonts, which is done by creating an Arch package. These can also be shared with the community in the [[AUR]]. The packages to install fonts are particularly similar; simply taking an existing [https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/adobe-source-code-pro-fonts package] as template should work well. To learn about how to modify it for your font, please refer to [[Creating packages]].<br />
<br />
The family name of a font file can be aquired with the use of {{ic|fc-query}} for example: {{ic|fc-query -f '%{family[0]}\n' /path/to/file}}. The formatting is described in the FcPatternFormat(3) manual.<br />
<br />
=== Manual installation ===<br />
<br />
The recommended way of adding fonts that are not in the repositories to your system is described in [[#Creating a package]]. This gives pacman the ability to remove or update them at a later time. Fonts can alternately be installed manually as well.<br />
<br />
To install fonts system-wide (available for all users), move the folder to the {{ic|/usr/share/fonts/}} directory. The files need to be readable by every user, use [[chmod]] to set the correct permissions (i.e. at least {{ic|0444}} for files and {{ic|0555}} for directories). To install fonts for only a single user, use {{ic|~/.local/share/fonts}} ({{ic|~/.fonts/}} is now deprecated).<br />
<br />
For Xserver to load fonts directly (as opposed to the use of a ''font server'') the directory for your newly added font must be added with a FontPath entry. This entry is located in the ''Files'' section [[Xorg#Configuration|of your Xorg configuration file]] (e.g. {{ic|/etc/X11/xorg.conf}} or {{ic|/etc/xorg.conf}}). See [[#Older applications]] for more detail.<br />
<br />
Then update the fontconfig font cache: (usually unnecessary as software using the fontconfig library does this)<br />
<br />
$ fc-cache<br />
<br />
=== Older applications ===<br />
<br />
With older applications that do not support fontconfig (e.g. GTK+ 1.x applications, and {{ic|xfontsel}}) the index will need to be created in the font directory:<br />
<br />
$ mkfontscale<br />
$ mkfontdir<br />
<br />
Or to include more than one folder with one command:<br />
<br />
$ for dir in /font/dir1/ /font/dir2/; do xset +fp $dir; done && xset fp rehash<br />
<br />
Or if fonts were installed in a different sub-folders under the e.g. {{ic|/usr/share/fonts}}:<br />
<br />
$ for dir in * ; do if [ -d "$dir" ]; then cd "$dir";xset +fp "$PWD" ;mkfontscale; mkfontdir;cd .. ;fi; done && xset fp rehash<br />
<br />
At times the X server may fail to load the fonts directory and you will need to rescan all the {{ic|fonts.dir}} files:<br />
<br />
# xset +fp /usr/share/fonts/misc # Inform the X server of new directories<br />
# xset fp rehash # Forces a new rescan<br />
<br />
To check that the font(s) is included:<br />
<br />
$ xlsfonts | grep fontname<br />
<br />
{{note|Many packages will automatically configure Xorg to use the font upon installation. If that is the case with your font, this step is not necessary.}}<br />
<br />
This can also be set globally in {{ic|/etc/X11/xorg.conf}} or {{ic|/etc/X11/xorg.conf.d}}.<br />
<br />
Here is an example of the section that must be added to {{ic|/etc/X11/xorg.conf}}. Add or remove paths based on your particular font requirements.<br />
<br />
# Let X.Org know about the custom font directories<br />
Section "Files"<br />
FontPath "/usr/share/fonts/100dpi"<br />
FontPath "/usr/share/fonts/75dpi"<br />
FontPath "/usr/share/fonts/cantarell"<br />
FontPath "/usr/share/fonts/cyrillic"<br />
FontPath "/usr/share/fonts/encodings"<br />
FontPath "/usr/share/fonts/misc"<br />
FontPath "/usr/share/fonts/truetype"<br />
FontPath "/usr/share/fonts/TTF"<br />
FontPath "/usr/share/fonts/util"<br />
EndSection<br />
<br />
=== Pango Warnings ===<br />
<br />
When [http://www.pango.org/ Pango] is in use on your system it will read from [http://www.freedesktop.org/wiki/Software/fontconfig fontconfig] to sort out where to source fonts.<br />
<br />
(process:5741): Pango-WARNING **: failed to choose a font, expect ugly output. engine-type='PangoRenderFc', script='common'<br />
(process:5741): Pango-WARNING **: failed to choose a font, expect ugly output. engine-type='PangoRenderFc', script='latin'<br />
<br />
If you are seeing errors similar to this and/or seeing blocks instead of characters in your application then you need to add fonts and update the font cache. This example uses the {{Pkg|ttf-liberation}} fonts to illustrate the solution (after successful installation of the package) and runs as root to enable them system-wide.<br />
<br />
# fc-cache<br />
/usr/share/fonts: caching, new cache contents: 0 fonts, 3 dirs<br />
/usr/share/fonts/TTF: caching, new cache contents: 16 fonts, 0 dirs<br />
/usr/share/fonts/encodings: caching, new cache contents: 0 fonts, 1 dirs<br />
/usr/share/fonts/encodings/large: caching, new cache contents: 0 fonts, 0 dirs<br />
/usr/share/fonts/util: caching, new cache contents: 0 fonts, 0 dirs<br />
/var/cache/fontconfig: cleaning cache directory<br />
fc-cache: succeeded<br />
<br />
You can test for a default font being set like so:<br />
<br />
# fc-match<br />
LiberationMono-Regular.ttf: "Liberation Mono" "Regular"<br />
<br />
== Font packages ==<br />
<br />
This is a selective list that includes many font packages from the [[AUR]] along with those in the official repositories. Fonts are tagged "Unicode" if they have wide Unicode support, see the project or <br />
Wikipedia pages for detail.<br />
<br />
The [https://github.com/ternstor/distrofonts Archfonts Python script] can be used to generate an overview of all the TTF fonts found in the official repositories / the AUR (the image generation is done using {{AUR|ttf2png}}).<br />
<br />
=== Bitmap ===<br />
<br />
* Default 8x16<br />
* [http://www.dcmembers.com/jibsen/download/61/ Dina] ({{Pkg|dina-font}}) – 6pt, 8pt, 9pt, 10pt, monospaced, based on Proggy<br />
* [http://openlab.jp/efont/unicode/ Efont] ({{AUR|efont-unicode-bdf}}) – 10px, 12px, 14px, 16px, 24px, normal, bold and italic<br />
* [http://font.gohu.org/ Gohu] ({{AUR|gohufont}}) – 11px, 14px, normal and bold<br />
* [http://artwizaleczapka.sourceforge.net/ Lime] ({{Pkg|artwiz-fonts}})<br />
* [http://tobiasjung.name/profont/ ProFont] ({{Pkg|profont}}{{Broken package link|package not found}}) – 10px, 11px, 12px, 15px, 17px, 22px, 29px, normal<br />
* [[Wikipedia:Proggy programming fonts|Proggy]] ({{AUR|proggyfonts}}) – has different variants<br />
* [http://www.fial.com/~scott/tamsyn-font/ Tamsyn] ({{Pkg|tamsyn-font}})<br />
* [http://terminus-font.sourceforge.net/ Terminus] ({{Pkg|terminus-font}})<br />
* [https://github.com/lucy/tewi-font Tewi] ({{AUR|bdf-tewi-git}})<br />
* [http://unifoundry.com/unifont.html Unifont] ([[Wikipedia:Unicode font#Comparison of fonts|most extensive]] Unicode coverage of any font) ({{Pkg|bdf-unifont}})<br />
<br />
=== Latin script ===<br />
<br />
==== Families ====<br />
<br />
* [[Wikipedia:Luxi fonts|Luxi fonts]] ({{Pkg|font-bh-ttf}}) – X.Org Luxi fonts<br />
* [[Wikipedia:Bitstream Vera|Bitstream Vera]] ({{Pkg|ttf-bitstream-vera}}) – serif, sans-serif, and monospace<br />
* [https://quoteunquoteapps.com/courierprime/ Courier Prime] ({{AUR|ttf-courier-prime}}) – Courier font alternative optimized for screenplays<br />
* [[Wikipedia:Croscore fonts|Croscore fonts]] ({{Pkg|ttf-croscore}}) – Google's substitute for Windows' Arial, Times New Roman, and Courier New<br />
* [[Wikipedia:DejaVu fonts|DejaVu fonts]] ({{Pkg|ttf-dejavu}}) – Bitstream Vera modified for greater Unicode coverage<br />
* [[Wikipedia:Droid (font)|Droid]] ({{Pkg|ttf-droid}}) – default font for older Android versions<br />
* [[Wikipedia:Roboto|Roboto]] ({{Pkg|ttf-roboto}}) – default font for newer Android versions<br />
* [[Wikipedia:Noto fonts|Google Noto]] ({{Pkg|noto-fonts}}) – Unicode<br />
* [[Wikipedia:Liberation fonts|Liberation fonts]] ({{Pkg|ttf-liberation}}) – free metric-compatible substitute for the Arial, Arial Narrow, Times New Roman and Courier New fonts found in Windows and Microsoft Office products<br />
* [[Wikipedia:Ubuntu Font Family|Ubuntu Font Family]] ({{Pkg|ttf-ubuntu-font-family}})<br />
* [[Microsoft fonts]] ({{AUR|ttf-ms-win10}}) – Windows 10 fonts<br />
Legacy Microsoft font packages:<br />
* [http://corefonts.sourceforge.net/ Microsoft fonts] ({{AUR|ttf-ms-fonts}}) – Andalé Mono, Courier New, Arial, Arial Black, Comic Sans, Impact, Lucida Sans, Microsoft Sans Serif, Trebuchet, Verdana, Georgia, Times New Roman<br />
* Vista fonts ({{AUR|ttf-vista-fonts}}) – Consolas, Calibri, Candara, Corbel, Cambria, Constantia<br />
<br />
==== Monospaced ====<br />
<br />
For more monospaced fonts see [[#Bitmap]] and [[#Families]].<br />
<br />
* [http://www.marksimonson.com/fonts/view/anonymous-pro Anonymous Pro] ({{pkg|ttf-anonymous-pro}}, included in {{AUR|ttf-google-fonts-git}})<br />
* [https://damieng.com/blog/2008/05/26/envy-code-r-preview-7-coding-font-released Envy Code R] ({{AUR|ttf-envy-code-r}})<br />
* Fantasque Sans Mono ({{AUR|ttf-fantasque-sans-git}})<br />
* [[Wikipedia:Fira Sans|Fira Mono]] ({{pkg|ttf-fira-mono}}, {{pkg|otf-fira-mono}}) – designed for Firefox OS<br />
* [[Wikipedia:GNU FreeFont|FreeMono]] ({{Pkg|ttf-freefont}}) - Unicode<br />
* [https://sourcefoundry.org/hack/ Hack] ({{pkg|ttf-hack}}) - an open source monospaced font, used as the default in KDE Plasma<br />
* [[Wikipedia:Inconsolata|Inconsolata]] ({{Pkg|ttf-inconsolata}}, included in {{AUR|ttf-google-fonts-git}}) - inspired by Consolas<br />
* [https://leonardo-m.livejournal.com/77079.html Inconsolata-g] ({{AUR|ttf-inconsolata-g}}) - adds some programmer-friendly modifications<br />
* [https://be5invis.github.io/Iosevka/ Iosevka] ({{AUR|ttf-iosevka}}) – Iosevka is a slender monospace sans-serif and slab-serif typeface inspired by Pragmata Pro, M+ and PF DIN Mono, designed to be the ideal font for programming.<br />
* [[Wikipedia:Lucida Typewriter|Lucida Typewriter]] (included in package {{AUR|jre}})<br />
* [[Wikipedia:Menlo (typeface)|Menlo]] (derivative: {{AUR|ttf-meslo}}) - default monospaced font of OS X<br />
* [[Wikipedia:Monaco (typeface)|Monaco]] ({{AUR|ttf-monaco}}) - proprietary font designed by Apple for OS X<br />
* Monofur ({{AUR|ttf-monofur}})<br />
* [https://madmalik.github.io/mononoki Mononoki] ({{AUR|ttf-mononoki}})<br />
* [[Wikipedia:Source_Code_Pro|Source Code Pro]] ({{pkg|adobe-source-code-pro-fonts}})<br />
<br />
Relevant websites:<br />
<br />
* [http://hivelogic.com/articles/top-10-programming-fonts Dan Benjamin's Top 10 Programming Fonts].<br />
* [http://www.lowing.org/fonts/ Trevor Lowing's font list]<br />
* [https://www.slant.co/topics/67/~what-are-the-best-programming-fonts Slant: What are the best programming fonts?]<br />
* [https://stackoverflow.com/questions/4689/recommended-fonts-for-programming Stack Overflow: Recommended fonts for programming]<br />
<br />
==== Sans-serif ====<br />
<br />
* [http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&id=andika Andika] ({{AUR|ttf-andika}})<br />
* [[Wikipedia:GNU FreeFont|FreeSans]] ({{Pkg|ttf-freefont}}) - Unicode<br />
* [https://github.com/rsms/inter Inter UI] ({{AUR|ttf-inter-ui}}) – designed for user interfaces<br />
* [[Wikipedia:Linux Libertine|Linux Biolinum]] ({{Pkg|ttf-linux-libertine}}) – free substitute for Times New Roman<br />
* [[Wikipedia:PT Sans|PT Sans]] ({{AUR|ttf-google-fonts-git}}) - 3 major variations: normal, narrow, and caption - Unicode: Latin, Cyrillic<br />
* [[Wikipedia:Source Sans Pro|Source Sans Pro]] ({{pkg|adobe-source-sans-pro-fonts}})<br />
* [[Wikipedia:Tahoma (typeface)|Tahoma]] ({{AUR|ttf-tahoma}})<br />
<br />
==== Serif ====<br />
<br />
* [http://www.georgduffner.at/ebgaramond/ EB Garamond] ({{AUR|otf-eb-garamond}})<br />
* [[Wikipedia:GNU FreeFont|FreeSerif]] ({{Pkg|ttf-freefont}}) - Unicode<br />
* [[Wikipedia:Gentium|Gentium]] ({{Pkg|ttf-gentium}}) - Unicode: Latin, Greek, Cyrillic, Phonetic Alphabet<br />
* [[Wikipedia:Linux Libertine|Linux Libertine]] ({{Pkg|ttf-linux-libertine}}) - Unicode: Latin, Greek, Cyrillic, Hebrew<br />
<br />
==== Unsorted ====<br />
<br />
{{Style|This section should be absorbed into the Monospace/Serif/Sans-Serif structure}}<br />
<br />
* {{Pkg|ttf-cheapskate}} - Font collection from ''dustismo.com''<br />
* {{Pkg|ttf-junicode}} - Junius font containing almost complete medieval latin script glyphs<br />
* {{Pkg|ttf-mph-2b-damase}} - Covers full plane 1 and several scripts<br />
* {{Pkg|xorg-fonts-type1}} - IBM Courier and Adobe Utopia sets of [[Wikipedia:PostScript fonts|PostScript fonts]]<br />
* {{AUR|all-repository-fonts}} - Meta package for all fonts in the official repositories.<br />
* {{AUR|ttf-google-fonts-git}} - a huge collection of free fonts (including Ubuntu, Inconsolata, Roboto, etc.) - Note: Your font dialog might get very long as >100 fonts will be added.<br />
<br />
=== Non-latin scripts ===<br />
<br />
==== Ancient Scripts ====<br />
<br />
* {{AUR|ttf-ancient-fonts}} - Font containing Unicode symbols for Aegean, Egyptian, Cuneiform, Anatolian, Maya, and Analecta scripts<br />
<br />
==== Arabic ====<br />
<br />
* {{AUR|ttf-amiri}} - A classical Arabic typeface in Naskh style poineered by Amiria Press<br />
* {{AUR|ttf-arabeyes-fonts}} - Collection of free Arabic fonts<br />
* {{AUR|ttf-qurancomplex-fonts}} - Fonts by King Fahd Glorious Quran Printing Complex in al-Madinah al-Munawwarah<br />
* {{AUR|ttf-sil-lateef}} - Unicode Arabic font from SIL<br />
* {{AUR|ttf-sil-scheherazade}} - Unicode Arabic font from SIL (Alternative for Traditional Arabic font)<br />
<br />
==== Braille ====<br />
<br />
*{{Pkg|ttf-ubraille}} - Font containing Unicode symbols for ''braille''<br />
<br />
==== Chinese, Japanese, Korean, Vietnamese ====<br />
<br />
===== Pan-CJK =====<br />
*adobe source han fonts - Large collection of fonts which comprehensively support Simplified Chinese, Traditional Chinese, Japanese, and Korean, with a consistent design and look.<br />
**{{Pkg|adobe-source-han-sans-otc-fonts}} - Sans fonts<br />
**{{Pkg|adobe-source-han-serif-otc-fonts}} - Serif fonts<br />
<br />
*{{Pkg|noto-fonts-cjk}} - Large collection of fonts which comprehensively support Simplified Chinese, Traditional Chinese, Japanese, and Korean, with a consistent design and look. It is currently a rebadged version of {{Pkg|adobe-source-han-sans-otc-fonts}}.<br />
<br />
===== Chinese =====<br />
<br />
{{Move|Localization/Chinese#Fonts|It makes sense to group language-specific things together.|section=Move CJK and Indic fonts to Localization subpages}}<br />
<br />
* adobe source han fonts<br />
** {{Pkg|adobe-source-han-sans-cn-fonts}} - Simplified Chinese OpenType/CFF Sans fonts<br />
** {{Pkg|adobe-source-han-sans-tw-fonts}} - Traditional Chinese OpenType/CFF Sans fonts<br />
** {{Pkg|adobe-source-han-serif-cn-fonts}} - Simplified Chinese OpenType/CFF Serif fonts<br />
** {{Pkg|adobe-source-han-serif-tw-fonts}} - Traditional Chinese OpenType/CFF Serif fonts<br />
<br />
* noto Chinese fonts<br />
** {{AUR|noto-fonts-sc}} - Noto CJK-SC fonts for Simplified Chinese<br />
** {{AUR|noto-fonts-tc}} - Noto CJK-TC fonts for Traditional Chinese<br />
<br />
* wqy fonts<br />
** {{Pkg|wqy-microhei}} - WenQuanYi Micro Hei font family (also known as Hei, Gothic or Dotum) is a sans-serif style derived from Droid Sans Fallback, it offers high quality CJK outline font and it is extremely compact (~5M).<br />
** {{Pkg|wqy-zenhei}} - Hei Ti Style (sans-serif) Chinese Outline font embedded with bitmapped Song Ti (also supporting Japanese (partial) and Korean characters).<br />
** {{Pkg|wqy-bitmapfont}} - Bitmapped Song Ti (serif) Chinese font.<br />
<br />
* arphic fonts<br />
** {{Pkg|ttf-arphic-ukai}} - ''Kaiti'' (brush stroke) Unicode font (enabling anti-aliasing is suggested)<br />
** {{Pkg|ttf-arphic-uming}} - ''Mingti'' (printed) Unicode font<br />
<br />
* {{Pkg|opendesktop-fonts}} - ''New Sung'' font, previously is ttf-fireflysung package<br />
<br />
* {{Pkg|ttf-hannom}} - Chinese and Vietnamese ttf fonts<br />
<br />
* Standart fonts of the Republic of China ministry of education in Taiwan<br />
** {{AUR|ttf-tw}} - Kai and Song traditional Chinese font from the Ministry of Education of Taiwan<br />
** {{AUR|ttf-twcns-fonts}} Chinese TrueType fonts by Ministry of Education of Taiwan government, support CNS11643 standard, including Kai and Sung fontface.<br />
<br />
*Windows Chinese fonts<br />
**{{AUR|ttf-ms-win8-zh_cn}} - windows8 simple Chinese fonts。<br />
**{{AUR|ttf-ms-win8-zh_tw}} - windows8 traditional Chinese fonts。<br />
**{{AUR|ttf-ms-win10-zh_cn}} - windows10 simple Chinese fonts。<br />
**{{AUR|ttf-ms-win10-zh_tw}} - windows10 traditional Chinese fonts。<br />
<br />
* {{AUR|ttf-i.bming}} - CJK serif font that emphasis on an old-style typeface.<br />
<br />
===== Japanese =====<br />
<br />
{{Move|Localization/Japanese#Fonts|It makes sense to group language-specific things together.|section=Move CJK and Indic fonts to Localization subpages}}<br />
<br />
* {{Pkg|adobe-source-han-sans-jp-fonts}} - Japanese OpenType/CFF fonts<br />
* {{Pkg|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.<br />
* {{Pkg|ttf-hanazono}} - A free Japanese kanji font, style Mincho (serif).<br />
* {{Pkg|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.<br />
* {{AUR|ttf-koruri}} - Japanese TrueType font obtained by mixing {{AUR|ttf-mplus}} and Open Sans<br />
* {{AUR|ttf-monapo}} - Japanese fonts to show [[wikipedia:2channel_Shift_JIS_art|2channel Shift JIS art]] properly.<br />
* {{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).<br />
* {{AUR|ttf-vlgothic}} - Japanese Gothic fonts. Default of Debian/Fedora/Vine Linux<br />
<br />
===== Korean =====<br />
<br />
{{Move|Localization/Korean#Fonts|It makes sense to group language-specific things together.|section=Move CJK and Indic fonts to Localization subpages}}<br />
<br />
* {{Pkg|adobe-source-han-sans-kr-fonts}} - Korean OpenType/CFF fonts<br />
* {{Pkg|ttf-baekmuk}} - Collection of Korean TrueType fonts<br />
* {{AUR|spoqa-han-sans}} - Source Han Sans customized by Spoqa<br />
* {{AUR|ttf-d2coding}} - D2Coding fixed width TrueType font made by Naver<br />
* {{AUR|ttf-nanum}} - Nanum series TrueType fonts<br />
* {{AUR|ttf-nanumgothic_coding}} - Nanum series fixed width TrueType fonts<br />
* {{AUR|ttf-kopub}}/{{AUR|otf-kopub}} - Korean TrueType/OpenType fonts by Korea Publisher Society<br />
* {{AUR|ttf-kopubworld}}/{{AUR|otf-kopubworld}} - Multilingual (Korean, Yethangul, Chinese extended, Japanese, Latin extended, Cyrillic, Arabic, Hebrew, Devanagari) TrueType/OpenType fonts by Korea Publisher Society<br />
* {{AUR|ttf-unfonts-core-ibx}} - A collection of Korean TrueType fonts by KLDP<br />
<br />
===== Vietnamese =====<br />
<br />
* {{Pkg|ttf-hannom}} - Vietnamese TrueType font for chữ Nôm characters<br />
<br />
==== Cyrillic ====<br />
<br />
See also [[#Latin script]].<br />
<br />
* {{AUR|ttf-paratype}} - Font family by ParaType: sans, serif, mono, extended cyrillic and latin, OFL license<br />
* {{AUR|otf-russkopis}} - A free OpenType cursive font for Cyrillic script<br />
<br />
==== Greek ====<br />
<br />
Almost all Unicode fonts contain the Greek character set (polytonic included). Some additional font packages, which might not contain the complete Unicode set but utilize high quality Greek (and Latin, of course) typefaces are:<br />
<br />
* {{AUR|otf-gfs}} - Selection of OpenType fonts from the Greek Font Society<br />
* {{AUR|ttf-mgopen}} - Professional TrueType fonts from Magenta<br />
<br />
==== Hebrew ====<br />
<br />
* {{AUR|opensiddur-hebrew-fonts}} - Large collection of Open-source licensed Hebrew fonts<br />
* {{AUR|culmus}} - Nice collection of free Hebrew fonts<br />
<br />
==== Indic ====<br />
<br />
{{Move|Localization/Indic#Fonts|It makes sense to group language-specific things together.|section=Move CJK and Indic fonts to Localization subpages}}<br />
<br />
* {{Pkg|ttf-freebanglafont}} - Font for Bangla<br />
* {{Pkg|ttf-indic-otf}} - Indic OpenType Fonts collection (containing ttf-freebanglafont), provides the character [http://www.fileformat.info/info/unicode/char/ca0/index.htm U+0CA0] "ಠ"<br />
* {{AUR|lohit-fonts}} - Indic TrueType fonts from Fedora Project (containing Oriya Fonts and more)<br />
* {{AUR|ttf-devanagarifonts}} - Devanagari TrueType fonts (contains 283 fonts)<br />
* {{AUR|ttf-gurmukhi-fonts_sikhnet}} - TrueType Gurmukhi fonts (gurbaniwebthick,prabhki)<br />
* {{AUR|ttf-gurmukhi_punjabi}} - TTF Gurmukhi / Punjabi (contains 252 fonts)<br />
* {{AUR|ttf-gujrati-fonts}} - TTF Gujarati fonts (Avantika,Gopika,Shree768)<br />
* {{AUR|ttf-kannada-font}} - Kannada, the language of Karnataka state in India<br />
* {{AUR|ttf-lklug}} - Sinhala Unicode font<br />
* {{AUR|ttf-tamil}} - Tamil Unicode fonts<br />
* {{AUR|ttf-urdufonts}} - Urdu fonts (Jameel Noori Nastaleeq (+kasheeda), Nafees Web Naskh, PDMS Saleem Quran Font) and font configuration to set Jameel Noori Nastaleeq as default font for Urdu<br />
* {{AUR|fonts-smc-malayalam}} - Malayalam Unicode Fonts released by 'Swathanthra Malayalam Computing' (contains 11 fonts).<br />
<br />
==== Khmer ====<br />
<br />
* {{Pkg|ttf-khmer}} - Font covering glyphs for Khmer language<br />
* [https://www.google.com/fonts/specimen/Hanuman Hanuman] ({{AUR|ttf-google-fonts-git}})<br />
<br />
==== Mongolic and Tungusic ====<br />
<br />
* {{AUR|ttf-abkai}} - Fonts for Sibe, Manchu and Daur scripts (incomplete, currently in development)<br />
<br />
==== Persian ====<br />
<br />
* {{AUR|persian-fonts}} - Meta package for installing all Persian fonts in AUR.<br />
* {{AUR|borna-fonts}} - Borna Rayaneh Co. Persian B font series.<br />
* {{AUR|iran-nastaliq-fonts}} - A free Unicode calligraphic Persian font.<br />
* {{AUR|iranian-fonts}} - Iranian-Sans and Iranian-Serif Persian font family.<br />
* {{AUR|ir-standard-fonts}} - Iran Supreme Council of Information and Communication Technology (SCICT) standard Persian fonts.<br />
* {{AUR|persian-hm-ftx-fonts}} - A Persian font series derived from X Series 2, Metafont and FarsiTeX fonts with Kashida feature.<br />
* {{AUR|persian-hm-xs2-fonts}} - A Persian font series derived from X Series 2 fonts with Kashida feature.<br />
* {{AUR|sina-fonts}} - Sina Pardazesh Co. Persian font series.<br />
* {{AUR|gandom-fonts}}, {{AUR|parastoo-fonts}}, {{AUR|sahel-fonts}}, {{AUR|samim-fonts}}, {{AUR|shabnam-fonts}}, {{AUR|tanha-fonts}}, {{AUR|vazir-fonts}}, {{AUR|vazir-code-fonts}} - Beautiful Persian fonts made by Ali Rasti Kerdar.<br />
* {{AUR|ttf-yas}} - The Yas Persian font series (with '''hollow zero''').<br />
* {{AUR|ttf-x2}} - Free fonts with support for Persian, Arabic, Urdu, Pashto, Dari, Uzbek, Kurdish, Uighur, old Turkish (Ottoman) and modern Turkish (Roman).<br />
<br />
==== Tai–Kadai ====<br />
<br />
* {{Pkg|fonts-tlwg}} - Collection of scalable Thai fonts<br />
* {{AUR|ttf-lao}} - Lao TTF font (Phetsarath_OT)<br />
* {{AUR|ttf-lao-fonts}} - Lao TTF fonts, both Unicode and non-Unicode for Windows<br />
<br />
==== Tibeto-Burman ====<br />
<br />
* {{Pkg|ttf-tibetan-machine}} - Tibetan Machine TTFont<br />
* {{AUR|ttf-myanmar-fonts}} - 121 Fonts from myordbok.com<br />
<br />
=== Emoji and symbols ===<br />
<br />
A section of the Unicode standard is designated for pictographic characters called "emoji".<br />
<br />
* {{Pkg|noto-fonts-emoji}} - Google's own emoji font, like on Android or Google Hangouts.<br />
* {{AUR|ttf-symbola}} - provides many Unicode symbols, including emoji, in outline style.<br />
* {{AUR|ttf-emojione}} - Official colorful EmojiOne font.<br />
* {{AUR|ttf-emojione-color}} - a color and B&W emoji SVGinOT font built from EmojiOne.<br />
* {{AUR|ttf-twemoji-color}} - Twitter's open-sourced emoji glyphs.<br />
<br />
[[wikipedia:Emoticon#Japanese_style|Kaomoji]] are sometimes referred to as "Japanese emoticons" and are composed of characters from various character sets, including CJK and Indic fonts. For example, the following set of packages covers most of existing kaomoji: {{Pkg|ttf-freefont}}, {{Pkg|ttf-arphic-uming}}, and {{Pkg|ttf-indic-otf}}.<br />
<br />
=== Math ===<br />
<br />
* {{Pkg|font-mathematica}} - Mathematica fonts by Wolfram Research, Inc.<br />
* {{Pkg|texlive-core}} and {{Pkg|texlive-fontsextra}} contain many math fonts such as Latin Modern Math and [[Wikipedia:STIX Fonts project|STIX Fonts]]. See [[TeX Live#Making fonts available to Fontconfig]] for configuration.<br />
* {{AUR|otf-stix}} - A standalone, more recent version of STIX<br />
* {{Pkg|otf-latin-modern}}, {{Pkg|otf-latinmodern-math}} - Improved version of Computer Modern fonts as used in LaTeX<br />
* {{AUR|ttf-computer-modern-fonts}}, {{AUR|otf-cm-unicode}} - [[wikipedia:Computer Modern|Computer Modern]] (of TeX fame)<br />
* {{AUR|ttf-mathtype}} - MathType fonts<br />
<br />
=== Other operating system fonts ===<br />
<br />
* {{AUR|ttf-mac-fonts}} - Apple MacOS TrueType fonts<br />
<br />
See [[Metric-compatible fonts]], which lists available alternatives for [[Microsoft fonts]].<br />
<br />
== Fallback font order with X11 ==<br />
<br />
Fontconfig automatically chooses a font that matches the current requirement. That is to say, if one is looking at a window containing English and Chinese for example, it will switch to another font for the Chinese text if the default one does not support it.<br />
<br />
Fontconfig lets every user configure the order they want via {{ic|$XDG_CONFIG_HOME/fontconfig/fonts.conf}}.<br />
If you want a particular Chinese font to be selected after your favorite Serif font, your file would look like this:<br />
<br />
<?xml version="1.0"?><br />
<!DOCTYPE fontconfig SYSTEM "fonts.dtd"><br />
<fontconfig><br />
<alias><br />
<family>serif</family><br />
<prefer><br />
<family>Your favorite Latin Serif font name</family><br />
<family>Your Chinese font name</family><br />
</prefer><br />
</alias><br />
</fontconfig><br />
<br />
{{Tip|If you use a Chinese locale, set {{ic|LC_LANG}} to {{ic|und}} to make this work. Otherwise both English and Chinese text will be rendered in the Chinese font.}}<br />
<br />
You can add a section for sans-serif and monospace as well. For more information, have a look at the fontconfig manual.<br />
<br />
See also [[Font configuration#Replace or set default fonts]].<br />
<br />
== Font alias ==<br />
<br />
There are several font aliases which represent other fonts in order that applications may use similar fonts. The most common aliases are: {{ic|serif}} for a font of the serif type (e.g. DejaVu Serif); {{ic|sans-serif}} for a font of the sans-serif type (e.g. DejaVu Sans); and {{ic|monospace}} for a monospaced font (e.g. DejaVu Sans Mono). However, the fonts which these aliases represent may vary and the relationship is often not shown in font management tools, such as those found in [[KDE]] and other [[desktop environments]].<br />
<br />
To reverse an alias and find which font it is representing, run:<br />
<br />
{{hc|$ fc-match monospace|<br />
DejaVuSansMono.ttf: "DejaVu Sans Mono" "Book"<br />
}}<br />
<br />
In this case, {{ic|DejaVuSansMono.ttf}} is the font represented by the monospace alias.<br />
<br />
== Tips and tricks ==<br />
<br />
=== List all installed fonts ===<br />
<br />
You can use the following command to list all installed Fontconfig fonts that are available on your system. <br />
<br />
$ fc-list<br />
<br />
=== Lists installed fonts for a particular language ===<br />
<br />
Applications and browsers select and display fonts depending upon fontconfig preferences and available font glyph for Unicode text. To list installed fonts for a particular language, issue a command {{ic|<nowiki>fc-list :lang="two letter language code"</nowiki>}}. For instance, to list installed Arabic fonts or fonts supporting Arabic glyph:<br />
{{hc|$ fc-list -f '%{file}\n' :lang&#61;ar|2=<br />
<nowiki><br />
/usr/share/fonts/TTF/FreeMono.ttf<br />
/usr/share/fonts/TTF/DejaVuSansCondensed.ttf<br />
/usr/share/fonts/truetype/custom/DroidKufi-Bold.ttf<br />
/usr/share/fonts/TTF/DejaVuSansMono.ttf<br />
/usr/share/fonts/TTF/FreeSerif.ttf<br />
</nowiki><br />
}}<br />
<br />
=== Set terminal font on-the-fly ===<br />
<br />
{{Expansion|Which terminals specifically support this method? Where is the documentation for the escape codes?}}<br />
<br />
For terminal emulators that use {{ic|Xresources}}, fonts can be set by using escape sequences. Specifically, {{ic|echo -e "\033]710;$font\007"}} to change the normal font ({{ic|*font}} in {{ic|~/.Xresources}}), and replace {{ic|710}} with {{ic|711}}, {{ic|712}}, and {{ic|713}} to change the {{ic|*boldFont}}, {{ic|*italicFont}}, and {{ic|*boldItalicFont}}, respectively.<br />
<br />
{{ic|$font}} uses the same syntax as in {{ic|~/.Xresources}} and can be anything the terminal emulator will support. (Example: {{ic|1=xft:dejavu sans mono:size=9}})<br />
<br />
=== Application-specific font cache ===<br />
<br />
Matplotlib ({{pkg|python-matplotlib}} or {{pkg|python2-matplotlib}}) uses its own font cache, so after updating fonts, be sure to remove {{ic|~/.matplotlib/fontList.cache}}, <br />
{{ic|~/.cache/matplotlib/fontList.cache}}, {{ic|~/.sage/matplotlib-1.2.1/fontList.cache}}, etc. so it will regenerate its cache and find the new fonts [http://matplotlib.1069221.n5.nabble.com/getting-matplotlib-to-recognize-a-new-font-td40500.html].<br />
<br />
== See also ==<br />
<br />
* [http://behdad.org/text/ State of Text Rendering]<br />
* [https://fontlibrary.org/en Font Library] - Fonts under Free licenses<br />
* [https://screenshots.debian.net/packages?search=fonts&show=with Fonts on screenshots.debian.net]</div>Jgwakhttps://wiki.archlinux.org/index.php?title=Localization_(%ED%95%9C%EA%B5%AD%EC%96%B4)/Korean_(%ED%95%9C%EA%B5%AD%EC%96%B4)&diff=565032Localization (한국어)/Korean (한국어)2019-01-28T09:58:55Z<p>Jgwak: 새로운 옛한글 폰트 추가</p>
<hr />
<div>[[Category:Localization (한국어)]]<br />
[[en:Localization/Korean]]<br />
{{Related articles start (한국어)}}<br />
{{Related|Internationalization}}<br />
{{Related articles end}}<br />
<br />
이 문서는 아치리눅스 설치 후 한국어 입력을 설정하는 방법을 다룹니다.<br />
<br />
이 문서를 읽기 전에 [[X11]] 환경을 미리 설치하고 설정하십시오. 이 문서는 콘솔에서 한국어를 입력하는 방법을 다루지 않습니다.<br />
<br />
==글꼴==<br />
<br />
한글 입력을 사용하기 위해서는 한글 글꼴이 설치되어 있어야 합니다. {{aur|ttf-nanum}} 패키지를 [[AUR]]에서 설치하십시오. 터미널 등에서 사용할 수 있는 고정폭 글꼴이 필요하다면 AUR에서 {{aur|ttf-nanumgothic_coding}} 패키지를 설치하십시오. 옛한글을 읽고 입력하기 원한다면, {{aur|ttf-unfonts-core-ibx}} 혹은 {{aur|ttf-kopubworld}}/{{aur|otf-kopubworld}} 패키지를 사용하십시오.<br />
<br />
다른 한글 폰트는 [[Fonts#Korean]]에서 확인할 수 있습니다.<br />
<br />
==한글 입력기 고르기==<br />
<br />
입력기 프레임워크들은 여러가지 입력기와 입력 라이브러리를 포함하여 사용중인 입력기를 쉽게 전환할 수 있도록 해줍니다. [[IBus]], [[uim]], [[fcitx]], [[scim]] 등의 입력기 프레임워크들이 한국어 입력을 지원합니다. 덧붙여, {{aur|nabi}}{{Broken package link|{{aur-mirror|nabi}}}}는 독립적인 한글 입력기로서, 다른 프레임워크를 사용하지 않습니다. 이 항목에서는 한글 입력기 선택을 돕기 위한 정보를 제공합니다.<br />
<br />
{{참고|각 입력기나 입력기 프레임워크에서 나타나는 문제들을 반드시 확인한 후에 입력기를 고르십시오.}}<br />
<br />
===입력기별 문제===<br />
<br />
;ibus: [[IBus]]는 [[GNOME]]과 우분투의 기본 입력기 프레임워크입니다. 가장 널리 지원을 받으며, 대부분의 어플리케이션에서 문제 없이 한글 입력을 할 수 있습니다. 2018년 7월 현재 JetBrains사에서 제공하는 대부분의 소프트웨어(IntelliJ, PyCharm 등)와 충돌을 일으킵니다. 예를 들어, "한글 입력에 문제가 있습니다."라고 입력하면 "한 글입력 에문제 가있습니다."로 표시됩니다.<br />
<br />
;uim: [[uim]]은 여러 언어를 지원하는 크로스 플랫폼 입력기입니다. 아치리눅스 공식 저장소의 {{pkg|uim}} 패키지에는 한국어 입력기인 uim-byeoru가 포함되어 있습니다. uim-byeoru는 구글 크롬과 크로미움을 포함한 대부분의 어플리케이션에서 문제 없이 한글 입력을 할 수 있습니다. 하지만 {{pkg|opera}} 사용자라면 opera에서 uim-byeoru를 사용하려고 할 때 opera가 충돌하는 현상이 나타날 수 있습니다.<br />
<br />
;scim: scim 혹은 [[Smart Common Input Method platform]]는 posix와 호환되는 운영체제를 위한 입력기 프레임워크입니다. 2014년 11월 현재, scim-hangul는 Google Chrome과 Chromium에서 문제를 일으킵니다. 기본 환경 변수를 사용할 경우, scim-hangul은 Google Chrome이나 Chromium에서 한글 입력을 할 수 없습니다. 2014년 현재, scim-hangul은 gedit과도 문제를 일으킵니다. 기본 환경 변수를 사용할 경우, 한글 입력기를 선택한 상태에서는 gedit에서 백스페이스가 정상적으로 작동하지 않습니다. 이 두 문제에 대한 해결 방법은 아래에서 다룹니다. 단, 아래의 해결 방법을 사용한 후에도 Google Chrome이나 Chromium에서는 입력기 버퍼 안의 글자가 사라지는 현상이 발생합니다. 즉 한글 입력 중에 스페이스바를 누르면 입력 중이던 마지막 한 글자가 사라집니다. ''현재 이 문제에 대한 해결책은 없습니다.''<br />
<br />
;fcitx: [[Fcitx]] 역시 POSIX 호환 운영체제들을 위한 입력기 프레임워크입니다. 사용하는데 문제는 없지만, GNOME을 사용한다면 탭 메뉴에서 몇 가지의 메뉴가 열리지 않습니다. 또한, Slack을 사용한다면, Electron이 입력을 무시해서 입력은 영어로밖에 입력이 되지 않습니다.<br />
<br />
;nabi: {{aur|nabi}}{{Broken package link|{{aur-mirror|nabi}}}}는 최환진 씨가 개발하는 독립적 한글 입력기입니다. 옛한글 입력 등 한글 입력에 특화된 여러 기능을 제공합니다. 한글과 영어만을 사용한다면, 나비 입력기를 설치해보십시오. 2014년 11월 현재 나비는 Google Chrome과 Chromium에서 문제를 일으킵니다. 스페이스바를 누를 경우, 입력 중이던 글자가 공백 뒤에 놓이는 현상이 나타납니다. 즉 Google Chrome에서 {{ic|한글 입력에 문제가 있습니다}}를 쳤다면, {{ic|한 글입력 에문제 가있습니다}}와 같이 입력이 됩니다. 현재 나비는 아치 리눅스에서 제공되고 있지 않습니다.<br />
<br />
;nimf: {{aur|nimf-git}}{{Broken package link|package not found}}는 예전에 개발되던 dasom의 수정본입니다.<br />
<br />
자신이 사용할 입력기를 골랐다면, 입력기 설정 섹션으로 넘어가십시오.<br />
<br />
==입력기 설정==<br />
<br />
===ibus-hangul===<br />
[[IBus]] 문서를 보십시오.<br />
<br />
===uim-byeoru===<br />
<br />
[[User:Isaac914/uim]]의 설명을 따라 uim을 기본 입력기로 설정하십시오. uim을 기본 입력기로 설정한 후에 이 항목으로 돌아오십시오.<br />
<br />
$ uim-pref-gtk (혹은 uim-pref-gtk3/uim-pref-qt4)<br />
명령으로 uim의 설정창을 여십시오.<br />
<br />
"Global settings"에서 ''specify default IM''(기본 입력기 설정)에 체크 표시를 하십시오. 그리고 "Byeoru"를 기본 입력기로 설정하십시오.<br />
<br />
또한, 'Edit'버튼을 눌러 사용하지 않을 입력기들을 비활성화할 수 있습니다.<br />
<br />
한글과 영어 외에 다른 언어의 입력기도 사용하며, 여러 입력 방법 사이를 빠르게 전환하고 싶다면, ''enable IM switching by hotkey'' 에 체크표시를 하고, 원하는 단축키를 설정하십시오.<br />
<br />
uim의 전역 설정을 마쳤다면, uim 설정창 왼쪽의 트리 메뉴에서 ''Byeoru''를 찾아 클릭하십시오. 여기에서 세벌식 등으로 키보드 레이아웃을 변경할 수 있습니다. Byeoru가 사용할 한자 사전 등의 기타 설정 역시 조정할 수 있습니다.<br />
<br />
이제 트리 메뉴에서 ''Byeoru'' 바로 아래에 있는 ''Byeoru Keybinding 1''에 클릭하십시오. 여기에서 한영 전환에 사용할 단축키를 설정하십시오. 위에서 입력기 전환을 위한 단축키를 선택했다면, 여기에서는 반드시 다른 단축키를 사용해야 합니다. 대부분의 한국 사용자들은 한영 전환에 {{ic|Ctrl+space}}나 {{ic|shift+space}}를 사용합니다.<br />
<br />
{{참고|오른쪽 alt키(한/영키)로 한영 전환을 하고 싶다면, [[#한영키 사용하기]] 섹션으로 가십시오.}}<br />
<br />
이제 uim-byeoru를 이용하여 한글 입력을 할 수 있을 것입니다.<br />
<br />
===scim-hangul===<br />
<br />
{{pkg|scim-hangul}} 패키지를 설치하십시오.<br />
<br />
다음을 {{ic|.xintrc}}, {{ic|.xprofile}}, {{ic|.xsession}} 파일에 추가하십시오.<br />
<br />
{{bc|<nowiki>export XMODIFIERS=@im=SCIM<br />
export GTK_IM_MODULE="xim"<br />
export QT_IM_MODULE="scim"<br />
scim -d</nowiki><br />
}}<br />
<br />
{{참고|이 문서에서 추천하는 환경변수와 [[scim]] 항목에서 추천하는 환경변수 사이에 약간의 차이가 있습니다. [[scim]]문서에서 추천하는 {{ic|<nowiki>GTK_IM_MODULE=”scim"</nowiki>}} 대신 {{ic|<nowiki>export GTK_IM_MODULE="xim"</nowiki>}}를 추가하였습니다. 이렇게 해야 Google Chrome과 Chromium에서 한글 입력이 가능해지며, gedit 등 gtk+ 3 어플리케이션에서 백스페이스를 정상적으로 사용할 수 있습니다.}}<br />
<br />
===fcitx-hangul===<br />
<br />
{{pkg|fcitx-hangul}}과 자신이 사용하는 GUI 툴킷에 알맞은 fcitx 프론트엔드 패키지를 [[Install|설치]]합니다. {{pkg|fcitx-gtk2}}, {{pkg|fcitx-gtk3}}, {{pkg|fcitx-qt4}}, {{pkg|fcitx-qt5}} 등에서 필요한 패키지를 선택하여 설치하십시오..<br />
<br />
KDE 사용자라면 {{pkg|kcm-fcitx}}를 설치하십시오. KDE 시스템 설정 안에서 fcitx를 설정할 수 있습니다.<br />
<br />
fcitx를 설치했다면, 다음을 {{ic|.xinitrc}}, {{ic|.xprofile}}, 혹은 {{ic|.xsession}}에 추가하십시오.<br />
<br />
{{bc|<nowiki>export GTK_IM_MODULE=fcitx<br />
export QT_IM_MODULE=fcitx<br />
export XMODIFIERS=@im=fcitx</nowiki><br />
}}<br />
<br />
===nabi===<br />
<br />
{{aur|nabi}}{{Broken package link|{{aur-mirror|nabi}}}} 패키지를 [[AUR]]에서 설치하십시오.<br />
<br />
나비의 최신 버전을 사용하고 싶다면, {{ic|git clone https://github.com/choehwanjin/nabi.git}} 명령을 내린 후, 터미널을 열어 복제된 git 저장소 안으로 들어갑니다. {{ic|./configure}} 스크립트를 실행하여 필요한 라이브러리가 모두 설치되었는지 확인한 후, {{ic|make}} 명령으로 나비를 컴파일하십시오. 컴파일이 끝났다면, 루트 권한으로{{ic|make install}} 명령을 내리십시오.<br />
<br />
나비를 설치했다면, {{ic|.xprofile}}, {{ic|.xinitrc}}, 혹은 {{ic|xsession}} 파일에 다음을 추가하십시오.<br />
<br />
<br />
{{bc|<nowiki>export XIM=nabi<br />
export XIM_ARGS=<br />
export XIM_PROGRAM="nabi"<br />
export XMODIFIERS="@im=nabi"<br />
export GTK_IM_MODULE=xim<br />
export QT_IM_MODULE=xim</nowiki><br />
}}<br />
<br />
X 세션을 재시작하십시오. 나비는 자동으로 시작될 것입니다. 기본 한글 키보드 레이아웃은 두벌식입니다. 세벌식, 두벌식 옛글 등 다른 키보드 레이아웃을 사용하고 싶다면 나비의 시스템 트레이 아이콘을 클릭하여 원하는 키보드 레아이웃을 선택하십시오.<br />
<br />
==팁과 트릭==<br />
<br />
===한영키 사용하기===<br />
<br />
scim, nabi, uim 중 하나를 선택했다면 한영키를 이용하여 한영전환을 할 수 있습니다. 입력기를 시작하는 환경 변수 '''뒤에''' 다음 환경 변수들을 추가하십시오.<br />
<br />
{{hc|nano .xprofile|<nowiki><br />
xmodmap -e 'remove mod1 = Alt_R'<br />
xmodmap -e 'keycode 108 = Hangul'<br />
xmodmap -e 'remove control = Control_R'<br />
xmodmap -e 'keycode 105 = Hangul_Hanja'</nowiki><br />
}}<br />
<br />
이제 오른쪽 alt키가 "Hangul"이라는 키로, 오른쪽 Ctrl키가 "Hangul_Hanja"라는 키로 매핑되었을 것입니다. 이제 선택한 입력기의 설정창에서 한영키를 한영 전환을 위한 단축키로, 한자키를 한자 입력을 위한 단축키로 설정하십시오. 만약 .xinitrc, .xprofile, .xsession 파일에 위의 환경변수를 추가하는 것으로 한영키나 한자키를 사용할 수 없다면, 위의 변수들을 포함한 쉘 스크립트를 작성하여 X 세션을 시작할 때마다 실행되도록 설정하십시오.<br />
<br />
===리브레오피스===<br />
<br />
리브레오피스에서 한글 입력을 할 수 없다면, {{ic|.xinitrc}}, {{ic|.xprofile}} 혹은 {{ic|.xsession}}에 다음을 추가해보십시오.<br />
{{ic|<nowiki>export OOO_FORCE_DESKTOP="gnome"</nowiki>}}</div>Jgwakhttps://wiki.archlinux.org/index.php?title=Localization/Korean&diff=565030Localization/Korean2019-01-28T09:57:49Z<p>Jgwak: new yethangul fonts</p>
<hr />
<div>[[Category:Localization]]<br />
[[ko:Localization/Korean]]<br />
{{Related articles start}}<br />
{{Related|Internationalization}}<br />
{{Related articles end}}<br />
<br />
This article describes how to set up a Korean language environment. It does not cover setting up Korean input on the console. <br />
<br />
==Fonts==<br />
<br />
To use any Korean input method, you need to have Korean fonts installed. Install {{AUR|ttf-nanum}} from the [[AUR]]. If you also want Korean monospaced fonts, install {{AUR|ttf-nanumgothic_coding}} from the AUR. If you want to view and use Yethangul(옛한글), install {{aur|ttf-unfonts-core-ibx}} or {{aur|ttf-kopubworld}}/{{aur|otf-kopubworld}} font.<br />
<br />
See also [[Fonts#Korean]].<br />
<br />
== Locale ==<br />
<br />
You should have {{ic|ko_KR.UTF-8}} enabled in {{ic|/etc/locale.gen}}. It is recommended that you always use a {{ic|.UTF-8}} locale rather than the {{ic|ko_KR.EUC-KR}} locale. For more information, read [[locale]].<br />
<br />
== Input methods ==<br />
<br />
The following [[input method]]s are available for Korean:<br />
<br />
* {{Pkg|fcitx-hangul}} for [[Fcitx]]<br />
* {{Pkg|ibus-hangul}} for [[IBus]]<br />
* {{Pkg|scim-hangul}} for [[SCIM]]<br />
* ''uim-byeoru'' of [[uim]]<br />
* [[Nimf]]<br />
* [[#Nabi]]<br />
<br />
===Configuration===<br />
<br />
==== Nabi ====<br />
<br />
[https://github.com/libhangul/nabi Nabi] is a standalone Korean input method, developed by Choe Hwanjin, offering many unique features, such as Yethangul support.<br />
<br />
[[Install]] the {{AUR|nabi-git}} package.<br />
<br />
Once you have finished the installation, add the following to [[xprofile]], [[xinitrc]], or {{ic|xsession}}:<br />
<br />
export XIM=nabi<br />
export XIM_ARGS=<br />
export XIM_PROGRAM="nabi"<br />
export XMODIFIERS="@im=nabi"<br />
export GTK_IM_MODULE=xim<br />
export QT_IM_MODULE=xim<br />
<br />
Once you restart the X session, nabi will autostart by default. The default Korean keyboard layout is Dubeolsik(두벌식). If you need a different Korean keyboard layout (e.g. Sebeolsik or Dubeolsik Yetgul), click on the system tray icon of nabi, and select a input method from the menu that pops up.<br />
<br />
====scim-hangul====<br />
<br />
[[Install]] {{Pkg|scim-hangul}}. <br />
<br />
Now add the following to the user's {{ic|.xinitrc}}, {{ic|.xprofile}}, or {{ic|.xsession}}:<br />
<br />
export XMODIFIERS=@im=SCIM<br />
export GTK_IM_MODULE="xim"<br />
export QT_IM_MODULE="scim"<br />
scim -d<br />
<br />
{{note|The above environment variables differ slightly from the ones recommended in the [[scim]] article. We are adding {{ic|<nowiki>export GTK_IM_MODULE="xim"</nowiki>}} instead of {{ic|<nowiki>GTK_IM_MODULE=”scim"</nowiki>}}. This allows us to input Korean in apps such as Chrome and Chromium (though with issues discussed above), and to use backspace properly in GTK+3 applications such as gedit.}}<br />
<br />
====uim-byeoru====<br />
<br />
Follow the instructions in [[User:Isaac914/uim]] to install uim and to get it running. Return to this section after uim is installed and running as the default input method.<br />
<br />
Open the uim preferences window by running :<br />
<br />
$ uim-pref-gtk (Or, uim-pref-gtk3/uim-pref-qt4)<br />
<br />
Within global settings, check on the ''Specify default IM'' checkbox. Then, set ''Byeoru'' as default. You may also want to disable input methods that you do not plan on using by clicking on the 'edit' button. If you want to quickly switch between Korean and other languages (other than English), check the ''enable IM switching by hotkey'' checkbox, and set a hotkey to switch between enabled IMEs.<br />
<br />
When you are done with the global preferences, find ''Byeoru'' in the tree menu on the left side of the preferences window. From there, you can set the Korean keyboard layout you want to use (e.g. {{ic|3 beol}}), specify the korean/Hanja dictionary that Byeoru will use, and other miscellaneous settings. Then, click on ''Byeoru Keybinding 1'' in the tree menu. Set the hotkey you want to use to enable/disable Byeoru. Most Korean users use {{ic|Ctrl+space}} or {{ic|shift+space}}.<br />
<br />
{{Note|If you want to use the right {{ic|Alt}} key to switch from Korean to English and vice versa, go to the [[#Using the Right alt key to switch input methods]] section.}}<br />
<br />
If all went properly, you should now be able to use UIM-byeoru to type in Korean.<br />
<br />
=== Troubleshooting ===<br />
<br />
{{Accuracy|These issues were apparently experienced November 2014, they should be rechecked, reported to upstream if still present and their bug report linked here.}}<br />
<br />
;[[IBus]]:As of November 2014, IBus sometimes doesn't recognize user-set hotkeys for IM switching. This means that you may need to click on the IBus systray icon every time to want to switch input methods.<br />
<br />
;[[uim]]:''uim-byeoru'' may cause [[Opera]] to crash.<br />
<br />
;scim: scim-hangul, as of November 2014, has issues with Google Chrome and [[Chromium]] web browsers. With the default environment variables, you cannot input Korean in Google Chrome or Chromium. scim also causes problems in Gedit as of November 2014. When scim-hangul is active, pressing {{ic|backspace}} does not work properly. A workaround for both these issues will be explained in [[#scim-hangul]]. However, even with this workaround applied, Chrome/Chromium users may find that the preedit string disappears when the spacebar or any other modifier key is pressed. ''There is currently no known workaround for this issue.''<br />
<br />
;fcitx:Fcitx-hangul has issues with Google Chrome and Chromium. Some users have reported that fcitx only recognizes Google Chrome/Chromium's URL bar as an input window only after their themes have been changed.<br />
<br />
;nabi: {{AUR|nabi-git}} is a standalone Korean input method that is being developed by Choehwanjin. Nabi provides many unique features, such as Yethangul support. If you only need to use Korean and English input, you may want to install nabi. Currently, nabi causes an issue with chromium. When you press the spacebar, the preedit string will be placed after the space, causing your input to look like this: {{ic|한 글입력 에문제 가있습니다}}<br />
<br />
====Libreoffice====<br />
<br />
In some cases, Libreoffice will not take Korean input from any input method. To resolve this issue, try adding {{ic|1=export OOO_FORCE_DESKTOP="gnome"}} to {{ic|.xinitrc}}, {{ic|.xprofile}}, or {{ic|.xsession}}.<br />
<br />
===Tips and Tricks===<br />
<br />
====Using the Right alt key to switch input methods====<br />
You can use the right {{ic|Alt}} key (e.g. '한/영키') to switch between Input methods if you are using uim, scim, or nabi. To do this, add the following lines '''after''' the environment variables that start your input method:<br />
<br />
{{hc|~/.xprofile|<nowiki><br />
xmodmap -e 'remove mod1 = Alt_R'<br />
xmodmap -e 'keycode 108 = Hangul'<br />
xmodmap -e 'remove control = Control_R'<br />
xmodmap -e 'keycode 105 = Hangul_Hanja'</nowiki><br />
}}<br />
<br />
Then, in the settings of your input method, add the right {{ic|Alt}} key as a hotkey to switch IMEs. The right {{ic|Alt}} key has been remapped to a non-modifier key called "Hangul". The script above also allows you to use the right {{ic|Ctrl}} key (e.g. '한자키') to activate Hanja input. The right {{ic|Ctrl}} key should also have been remapped to "Hangul_Hanja". Add this key as a Hanja hotkey within the settings of your input method. If adding that to your {{ic|.xprofile}} or {{ic|.xinitrc}} file did not work, create a script containing those four lines and set it to auto execute when your desktop environment starts up.</div>Jgwakhttps://wiki.archlinux.org/index.php?title=DisplayLink&diff=562308DisplayLink2019-01-07T22:22:05Z<p>Jgwak: bug fixed!</p>
<hr />
<div>[[Category:Displays]]<br />
[[ja:DisplayLink]]<br />
DisplayLink devices on Linux still only have experimental support. While some people have had success in using them, it is generally not an easy process and not guaranteed to work. The steps on this page describe the generally most successful methods of using external monitors with DisplayLink.<br />
<br />
Also be warned that even over USB 3.0, a DisplayLink monitor may exhibit noticeably more lag than e.g. a DisplayPort monitor, especially when large portions of the screen are being redrawn.<br />
<br />
==Installation==<br />
<br />
=== USB 2.0 DL-1x5, DL-1x0 Devices ===<br />
<br />
The kernel [[Wikipedia: Direct_Rendering_Manager|DRM]] driver for DisplayLink is {{ic|udl}}, a rewrite of the original [https://www.kernel.org/doc/Documentation/fb/udlfb.txt udlfb] driver. It allows configuring DisplayLink monitors using [[Xrandr]].<br />
<br />
This should work without any configuration changes on {{pkg|linux}} 4.14.9-1 and later. If you're using an earlier version of that package or have {{ic|1=CONFIG_FB_UDL=m}} set in your kernel config, you need to [[blacklist]] the old kernel module, {{ic|udlfb}}, which may attempt to load itself first.<br />
<br />
=== USB 3.0 DL-6xxx, DL-5xxx, DL-41xx, DL-3xxx Devices ===<br />
<br />
# Install the {{AUR|displaylink}} driver. It allows configuring DisplayLink monitors using [[Xrandr]] in the same manner as the {{ic|udl}} driver.<br />
# Enable {{ic|displaylink.service}}.<br />
# Use the "modesetting" driver with AccelMethod "none" and MatchDriver "evdi".<br />
<br />
Create a file with the following content:<br />
{{hc|/usr/share/X11/xorg.conf.d/20-evdidevice.conf|<br />
Section "OutputClass"<br />
Identifier "DisplayLink"<br />
MatchDriver "evdi"<br />
Driver "modesetting"<br />
Option "AccelMethod" "none"<br />
EndSection<br />
<br />
}}<br />
A reboot is required for the setting to be effective. You may need the {{aur|evdi-git}} package.<br />
<br />
=== Setting up X Displays ===<br />
<br />
After that, run:<br />
<br />
{{hc|$ xrandr --listproviders|<nowiki><br />
Providers: number : 2<br />
Provider 0: id: 0x49 cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 2 outputs: 8 associated providers: 0 name:Intel<br />
Provider 1: id: 0x13c cap: 0x2, Sink Output crtcs: 1 outputs: 1 associated providers: 0 name:modesetting<br />
</nowiki>}}<br />
<br />
In the above output, we can see that provider 0 is the system's regular graphics provider (Intel), and provider 1 (modesetting) is the DisplayLink provider. To use the DisplayLink device, connect provider 1 to provider 0:<br />
<br />
$ xrandr --setprovideroutputsource 1 0<br />
<br />
and xrandr will add a DVI output you can [[Xrandr#Configuration|use as normal with xrandr]]. This is still experimental but supports hotplugging and when works, it is by far the simplest setup. If it works then everything below is unnecessary.<br />
<br />
==Configuration==<br />
<br />
These instructions assume that you already have an up and running X server and are simply adding a monitor to your existing setup.<br />
<br />
===Load the framebuffer device===<br />
<br />
Before your system will recognize your DisplayLink device, the {{ic|udl}} kernel module must be loaded. To do this, run<br />
<br />
# modprobe udl<br />
<br />
If your DisplayLink device is connected, it should show some visual indication of this. Although a green screen is the standard indicator of this, other variations have been spotted and are perfectly normal. Most importantly, the output of {{ic|dmesg}} should show something like the following, indicating a new DisplayLink device was found:<br />
<br />
{{bc|<nowiki>usb 2-1.1: new high-speed USB device number 7 using ehci-pci<br />
usb 2-1.1: New USB device found, idVendor=17e9, idProduct=03e0<br />
usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3<br />
usb 2-1.1: Product: Lenovo LT1421 wide<br />
usb 2-1.1: Manufacturer: DisplayLink<br />
usb 2-1.1: SerialNumber: 6V9BBRM1<br />
[drm] vendor descriptor length:17 data:17 5f 01 00 15 05 00 01 03 00 04<br />
udl 2-1.1:1.0: fb1: udldrmfb frame buffer device<br />
[drm] Initialized udl 0.0.1 20120220 on minor 1<br />
</nowiki>}}<br />
<br />
Furthermore, {{ic|/dev}} should contain a new {{ic|fb}} device, likely {{ic|/dev/fb1}} if you already had a framebuffer for your primary display.<br />
<br />
To automatically load {{ic|udl}} at boot, create the file {{ic|udl.conf}} in {{ic|/etc/modules-load.d/}} with the following contents:<br />
<br />
{{hc|/etc/modules-load.d/udl.conf|udl}}<br />
<br />
For more information on loading kernel modules, see [[Kernel modules#Automatic module loading with systemd]].<br />
<br />
===Configuring X Server===<br />
Use {{ic|xrandr}} or your Desktop Environment's display setup UI to configure your USB monitors running either the {{ic|udl}} or {{ic|displaylink}} driver.<br />
<br />
====xrandr====<br />
<br />
Once the driver is loaded, the DisplayLink monitor is listed as an output provider:<br />
<br />
{{hc|$ xrandr --listproviders|<nowiki><br />
Providers: number : 2<br />
Provider 0: id: 0x43 cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 2 outputs: 2 associated providers: 1 name:Intel<br />
Provider 1: id: 0xcb cap: 0x2, Sink Output crtcs: 1 outputs: 1 associated providers: 1 name:modesetting<br />
</nowiki>}}<br />
In the above example, provider 1 is the DisplayLink device, and provider 0 is the default display. Running {{ic|xrandr --current}} gives a list of available screens:<br />
<br />
{{hc|$ xrandr --current|<nowiki><br />
Screen 0: minimum 320 x 200, current 1600 x 900, maximum 8192 x 8192<br />
LVDS1 connected 1600x900+0+0 (normal left inverted right x axis y axis) 309mm x 174mm<br />
1600x900 60.0*+ 40.0 <br />
1440x900 59.9 <br />
1360x768 59.8 60.0 <br />
1152x864 60.0 <br />
1024x768 60.0 <br />
800x600 60.3 56.2 <br />
640x480 59.9 <br />
VGA1 disconnected (normal left inverted right x axis y axis)<br />
DVI-1-0 connected (normal left inverted right x axis y axis)<br />
1366x768 60.0 +<br />
1368x768_59.90 59.9 <br />
1368x768_59.90 (0xd0) 85.7MHz<br />
h: width 1368 start 1440 end 1584 total 1800 skew 0 clock 47.6KHz<br />
v: height 768 start 769 end 772 total 795 clock 59.9Hz<br />
</nowiki>}}<br />
<br />
If the above does not list the DisplayLink screen, then you will need to offload DisplayLink to the main GPU:<br />
<br />
{{bc|xrandr --setprovideroutputsource 1 0}}<br />
<br />
Once the screen is available, refer to [[Xrandr]] for info on setting it up. For automating the configuration process, see [https://github.com/nathantypanski/displaylink.sh displaylink.sh].<br />
<br />
====Enabling DVI output on startup====<br />
The DisplayLink provider will not be automatically connected to the main provider in most cases, therefore the DVI output device will not be available. It can be helpful to automatically do this when X starts to facilitate automatic display configuration by the window manager.<br />
<br />
Edit your desktop manager's startup configuration and add commands similar to:<br />
{{bc|<nowiki><br />
$(xrandr --listproviders | grep -q "modesetting") && xrandr --setprovideroutputsource 1 0<br />
</nowiki>}}<br />
<br />
For example, the appropriate startup configuration file for [[SDDM]] is {{ic|/usr/share/sddm/scripts/Xsetup}}.<br />
<br />
Avoid placing these commands in {{ic|~/.xprofile}} as this breaks the display configuration of some window managers. Instead these commands should be run prior to any display output or setup.<br />
<br />
{{Note|If you have additional providers, specify the name of the provider instead of using indexes. The name of the DisplayLink device will be {{ic|modesetting}}}}<br />
<br />
==== Switching between displaylink and nvidia/nouveau driver ====<br />
<br />
Currently (displaylink version 1.3.54-1) it is not possible to use displaylink device and nvidia/nouveau driver simultaniously on optimus based laptops.<br />
Currently to be able to use displaylink device on intel GPU, you should create config file (see troubleshooting section below). However, with that config file it is not possible to use primusrun. Bumblebee service is running, but it cannot work. Also, laptop's fans are becoming very noisy and laptop's temperature becomes very high. When you want to switch back to activate nvidia driver, comment everything in that file and reboot.<br />
<br />
To simplify process of switching, you can [[install]] {{aur|dl-switch}} and add an additional menu entry to your bootloader using the [[kernel parameter]] {{ic|1=systemd.unit=displaylink.target}}, thus activating displaylink workaround.<br />
<br />
To check which driver is used for your discrete video card, run {{ic|lspci -nnk -s xx:xx.x}} (replace xx:xx.x with your nvidia gpu pci id).<br />
<br />
== Troubleshooting ==<br />
<br />
=== Not working configuration ===<br />
<br />
These are tested on [[Xfce]] using Display settings (included in XFCE4 package) and external tool - {{pkg|arandr}}. XFCE4 Display settings are likely to crash, so ARandR might help.<br />
<br />
When you connect display link device via USB to your computer, the computer should show monitors in Display settings. There are few troubleshooting steps that you should try:<br />
<br />
* Check [[#Setting up X Displays]]. If you can find any external monitors recognized, you should try to make them visible by the following commands:<br />
{{bc|<nowiki>xrandr --setprovideroutputsource 1 0<br />
xrandr --setprovideroutputsource 2 0<br />
xrandr --setprovideroutputsource 3 0<br />
...<br />
</nowiki>}}<br />
This will make them visible and recognized in Display settings.<br />
* Restart {{ic|displaylink.service}}.<br />
* Re-connecte USB cable.<br />
* Check if {{ic|udl}} driver is loaded and monitors are connected.<br />
<br />
=== Screen redraw is broken ===<br />
If you are using {{ic|udl}} as your kernel driver and the monitor appears to work, but is only updating where you move the mouse or when windows change in certain places, then you probably have the wrong modeline for your screen. Getting a proper modeline for your screen with a command like<br />
<br />
{{bc|<br />
gtf 1366 768 59.9<br />
}}<br />
<br />
where {{ic|1366}} and {{ic|768}} are the horizontal and vertical resolutions for your monitor, and {{ic|59.9}} is the refresh rate from its specs. To use this, create a new mode with {{ic|xrandr}} like follows:<br />
<br />
{{bc|<br />
xrandr --newmode "1368x768_59.90" 85.72 1368 1440 1584 1800 768 769 772 795 -HSync +Vsync<br />
}}<br />
<br />
and add it to [[Xrandr]]:<br />
<br />
{{bc|<br />
xrandr --addmode DVI-0 1368x768_59.90<br />
}}<br />
<br />
Then tell the monitor to use that mode for the DisplayLink monitor, and this should fix the redraw issues. Check the [[Xrandr]] page for information on using a different mode.<br />
<br />
If this does not solve the problem (or if the correct modeline was already in place because of correct DDC data), it can help to run a compositor. E.g. when using plain i3, running {{Pkg|xcompmgr}} or {{Pkg|compton}} can mitigate the problem.<br />
<br />
=== DisplayLink refresh rate is extremely slow with gnome 3 ===<br />
If once you set up your DisplayLink your entire desktop becomes slow, try setting a "simpler" background image, such as complete black.<br />
<br />
=== Slow redraw/Unresponsiveness in Google Chrome and Webkit2-based Applications ===<br />
This is to be associated with bugs in hardware acceleration, which can be tested by running glxgears in the displaylink screen resulting in 1fps. There is currently no complete fix available, but turning off Hardware-Acceleration in affected applications can work as a temporary fix.<br />
<br />
This can be done in applications without a hardware-acceleration option by prepending the {{ic|1=LIBGL_ALWAYS_SOFTWARE=1}} environment variable.<br />
<br />
=== Impossible to activate displaylink's screen ===<br />
In case you are able to see attached monitor via DisplayLink device in your screen settings, but after you turn it on and apply settings, it becomes deactivated, then try blacklist nouveau module and reboot:<br />
{{hc|/etc/modprobe.d/nouveau.conf|<nowiki><br />
blacklist nouveau<br />
options nouveau modeset=0<br />
</nowiki>}}<br />
<br />
=== Suspend problem ===<br />
<br />
Displaylink is not working after suspend. Unplug and then plug again displaylink's usb cable to your computer. Monitor that is connected via DisplayLink will remain black. If you have lock screen, login to the system and then picture will appear at that monitor and you will be able to use displaylink as normal.<br />
<br />
=== DisplayLink is not working when usb hot plugged ===<br />
To be able to use DisplayLink monitors, its usb cable should be attached to laptop during boot time. Otherwise it can behave like they are available and mouse can be moved there, but its picture is frozen, even with correct configuration (see workaround 1). If it was not attached at boot time, attach it and reboot.<br />
<br />
=== DisplayLink driver does not work with Intel GPUs after recent X upgrades ===<br />
As [http://support.displaylink.com/knowledgebase/articles/1181623 this support] page says, upgrading the X Window Server to a version newer than 1.18.3 will make the system not compatible with DisplayLink by default. This applies to systems using an integrated Intel GPU, or a combination of integrated Intel GPU and a discrete GPU.<br />
Until fixes in X Windows System will be released, there are two workarounds:<br />
<br />
==== Workaround 1: Use older intel driver as a fallback ====<br />
<br />
Use the "intel" driver for the integrated GPU instead of "modesetting", which is now the default.<br />
<br />
Create a file with the following content:<br />
{{hc|/usr/share/X11/xorg.conf.d/20-displaylink.conf|<br />
Section "Device" <br />
Identifier "Intel Graphics"<br />
Driver "intel"<br />
EndSection<br />
}}<br />
A reboot is required for the setting to be effective.<br />
<br />
You may need the {{aur|evdi-git}} package.<br />
<br />
==== Workaround 2: Temporarily disable PageFlip for modesetting ====<br />
<br />
For users that prefer to keep using "modesetting" driver, disabling page flipping should also help.<br />
Create a file with the following content:<br />
{{hc|/usr/share/X11/xorg.conf.d/20-displaylink.conf|<br />
Section "Device"<br />
Identifier "DisplayLink"<br />
Driver "modesetting"<br />
Option "PageFlip" "false"<br />
EndSection <br />
}}<br />
<br />
=== Displays disconnect at random intervals when using the Dell D6000 docking station ===<br />
<br />
User's have [https://www.displaylink.org/forum/showthread.php?t=65476 reported] that when using the Dell D6000 docking station, their display(s) may disconnect at random intervals during usage. This will require physically reconnecting the dock in order to reinitialise the displays.<br />
<br />
This issue appears to be caused by [[PulseAudio]]'s {{ic|module-suspend-on-idle}} module, which automatically suspends sinks/sources on idle.<br />
<br />
To disable loading of the {{ic|module-suspend-on-idle}} module, comment out the following line in the configuration file in use ({{ic|~/.config/pulse/default.pa}} or {{ic|/etc/pulse/default.pa}}):<br />
<br />
{{hc|/etc/pulse/default.pa|<br />
### Automatically suspend sinks/sources that become idle for too long<br />
# load-module module-suspend-on-idle<br />
}}<br />
<br />
== See Also ==<br />
<br />
* [http://displaylink.org/forum/forumdisplay.php?f=29 DisplayLink Open Source]: Official DisplayLink open source support forum<br />
* [http://plugable.com/platforms/linux Plugable]: Vendor blog chronicling Linux support for DisplayLink.<br />
* [http://www.displaylink.com/downloads/ubuntu.php Ubuntu Driver Download]: DisplayLink Ubuntu Driver Download and Information<br />
* [http://downloads.displaylink.com/releasenotes/DisplayLink_Ubuntu_1.0.68_release-note.txt Release Notes]: Latest release notes for DisplayLink Ubuntu Software</div>Jgwakhttps://wiki.archlinux.org/index.php?title=Localization_(%ED%95%9C%EA%B5%AD%EC%96%B4)/Korean_(%ED%95%9C%EA%B5%AD%EC%96%B4)&diff=529258Localization (한국어)/Korean (한국어)2018-07-10T22:34:12Z<p>Jgwak: Add reference to fonts page.</p>
<hr />
<div>[[category: Internationalization (한국어)]]<br />
[[en:Internationalization/Korean]]<br />
{{Related articles start (한국어)}}<br />
{{Related|Internationalization}}<br />
{{Related articles end}}<br />
<br />
이 문서는 아치리눅스 설치 후 한국어 입력을 설정하는 방법을 다룹니다.<br />
<br />
이 문서를 읽기 전에 [[X11]] 환경을 미리 설치하고 설정하십시오. 이 문서는 콘솔에서 한국어를 입력하는 방법을 다루지 않습니다.<br />
<br />
==글꼴==<br />
<br />
한글 입력을 사용하기 위해서는 한글 글꼴이 설치되어 있어야 합니다. {{aur|ttf-nanum}} 패키지를 [[AUR]]에서 설치하십시오. 터미널 등에서 사용할 수 있는 고정폭 글꼴이 필요하다면 AUR에서 {{aur|ttf-nanumgothic_coding}} 패키지를 설치하십시오. 옛한글을 읽고 입력하기 원한다면, {{aur|ttf-unfonts-core-ibx}} 패키지를 사용하십시오.<br />
<br />
다른 한글 폰트는 [[Fonts#Korean]]에서 확인할 수 있습니다.<br />
<br />
==한글 입력기 고르기==<br />
<br />
입력기 프레임워크들은 여러가지 입력기와 입력 라이브러리를 포함하여 사용중인 입력기를 쉽게 전환할 수 있도록 해줍니다. [[IBus]], [[uim]], [[fcitx]], [[scim]] 등의 입력기 프레임워크들이 한국어 입력을 지원합니다. 덧붙여, {{aur|nabi}}{{Broken package link|{{aur-mirror|nabi}}}}는 독립적인 한글 입력기로서, 다른 프레임워크를 사용하지 않습니다. 이 항목에서는 한글 입력기 선택을 돕기 위한 정보를 제공합니다.<br />
<br />
{{참고|각 입력기나 입력기 프레임워크에서 나타나는 문제들을 반드시 확인한 후에 입력기를 고르십시오.}}<br />
<br />
===입력기별 문제===<br />
<br />
;ibus: [[IBus]]는 [[GNOME]]과 우분투의 기본 입력기 프레임워크입니다. 가장 널리 지원을 받으며, 대부분의 어플리케이션에서 문제 없이 한글 입력을 할 수 있습니다. <br />
<br />
;uim: [[uim]]은 여러 언어를 지원하는 크로스 플랫폼 입력기입니다. 아치리눅스 공식 저장소의 {{pkg|uim}} 패키지에는 한국어 입력기인 uim-byeoru가 포함되어 있습니다. uim-byeoru는 구글 크롬과 크로미움을 포함한 대부분의 어플리케이션에서 문제 없이 한글 입력을 할 수 있습니다. 하지만 {{pkg|opera}} 사용자라면 opera에서 uim-byeoru를 사용하려고 할 때 opera가 충돌하는 현상이 나타날 수 있습니다.<br />
<br />
;scim: scim 혹은 [[Smart Common Input Method platform]]는 posix와 호환되는 운영체제를 위한 입력기 프레임워크입니다. 2014년 11월 현재, scim-hangul는 Google Chrome과 Chromium에서 문제를 일으킵니다. 기본 환경 변수를 사용할 경우, scim-hangul은 Google Chrome이나 Chromium에서 한글 입력을 할 수 없습니다. 2014년 현재, scim-hangul은 gedit과도 문제를 일으킵니다. 기본 환경 변수를 사용할 경우, 한글 입력기를 선택한 상태에서는 gedit에서 백스페이스가 정상적으로 작동하지 않습니다. 이 두 문제에 대한 해결 방법은 아래에서 다룹니다. 단, 아래의 해결 방법을 사용한 후에도 Google Chrome이나 Chromium에서는 입력기 버퍼 안의 글자가 사라지는 현상이 발생합니다. 즉 한글 입력 중에 스페이스바를 누르면 입력 중이던 마지막 한 글자가 사라집니다. ''현재 이 문제에 대한 해결책은 없습니다.''<br />
<br />
;fcitx: [[Fcitx]] 역시 POSIX 호환 운영체제들을 위한 입력기 프레임워크입니다. 사용하는데 문제는 없지만, GNOME을 사용한다면 탭 메뉴에서 몇 가지의 메뉴가 열리지 않습니다. 또한, Slack을 사용한다면, Electron이 입력을 무시해서 입력은 영어로밖에 입력이 되지 않습니다.<br />
<br />
;nabi: {{aur|nabi}}{{Broken package link|{{aur-mirror|nabi}}}}는 최환진 씨가 개발하는 독립적 한글 입력기입니다. 옛한글 입력 등 한글 입력에 특화된 여러 기능을 제공합니다. 한글과 영어만을 사용한다면, 나비 입력기를 설치해보십시오. 2014년 11월 현재 나비는 Google Chrome과 Chromium에서 문제를 일으킵니다. 스페이스바를 누를 경우, 입력 중이던 글자가 공백 뒤에 놓이는 현상이 나타납니다. 즉 Google Chrome에서 {{ic|한글 입력에 문제가 있습니다}}를 쳤다면, {{ic|한 글입력 에문제 가있습니다}}와 같이 입력이 됩니다. 현재 나비는 아치 리눅스에서 제공되고 있지 않습니다.<br />
<br />
;dasom: 다솜 입력기({{aur|dasom-git}})는 다국어 입력기 프레임워크 입니다. 타 입력기에서 나타나는 끝글자 버그가 다솜에서는 발생하지 않습니다. 한글 및 영문 엔진, qt4, qt5, gtk2, gtk3, XIM 모듈을 지원하며, 세벌씩 자판과 드보락 자판도 지원합니다. <br />
<br />
<br />
자신이 사용할 입력기를 골랐다면, 입력기 설정 섹션으로 넘어가십시오.<br />
<br />
==입력기 설정==<br />
<br />
===ibus-hangul===<br />
[[IBus]] 문서를 보십시오.<br />
<br />
===uim-byeoru===<br />
<br />
[[User:Isaac914/uim]]의 설명을 따라 uim을 기본 입력기로 설정하십시오. uim을 기본 입력기로 설정한 후에 이 항목으로 돌아오십시오.<br />
<br />
$ uim-pref-gtk (혹은 uim-pref-gtk3/uim-pref-qt4)<br />
명령으로 uim의 설정창을 여십시오.<br />
<br />
"Global settings"에서 ''specify default IM''(기본 입력기 설정)에 체크 표시를 하십시오. 그리고 "Byeoru"를 기본 입력기로 설정하십시오.<br />
<br />
또한, 'Edit'버튼을 눌러 사용하지 않을 입력기들을 비활성화할 수 있습니다.<br />
<br />
한글과 영어 외에 다른 언어의 입력기도 사용하며, 여러 입력 방법 사이를 빠르게 전환하고 싶다면, ''enable IM switching by hotkey'' 에 체크표시를 하고, 원하는 단축키를 설정하십시오.<br />
<br />
uim의 전역 설정을 마쳤다면, uim 설정창 왼쪽의 트리 메뉴에서 ''Byeoru''를 찾아 클릭하십시오. 여기에서 세벌식 등으로 키보드 레이아웃을 변경할 수 있습니다. Byeoru가 사용할 한자 사전 등의 기타 설정 역시 조정할 수 있습니다.<br />
<br />
이제 트리 메뉴에서 ''Byeoru'' 바로 아래에 있는 ''Byeoru Keybinding 1''에 클릭하십시오. 여기에서 한영 전환에 사용할 단축키를 설정하십시오. 위에서 입력기 전환을 위한 단축키를 선택했다면, 여기에서는 반드시 다른 단축키를 사용해야 합니다. 대부분의 한국 사용자들은 한영 전환에 {{ic|Ctrl+space}}나 {{ic|shift+space}}를 사용합니다.<br />
<br />
{{참고|오른쪽 alt키(한/영키)로 한영 전환을 하고 싶다면, [[#한영키 사용하기]] 섹션으로 가십시오.}}<br />
<br />
이제 uim-byeoru를 이용하여 한글 입력을 할 수 있을 것입니다.<br />
<br />
===scim-hangul===<br />
<br />
{{pkg|scim-hangul}} 패키지를 설치하십시오.<br />
<br />
다음을 {{ic|.xintrc}}, {{ic|.xprofile}}, {{ic|.xsession}} 파일에 추가하십시오.<br />
<br />
{{bc|<nowiki>export XMODIFIERS=@im=SCIM<br />
export GTK_IM_MODULE="xim"<br />
export QT_IM_MODULE="scim"<br />
scim -d</nowiki><br />
}}<br />
<br />
{{참고|이 문서에서 추천하는 환경변수와 [[scim]] 항목에서 추천하는 환경변수 사이에 약간의 차이가 있습니다. [[scim]]문서에서 추천하는 {{ic|<nowiki>GTK_IM_MODULE=”scim"</nowiki>}} 대신 {{ic|<nowiki>export GTK_IM_MODULE="xim"</nowiki>}}를 추가하였습니다. 이렇게 해야 Google Chrome과 Chromium에서 한글 입력이 가능해지며, gedit 등 gtk+ 3 어플리케이션에서 백스페이스를 정상적으로 사용할 수 있습니다.}}<br />
<br />
===fcitx-hangul===<br />
<br />
{{pkg|fcitx-hangul}}과 자신이 사용하는 GUI 툴킷에 알맞은 fcitx 프론트엔드 패키지를 [[Install|설치]]합니다. {{pkg|fcitx-gtk2}}, {{pkg|fcitx-gtk3}}, {{pkg|fcitx-qt4}}, {{pkg|fcitx-qt5}} 등에서 필요한 패키지를 선택하여 설치하십시오..<br />
<br />
KDE 사용자라면 {{pkg|kcm-fcitx}}를 설치하십시오. KDE 시스템 설정 안에서 fcitx를 설정할 수 있습니다.<br />
<br />
fcitx를 설치했다면, 다음을 {{ic|.xinitrc}}, {{ic|.xprofile}}, 혹은 {{ic|.xsession}}에 추가하십시오.<br />
<br />
{{bc|<nowiki>export GTK_IM_MODULE=fcitx<br />
export QT_IM_MODULE=fcitx<br />
export XMODIFIERS=@im=fcitx</nowiki><br />
}}<br />
<br />
===nabi===<br />
<br />
{{aur|nabi}}{{Broken package link|{{aur-mirror|nabi}}}} 패키지를 [[AUR]]에서 설치하십시오.<br />
<br />
나비의 최신 버전을 사용하고 싶다면, {{ic|git clone https://github.com/choehwanjin/nabi.git}} 명령을 내린 후, 터미널을 열어 복제된 git 저장소 안으로 들어갑니다. {{ic|./configure}} 스크립트를 실행하여 필요한 라이브러리가 모두 설치되었는지 확인한 후, {{ic|make}} 명령으로 나비를 컴파일하십시오. 컴파일이 끝났다면, 루트 권한으로{{ic|make install}} 명령을 내리십시오.<br />
<br />
나비를 설치했다면, {{ic|.xprofile}}, {{ic|.xinitrc}}, 혹은 {{ic|xsession}} 파일에 다음을 추가하십시오.<br />
<br />
<br />
{{bc|<nowiki>export XIM=nabi<br />
export XIM_ARGS=<br />
export XIM_PROGRAM="nabi"<br />
export XMODIFIERS="@im=nabi"<br />
export GTK_IM_MODULE=xim<br />
export QT_IM_MODULE=xim</nowiki><br />
}}<br />
<br />
X 세션을 재시작하십시오. 나비는 자동으로 시작될 것입니다. 기본 한글 키보드 레이아웃은 두벌식입니다. 세벌식, 두벌식 옛글 등 다른 키보드 레이아웃을 사용하고 싶다면 나비의 시스템 트레이 아이콘을 클릭하여 원하는 키보드 레아이웃을 선택하십시오.<br />
<br />
===dasom===<br />
{{aur|dasom-git}},{{aur|dasom-gtk-git}} ,{{aur|dasom-qt-git}} 패키지와 {{aur|dasom-jeongeum-git}} 패키지를 [[AUR]]에서 설치하십시오.<br />
<br />
설치 후, {{ic|.xprofile}} 파일에 다음을 추가하십시오.<br />
<br />
{{bc|<nowiki>export GTK_IM_MODULE=dasom<br />
export QT_IM_MODULE=dasom<br />
export XMODIFIERS="@im=dasom"<br />
dasom-daemon<br />
dasom-indicator</nowiki><br />
}}<br />
<br />
만약, [[GNOME]] 데스크탑을 사용한다면, 다음을 추가적으로 실행하십시오.<br />
{{bc|<nowiki>gsettings set org.gnome.settings-daemon.plugins.keyboard active false<br />
gsettings set org.gnome.settings-daemon.plugins.xsettings overrides "{'Gtk/IMModule':<'dasom'>}"</nowiki><br />
}}<br />
<br />
X 세션을 재시작하십시오. 다솜입력기는 자동으로 시작될 것입니다.<br />
<br />
<br />
==팁과 트릭==<br />
<br />
===한영키 사용하기===<br />
<br />
scim, nabi, uim 중 하나를 선택했다면 한영키를 이용하여 한영전환을 할 수 있습니다. 입력기를 시작하는 환경 변수 '''뒤에''' 다음 환경 변수들을 추가하십시오.<br />
<br />
{{hc|nano .xprofile|<nowiki><br />
xmodmap -e 'remove mod1 = Alt_R'<br />
xmodmap -e 'keycode 108 = Hangul'<br />
xmodmap -e 'remove control = Control_R'<br />
xmodmap -e 'keycode 105 = Hangul_Hanja'</nowiki><br />
}}<br />
<br />
이제 오른쪽 alt키가 "Hangul"이라는 키로, 오른쪽 Ctrl키가 "Hangul_Hanja"라는 키로 매핑되었을 것입니다. 이제 선택한 입력기의 설정창에서 한영키를 한영 전환을 위한 단축키로, 한자키를 한자 입력을 위한 단축키로 설정하십시오. 만약 .xinitrc, .xprofile, .xsession 파일에 위의 환경변수를 추가하는 것으로 한영키나 한자키를 사용할 수 없다면, 위의 변수들을 포함한 쉘 스크립트를 작성하여 X 세션을 시작할 때마다 실행되도록 설정하십시오.<br />
<br />
===리브레오피스===<br />
<br />
리브레오피스에서 한글 입력을 할 수 없다면, {{ic|.xinitrc}}, {{ic|.xprofile}} 혹은 {{ic|.xsession}}에 다음을 추가해보십시오.<br />
{{ic|<nowiki>export OOO_FORCE_DESKTOP="gnome"</nowiki>}}</div>Jgwakhttps://wiki.archlinux.org/index.php?title=Localization_(%ED%95%9C%EA%B5%AD%EC%96%B4)/Korean_(%ED%95%9C%EA%B5%AD%EC%96%B4)&diff=529257Localization (한국어)/Korean (한국어)2018-07-10T22:32:31Z<p>Jgwak: Cleaned up archaic fonts.</p>
<hr />
<div>[[category: Internationalization (한국어)]]<br />
[[en:Internationalization/Korean]]<br />
{{Related articles start (한국어)}}<br />
{{Related|Internationalization}}<br />
{{Related articles end}}<br />
<br />
이 문서는 아치리눅스 설치 후 한국어 입력을 설정하는 방법을 다룹니다.<br />
<br />
이 문서를 읽기 전에 [[X11]] 환경을 미리 설치하고 설정하십시오. 이 문서는 콘솔에서 한국어를 입력하는 방법을 다루지 않습니다.<br />
<br />
==글꼴==<br />
<br />
한글 입력을 사용하기 위해서는 한글 글꼴이 설치되어 있어야 합니다. {{aur|ttf-nanum}} 패키지를 [[AUR]]에서 설치하십시오. 터미널 등에서 사용할 수 있는 고정폭 글꼴이 필요하다면 AUR에서 {{aur|ttf-nanumgothic_coding}} 패키지를 설치하십시오. 옛한글을 읽고 입력하기 원한다면, {{aur|ttf-unfonts-core-ibx}} 패키지를 사용하십시오.<br />
<br />
==한글 입력기 고르기==<br />
<br />
입력기 프레임워크들은 여러가지 입력기와 입력 라이브러리를 포함하여 사용중인 입력기를 쉽게 전환할 수 있도록 해줍니다. [[IBus]], [[uim]], [[fcitx]], [[scim]] 등의 입력기 프레임워크들이 한국어 입력을 지원합니다. 덧붙여, {{aur|nabi}}{{Broken package link|{{aur-mirror|nabi}}}}는 독립적인 한글 입력기로서, 다른 프레임워크를 사용하지 않습니다. 이 항목에서는 한글 입력기 선택을 돕기 위한 정보를 제공합니다.<br />
<br />
{{참고|각 입력기나 입력기 프레임워크에서 나타나는 문제들을 반드시 확인한 후에 입력기를 고르십시오.}}<br />
<br />
===입력기별 문제===<br />
<br />
;ibus: [[IBus]]는 [[GNOME]]과 우분투의 기본 입력기 프레임워크입니다. 가장 널리 지원을 받으며, 대부분의 어플리케이션에서 문제 없이 한글 입력을 할 수 있습니다. <br />
<br />
;uim: [[uim]]은 여러 언어를 지원하는 크로스 플랫폼 입력기입니다. 아치리눅스 공식 저장소의 {{pkg|uim}} 패키지에는 한국어 입력기인 uim-byeoru가 포함되어 있습니다. uim-byeoru는 구글 크롬과 크로미움을 포함한 대부분의 어플리케이션에서 문제 없이 한글 입력을 할 수 있습니다. 하지만 {{pkg|opera}} 사용자라면 opera에서 uim-byeoru를 사용하려고 할 때 opera가 충돌하는 현상이 나타날 수 있습니다.<br />
<br />
;scim: scim 혹은 [[Smart Common Input Method platform]]는 posix와 호환되는 운영체제를 위한 입력기 프레임워크입니다. 2014년 11월 현재, scim-hangul는 Google Chrome과 Chromium에서 문제를 일으킵니다. 기본 환경 변수를 사용할 경우, scim-hangul은 Google Chrome이나 Chromium에서 한글 입력을 할 수 없습니다. 2014년 현재, scim-hangul은 gedit과도 문제를 일으킵니다. 기본 환경 변수를 사용할 경우, 한글 입력기를 선택한 상태에서는 gedit에서 백스페이스가 정상적으로 작동하지 않습니다. 이 두 문제에 대한 해결 방법은 아래에서 다룹니다. 단, 아래의 해결 방법을 사용한 후에도 Google Chrome이나 Chromium에서는 입력기 버퍼 안의 글자가 사라지는 현상이 발생합니다. 즉 한글 입력 중에 스페이스바를 누르면 입력 중이던 마지막 한 글자가 사라집니다. ''현재 이 문제에 대한 해결책은 없습니다.''<br />
<br />
;fcitx: [[Fcitx]] 역시 POSIX 호환 운영체제들을 위한 입력기 프레임워크입니다. 사용하는데 문제는 없지만, GNOME을 사용한다면 탭 메뉴에서 몇 가지의 메뉴가 열리지 않습니다. 또한, Slack을 사용한다면, Electron이 입력을 무시해서 입력은 영어로밖에 입력이 되지 않습니다.<br />
<br />
;nabi: {{aur|nabi}}{{Broken package link|{{aur-mirror|nabi}}}}는 최환진 씨가 개발하는 독립적 한글 입력기입니다. 옛한글 입력 등 한글 입력에 특화된 여러 기능을 제공합니다. 한글과 영어만을 사용한다면, 나비 입력기를 설치해보십시오. 2014년 11월 현재 나비는 Google Chrome과 Chromium에서 문제를 일으킵니다. 스페이스바를 누를 경우, 입력 중이던 글자가 공백 뒤에 놓이는 현상이 나타납니다. 즉 Google Chrome에서 {{ic|한글 입력에 문제가 있습니다}}를 쳤다면, {{ic|한 글입력 에문제 가있습니다}}와 같이 입력이 됩니다. 현재 나비는 아치 리눅스에서 제공되고 있지 않습니다.<br />
<br />
;dasom: 다솜 입력기({{aur|dasom-git}})는 다국어 입력기 프레임워크 입니다. 타 입력기에서 나타나는 끝글자 버그가 다솜에서는 발생하지 않습니다. 한글 및 영문 엔진, qt4, qt5, gtk2, gtk3, XIM 모듈을 지원하며, 세벌씩 자판과 드보락 자판도 지원합니다. <br />
<br />
<br />
자신이 사용할 입력기를 골랐다면, 입력기 설정 섹션으로 넘어가십시오.<br />
<br />
==입력기 설정==<br />
<br />
===ibus-hangul===<br />
[[IBus]] 문서를 보십시오.<br />
<br />
===uim-byeoru===<br />
<br />
[[User:Isaac914/uim]]의 설명을 따라 uim을 기본 입력기로 설정하십시오. uim을 기본 입력기로 설정한 후에 이 항목으로 돌아오십시오.<br />
<br />
$ uim-pref-gtk (혹은 uim-pref-gtk3/uim-pref-qt4)<br />
명령으로 uim의 설정창을 여십시오.<br />
<br />
"Global settings"에서 ''specify default IM''(기본 입력기 설정)에 체크 표시를 하십시오. 그리고 "Byeoru"를 기본 입력기로 설정하십시오.<br />
<br />
또한, 'Edit'버튼을 눌러 사용하지 않을 입력기들을 비활성화할 수 있습니다.<br />
<br />
한글과 영어 외에 다른 언어의 입력기도 사용하며, 여러 입력 방법 사이를 빠르게 전환하고 싶다면, ''enable IM switching by hotkey'' 에 체크표시를 하고, 원하는 단축키를 설정하십시오.<br />
<br />
uim의 전역 설정을 마쳤다면, uim 설정창 왼쪽의 트리 메뉴에서 ''Byeoru''를 찾아 클릭하십시오. 여기에서 세벌식 등으로 키보드 레이아웃을 변경할 수 있습니다. Byeoru가 사용할 한자 사전 등의 기타 설정 역시 조정할 수 있습니다.<br />
<br />
이제 트리 메뉴에서 ''Byeoru'' 바로 아래에 있는 ''Byeoru Keybinding 1''에 클릭하십시오. 여기에서 한영 전환에 사용할 단축키를 설정하십시오. 위에서 입력기 전환을 위한 단축키를 선택했다면, 여기에서는 반드시 다른 단축키를 사용해야 합니다. 대부분의 한국 사용자들은 한영 전환에 {{ic|Ctrl+space}}나 {{ic|shift+space}}를 사용합니다.<br />
<br />
{{참고|오른쪽 alt키(한/영키)로 한영 전환을 하고 싶다면, [[#한영키 사용하기]] 섹션으로 가십시오.}}<br />
<br />
이제 uim-byeoru를 이용하여 한글 입력을 할 수 있을 것입니다.<br />
<br />
===scim-hangul===<br />
<br />
{{pkg|scim-hangul}} 패키지를 설치하십시오.<br />
<br />
다음을 {{ic|.xintrc}}, {{ic|.xprofile}}, {{ic|.xsession}} 파일에 추가하십시오.<br />
<br />
{{bc|<nowiki>export XMODIFIERS=@im=SCIM<br />
export GTK_IM_MODULE="xim"<br />
export QT_IM_MODULE="scim"<br />
scim -d</nowiki><br />
}}<br />
<br />
{{참고|이 문서에서 추천하는 환경변수와 [[scim]] 항목에서 추천하는 환경변수 사이에 약간의 차이가 있습니다. [[scim]]문서에서 추천하는 {{ic|<nowiki>GTK_IM_MODULE=”scim"</nowiki>}} 대신 {{ic|<nowiki>export GTK_IM_MODULE="xim"</nowiki>}}를 추가하였습니다. 이렇게 해야 Google Chrome과 Chromium에서 한글 입력이 가능해지며, gedit 등 gtk+ 3 어플리케이션에서 백스페이스를 정상적으로 사용할 수 있습니다.}}<br />
<br />
===fcitx-hangul===<br />
<br />
{{pkg|fcitx-hangul}}과 자신이 사용하는 GUI 툴킷에 알맞은 fcitx 프론트엔드 패키지를 [[Install|설치]]합니다. {{pkg|fcitx-gtk2}}, {{pkg|fcitx-gtk3}}, {{pkg|fcitx-qt4}}, {{pkg|fcitx-qt5}} 등에서 필요한 패키지를 선택하여 설치하십시오..<br />
<br />
KDE 사용자라면 {{pkg|kcm-fcitx}}를 설치하십시오. KDE 시스템 설정 안에서 fcitx를 설정할 수 있습니다.<br />
<br />
fcitx를 설치했다면, 다음을 {{ic|.xinitrc}}, {{ic|.xprofile}}, 혹은 {{ic|.xsession}}에 추가하십시오.<br />
<br />
{{bc|<nowiki>export GTK_IM_MODULE=fcitx<br />
export QT_IM_MODULE=fcitx<br />
export XMODIFIERS=@im=fcitx</nowiki><br />
}}<br />
<br />
===nabi===<br />
<br />
{{aur|nabi}}{{Broken package link|{{aur-mirror|nabi}}}} 패키지를 [[AUR]]에서 설치하십시오.<br />
<br />
나비의 최신 버전을 사용하고 싶다면, {{ic|git clone https://github.com/choehwanjin/nabi.git}} 명령을 내린 후, 터미널을 열어 복제된 git 저장소 안으로 들어갑니다. {{ic|./configure}} 스크립트를 실행하여 필요한 라이브러리가 모두 설치되었는지 확인한 후, {{ic|make}} 명령으로 나비를 컴파일하십시오. 컴파일이 끝났다면, 루트 권한으로{{ic|make install}} 명령을 내리십시오.<br />
<br />
나비를 설치했다면, {{ic|.xprofile}}, {{ic|.xinitrc}}, 혹은 {{ic|xsession}} 파일에 다음을 추가하십시오.<br />
<br />
<br />
{{bc|<nowiki>export XIM=nabi<br />
export XIM_ARGS=<br />
export XIM_PROGRAM="nabi"<br />
export XMODIFIERS="@im=nabi"<br />
export GTK_IM_MODULE=xim<br />
export QT_IM_MODULE=xim</nowiki><br />
}}<br />
<br />
X 세션을 재시작하십시오. 나비는 자동으로 시작될 것입니다. 기본 한글 키보드 레이아웃은 두벌식입니다. 세벌식, 두벌식 옛글 등 다른 키보드 레이아웃을 사용하고 싶다면 나비의 시스템 트레이 아이콘을 클릭하여 원하는 키보드 레아이웃을 선택하십시오.<br />
<br />
===dasom===<br />
{{aur|dasom-git}},{{aur|dasom-gtk-git}} ,{{aur|dasom-qt-git}} 패키지와 {{aur|dasom-jeongeum-git}} 패키지를 [[AUR]]에서 설치하십시오.<br />
<br />
설치 후, {{ic|.xprofile}} 파일에 다음을 추가하십시오.<br />
<br />
{{bc|<nowiki>export GTK_IM_MODULE=dasom<br />
export QT_IM_MODULE=dasom<br />
export XMODIFIERS="@im=dasom"<br />
dasom-daemon<br />
dasom-indicator</nowiki><br />
}}<br />
<br />
만약, [[GNOME]] 데스크탑을 사용한다면, 다음을 추가적으로 실행하십시오.<br />
{{bc|<nowiki>gsettings set org.gnome.settings-daemon.plugins.keyboard active false<br />
gsettings set org.gnome.settings-daemon.plugins.xsettings overrides "{'Gtk/IMModule':<'dasom'>}"</nowiki><br />
}}<br />
<br />
X 세션을 재시작하십시오. 다솜입력기는 자동으로 시작될 것입니다.<br />
<br />
<br />
==팁과 트릭==<br />
<br />
===한영키 사용하기===<br />
<br />
scim, nabi, uim 중 하나를 선택했다면 한영키를 이용하여 한영전환을 할 수 있습니다. 입력기를 시작하는 환경 변수 '''뒤에''' 다음 환경 변수들을 추가하십시오.<br />
<br />
{{hc|nano .xprofile|<nowiki><br />
xmodmap -e 'remove mod1 = Alt_R'<br />
xmodmap -e 'keycode 108 = Hangul'<br />
xmodmap -e 'remove control = Control_R'<br />
xmodmap -e 'keycode 105 = Hangul_Hanja'</nowiki><br />
}}<br />
<br />
이제 오른쪽 alt키가 "Hangul"이라는 키로, 오른쪽 Ctrl키가 "Hangul_Hanja"라는 키로 매핑되었을 것입니다. 이제 선택한 입력기의 설정창에서 한영키를 한영 전환을 위한 단축키로, 한자키를 한자 입력을 위한 단축키로 설정하십시오. 만약 .xinitrc, .xprofile, .xsession 파일에 위의 환경변수를 추가하는 것으로 한영키나 한자키를 사용할 수 없다면, 위의 변수들을 포함한 쉘 스크립트를 작성하여 X 세션을 시작할 때마다 실행되도록 설정하십시오.<br />
<br />
===리브레오피스===<br />
<br />
리브레오피스에서 한글 입력을 할 수 없다면, {{ic|.xinitrc}}, {{ic|.xprofile}} 혹은 {{ic|.xsession}}에 다음을 추가해보십시오.<br />
{{ic|<nowiki>export OOO_FORCE_DESKTOP="gnome"</nowiki>}}</div>Jgwakhttps://wiki.archlinux.org/index.php?title=Localization/Korean&diff=529256Localization/Korean2018-07-10T22:30:00Z<p>Jgwak: Cleaned up archaic font lists.</p>
<hr />
<div>[[category: Internationalization]]<br />
[[ko:Internationalization/Korean]]<br />
{{Related articles start}}<br />
{{Related|Internationalization}}<br />
{{Related articles end}}<br />
<br />
This article describes how to set up a Korean language environment. It does not cover setting up Korean input on the console. <br />
<br />
==Fonts==<br />
<br />
To use any Korean input method, you need to have Korean fonts installed. Install {{AUR|ttf-nanum}} from the [[AUR]]. If you also want Korean monospaced fonts, install {{AUR|ttf-nanumgothic_coding}} from the AUR. If you want to view and use Yethangul(옛한글), install {{aur|ttf-unfonts-core-ibx}} font.<br />
<br />
See also [[Fonts#Korean]].<br />
<br />
== Locale ==<br />
<br />
You should have {{ic|ko_KR.UTF-8}} enabled in {{ic|/etc/locale.gen}}. It is recommended that you always use a {{ic|.UTF-8}} locale rather than the {{ic|ko_KR.EUC-KR}} locale. For more information, read [[locale]].<br />
<br />
== Input methods ==<br />
<br />
The following [[input method]]s are available for Korean:<br />
<br />
* {{Pkg|fcitx-hangul}} for [[Fcitx]]<br />
* {{Pkg|ibus-hangul}} for [[IBus]]<br />
* {{Pkg|scim-hangul}} for [[SCIM]]<br />
* ''uim-byeoru'' of [[uim]]<br />
* [[#Nabi]]<br />
<br />
===Configuration===<br />
<br />
==== Nabi ====<br />
<br />
[https://github.com/libhangul/nabi Nabi] is a standalone Korean input method, developed by Choe Hwanjin, offering many unique features, such as Yethangul support.<br />
<br />
[[Install]] the {{AUR|nabi-git}} package.<br />
<br />
Once you have finished the installation, add the following to [[xprofile]], [[xinitrc]], or {{ic|xsession}}:<br />
<br />
export XIM=nabi<br />
export XIM_ARGS=<br />
export XIM_PROGRAM="nabi"<br />
export XMODIFIERS="@im=nabi"<br />
export GTK_IM_MODULE=xim<br />
export QT_IM_MODULE=xim<br />
<br />
Once you restart the X session, nabi will autostart by default. The default Korean keyboard layout is Dubeolsik(두벌식). If you need a different Korean keyboard layout (e.g. Sebeolsik or Dubeolsik Yetgul), click on the system tray icon of nabi, and select a input method from the menu that pops up.<br />
<br />
====scim-hangul====<br />
<br />
[[Install]] {{Pkg|scim-hangul}}. <br />
<br />
Now add the following to the user's {{ic|.xinitrc}}, {{ic|.xprofile}}, or {{ic|.xsession}}:<br />
<br />
export XMODIFIERS=@im=SCIM<br />
export GTK_IM_MODULE="xim"<br />
export QT_IM_MODULE="scim"<br />
scim -d<br />
<br />
{{note|The above environment variables differ slightly from the ones recommended in the [[scim]] article. We are adding {{ic|<nowiki>export GTK_IM_MODULE="xim"</nowiki>}} instead of {{ic|<nowiki>GTK_IM_MODULE=”scim"</nowiki>}}. This allows us to input Korean in apps such as Chrome and Chromium (though with issues discussed above), and to use backspace properly in GTK+3 applications such as gedit.}}<br />
<br />
====uim-byeoru====<br />
<br />
Follow the instructions in [[User:Isaac914/uim]] to install uim and to get it running. Return to this section after uim is installed and running as the default input method.<br />
<br />
Open the uim preferences window by running :<br />
<br />
$ uim-pref-gtk (Or, uim-pref-gtk3/uim-pref-qt4)<br />
<br />
Within global settings, check on the ''Specify default IM'' checkbox. Then, set ''Byeoru'' as default. You may also want to disable input methods that you do not plan on using by clicking on the 'edit' button. If you want to quickly switch between Korean and other languages (other than English), check the ''enable IM switching by hotkey'' checkbox, and set a hotkey to switch between enabled IMEs.<br />
<br />
When you are done with the global preferences, find ''Byeoru'' in the tree menu on the left side of the preferences window. From there, you can set the Korean keyboard layout you want to use (e.g. {{ic|3 beol}}), specify the korean/Hanja dictionary that Byeoru will use, and other miscellaneous settings. Then, click on ''Byeoru Keybinding 1'' in the tree menu. Set the hotkey you want to use to enable/disable Byeoru. Most Korean users use {{ic|Ctrl+space}} or {{ic|shift+space}}.<br />
<br />
{{Note|If you want to use the right {{ic|Alt}} key to switch from Korean to English and vice versa, go to the [[#Using the Right alt key to switch input methods]] section.}}<br />
<br />
If all went properly, you should now be able to use UIM-byeoru to type in Korean.<br />
<br />
=== Troubleshooting ===<br />
<br />
{{Accuracy|These issues were apparently experienced November 2014, they should be rechecked, reported to upstream if still present and their bug report linked here.}}<br />
<br />
;[[IBus]]:As of November 2014, IBus sometimes doesn't recognize user-set hotkeys for IM switching. This means that you may need to click on the IBus systray icon every time to want to switch input methods.<br />
<br />
;[[uim]]:''uim-byeoru'' may cause [[Opera]] to crash.<br />
<br />
;scim: scim-hangul, as of November 2014, has issues with Google Chrome and [[Chromium]] web browsers. With the default environment variables, you cannot input Korean in Google Chrome or Chromium. scim also causes problems in Gedit as of November 2014. When scim-hangul is active, pressing {{ic|backspace}} does not work properly. A workaround for both these issues will be explained in [[#scim-hangul]]. However, even with this workaround applied, Chrome/Chromium users may find that the preedit string disappears when the spacebar or any other modifier key is pressed. ''There is currently no known workaround for this issue.''<br />
<br />
;fcitx:Fcitx-hangul has issues with Google Chrome and Chromium. Some users have reported that fcitx only recognizes Google Chrome/Chromium's URL bar as an input window only after their themes have been changed.<br />
<br />
;nabi: {{AUR|nabi-git}} is a standalone Korean input method that is being developed by Choehwanjin. Nabi provides many unique features, such as Yethangul support. If you only need to use Korean and English input, you may want to install nabi. Currently, nabi causes an issue with chromium. When you press the spacebar, the preedit string will be placed after the space, causing your input to look like this: {{ic|한 글입력 에문제 가있습니다}}<br />
<br />
====Libreoffice====<br />
<br />
In some cases, Libreoffice will not take Korean input from any input method. To resolve this issue, try adding {{ic|1=export OOO_FORCE_DESKTOP="gnome"}} to {{ic|.xinitrc}}, {{ic|.xprofile}}, or {{ic|.xsession}}.<br />
<br />
===Tips and Tricks===<br />
<br />
====Using the Right alt key to switch input methods====<br />
You can use the right {{ic|Alt}} key (e.g. '한/영키') to switch between Input methods if you are using uim, scim, or nabi. To do this, add the following lines '''after''' the environment variables that start your input method:<br />
<br />
{{hc|~/.xprofile|<nowiki><br />
xmodmap -e 'remove mod1 = Alt_R'<br />
xmodmap -e 'keycode 108 = Hangul'<br />
xmodmap -e 'remove control = Control_R'<br />
xmodmap -e 'keycode 105 = Hangul_Hanja'</nowiki><br />
}}<br />
<br />
Then, in the settings of your input method, add the right {{ic|Alt}} key as a hotkey to switch IMEs. The right {{ic|Alt}} key has been remapped to a non-modifier key called "Hangul". The script above also allows you to use the right {{ic|Ctrl}} key (e.g. '한자키') to activate Hanja input. The right {{ic|Ctrl}} key should also have been remapped to "Hangul_Hanja". Add this key as a Hanja hotkey within the settings of your input method. If adding that to your {{ic|.xprofile}} or {{ic|.xinitrc}} file did not work, create a script containing those four lines and set it to auto execute when your desktop environment starts up.</div>Jgwakhttps://wiki.archlinux.org/index.php?title=Fonts&diff=529255Fonts2018-07-10T22:20:11Z<p>Jgwak: Add more Korean fonts.</p>
<hr />
<div>[[Category:Fonts]]<br />
[[cs:Fonts]]<br />
[[de:Schriftarten]]<br />
[[es:Fonts]]<br />
[[it:Fonts]]<br />
[[ja:フォント]]<br />
[[ru:Fonts]]<br />
[[zh-hans:Fonts]]<br />
[[zh-hant:Fonts]]<br />
{{Related articles start}}<br />
{{Related|Font configuration}}<br />
{{Related|Java Runtime Environment Fonts}}<br />
{{Related|Metric-compatible fonts}}<br />
{{Related articles end}}<br />
<br />
From [[Wikipedia:Computer font]]: "A computer font (or font) is an electronic data file containing a set of glyphs, characters, or symbols such as dingbats."<br />
<br />
Note that certain font licenses may impose some legal limitations.<br />
<br />
== Font formats ==<br />
<br />
Most computer fonts used today are in either ''bitmap'' or ''outline'' data formats. <br />
;Bitmap fonts: Consist of a matrix of dots or pixels representing the image of each glyph in each face and size.<br />
;Outline or ''vector'' fonts: Use Bézier curves, drawing instructions and mathematical formulae to describe each glyph, which make the character outlines scalable to any size.<br />
<br />
=== Bitmap formats ===<br />
<br />
* [[Wikipedia:Glyph Bitmap Distribution Format|Bitmap Distribution Format]] (BDF) by Adobe<br />
* [[Wikipedia:Portable Compiled Format|Portable Compiled Format]] (PCF) by Xorg<br />
* [[Wikipedia:PC Screen Font|PC Screen Font]] (PSF) used by the Kernel for console fonts, not supported by Xorg (for Unicode PSF files the extension is {{ic|psfu}})<br />
<br />
These formats can also be gzipped. See [[#Bitmap]] for the available bitmap fonts.<br />
<br />
=== Outline formats ===<br />
<br />
* [[Wikipedia:PostScript fonts|PostScript fonts]] by Adobe – has various formats, e.g: Printer Font ASCII (PFA) and Printer Font Binary (PFB)<br />
* [[Wikipedia:TrueType|TrueType]] by Apple and Microsoft (file extension: {{ic|ttf}})<br />
* [[Wikipedia:OpenType|OpenType]] by Microsoft, built on TrueType (file extensions: {{ic|otf}}, {{ic|ttf}})<br />
<br />
For most purposes, the technical differences between TrueType and OpenType can be ignored.<br />
<br />
=== Other formats ===<br />
<br />
The typesetting application, ''TeX,'' and its companion font software, ''Metafont,'' render characters using their own methods. Some of the file extensions used for fonts by these two programs are {{ic|*pk}}, {{ic|*gf}}, {{ic|mf}} and {{ic|vf}}.<br />
<br />
[https://fontforge.github.io/en-US/ FontForge] ({{Pkg|fontforge}}), a font editing application, can store fonts in its native text-based format, {{ic|sfd}}, ''s''pline ''f''ont ''d''atabase.<br />
<br />
The [http://www.w3.org/TR/SVG/fonts.html SVG] format also has its own font description method.<br />
<br />
== Installation ==<br />
<br />
There are various methods for installing fonts.<br />
<br />
=== Pacman ===<br />
<br />
Fonts and font collections in the enabled repositories can be installed using [[pacman]].<br />
<br />
Available fonts may be found by [[pacman#Querying package databases|querying packages]] (e.g. for {{ic|font}} or {{ic|ttf}}).<br />
<br />
=== Creating a package ===<br />
<br />
You should give pacman the ability to manage your fonts, which is done by creating an Arch package. These can also be shared with the community in the [[AUR]]. The packages to install fonts are particularly similar; simply taking an existing [https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/adobe-source-code-pro-fonts package] as template should work well. To learn about how to modify it for your font, please refer to [[Creating packages]].<br />
<br />
The family name of a font file can be aquired with the use of {{ic|fc-query}} for example: {{ic|fc-query -f '%{family[0]}\n' /path/to/file}}. The formatting is described in the FcPatternFormat(3) manual.<br />
<br />
=== Manual installation ===<br />
<br />
The recommended way of adding fonts that are not in the repositories to your system is described in [[#Creating a package]]. This gives pacman the ability to remove or update them at a later time. Fonts can alternately be installed manually as well.<br />
<br />
To install fonts system-wide (available for all users), move the folder to the {{ic|/usr/share/fonts/}} directory. The files need to be readable by every user, use [[chmod]] to set the correct permissions (i.e. at least {{ic|0444}} for files and {{ic|0555}} for directories). To install fonts for only a single user, use {{ic|~/.local/share/fonts}} ({{ic|~/.fonts/}} is now deprecated).<br />
<br />
For Xserver to load fonts directly (as opposed to the use of a ''font server'') the directory for your newly added font must be added with a FontPath entry. This entry is located in the ''Files'' section [[Xorg#Configuration|of your Xorg configuration file]] (e.g. {{ic|/etc/X11/xorg.conf}} or {{ic|/etc/xorg.conf}}). See [[#Older applications]] for more detail.<br />
<br />
Then update the fontconfig font cache: (usually unnecessary as software using the fontconfig library do this.)<br />
<br />
$ fc-cache<br />
<br />
=== Older applications ===<br />
<br />
With older applications that do not support fontconfig (e.g. GTK+ 1.x applications, and {{ic|xfontsel}}) the index will need to be created in the font directory:<br />
<br />
$ mkfontscale<br />
$ mkfontdir<br />
<br />
Or to include more than one folder with one command:<br />
<br />
$ for dir in /font/dir1/ /font/dir2/; do xset +fp $dir; done && xset fp rehash<br />
<br />
Or if fonts were installed in a different sub-folders under the e.g. {{ic|/usr/share/fonts}}:<br />
<br />
$ for dir in * ; do if [ -d "$dir" ]; then cd "$dir";xset +fp "$PWD" ;mkfontscale; mkfontdir;cd .. ;fi; done && xset fp rehash<br />
<br />
At times the X server may fail to load the fonts directory and you will need to rescan all the {{ic|fonts.dir}} files:<br />
<br />
# xset +fp /usr/share/fonts/misc # Inform the X server of new directories<br />
# xset fp rehash # Forces a new rescan<br />
<br />
To check that the font(s) is included:<br />
<br />
$ xlsfonts | grep fontname<br />
<br />
{{note|Many packages will automatically configure Xorg to use the font upon installation. If that is the case with your font, this step is not necessary.}}<br />
<br />
This can also be set globally in {{ic|/etc/X11/xorg.conf}} or {{ic|/etc/X11/xorg.conf.d}}.<br />
<br />
Here is an example of the section that must be added to {{ic|/etc/X11/xorg.conf}}. Add or remove paths based on your particular font requirements.<br />
<br />
# Let X.Org know about the custom font directories<br />
Section "Files"<br />
FontPath "/usr/share/fonts/100dpi"<br />
FontPath "/usr/share/fonts/75dpi"<br />
FontPath "/usr/share/fonts/cantarell"<br />
FontPath "/usr/share/fonts/cyrillic"<br />
FontPath "/usr/share/fonts/encodings"<br />
FontPath "/usr/share/fonts/misc"<br />
FontPath "/usr/share/fonts/truetype"<br />
FontPath "/usr/share/fonts/TTF"<br />
FontPath "/usr/share/fonts/util"<br />
EndSection<br />
<br />
=== Pango Warnings ===<br />
<br />
When [http://www.pango.org/ Pango] is in use on your system it will read from [http://www.freedesktop.org/wiki/Software/fontconfig fontconfig] to sort out where to source fonts.<br />
<br />
(process:5741): Pango-WARNING **: failed to choose a font, expect ugly output. engine-type='PangoRenderFc', script='common'<br />
(process:5741): Pango-WARNING **: failed to choose a font, expect ugly output. engine-type='PangoRenderFc', script='latin'<br />
<br />
If you are seeing errors similar to this and/or seeing blocks instead of characters in your application then you need to add fonts and update the font cache. This example uses the {{Pkg|ttf-liberation}} fonts to illustrate the solution (after successful installation of the package) and runs as root to enable them system-wide.<br />
<br />
# fc-cache<br />
/usr/share/fonts: caching, new cache contents: 0 fonts, 3 dirs<br />
/usr/share/fonts/TTF: caching, new cache contents: 16 fonts, 0 dirs<br />
/usr/share/fonts/encodings: caching, new cache contents: 0 fonts, 1 dirs<br />
/usr/share/fonts/encodings/large: caching, new cache contents: 0 fonts, 0 dirs<br />
/usr/share/fonts/util: caching, new cache contents: 0 fonts, 0 dirs<br />
/var/cache/fontconfig: cleaning cache directory<br />
fc-cache: succeeded<br />
<br />
You can test for a default font being set like so:<br />
<br />
# fc-match<br />
LiberationMono-Regular.ttf: "Liberation Mono" "Regular"<br />
<br />
== Console fonts ==<br />
<br />
{{Note|This section is about the [[Wikipedia:Linux console|Linux console]]. For alternative console solutions offering more features (full Unicode fonts, modern graphics adapters etc.), see [[fbterm]], [[KMSCON]] or similar projects.}}<br />
<br />
By default, the [[Wikipedia:Virtual console|virtual console]] uses the kernel built-in font with a [[Wikipedia:CP437|CP437]] character set,<sup>[https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/tty/vt/Makefile#n4]</sup> but this can be easily changed.<br />
<br />
The [[Wikipedia:Linux console|Linux console]] uses UTF-8 encoding by default, but because the standard VGA-compatible framebuffer is used, a console font is limited to either a standard 256, or 512 glyphs. If the font has more than 256 glyphs, the number of colours is reduced from 16 to 8. In order to assign correct symbol to be displayed to the given Unicode value, a special translation map, often called ''unimap'', is needed. Nowadays most of the console fonts have the ''unimap'' built-in; historically, it had to be loaded separately.<br />
<br />
The {{Pkg|kbd}} package provides tools to change virtual console font and font mapping. Available fonts are saved in the {{ic|/usr/share/kbd/consolefonts/}} directory, those ending with ''.psfu'' or ''.psfu.gz'' have a Unicode translation map built-in.<br />
<br />
Keymaps, the connection between the key pressed and the character used by the computer, are found in the subdirectories of {{ic|/usr/share/kbd/keymaps/}}, see [[Keyboard configuration in console]] for details.<br />
<br />
{{Note|Replacing the font can cause issues with programs that expect a standard VGA-style font, such as those using line drawing graphics.}}<br />
<br />
{{Tip|For European based languages written in Latin/Greek letters you can use {{ic|eurlatgr}} font, it includes a broad range of Latin/Greek letter variations as well as<br />
special characters [https://lists.altlinux.org/pipermail/kbd/2014-February/000439.html].}}<br />
<br />
=== Preview and temporary changes ===<br />
<br />
{{Tip|An organized library of images for previewing is available: [http://alexandre.deverteuil.net/pages/consolefonts/ Linux console fonts screenshots].}}<br />
<br />
$ showconsolefont<br />
<br />
shows a table of glyphs or letters of a font.<br />
<br />
{{ic|setfont}} temporarily change the font if passed a font name (in {{ic|/usr/share/kbd/consolefonts/}}) such as<br />
<br />
$ setfont lat2-16 -m 8859-2<br />
<br />
Font names are case-sensitive. With no parameter, {{ic|setfont}} returns the console to the default font.<br />
<br />
{{Tip|All font changing commands can be typed in "blind".}}<br />
<br />
{{Note|''setfont'' only works on the console currently being used. Any other consoles, active or inactive, remain unaffected.}}<br />
<br />
=== Persistent configuration ===<br />
<br />
The {{ic|FONT}} variable in {{ic|/etc/vconsole.conf}} is used to set the font at boot, persistently for all consoles. See {{man|5|vconsole.conf}} for details.<br />
<br />
For displaying characters such as ''Č, ž, đ, š'' or ''Ł, ę, ą, ś'' using the font {{ic|lat2-16.psfu.gz}}:<br />
<br />
{{hc|/etc/vconsole.conf|2=<br />
...<br />
FONT=lat2-16<br />
FONT_MAP=8859-2<br />
}}<br />
<br />
It means that second part of ISO/IEC 8859 characters are used with size 16. You can change font size using other values (e.g. {{ic|lat2-08}}). For the regions determined by 8859 specification, look at the [[Wikipedia:ISO/IEC 8859#The parts of ISO/IEC 8859]].<br />
<br />
To use the specified font in early userspace, use the {{ic|consolefont}} hook in {{ic|/etc/mkinitcpio.conf}}. See [[Mkinitcpio#HOOKS]] for more information. <br />
<br />
If the fonts seems to not change on boot, or change only temporarily, it is most likely that they got reset when graphics driver was initialized and console was switched to framebuffer. To avoid this, load your graphics driver earlier. See for example [[Kernel mode setting#Early KMS start]], [https://bbs.archlinux.org/viewtopic.php?id=145765] or other ways to setup your framebuffer before {{ic|/etc/vconsole.conf}} is applied.<br />
<br />
== Font packages ==<br />
<br />
This is a selective list that includes many font packages from the [[AUR]] along with those in the official repositories. Fonts are tagged "Unicode" if they have wide Unicode support, see the project or <br />
Wikipedia pages for detail.<br />
<br />
The [https://github.com/ternstor/distrofonts Archfonts Python script] can be used to generate an overview of all the TTF fonts found in the official repositories / the AUR (the image generation is done using {{AUR|ttf2png}}).<br />
<br />
=== Bitmap ===<br />
<br />
* Default 8x16<br />
* [http://www.dcmembers.com/jibsen/download/61/ Dina] ({{Pkg|dina-font}}) – 6pt, 8pt, 9pt, 10pt, monospaced, based on Proggy<br />
* [http://openlab.jp/efont/unicode/ Efont] ({{AUR|efont-unicode-bdf}}) – 10px, 12px, 14px, 16px, 24px, normal, bold and italic<br />
* [http://font.gohu.org/ Gohu] ({{AUR|gohufont}}) – 11px, 14px, normal and bold<br />
* [http://artwizaleczapka.sourceforge.net/ Lime] ({{Pkg|artwiz-fonts}})<br />
* [http://tobiasjung.name/profont/ ProFont] ({{Pkg|profont}}) – 10px, 11px, 12px, 15px, 17px, 22px, 29px, normal<br />
* [[Wikipedia:Proggy programming fonts|Proggy]] ({{AUR|proggyfonts}}) – has different variants<br />
* [http://www.fial.com/~scott/tamsyn-font/ Tamsyn] ({{Pkg|tamsyn-font}})<br />
* [http://terminus-font.sourceforge.net/ Terminus] ({{Pkg|terminus-font}})<br />
* [https://github.com/lucy/tewi-font Tewi] ({{AUR|bdf-tewi-git}})<br />
* [http://unifoundry.com/unifont.html Unifont] ([[Wikipedia:Unicode font#Comparison of fonts|most extensive]] Unicode coverage of any font) ({{Pkg|bdf-unifont}})<br />
<br />
=== Latin script ===<br />
<br />
==== Families ====<br />
<br />
* [[Wikipedia:Luxi fonts|Luxi fonts]] ({{Pkg|font-bh-ttf}}) – X.Org Luxi fonts<br />
* [[Wikipedia:Bitstream Vera|Bitstream Vera]] ({{Pkg|ttf-bitstream-vera}}) – serif, sans-serif, and monospace<br />
* [https://quoteunquoteapps.com/courierprime/ Courier Prime] ({{AUR|ttf-courier-prime}}) – Courier font alternative optimized for screenplays<br />
* [[Wikipedia:Croscore fonts|Croscore fonts]] ({{Pkg|ttf-croscore}}) – Google's substitute for Windows' Arial, Times New Roman, and Courier New<br />
* [[Wikipedia:DejaVu fonts|DejaVu fonts]] ({{Pkg|ttf-dejavu}}) – Bitstream Vera modified for greater Unicode coverage<br />
* [[Wikipedia:Droid (font)|Droid]] ({{Pkg|ttf-droid}}, included in {{AUR|ttf-google-fonts-git}}) – default font for older Android versions<br />
* [[Wikipedia:Roboto|Roboto]] ({{Pkg|ttf-roboto}}) – default font for newer Android versions<br />
* [[Wikipedia:Noto fonts|Google Noto]] ({{Pkg|noto-fonts}}) – Unicode<br />
* [[Wikipedia:Liberation fonts|Liberation fonts]] ({{Pkg|ttf-liberation}}) – free metric-compatible substitute for the Arial, Arial Narrow, Times New Roman and Courier New fonts found in Windows and Microsoft Office products<br />
* [[Wikipedia:Ubuntu Font Family|Ubuntu Font Family]] ({{Pkg|ttf-ubuntu-font-family}})<br />
* [[Microsoft fonts]] ({{AUR|ttf-ms-win10}}) – Windows 10 fonts<br />
Legacy Microsoft font packages:<br />
* [http://corefonts.sourceforge.net/ Microsoft fonts] ({{AUR|ttf-ms-fonts}}) – Andalé Mono, Courier New, Arial, Arial Black, Comic Sans, Impact, Lucida Sans, Microsoft Sans Serif, Trebuchet, Verdana, Georgia, Times New Roman<br />
* Vista fonts ({{AUR|ttf-vista-fonts}}) – Consolas, Calibri, Candara, Corbel, Cambria, Constantia<br />
<br />
==== Monospaced ====<br />
<br />
For more monospaced fonts see [[#Bitmap]] and [[#Families]].<br />
<br />
* [http://www.marksimonson.com/fonts/view/anonymous-pro Anonymous Pro] ({{pkg|ttf-anonymous-pro}}, included in {{AUR|ttf-google-fonts-git}})<br />
* [https://damieng.com/blog/2008/05/26/envy-code-r-preview-7-coding-font-released Envy Code R] ({{AUR|ttf-envy-code-r}})<br />
* Fantasque Sans Mono ({{AUR|ttf-fantasque-sans-git}})<br />
* [[Wikipedia:Fira Sans|Fira Mono]] ({{pkg|ttf-fira-mono}}, {{pkg|otf-fira-mono}}) – designed for Firefox OS<br />
* [[Wikipedia:GNU FreeFont|FreeMono]] ({{Pkg|ttf-freefont}}) - Unicode<br />
* [https://sourcefoundry.org/hack/ Hack] ({{pkg|ttf-hack}}) - an open source monospaced font, used as the default in KDE Plasma<br />
* [[Wikipedia:Inconsolata|Inconsolata]] ({{Pkg|ttf-inconsolata}}, included in {{AUR|ttf-google-fonts-git}}) - inspired by Consolas<br />
* [https://leonardo-m.livejournal.com/77079.html Inconsolata-g] ({{AUR|ttf-inconsolata-g}}) - adds some programmer-friendly modifications<br />
* [[Wikipedia:Lucida Typewriter|Lucida Typewriter]] (included in package {{AUR|jre}})<br />
* [[Wikipedia:Menlo (typeface)|Menlo]] (derivative: {{AUR|ttf-meslo}}) - default monospaced font of OS X<br />
* [[Wikipedia:Monaco (typeface)|Monaco]] ({{AUR|ttf-monaco}}) - proprietary font designed by Apple for OS X<br />
* Monofur ({{AUR|ttf-monofur}})<br />
* [https://madmalik.github.io/mononoki Mononoki] ({{AUR|ttf-mononoki}})<br />
* [[Wikipedia:Source_Code_Pro|Source Code Pro]] ({{pkg|adobe-source-code-pro-fonts}})<br />
<br />
Relevant websites:<br />
<br />
* [http://hivelogic.com/articles/top-10-programming-fonts Dan Benjamin's Top 10 Programming Fonts].<br />
* [http://www.lowing.org/fonts/ Trevor Lowing's font list]<br />
* [https://www.slant.co/topics/67/~what-are-the-best-programming-fonts Slant: What are the best programming fonts?]<br />
* [https://stackoverflow.com/questions/4689/recommended-fonts-for-programming Stack Overflow: Recommended fonts for programming]<br />
<br />
==== Sans-serif ====<br />
<br />
* [http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&id=andika Andika] ({{AUR|ttf-andika}})<br />
* [[Wikipedia:GNU FreeFont|FreeSans]] ({{Pkg|ttf-freefont}}) - Unicode<br />
* [https://github.com/rsms/inter Inter UI] ({{AUR|ttf-inter-ui}}) – designed for user interfaces<br />
* [[Wikipedia:Linux Libertine|Linux Biolinum]] ({{Pkg|ttf-linux-libertine}}) – free substitute for Times New Roman<br />
* [[Wikipedia:PT Sans|PT Sans]] ({{AUR|ttf-google-fonts-git}}) - 3 major variations: normal, narrow, and caption - Unicode: Latin, Cyrillic<br />
* [[Wikipedia:Source Sans Pro|Source Sans Pro]] ({{pkg|adobe-source-sans-pro-fonts}})<br />
* [[Wikipedia:Tahoma (typeface)|Tahoma]] ({{AUR|ttf-tahoma}})<br />
<br />
==== Serif ====<br />
<br />
* [http://www.georgduffner.at/ebgaramond/ EB Garamond] ({{AUR|otf-eb-garamond}})<br />
* [[Wikipedia:GNU FreeFont|FreeSerif]] ({{Pkg|ttf-freefont}}) - Unicode<br />
* [[Wikipedia:Gentium|Gentium]] ({{Pkg|ttf-gentium}}) - Unicode: Latin, Greek, Cyrillic, Phonetic Alphabet<br />
* [[Wikipedia:Linux Libertine|Linux Libertine]] ({{Pkg|ttf-linux-libertine}}) - Unicode: Latin, Greek, Cyrillic, Hebrew<br />
<br />
==== Unsorted ====<br />
<br />
{{Style|This section should be absorbed into the Monospace/Serif/Sans-Serif structure}}<br />
<br />
* {{Pkg|ttf-cheapskate}} - Font collection from ''dustismo.com''<br />
* {{Pkg|ttf-junicode}} - Junius font containing almost complete medieval latin script glyphs<br />
* {{Pkg|ttf-mph-2b-damase}} - Covers full plane 1 and several scripts<br />
* {{Pkg|xorg-fonts-type1}} - IBM Courier and Adobe Utopia sets of [[Wikipedia:PostScript fonts|PostScript fonts]]<br />
* {{AUR|all-repository-fonts}} - Meta package for all fonts in the official repositories.<br />
* {{AUR|ttf-google-fonts-git}} - a huge collection of free fonts (including Ubuntu, Inconsolata, Droid, etc.) - Note: Your font dialog might get very long as >100 fonts will be added.<br />
<br />
=== Non-latin scripts ===<br />
<br />
==== Ancient Scripts ====<br />
<br />
* {{AUR|ttf-ancient-fonts}} - Font containing Unicode symbols for Aegean, Egyptian, Cuneiform, Anatolian, Maya, and Analecta scripts<br />
<br />
==== Arabic ====<br />
<br />
* {{AUR|ttf-amiri}} - A classical Arabic typeface in Naskh style poineered by Amiria Press<br />
* {{AUR|ttf-arabeyes-fonts}} - Collection of free Arabic fonts<br />
* {{AUR|ttf-qurancomplex-fonts}} - Fonts by King Fahd Glorious Quran Printing Complex in al-Madinah al-Munawwarah<br />
* {{AUR|ttf-sil-lateef}} - Unicode Arabic font from SIL<br />
* {{AUR|ttf-sil-scheherazade}} - Unicode Arabic font from SIL<br />
<br />
==== Braille ====<br />
<br />
*{{Pkg|ttf-ubraille}} - Font containing Unicode symbols for ''braille''<br />
<br />
==== Chinese, Japanese, Korean, Vietnamese ====<br />
<br />
===== Pan-CJK =====<br />
*adobe source han fonts - Large collection of fonts which comprehensively support Simplified Chinese, Traditional Chinese, Japanese, and Korean, with a consistent design and look.<br />
**{{Pkg|adobe-source-han-sans-otc-fonts}} - Sans fonts<br />
**{{Pkg|adobe-source-han-serif-otc-fonts}} - Serif fonts<br />
<br />
*{{Pkg|noto-fonts-cjk}} - Large collection of fonts which comprehensively support Simplified Chinese, Traditional Chinese, Japanese, and Korean, with a consistent design and look. It is currently a rebadged version of {{Pkg|adobe-source-han-sans-otc-fonts}}.<br />
<br />
===== Chinese =====<br />
<br />
{{Move|Internationalization/Chinese#Fonts|It makes sense to group language-specific things together.}}<br />
<br />
* adobe source han fonts<br />
** {{Pkg|adobe-source-han-sans-cn-fonts}} - Simplified Chinese OpenType/CFF Sans fonts<br />
** {{Pkg|adobe-source-han-sans-tw-fonts}} - Traditional Chinese OpenType/CFF Sans fonts<br />
** {{Pkg|adobe-source-han-serif-cn-fonts}} - Simplified Chinese OpenType/CFF Serif fonts<br />
** {{Pkg|adobe-source-han-serif-tw-fonts}} - Traditional Chinese OpenType/CFF Serif fonts<br />
<br />
* noto Chinese fonts<br />
** {{AUR|noto-fonts-sc}} - Noto CJK-SC fonts for Simplified Chinese<br />
** {{AUR|noto-fonts-tc}} - Noto CJK-TC fonts for Traditional Chinese<br />
<br />
* wqy fonts<br />
** {{Pkg|wqy-microhei}} - WenQuanYi Micro Hei font family (also known as Hei, Gothic or Dotum) is a sans-serif style derived from Droid Sans Fallback, it offers high quality CJK outline font and it is extremely compact (~5M).<br />
** {{Pkg|wqy-zenhei}} - Hei Ti Style (sans-serif) Chinese Outline font embedded with bitmapped Song Ti (also supporting Japanese (partial) and Korean characters).<br />
** {{Pkg|wqy-bitmapfont}} - Bitmapped Song Ti (serif) Chinese font.<br />
<br />
* arphic fonts<br />
** {{Pkg|ttf-arphic-ukai}} - ''Kaiti'' (brush stroke) Unicode font (enabling anti-aliasing is suggested)<br />
** {{Pkg|ttf-arphic-uming}} - ''Mingti'' (printed) Unicode font<br />
<br />
* {{Pkg|opendesktop-fonts}} - ''New Sung'' font, previously is ttf-fireflysung package<br />
<br />
* {{Pkg|ttf-hannom}} - Chinese and Vietnamese ttf fonts<br />
<br />
* Standart fonts of the Republic of China ministry of education in Taiwan<br />
** {{AUR|ttf-tw}} - Kai and Song traditional Chinese font from the Ministry of Education of Taiwan<br />
** {{AUR|ttf-twcns-fonts}} Chinese TrueType fonts by Ministry of Education of Taiwan government, support CNS11643 standard, including Kai and Sung fontface.<br />
<br />
*Windows Chinese fonts<br />
**{{AUR|ttf-ms-win8-zh_cn}} - windows8 simple Chinese fonts。<br />
**{{AUR|ttf-ms-win8-zh_tw}} - windows8 traditional Chinese fonts。<br />
**{{AUR|ttf-ms-win10-zh_cn}} - windows10 simple Chinese fonts。<br />
**{{AUR|ttf-ms-win10-zh_tw}} - windows10 traditional Chinese fonts。<br />
<br />
* {{AUR|ttf-i.bming}} - CJK serif font that emphasis on an old-style typeface.<br />
<br />
===== Japanese =====<br />
<br />
{{Move|Internationalization/Japanese#Fonts|It makes sense to group language-specific things together.}}<br />
<br />
* {{Pkg|adobe-source-han-sans-jp-fonts}} - Japanese OpenType/CFF fonts<br />
* {{Pkg|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.<br />
* {{Pkg|ttf-hanazono}} - A free Japanese kanji font, style Mincho (serif).<br />
* {{Pkg|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.<br />
* {{AUR|ttf-koruri}} - Japanese TrueType font obtained by mixing {{AUR|ttf-mplus}} and Open Sans<br />
* {{AUR|ttf-monapo}} - Japanese fonts to show [[wikipedia:2channel_Shift_JIS_art|2channel Shift JIS art]] properly.<br />
* {{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).<br />
* {{AUR|ttf-vlgothic}} - Japanese Gothic fonts. Default of Debian/Fedora/Vine Linux<br />
<br />
===== Korean =====<br />
<br />
{{Move|Internationalization/Korean#Fonts|It makes sense to group language-specific things together.}}<br />
<br />
* {{Pkg|adobe-source-han-sans-kr-fonts}} - Korean OpenType/CFF fonts<br />
* {{Pkg|ttf-baekmuk}} - Collection of Korean TrueType fonts<br />
* {{AUR|spoqa-han-sans}} - Source Han Sans customized by Spoqa<br />
* {{AUR|ttf-d2coding}} - D2Coding fixed width TrueType font made by Naver<br />
* {{AUR|ttf-nanum}} - Nanum series TrueType fonts<br />
* {{AUR|ttf-nanumgothic_coding}} - Nanum series fixed width TrueType fonts<br />
* {{AUR|ttf-kopub}}/{{AUR|otf-kopub}} - Korean TrueType/OpenType fonts by Korea Publisher Society<br />
* {{AUR|ttf-unfonts-core-ibx}} - A collection of Korean TrueType fonts by KLDP<br />
<br />
===== Vietnamese =====<br />
<br />
* {{Pkg|ttf-hannom}} - Vietnamese TrueType font for chữ Nôm characters<br />
<br />
==== Cyrillic ====<br />
<br />
See also [[#Latin script]].<br />
<br />
* {{AUR|ttf-paratype}} - Font family by ParaType: sans, serif, mono, extended cyrillic and latin, OFL license<br />
* {{AUR|otf-russkopis}} - A free OpenType cursive font for Cyrillic script<br />
<br />
==== Greek ====<br />
<br />
Almost all Unicode fonts contain the Greek character set (polytonic included). Some additional font packages, which might not contain the complete Unicode set but utilize high quality Greek (and Latin, of course) typefaces are:<br />
<br />
* {{AUR|otf-gfs}} - Selection of OpenType fonts from the Greek Font Society<br />
* {{AUR|ttf-mgopen}} - Professional TrueType fonts from Magenta<br />
<br />
==== Hebrew ====<br />
<br />
* {{AUR|culmus}} - Nice collection of free Hebrew fonts<br />
<br />
==== Indic ====<br />
<br />
* {{Pkg|ttf-freebanglafont}} - Font for Bangla<br />
* {{Pkg|ttf-indic-otf}} - Indic OpenType Fonts collection (containing ttf-freebanglafont), provides the character [http://www.fileformat.info/info/unicode/char/ca0/index.htm U+0CA0] "ಠ"<br />
* {{AUR|lohit-fonts}} - Indic TrueType fonts from Fedora Project (containing Oriya Fonts and more)<br />
* {{AUR|ttf-devanagarifonts}} - Devanagari TrueType fonts (contains 283 fonts)<br />
* {{AUR|ttf-gurmukhi-fonts_sikhnet}} - TrueType Gurmukhi fonts (gurbaniwebthick,prabhki)<br />
* {{AUR|ttf-gurmukhi_punjabi}} - TTF Gurmukhi / Punjabi (contains 252 fonts)<br />
* {{AUR|ttf-gujrati-fonts}} - TTF Gujarati fonts (Avantika,Gopika,Shree768)<br />
* {{AUR|ttf-kannada-font}} - Kannada, the language of Karnataka state in India<br />
* {{AUR|ttf-lklug}} - Sinhala Unicode font<br />
* {{AUR|ttf-tamil}} - Tamil Unicode fonts<br />
* {{AUR|ttf-urdufonts}} - Urdu fonts (Jameel Noori Nastaleeq (+kasheeda), Nafees Web Naskh, PDMS Saleem Quran Font) and font configuration to set Jameel Noori Nastaleeq as default font for Urdu<br />
* {{AUR|fonts-smc-malayalam}} - Malayalam Unicode Fonts released by 'Swathanthra Malayalam Computing' (contains 11 fonts).<br />
<br />
==== Khmer ====<br />
<br />
* {{Pkg|ttf-khmer}} - Font covering glyphs for Khmer language<br />
* [https://www.google.com/fonts/specimen/Hanuman Hanuman] ({{AUR|ttf-google-fonts-git}})<br />
<br />
==== Mongolic and Tungusic ====<br />
<br />
* {{AUR|ttf-abkai}} - Fonts for Sibe, Manchu and Daur scripts (incomplete, currently in development)<br />
<br />
==== Persian ====<br />
<br />
* {{AUR|persian-fonts}} - Meta package for installing all Persian fonts in AUR.<br />
* {{AUR|borna-fonts}} - Borna Rayaneh Co. Persian B font series.<br />
* {{AUR|iran-nastaliq-fonts}} - A free Unicode calligraphic Persian font.<br />
* {{AUR|iranian-fonts}} - Iranian-Sans and Iranian-Serif Persian font family.<br />
* {{AUR|ir-standard-fonts}} - Iran Supreme Council of Information and Communication Technology (SCICT) standard Persian fonts.<br />
* {{AUR|persian-hm-ftx-fonts}} - A Persian font series derived from X Series 2, Metafont and FarsiTeX fonts with Kashida feature.<br />
* {{AUR|persian-hm-xs2-fonts}} - A Persian font series derived from X Series 2 fonts with Kashida feature.<br />
* {{AUR|sina-fonts}} - Sina Pardazesh Co. Persian font series.<br />
* {{AUR|gandom-fonts}}, {{AUR|parastoo-fonts}}, {{AUR|sahel-fonts}}, {{AUR|samim-fonts}}, {{AUR|shabnam-fonts}}, {{AUR|tanha-fonts}}, {{AUR|vazir-fonts}}, {{AUR|vazir-code-fonts}} - Beautiful Persian fonts made by Ali Rasti Kerdar.<br />
* {{AUR|ttf-yas}} - The Yas Persian font series (with '''hollow zero''').<br />
* {{AUR|ttf-x2}} - Free fonts with support for Persian, Arabic, Urdu, Pashto, Dari, Uzbek, Kurdish, Uighur, old Turkish (Ottoman) and modern Turkish (Roman).<br />
<br />
==== Tai–Kadai ====<br />
<br />
* {{Pkg|fonts-tlwg}} - Collection of scalable Thai fonts<br />
* {{AUR|ttf-lao}} - Lao TTF font (Phetsarath_OT)<br />
* {{AUR|ttf-lao-fonts}} - Lao TTF fonts, both Unicode and non-Unicode for Windows<br />
<br />
==== Tibeto-Burman ====<br />
<br />
* {{Pkg|ttf-tibetan-machine}} - Tibetan Machine TTFont<br />
* {{AUR|ttf-myanmar-fonts}} - 121 Fonts from myordbok.com<br />
<br />
=== Emoji and symbols ===<br />
<br />
A section of the Unicode standard is designated for pictographic characters called "emoji".<br />
<br />
* {{Pkg|noto-fonts-emoji}} - Google's own emoji font, like on Android or Google Hangouts.<br />
* {{AUR|ttf-symbola}} - provides many Unicode symbols, including emoji, in outline style.<br />
* {{AUR|ttf-emojione}} - Official colorful EmojiOne font.<br />
* {{AUR|ttf-emojione-color}} - a color and B&W emoji SVGinOT font built from EmojiOne.<br />
* {{AUR|ttf-twemoji-color}} - Twitter's open-sourced emoji glyphs.<br />
<br />
[[wikipedia:Emoticon#Japanese_style|Kaomoji]] are sometimes referred to as "Japanese emoticons" and are composed of characters from various character sets, including CJK and Indic fonts. For example, the following set of packages covers most of existing kaomoji: {{Pkg|ttf-freefont}}, {{Pkg|ttf-arphic-uming}}, and {{Pkg|ttf-indic-otf}}.<br />
<br />
=== Math ===<br />
<br />
* {{Pkg|font-mathematica}} - Mathematica fonts by Wolfram Research, Inc.<br />
* {{Pkg|texlive-core}} and {{Pkg|texlive-fontsextra}} contain many math fonts such as Latin Modern Math and [[Wikipedia:STIX Fonts project|STIX Fonts]]. See [[TeX Live#Fonts]] for configuration.<br />
* {{AUR|otf-stix}} - A standalone, more recent version of STIX<br />
* {{Pkg|otf-latin-modern}}, {{Pkg|otf-latinmodern-math}} - Improved version of Computer Modern fonts as used in LaTeX<br />
* {{AUR|ttf-computer-modern-fonts}}, {{AUR|otf-cm-unicode}} - [[wikipedia:Computer Modern|Computer Modern]] (of TeX fame)<br />
* {{AUR|ttf-mathtype}} - MathType fonts<br />
<br />
=== Other operating system fonts ===<br />
<br />
* {{AUR|ttf-mac-fonts}} - Apple MacOS TrueType fonts<br />
<br />
See [[Metric-compatible fonts]], which lists available alternatives for [[Microsoft fonts]].<br />
<br />
== Fallback font order with X11 ==<br />
<br />
Fontconfig automatically chooses a font that matches the current requirement. That is to say, if one is looking at a window containing English and Chinese for example, it will switch to another font for the Chinese text if the default one does not support it.<br />
<br />
Fontconfig lets every user configure the order they want via {{ic|$XDG_CONFIG_HOME/fontconfig/fonts.conf}}.<br />
If you want a particular Chinese font to be selected after your favorite Serif font, your file would look like this:<br />
<br />
<?xml version="1.0"?><br />
<!DOCTYPE fontconfig SYSTEM "fonts.dtd"><br />
<fontconfig><br />
<alias><br />
<family>serif</family><br />
<prefer><br />
<family>Your favorite Latin Serif font name</family><br />
<family>Your Chinese font name</family><br />
</prefer><br />
</alias><br />
</fontconfig><br />
<br />
{{Tip|If you use a Chinese locale, set {{ic|LC_LANG}} to {{ic|und}} to make this work. Otherwise both English and Chinese text will be rendered in the Chinese font.}}<br />
<br />
You can add a section for sans-serif and monospace as well. For more information, have a look at the fontconfig manual.<br />
<br />
See also [[Font configuration#Replace or set default fonts]].<br />
<br />
== Font alias ==<br />
<br />
There are several font aliases which represent other fonts in order that applications may use similar fonts. The most common aliases are: {{ic|serif}} for a font of the serif type (e.g. DejaVu Serif); {{ic|sans-serif}} for a font of the sans-serif type (e.g. DejaVu Sans); and {{ic|monospace}} for a monospaced font (e.g. DejaVu Sans Mono). However, the fonts which these aliases represent may vary and the relationship is often not shown in font management tools, such as those found in [[KDE]] and other [[desktop environments]].<br />
<br />
To reverse an alias and find which font it is representing, run:<br />
<br />
{{hc|$ fc-match monospace|<br />
DejaVuSansMono.ttf: "DejaVu Sans Mono" "Book"<br />
}}<br />
<br />
In this case, {{ic|DejaVuSansMono.ttf}} is the font represented by the monospace alias.<br />
<br />
== Tips and tricks ==<br />
<br />
=== List all installed fonts ===<br />
<br />
You can use the following command to list all installed Fontconfig fonts that are available on your system. <br />
<br />
$ fc-list<br />
<br />
=== Lists installed fonts for a particular language ===<br />
<br />
Applications and browsers select and display fonts depending upon fontconfig preferences and available font glyph for Unicode text. To list installed fonts for a particular language, issue a command {{ic|<nowiki>fc-list :lang="two letter language code"</nowiki>}}. For instance, to list installed Arabic fonts or fonts supporting Arabic glyph:<br />
{{hc|$ fc-list -f '%{file}\n' :lang&#61;ar|2=<br />
<nowiki><br />
/usr/share/fonts/TTF/FreeMono.ttf<br />
/usr/share/fonts/TTF/DejaVuSansCondensed.ttf<br />
/usr/share/fonts/truetype/custom/DroidKufi-Bold.ttf<br />
/usr/share/fonts/TTF/DejaVuSansMono.ttf<br />
/usr/share/fonts/TTF/FreeSerif.ttf<br />
</nowiki><br />
}}<br />
<br />
=== Set terminal font on-the-fly ===<br />
<br />
{{Expansion|Which terminals specifically support this method? Where is the documentation for the escape codes?}}<br />
<br />
For terminal emulators that use {{ic|Xresources}}, fonts can be set by using escape sequences. Specifically, {{ic|echo -e "\033]710;$font\007"}} to change the normal font ({{ic|*font}} in {{ic|~/.Xresources}}), and replace {{ic|710}} with {{ic|711}}, {{ic|712}}, and {{ic|713}} to change the {{ic|*boldFont}}, {{ic|*italicFont}}, and {{ic|*boldItalicFont}}, respectively.<br />
<br />
{{ic|$font}} uses the same syntax as in {{ic|~/.Xresources}} and can be anything the terminal emulator will support. (Example: {{ic|1=xft:dejavu sans mono:size=9}})<br />
<br />
=== Application-specific font cache ===<br />
<br />
Matplotlib ({{pkg|python-matplotlib}} or {{pkg|python2-matplotlib}}) uses its own font cache, so after updating fonts, be sure to remove {{ic|~/.matplotlib/fontList.cache}}, <br />
{{ic|~/.cache/matplotlib/fontList.cache}}, {{ic|~/.sage/matplotlib-1.2.1/fontList.cache}}, etc. so it will regenerate its cache and find the new fonts [http://matplotlib.1069221.n5.nabble.com/getting-matplotlib-to-recognize-a-new-font-td40500.html].<br />
<br />
== See also ==<br />
<br />
* [http://behdad.org/text/ State of Text Rendering]<br />
* [https://fontlibrary.org/en Font Library] - Fonts under Free licenses<br />
* [https://screenshots.debian.net/packages?search=fonts&show=with Fonts on screenshots.debian.net]</div>Jgwakhttps://wiki.archlinux.org/index.php?title=DisplayLink&diff=526713DisplayLink2018-06-18T02:38:55Z<p>Jgwak: Warning about the current evdi issue.</p>
<hr />
<div>[[Category:Displays]]<br />
[[ja:DisplayLink]]<br />
DisplayLink devices on Linux still only have experimental support. While some people have had success in using them, it is generally not an easy process and not guaranteed to work. The steps on this page describe the generally most successful methods of using external monitors with DisplayLink.<br />
<br />
Also be warned that even over USB 3.0, a DisplayLink monitor may exhibit noticeably more lag than e.g. a DisplayPort monitor, especially when large portions of the screen are being redrawn.<br />
<br />
==Installation==<br />
<br />
=== USB 2.0 DL-1x5, DL-1x0 Devices ===<br />
<br />
The kernel [[Wikipedia: Direct_Rendering_Manager|DRM]] driver for DisplayLink is {{ic|udl}}, a rewrite of the original [https://www.kernel.org/doc/Documentation/fb/udlfb.txt udlfb] driver. It allows configuring DisplayLink monitors using [[Xrandr]].<br />
<br />
This should work without any configuration changes on {{pkg|linux}} 4.14.9-1 and later. If you're using an earlier version of that package or have {{ic|1=CONFIG_FB_UDL=m}} set in your kernel config, you need to [[blacklist]] the old kernel module, {{ic|udlfb}}, which may attempt to load itself first.<br />
<br />
=== USB 3.0 DL-6xxx, DL-5xxx, DL-41xx, DL-3xxx Devices ===<br />
<br />
{{Warning|The current version of {{AUR|evdi}}, which {{AUR|displaylink}} depends on, doesn't work on the latest version of {{Pkg|xorg-server}}. You should [[Downgrading_packages|downgrade]] your {{Pkg|xorg-server}} and some relevant packages including but not limited to {{Pkg|xf86-video-fbdev}} and {{Pkg|xf86-video-intel}} to version {{ic|1.19.6}} in order to make {{AUR|displaylink}} work. Please check the following [https://github.com/DisplayLink/evdi/issues/133 github issue] for the latest update of this issue.}}<br />
<br />
# Install the {{AUR|displaylink}} driver. It allows configuring DisplayLink monitors using [[Xrandr]] in the same manner as the {{ic|udl}} driver.<br />
# Enable {{ic|displaylink.service}}.<br />
<br />
=== Setting up X Displays ===<br />
<br />
After that, run:<br />
<br />
{{hc|$ xrandr --listproviders|<nowiki><br />
Providers: number : 2<br />
Provider 0: id: 0x49 cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 2 outputs: 8 associated providers: 0 name:Intel<br />
Provider 1: id: 0x13c cap: 0x2, Sink Output crtcs: 1 outputs: 1 associated providers: 0 name:modesetting<br />
</nowiki>}}<br />
<br />
In the above output, we can see that provider 0 is the system's regular graphics provider (Intel), and provider 1 (modesetting) is the DisplayLink provider. To use the DisplayLink device, connect provider 1 to provider 0:<br />
<br />
$ xrandr --setprovideroutputsource 1 0<br />
<br />
and xrandr will add a DVI output you can [[Xrandr#Configuration|use as normal with xrandr]]. This is still experimental but supports hotplugging and when works, it is by far the simplest setup. If it works then everything below is unnecessary.<br />
<br />
==Configuration==<br />
<br />
These instructions assume that you already have an up and running X server and are simply adding a monitor to your existing setup.<br />
<br />
===Load the framebuffer device===<br />
<br />
Before your system will recognize your DisplayLink device, the {{ic|udl}} kernel module must be loaded. To do this, run<br />
<br />
# modprobe udl<br />
<br />
If your DisplayLink device is connected, it should show some visual indication of this. Although a green screen is the standard indicator of this, other variations have been spotted and are perfectly normal. Most importantly, the output of {{ic|dmesg}} should show something like the following, indicating a new DisplayLink device was found:<br />
<br />
{{bc|<nowiki>usb 2-1.1: new high-speed USB device number 7 using ehci-pci<br />
usb 2-1.1: New USB device found, idVendor=17e9, idProduct=03e0<br />
usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3<br />
usb 2-1.1: Product: Lenovo LT1421 wide<br />
usb 2-1.1: Manufacturer: DisplayLink<br />
usb 2-1.1: SerialNumber: 6V9BBRM1<br />
[drm] vendor descriptor length:17 data:17 5f 01 00 15 05 00 01 03 00 04<br />
udl 2-1.1:1.0: fb1: udldrmfb frame buffer device<br />
[drm] Initialized udl 0.0.1 20120220 on minor 1<br />
</nowiki>}}<br />
<br />
Furthermore, {{ic|/dev}} should contain a new {{ic|fb}} device, likely {{ic|/dev/fb1}} if you already had a framebuffer for your primary display.<br />
<br />
To automatically load {{ic|udl}} at boot, create the file {{ic|udl.conf}} in {{ic|/etc/modules-load.d/}} with the following contents:<br />
<br />
{{hc|/etc/modules-load.d/udl.conf|udl}}<br />
<br />
For more information on loading kernel modules, see [[Kernel modules#Automatic module handling]].<br />
<br />
===Configuring X Server===<br />
Use {{ic|xrandr}} or your Desktop Environment's display setup UI to configure your USB monitors running either the {{ic|udl}} or {{ic|displaylink}} driver.<br />
<br />
====xrandr====<br />
<br />
Once the driver is loaded, the DisplayLink monitor is listed as an output provider:<br />
<br />
{{hc|$ xrandr --listproviders|<nowiki><br />
Providers: number : 2<br />
Provider 0: id: 0x43 cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 2 outputs: 2 associated providers: 1 name:Intel<br />
Provider 1: id: 0xcb cap: 0x2, Sink Output crtcs: 1 outputs: 1 associated providers: 1 name:modesetting<br />
</nowiki>}}<br />
In the above example, provider 1 is the DisplayLink device, and provider 0 is the default display. Running {{ic|xrandr --current}} gives a list of available screens:<br />
<br />
{{hc|$ xrandr --current|<nowiki><br />
Screen 0: minimum 320 x 200, current 1600 x 900, maximum 8192 x 8192<br />
LVDS1 connected 1600x900+0+0 (normal left inverted right x axis y axis) 309mm x 174mm<br />
1600x900 60.0*+ 40.0 <br />
1440x900 59.9 <br />
1360x768 59.8 60.0 <br />
1152x864 60.0 <br />
1024x768 60.0 <br />
800x600 60.3 56.2 <br />
640x480 59.9 <br />
VGA1 disconnected (normal left inverted right x axis y axis)<br />
DVI-1-0 connected (normal left inverted right x axis y axis)<br />
1366x768 60.0 +<br />
1368x768_59.90 59.9 <br />
1368x768_59.90 (0xd0) 85.7MHz<br />
h: width 1368 start 1440 end 1584 total 1800 skew 0 clock 47.6KHz<br />
v: height 768 start 769 end 772 total 795 clock 59.9Hz<br />
</nowiki>}}<br />
<br />
If the above does not list the DisplayLink screen, then you will need to offload DisplayLink to the main GPU:<br />
<br />
{{bc|xrandr --setprovideroutputsource 1 0}}<br />
<br />
Once the screen is available, refer to [[Xrandr]] for info on setting it up. For automating the configuration process, see [https://github.com/nathantypanski/displaylink.sh displaylink.sh].<br />
<br />
====Enabling DVI output on startup====<br />
The DisplayLink provider will not be automatically connected to the main provider in most cases, therefore the DVI output device will not be available. It can be helpful to automatically do this when X starts to facilitate automatic display configuration by the window manager.<br />
<br />
Edit your desktop manager's startup configuration and add commands similar to:<br />
{{bc|<nowiki><br />
$(xrandr --listproviders | grep -q "modesetting") && xrandr --setprovideroutputsource 1 0<br />
</nowiki>}}<br />
<br />
For example, the appropriate startup configuration file for [[SDDM]] is {{ic|/usr/share/sddm/scripts/Xsetup}}.<br />
<br />
Avoid placing these commands in {{ic|~/.xprofile}} as this breaks the display configuration of some window managers. Instead these commands should be run prior to any display output or setup.<br />
<br />
{{Note|If you have additional providers, specify the name of the provider instead of using indexes. The name of the DisplayLink device will be {{ic|modesetting}}}}<br />
<br />
==== Switching between displaylink and nvidia/nouveau driver ====<br />
<br />
Currently (displaylink version 1.3.54-1) it is not possible to use displaylink device and nvidia/nouveau driver simultaniously on optimus based laptops.<br />
Currently to be able to use displaylink device on intel GPU, you should create config file (see troubleshooting section below). However, with that config file it is not possible to use primusrun. Bumblebee service is running, but it cannot work. Also, laptop's fans are becoming very noisy and laptop's temperature becomes very high. When you want to switch back to activate nvidia driver, comment everything in that file and reboot.<br />
<br />
To simplify process of switching, you can install {{aur|dl-switch}} package and add additional menu entry to your bootloader with kernel parameter activating displaylink workaround. For rEFInd bootloader it will look like this:<br />
<br />
{{hc|/boot/EFI/refind/refind.conf|<nowiki><br />
...<br />
submenuentry "Boot with DisplayLink workaround" {<br />
add_options "systemd.unit=displaylink.target"<br />
}<br />
...<br />
</nowiki>}}<br />
When booting, your are able to choose: boot using default options or boot with displaylink working.<br />
<br />
To check which driver is used for your discrete video card, run {{ic|lspci -nnk -s xx:xx.x}} (replace xx:xx.x with your nvidia gpu pci id).<br />
<br />
== Troubleshooting ==<br />
<br />
=== Not working configuration ===<br />
<br />
These are tested on [[Xfce]] using Display settings (included in XFCE4 package) and external tool - {{pkg|arandr}}. XFCE4 Display settings are likely to crash, so ARandR might help.<br />
<br />
When you connect display link device via USB to your computer, the computer should show monitors in Display settings. There are few troubleshooting steps that you should try:<br />
<br />
* Check [[#Setting up X Displays]]. If you can find any external monitors recognized, you should try to make them visible by the following commands:<br />
{{bc|<nowiki>xrandr --setprovideroutputsource 1 0<br />
xrandr --setprovideroutputsource 2 0<br />
xrandr --setprovideroutputsource 3 0<br />
...<br />
</nowiki>}}<br />
This will make them visible and recognized in Display settings.<br />
* Restart {{ic|displaylink.service}}.<br />
* Re-connecte USB cable.<br />
* Check if {{ic|udl}} driver is loaded and monitors are connected.<br />
<br />
=== Screen redraw is broken ===<br />
If you are using {{ic|udl}} as your kernel driver and the monitor appears to work, but is only updating where you move the mouse or when windows change in certain places, then you probably have the wrong modeline for your screen. Getting a proper modeline for your screen with a command like<br />
<br />
{{bc|<br />
gtf 1366 768 59.9<br />
}}<br />
<br />
where {{ic|1366}} and {{ic|768}} are the horizontal and vertical resolutions for your monitor, and {{ic|59.9}} is the refresh rate from its specs. To use this, create a new mode with {{ic|xrandr}} like follows:<br />
<br />
{{bc|<br />
xrandr --newmode "1368x768_59.90" 85.72 1368 1440 1584 1800 768 769 772 795 -HSync +Vsync<br />
}}<br />
<br />
and add it to [[Xrandr]]:<br />
<br />
{{bc|<br />
xrandr --addmode DVI-0 1368x768_59.90<br />
}}<br />
<br />
Then tell the monitor to use that mode for the DisplayLink monitor, and this should fix the redraw issues. Check the [[Xrandr]] page for information on using a different mode.<br />
<br />
If this does not solve the problem (or if the correct modeline was already in place because of correct DDC data), it can help to run a compositor. E.g. when using plain i3, running {{Pkg|xcompmgr}} or {{Pkg|compton}} can mitigate the problem.<br />
<br />
=== DisplayLink refresh rate is extremely slow with gnome 3 ===<br />
If once you set up your DisplayLink your entire desktop becomes slow, try setting a "simpler" background image, such as complete black.<br />
<br />
=== Slow redraw/Unresponsiveness in Google Chrome and Webkit2-based Applications ===<br />
This is to be associated with bugs in hardware acceleration, which can be tested by running glxgears in the displaylink screen resulting in 1fps. There is currently no complete fix available, but turning off Hardware-Acceleration in affected applications can work as a temporary fix.<br />
<br />
This can be done in applications without a hardware-acceleration option by prepending the {{ic|1=LIBGL_ALWAYS_SOFTWARE=1}} environment variable.<br />
<br />
=== Impossible to activate displaylink's screen ===<br />
In case you are able to see attached monitor via DisplayLink device in your screen settings, but after you turn it on and apply settings, it becomes deactivated, then try blacklist nouveau module and reboot:<br />
{{hc|/etc/modprobe.d/nouveau.conf|<nowiki><br />
blacklist nouveau<br />
options nouveau modeset=0<br />
</nowiki>}}<br />
<br />
=== Suspend problem ===<br />
<br />
Displaylink is not working after suspend. Unplug and then plug again displaylink's usb cable to your computer. Monitor that is connected via DisplayLink will remain black. If you have lock screen, login to the system and then picture will appear at that monitor and you will be able to use displaylink as normal.<br />
<br />
=== DisplayLink is not working when usb hot plugged ===<br />
To be able to use DisplayLink monitors, its usb cable should be attached to laptop during boot time. Otherwise it can behave like they are available and mouse can be moved there, but its picture is frozen, even with correct configuration (see workaround 1). If it was not attached at boot time, attach it and reboot.<br />
<br />
=== DisplayLink driver does not work with Intel GPUs after recent X upgrades ===<br />
As [http://support.displaylink.com/knowledgebase/articles/1181623 this support] page says, upgrading the X Window Server to a version newer than 1.18.3 will make the system not compatible with DisplayLink by default. This applies to systems using an integrated Intel GPU, or a combination of integrated Intel GPU and a discrete GPU.<br />
Until fixes in X Windows System will be released, there are two workarounds:<br />
<br />
==== Workaround 1: Use older intel driver as a fallback ====<br />
<br />
Use the "intel" driver for the integrated GPU instead of "modesetting", which is now the default.<br />
<br />
Create a file with the following content:<br />
{{hc|/usr/share/X11/xorg.conf.d/20-displaylink.conf|<br />
Section "Device" <br />
Identifier "Intel Graphics"<br />
Driver "intel"<br />
EndSection<br />
}}<br />
A reboot is required for the setting to be effective.<br />
<br />
You may need the {{aur|evdi-git}} package.<br />
<br />
==== Workaround 2: Temporarily disable PageFlip for modesetting ====<br />
<br />
For users that prefer to keep using "modesetting" driver, disabling page flipping should also help.<br />
Create a file with the following content:<br />
{{hc|/usr/share/X11/xorg.conf.d/20-displaylink.conf|<br />
Section "Device"<br />
Driver "modesetting"<br />
Option "PageFlip" "false"<br />
EndSection <br />
}}<br />
<br />
== See Also ==<br />
<br />
* [http://displaylink.org/forum/forumdisplay.php?f=29 DisplayLink Open Source]: Official DisplayLink open source support forum<br />
* [http://plugable.com/platforms/linux Plugable]: Vendor blog chronicling Linux support for DisplayLink.<br />
* [http://www.displaylink.com/downloads/ubuntu.php Ubuntu Driver Download]: DisplayLink Ubuntu Driver Download and Information<br />
* [http://downloads.displaylink.com/releasenotes/DisplayLink_Ubuntu_1.0.68_release-note.txt Release Notes]: Latest release notes for DisplayLink Ubuntu Software</div>Jgwakhttps://wiki.archlinux.org/index.php?title=KeePass&diff=517993KeePass2018-04-20T02:26:58Z<p>Jgwak: KeepassXC supports Yubikey as well.</p>
<hr />
<div>[[Category:Security]]<br />
[[ja:KeePass]]<br />
KeePass is an encrypted password database format. It is an alternative to online password managers and is supported on all major platforms.<br />
<br />
There are two versions of the format: ''KeePass 1.x (Classic)'' and ''KeePass 2.x''<br />
<br />
== Installation ==<br />
<br />
There are three major implementations of KeePass, which are all available in the official repositories:<br />
<br />
* {{App|[[Wikipedia:KeePass|KeePass]]|A cross-platform password manager that has autotype and clipboard support when respectively {{ic|xdotool}} and {{ic|xsel}} are installed. It lets you import [http://keepass.info/help/base/importexport.html many formats] and has [http://keepass.info/plugins.html many plugins].|http://keepass.info|{{Pkg|keepass}}}}<br />
<br />
* {{App|[[Wikipedia:KeePassX|KeePassX]]|Started as a Linux port of KeePass. {{Pkg|keepassx2}} uses the KeePass 2.x format, but can import 1.x databases. It also lets you import PwManager and KWallet XML databases. It does not support plugins. [https://www.keepassx.org/faq].<br />
|https://www.keepassx.org/|{{Pkg|keepassx}} {{Pkg|keepassx2}}}}<br />
<br />
* {{App|[[Wikipedia:KeePassXC|KeePassXC]]|Fork of KeePassX that aims to incorporate stalled pull requests, that are not being incorporated into KeePassX. |https://keepassxc.org|{{Pkg|keepassxc}} }}<br />
<br />
Other lesser-known alternatives can be found in the AUR:<br />
<br />
* {{App|keepassc|A curses-based password manager compatible to KeePass v.1.x and KeePassX. It uses {{ic|xsel}} for clipboard functions.<br />
|https://raymontag.github.io/keepassc/|{{AUR|keepassc}}}}<br />
<br />
* {{App|kpcli|A command line interface for KeePassX database files {{ic|*.kdb}}.<br />
|https://sourceforge.net/projects/kpcli/|{{AUR|kpcli}}}}<br />
<br />
* {{App|keepmenu|Dmenu/Rofi frontend for Keepass database files.<br />
|https://github.com/firecat53/keepmenu|{{AUR|python-keepmenu-git}}}}<br />
<br />
* {{App|keeweb|A web app (online / Electron) compatible with KeePass 2.x.<br />
|https://keeweb.info|{{AUR|keeweb-desktop}} {{AUR|nextcloud-app-keeweb}} }}<br />
<br />
== Integration ==<br />
<br />
Many [http://keepass.info/plugins.html plugins and extensions] are available for integrating KeePass to other software. <br />
<br />
=== Plugin Installation ===<br />
<br />
{{Tip|Starting from KeePassXC version 2.3, an [https://keepassxc.org/docs/keepassxc-browser-migration/ official plugin is available] that supports [[Chrome]], [[Chromium]], [[Firefox]] and [[Vivaldi]] - which replaces KeePassHTTP.}}<br />
<br />
{{Note|KeePassX does not support plugins on its master branch. An alternative is to use global autotype feature.}}<br />
<br />
KeePass is by default, installed at {{ic|/usr/share/keepass/}}. Copy {{ic|plugin.plgx}} to a plugins sub-directory under the KeePass installation directory as demonstrated below:<br />
<br />
{{bc|<br />
# mkdir /usr/share/keepass/plugins<br />
# cp plugin.plgx /usr/share/keepass/plugins<br />
}}<br />
<br />
{{Warning|Upstream strongly advises to disable KeePassHTTP because of security issues. For more information see, [https://github.com/pfn/keepasshttp/issues/258 pfn/keepasshttp/issues] and [https://github.com/keepassxreboot/keepassxc/issues/147 keepassxreboot/keepassxc/issues]. To [https://github.com/keepassxreboot/keepassxc/issues/147#issuecomment-274669750 mitigate the impact] of the KeePassHTTP flaw, KeePassXC has [https://github.com/keepassxreboot/keepassxc/pull/196 issued a hotfix] as of version 2.1.1. Some users consider the improvement good enough ([https://github.com/keepassxreboot/keepassxc/issues/147#issuecomment-274682664 1], [https://github.com/keepassxreboot/keepassxc/issues/147#issuecomment-274669042 2]) for practical purposes, as long as the system is not compromised. However, as there is still [https://github.com/keepassxreboot/keepassxc/issues/147#issuecomment-274671861 some risk] involved, KeePassHTTP support is [https://github.com/keepassxreboot/keepassxc/blob/2.1.1/README.md#note-about-keepasshttp no longer enabled by default] in KeePassXC.}}<br />
<br />
=== Firefox ===<br />
<br />
* [http://keefox.org/ KeeFox] ({{aur|keepass-plugin-rpc}})<br />
: Firefox extension that links the browser to existing or new KeePass database. KeeFox needs to be setup before it is fully functional. <br />
<br />
* [https://addons.mozilla.org/en-US/firefox/addon/passifox/ PassIFox] ([https://github.com/pfn/keepasshttp/ KeepassHTTP plugin])<br />
: Extension allowing Firefox to form-fill passwords stored in KeePass.<br />
<br />
* [https://addons.mozilla.org/en-us/firefox/addon/keepass-helper/ KeePass Helper (legacy addon)], [https://addons.mozilla.org/en-US/firefox/addon/url-in-title/ TitleURL]<br />
: Modifies window title to assist autotype feature.<br />
<br />
* [https://addons.mozilla.org/en-US/firefox/addon/keepassxc-browser/ KeePassXC-Browser]<br />
: Official browser plugin for the KeePassXC password manager (Firefox version).<br />
<br />
=== Chrome/Chromium ===<br />
<br />
* [https://chrome.google.com/webstore/detail/chromeipass/ompiailgknfdndiefoaoiligalphfdae ChromeIPass] ([https://github.com/pfn/keepasshttp/ KeepassHTTP plugin])<br />
: Extension allowing Google Chrome and Chromium to form-fill passwords stored in KeePass.<br />
<br />
* [https://chrome.google.com/webstore/detail/url-in-title/ignpacbgnbnkaiooknalneoeladjnfgb Url in title]<br />
: Modifies window title to assist autotype feature. Similar to KeePass Helper for Firefox in function.<br />
<br />
* [https://chrome.google.com/webstore/detail/url-in-title/oboonakemofpalcgghocfoadofidjkkk KeePassXC-Browser]<br />
: Official browser plugin for the KeePassXC password manager (Chrome/Chromium version).<br />
<br />
=== Nextcloud ===<br />
<br />
* [https://github.com/jhass/nextcloud-keeweb Keeweb for Nextcloud] ({{aur|nextcloud-app-keeweb}})<br />
: Open Keepass stores inside Nextcloud<br />
<br />
=== Yubikey ===<br />
<br />
[[Yubikey]] can be integrated with KeePass thanks to contributors of KeePass plugins.<br />
<br />
# StaticPassword<br />
#:Configure one of Yubikey slots to store static password. You can make the password as strong as 65 characters (64 characters with leading `!`). This password can then be used as master password for your KeePass database.<br />
# one-time passwords (OATH-HOTP)<br />
#:# Download plugin from KeePass website: http://keepass.info/plugins.html#otpkeyprov<br />
#:# Use {{AUR|yubikey-personalization-gui-git}} to setup OATH-HOTP<br />
#:# In advanced mode untick `OATH Token Identifier`<br />
#:# In KeePass additional option will show up under `Key file / provider` called `One-Time Passwords (OATH HOTP)<br />
#:# Copy secret, key length (6 or 8), and counter (in Yubikey personalization GUI this parameter is called `Moving Factor Seed`)<br />
#:# You may need to setup `Look-ahead count` option to something greater than 0, please see [https://forum.yubico.com/viewtopic.php?f=16&t=1120|this thread] for more information<br />
#:# See [https://www.yubico.com/products/services-software/personalization-tools/oath/|this video] for more help<br />
# Challenge-Response (HMAC-SHA1)<br />
#:# Get the plugin from AUR: {{AUR|keepass-plugin-keechallenge}}<br />
#:# In KeePass additional option will show up under `Key file / provider` called `Yubikey challenge-response`<br />
#:# Plugin assumes slot 2 is used<br />
<br />
KeepassXC provides built-in support for Yubikey Challenge-Response without plugins.<br />
<br />
== Tips and tricks ==<br />
<br />
=== Disable your clipboard manager ===<br />
<br />
If you are an avid user of clipboard managers, you can may need to disable your clipboard manager before you launch keepass and then re-start your clipboard manager afterward.<br />
<br />
== See Also ==<br />
<br />
* [[List of applications/Security#Password_managers]]</div>Jgwak