source: x/installing/TTF-and-OTF-fonts.xml@ e180a646

10.0 10.1 11.0 11.1 11.2 11.3 8.0 8.1 8.2 8.3 8.4 9.0 9.1 basic bdubbs/svn elogind ken/inkscape-core-mods lazarus perl-modules plabs/python-mods qt5new trunk upgradedb xry111/intltool xry111/soup3 xry111/test-20220226
Last change on this file since e180a646 was e180a646, checked in by Ken Moffat <ken@…>, 6 years ago

For a' that, an a' that,
It's coming yet for a' that,
That ilka body the world o'er,
Can use Guid Fonts for a' that.

git-svn-id: svn:// af4574ff-66df-0310-9fd7-8a98e5e911e0

  • Property mode set to 100644
File size: 27.7 KB
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3 "" [
4 <!ENTITY % general-entities SYSTEM "../../general.ent">
5 %general-entities;
8<sect1 id="TTF-and-OTF-fonts">
9 <?dbhtml filename="TTF-and-OTF-fonts.html"?>
11 <sect1info>
12 <othername>$LastChangedBy$</othername>
13 <date>$Date$</date>
14 </sect1info>
16 <title>TTF and OTF fonts</title>
18 <indexterm zone="TTF-and-OTF-fonts">
19 <primary sortas="a-TTF-and-OTF-fonts">TTF and OTF fonts</primary>
20 </indexterm>
22 <!-- although indexterm entries can be added for the individual fonts, and
23 will link to the correct part of the page, that seems unnecessary unless
24 the font is linked from other pages -->
26 <sect2 role="configuration">
27 <title>About TTF and OTF fonts</title>
29 <para>
30 Originally, Xorg provided only bitmap fonts. Later, some scalable
31 Type1 fonts were added, but the desktop world moved on to using TrueType
32 and Open Type fonts. To support these, Xorg uses Xft, the X FreeType
33 interface library.
34 </para>
36 <para>
37 These fonts can provide hints, which <application>fontconfig</application>
38 uses to adjust them for maximum readability on computer monitors. On linux
39 you should always prefer the hinted versions, if available (in general the
40 latin, cyrillic and greek alphabets can use hints, most other writing
41 systems do not use hinting).
42 </para>
44 <para>
45 A few fonts are provided as collections (TTC or OTC) where font data
46 is shared between different fonts, thus saving disk space. Treat these in
47 exactly the same way as individual TTF or OTF files.
48 </para>
50 <para>
51 If a font provides both TTF and OTF forms, prefer the OTF form in
52 linux, it may provide more features for programs which know how to use them
53 (such as xelatex).
54 </para>
56 <para>
57 For some scripts <application>pango</application> is required to
58 render things correctly, either by selecting different glyph forms, or by
59 combining glyphs - in both cases, according to the context. This applies
60 particularly to arabic and indic scripts.
61 </para>
63 <para>
64 Standard scalable fonts that come with <application>X</application>
65 provide very poor Unicode coverage. You may notice in applications that
66 use <application>Xft</application> that some characters appear as a box
67 with four binary digits inside. In this case, a font with the
68 required glyphs has not been found. Other times, applications that
69 don't use other font families by default and don't accept substitutions
70 from <application>Fontconfig</application> will display blank lines when
71 the default font doesn't cover the orthography of the user's language.
72 </para>
74 <para>
75 The fonts available to a program are those which were present when
76 it was started, so if you add an extra font and wish to use it in a program
77 which is currently running, then you will have to close and restart that
78 program.
79 </para>
81 <para>
82 Some people are happy to have dozens, or even hundreds, of font files
83 available, but if you ever wish to select a specific font in a desktop
84 application (for example in a word processor) then scrolling through a lot of
85 fonts to find the right one is slow and awkward - fewer is better. So, for
86 some font packages you might decide to install only one of the fonts - but
87 nevertheless install the different variants (italic, bold, etc) as these are
88 all variations for the same font name.
89 </para>
91 <para>
92 In the past, everybody recommended running <command>fc-cache</command>
93 as the <systemitem class="username">root</systemitem> user after installing
94 or removing fonts, but this is no-longer necessary on linux,
95 <application>fontconfig</application> will do it automatically if needed and
96 if its caches are more than 30 seconds old. But if you add a font and want to
97 immediately use it then you can run that command (as a normal user).
98 </para>
100 <para>
101 There are several references below to CJK characters. This stands for
102 Chinese, Japanese and Korean, although modern Korean is now almost all
103 written using the phonetic Hangul glyphs (it used to sometimes use Hanja
104 glyphs which are similar to Chinese and Japanese). Unicode decided to go
105 for <ulink
106 url="">Han Unification</ulink>
107 and to map some Chinese and Japanese glyphs to the same codepoints. This
108 was very unpopular in Japan, and the result is that different fonts will
109 render some codepoints in quite different shapes. In addition, Simplified
110 Chinese will sometimes use the same codepoint as Traditional Chinese but
111 will show it differently, somewhat analagous to the different shapes used
112 for the letters 'a' and 'g' in English (single-storey and two-storey),
113 except that in a language context one will look "wrong" rather than just
114 "different".
115 </para>
117 <para>
118 Unlike most other packages in this book, the BLFS editors do not
119 monitor the versions of the fonts on this page - once a font is good enough
120 for general use, the typical additions in a new version are minor (e.g. new
121 currency symbols, or glyphs not for a modern language, such as emojis or
122 playing cards). Therefore, none of these fonts show version or md5
123 information.
124 </para>
126 <para>
127 The list below will not provide complete Unicode coverage.
128 Unicode is updated every year, and most additions are now for historic
129 writing systems. For almost-complete coverage you can install <xref
130 linkend="noto-fonts"/> (about 180 fonts when last checked) but that
131 number of fonts makes it <emphasis>much</emphasis> less convenient to
132 select a specific font in a document, and most people will regard many
133 of them as a waste of space. We used to recommend the <ulink
134 url="">Unicode Font Guide</ulink>, but that
135 has not been updated since 2008 and many of its links are dead.
136 </para>
138 <para>
139 Rendered examples of most of these fonts, and many others, with
140 details of what languages they cover, some examples of latin fonts with
141 the same metrics (listed as "Substitute latin fonts") and various files
142 of dummy text to compare fonts of similar types, can be found at this
143 <ulink url="">
144 font comparison</ulink> page. That site also covers other current
145 writing systems.
146 </para>
148 <para>
149 Fonts are often supplied in zip files, requiring <xref linkend="unzip"/>
150 to list and extract them, but even if the current release is a tarball
151 you should still check to see if it will create a directory (scatterring
152 the contents of a zipfile or tarball across the current directory can be
153 very messy, and a few fonts create odd __MACOSX/ directories. In addition,
154 many fonts are supplied with permissions which do not let 'other' read
155 them - if a font is to be installed for system-wide use, any directories
156 must be mode 755 and all the files mode 644, so change them if necessary.
157 If you forget, the root user may be able to see a particular font in
158 <command>fc-list</command> but a normal user will not.
159 </para>
161 <para>
162 As a font installation example, consider the installation of the
163 <xref linkend="dejavu-fonts"/>. In this particular package, the TTF files
164 are in a subdirectory. From the unpacked source directory, run the
165 following commands as the <systemitem class="username">root</systemitem>
166 user:
167 </para>
169<screen role="root"><userinput>install -v -d -m755 /usr/share/fonts/dejavu &amp;&amp;
170install -v -m644 ttf/*.ttf /usr/share/fonts/dejavu &amp;&amp;
171fc-cache -v /usr/share/fonts/dejavu</userinput></screen>
173 <para>
174 If you wish, you can also install any licenses or other documentation,
175 either alongside the font or in a corresponding directory under
176 <filename class="directory">/usr/share/doc/</filename>.
177 </para>
179 <para>
180 A few fonts ship with source as well as with the completed TTF or OTF
181 file(s). Unless you intend to modify the font, and have the correct tools
182 (sometimes <xref linkend="fontforge"/>, but often commercial tools), the
183 source will provide no benefit, so do not install it. One or two fonts even
184 ship with Web Open Font Format (WOFF) files - useful if you run a webserver
185 and want to use that font on it, but not useful for desktops.
186 </para>
188 <para>
189 To provide greater Unicode coverage, you are recommended to install
190 some of the following fonts, depending on what webistes and languages you
191 wish to read. The next part of this page details some fonts which cover
192 at least latin alphabets, the final part deals with come CJK issues.
193 </para>
195 <note>
196 <para>
197 You are strongly recommended to install the <xref
198 linkend="dejavu-fonts"/>.
199 </para>
200 </note>
202 <!-- fonts covering at least latin languages, order alphabetically
203 NB the xreflabel in the bridgehead is used in any link names, the
204 associated text is embiggened for the heading, the text for the
205 sortas appears as the key in the longindex -->
207 <bridgehead renderas="sect3" id="Caladea"
208 xreflabel="Caladea">Caladea</bridgehead>
210 <para><ulink
211 url="">Caladea</ulink>
212 (created as a Chrome OS extra font, hence the 'crosextrafonts' tarball
213 name) is metrically compatible with MS Cambria and can be used if you have
214 to edit a document which somebody started in Microsoft Office using
215 Cambria and then return it to them.</para>
217 <bridgehead renderas="sect3" id="cantarell-fonts"
218 xreflabel="Cantarell fonts">Cantarell fonts</bridgehead>
220 <indexterm zone="TTF-and-OTF-fonts cantarell-fonts">
221 <primary sortas="a-cantarell-fonts">Cantarell fonts</primary>
222 </indexterm>
224 <para><ulink
225 url="&gnome-download-http;/cantarell-fonts/0.0/">Cantarell fonts</ulink>
226 - The Cantarell typeface family provides a contemporary Humanist sans
227 serif. It is particularly optimised for legibility at small sizes and is
228 the preferred font family for the <application>GNOME-3</application> user
229 interface.</para>
231 <bridgehead renderas="sect3" id="Carlito"
232 xreflabel="Carlito">Carlito</bridgehead>
234 <para><ulink
235 url="">Carlito</ulink>
236 (created as another Chrome OS extra font, again the 'crosextrafonts-'
237 prefix in the tarball name) is metrically compatible with MS Calibri and
238 can be used if you have to edit a document which somebody started in
239 Microsoft Office using Calibri and then return it to them.</para>
241 <bridgehead renderas="sect3" id="dejavu-fonts"
242 xreflabel="Dejavu fonts">DejaVu fonts</bridgehead>
244 <indexterm zone="TTF-and-OTF-fonts dejavu-fonts">
245 <primary sortas="a-dejavu-fonts">DejaVu fonts</primary>
246 </indexterm>
248 <para>
249 <ulink
250 url="">DejaVu
251 fonts</ulink> - These fonts are an extension of, and replacement for, the
252 Bitstream Vera fonts and provide Latin-based scripts with accents and
253 punctuation such as "smart-quotes" and variant spacing characters, as well
254 as Cyrillic, Greek, Arabic, Hebrew, Armenian, Georgian and some other
255 glyphs. In the absence of the Bitstream Vera fonts (which had much less
256 coverage), these are the default fallback fonts.
257 </para>
259 <bridgehead renderas="sect3" id="kdefonts"
260 xreflabel="kdefonts">Fonts used by KDE</bridgehead>
262 <para>
263 When KDE Frameworks 5 began, it used <xref linkend="oxygen-fonts"/>
264 in 'startkde'. Those fonts are no-longer actively maintained, so KDE made
265 a decision to switch to <xref linkend="noto-fonts"/>. At the moment Noto
266 Sans is primarily used when running Gtk applications within KDE, and
267 Oxygen continues to be used by 'startkde'.
268 </para>
270 <para>
271 Those pages will eventually be merged into this section. If you use a
272 language which is not written in a latin, greek or cyrillic alphabet then
273 you should probably install at least Noto Sans itself (for any latin,
274 ASCII, common digits and punctuation), perhaps Noto Sans Symbols (for
275 currency symbols) and the separate Noto (Sans, if available) font
276 appropriate to that language, as well as the Oxygen fonts. An updated
277 link to download individual Noto fonts is <ulink
278 url=""></ulink>.
279 </para>
281 <para>
282 However, you should be aware that <application>fontconfig</application>
283 knows nothing about Noto fonts. The 'Noto Sans Something' fonts are each
284 treated as separate fonts (and for Arabic there is not a specifically Sans
285 name), so if you have other fonts installed then the choice of which font
286 to use for missing glyphs where 'Noto Sans' is specified will be random,
287 except that Sans fonts will be preferred over <emphasis>known</emphasis>
288 Serif and Monospace fonts because Sans is the fallback for unknown fonts.
289 </para>
291 <bridgehead renderas="sect3" id="freefont"
292 xreflabel="freefont">GNU FreeFont</bridgehead>
294 <para>
295 <ulink url="">GNU
296 FreeFont</ulink> - This set of fonts covers many non-CJK characters, in
297 particular some of the variants of latin and cyrillic letters used in
298 minority languages, but the glyphs are comparatively small (unlike DejaVu
299 fonts which are comparatively large) and rather light weight ("less black"
300 when black on white is used) which means that in some contexts such as
301 terminals they are not visually pleasing, for example when most other
302 glyphs are provided by another font. On the other hand, some fonts used
303 primarily for printed output, and many CJK fonts, are also light weight.
304 </para>
306 <bridgehead renderas="sect3" id="Gelasio"
307 xreflabel="Gelasio">Gelasio</bridgehead>
309 <para>
310 <ulink url="">Gelasio</ulink> is
311 metrically compatible with MS Georgia and
312 <application>fontconfig</application> will use it if ever Georgia is
313 requested but not installed.
314 </para>
316 <bridgehead renderas="sect3" id="liberation-fonts"
317 xreflabel="Liberation fonts">Liberation fonts</bridgehead>
319 <indexterm zone="TTF-and-OTF-fonts liberation-fonts">
320 <primary sortas="a-liberation-fonts">Liberation fonts</primary>
321 </indexterm>
323 <para>
324 The <ulink url="">Liberation
325 fonts</ulink> provide libre substitutes for Arial, Courier New, and Times
326 New Roman. <application>Fontconfig</application> will use them as
327 substitutes for those fonts, and also for the similar Helvetica, Courier,
328 Times Roman although for these latter it can prefer a different font (see
329 the examples in the 'Substitutes' PDFs at <ulink
330 url=""></ulink>
331 </para>
333 <para>
334 Many people will find the Liberation fonts useful for pages where one of
335 those fonts is requested.
336 </para>
338 <bridgehead renderas="sect3" id="corefonts"
339 xreflabel="corefonts">Microsoft Core Fonts</bridgehead>
341 <para>The <ulink url="">Microsoft Core
342 fonts</ulink> date from 2002. They were supplied with old versions of
343 Microsoft Windows and were apparently made available for general use.
344 You can extract them from the 'exe' files using
345 <application>bsd-tar</application> from <xref linkend="libarchive"/>.
346 Be sure to read the license before using them. At one time some of
347 these fonts (particularly Arial, Times New Roman, and to a lesser
348 extent Courier New) were widely specified on web pages. The full set
349 contains Andale Mono, Arial, Arial Black, Comic Sans MS, Courier
350 New, Georgia, Impact, Times New Roman, Trebuchet MS, Verdana and
351 Webdings.
352 </para>
354 <para>
355 Please note that if you only want to use a font with the same metrics
356 (character size, etc) as Arial, Courier New, or Times New Roman you can
357 use the libre Liberation Fonts (above), and similarly you can replace
358 Georgia with Gelasio.
359 </para>
361 <para>
362 Although many old posts recommend installing these fonts for
363 better-looking output, there are more recent posts that these are ugly
364 or 'broken'. One suggestion is that they do not support anti-aliasing.
365 </para>
367 <para>
368 The newer fonts which Microsoft made their defaults in later releases of
369 MS Windows or MS Office (Calibri and Cambria) have never been freely
370 available. But if you do not have them installed you can find metric
371 equivalents (Carlito, Caladea) above.
372 </para>
374 <bridgehead renderas="sect3" id="CJKfonts"
375 xreflabel="CJKfonts">CJK fonts:</bridgehead>
377 <para>
378 As indicated earlier, usage of a combination of Chinese, Japanese
379 and Korean can be tricky - each font only covers a subset of the available
380 codepoints, the preferred shapes of the glyphs can differ between the
381 languages, and many of the CJK fonts do not actually support modern
382 Korean.
383 </para>
385 <para>
386 Also, by default <application>fontconfig</application> prefers Chinese to
387 Japanese. Tuning that is covered at <xref
388 linkend="prefer-chosen-CJK-fonts"/>.
389 </para>
391 <para>
392 Although Unicode has been extended to allow a very large number of CJK
393 codepoints, those outside the Base Plane (greater than U+0xFFFF) are not
394 commonly used in Mandarin (the normal form of written Chinese, whether
395 Simplified (PRC) or Traditional (Taiwan)), or Japanese.
396 </para>
398 <para>
399 For Hong Kong, which uses Traditional Chinese and where Cantonese is the
400 dominant language, the Hong Kong Supplementary Character Set was added to
401 Unicode in 2005 and revised in 2009 (it is part of CJK Extension B and
402 contains more than 1900 characters). Earlier fonts will not be able to
403 support either Cantonese or use of these characters where local names are
404 written in Mandarin. The UMing HK, Noto Sans CJK HK and WenQuanYi Zen Hei
405 fonts all seem to cover Hong Kong usage
406 (<application>fontconfig</application> disagrees about Noto Sans CJK HK).
407 </para>
409 <para>
410 The Han glyphs are double-width, other glyphs in the same font may be
411 narrower. For their CJK content, all of these fonts can be regarded as
412 monospaced (i.e. fixed width).
413 </para>
415 <para>
416 If all you wish to do is to be able to render CJK glyphs, installing
417 <xref linkend="wenquanyi-zenhei"/> may be a good place to start if you do
418 not already have a preference.
419 </para>
421 <bridgehead renderas="sect3" id="Chinese-fonts"
422 xreflabel="Chinese fonts">Chinese fonts:</bridgehead>
424 <para>
425 In Chinese, there are three font styles in common use: Sung (also
426 known as Song or Ming) which is the most-common ornamented ("serif")
427 form, Kai ("brush strokes") which is an earlier ornamented style that
428 looks quite different, and modern Hei ("sans"). Unless you appreciate the
429 differences, you probably do not want to install Kai fonts.
430 </para>
432<!-- prefer the less-old Opendesktop-fonts to fireflysung
433 <bridgehead renderas="sect4" id="fireflysung"
434 xreflabel="fireflysung">Fireflysung</bridgehead>
436 <para>
437 <ulink
438 url="">fireflysung</ulink>
439 - This font ('AR PL New Sung') was one of the first libre fonts to
440 provides Chinese coverage. <application>fontconfig</application> knows
441 it is to be treated as a Serif font.
442 </para> -->
444 <bridgehead renderas="sect4" id="NotoSansCJK"
445 xreflabel="Noto Sans CJK">Noto Sans CJK</bridgehead>
447 <!-- indexterm entry retained for future linkage from kde -->
448 <indexterm zone="TTF-and-OTF-fonts NotoSansCJK">
449 <primary sortas="a-noto-sans-cjk">Noto Sans CJK</primary>
450 </indexterm>
452 <para><ulink
453 url="">Noto Sans CJK</ulink>
454 - Sans-Serif sets of all CJK fonts in a ttc - as the link says, you can
455 choose to install the TTC and cover all the languages in all weights in
456 a 110MB file, or you can download subsets. There are also Monospace
457 versions.
458 </para>
460 <bridgehead renderas="sect4" id="Opendesktop-fonts"
461 xreflabel="Opendesktop-fonts">Opendesktop fonts</bridgehead>
463 <para>A copy of version 1.4.2 of the <ulink
464 url="">opendesktop-fonts</ulink>
465 is preserved at Arch. This was a later development of fireflysung which
466 BLFS used to recommend, adding Kai and Mono fonts. The name of the Sung
467 font remains 'AR PL New Sung' so they cannot both be installed together.
468 </para>
470 <para>
471 At one time there was a 1.6 release, and more recently some versions at
472 github, which also included a Sans font (Odohei), but those have dropped
473 off the web and it is unclear if there was a problem.
474 <application>Fontconfig</application> does not know anything about the
475 later fonts (AR PL New Kai, AR PL New Sung Mono) and will default to
476 treating them as Sans.
477 </para>
479<!-- comment, because not recommended
480 <bridgehead renderas="sect4" id="UKai"
481 xreflabel="UKai">UKai</bridgehead>
483 <para>
484 <ulink
485 url="">UKai fonts</ulink>
486 - sets of Chinese Kai fonts in a ttc which contain variations of
487 Simplified and Traditional (Taiwanese, second variant for different
488 <ulink url="">bopomofo</ulink>,
489 and Cantonese). This ships with old-syntax files which can install to
490 <filename class="directory">/etc/fonts/conf.d/</filename> but see <xref
491 linkend="editing-old-style-conf-files"/>.
492 </para>
495 <bridgehead renderas="sect4" id="UMing"
496 xreflabel="UMing">UMing</bridgehead>
498 <para>
499 <ulink
500 url="">UMing fonts</ulink>
501 - sets of Chinese Ming fonts (from Debian, use the '.orig' tarball) in
502 a ttc which contain variations of Simplified and Traditional Chinese
503 (Taiwanese, with second variant for different
504 <ulink url="">bopomofo</ulink>,
505 and Cantonese for Hong Kong). This ships with old-syntax files which you
506 can install to
507 <filename class="directory">/etc/fonts/conf.d/</filename> but see <xref
508 linkend="editing-old-style-conf-files"/>.
509 </para>
511 <bridgehead renderas="sect4" id="wenquanyi-zenhei"
512 xreflabel="WenQuanYi ZenHei">WenQuanYi Zen Hei</bridgehead>
514 <indexterm zone="TTF-and-OTF-fonts wenquanyi-zenhei">
515 <primary sortas="a-wenquanyi-zenhei">WenQuanYi Zen Hei</primary>
516 </indexterm>
518 <para>
519 <ulink
520 url="">WenQuanYi
521 Zen Hei</ulink> provides a Sans-Serif font which covers all CJK scripts
522 including Korean. Although it includes old-style conf files, these are
523 not required: <application>fontconfig</application> will already treat
524 these fonts (the 'sharp' contains bitmaps, the monospace appears not
525 to be Mono in its ASCII part) as Sans, Serif, and Monospace. If all
526 you wish to do is to be able to render Han and Korean text without
527 worrying about the niceties of the shapes used, the main font from
528 this package is a good font to use.
529 </para>
532 <bridgehead renderas="sect3" id="Japanese-fonts"
533 xreflabel="Japanese fonts">Japanese fonts:</bridgehead>
535 <para>
536 In Japanese, Gothic fonts are Sans, Mincho are Serif. BLFS used to
537 only mention the Kochi fonts, but those appear to now be the
538 least-preferred of the Japanese fonts.
539 </para>
541 <para>
542 Apart from the fonts detailed below, also consider <xref
543 linkend="NotoSansCJK"/>.
544 </para>
546 <bridgehead renderas="sect4" id="IPAex"
547 xreflabel="IPAex fonts">IPAex fonts</bridgehead>
549 <!-- indexterm retained for expected link from tuning fontconfig -->
550 <indexterm zone="TTF-and-OTF-fonts IPAex">
551 <primary sortas="a-ipaex-fonts">IPAex fonts</primary>
552 </indexterm>
554 <para>
555 The <ulink url="">IPAex fonts</ulink> are
556 the current version of the IPA fonts. Click on 'English' at the link and
557 then click on the Download icon to find IPAex Font Ver.003.01.
558 Unfortunately, <application>fontconfig</application> only knows about
559 the older IPAfonts and the forked IPA Mona font (which is not easily
560 available and which apparently does not meet Debian's Free Software
561 guidelines). Therefore if you install the IPAex fonts you may wish
562 to make it known to fontconfig, see <xref
563 linkend="prefer-chosen-CJK-fonts"/> for one possible way to do this.
564 </para>
566 <bridgehead renderas="sect4" id="Kochi"
567 xreflabel="Kochi">Kochi fonts</bridgehead>
569 <para>
570 The <ulink url="">Kochi
571 Substitute fonts</ulink> were the first truly libre Japanese fonts (the
572 earlier Kochi fonts were allegedly plagiarized from a commercial font).
573 </para>
575 <bridgehead renderas="sect4" id="VLGothic"
576 xreflabel="VL Gothic">VL Gothic</bridgehead>
578 <indexterm zone="TTF-and-OTF-fonts VLGothic">
579 <primary sortas="a-vlgothic-fonts">VL Gothic</primary>
580 </indexterm>
582 <para>
583 The <ulink url="">VL
584 Gothic</ulink> font is a modern Japanese font in two variants with
585 monotonic or proportional spacing for the non-Japanese characters.
586 </para>
589 <bridgehead renderas="sect3" id="Korean-fonts"
590 xreflabel="Korean fonts">Korean fonts:</bridgehead>
592 <para>
593 In Korean, Batang or Myeongjo (the older name) are Serif, Dotum or
594 Gothic are the main Sans fonts. BLFS previously recommended the Baekmuk
595 fonts, but the Nanum and Un fonts are now preferred to Baekmuk by
596 <application>fontconfig</application> because of user requests.
597 </para>
599 <!-- when testing, my previous Nanum link gave permission errors, so
600 link to a general page, at the cost of making it more complicated to
601 download -->
603 <para>
604 A convenient place to see examples of these and many other Korean
605 fonts is <ulink url="">Free Korean
606 Fonts</ulink>. Click on 'Gothic Fonts' or 'All Categories -> Myeongjo
607 Fonts', then click on the font example to see more details including the
608 License, and click on the link to download it. For Nanum, you will need
609 to be able to read Korean to find the download link on the page you get
610 to. For Un there are direct links and you can find the un-fonts-core
611 tarball in the <filename class="directory">releases/</filename>
612 directory.
613 </para>
615 <para>Alternatively, consider <xref linkend="NotoSansCJK"/> (a11 of the
616 variants cover Hangul) or <xref linkend="wenquanyi-zenhei"/>.
617 </para>
619 </sect2>
Note: See TracBrowser for help on using the repository browser.