• R/O
  • SSH
  • HTTPS

tsukurimashou: Commit


Commit MetaInfo

Revision484 (tree)
Time2013-11-10 13:43:44
Authormskala

Log Message

change name, Jieubsida to Mandeubsida

Change Summary

Incremental Difference

--- trunk/txt/jnames.txt (revision 483)
+++ trunk/txt/jnames.txt (revision 484)
@@ -60,7 +60,7 @@
6060 monospace l___da
6161 proportional PS
6262
63-jieubsida 지읍시다
63+mandeubsida 만듭시다
6464
6565 dodum 돋움
6666 batang 바탕
--- trunk/website/glyphgrid.tex (revision 483)
+++ trunk/website/glyphgrid.tex (revision 484)
@@ -2,7 +2,7 @@
22
33 %
44 % Tsukurimashou glyph grid
5-% Copyright (C) 2012 Matthew Skala
5+% Copyright (C) 2012, 2013 Matthew Skala
66 %
77 % This program is free software: you can redistribute it and/or modify
88 % it under the terms of the GNU General Public License as published by
@@ -62,7 +62,7 @@
6262 \node[anchor=south west] at ($(current page.south west)+(\x-0.06,\y)$)
6363 {\scalebox{5.95}{\z}};
6464 }
65- \setmainfont[RawFeature={+ccmp,+ljmo,+vjmo,+liga}]{JieubsidaDodum}
65+ \setmainfont[RawFeature={+ccmp,+ljmo,+vjmo,+liga}]{MandeubsidaDodum}
6666 \foreach \x/\y/\z in
6767 {0/2/호,1/2/와,2/2/께,3/2/무,4/2/이,5/2/A,6/2/Q,7/2/q,8/2/t,9/2/i} {
6868 \node[anchor=south west] at ($(current page.south west)+(\x-0.06,\y)$)
@@ -77,7 +77,7 @@
7777 \node[anchor=south west] at ($(current page.south west)+(\x-0.06,\y)$)
7878 {\scalebox{5.95}{\z}};
7979 }
80- \setmainfont[RawFeature={+ccmp,+ljmo,+vjmo,+liga}]{JieubsidaBatang}
80+ \setmainfont[RawFeature={+ccmp,+ljmo,+vjmo,+liga}]{MandeubsidaBatang}
8181 \foreach \x/\y/\z in
8282 {0/7/하,1/7/였,2/7/후,3/7/로,4/7/는,5/7/E,6/7/S,7/7/f,8/7/v,9/7/n} {
8383 \node[anchor=south west] at ($(current page.south west)+(\x-0.06,\y)$)
--- trunk/doc/demo.tex (revision 483)
+++ trunk/doc/demo.tex (revision 484)
@@ -2,7 +2,7 @@
22
33 %
44 % Demo for Tsukurimashou
5-% Copyright (C) 2011, 2012 Matthew Skala
5+% Copyright (C) 2011, 2012, 2013 Matthew Skala
66 %
77 % This program is free software: you can redistribute it and/or modify
88 % it under the terms of the GNU General Public License as published by
@@ -49,7 +49,7 @@
4949 % Just because all these are conditional doesn't mean all invocations of
5050 % them are conditional. If you really disable core fonts, you'll lose.
5151 % The main point is just to allow people to build a demo without
52-% Jieubsida, since that's the default configuration.
52+% Mandeubsida, since that's the default configuration.
5353
5454 \expandafter\ifx\csname haveTsukurimashouKakuPS\endcsname\relax\else
5555 \newfontface\kaku{TsukurimashouKakuPS}
@@ -75,16 +75,16 @@
7575 \newfontface\bokukko{TsukurimashouBokukkoPS}
7676 \fi
7777
78-\expandafter\ifx\csname haveJieubsidaBatangPS\endcsname\relax\else
79- \newfontface\batang[RawFeature={+ccmp,+ljmo,+vjmo,+liga}]{JieubsidaBatangPS}
78+\expandafter\ifx\csname haveMandeubsidaBatangPS\endcsname\relax\else
79+ \newfontface\batang[RawFeature={+ccmp,+ljmo,+vjmo,+liga}]{MandeubsidaBatangPS}
8080 \fi
8181
82-\expandafter\ifx\csname haveJieubsidaDodumPS\endcsname\relax\else
83- \newfontface\dodum[RawFeature={+ccmp,+ljmo,+vjmo,+liga}]{JieubsidaDodumPS}
82+\expandafter\ifx\csname haveMandeubsidaDodumPS\endcsname\relax\else
83+ \newfontface\dodum[RawFeature={+ccmp,+ljmo,+vjmo,+liga}]{MandeubsidaDodumPS}
8484 \fi
8585
86-\expandafter\ifx\csname haveJieubsidaSunMoonPS\endcsname\relax\else
87- \newfontface\sunmoon[RawFeature={+ccmp,+ljmo,+vjmo,+liga}]{JieubsidaSunMoonPS}
86+\expandafter\ifx\csname haveMandeubsidaSunMoonPS\endcsname\relax\else
87+ \newfontface\sunmoon[RawFeature={+ccmp,+ljmo,+vjmo,+liga}]{MandeubsidaSunMoonPS}
8888 \fi
8989
9090 \expandafter\ifx\csname haveTsukurimashouKaku\endcsname\relax\else
@@ -428,13 +428,13 @@
428428
429429 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
430430
431-\expandafter\ifx\csname haveJieubsidaDodumPS\endcsname\relax\else
431+\expandafter\ifx\csname haveMandeubsidaDodumPS\endcsname\relax\else
432432
433433 \dodum
434434
435435 \Large
436-지읍시다돋움\\
437-Jieubsida Dodum
436+만듭시다돋움\\
437+Mandeubsida Dodum
438438
439439 \normalsize
440440
@@ -450,13 +450,13 @@
450450
451451 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
452452
453-\expandafter\ifx\csname haveJieubsidaBatangPS\endcsname\relax\else
453+\expandafter\ifx\csname haveMandeubsidaBatangPS\endcsname\relax\else
454454
455455 \batang
456456
457457 \Large
458-지읍시다바탕\\
459-Jieubsida Batang
458+만듭시다바탕\\
459+Mandeubsida Batang
460460
461461 \normalsize
462462
@@ -473,17 +473,17 @@
473473
474474 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
475475
476-\expandafter\ifx\csname haveJieubsidaSunMoonPS\endcsname\relax\else
476+\expandafter\ifx\csname haveMandeubsidaSunMoonPS\endcsname\relax\else
477477
478478 \sunmoon
479479
480480 \Large
481-지읍시다선문\\
482-Jieubsida Sun-Moon
481+만듭시다선문\\
482+Mandeubsida Sun-Moon
483483
484484 \normalsize
485485
486-Jieubsida Sun-Moon has a similar look to Tsukurimashou Bokukko, reminiscent
486+Mandeubsida Sun-Moon has a similar look to Tsukurimashou Bokukko, reminiscent
487487 of hand lettering with a felt-tip marker. It is named after a character
488488 from the Web comic Bonobo Conspiracy.
489489
@@ -575,7 +575,7 @@
575575 あそこで言語の変態をしましょう!」。%
576576 \footnote{日本語 (Japanese), Tsukurimashou Project.}
577577
578-\expandafter\ifx\csname haveJieubsidaDodumPS\endcsname\relax\else
578+\expandafter\ifx\csname haveMandeubsidaDodumPS\endcsname\relax\else
579579 {\dodum%
580580 여호와께서 가라사대 이 무리가 한 족속이요, 언어도 하나이므로 이같이
581581 시작하였으니 이후로는 그 경영하는 일을 금지할 수 없으리로다.
--- trunk/doc/proofs.tex (revision 483)
+++ trunk/doc/proofs.tex (revision 484)
@@ -80,9 +80,9 @@
8080 \newfontface\kakudemo[WordSpace={1,0,0},PunctuationSpace=3]{TsukurimashouKaku}
8181 \newfontface\minchodemo[WordSpace={1,0,0},PunctuationSpace=3]{TsukurimashouMincho}
8282 \newfontface\dodumdemo[WordSpace={1,0,0},PunctuationSpace=3,%
83- RawFeature={+liga,+ljmo,+vjmo}]{JieubsidaDodum}
83+ RawFeature={+liga,+ljmo,+vjmo}]{MandeubsidaDodum}
8484 \newfontface\batangdemo[WordSpace={1,0,0},PunctuationSpace=3,%
85- RawFeature={+liga,+ljmo,+vjmo}]{JieubsidaBatang}
85+ RawFeature={+liga,+ljmo,+vjmo}]{MandeubsidaBatang}
8686 \newfontface\atamademo[WordSpace={1,0,0},PunctuationSpace=3]{TsuItaAtama}
8787 \newfontface\sokudemo[WordSpace={1,0,0},PunctuationSpace=3]{TsuItaSoku}
8888 \newfontface\cosettedemo[WordSpace={1,0,0},PunctuationSpace=3]{BlackletterLolitaCosette}
@@ -93,7 +93,7 @@
9393 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
9494
9595 \newcommand{\tsukuDemoFonts}{\let\KDF\kakudemo\let\MDF\minchodemo\relax}
96-\newcommand{\jieubDemoFonts}{\let\KDF\dodumdemo\let\MDF\batangdemo\relax}
96+\newcommand{\mandeDemoFonts}{\let\KDF\dodumdemo\let\MDF\batangdemo\relax}
9797 \newcommand{\tsuitaDemoFonts}{\let\KDF\atamademo\let\MDF\sokudemo\relax}
9898 \newcommand{\bllDemoFonts}{\let\KDF\cosettedemo\let\MDF\cosettedemo\relax}
9999
--- trunk/doc/usermanual.tex (revision 483)
+++ trunk/doc/usermanual.tex (revision 484)
@@ -62,8 +62,8 @@
6262 \newfontface\tenshinokami{TsukurimashouTenshinoKamiPS}
6363 \newfontface\bokukko{TsukurimashouBokukkoPS}
6464
65-\expandafter\ifx\csname haveJieubsidaDodumPS\endcsname\relax\else
66- \newfontface\dodum[RawFeature={+ccmp,+ljmo,+vjmo,+liga}]{JieubsidaDodumPS}
65+\expandafter\ifx\csname haveMandeubsidaDodumPS\endcsname\relax\else
66+ \newfontface\dodum[RawFeature={+ccmp,+ljmo,+vjmo,+liga}]{MandeubsidaDodumPS}
6767 \fi
6868
6969 \expandafter\ifx\csname haveTsuItaSokuPS\endcsname\relax
@@ -226,7 +226,7 @@
226226 code; but I've provided parameters for several ready-made faces, each of
227227 which can be drawn in monospace or proportional forms. The mainline
228228 Tsukurimashou fonts are intended for Japanese, but version 0.5 also
229-introduced a series of fonts called Jieubsida, designed for Korean
229+introduced a series of fonts called Mandeubsida, designed for Korean
230230 hangul. There is also some experimental code intended to eventually become
231231 a set of blackletter fonts, but it is disabled by default and not currently
232232 usable.
@@ -295,7 +295,7 @@
295295
296296 \item Support of Korean is limited because of my limited knowledge
297297 of that language; and learning it is not a high priority for me. At
298- this point the Jieubsida fonts only support Korean hangul, not hanja
298+ this point the Mandeubsida fonts only support Korean hangul, not hanja
299299 (which are the Korean equivalent of kanji, but just different enough
300300 that copying over the Tsukurimashou kanji would not be good enough).
301301
@@ -351,7 +351,7 @@
351351 for it. Having a pay option will also give anybody who wants to support my
352352 efforts, an easy way to do that. For now, though, I am distributing
353353 Tsukurimashou only as this source package, with precompiled versions
354-included for the Kaku and Mincho styles. The Jieubsida fonts, which don't
354+included for the Kaku and Mincho styles. The Mandeubsida fonts, which don't
355355 need the in-progress kanji glyphs, may also be available in precompiled form
356356 as a separate package. If you want other styles, you'll have to compile
357357 them yourself or get them from someone who has done so. This limitation is
@@ -659,10 +659,10 @@
659659 horizontal axis is labelled by version but scaled by time. Even-numbered
660660 versions tend to take more time because I tend to do the easier characters
661661 in each grade level first. All the glyph counts in these charts are for the
662-Tsukurimashou (Japanese) fonts alone. The Jieubsida (Korean) fonts contain
662+Tsukurimashou (Japanese) fonts alone. The Mandeubsida (Korean) fonts contain
663663 the 11172-glyph block of precomposed syllables, which because they are
664664 algorithmically generated cannot be well compared to the more
665-manually-created kanji and other glyphs. The Jieubsida fonts also contain a
665+manually-created kanji and other glyphs. The Mandeubsida fonts also contain a
666666 few hundred non-precomposed glyphs, beyond the core they share with
667667 Tsukurimashou.
668668
@@ -733,8 +733,8 @@
733733 Figure~\ref{fig:loc-per-glyph} gives a different view of development
734734 progress: the number of lines of code (total lines in mp/*.mp, including
735735 comments and blanks but not including code in other languages and locations;
736-also excluding jieub-*.mp, but still including a few other files from
737-Jieubsida) plotted against the total number of glyphs in the main
736+also excluding mande-*.mp, but still including a few other files from
737+Mandeubsida) plotted against the total number of glyphs in the main
738738 Tsukurimashou family.
739739
740740 \begin{figure}
@@ -945,7 +945,7 @@
945945 which has complicated indirect consequences because the Tsukurimashou
946946 infrastructures uses BDF files as input to the auto-kerning program. As
947947 a result, when this bug bites the horizontal metrics go screwy on some
948- fonts---notably, Jieubsida Batang PS ends up looking monospaced.
948+ fonts---notably, Mandeubsida Batang PS ends up looking monospaced.
949949 Reported to FontForge mailing list in November 2011, inspiring FreeType
950950 maintainer Werner Lemberg to find and fix an unrelated bug in FreeType
951951 (it was unable to process BDF files with high code points; see
@@ -1235,7 +1235,7 @@
12351235 Similarly, this feature will substitute precomposed voiced kana glyphs for
12361236 combinations of unvoiced kana plus combining dakuten or handakuten.
12371237
1238-In the Jieubsida fonts, this feature breaks precomposed
1238+In the Mandeubsida fonts, this feature breaks precomposed
12391239 syllables that don't have final consonants into their component jamo, and
12401240 combines sequences of jamo for single vowels and consonants into jamo
12411241 representing the sequences, where possible. Splitting tail-less precomposed
@@ -1257,7 +1257,7 @@
12571257 was a design decision to make the letters look good without ligatures even
12581258 in proportional fonts.
12591259
1260-The Jieubsida fonts, however, contain an extensive ligature table for
1260+The Mandeubsida fonts, however, contain an extensive ligature table for
12611261 hangul, and use of this feature is required to get full support for hangul
12621262 script. Without it, the decomposition of precomposed tail-less syllables in
12631263 the ``ccmp'' feature will stand, leaving those syllables looking poorly
@@ -1271,7 +1271,7 @@
12711271
12721272 \blsubsection{頭子音の形}{Lead Jamo Shaping (ljmo)}
12731273
1274-This feature only exists in the Jieubsida fonts and should be turned on by
1274+This feature only exists in the Mandeubsida fonts and should be turned on by
12751275 default. It replaces ``lead'' jamo glyphs (consonants at the starts of
12761276 syllables) with contextual variants that depend on the vowel and the
12771277 presence or absence of a tail. For more information, see the section on
@@ -1481,7 +1481,7 @@
14811481
14821482 \blsubsection{母音の形}{Vowel Jamo Shaping (vjmo)}
14831483
1484-This feature only exists in the Jieubsida fonts, and should be turned on by
1484+This feature only exists in the Mandeubsida fonts, and should be turned on by
14851485 default when it exists. It replaces ``vowel'' jamo glyphs with appropriate
14861486 contextual variations depending on the layout of the syllable. The layout
14871487 that will be used by ``vjmo'' is actually chosen during execution of the
@@ -1504,7 +1504,7 @@
15041504 Unicode character in ordinary text. This feature removes the private-use
15051505 code points from many such glyphs.
15061506
1507-For instance, in Jieubsida there is a glyph named ``uni112A'' for code point
1507+For instance, in Mandeubsida there is a glyph named ``uni112A'' for code point
15081508 U+112A, but there is also a glyph named ``uni112A.bug'' which looks
15091509 identical but is referenced in the substitution table in order to work
15101510 around a bug in the ICU library used by \XeTeX. The uni112A.bug glyph, as
@@ -1651,10 +1651,10 @@
16511651
16521652 \blsection{ハングル語}{Korean Language Support}
16531653
1654-\expandafter\ifx\csname haveJieubsidaDodumPS\endcsname\relax
1654+\expandafter\ifx\csname haveMandeubsidaDodumPS\endcsname\relax
16551655
16561656 This user manual was built without the Korean fonts (in particular,
1657-Jieubsida Dodum PS) and as a result, the section on Korean support cannot be
1657+Mandeubsida Dodum PS) and as a result, the section on Korean support cannot be
16581658 typeset.
16591659
16601660 \else
@@ -1670,14 +1670,16 @@
16701670 Korean has some degree of connection to Japanese, the hangul writing system
16711671 used for it is technically interesting and superficially appears easy, and
16721672 for various reasons, I decided to extend Tsukurimashou to include some
1673-support for Korean. The result is the ``Jieubsida'' {\dodum 「지읍시다」}
1674-series of fonts. The name is as nearly as possible a direct translation
1675-from Japanese to Korean of the name ``Tsukurimashou'' 「作りましょう」.
1676-Jieubsida builds from the same code base as Tsukurimashou, if you select the
1673+support for Korean. The result is the ``Mandeubsida'' {\dodum 「만듭시다」}
1674+series of fonts. The name is intended to be a direct translation
1675+from Japanese to Korean of the name ``Tsukurimashou'' 「作りましょう」;
1676+prior to version 0.9 these fonts were called ``Jieubsida'' {\dodum
1677+「지읍시다」}, which I'm told is not a good translation.
1678+Mandeubsida builds from the same code base as Tsukurimashou, if you select the
16771679 appropriate options during configuration.
16781680
16791681 There are several ways to write Korean in Unicode, and they are
1680-supported to varying degress by Jieubsida:
1682+supported to varying degress by Mandeubsida:
16811683 \begin{itemize}
16821684 \item Individual jamo from the ``hangul compatibility jamo'' range
16831685 of code points, U+3131 to U+318E.
@@ -1691,7 +1693,7 @@
16911693
16921694 Hangul is theoretically a purely phonetic alphabet. Letters are called
16931695 jamo, and each one is supposed to correspond to exactly one phoneme of the
1694-Korean language. The set of jamo in Unicode and Jieubsida is a little
1696+Korean language. The set of jamo in Unicode and Mandeubsida is a little
16951697 bigger than in the standard present-day Korean language, as a result of
16961698 historical changes in the centuries since the writing system was introduced.
16971699 The rules for how jamo may be used together have also become more
@@ -1731,7 +1733,7 @@
17311733
17321734 \blsubsection{コンパチのジャモ}{Compatibility jamo}
17331735
1734-The ``hangul compatibility jamo'' range is fully supported by Jieubsida.
1736+The ``hangul compatibility jamo'' range is fully supported by Mandeubsida.
17351737 It's easy: one jamo per character box. But it is not done to actually write
17361738 the Korean language that way; readers and writers want one syllable per
17371739 character box, with the individual jamo changing size and layout to pack
@@ -1739,7 +1741,7 @@
17391741 useful in documents like this one, which discuss the technical details of
17401742 the writing system.
17411743
1742-Hangul compatibility jamo look like {\dodum 「ㅈㅣㅇㅡㅂㅅㅣㄷㅏ」}.
1744+Hangul compatibility jamo look like {\dodum 「ㅁㅏㄴㄷㅡㅂㅅㅣㄷㅏ」}.
17431745 Writing words that way leads to some ambiguity in syllable division, which
17441746 may be one reason it never caught on (though the same ambiguity exists in
17451747 most Romanization forms).
@@ -1756,10 +1758,10 @@
17561758 them that actually occurs in present-day relatively standardized Korean, can
17571759 be used to write the present-day language with a minimum of fuss. That's
17581760 what most people do; most Korean documents on the Web are encoded into that
1759-range of Unicode; and Jieubsida contains the full set of glyphs to support
1761+range of Unicode; and Mandeubsida contains the full set of glyphs to support
17601762 it.
17611763
1762-The precomposed syllables look like {\dodum 「지읍시다」}.
1764+The precomposed syllables look like {\dodum 「만듭시다」}.
17631765
17641766 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
17651767
@@ -1776,7 +1778,7 @@
17761778 The main sequence of Unicode jamo code points is in U+1100 through U+11FF;
17771779 then there are ``extension'' blocks in U+A960 through U+A97C (extension A,
17781780 for leads) and U+D7B0 through U+D7FB (extension B, for vowels and tails).
1779-As of version 0.6, Jieubsida supports them all, although some rare vowels
1781+As of version 0.6, Mandeubsida supports them all, although some rare vowels
17801782 that pose visual layout problems (such as U+D7BE {\dodum 「\char"D7BE」})
17811783 may not look as good as you might hope.
17821784
@@ -1811,11 +1813,11 @@
18111813 space reserved for it on the right in every lead jamo glyph.
18121814
18131815 Conjoining jamo overlaid in this way look like
1814-{\fontspec[RawFeature={+ccmp,-ljmo,-vjmo,-liga}]{JieubsidaDodumPS}%
1815-「\char"110C\char"1175%
1816-\char"110B\char"1173\char"11B8%
1816+{\fontspec[RawFeature={+ccmp,-ljmo,-vjmo,-liga}]{MandeubsidaDodumPS}%
1817+「\char"1106\char"1161\char"11AB%
1818+\char"1103\char"1173\char"11B8%
18171819 \char"1109\char"1175%
1818-\char"1103\char"1161」}; compare with precomposed {\dodum 「지읍시다」}. It
1820+\char"1103\char"1161」}; compare with precomposed {\dodum 「만듭시다」}. It
18191821 does not look very appealing, especially because that's a near-worst-case
18201822 example where three out of four syllables have empty tails and the fixed
18211823 layout cannot stretch jamo to consume the resulting blank space; but this
@@ -1833,7 +1835,7 @@
18331835 layout of each syllable depending on all the jamo in the syllable, so that
18341836 any given jamo might appear in hundreds of subtly different sizes and
18351837 locations. It is not practical to store all those variations of every jamo
1836-as individual glyphs, but Jieubsida compromises by recognizing six different
1838+as individual glyphs, but Mandeubsida compromises by recognizing six different
18371839 standardized layouts for a syllable, depending on the shape of the vowel and
18381840 the presence or absence of a nonempty tail.
18391841
@@ -1899,13 +1901,13 @@
18991901 With the alternate forms chosen by the substitution rules, but no
19001902 precomposed syllables, the font
19011903 family name is rendered as
1902-{\fontspec[RawFeature={+ccmp,+ljmo,+vjmo,-liga}]{JieubsidaDodumPS}
1903-「\char"110C\char"1175%
1904-\char"110B\char"1173\char"11B8%
1904+{\fontspec[RawFeature={+ccmp,+ljmo,+vjmo,-liga}]{MandeubsidaDodumPS}
1905+「\char"1106\char"1161\char"11AB%
1906+\char"1103\char"1173\char"11B8%
19051907 \char"1109\char"1175%
19061908 \char"1103\char"1161」}.
19071909 Note that is almost identical to the
1908-precomposed-syllable version, {\dodum 「지읍시다」}. There are some minor
1910+precomposed-syllable version, {\dodum 「만듭시다」}. There are some minor
19091911 differences in the size and spacing of the jamo, because the
19101912 glyph-overlay approach basically makes kerning impossible, and the six
19111913 canned layouts still do not quite match the per-syllable customized layouts
@@ -1920,11 +1922,11 @@
19201922 effect, actually entering the conjoining jamo for the
19211923 standardized present-day Korean language will give the same result as using
19221924 the precomposed code points. The family name entered this way appears as
1923-{\dodum 「\char"110C\char"1175%
1924-\char"110B\char"1173\char"11B8%
1925+{\dodum 「\char"1106\char"1161\char"11AB%
1926+\char"1103\char"1173\char"11B8%
19251927 \char"1109\char"1175%
19261928 \char"1103\char"1161」}, which should be both visually and logically
1927-(same glyph sequence) identical to {\dodum 「지읍시다」}.
1929+(same glyph sequence) identical to {\dodum 「만듭시다」}.
19281930
19291931 Also worth mentioning is the ``ccmp'' feature, which is supposed to run
19301932 before all others. It splits precomposed syllables that have no tails into
@@ -1938,7 +1940,7 @@
19381940 thinks you want to do, such as putting conjoining tail {\dodum 「ㅁ」} after
19391941 precomposed {\dodum 「기」} and expecting it to turn into precomposed
19401942 {\dodum 「기\char"11B7」}. I'm told that not many fonts actually support
1941-that. Jieubsida does! However, I cannot promise that absolutely every
1943+that. Mandeubsida does! However, I cannot promise that absolutely every
19421944 weird Unicode thing will work. Most of them should.
19431945
19441946 The big win is that with all the substitution
@@ -1983,7 +1985,7 @@
19831985 recent; but if you write the present-day Japanese form where you should
19841986 write the Korean form, it will look wrong.
19851987
1986-The current versions of the Jieubsida/Tsukurimashou fonts address this issue
1988+The current versions of the Mandeubsida/Tsukurimashou fonts address this issue
19871989 by simply not supporting hanja at all.
19881990
19891991 Supporting hanja would mean going through the entire set of kanji, finding
@@ -1998,7 +2000,7 @@
19982000 project.
19992001
20002002 It's easy to imagine that someone could build a font containing both the
2001-kanji glyphs from Tsukurimashou and the hangul glyphs from Jieubsida, and
2003+kanji glyphs from Tsukurimashou and the hangul glyphs from Mandeubsida, and
20022004 then try to use it to write hanja. I hope you will not attempt that, and
20032005 the Tsukurimashou build system is designed not to build such fonts. There
20042006 are too many fonts like that on the Net already as a result of people's
@@ -2007,7 +2009,7 @@
20072009 I can't stop people from creating such chimeras for their own use, but I
20082010 don't want someone to create a Korean-language document with Japanese fake
20092011 hanja in it, be asked ``What is that horrible font you're using that gets
2010-the hanja shapes wrong?'' and have them say ``It's Jieubsiuda by Matthew
2012+the hanja shapes wrong?'' and have them say ``It's Mandeubsida by Matthew
20112013 Skala!'' Please, if you're going to set kanji next to hangul and call them
20122014 hanja, try to make clear to people who see the results that it was your idea
20132015 to do that and not mine.
@@ -2023,7 +2025,7 @@
20232025 First, I will use the term ``font'' to refer to an OTF or similar file with
20242026 a complete glyph set (or as many glyphs as have been selected with
20252027 configure). This will generally be a few thousand glyphs for the
2026-Tsukurimashou family and about 13 thousand for the Jieubsida family.
2028+Tsukurimashou family and about 13 thousand for the Mandeubsida family.
20272029 Because METATYPE1 is limited to producing Postscript font files with at most
20282030 256 glyphs each, the system builds ``subfonts'' each corresponding to a
20292031 ``page'' of the Unicode character set---that is, an aligned 256-code-point
@@ -2050,7 +2052,7 @@
20502052 same overall shapes for all glyphs, though the visual style of the strokes
20512053 will vary. If there are significant differences in shapes or glyph sets,
20522054 they will be put in a separate family. At present the supported values for
2053-the family are ``tsukurimashou,'' ``tsuita,'' and ``jieubsida,'' though
2055+the family are ``tsukurimashou,'' ``tsuita,'' and ``mandeubsida,'' though
20542056 there is also some experimental (less than alpha status) code for
20552057 families to be called ``blackletter\_lolita'' and ``kazoemashou.''
20562058
@@ -2064,7 +2066,7 @@
20642066 \item{\anbiruteki tsukurimashou} kaku, maru, mincho, bokukko,
20652067 anbiruteki$^*$, tenshinokami$^*$.
20662068 \item{\anbiruteki tsuita} soku, atama.
2067- \item{\anbiruteki jieubsida} dodum, batang, sunmoon.
2069+ \item{\anbiruteki mandeubsida} dodum, batang, sunmoon.
20682070 \item{\anbiruteki blackletter\_lolita} cosette.
20692071 \item{\anbiruteki kazoemashou} seisuu.
20702072 \end{description}
@@ -2168,7 +2170,7 @@
21682170
21692171 There are also ``JK names,'' which are constructed just like long names but
21702172 with elements written in Japanese or Korean, and thus generally in non-ASCII
2171-Unicode characters. For Jieubsida fonts these should be in Korean (but the
2173+Unicode characters. For Mandeubsida fonts these should be in Korean (but the
21722174 occasional Japanese or English word may appear because of a
21732175 yet-unimplemented translation feature) and have spaces between the elements;
21742176 otherwise JK names are in Japanese and have no spaces. The main use of JK
@@ -3282,7 +3284,7 @@
32823284 class can be too big or FontForge barfs. That in turn limits the size of
32833285 the average class to some maximum, and so limits the number of classes to
32843286 some minimum. Using 200 classes seems to be enough for the current
3285-Jieubsida fonts, which are roughly 13000 glyphs each, and it is reasonable
3287+Mandeubsida fonts, which are roughly 13000 glyphs each, and it is reasonable
32863288 to estimate that none of the fonts created in the planned scope of this
32873289 project will have much more than that many glyphs.
32883290
--- trunk/doc/bkstyle.tex (revision 483)
+++ trunk/doc/bkstyle.tex (revision 484)
@@ -87,9 +87,9 @@
8787 \newfontface\kakudemo[WordSpace={1,0,0},PunctuationSpace=3]{TsukurimashouKaku}
8888 \newfontface\minchodemo[WordSpace={1,0,0},PunctuationSpace=3]{TsukurimashouMincho}
8989 \newfontface\dodumdemo[WordSpace={1,0,0},PunctuationSpace=3,%
90- RawFeature={+liga,+ljmo,+vjmo}]{JieubsidaDodum}
90+ RawFeature={+liga,+ljmo,+vjmo}]{MandeubsidaDodum}
9191 \newfontface\batangdemo[WordSpace={1,0,0},PunctuationSpace=3,%
92- RawFeature={+liga,+ljmo,+vjmo}]{JieubsidaBatang}
92+ RawFeature={+liga,+ljmo,+vjmo}]{MandeubsidaBatang}
9393 \newfontface\atamademo[WordSpace={1,0,0},PunctuationSpace=3]{TsuItaAtama}
9494 \newfontface\sokudemo[WordSpace={1,0,0},PunctuationSpace=3]{TsuItaSoku}
9595 \newfontface\cosettedemo[WordSpace={1,0,0},PunctuationSpace=3]{BlackletterLolitaCosette}
@@ -100,7 +100,7 @@
100100 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
101101
102102 \newcommand{\tsukuDemoFonts}{\let\KDF\kakudemo\let\MDF\minchodemo\relax}
103-\newcommand{\jieubDemoFonts}{\let\KDF\dodumdemo\let\MDF\batangdemo\relax}
103+\newcommand{\mandeDemoFonts}{\let\KDF\dodumdemo\let\MDF\batangdemo\relax}
104104 \newcommand{\tsuitaDemoFonts}{\let\KDF\atamademo\let\MDF\sokudemo\relax}
105105 \newcommand{\bllDemoFonts}{\let\KDF\cosettedemo\let\MDF\cosettedemo\relax}
106106
--- trunk/Makefile.am (revision 483)
+++ trunk/Makefile.am (revision 484)
@@ -219,8 +219,8 @@
219219 $(wildcard $(mvp)/fsc/*.fsc) \
220220 t1asm/README t1asm/t1asm.1 \
221221 $(filter-out \
222- $(wildcard $(mvp)/mp/jieub-a[c-f].mp) \
223- $(wildcard $(mvp)/mp/jieub-[b-d][0-9a-f].mp),\
222+ $(wildcard $(mvp)/mp/mande-a[c-f].mp) \
223+ $(wildcard $(mvp)/mp/mande-[b-d][0-9a-f].mp),\
224224 $(wildcard $(mvp)/mp/*.mp)) \
225225 t1asm/README t1asm/t1asm.1
226226
@@ -265,7 +265,7 @@
265265 doc/pgflibraryshapes.callouts.code.tex \
266266 fea/*.fea \
267267 hamlog/kddata.hl hamlog/jnames.hl \
268- mp/jieub-a[c-f].mp mp/jieub-[b-d][0-9a-f].mp mp/.hglstamp \
268+ mp/mande-a[c-f].mp mp/mande-[b-d][0-9a-f].mp mp/.hglstamp \
269269 pe/assemble-font.pe pe/make-empty.pe pe/*-bearing.pe \
270270 pfb/*.afm pfb/*.pfb \
271271 pfbtmp/*.pfb prf/*.prf sfd/*.sfd sum/*.sum \
@@ -273,7 +273,7 @@
273273 txt/fontlog.txt txt/tsukurimashou.eids
274274
275275 CLEANFILES = \
276- otf/Tsukurimashou*.otf otf/BlackletterLolita*.otf otf/Jieubsida*.otf \
276+ otf/Tsukurimashou*.otf otf/BlackletterLolita*.otf otf/Mandeubsida*.otf \
277277 doc/*.pdf
278278
279279 DISTCLEANFILES = \
@@ -366,7 +366,7 @@
366366 echo 'generic_family($(DEFAULT_TOK)).' >> hamlog/config.hl ; \
367367 ( for a in a b c d; \
368368 do for b in 0 1 2 3 4 5 6 7 8 9 a b c d e f ; do \
369- echo jieub-$$a$$b.mp ; done ; done ; \
369+ echo mande-$$a$$b.mp ; done ; done ; \
370370 ls $(mvp)/mp/ mp/ ) | \
371371 $(PERL) -CSD -n \
372372 -e 'print "page_exists($$1,page$$2).\n"' \
@@ -771,7 +771,7 @@
771771
772772 fea/bll.fea: fsc/tsuku.fsc
773773
774-fea/jieub.fea: fsc/hangul.fsc
774+fea/mande.fea: fsc/hangul.fsc
775775
776776 fea/tsuita.fea: fsc/tsuku.fsc
777777
Show on old repository browser