diff --git a/.gitignore b/.gitignore index 91d196c..1ad92c7 100755 --- a/.gitignore +++ b/.gitignore @@ -42,4 +42,5 @@ dwsync.xml ################### temp newclues-gh-pages +output # manifestos-tmp diff --git a/content/manifestos-img/2014-cybertwee-manifesto.gif b/content/manifestos-img/2014-cybertwee-manifesto.gif deleted file mode 100644 index 40ce4ea..0000000 Binary files a/content/manifestos-img/2014-cybertwee-manifesto.gif and /dev/null differ diff --git a/content/manifestos-img/2014-cybertwee-manifesto.png b/content/manifestos-img/2014-cybertwee-manifesto.png new file mode 100644 index 0000000..1b41290 Binary files /dev/null and b/content/manifestos-img/2014-cybertwee-manifesto.png differ diff --git a/content/manifestos/2014-10-cybertwee.md b/content/manifestos/2014-10-cybertwee.md index 3031a08..5a4adf4 100644 --- a/content/manifestos/2014-10-cybertwee.md +++ b/content/manifestos/2014-10-cybertwee.md @@ -14,10 +14,10 @@ our nectar is not just a lure or a trap for passing flies but a self indulgent intrapersonal biofeedback mechanism spelled in emoji and gentle selfies. -![the cybertwee manifesto](../content/manifestos-img/2014-cybertwee-manifesto.gif) +![the cybertwee manifesto](../content/manifestos-img/2014-cybertwee-manifesto.png) --- source: cybertwee.net / https://youtu.be/xMdiSUIpg50 date: October 2014 -cybertwee is an arts collective co-founded in 2014 by artists gabriella hileman, violet forest, and may waver \ No newline at end of file +cybertwee is an arts collective co-founded in 2014 by artists gabriella hileman, violet forest, and may waver diff --git a/fonts/hk-grotesk/HKGrotesk-Regular.otf b/fonts/HKGrotesk-Regular.otf old mode 100755 new mode 100644 similarity index 100% rename from fonts/hk-grotesk/HKGrotesk-Regular.otf rename to fonts/HKGrotesk-Regular.otf diff --git a/fonts/Linux-Libertine/LinLibertine_RB.otf b/fonts/LinLibertine_RB.otf similarity index 100% rename from fonts/Linux-Libertine/LinLibertine_RB.otf rename to fonts/LinLibertine_RB.otf diff --git a/fonts/Linux-Libertine/LinLibertine_RI.otf b/fonts/LinLibertine_RI.otf similarity index 100% rename from fonts/Linux-Libertine/LinLibertine_RI.otf rename to fonts/LinLibertine_RI.otf diff --git a/fonts/Linux-Libertine/Bugs.txt b/fonts/Linux-Libertine/Bugs.txt deleted file mode 100644 index e18668a..0000000 --- a/fonts/Linux-Libertine/Bugs.txt +++ /dev/null @@ -1,12 +0,0 @@ -linuxlibertine.sf.net -If you want to report bugs please decide if you want to: -- use the bug tracking system on sourceforge (see linuxlibertine.sf.net -> bugtracker) -- send a mail to philthelion (at) sf.net - - --Hinting is still not perfect (you will find hinting faults that deform glyphs in an ugly way but this effetcs just the screen - not printing) -Please note that Hinting isn't always the best way for rendering on screen (especially on Linux-systems). You may want to try the OTF-files instead of TTF to achieve a better displaytion. Please do not forget, that Hinting changes the letterforms to fit the screen pixels. Therefore the letters do look differently on screen! If you want to see how it might look printed, choose at least 600% zoom. - --A few accented charakters or non-latin-charakters are probably not the style native users would prefer (even Unicode-Standards sometimes aren't). Get into contact with me, if you have something to correct. In this way I got, for example, many corrections for the Russion charakters lately, what resulted in an enormous improvement of the cyrillic alphabet in LinuxLibertine (thanks alot for your help, once again!). - --... \ No newline at end of file diff --git a/fonts/Linux-Libertine/ChangeLog.txt b/fonts/Linux-Libertine/ChangeLog.txt deleted file mode 100644 index 1e2c005..0000000 --- a/fonts/Linux-Libertine/ChangeLog.txt +++ /dev/null @@ -1,1997 +0,0 @@ -Libertine Open Fonts Project -- http://www.linuxlibertine.org - -Changes to version 5.2.8 (2012-04-21) -- Libertine Regular: -did ticket 3522377 »Right curly bracket pieces« -- Biolinum Bold: -FIXED 3521717 "NT" combination in Biolinum is too wide open - --Libertine (all styles): -- Kerning is now devided by glyph sets (latin, cyrrilic, greek and small caps). -By this means the list of kernpairs becomes much shorter, thus TTFs tend to load much -faster and a problem with papyrus text editor is being fixed. - -Changes to version 5.2.0 (2011-06-23) - -- Small Caps updated for Libertine Semibold and Semibold italic. For SemiboldItalic: Added small caps to GSUB-Table. -- Libertine Bold: Added real bold minuscles to the cyrrilic pane - -Changes to version 6.x.x (2011-06-13) --Libertine Display: Width of ffi-ligature corrected - - -Changes to version 5.1.3 (2011-06-13) - --Added missing ligatures and/or removed ligature information from the liga-gsub list. - done for Libertine Bold, BoldItalic, Italic --Corrected style information for Libertine and Biolinum styles (bug 3307966). - This bug caused that bold italic was used as italic style on some systems. --Semibold style are now recognized as part of the Libertine or Biolinum Family. --Libertine Bold Italic: - - missing numeral sets (old style) added - - bold small caps added - - bold greek letters added -- Libertine Bold - - bold greek letters added - - improved ligatures - -Changes to version 5.1.0 (2011-05-29) - -- Bug ID: 3310598 corrected (unicode placement of inferior glyphs uni2095-uni209c) -Thanks Kim for the report -- Libertine R: inferior and superiors: n, r, m, t, u, v, w, p, improvements and design adaptation - - -Changes to version 5.0.1 (2011-05-29) -TrueType Package: Corrected missing style information for LinBiolinum_aS.ttf - LinBiolinum_aSI.ttf - This bug caused that these styles could not be installed or used parallely with each other. - - -Changes to version 5.0.0 (2011-05-20) - -Again a lot of improvements, just mentioning the most obvious: - -- Improved Libertine Italic -- New Libertine Bold Italic. Former style => Semibold Italic -- m, n, p, r => improvements in upper left serif. It is now more dynamically moving in the vertical stem. -- New style of the Libertine Regular for high grades (16pt upwards): Libertine Regular Display -- Additional output formats: - - WOFF (Web Open Font Format) => you will always find a recent copy to link with your websites at: - http://linuxlibertine.sourceforge.net/fonts/ - Thanks to Zoltan you may eventually find them on www.google.com/webfonts, too. - - SVG Fonts -- Libertine I and BI: fractions improved -- Additions to the Biolinum Keyboard: Mouse-Symbols (two and three button mice with emphasized one and two finger-click) -- Initials created (Display Glyphs with fine external contour) in range A-Z + some accented glyphs from latin1 encoding - - -Changes to (unpublished) version 4.8.0 (2010-04-30) -201009 complete redesign of Libertine Bold -all common letters are now further embolded. The former Bold style is now -regarded as Semi-Bold. - - -- Libertine Bold -> Libertine Semibold -- new Libertine Bold -- A-Z and accented gylphs -- a-z and accented glyphs -- 0-9 and derivates -Libertine stemwidth put into perspective: Regular (80) - Semibold (110) - Bold -(130) -- public domain and creative commons sign added - - -20100630 Libertine regular: -- k is now wider (as wide as the n) -- s right border increased from 32 -> 40 -- c right border increased from 25 -> 30 -- y left border decreased from 20 -> 16 -- z more organic shape an better grey value -- n,m,h,u 6 EM wider -- Bug #3019031: emacron with wrong accent (mark instead of base) -- Bug #3014435: y.alt adapted to new glyph form and added to opentype -substitution tables "salt" and "alt" -- Hebrew letters improved -- Bug #3004241: opentype substitution -> f.short and dotlessi will now be -substituted by the relating small capital forms -- Bug #3012358: Line spacing problem on windows photoshop. Try: Use -Linespacing-field 0-> 180 (at first only in Libertine Regular for testing) -- T, Z changes to the serifs and more organic shape -- Added A.alt as a test of a more organic A -- improved Hebrew glyphs and mark to base positioning -- numbers scaled up by 5% because many complanied they were to small -- new Indian Rupee symbol uni20A8 -- improvements in the Biolinum bold -- moved styleset 04 > 06 -- new style set 04: versal eszett and small capital eszett is substituted by -double S (SS) resp. double smal caps ss (ss). --q_u.sc Xavier points out, that a small caps qu-ligature is missing. Added to -codepoint uniE094. Added Qu.sc to Libertine Bold --uni2124 etc. for bold, bolditalic... -- Xi was slightly unsymmetric: corrected - - -Changes to version 4.7.0 regular(-) & italic(/) & capitals (C) (20100430) - -- All styles: Reported bugs fixed. - -- Libertine regular: - - added missing anchors for i, idieresis, ccaron, scaron - - added missing characters accent uni0364 and glyph uni1D15 - - completed combining accented chars block 0300-036F - -ij-Ligature more space between the glyphs, dot of j is slightly higher - -i,j,... more distinctive dotaccent and higher position - -r,f,j,y changes in the drop, which became more distinctive - - h slightl wider - - e slightly wider - - moved [a-z].superior from PUA to dedicated Unicode positions - - crossed form of W for new Wikipedia-logo - - new capital Eng - - New extended latin characters - -issue 3025163fixed: placed the anchor now below the g-bowl. Same for q, -p, and j. - -180° degree symmetry for the o and O - - public domain and creative commons sign added - -- Biolinum Bold: numerous improvements in following glyphs: - - a - - i, j, ä, ö, ü... - - w, v - - e - - f, ß - - c - - m, n - - b, d - - s - - kerning faults corrected - - numbers 0 - 9 - - komma , hyphen -, numbersign # - - f - - A-Z slightly thinner verticals - - R, P better bows - - -- added small cyrillic m (uni043C) to Biolinum and some other missing cyrillics -(not yet all done...) -- Inverted Interrobang (uni2E18) added -- Add Substitution/Transposition brackets 2E02-0A -- macroncmb (uni0304) had a wrong positioned mark anchor and was thus flying -much to high -- Problems with Fractions (ID 2665656): without a contextual chaining -substitution fractions like 1/7 or 1/10, that don't have a concrete -Unicode-posistion, were unavailible. Now solved via contextual chaining -substitution. -- bold: ck, ch-ligature's part characters were a bit close. Now some more space -between them -- diacritic U+031A was wrongly placed. Is now being positioned above-right. New -anchor is called top_rechts -- corrected s_t-ligature in biolinum bold -Ingo Preuss points out thatsome glyphs were wrongly named: -- uni0237 is now called dotlessj (instead of uniF6BE, which was wrongly named -this way) -- all references to dotlessj now point to uni0237 - -In the following cases names were corrected, unicode points stayed unchanged -- tcommaaccent (uni0163) is now called tcedilla -- Tcommaaccent (uni0162) is now called Tcedilla -- uni021B is now called tcommaaccent -- uni021A is now called Tcommaaccent -- the locl-OpenType-substitution for Romanian wasn't changed, because it already -worked correctly -- orthogonal is now called uni221F -- sun is now called uni263C -- I had to move that .cap-variants of the accents to the PUA, because they -covered space where Unicode in between defined new characters. So I -systematically moved the .cap-Accents to: - grave.cap uni0358 -> uniE358 - acute.cap uni0359 -> uniE359 - circumflex.cap and so forth - caron.cap - breve.cap - hungarumlaut.cap - space_uni030F.cap - breveinvertedcmb.cap - breve.cyrcap 360 - breve.cyr - dieresis.cap - hookabovecomb.cap - dotaccent.cap -(regular, italic) -- new point accent at uni0358 -- new Mark for uni0358 in many O/o-characters -- improved support for POJ (Taiwan transcription) -- now kerning for kernclasspair p.sc + a.sc -- first use of contextual chaining substitution: - - when a combining accent follows an i, the dotlessi is used to prevent an -accent crash - - when one of the accented or leftwarding glyphs such as (ä, V) follow an f, -a short neck version of f (f.alt) is being used for optical reasons -- Added U+033B COMBINING SQUARE BELOW -- there was the "space" in a left kern class (together with dot, etc.). This -resulted in too few visible room when a "space" should seperate a word from the -now beginning quotation. -Italic: Correction of schwa - - -Changes to version 4.4.1 regular(-) & italic(/) & capitals (C) (20090321) -- First release of Linux Biolinum and its bold variant -- New paragraphs signs (uni00A7 and uni00B6) -- nicer guillemets uni00AB and 00BB as well as the single ones -- improved "copyright"-sign and "registered"-sign -- improved micro-sign -- further improvements in the small capitals set -- superior/inferior h, i, j, n, r has now new serifs, too -- new dotaccent.cap-glyph (slightly bigger than dotaccent) for capital glyphs -- j slightly improved upper serif (now similar to i) -- improvements in row of IPA-signs (recent serifs etc) -- Asterisk has now f-height (a bit lower than before) and lost bearing left and -right -- 0, 2, 3, 4, 5, 6, 7, 8, 9 slight improvements -- tilde, slight improvements -- cedilla improved (now somewhat thicker) -- ae improved -- C, c, e, t new finely bulged runner (or however you might call the thin end of -these letters) -- brought some ligatures up to recent baseglyph form -- florin improved -- dansk ring accent improved -> aring -- comma accent improved, in characters with this accent the latter have now the -same vertical position -- roman numbers improved -- and many smaller things I forgot to note -- as well as hopefully all that I marked as "solved" in the bug tracker -- same height for underbar in unicode positions as well in combined chars with -uni0331 (same with italic) -- frac-table: wrong entry "three fraction eight -> fiveeights" corrected -- Glyph-naming synchronized for -Biolinum Re, Biolinum Bd, -- uni0361 (ligature symbol) and 035C (ligature aubsymbol)added -- uni033B (quadratic subaccent) added -- vertical position of combining-accent-macron and true macron-unicode-glyphs -equalized - - -Changes to version 4.1.8 regular(-) & italic(/) & capitals (C) (20081103) -- finer and more organic serifs for nearly all glyphs -- basic EM-background proportion changed to 726 (above base line) and 472 (below -the baseline) -- Fonts bounds/linespacing in TTF and OTF adjusted -- E, F: a bit thinner now -- A,V,W,v,w design improvements in diagonals -- some small improvements in spacing of small basic latin charakters -- reduced overshoot for wide-round contours -- a, e: small designchange -- m is a little wider now -- basic working EM is now 1000 instead of 2048 -- tz-ligature -- z's diagonal is a bit thicker, the horizontals a bit thinner, now -- new glyphs like curl for bible studies -- shortened few overbounding glyphs -- improvements in polytonic greek -- J, j: change in design of the bow and drop - - - -Changes to version 2.9 (unreleased) regular(-) & italic(/) & capitals (C) -(20080619) -- There was a compiling-problem with the LinLibertine_Re-2.8.14.otf that caused -a unusable GSUB-table. Though outline-information seemed to be unaffected MacOSX -didn’t want to intall it. This version should be without this bug, the reason -for the old bug could not be discovered. -- Change in the OpenType-Substitution table (different order of interpretation: -sups and sinf should be substituted even if oldstyle flag is also set. -/ True Cyrrillic italics for the italic variant -/ new “a” for the italic, also thinner p, n, m and e -/ Some stylistic improvements for italic numbers -/ new @ for the italic -- further kerning -/ improved accented characters in the italic variant -- Q’s tail is now more harmonic and looks as drawn out of the O and not as just -clipped to the bottom -- Qu (Q_u) has been improved and is now standard ligature -- new form for s_t- and c_t-ligature, Thanks to Nathan! -- OpenType-GSUB-table has been improved. New functionality for Romanian and -Moldavian (comma-accent instead of cedilla), for Turky (idotaccent.sc is chosen -when Tyrkish is default language, otherwiese i.sc is the small capital form -used; f_i_()-ligatures are set off in Turkish because it hinders the -differenciation of f-i and f-dotlessi in that language. -/ Italic variant now uses the same perfect OpenType-GSUB as the regular. -/ new a.sc for the italic. Adding missing sc-glyphs, bring others to the latest -design. - - - -Changes to version 2.8.14 regular(|) & italic(/) & capitals (20080619) - -- TTF-Hinting improvements because of better TTF-Instruction of FontForge -- some small kerning improvements -- glyphs U+02BE and U+02BF are no combining charakters > corrected -- kerning problem with 9 in italic corrected -- some small corrections as usual -- slavonic church signs added -- Added cartouches for numbers between 0 and 99 at uniE128 till uniE12A -- Change punctuationspace to width of fullstop (.) It is now 450 of width and -not 350. - - -Changes to version 2.7.9 regular(|) & italic(/) & capitals (20071228) - ->Inconsistent/incorrect glyph names 2.7.9 Private: (?) ->No ->The fonts do not use glyph names consistently. LinLibertineC_Re-2.7.3..ttf ->is currently especially problematic. For example, ->f_i is called uniE0B8 ->f_l uniE0B9 -both chars removed (senseless in a caps-font) - ->Euro.fitted zero.oldstyle ->Yen.fitted one.oldstyle ->perthousandzero five.oldstyle ->zero.oldstyle six.oldstyle ->one.oldstyle seven.oldstyle ->two.oldstyle uniE022 ->three.oldstyle nine.oldstyle ->four.oldstyle uniE024 ->five.oldstyle uniE025 ->six.oldstyle uniE026 ->seven.oldstyle uniE027 ->eight.oldstyle uniE028 ->nine.oldstyle uniE029 -All above corrected - - ->zero.taboldstyle uniE118 ->one.taboldstyle uniE119 ->two.taboldstyle uniE11A ->three.taboldstyle uniE11B ->four.taboldstyle uniE11C ->five.taboldstyle uniE11D ->six.taboldstyle uniE11E ->seven.taboldstyle uniE11F ->eight.taboldstyle uniE120 ->nine.taboldstyle uniE121 -All above corrected - ->In LinLibertineU_Re-2.2.7.ttf, for example, ->f_f is called ff ->f_i fi ->f_l fl ->f_f_i ffi ->f_f_l ffl ->s_t st -All above corrected - - ->In LinLibertine_BI-2.7.2.ttf, for example, ->z.alt is called uniE093 ->J.alt uniE094 ->and the following names refer to blank glyphs: ->f_b ->f_h ->f_j ->f_f_b ->f_f_j ->f_f_k ->f_f_h ->f_f_t -All above corrected - ->The glyph names listed as "correct" above are based on what the majority of ->the fonts in the family use. (E.g. it would actually be easier if the ->ligatures were named ff, fi, fl etc. but since only a few are named in that ->way, I assume f_f, f_i, f_l etc. are the intended names.) -These are actually the names Adobe defined for ligatures in OpenTypes always -a_b_c... - ->The inconsistent naming of glyphs and the use of names for blank glyphs ->make installing for use with pdftex significantly more complex and much ->more frustrating than is necessary. -Yes, this is true. That was of course a bug. - ->I don't know how it affects other uses ->of the fonts, however. -Wrong PS-Names affect just OpenType-capable programs. Normal office use is not -affected. - ->The examples I've given are those which were most ->important to me when preparing metric files and virtual fonts for use with ->pdftex. - - - - - - - - - - -Changes to version 2.7.9 regular(|) & italic(/) & capitals (20071228) -- new Hinting! Now it is possible to use Libertine with Word on Windows -properly. The shape on screen should be clearer now on every system! -- new kern pairs for better typography -- some wrong contour directions corrected -- many small corrections -- OT "fina" has been removed from wordend-sigma -- countless small improvements -- kerning for Caps variant -- the conflict (that came up lately with a library update) between underlined -and regular is diminished - - -Changes to version 2.6.9 regular(|) & italic(/) & capitals (20070423) - -Gernerally: - - Symbols for „page“, „graph“, „picture“ and „table“ added - - Oldstyle numbers (minuscle numbers) were just contained as -proportionals. Somebody wanted them also as table numbers. Ladder became -standard oldstyles now. Some of these glyphs look somewhat thinner to fit them -on the fixed width. - -bold italic variant had a wrong style entry which seemed to confuse -Mac's fonthandling, also other style confusions should be fixed now - -bold italic also had wrong metrics which resulted in a cutoff of glyph -parts and wrong line spacing. - -German interests: - -großes Eszett hinzugefügt (uni1E9E) entsprechend Kapitälchen-Eszett - -kleines Eszett so verändert, dass es zum großen passt (ſz statt ſs), -das vorige Eszett ist als germandbls.alt weiterenthalten - -Im Stilsatz ss03 kann für Schweizer nun automatisch von Eszetts auf ss -umgestellt werden. - -die dt. ÄÖÜ sind nun von der Alternativposition an die rechte Stelle -gerückt. Für die nichtdeutschsprachige Nutzung empfehlen sich jetzt die (vormals -standart, jetzt aber auf die Alternativposition gewechselten Akzentuierten) - -Cyrillic: - Due to A. Panovs help hopefully a lot of design impriovements for the -cyrrilic alphabet. - Mainly: Є Љ Њ Б З Ф Ш Щ Ъ Ы Ь Э Ю Ө (and its small letter derivates) For -details: - ("Ь" in regular typeface has extra contour at left bottom.) - --corrected-- - - Lower part of "Ь" and "Ъ" (and for lowercase letters "ь", "ы", -"ъ", - "ѣ") differ. I think the letter "Ь" (or "ь" for lowercase) -should be - used as base for others. - - ("Ф" is still slightly asymmetric with respect to vertical axis. -It may produce artefacts with rendering.) - --corrected-- - - (Middle vertical stems in "Ш", "Щ" have not rounded lower -edges.) - --corrected-- - - ("Ш", "ш" are not quite symmetric agains middle vertical axis -(all - typefaces). "Щ", "щ" must be updated accordingly.) - --corrected-- - - (The tongue in "Э" can have two stylistic variants: straight and - tilde-like. ) - OK, then tilde-like. - - (The designer decides which version should be selected. Some -other letters should follow this decision: U+0472, U+04E8, U+0404, etc.) - --corrected-- - - (The capital letters U+0472 and U+04E8 usually are identical, -excepting the case of archaic (before ca. XVIII century) form of U+0472.) - --corrected-- - - (The U+0473 frequently is narrower than "o" and U+04E9. In case -of a tilde-tongue in "Э" a tongue in U+0404 is not flipped, i.e. it has the same -diriction as in "Э".) - --corrected-- - -Small Caps: - - Some changes here for better spacing. - - FO-overlap (due to wrong kerning entry) removed - -Bolded: - - Complete revision of the bold version. Should result in a clearer -shape and better thin-width-contrast - -OpenType: - - Due to better support in the FontForge editor the OpenType-tables have -been completely redefined. - - - -Changes to version 2.5.9 regular(|) & italic(/) & capitals (20070423) -- countless improvements as usual -- some unicode standard optimizations (NUL-glyph, .notdef, ...) -- U+0180 group of charakters were sometimes not the way the latest unicode wants -them so we changed them. This refers mainly to the differentiation of capital -and small letters -- Vietnamese horned vokals have been changed the way, that the horn is now -always at the same hight. All accented vietnamese glyphs were revised -- some optic improvements in placement of accents -- added a capital variant of hookabove and changed all the capital letters to -this new hookabove form. It is wider and lower for better line-holding -- kerning was greatly improved, i.e.: Kombinations like "f)", "f?", "(j"... -shouldn't overlap anymore. Capital letter words should now be better spaced. -- There was one wrong cyrrilic letter Lje (U+0409). -And there were some correct objections to the handling of the downgoing serif in -Dzhe/dzhe, De/de, Tse/tse, Shcha/shcha. These now have the same depth and -similar form -- Some small changes in cyrrilics most complex letter Zhe -but also in Ef -in the hardening and softening signs (should not look like a reversed P but like -the bud of the B), -Ya shouldn't look like a flipped R, -be had a too right tail, -breve.cyr didn't look cyrrillic enough, -ef shouldn't be too calligraphic, -dje/she have now x-hight-bars -- due to a bug U+1fc7 (an accented eta) was missing -- some eagled-eyed person had seen that the U+721 was not at its place -- perthousandzero added at U+E00E for full LaTex-support -- some accented smallcaps added to basic font table for LaTex-support (This -doesn't affect the Caps-version of Libertine, which already had all these -glyphs) -- removed a cyrrilic opentype entry that substituted N-o with the numberligature -because a stupid GNOME environment read out this table entry on a Spanish system -and messed up typography... - - -Changes to version 2.4.9 regular(|) & italic(/) & capitals (20070309) -- many countless improvements -- some letters are slimer now: a, k, c, r -this is especially useful for languages with longs words. German in the first -place... -- on screen letters with round parts should now look more equal on screen --C, D, G, S have now better (shorter) serifs which are more useful for the -standart printing size of 12-10pt -- the thinnest line should now have a width of at least 50 (improvements for -12-10pt printing) -- the whole range from U+180 -> U+01BF has been reworked --small improvements in the IPA-Extensions --for better acception of the old greek we changed the inverted breve to a tilde -which is more widely used..., accents also have received some improvements --The cyrillic alphabeth has had again great changes due to unsatisfied users. We -now have more equal cyrillic serifs, some letters are thinner some wider, -spacing has been renewed --p,i have now horizontal serifs in the cyrillic --the bold regular is greatly improved. It's now fatter, looks more elegant -- the curive has also improvements: - J is now better - many things are corresponding to the improvements in the regular --improvements in the capital variant - -Changes to version 2.3.2regular(|) & italic(/) & capitals (20060920) -Countless improvements... --especially for the italic, the kyrillic --polish accents ogonki are now what they should be --new: hebrew alphabeth --numbers --accents brought to one hight (some dotted chars weren't) --Same hight for capitals (already one point difference can the letter look -higher on screen. For print this doesn't play any role... --superior/inferior numbers improved --ae looks now different: mor organic. If you don't like this. Theres also an old -variant at the end of the font --ij ligature isn't connected anymore --greek accented chars improved (accents should now be optically at the same -position), kappa improved --planet signs added --Sternkreiszeichen hinzugefügt --male, female,... improved -. -. -. - - - -Changes to version 2.2.0regular(|) & italic(/) & capitals (20060920) -- Viele, viele Änderungen! -- Volle Unterstützung von OpenType: - Ligaturen - Kapitälchen (Small capitals) - Ziffern -> Tabulare, Proportionale, Mediävale - Gestrichene Null (slashed Zero) - -- Kapitälchen komplett neu entworfen -- Kerning vollständig neu entworfen (nach Klassen) -- neue Ligaturen entworfen: ck, ch, ffb, ffk, fk, fb, fh, ffh, -- Ampersand überarbeitet, -- Alternatives Ampersand für Kapitälchen -- E und F überarbeitet -- W und V " -- M und N (letzteres mit verlängerter Diagonale) -- viele Buchstaben für Type1-Verwendung bereiningt! -- Nummern in Kreisen - - -Changes to version 2.1.8regular(|) & italic(/) & capitals (20060901) -Viele Überarbeitungen: -- Kyrillisches Alphabet weiter verbessert -- E, F, L, T, M, B, D, A, C, Z, P, R Serifen verbessert -- b -- f Bogen etwas länger und flacher -- h verändert -- uni03d0 und theta1 kleiner gemacht -- Dje verändert (nun nativer) -- Macron von 80 auf 90 verdickt -- kleine römische Ziffern verändert -- ij ist nun eine verbundene Ligatur -- viele, viele kleine Bereinigungen - - -Changes to version 2.1.6 regular(|) & italic(/) & capitals (200608024) -- Zeilenabstände und Font-Metrik verbessert, Durchschuss nun geringer. -- becyrillic hat nun angemessene Abstände -- Untere Serifen sind nun 55 dick und breiter -> Gemeine: 436; Versalien: 526 -/ Kursive komplett überarbeitet und auf aktuellen Stand gebracht. -und vieles Kleines mehr... - - -Changes to version 2.1.5 regular(|) & italic(/) & capitals (200608024) -- Tex-Namen für alle Glyphen -- i-Punkt und . dicker -- Sämtliche Akzente überarbeitet -- Neue, flachere Akzente für Großbuchstaben -- viele Griechische Buchstaben überarbeitet -> dynamischer -- Serifen großteils überarbeitet -- Russischer Akzent jetzt im russischen Stil -- uni041A jetzt wie uni416 -- Männlich / Weiblich-Zeichen ist jetzt besser an die Grenzen des Fonts -angepasst -- viele weitere Änderungen -- Fette Variante heißt jetzt auch wieder Fett -> Problem bei manchen -Betriebsystemen behoben -- Leerzeichen ist nun 512 EM breit, so wie's praktisch Standart ist -!!- Namensproblem bei der Fetten behoben - -Changes to version 2.1.3 regular(|) & italic(/) & capitals (20060806) -- 6-Problem gelöst -- Phi-Problem gelöst -- Lowcomma neu -> Pinselstil -- epsilon -- und vieles mehr... -- <> kleinergleich, größergleich, und Verwandte auf gleiche Größe -- +, -, = überarbeitet -- Unendlichzeichen -- h und n verbessert (Bogen) -- Serifen der Gemeinen und der Großbuchstaben verbessert - - -Changes to version 2.1.2 regular(|) & italic(/) & capitals (20060806) -- Rückführung der griechischen Akzente auf U+002... -- Macron verbessert, U+02C9 nun positiv -- Abstände der griechischen Buchstaben verbessert u.a.: iota LBearing +40 -- eta, sigma, rho, tau, psi und weitere griechische Gemeine verbessert -> -Pinselstilhaftigkeit erhöht - ------------Fertig-nach Tobias Vorschlägen---------------------------- -02C4 (MODIFIER LETTER UP ARRORHEAD), * raised articulation (-> 005E ^ -circumflex accent, 2303 ^ up arrowhead). Siehe -http://www.unicode.org/charts/PDF/U02B0.pdf -Wenn ich in die PDF-Datei schaue, sehen 02C2 (<), 02C3 (>), 02C4 (^) und -02C4 (v) größer aus als 02C4 (^) und 02C5 (v). Vielleicht sollte man für -02C2 bis 02C3 einfach ein gedrehtes '<' benutzen? -- Zeichenbreite im Block "SPACE MODIFIER LETTERS (02B0–02FF)" -(http://www.unicode.org/charts/PDF/U02B0.pdf) ist zum Teil verkehrt. -Diese Zeichen sollen alle eine endliche Breite haben (im Gegensatz zu -den COMBINING DIACRITICAL MARKS (0300-036F), die auf/unter einem Zeichen -sitzen sollen). Insbesondere: -- zu Breit: hochgestellte h, w und y -- viel zu schmall: T, _|_ und + (etc.) -- Zeichenbreite/Position im Block "COMBINING DIACRITICAL MARKS (0300-036F) -http://www.unicode.org/charts/PDF/U0300.pdf -Bei den meisten Zeichen stimmt die Breite/Position, bis auf: -- 0306 COMBINING BREVE -> zu weit rechts -- 030B COMBING DOUBLE ACUTE ACCENT -> zu weit rechts. -- 0327 COMBINING CEDILLA -> viel, viel zu weit rechts! -- 0338 COMBINING LONG SOLIDUS OVERLY --> Ich würde den Strich entweder etwas nach unten verlängern oder nach -etwas nach unten schieben; oder etwas nach links schieben? Jedenfalls -sieht "o" + U0338 (= ca. ø) komisch aus. -- Vielleicht ein klein bißchen zu weit rechts: 0323, 0330, 0331, 0342, -- 0384 GREEK TONOS -> Das Zeichen sollte normal breit sein und kein -"combining" Akzent. -- 03F1 GREEK LUNATE SIGMA SYMBOL = GREEK SMALL LETTER LUNATE SIGMA -> -Das Zeichen sollte anders als Sigma aussehen und zwar ohne den Bogen -unten (ca, wie "c", oft spitz zulaufend). -- 03F4 GREEK CAPITAL THETA SYMBOL -> anders als Theta, durchgehender -Strich in der Mitte -- 03F5 GREEK LUNATE EPSILON SYMBOL = straight epsilon -> Wie der Name -schon sagt ein nicht geschwungenes Epsilon. In der Physik benutzt man -oftmals beide Epsilons das gerade und das geschwungene. -(03F6 GREEK REVERSED LUNATE EPSILON = reversed straight epsilon -> bitte -das gedrehte 03F5 hinzufügen) -- 03F9 GREEK CAPITAL LUNATE SIGMA SYMBOL -> sollte anders als Sigma -aussehen, klassischerweise wie "C" (oft ohne Serifen und spitz zulaufend) - -NUMBER FORMS -- 215F "1/ " -> Man sollte wohl die Breite so ändern, daß "1/" + -tiefgestellte Zahl (2080 bis 2089) gut aussehen. -> Durch Kerning gelöst - -Fehlten: -- Griechisch-Block: 03DA-03E1 fehlen (Archaische Buchstaben) -http://www.unicode.org/charts/PDF/U0370.pdf -(Wieso die in MES-2 sind, weiß ich allerdings nicht) -* 03DA GREEK LETTER STIGMA -* 03DB GREEK SMALL LETTER STIGMA -* 03DC GREEK LETTER DIGAMMA -* 03DD GREEK SMALL LETTER DIGAMMA -* 03DE GREEK LETTER KOPPA -* 03DF GREEK SMALL LETTER KOPPA -* 03E0 GREEK LETTER SAMPI -* 03E1 GREEK SMALL LETTER SAMPI -MATHEMATICAL OPERATORS, http://www.unicode.org/charts/PDF/U2200.pdf -- 2208 ELEMENT OF, 2209 NOT AN ELEMENT OF und 220A SMALL ELEMENT OF --> das (Nicht-)Element-von-Symbol finde ich zu groß, es sollte nicht so -groß wie Versalien/Großbuchstaben sein, sondern so groß oder etwas -kleiner als Gemeine/Kleinbuchstaben. Das kleine Element-von-Symbol finde -ich zu klein. - -Changes to version 2.1.1 regular(|) & italic(/) & capitals (20060729) -- IPA 02D0 Richtung korrigiert - 0258 '' '' -- Diacritische Zeichen überarbeitet -- i/j ist nun dotlessi/j + dotaccent -- Tux is again @ uniE00E -- MathSymb 2214 corrected wrong contour -- d', l', t' -- OE neu -- iota überarbeitet -- idieresis, edieresis vom Kyrillischen sind nun Verknpf. vom Latein - -Changes to version 2.1.0rc regular(|) & italic(/) & capitals (20060729) -- many small unnamed improvements -- implemented the IPA-extensions -- Small numbers -> superiors and inferiors are now bolder -- fractures are greatly improved and some new are added -- We now have proportional numbers and mediävale as some people asked for them -- Kerning for roman Numbers -- Ligatures should now be seen as a combination of different letters in -OpenType-Compliant programs (unfortunately aren't there any compliant programs, -or are there?) -- added lots of greek special charakters -- korrected lots of greek special charakters -- some small extensions in mathematical symbols -- eth, Thorn and thorn were completely renewed -- bearing of o,d,eth,p better -- some smaller things -- geometric forms are now better adapted to the charakter sizes -- added alternative variants for German Umlauts -- Tilde improved -- removed dublicate glyphs uniE001-004 -/ f, g, h and u are improved -U now also a bold variant of the underlined -* bolded versions for all updated - -Changes to version 2.0.9 regular(|) & italic(/) & capitals (20060401) -- small changes, used new converter (fontforge-20060408) -> may result in -slightly better contours (who knows...) -- first underlined variant -- Bold variant has now better bearings (were to small) now it is what we want! - -Changes to version 2.0.8 regular(|) & italic(/) & capitals (20060401) -- completely new bold version! -- first bold-italic variant! -=> the family has therefore now finally all faces it classically needs, juhu! -;-) --further small corrections in all faces -- I created TrueTypeInstructed variants of LinuxLibertine named "LinuxLibertine -T" they can be therefore installed paralelly to the unhinted variants. -Note 1: I recommend all users of OpenOffice 2.0.x on Linux to use the unhinted -variants. On my linux-systems the unhinted variant is automaticly hinted and -better looking than the hinted! On Windows-Systems -- nevertheless -- the -unhinted variant is ugly on screen. Here you should take the instructed/hinted -variant. -Note 2: Hints (in the meaning of TrueTypeInstructions) do not have any effect on -printing. - -Changes to version 2.0.7 regular(|) & italic(/) & capitals (20060227) -Line spacing was again greately improved (I hope) -| many changes -| in cyrillic -| Accented chars optimized (same height for all accents!) -| new accents -| new special characters -| some existing special chars were improved -/ r is now without serif -/ many small changes -and most of it I just forgot - -Changes to version 2.0.4 regular(|) & italic(/) & capitals (20060202) -| many changes -| in cyrillic -| polish -| additions to arabic diacritics -| small corrections in overlapping paths and wrong contour directions -| all corrections should be suitable for the other variants as well - -Changes to version 2.0.3 regular(|) & italic(/) & capitals (20060120) -| many small changes -| corrections for Cyrillic glyphs - Mac-Variant for all fonttypes -/ corrections for Cyrillic glyphs -b corrections for Cyrillic glyphs - -Changes to version 2.0.0 regular(|) & italic(/) & capitals (20060120) -/ many many great changes in the italic! -| some new symbols and ornaments -| ligatures optimized -| lots of stuff I forgot to write down... -| Oh, yes, the problem with in stalling all variants paralelly on windows is -fixed - -Changes to version 1.1.9 regular(|) & italic(/) & capitals (20060120) -| numerous changes! -| e.g. LineGap is smaler now -> similar to Times -| some nice decoratives added (oriental leaf, left and right; fleuron, art deco -paragraph end symbol, Tux penguin) -| many new characters for special languages -/ italic updated as well -| bold variant also updated -| many, many other useful additions and bugfixes - -Changes to version 1.1.1 regular(|) & italic(/) & capitals (20050908) -| many changes, mamy small changes -| Zahlen /numbers sind jetzt fertig -| Korrekturen an Abständen -| Schmälerung des Leerzeichens -| t + f haben jetzt schmalere Querstriche -| r fetter und rechts weniger Abstand -| y neu und besser -| () Klammern überarbeitet, waren zu hoch -| []{} siehe oben -| µ ist ganz neu -| € auf Zahlenhöhe -| t verändert -| M nach unten noch breiter werdend -| ø und großes O/ pberarbeitet -| Hoch- und Tiefzahlen /Subscripts -| Brüche neu -| Römische Zahlen auf Zahlenhöhe und ganz neu -| und noch viel viel mehr! - -Changes to version 1.0.4-10pt regular(|) & italic(/) & capitals (20050908) -| weitere Arbeiten an den Zahlen besonders 2,3,5,6,0 -| Korrekturen an Abständen von K, A, N, V, W, v, w, a, -| W und X waren nicht so hoch wie andere Versalien -| Verschmälerung des Leerzeichens von 690 auf 600pt -| Gesäuberte Buchstaben: i, a, l, longs, ß, r, f, - -Changes to version 1.0.3-10pt regular(|) & italic(/) & capitals (20050908) -| Tabellarische Zahlen fast fertig -| Kern-Paare teils korrigiert - -Changes to version 1.0.2-10pt regular(|) & italic(/) & capitals (20050412) -| Tabellarische Zahlen (noch in Arbeit) - -Changes to version 1.0.1-10pt regular(|) & italic(/) & capitals (20050323) -| all Capitals are 60pt less high -| ? question mark is slightly thinner and less high now -| uni022C (O mit tilde und Macron): Das Macron (¯) ist etwas zu weit rechts -| uni022D (o mit Tilde und Macron): dito -| uni0210 (R mit ") die " sind zuweit links - (beim r und u mit " könnten sie noch ein Tick weiter rechts sein) -| uni0307 (dotaccent) der Punkt könnte etwas höher sein -| uni0308 (dieresis) hat positive Breite -| 0309 (combininghook) ggf. zu hoch, Breite nicht null -| 030C (umgedrehtes ^): positive Breite -| 0327 (cedille): positive Breite -| 0323 combining dot below: vielleicht noch ein bißchen nach links? -Anmerkung: Wenn man jetzt noch die Diacritical Marks verschiebt, dann verändern -sie sich in allen anderen Akzentuierten Zeichen mit, wo sie durch Referenzen -eingebunden sind. Daher habe ich die Verschiebungen ersteinmal nicht -vorgenommen. -|Beim kleinen psi [03C8] kann ich mich nicht recht an den schrägen Mittelstrich - - gewöhnen.) -| 1E48: Das _ beim N sollte wohl etwas länger sein oder etwas nach links - verschoben werden -| Bei Greek Extended (1F00 bis 1FFF) ist bei 'E und 'H (allein und mit - verschiedenen weiteren Akzenten) das ' vor der position 0, und - überschreibt somit das vorherige Zeichen. Das ist wohl nicht Absicht, - oder? Analog bei `I (1FDA). -| uni2102: Das C (für die Menge komplexe Zahlen) sollte einen - Doppelstrich haben, wie deine H,Q,Z,R -| 213D bis 2149: das gilt auch für die Zeichen hier (gamma, Gamma, Pi, - Sigma, D, d, e und j) -| 2153 bis 215A: Die Brüche 1/3, 2/3, 1/5, 2/5, 3/5, 4/5, 1/6, 5/6 - fehlen; besonders 1/3 und 2/3 wären schön -| 2217 und 2218 sollten witer unten stehen (genaus so hoch wie das Minus - und der Punkt 2219) da das Multiplikationsoperatoren sind. -| 226A und 226B: Das sind vielgrößer/vielkleiner Zeichen. Ich hätte sie - aber so nicht erkannt. Nimm einfach << und >> und schiebe sie ein wenig - ineinander. - -Changes to version 1.0.0-10pt regular(|) & italic(/) & capitals (20050323) -| accented chars corrected -| quotes (simple and doubles) are moved down slightly - -Changes to version 0.9.8-10pt regular(|) & italic(/) & capitals (20041208) -| all normal latin chars are now some points wider (we want to have a 10pt font! -:->) -| some special chars bolded as well about stroke 10 -| all greek letters and special chars in between are also expanded -| cyrilliy A has now a more popular form -| some other small changes - -Changes to version 0.9.6-10ptL regular(|) & italic(/) & capitals(20041201) -- bigger serifs for l,i,j,f,a,b,c,d,e,m,n,p,r,h,k,q,s,u,v,w,x,y,z,ß and many -more - -Changes to version 0.9.5 regular(|) & italic(/) & capitals (#)(20041008) --r rBearing 49 => 55 --s lBearing 117 => 100 - rBearing 90 => 75 --i lBearing 70 => 80 - rBearing 53 => 65 --t rBearing --g ear is now more dominant - - -Changes to version 0.9.4 regular(|) & italic(/) & capitals (#)(20040802) -- P rBearing -17 => 10 -- Px kern pairs redone (to bigger distance) -- w/v-x kern pairs -- many small changes -b] bold typeface iniciated - -Changes to version 0.9.3 regular(|) & italic(/) & capitals (#)(20040802) -| z is lighter now -| Eurosign is smarter -| numbers and Bearings edited -| v,w,x,y rBearing 12|22 => 24 -| i lBearing 64 => 70 -| double-quoteds increased distance about 15pt -| O is lighter -| '`changed accents -| * is now typagraphic (I'm really proud of that one!) -| ? small changes -| fi, ff, ffl, ffi redid ligatures -| changes in accented charackters -| ae changed -| Paragraph sign -| hinting -| þ -| M rBearing 60 => 65 -# c -many other small changes - - -Changes to version 0.9.2 regular(|) & italic(/) & capitals (#)(20040802) -| success in line gap setting: -winAscent=1900 -winDescent=500 -linegap=0 -these are quite useful values. We'll see whether it may be better to reduce -winAscent. - -Changes to version 0.9.0 regular(|) & italic(/) & capitals (#)(20040727) -| another try in line gap setting - -Changes to version 0.8.8 regular(|) & italic(/) & capitals (#)(20040723) -| improvements and great changes in all numbers -| 1 changed from roman to actual latin -| , (komma) improved slightly -| ) rBearing + -| ? improved slightly -| @ greately improved -| [] bracket improved -| + - at one hight -| ~ improved -| § improved -| breve improved -| c/o and other small things -# Capitals initiated - -Changes to version 0.8.7 regular(|) & italic(/) (20040715) -| added uni28F -| did some mathematical symbols -| some other small things - - -Changes to version 0.8.6 regular(|) & italic(/) (20040715) -LineSpacing is great in other programs than OpenOffice -| t improved slightly -| O improved -| u improved -| 0 improved -| and other small things - -Changes to version 0.8.5 regular(|) & italic(/) (20040715) -| another try in correct line-spacing -| m corrected - -Changes to version 0.8.4 regular(|) & italic(/) (20040630) -| longs improved -| b improved slightly -| c improved -| O further work -| a greatly improved -| 0 another try - - -Changes to version 0.8.3 regular(|) & italic(/) (20040630) -| y lBearing -31 => 0 -| s again changes -| line gap was still too big -| L rBearing 40 => 60 -| u changes in the bow -| 0 is now rounder -| f edited -| g ear and lower bow corrected -| O changes again - -Changes to version 0.8.2 regular(|) & italic(/) (20040630) -| line gap was to huge -| s so new slightly to dark - worked over -| t worked over -| G edited -| r edited, was to dark -| N rBearing 65 => 70 -| O yet another trial - - -Changes to version 0.8.1 regular(|) & italic(/) (20040630) -| D rBearing 110 => 120 -| t rBearing 45 => 60 -| H rBearing 55 => 70 -| M rBearing 53 => 60 -| N rBearing 56 => 65 - diagonal was much to fat, now thinner -| S rBearing 90 => 100 -| Z rBearing 35 => 60 -| l rBearing 60 => 65 - lBearing 66 => 70 -| T some changes (higher top) -| t changes in the bow -| & (ampersand) had great changes -| s great changes, serifs were too complex -| j lBearing -50 => -58 -| ! (exclamation mark) shrinked to 99% -| a,e upper bow higher -| a bow -| u upper serifs higher -| O still in work - -Changes to version 0.8.0 regular(|) & italic(/) (20040627) -| Set WinAsc/Desc to correct wrong line-spacing in most Applications -| ? (Question Mark) was too big -| e edited -| O edited but I'm not confident yet -| J lBearing -157 => -140 - -Changes to version 0.7.9 regular(|) & italic(/) (20040604) -| B rBearing 80 => 90 -| I rBearing 65 => 72 - lBearing 48 => 60 -| t rBearing 32 => 45 -| s rBearing 105 => 75 -| e lBearing 183 => 88 -| b rBearing 85 => 90 -| j lBearing -72 => -50 - rBearing 153 => 160 -| 0 Bearings -| l rBearing 50 => 60 -| p rBearing 75 => 80 - bow overworked -| AE overworked -| þ overworked -| o overworked -| oe overworked -| uni434 overworked -| uni310e & f made kursive -| uni2070-209F created -| O edited -| S edited -| t edited - - -Changes to version 0.7.8 regular(|) & italic(/) (20040604) -| b cleaned -| c cleaned -| d cleaned -| f cleaned -| g cleaned -| j cleaned -| k cleaned and combined -| m cleaned -| n cleaned -| o cleaned -| p cleaned -| q cleaned -| r cleaned -| u cleaned -| w cleaned and combined -| y cleaned and combined -| O, P, Q, R overworked -| W combined -| Y wider -| ß overworked - - -Changes to version 0.7.7 regular(|) & italic(/) (20040604) -| nothing that I can remember - -Changes to version 0.7.5 regular(|) & italic(/) (20040604) -| S rBearing corrected (was double size) -| All capital letters shrinked to 97% -| D overworked -| J -| T's cap is 20pts wider -| U bow changed -| X -| a is now lsightly smaller - - -Changes to version 0.7.4 regular(|) & italic(/) (20040531) -| small changes in diacritical marks -| s overworked -| E,F VStem is now 10 pt wider and therefore as other capitals -| did a new hinting on all basic letters - -Changes to version 0.7.3 regular(|) & italic(/) (20040531) -| removed some overlappings in e.g. A, K. W a.s.f -| uni431 overworked -| uni 432 overworked -| overworked cyrillic -| added some strange chars uni1E0... - -Changes to version 0.7.1 regular(|) & italic(/) (20040525) -| copied some greek letters from RC van Dalen' Garogier -| t overworked, wider -| J overworked -| overworked omega -| overworked phi -| overworked eta -| overworked numbers -| k small corrections -| worked over accented charakters -| many accented chars and special chars added -| Cyrillic charakters added (that was quite a horror of work and it's not -yet finished... spacing leaves to be done -| B overworked -| C overworked -| G overworked -| O overworked -| U Overworked -| S Overworked - -Changes to version 0.7.0 regular(|) & italic(/) (20040522) -| Omicron ist now reference to O -| uni25cb overworked is now reference to Rcircle and others -| Xi overworked -| chi overworked -| gcedilla changed -| k,n,rcedillas changed -| corrected uni21A -and other fixes - -Changes to version 0.6.9 regular(|) & italic(/) (20040519) -| overworked µ -| added 018E -| added 01B6 - 01B9 -| added 0283 -| overworked 0292 -| i,j dot is now better positioned -| created dotlessj -| overworked all accented charakters -| added Tobias' changes, namely: - Latin Extended-B - - Added 022E - - Added 022F - - Added 01c0 - - Added 01c1 - - Added 01c2 - - Added 0218 - - Added 0219 - - Added 021A - - Added 021B - - Added 021E - - Added 021F - - IPA Symbols: - - Flipped 025C (reverted epsilon) vertically - - Added 0287 - - Added 0292 - - Combining diacritical marks - - Added 0307 - - Added 0326 - - -Changes to version 0.6.8 regular(|) & italic(/) (20040517) -| added Tobias' changes - -Changes to version 0.6.7 regular(|) & italic(/) (20040513) -| added Tobias' implementations and further ipa-extensions (8 chars) -| added Vienamese special charakters - -Changes to version 0.6.6 regular(|) & italic(/) (20040510) -/ updated to recent development stage -many other small things - -Changes to version 0.6.5 regular(|) & italic(/) (20040510) -| "" (quoteds) increased the distance between bow commas -| " (quoteds) and kerning -| singlequotes added -| added some mathemagical symbols -| ~n width corrected -| corrections in special characters -| added roman numbers -| all latin standart charakter-lines are now right turning and therefore should - most Xor-Errors in special chars due to references be corrected now -| updated tobias' corrections - - - - -Changes to version 0.6.4 regular(|) & italic(/) (20040508) -| added Tobias' box and arrow symbols -| added a German quoted at uni201F -| U is now 80pt wider and hopefully wide enough now -| kernpair nt, mt 0 => -30 -| A serifs shorter - -Changes to version 0.6.3 regular(|) & italic(/) (20040415) -| AE corrected -| k rBearing 0 => 25 -| t Bearings -| z rBearing 85 => 72 -| b bow -| d rBearing 68 => 62 -| h lBearing 64 => 58 -| m 16pt wider -| x, Bearings 12 => 22 -| v,w Bearings 0 => 12 -| o smaller -| ,. bigger 103% -| did uni25cf - -Changes to version 0.6.2 regular(|) & italic(/) (20040315) -| d has now a new serif -| t changes -| S rBearing 90 => 95 -| E rBearing 90 => 100 -| z lBearing 95 => 85 -| ä,ö,ü a.s.f have bigger dieresis (points) -| k smal changes in the arm -| x l/rBearing 7=> 12 -| T kern pairs -| �overworked -| ff overworked -| fi overworked -| dotlessi overworked -| added U+00A0 nonbraking space - U+014A & B (eng) - and further uni-charcters to comply MSE-1 - (European languages standart) - florin - -Changes to version 0.6.1 regular(|) & italic(/) (20040315) -| ligatures overworked -| k left bearing changed: 70 => 58 - right bearing changed: -20 => 0 -| x left bearing changed: 8 => 6 - right bearing changed: -20 => 6 -| - (hyphen) is now thinner -| :; are now bigger -| overworked -| J rBearing increased -| d lBearing -5pt -| B rBearing 90 => 80 -| l lBearing 74 => 66 - rBearing 57 => 50 -| v,w,y lBearing -14 => 0 - rBearing -14 => 0 -| Z stronger Serifs -| t new bow -| u thicker bow - changes in all serifs -| r's bow is more contrastive -| V,W,Y kernpairs overworked -| new anstrich for: b,d,h,i,j,k,l,m,n,p,r -| t lBearing 73 => 60 - - -Changes to version 0.6.0 regular(|) & italic(/) (20040315) -| b has now a foot -| new serifs for H,W,V,T,I,J,K,L,E,F,M,N,P,R,U,X,A,B,D,G,Y -| new serifs for f,h,i,k,l,m,n,p,q,r,v.w.x.y -| Xe kernpair -20 => -40 -| B is a bit (27pt) wider -| G had some changes -| some more little changes - -Changes to version 0.5.9 regular(|) & italic(/) (20040315) -| did the common latin legatures -| �still working on the bows -| e is a now 2% less wide as before - had some changes -| dashes overworked - -Changes to version 0.5.8 regular(|) & italic(/) (20040315) -/ b, �changes -/ f overwork in the bow -- some other changes - - -Changes to version 0.5.7 regular(|) & italic(/) (20040315) --N is now 66pt wider --^ {Ascicircum} is now better -- {exclamdown} is now availible -- {currency} has been added -| "-" hyphen is the same as softhyphen. length is now 510pt --bars have been made --many, many unlisted changes in so called "special" chars -| a,b,c,d,e,f had small overwork -| g's ear still had another overwork. Whether this will be better - we'll see... -| �is now wider -| ... {Ellipsis} had an overwork -| j Beraings + 10/15pt - -Changes to version 0.5.6 regular(|) & italic(/) (20040303) -- t's bow is now stronger -| l has moved 5pt to the right -- L rBearing 29 => 40 -| kern pair {space}T -75 => -100 -- is now up to date -| r has a finer drop -- Y has been combined -- M rBearing 68 => 75 - lBearing 78 => 75 -- H rBearing 80 => 75 - lBearing => 75 -- s rBearing 115 => 105 -- V is now 30pt wider -- E,F combined -| C edded Extrema -| points are now centered -| e added extrema -- K is now ca 50pt wider -| a,c,f added extrema -- S thicker serifs -- �has gained a lot, though - in italic the subpart is still missing -| # is corrected -/ & corrected -/ v,w a bit more slanted - -Changes to version 0.5.5 and 0.5.5i (20040303) -- did a "correct direction" on all chars -- did a autoinstr on all chars -/ Quotesingle korrigiert -/ hopefully all chars slanted now -- ascicircum scaled to 75% - -Changes to version 0.5.4 (20040303) -- n,m rBearing had to be reset to 60 -- ~ (tilde) is now better -- ff is much better now -- fi as well -- � � , � � �better now -- change to v, w - -Changes to version -italic-0.5.4 (20040303) -- do nearly all characters as they have to be - in an italic -- v in style of Janson italic - -Changes to version 0.5.3 (20040228) -- b. kern-pair -10 => -50 -- @ got better -- n,m became 28pt wider -- W thin stems became thinner (ca. 4pt) -- u change in the bow -- �corrected -- D became wider -- 1,2,3,4,5,6,7 had a major overwork -- C,G wider bows - - -Changes to version 0.5.2 (20040222) -- b rBearing 90 => 80 -- r rBearing 66 => 55 -- c,d,e,q have now more similar bows -- p has now a better bow -- a has slight changes -- o has now a thinner band, less dominant -- s had some changes in the curves -- f changes in the bow -- h slight changes -- y is hopefully now what I want it to be -- @ has changed in a good way but the design cannot be - finished yet -- Tried an italic version - -Changes to version 0.5.1 (20040214) -- S ground touching bow had an overwork -- U left stem is now 160pt wide -- u is now wider -- a lBearing 90 => 100 -- s rBearing 108 => 115 -- z has now round edges -- b change in the bow -- g strong changes in the bows -- t doing a step backwards: lifting bow upper again -- H became 25pt wider -- B,D,K,M,R,T,U got the new serifs -- e hStem moved slightly upwards -- rg kernpair 0 => -25 -- X completely reworked, added adequate kern pairs -- c overworked -- Z edge improved -- ? (Questionmark) new designed -- ! (Exklamationmark) new designed -- p,q shortened the Unterl�ge - -Changes to version 0.5.0 (20040212) -It showed that most of my critics said that a drop -would be better readably and nicer to look at than -a square in letters like r,c,f,a -result is a major design-shift: we are now doing -charakters like r,f,y,a with drops. I'll try to -conservate old forms for a later splitting in two fonts. -- i still reducing rBearing 70 => 65 -- n,m,h enlarging rBearing 50 => 60 -- all small: Bearings enlarged by 5pt on each site -- all capitals: Bearings enlarged about 10pt on each site -- r,f overworked the new drop -- J,c have now a drop too -- b changes in the bow -- y greatly overworked -- �desiris corrected -- o had some changes in the round -- P new serifs -- E overworked upper serif -- G overworked upper serif -- g earstem is now slighy bigger - - - -Changes to version 0.4.9 (20040205) -- A longer Serifs -- f #balken hochgeschoben - balken dnner -- Z rBearing 34 => 40 - now wider -- E,F,L Serifs overworked (more dominant now) -- a thicker in the bow - rBearing 45 => 38 - two versions as with r -- i reduce rBearing 77 => 70 -- h,m,n rBearing 45 => 50 -- t changes in the bow -- H hstem changed -- b change in vStem -- q ear changed -- u small change in left part of the bow -- s rBearing 90 => 98 - lBearing 100 => 108 -- r rBearing 56 => 60 - great change in the arm, two versions, - one completely new with drop-end - old form with edge-end (on ) -- d rBearing 86 => 90 -- b rBearing 80 => 85 -- dieresis, accents a.s.f moved 10pt upwards -- o is now rounder -- M arrow is now slightly round -- y had an overwork -- f change in the bow - -Changes to version 0.4.8 (20040202) -- h,m,n rBearing 35 => 45 -- v,w RBearing 20 => 27 - lBearing 20 => 24 -- u rBearing 70 => 75 - vStem left was 2 pt to wide - vStem right was 1 pt to wide -- d rBearing 78 => 85 - changes in the bow - vStem was 1 pt to wide -- H rBearing 64 => 70 -- r vStem was 1 pt to wide -- t major overwork -- i reduce rBearing 85 => 78 - lBearing 70 => 75 -- e rBearing 77 => 75 -- l rBearing 60 => 70 - lBearing 73 => 75 -- y search for a better design -- M rBearing 70 => 80 -- c changes in the bow -- f has a less dominant bow now -- N has now a spice V-Compound - new Serifs -- E,F new middle hStem -- a now thicker - rBearing 48 => 45 -- W() kerning reduced to -125 -- C rBearing 70 => 80 -- all small: vStem wider 142 => 143 - -Changes to version 0.4.7 (20040124) -- E majority overworked - new serifs - thinner hline - wider - rBearing 30 => 70 -- F same as with E -- I rBearing 38 => 65 - new serifs - hinted -- M rBearing 40 => 70 -- H rBearing 40 => 65 - new serifs - hinted -- K rBearing 10 => 25 -- L new Serifs - hinted -- S rBearing 70 => 80 -- b rBearing 70 => 80 - hinted -- e rBearing 70 => 75 - lBearing 70 => 80 - hinted - some changes in the charakter -- a is fatter now - overworked whole char - -- O rBearing 100 => 105 -- m,n,h rBearing 24 => 35 -- s rBearing 87 => 90 -- r rBearing 48 => 55 -- v,w completely new designed - -Changes to version 0.4.6 (20040124) -- [space] is now wider 595 => 690 -- [small] rBeraing, lBearing extended about 3pt each - enlarged to 102% -- a upper bow is has now a lower beginning - has now a "a-typical" serif - has a thicker bauch -- u is 12pt wider -- n is 8pt wider -- m is 15pt wider -- b is 11pt wider -- c open end lifted up -- i reduce a bit backwards rBearing 95 => 85 -- d wider about 10pt - bow is higher -- e more dynamic now - wider -- o overworked -- v big change -- z upper serif had a very small change - -Changes to version 0.4.5 (20040114) -- U left arm is thinner now - changes in the bow -- p bow more dynamic -- d bow now more dynamic -- c slightly thinner now - more points -- L foot is 30pts wider -- N Trick in the edges has been to strong - diagonal arm is thinner now -- k lBearing 29 => 22 -- po, pe, pd, od, a.s.f kerning 0 => +25 -- all small: enlarged Bearings to 105% -- space: enlarged to 595 -- a new serifs -- b new serifs -- d new serifs -- h new serifs -- i new serifs (upper and below) to test whether more - points in serifs makes print-outs and desktop-views better) - gave more rBearing 66 => 90 - dot is now bigger again (105%) -- j new serifs -- k new serifs -- l new serifs -- m new serifs - bows are much better now -- n new serifs - the bow is much better now -- p new serifs - changes in the bow -- q new serifs -- r new serifs -- u new serifs - - -Changes to version 0.4.4 (20040108) -- M was a little too extravagant hopefully better now -- c was to huge - bow was to high -- o rBearing 70 => 65 -- P rBearing 28 => 20 -- vo,wo, ve, we kerning -15 => -20 -- va,wa kerning -5 => -10 -- ow,ov kerning -25 => 20 -- ev,ew kerning -25 => 20 -- y created kernpairs synonym to v,w -- v-family "v-" kerning 0 => -25 -- ro, re kerning -30 => -15 -- O slightly thinner -- i hinting now better -- all small: overworked hints - -Changes to version 0.4.3 (20031219) -- c some small changes - lbearing 70 => 75 - rBearing 50 => 45 - changes in the bow - cedilla some points to the left -- ve, we, wo, vo kerning -30 => -15 -- va, wa kerning -15 => -5 -- M became more dynamic - rBearing 60 => 40 -- H rBearing 50 => 40 -- .,i,j... (dots) were slightly oval -- j rBearing 159 => 140 -- k arm raised back again -- V,W rBearing 16 => 10 -- Vo, Wo, We, Ve kerning -120 => -140 -- Wa, Va kerning -120 => -130 -- s upper serif now more vertikal -- b rBearing 72 => 65 - bow had some small changes -- R is a little wider now - bow is a little better -- g many changes in the bow - more space between the upper and the down circle -- P constructed a new P from the new R -- y great work but design not yet finished -- u some small changes in first vStem to avoid different thickness in print-outs - - -Changes to version 0.4.2 (20031217) -Greek Symbols will come: -- Delta added -- Psi added -- Sigmal added -- Phi -- Lambda added -- Omega added -- Xi added -- Gamma added -- te kerning -25 => 0 -- t rBearing 65 => 75 -- c rBearing 60 => 50 -- �rBearing 94 => 70 -- �rBearing 59 => 65 -- rBearing 62 => 65 -- all round small charakters a,b,c,d,e,g,h,i,j,m,n,o,p,q,r,s - have grown a bit to get a better text-tape -- g rBearing 60 => 50 -- u lBearing 60 => 53 - -Changes to version 0.4.1 (20031214) -- all rounds to Bearing 75 => 70 - (b, c, d, o, p, q) -- e: rBearing 75 => 65 -- letters like i, m,n,r, a.s.f. lBearing: - 65 => 60 -- i: 70 => 65 -- b: round has been overworked -- Vi, Wi kerning: -70 => -50 -- Vo, Ve, Va, Wo, We, Wa kerning -150 => -120 -- t: top is a little lower now -- � major overwork -- S: major overwork -- r: a step back to the r in 0.3.9 -- P: Bow is better now -- a: overwork of the bow -- ow, ew, ev, ov kerning => -25 -- H, I: rBearing 50 -- M rBearing 69 => 60 -- yc kerning => -25 -- N is wider now -- y: rBearing 24 => 19 -- r: rBearing 25 => 28 - -Changes to version 0.4.0 (20031207) -- a, u rightBearing 59 => 65 -- v,w,V,W were to far down -22 => -5 -- v,w RBearing 24 => 19 -- r thicker bow -- all rounds to Bearing 99 => 75 - (b, c, d, e, o, p, q) -- V,W RBearing 20 => 16 -- g rBearing 70 => 60 -- t lBearing 86 => 75 -- n changes in the bow -- s lBearing 82 => 92 -- s rBearing 92 => 80 -- tt kerning 40 => 15 -- f slightly dominanter bow -- ff -100 => -80 -- fb 50 => 80 -- t rBearing 80 => 65 -- ta kern -10 => 0 (deregister kern pair) -- r rBearing 50 => 25 -- g lBearing 79 => 69 - - -Changes to version 0.3.9 (20031113) -- the changes of the last version brought some wrong bearings - following are corrected now: - - a,u right bearing 80 => 65 - - a left 85 => 79 - - d right 80 => 80 - - l rigth 69 => 58 - - tt kernpair_dist -80 => -40 - - s left and rigtht bearing 85 => 90 - - i left and rigtht bearing 69 => 76 - - w, v left and rigtht bearing 22 => 28 - - h left 71 => 68 - - o both 89 => 82 - - t left 96 => 86 - - c left 100=> 90 - - re, ke, ko kern pair [di]: -20 = -30 - - rg kern pair [di]: 0 => -20 - - r. kern pair [di]: 0 => -60 - - H had the same bearing as M but M has longer serifs => H 69=>51 - -- e seemed to be to domaninant, => shrinked to 98% -- s seemed to small => enlarged to x=102% y=101% -- Q got a connection between tilde and the O -- f bow got a bit longer in right direction -- b change in the bow -- longer serifs for the gemeinen -- N got wider -- h,n got wider -- new cedilla -- ? overworked - - - -Changes to version 0.3.8 (20031102) -- v, w are now wider -- a: grave changes -- i,j: Dot got 10% smaller -- .;:? Dots got 10% smaller -- ? complete newdesigned -- , (Komma) major overwork -- �(German sz) overworked -- t RBearing + 10pt -- u more contras and finer connection -- U now wider and more round bow -- N second trick on the angle of left hstem and diagonal -- K: overworked -- J: better bow -- k: overworked -- b,p, D, B, P: better bow -- h, m, n, u: nicer and more contrative bows -- O, Q better rounds now -- g got new ear -- all letters: RBearing, LBearing + 15% -- e: small changes in the bow - -Changes to version 0.3.7 (20031028) -- r seemed to thick (VStem) in small printouts => changes in bow -- h right VStem seemed to thick in small printouts => changes in bow -- u is now what I wanted it to be wider and thinner as well more elegant -- c is now as thinn as the bow of d; small changes in R+LBeering -- g became slightly thinner -- y is slightly better now (less extreme) but still needs a lot of work -- t's RBearing was too small (+10pt) -- k's arm was liftet slightly above the x-height, because it seemed to low -- S became slightly thinner -- T's roof won hight because it looked slightly smaller than other Caps -- p's bow is now like the one of d -- e is now wider -- O slight changes - -Changes to version 0.3.6 (20031025) -- Bearings for all Gemeine (small letters) changed! -- g: ear isn't so potent anymore, wider, increased Bearings -- m,n,h overworked the bow -- a overworked the bow - - -Changes to version 0.3.5 (20031019) -- R: lost fracture from last release removed -- | (pipeline): finer outline -- `' (high commas) inserted -- slashes added -- elipses added -- promille added -- <> (dynamic ones) added -- % new design (efont) -- ! had changes -- & (ampersand) from efont -- '," (inch, geometr. minute/second) are now undynamic -- / smaller -- numbers: new medi�al (OSF) numbers from efont -- @ has a new a in the middle -- v, w: finer, make paralell, anti-block-trick -- V, W: anti-block-trick, make parallel -- N,Z,M,K,Y,k,x,y,z,X: make paralell -- (pound) added -- some more little things - -Changes to version 0.3.4 (20031019) -- C has greately changed and is now what I wanted it to be. -- S: slight changes in the upper bow and serif -- h has now more point in its bow -- H, A: HLine is now 80pt thick -- G has greately changed and is now what I wanted it to be -- b, d, h, i, j, k, l, m, n, p, r: the upper serif has now a - certain slight concave bow -- same with a,d,u, just with the under serif -- R got more points -- e: slight changes and new points -- U: more points and wider -- O: slight changes -- Q: RBearing +20pt -- p: slight changes and new points -- Accents are smaller now -- j: changes in the bow -- {},(),[]: new brackets anch important changes in all -- some Bearings slightly corrected - -Take this version as a first milestone! -Changes to version 0.3.3 (20031019) -- O, Q became slightly thinner -- P small but important corrections -- d, b better round like already done with p & q -- x had major changes -- s had major changes -- o very light changes -- a, d, u have a walking foot now -- J: slight changes in the bow -- D: major changes in the bow -- B: major changes, grew wider -- c: light changes -- g: light changes -- e: light changes -- stem width of small letters are now 140 instead of 145 -- p, q: weniger Unterl�ge -- S: has now more RBearing -- the lBearing and RBearing of the Gemeinen (small letters) have been extended - about 5pt. -- �(sz, german) had a redesign but still needs a lot of work - -Changes to version 0.3.2 (20031018) -- R has been overworked and is now similar to P again -- P has been slightly overworked -- M is now wider -- B had major changes -- T's and Z new serifs had to be reduced a bit again -- z now got the same serif as its father -- r got again more expressiv -- s had an overwork -- x: its thicker leg is now slightly thinner -- l, i, d, b, h, m, n, p, q, r, t, u, k, j, f is now 145pt thick -- H, I, J, E, F is now 160pt thick -- E, F are now wider -- e: slight changes -- C: better but still not like I want it to have -- v, w: feet now beyond groundline -- c is much better now -- o is much better now -- O is much better now -- B is much better now -- S: the upper part is wider now -- q is completely new dedigned. May this be a good example for b, p, d? -- dieresis (german umlaut points) have more space in between themselves -- Q looks wonderful now (at least much much better) -- () are now much better (taken from GPLed efont) -- longs (the old f-like s) has now its real place -- X got the last missing serif of the whole font (!) ;-) - -Changes to version 0.3.1 (20031016) -- r's ear has now a lower connection to vStem and looks hopefully better in -small points, - rightBearing increased -- g is now slightly smaller and generally smarter -- dieresis (namely the two dots that belong onto the german umlauts are smaller -(85%) -- K: its leg is now doing a step forward -- J has lost its old serif at the ground-line and has other majot changes -- H hStem is not as thick anymore -- A same like with H above -- G's table is now longer -- E,F: hStems are now 85points thick and not 104pt -- D became fat -- T,Z: Serif now grow into the air, hStems are now ca. 85pt -- U has grown wider -- u's left vStem got thinner, rBearing +10 -- i: lBearing +10, rightBearing +10 -- c: lBearing + -- I: rBearing + -- L: rBearing + and hStem is now ca. 85pt -- dot: lBearing +, rBearing + -- C: it's getting better but much work remains -- a: more contrast in changing line-thickness -- w looks now and again like a real renaissance w -- V gained a serif at his left arm -- W is newly generated from two Vs and now looks again like a real renaissance W -- new kearn pairs for V and W -- y has been newly formed out of v - -Changes to version 0.3.0 (20031011) -- big change: All letters became bigger to reduce the lost space above the -latters that no - PC-Font seems to have normally... -- A has now more right bearing -- r got back the 15 points rightBearing it lost while extending its ear in 0.2.8 -- G rightBearing is now 55pt -- e has now more left and right bearing -- v same as e above -- o same as e above -- n has now slightly more lBearing -- d, b now got slightly more bearing at the round side -- u got more rBearing (same as "a") -- ko kern pair was to close together, fixed -- k has now more rBearing (not negative anymore) -- ka is a new kern pair -- a & u more rBearing (+6pt) -- B, M, H, O, D got more rBearing -- "V-" is obviously a kern pair and same with T,W,X,... -- AC, AG, AO, AQ, AT, AU, AV, AW, AY are new kern pairs -- small kerning for round letters and "." e.g.: "o.", "p.",... -- c: major changes -- C: major changes - - -Changes to version 0.2.9 (20031008) -- Added some arrows you need for chemistry-terms (->, <-, <-->, v, � - -Changes to version 0.2.8 (20031005) -- did a little work in kerning of pairs like Vx, Wx, fx, ff -- E,F,k: vertical stem is now 2 points thinner -- n overworked. Major changes: left vertikal stem has now lost sharpness; - bow from n is now just a connect to the left HStem an no part anymore; - new character balance on the right -- same like above with h, m, r -- r got mor extrem in bow and ear -- b, d, p similar procedure like above with m, n, r -- i, j, l, k, b, d, h the overlength is now slightly unsharpened -- G is now mor round und more proud - -Changes to version 0.2.7 (20031002) -- g got a slightly smaller ear -- fi-ligature has better right bearing (the one of "i" of course) -- n has now less right bearing (20 -> 5) -- m has now more right bearing (-8 -> 5) -- h has now less right bearing (12 -> 5) -- c got a bigger left bearing (54 -> 60) -- b's stem seam to be to thick. I shrinked its width from 42 -> 37 -- r: increased right bearing (25 -> 35) -- V got a bigger left vertical -- N got a thinner vertical -- 1 (one) is littler thinner now and again -- . (dot) has now greater right bearing (55 -> 65) -- , (comma) has now greater right bearing (55 -> 65) -- t got bigger right bearing (45 -> 50) -- z: for aesthetical reasons the above horizontal stem seems to must be thinner -than the one at the -base line, so 9points off - -Changes to version 0.2.6 (20030930) -- I overworked all serifs! The results are not visible in printing small sizes -in TrueType -but since AutoHinting recognizes the serifs now we should have better printing -results at -good postscript printers in PostScript-Fonts. -- Kerning table has been greately expanded even for pairs like ke, ka... Very -sad that nearly all -Linux-TrueType programs don't care about the kerning table at all! This must -change in future! -- g has been overworked and seems to become pretty at least. Especially the ear -had a good change. -- C had major changes and satisfies me now. -- all numbers had some changes and got for the first all the same bearings left -and right -- fi-ligature had complete redo, looks better but doesn't satisfies me, yet -- r got a little thicker nipple at the right end of its arm that leads to better -printing an -recognition results at small points -- t has a slighly thinner round in its neck now \ No newline at end of file diff --git a/fonts/Linux-Libertine/GPL.txt b/fonts/Linux-Libertine/GPL.txt deleted file mode 100644 index b890e55..0000000 --- a/fonts/Linux-Libertine/GPL.txt +++ /dev/null @@ -1,343 +0,0 @@ - GNU GENERAL PUBLIC LICENSE (with font exception) - Version 2, June 1991 - - Copyright (C) 1989, 1991 Free Software Foundation, Inc. - 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA - Everyone is permitted to copy and distribute verbatim copies - of this license document, but changing it is not allowed. - - Preamble - - The licenses for most software are designed to take away your -freedom to share and change it. By contrast, the GNU General Public -License is intended to guarantee your freedom to share and change free -software--to make sure the software is free for all its users. This -General Public License applies to most of the Free Software -Foundation's software and to any other program whose authors commit to -using it. (Some other Free Software Foundation software is covered by -the GNU Library General Public License instead.) You can apply it to -your programs, too. - - When we speak of free software, we are referring to freedom, not -price. Our General Public Licenses are designed to make sure that you -have the freedom to distribute copies of free software (and charge for -this service if you wish), that you receive source code or can get it -if you want it, that you can change the software or use pieces of it -in new free programs; and that you know you can do these things. - - To protect your rights, we need to make restrictions that forbid -anyone to deny you these rights or to ask you to surrender the rights. -These restrictions translate to certain responsibilities for you if you -distribute copies of the software, or if you modify it. - - For example, if you distribute copies of such a program, whether -gratis or for a fee, you must give the recipients all the rights that -you have. You must make sure that they, too, receive or can get the -source code. And you must show them these terms so they know their -rights. - - We protect your rights with two steps: (1) copyright the software, and -(2) offer you this license which gives you legal permission to copy, -distribute and/or modify the software. - - Also, for each author's protection and ours, we want to make certain -that everyone understands that there is no warranty for this free -software. If the software is modified by someone else and passed on, we -want its recipients to know that what they have is not the original, so -that any problems introduced by others will not reflect on the original -authors' reputations. - - Finally, any free program is threatened constantly by software -patents. We wish to avoid the danger that redistributors of a free -program will individually obtain patent licenses, in effect making the -program proprietary. To prevent this, we have made it clear that any -patent must be licensed for everyone's free use or not licensed at all. - - The precise terms and conditions for copying, distribution and -modification follow. - - GNU GENERAL PUBLIC LICENSE - TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION - - 0. This License applies to any program or other work which contains -a notice placed by the copyright holder saying it may be distributed -under the terms of this General Public License. The "Program", below, -refers to any such program or work, and a "work based on the Program" -means either the Program or any derivative work under copyright law: -that is to say, a work containing the Program or a portion of it, -either verbatim or with modifications and/or translated into another -language. (Hereinafter, translation is included without limitation in -the term "modification".) Each licensee is addressed as "you". - -Activities other than copying, distribution and modification are not -covered by this License; they are outside its scope. The act of -running the Program is not restricted, and the output from the Program -is covered only if its contents constitute a work based on the -Program (independent of having been made by running the Program). -Whether that is true depends on what the Program does. - - 1. You may copy and distribute verbatim copies of the Program's -source code as you receive it, in any medium, provided that you -conspicuously and appropriately publish on each copy an appropriate -copyright notice and disclaimer of warranty; keep intact all the -notices that refer to this License and to the absence of any warranty; -and give any other recipients of the Program a copy of this License -along with the Program. - -You may charge a fee for the physical act of transferring a copy, and -you may at your option offer warranty protection in exchange for a fee. - - 2. You may modify your copy or copies of the Program or any portion -of it, thus forming a work based on the Program, and copy and -distribute such modifications or work under the terms of Section 1 -above, provided that you also meet all of these conditions: - - a) You must cause the modified files to carry prominent notices - stating that you changed the files and the date of any change. - - b) You must cause any work that you distribute or publish, that in - whole or in part contains or is derived from the Program or any - part thereof, to be licensed as a whole at no charge to all third - parties under the terms of this License. - - c) If the modified program normally reads commands interactively - when run, you must cause it, when started running for such - interactive use in the most ordinary way, to print or display an - announcement including an appropriate copyright notice and a - notice that there is no warranty (or else, saying that you provide - a warranty) and that users may redistribute the program under - these conditions, and telling the user how to view a copy of this - License. (Exception: if the Program itself is interactive but - does not normally print such an announcement, your work based on - the Program is not required to print an announcement.) - -These requirements apply to the modified work as a whole. If -identifiable sections of that work are not derived from the Program, -and can be reasonably considered independent and separate works in -themselves, then this License, and its terms, do not apply to those -sections when you distribute them as separate works. But when you -distribute the same sections as part of a whole which is a work based -on the Program, the distribution of the whole must be on the terms of -this License, whose permissions for other licensees extend to the -entire whole, and thus to each and every part regardless of who wrote it. - -Thus, it is not the intent of this section to claim rights or contest -your rights to work written entirely by you; rather, the intent is to -exercise the right to control the distribution of derivative or -collective works based on the Program. - -In addition, mere aggregation of another work not based on the Program -with the Program (or with a work based on the Program) on a volume of -a storage or distribution medium does not bring the other work under -the scope of this License. - - 3. You may copy and distribute the Program (or a work based on it, -under Section 2) in object code or executable form under the terms of -Sections 1 and 2 above provided that you also do one of the following: - - a) Accompany it with the complete corresponding machine-readable - source code, which must be distributed under the terms of Sections - 1 and 2 above on a medium customarily used for software interchange; or, - - b) Accompany it with a written offer, valid for at least three - years, to give any third party, for a charge no more than your - cost of physically performing source distribution, a complete - machine-readable copy of the corresponding source code, to be - distributed under the terms of Sections 1 and 2 above on a medium - customarily used for software interchange; or, - - c) Accompany it with the information you received as to the offer - to distribute corresponding source code. (This alternative is - allowed only for noncommercial distribution and only if you - received the program in object code or executable form with such - an offer, in accord with Subsection b above.) - -The source code for a work means the preferred form of the work for -making modifications to it. For an executable work, complete source -code means all the source code for all modules it contains, plus any -associated interface definition files, plus the scripts used to -control compilation and installation of the executable. However, as a -special exception, the source code distributed need not include -anything that is normally distributed (in either source or binary -form) with the major components (compiler, kernel, and so on) of the -operating system on which the executable runs, unless that component -itself accompanies the executable. - -If distribution of executable or object code is made by offering -access to copy from a designated place, then offering equivalent -access to copy the source code from the same place counts as -distribution of the source code, even though third parties are not -compelled to copy the source along with the object code. - - 4. You may not copy, modify, sublicense, or distribute the Program -except as expressly provided under this License. Any attempt -otherwise to copy, modify, sublicense or distribute the Program is -void, and will automatically terminate your rights under this License. -However, parties who have received copies, or rights, from you under -this License will not have their licenses terminated so long as such -parties remain in full compliance. - - 5. You are not required to accept this License, since you have not -signed it. However, nothing else grants you permission to modify or -distribute the Program or its derivative works. These actions are -prohibited by law if you do not accept this License. Therefore, by -modifying or distributing the Program (or any work based on the -Program), you indicate your acceptance of this License to do so, and -all its terms and conditions for copying, distributing or modifying -the Program or works based on it. - - 6. Each time you redistribute the Program (or any work based on the -Program), the recipient automatically receives a license from the -original licensor to copy, distribute or modify the Program subject to -these terms and conditions. You may not impose any further -restrictions on the recipients' exercise of the rights granted herein. -You are not responsible for enforcing compliance by third parties to -this License. - - 7. If, as a consequence of a court judgment or allegation of patent -infringement or for any other reason (not limited to patent issues), -conditions are imposed on you (whether by court order, agreement or -otherwise) that contradict the conditions of this License, they do not -excuse you from the conditions of this License. If you cannot -distribute so as to satisfy simultaneously your obligations under this -License and any other pertinent obligations, then as a consequence you -may not distribute the Program at all. For example, if a patent -license would not permit royalty-free redistribution of the Program by -all those who receive copies directly or indirectly through you, then -the only way you could satisfy both it and this License would be to -refrain entirely from distribution of the Program. - -If any portion of this section is held invalid or unenforceable under -any particular circumstance, the balance of the section is intended to -apply and the section as a whole is intended to apply in other -circumstances. - -It is not the purpose of this section to induce you to infringe any -patents or other property right claims or to contest validity of any -such claims; this section has the sole purpose of protecting the -integrity of the free software distribution system, which is -implemented by public license practices. Many people have made -generous contributions to the wide range of software distributed -through that system in reliance on consistent application of that -system; it is up to the author/donor to decide if he or she is willing -to distribute software through any other system and a licensee cannot -impose that choice. - -This section is intended to make thoroughly clear what is believed to -be a consequence of the rest of this License. - - 8. If the distribution and/or use of the Program is restricted in -certain countries either by patents or by copyrighted interfaces, the -original copyright holder who places the Program under this License -may add an explicit geographical distribution limitation excluding -those countries, so that distribution is permitted only in or among -countries not thus excluded. In such case, this License incorporates -the limitation as if written in the body of this License. - - 9. The Free Software Foundation may publish revised and/or new versions -of the General Public License from time to time. Such new versions will -be similar in spirit to the present version, but may differ in detail to -address new problems or concerns. - -Each version is given a distinguishing version number. If the Program -specifies a version number of this License which applies to it and "any -later version", you have the option of following the terms and conditions -either of that version or of any later version published by the Free -Software Foundation. If the Program does not specify a version number of -this License, you may choose any version ever published by the Free Software -Foundation. - - 10. If you wish to incorporate parts of the Program into other free -programs whose distribution conditions are different, write to the author -to ask for permission. For software which is copyrighted by the Free -Software Foundation, write to the Free Software Foundation; we sometimes -make exceptions for this. Our decision will be guided by the two goals -of preserving the free status of all derivatives of our free software and -of promoting the sharing and reuse of software generally. - -As a special exception, if you create a document which uses this font, and embed this font or unaltered portions of this font into the document, this font does not by itself cause the resulting document to be covered by the GNU General Public License. This exception does not however invalidate any other reasons why the document might be covered by the GNU General Public License. If you modify this font, you may extend this exception to your version of the font, but you are not obligated to do so. If you do not wish to do so, delete this exception statement from your version. - - NO WARRANTY - - 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY -FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN -OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES -PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED -OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF -MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS -TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE -PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, -REPAIR OR CORRECTION. - - 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING -WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR -REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, -INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING -OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED -TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY -YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER -PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE -POSSIBILITY OF SUCH DAMAGES. - - END OF TERMS AND CONDITIONS - - How to Apply These Terms to Your New Programs - - If you develop a new program, and you want it to be of the greatest -possible use to the public, the best way to achieve this is to make it -free software which everyone can redistribute and change under these terms. - - To do so, attach the following notices to the program. It is safest -to attach them to the start of each source file to most effectively -convey the exclusion of warranty; and each file should have at least -the "copyright" line and a pointer to where the full notice is found. - - - Copyright (C) - - This program is free software; you can redistribute it and/or modify - it under the terms of the GNU General Public License as published by - the Free Software Foundation; either version 2 of the License, or - (at your option) any later version. - - This program is distributed in the hope that it will be useful, - but WITHOUT ANY WARRANTY; without even the implied warranty of - MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the - GNU General Public License for more details. - - You should have received a copy of the GNU General Public License - along with this program; if not, write to the Free Software - Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA - - -Also add information on how to contact you by electronic and paper mail. - -If the program is interactive, make it output a short notice like this -when it starts in an interactive mode: - - Gnomovision version 69, Copyright (C) year name of author - Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. - This is free software, and you are welcome to redistribute it - under certain conditions; type `show c' for details. - -The hypothetical commands `show w' and `show c' should show the appropriate -parts of the General Public License. Of course, the commands you use may -be called something other than `show w' and `show c'; they could even be -mouse-clicks or menu items--whatever suits your program. - -You should also get your employer (if you work as a programmer) or your -school, if any, to sign a "copyright disclaimer" for the program, if -necessary. Here is a sample; alter the names: - - Yoyodyne, Inc., hereby disclaims all copyright interest in the program - `Gnomovision' (which makes passes at compilers) written by James Hacker. - - , 1 April 1989 - Ty Coon, President of Vice - -This General Public License does not permit incorporating your program into -proprietary programs. If your program is a subroutine library, you may -consider it more useful to permit linking proprietary applications with the -library. If this is what you want to do, use the GNU Library General -Public License instead of this License. - diff --git a/fonts/Linux-Libertine/INSTALL.txt b/fonts/Linux-Libertine/INSTALL.txt deleted file mode 100644 index aa15e03..0000000 --- a/fonts/Linux-Libertine/INSTALL.txt +++ /dev/null @@ -1,9 +0,0 @@ -1.) COMPILING -If you miss the directory "Fonts" here, you still have to compile the source-files which lay in the directory "SRC". You do this by calling "./make". Please note, that you'll need a recent version of fontforge to do so. You will also need a unix shell to interprete the scripts. If you have not a certain reason to compile the fonts yourself, we recommend you to download the respective "LinLibertineFont" archive from our website: -linuxlibertine.sf.net - -2.) INSTALL -Windows: Copy fonts into folder C:\windows\fonts. -Linux: Use system programs such as KDE-Kontrol to install the fonts. These also update Linux specific system files. - -Philipp Poll -- philthelion at users.sourceforge.net \ No newline at end of file diff --git a/fonts/Linux-Libertine/LICENCE.txt b/fonts/Linux-Libertine/LICENCE.txt deleted file mode 100644 index dd8b672..0000000 --- a/fonts/Linux-Libertine/LICENCE.txt +++ /dev/null @@ -1,7 +0,0 @@ -- Lizenz / Licence - - -Unsere Schriften sind frei im Sinne der GPL, d.h. (stark vereinfacht) dass Veränderungen an der Schriftart erlaubt sind unter der Bedingung, dass diese wieder der Öffentlichkeit unter gleicher Lizenz freigegeben werden. Querdenker behaupten oft, dass bei der Verwendung einer GPL-Schrift eingebettet in beispielsweise eine PDF auch diese freigestellt werden müsse. Deshalb gibt es die sogenannte "Font-exception" der GPL (welche diesem Lizenztext hinzugefügt wurde). Weitere Informationen zur GPL (Lizenztext mit Font-Exzeption als GPL.txt in diesem Paket). -Zusätzlich stehen die Schriften unter der Open Font License (siehe OFL.txt). - -Our fonts are free in the sense of the GPL. In short: Changing the font is allowed as long as the derivative work is published under the same licence again. Pedantics keep claiming that the embedded use of GPL-fonts in i.e. PDFs requires the free publication of the PDF as well. This is why our GPL contains the so called "font exception". Further information about the GPL (licence text with font exception see GPL.txt in this package). -Additionally our fonts are licensed under the Open Fonts License (see OFL.txt). \ No newline at end of file diff --git a/fonts/Linux-Libertine/LinBiolinum_K.otf b/fonts/Linux-Libertine/LinBiolinum_K.otf deleted file mode 100644 index aae5df2..0000000 Binary files a/fonts/Linux-Libertine/LinBiolinum_K.otf and /dev/null differ diff --git a/fonts/Linux-Libertine/LinBiolinum_R.otf b/fonts/Linux-Libertine/LinBiolinum_R.otf deleted file mode 100644 index ada5880..0000000 Binary files a/fonts/Linux-Libertine/LinBiolinum_R.otf and /dev/null differ diff --git a/fonts/Linux-Libertine/LinBiolinum_RB.otf b/fonts/Linux-Libertine/LinBiolinum_RB.otf deleted file mode 100644 index d86721e..0000000 Binary files a/fonts/Linux-Libertine/LinBiolinum_RB.otf and /dev/null differ diff --git a/fonts/Linux-Libertine/LinBiolinum_RI.otf b/fonts/Linux-Libertine/LinBiolinum_RI.otf deleted file mode 100644 index 86d0cf4..0000000 Binary files a/fonts/Linux-Libertine/LinBiolinum_RI.otf and /dev/null differ diff --git a/fonts/Linux-Libertine/LinLibertine_DR.otf b/fonts/Linux-Libertine/LinLibertine_DR.otf deleted file mode 100644 index 4ff2874..0000000 Binary files a/fonts/Linux-Libertine/LinLibertine_DR.otf and /dev/null differ diff --git a/fonts/Linux-Libertine/LinLibertine_I.otf b/fonts/Linux-Libertine/LinLibertine_I.otf deleted file mode 100644 index 14e5a74..0000000 Binary files a/fonts/Linux-Libertine/LinLibertine_I.otf and /dev/null differ diff --git a/fonts/Linux-Libertine/LinLibertine_M.otf b/fonts/Linux-Libertine/LinLibertine_M.otf deleted file mode 100644 index 6c81e7d..0000000 Binary files a/fonts/Linux-Libertine/LinLibertine_M.otf and /dev/null differ diff --git a/fonts/Linux-Libertine/LinLibertine_R.otf b/fonts/Linux-Libertine/LinLibertine_R.otf deleted file mode 100644 index 6d345d5..0000000 Binary files a/fonts/Linux-Libertine/LinLibertine_R.otf and /dev/null differ diff --git a/fonts/Linux-Libertine/LinLibertine_RBI.otf b/fonts/Linux-Libertine/LinLibertine_RBI.otf deleted file mode 100644 index c1a4ff7..0000000 Binary files a/fonts/Linux-Libertine/LinLibertine_RBI.otf and /dev/null differ diff --git a/fonts/Linux-Libertine/LinLibertine_RZ.otf b/fonts/Linux-Libertine/LinLibertine_RZ.otf deleted file mode 100644 index 5ce6b73..0000000 Binary files a/fonts/Linux-Libertine/LinLibertine_RZ.otf and /dev/null differ diff --git a/fonts/Linux-Libertine/LinLibertine_RZI.otf b/fonts/Linux-Libertine/LinLibertine_RZI.otf deleted file mode 100644 index 17331a0..0000000 Binary files a/fonts/Linux-Libertine/LinLibertine_RZI.otf and /dev/null differ diff --git a/fonts/Linux-Libertine/OFL-1.1.txt b/fonts/Linux-Libertine/OFL-1.1.txt deleted file mode 100644 index 8aed073..0000000 --- a/fonts/Linux-Libertine/OFL-1.1.txt +++ /dev/null @@ -1,94 +0,0 @@ -Copyright (c) 2003–2012, Philipp H. Poll (www.linuxlibertine.org | gillian at linuxlibertine.org), -with Reserved Font Name "Linux Libertine" and "Biolinum". - -This Font Software is licensed under the SIL Open Font License, Version 1.1. -This license is copied below, and is also available with a FAQ at: -http://scripts.sil.org/OFL - - ------------------------------------------------------------ -SIL OPEN FONT LICENSE Version 1.1 - 26 February 2007 ------------------------------------------------------------ - -PREAMBLE -The goals of the Open Font License (OFL) are to stimulate worldwide -development of collaborative font projects, to support the font creation -efforts of academic and linguistic communities, and to provide a free and -open framework in which fonts may be shared and improved in partnership -with others. - -The OFL allows the licensed fonts to be used, studied, modified and -redistributed freely as long as they are not sold by themselves. The -fonts, including any derivative works, can be bundled, embedded, -redistributed and/or sold with any software provided that any reserved -names are not used by derivative works. The fonts and derivatives, -however, cannot be released under any other type of license. The -requirement for fonts to remain under this license does not apply -to any document created using the fonts or their derivatives. - -DEFINITIONS -"Font Software" refers to the set of files released by the Copyright -Holder(s) under this license and clearly marked as such. This may -include source files, build scripts and documentation. - -"Reserved Font Name" refers to any names specified as such after the -copyright statement(s). - -"Original Version" refers to the collection of Font Software components as -distributed by the Copyright Holder(s). - -"Modified Version" refers to any derivative made by adding to, deleting, -or substituting -- in part or in whole -- any of the components of the -Original Version, by changing formats or by porting the Font Software to a -new environment. - -"Author" refers to any designer, engineer, programmer, technical -writer or other person who contributed to the Font Software. - -PERMISSION & CONDITIONS -Permission is hereby granted, free of charge, to any person obtaining -a copy of the Font Software, to use, study, copy, merge, embed, modify, -redistribute, and sell modified and unmodified copies of the Font -Software, subject to the following conditions: - -1) Neither the Font Software nor any of its individual components, -in Original or Modified Versions, may be sold by itself. - -2) Original or Modified Versions of the Font Software may be bundled, -redistributed and/or sold with any software, provided that each copy -contains the above copyright notice and this license. These can be -included either as stand-alone text files, human-readable headers or -in the appropriate machine-readable metadata fields within text or -binary files as long as those fields can be easily viewed by the user. - -3) No Modified Version of the Font Software may use the Reserved Font -Name(s) unless explicit written permission is granted by the corresponding -Copyright Holder. This restriction only applies to the primary font name as -presented to the users. - -4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font -Software shall not be used to promote, endorse or advertise any -Modified Version, except to acknowledge the contribution(s) of the -Copyright Holder(s) and the Author(s) or with their explicit written -permission. - -5) The Font Software, modified or unmodified, in part or in whole, -must be distributed entirely under this license, and must not be -distributed under any other license. The requirement for fonts to -remain under this license does not apply to any document created -using the Font Software. - -TERMINATION -This license becomes null and void if any of the above conditions are -not met. - -DISCLAIMER -THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, -EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF -MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT -OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE -COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, -INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL -DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING -FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM -OTHER DEALINGS IN THE FONT SOFTWARE. diff --git a/fonts/Linux-Libertine/README b/fonts/Linux-Libertine/README deleted file mode 100644 index d113ee0..0000000 --- a/fonts/Linux-Libertine/README +++ /dev/null @@ -1,36 +0,0 @@ -LOFP - Libertine Open Fonts Project - -1. OPEN FONTS PROJECT'S AIMS -We work on a serif and organic grotesque font-family for practical use in documents. Our project aims at creating a free alternative to the standard W*ndows Font (T*mes). -But neveretheless Libertine and Biolinum are not a clone of any common font! They have been developed from scratch and go different ways in typography than the Times or Arial. Just the useability and the dimensions shall be similar, Libertine should be even better for typical office use! If you want Times- and Arial-clones go elsewhere. If you just need reliable and good typography give our fonts a chance. If you want to know more about the design of Libertine and Biolinum, have a look at our website. - -2. LICENSE AND OPENSOURCE -We publish our fonts under the terms of the GPL (see GPL.txt) and OFL (OFL.txt) --> see also LICENCE.txt! -The OpenSource-tool Fontforge is used as font editor (see http://fontforge.sf.net). - -3. FONT FORMATS TTF VS. OTF -The font files are available as TTF (TrueType) and OTF (OpenType) fonts. The TTF-Family is called -"Linux Libertine" and "Linux Biolinum" -and the OTF -"LinuxLibertine O" and "Linux Biolinum O". - -So that both types can be installed and used parallely. -Most often TTF is the better supported format though OTF has advances in printing. Decide yourself what is better for your purpose. OpenType-features are equally available in both fonts. Note that OpenOffice doesn’t support OTFs, yet. - -4. THE LINUX BIOLINUM FONT FACE -Please note: The Biolinum is a very early version. While you use Libertine-Fonts without any warranty anyway, take special care with this young font face. - -5. HINTING -The TrueType-hinting is a complex technique and our editor FontForge doesn't support full possibilities (but it becomes alot better version by version)... -Since version 2.7 also the normal TTFs are hinted. If you don't like this, send me a mail. You may also try the OpenTypes (which contain PS-Hintings which are quite good supported by FontForge). - -6. DOWNLOAD AND CONTACT -We publish our fonts at http://www.linuxlibertine.org/. - -7. THE UNDERLINED VARIANT -Please note: The underlined variant is recently not being maintained because its concept doesn’t seem to be sofware-technically reliable and because of lack of interest. -The advantage of this font was that g, commas, cedillas... were not overprinted by the line anymore. For technical reasons the space was not underlined but you could use the _ instead. In this font it had the width of the space and the line was at hight of the underline. The underlined variant used an older font outline. - -Philipp Poll -- gillian at linuxlibertine.org - diff --git a/fonts/Linux-Libertine/Readme-TEX.txt b/fonts/Linux-Libertine/Readme-TEX.txt deleted file mode 100644 index 7d485cd..0000000 --- a/fonts/Linux-Libertine/Readme-TEX.txt +++ /dev/null @@ -1,8 +0,0 @@ -Libertine and LaTex - -Because of some advantages over XeTex we reactivated our classical Libertine-Tex-package. It can be found here: -http://linuxlibertine.sourceforge.net/latex/ - -Of course, you are also free to use the innovative Tex-Variant “XeTex”, which supports Libertine directly plus its wonderful OpenType-features. You’ll find information about the use of Libertine with XeTex and the advantages of OpenType-support on our Website, here: - -http://linuxlibertine.sf.net diff --git a/fonts/Linux-Libertine/ToDo.txt b/fonts/Linux-Libertine/ToDo.txt deleted file mode 100644 index 47e5e76..0000000 --- a/fonts/Linux-Libertine/ToDo.txt +++ /dev/null @@ -1,4 +0,0 @@ -Tasks that need to be done. You are welcome to contribute: - -Liberine Bold and BoldItalic: Inferiors und Superiors are not yet all emboldened. Use uni2099 as reference. -Greek and Cyrillic glyph maps aren't completely emboldenend, yet \ No newline at end of file diff --git a/fonts/hk-grotesk/HKGrotesk-Bold.otf b/fonts/hk-grotesk/HKGrotesk-Bold.otf deleted file mode 100755 index 9a07d0a..0000000 Binary files a/fonts/hk-grotesk/HKGrotesk-Bold.otf and /dev/null differ diff --git a/fonts/hk-grotesk/HKGrotesk-Light.otf b/fonts/hk-grotesk/HKGrotesk-Light.otf deleted file mode 100755 index 71d74b4..0000000 Binary files a/fonts/hk-grotesk/HKGrotesk-Light.otf and /dev/null differ diff --git a/fonts/hk-grotesk/HKGrotesk-Medium.otf b/fonts/hk-grotesk/HKGrotesk-Medium.otf deleted file mode 100755 index 5071d53..0000000 Binary files a/fonts/hk-grotesk/HKGrotesk-Medium.otf and /dev/null differ diff --git a/fonts/hk-grotesk/OFL-FAQ.txt b/fonts/hk-grotesk/OFL-FAQ.txt deleted file mode 100755 index 9fa14c6..0000000 --- a/fonts/hk-grotesk/OFL-FAQ.txt +++ /dev/null @@ -1,429 +0,0 @@ -Copyright (c) 2015, Alfredo Marco Pradil (), with Reserved Font Name HK Grotesk. - -OFL FAQ - Frequently Asked Questions about the SIL Open Font License (OFL) -Version 1.1-update4 - Sept 2014 -(See http://scripts.sil.org/OFL for updates) - - -CONTENTS OF THIS FAQ -1 USING AND DISTRIBUTING FONTS LICENSED UNDER THE OFL -2 USING OFL FONTS FOR WEB PAGES AND ONLINE WEB FONT SERVICES -3 MODIFYING OFL-LICENSED FONTS -4 LICENSING YOUR ORIGINAL FONTS UNDER THE OFL -5 CHOOSING RESERVED FONT NAMES -6 ABOUT THE FONTLOG -7 MAKING CONTRIBUTIONS TO OFL PROJECTS -8 ABOUT THE LICENSE ITSELF -9 ABOUT SIL INTERNATIONAL -APPENDIX A - FONTLOG EXAMPLE - -1 USING AND DISTRIBUTING FONTS LICENSED UNDER THE OFL - -1.1 Can I use the fonts for a book or other print publication, to create logos or other graphics or even to manufacture objects based on their outlines? -Yes. You are very welcome to do so. Authors of fonts released under the OFL allow you to use their font software as such for any kind of design work. No additional license or permission is required, unlike with some other licenses. Some examples of these uses are: logos, posters, business cards, stationery, video titling, signage, t-shirts, personalised fabric, 3D-printed/laser-cut shapes, sculptures, rubber stamps, cookie cutters and lead type. - -1.1.1 Does that restrict the license or distribution of that artwork? -No. You remain the author and copyright holder of that newly derived graphic or object. You are simply using an open font in the design process. It is only when you redistribute, bundle or modify the font itself that other conditions of the license have to be respected (see below for more details). - -1.1.2 Is any kind of acknowledgement required? -No. Font authors may appreciate being mentioned in your artwork's acknowledgements alongside the name of the font, possibly with a link to their website, but that is not required. - -1.2 Can the fonts be included with Free/Libre and Open Source Software collections such as GNU/Linux and BSD distributions and repositories? -Yes! Fonts licensed under the OFL can be freely included alongside other software under FLOSS (Free/Libre and Open Source Software) licenses. Since fonts are typically aggregated with, not merged into, existing software, there is little need to be concerned about incompatibility with existing software licenses. You may also repackage the fonts and the accompanying components in a .rpm or .deb package (or other similar package formats or installers) and include them in distribution CD/DVDs and online repositories. (Also see section 5.9 about rebuilding from source.) - -1.3 I want to distribute the fonts with my program. Does this mean my program also has to be Free/Libre and Open Source Software? -No. Only the portions based on the Font Software are required to be released under the OFL. The intent of the license is to allow aggregation or bundling with software under restricted licensing as well. - -1.4 Can I sell a software package that includes these fonts? -Yes, you can do this with both the Original Version and a Modified Version of the fonts. Examples of bundling made possible by the OFL would include: word processors, design and publishing applications, training and educational software, games and entertainment software, mobile device applications, etc. - -1.5 Can I include the fonts on a CD of freeware or commercial fonts? -Yes, as long some other font or software is also on the disk, so the OFL font is not sold by itself. - -1.6 Why won't the OFL let me sell the fonts alone? -The intent is to keep people from making money by simply redistributing the fonts. The only people who ought to profit directly from the fonts should be the original authors, and those authors have kindly given up potential direct income to distribute their fonts under the OFL. Please honour and respect their contribution! - -1.7 What about sharing OFL fonts with friends on a CD, DVD or USB stick? -You are very welcome to share open fonts with friends, family and colleagues through removable media. Just remember to include the full font package, including any copyright notices and licensing information as available in OFL.txt. In the case where you sell the font, it has to come bundled with software. - -1.8 Can I host the fonts on a web site for others to use? -Yes, as long as you make the full font package available. In most cases it may be best to point users to the main site that distributes the Original Version so they always get the most recent stable and complete version. See also discussion of web fonts in Section 2. - -1.9 Can I host the fonts on a server for use over our internal network? -Yes. If the fonts are transferred from the server to the client computer by means that allow them to be used even if the computer is no longer attached to the network, the full package (copyright notices, licensing information, etc.) should be included. - -1.10 Does the full OFL license text always need to accompany the font? -The only situation in which an OFL font can be distributed without the text of the OFL (either in a separate file or in font metadata), is when a font is embedded in a document or bundled within a program. In the case of metadata included within a font, it is legally sufficient to include only a link to the text of the OFL on http://scripts.sil.org/OFL, but we strongly recommend against this. Most modern font formats include metadata fields that will accept the full OFL text, and full inclusion increases the likelihood that users will understand and properly apply the license. - -1.11 What do you mean by 'embedding'? How does that differ from other means of distribution? -By 'embedding' we mean inclusion of the font in a document or file in a way that makes extraction (and redistribution) difficult or clearly discouraged. In many cases the names of embedded fonts might also not be obvious to those reading the document, the font data format might be altered, and only a subset of the font - only the glyphs required for the text - might be included. Any other means of delivering a font to another person is considered 'distribution', and needs to be accompanied by any copyright notices and licensing information available in OFL.txt. - -1.12 So can I embed OFL fonts in my document? -Yes, either in full or a subset. The restrictions regarding font modification and redistribution do not apply, as the font is not intended for use outside the document. - -1.13 Does embedding alter the license of the document itself? -No. Referencing or embedding an OFL font in any document does not change the license of the document itself. The requirement for fonts to remain under the OFL does not apply to any document created using the fonts and their derivatives. Similarly, creating any kind of graphic using a font under OFL does not make the resulting artwork subject to the OFL. - -1.14 If OFL fonts are extracted from a document in which they are embedded (such as a PDF file), what can be done with them? Is this a risk to author(s)? -The few utilities that can extract fonts embedded in a PDF will typically output limited amounts of outlines - not a complete font. To create a working font from this method is much more difficult and time consuming than finding the source of the original OFL font. So there is little chance that an OFL font would be extracted and redistributed inappropriately through this method. Even so, copyright laws address any misrepresentation of authorship. All Font Software released under the OFL and marked as such by the author(s) is intended to remain under this license regardless of the distribution method, and cannot be redistributed under any other license. We strongly discourage any font extraction - we recommend directly using the font sources instead - but if you extract font outlines from a document, please be considerate: respect the work of the author(s) and the licensing model. - -1.15 What about distributing fonts with a document? Within a compressed folder structure? Is it distribution, bundling or embedding? -Certain document formats may allow the inclusion of an unmodified font within their file structure which may consist of a compressed folder containing the various resources forming the document (such as pictures and thumbnails). Including fonts within such a structure is understood as being different from embedding but rather similar to bundling (or mere aggregation) which the license explicitly allows. In this case the font is conveyed unchanged whereas embedding a font usually transforms it from the original format. The OFL does not allow anyone to extract the font from such a structure to then redistribute it under another license. The explicit permission to redistribute and embed does not cancel the requirement for the Font Software to remain under the license chosen by its author(s). Even if the font travels inside the document as one of its assets, it should not lose its authorship information and licensing. - -1.16 What about ebooks shipping with open fonts? -The requirements differ depending on whether the fonts are linked, embedded or distributed (bundled or aggregated). Some ebook formats use web technologies to do font linking via @font-face, others are designed for font embedding, some use fonts distributed with the document or reading software, and a few rely solely on the fonts already present on the target system. The license requirements depend on the type of inclusion as discussed in 1.15. - -1.17 Can Font Software released under the OFL be subject to URL-based access restrictions methods or DRM (Digital Rights Management) mechanisms? -Yes, but these issues are out-of-scope for the OFL. The license itself neither encourages their use nor prohibits them since such mechanisms are not implemented in the components of the Font Software but through external software. Such restrictions are put in place for many different purposes corresponding to various usage scenarios. One common example is to limit potentially dangerous cross-site scripting attacks. However, in the spirit of libre/open fonts and unrestricted writing systems, we strongly encourage open sharing and reuse of OFL fonts, and the establishment of an environment where such restrictions are unnecessary. Note that whether you wish to use such mechanisms or you prefer not to, you must still abide by the rules set forth by the OFL when using fonts released by their authors under this license. Derivative fonts must be licensed under the OFL, even if they are part of a service for which you charge fees and/or for which access to source code is restricted. You may not sell the fonts on their own - they must be part of a larger software package, bundle or subscription plan. For example, even if the OFL font is distributed in a software package or via an online service using a DRM mechanism, the user would still have the right to extract that font, use, study, modify and redistribute it under the OFL. - -1.18 I've come across a font released under the OFL. How can I easily get more information about the Original Version? How can I know where it stands compared to the Original Version or other Modified Versions? -Consult the copyright statement(s) in the license for ways to contact the original authors. Consult the FONTLOG (see section 6 for more details and examples) for information on how the font differs from the Original Version, and get in touch with the various contributors via the information in the acknowledgement section. Please consider using the Original Versions of the fonts whenever possible. - -1.19 What do you mean in condition 4 of the OFL's permissions and conditions? Can you provide examples of abusive promotion / endorsement / advertisement vs. normal acknowledgement? -The intent is that the goodwill and reputation of the author(s) should not be used in a way that makes it sound like the original author(s) endorse or approve of a specific Modified Version or software bundle. For example, it would not be right to advertise a word processor by naming the author(s) in a listing of software features, or to promote a Modified Version on a web site by saying "designed by ...". However, it would be appropriate to acknowledge the author(s) if your software package has a list of people who deserve thanks. We realize that this can seem to be a grey area, but the standard used to judge an acknowledgement is that if the acknowledgement benefits the author(s) it is allowed, but if it primarily benefits other parties, or could reflect poorly on the author(s), then it is not. - -1.20 I'm writing a small app for mobile platforms, do I need to include the whole package? -If you bundle a font under the OFL with your mobile app you must comply with the terms of the license. At a minimum you must include the copyright statement, the license notice and the license text. A mention of this information in your About box or Changelog, with a link to where the font package is from, is good practice, and the extra space needed to carry these items is very small. You do not, however, need to include the full contents of the font package - only the fonts you use and the copyright and license that apply to them. For example, if you only use the regular weight in your app, you do not need to include the italic and bold versions. - -1.21 What about including OFL fonts by default in my firmware or dedicated operating system? -Many such systems are restricted and turned into appliances so that users cannot study or modify them. Using open fonts to increase quality and language coverage is a great idea, but you need to be aware that if there is a way for users to extract fonts you cannot legally prevent them from doing that. The fonts themselves, including any changes you make to them, must be distributed under the OFL even if your firmware has a more restrictive license. If you do transform the fonts and change their formats when you include them in your firmware you must respect any names reserved by the font authors via the RFN mechanism and pick your own font name. Alternatively if you directly add a font under the OFL to the font folder of your firmware without modifying or optimizing it you are simply bundling the font like with any other software collection, and do not need to make any further changes. - -1.22 Can I make and publish CMS themes or templates that use OFL fonts? Can I include the fonts themselves in the themes or templates? Can I sell the whole package? -Yes, you are very welcome to integrate open fonts into themes and templates for your preferred CMS and make them more widely available. Remember that you can only sell the fonts and your CMS add-on as part of a software bundle. (See 1.4 for details and examples about selling bundles). - -1.23 Can OFL fonts be included in services that deliver fonts to the desktop from remote repositories? Even if they contain both OFL and non-OFL fonts? -Yes. Some foundries have set up services to deliver fonts to subscribers directly to desktops from their online repositories; similarly, plugins are available to preview and use fonts directly in your design tool or publishing suite. These services may mix open and restricted fonts in the same channel, however they should make a clear distinction between them to users. These services should also not hinder users (such as through DRM or obfuscation mechanisms) from extracting and using the OFL fonts in other environments, or continuing to use OFL fonts after subscription terms have ended, as those uses are specifically allowed by the OFL. - -1.24 Can services that provide or distribute OFL fonts restrict my use of them? -No. The terms of use of such services cannot replace or restrict the terms of the OFL, as that would be the same as distributing the fonts under a different license, which is not allowed. You are still entitled to use, modify and redistribute them as the original authors have intended outside of the sole control of that particular distribution channel. Note, however, that the fonts provided by these services may differ from the Original Versions. - - -2 USING OFL FONTS FOR WEBPAGES AND ONLINE WEB FONT SERVICES - -NOTE: This section often refers to a separate paper on 'Web Fonts & RFNs'. This is available at http://scripts.sil.org/OFL_web_fonts_and_RFNs - -2.1 Can I make webpages using these fonts? -Yes! Go ahead! Using CSS (Cascading Style Sheets) is recommended. Your three best options are: -- referring directly in your stylesheet to open fonts which may be available on the user's system -- providing links to download the full package of the font - either from your own website or from elsewhere - so users can install it themselves -- using @font-face to distribute the font directly to browsers. This is recommended and explicitly allowed by the licensing model because it is distribution. The font file itself is distributed with other components of the webpage. It is not embedded in the webpage but referenced through a web address which will cause the browser to retrieve and use the corresponding font to render the webpage (see 1.11 and 1.15 for details related to embedding fonts into documents). As you take advantage of the @font-face cross-platform standard, be aware that web fonts are often tuned for a web environment and not intended for installation and use outside a browser. The reasons in favour of using web fonts are to allow design of dynamic text elements instead of static graphics, to make it easier for content to be localized and translated, indexed and searched, and all this with cross-platform open standards without depending on restricted extensions or plugins. You should check the CSS cascade (the order in which fonts are being called or delivered to your users) when testing. - -2.2 Can I make and use WOFF (Web Open Font Format) versions of OFL fonts? -Yes, but you need to be careful. A change in font format normally is considered modification, and Reserved Font Names (RFNs) cannot be used. Because of the design of the WOFF format, however, it is possible to create a WOFF version that is not considered modification, and so would not require a name change. You are allowed to create, use and distribute a WOFF version of an OFL font without changing the font name, but only if: - -- the original font data remains unchanged except for WOFF compression, and -- WOFF-specific metadata is either omitted altogether or present and includes, unaltered, the contents of all equivalent metadata in the original font. - -If the original font data or metadata is changed, or the WOFF-specific metadata is incomplete, the font must be considered a Modified Version, the OFL restrictions would apply and the name of the font must be changed: any RFNs cannot be used and copyright notices and licensing information must be included and cannot be deleted or modified. You must come up with a unique name - we recommend one corresponding to your domain or your particular web application. Be aware that only the original author(s) can use RFNs. This is to prevent collisions between a derivative tuned to your audience and the original upstream version and so to reduce confusion. - -Please note that most WOFF conversion tools and online services do not meet the two requirements listed above, and so their output must be considered a Modified Version. So be very careful and check to be sure that the tool or service you're using is compressing unchanged data and completely and accurately reflecting the original font metadata. - -2.3 What about other web font formats such as EOT/EOTLite/CWT/etc.? -In most cases these formats alter the original font data more than WOFF, and do not completely support appropriate metadata, so their use must be considered modification and RFNs may not be used. However, there may be certain formats or usage scenarios that may allow the use of RFNs. See http://scripts.sil.org/OFL_web_fonts_and_RFNs - -2.4 Can I make OFL fonts available through web font online services? -Yes, you are welcome to include OFL fonts in online web font services as long as you properly meet all the conditions of the license. The origin and open status of the font should be clear among the other fonts you are hosting. Authorship, copyright notices and license information must be sufficiently visible to your users or subscribers so they know where the font comes from and the rights granted by the author(s). Make sure the font file contains the needed copyright notice(s) and licensing information in its metadata. Please double-check the accuracy of every field to prevent contradictory information. Other font formats, including EOT/EOTLite/CWT and superior alternatives like WOFF, already provide fields for this information. Remember that if you modify the font within your library or convert it to another format for any reason the OFL restrictions apply and you need to change the names accordingly. Please respect the author's wishes as expressed in the OFL and do not misrepresent original designers and their work. Don't lump quality open fonts together with dubious freeware or public domain fonts. Consider how you can best work with the original designers and foundries, support their efforts and generate goodwill that will benefit your service. (See 1.17 for details related to URL-based access restrictions methods or DRM mechanisms). - -2.5 Some web font formats and services provide ways of "optimizing" the font for a particular website or web application; is that allowed? -Yes, it is permitted, but remember that these optimized versions are Modified Versions and so must follow OFL requirements like appropriate renaming. Also you need to bear in mind the other important parameters beyond compression, speed and responsiveness: you need to consider the audience of your particular website or web application, as choosing some optimization parameters may turn out to be less than ideal for them. Subsetting by removing certain glyphs or features may seriously limit functionality of the font in various languages that your users expect. It may also introduce degradation of quality in the rendering or specific bugs on the various target platforms compared to the original font from upstream. In other words, remember that one person's optimized font may be another person's missing feature. Various advanced typographic features (OpenType, Graphite or AAT) are also available through CSS and may provide the desired effects without the need to modify the font. - -2.6 Is subsetting a web font considered modification? -Yes. Removing any parts of the font when delivering a web font to a browser, including unused glyphs and smart font code, is considered modification. This is permitted by the OFL but would not normally allow the use of RFNs. Some newer subsetting technologies may be able to subset in a way that allows users to effectively have access to the complete font, including smart font behaviour. See 2.8 and http://scripts.sil.org/OFL_web_fonts_and_RFNs - -2.7 Are there any situations in which a modified web font could use RFNs? -Yes. If a web font is optimized only in ways that preserve Functional Equivalence (see 2.8), then it may use RFNs, as it reasonably represents the Original Version and respects the intentions of the author(s) and the main purposes of the RFN mechanism (avoids collisions, protects authors, minimizes support, encourages derivatives). However this is technically very difficult and often impractical, so a much better scenario is for the web font service or provider to sign a separate agreement with the author(s) that allows the use of RFNs for Modified Versions. - -2.8 How do you know if an optimization to a web font preserves Functional Equivalence? -Functional Equivalence is described in full in the 'Web fonts and RFNs' paper at http://scripts.sil.org/OFL_web_fonts_and_RFNs, in general, an optimized font is deemed to be Functionally Equivalent (FE) to the Original Version if it: - -- Supports the same full character inventory. If a character can be properly displayed using the Original Version, then that same character, encoded correctly on a web page, will display properly. -- Provides the same smart font behavior. Any dynamic shaping behavior that works with the Original Version should work when optimized, unless the browser or environment does not support it. There does not need to be guaranteed support in the client, but there should be no forced degradation of smart font or shaping behavior, such as the removal or obfuscation of OpenType, Graphite or AAT tables. -- Presents text with no obvious degradation in visual quality. The lettershapes should be equally (or more) readable, within limits of the rendering platform. -- Preserves original author, project and license metadata. At a minimum, this should include: Copyright and authorship; The license as stated in the Original Version, whether that is the full text of the OFL or a link to the web version; Any RFN declarations; Information already present in the font or documentation that points back to the Original Version, such as a link to the project or the author's website. - -If an optimized font meets these requirements, and so is considered to be FE, then it's very likely that the original author would feel that the optimized font is a good and reasonable equivalent. If it falls short of any of these requirements, the optimized font does not reasonably represent the Original Version, and so should be considered to be a Modified Version. Like other Modified Versions, it would not be allowed to use any RFNs and you simply need to pick your own font name. - -2.9 Isn't use of web fonts another form of embedding? -No. Unlike embedded fonts in a PDF, web fonts are not an integrated part of the document itself. They are not specific to a single document and are often applied to thousands of documents around the world. The font data is not stored alongside the document data and often originates from a different location. The ease by which the web fonts used by a document may be identified and downloaded for desktop use demonstrates that they are philosophically and technically separate from the web pages that specify them. See http://scripts.sil.org/OFL_web_fonts_and_RFNs - -2.10 So would it be better to not use RFNs at all if you want your font to be distributed by a web fonts service? -No. Although the OFL does not require authors to use RFNs, the RFN mechanism is an important part of the OFL model and completely compatible with web font services. If that web font service modifies the fonts, then the best solution is to sign a separate agreement for the use of any RFNs. It is perfectly valid for an author to not declare any RFNs, but before they do so they need to fully understand the benefits they are giving up, and the overall negative effect of allowing many different versions bearing the same name to be widely distributed. As a result, we don't generally recommend it. - -2.11 What should an agreement for the use of RFNs say? Are there any examples? -There is no prescribed format for this agreement, as legal systems vary, and no recommended examples. Authors may wish to add specific clauses to further restrict use, require author review of Modified Versions, establish user support mechanisms or provide terms for ending the agreement. Such agreements are usually not public, and apply only to the main parties. However, it would be very beneficial for web font services to clearly state when they have established such agreements, so that the public understands clearly that their service is operating appropriately. - -See the separate paper on 'Web Fonts & RFNs' for in-depth discussion of issues related to the use of RFNs for web fonts. This is available at http://scripts.sil.org/OFL_web_fonts_and_RFNs - - -3 MODIFYING OFL-LICENSED FONTS - -3.1 Can I change the fonts? Are there any limitations to what things I can and cannot change? -You are allowed to change anything, as long as such changes do not violate the terms of the license. In other words, you are not allowed to remove the copyright statement(s) from the font, but you could put additional information into it that covers your contribution. See the placeholders in the OFL header template for recommendations on where to add your own statements. (Remember that, when authors have reserved names via the RFN mechanism, you need to change the internal names of the font to your own font name when making your modified version even if it is just a small change.) - -3.2 I have a font that needs a few extra glyphs - can I take them from an OFL licensed font and copy them into mine? -Yes, but if you distribute that font to others it must be under the OFL, and include the information mentioned in condition 2 of the license. - -3.3 Can I charge people for my additional work? In other words, if I add a bunch of special glyphs or OpenType/Graphite/AAT code, can I sell the enhanced font? -Not by itself. Derivative fonts must be released under the OFL and cannot be sold by themselves. It is permitted, however, to include them in a larger software package (such as text editors, office suites or operating systems), even if the larger package is sold. In that case, you are strongly encouraged, but not required, to also make that derived font easily and freely available outside of the larger package. - -3.4 Can I pay someone to enhance the fonts for my use and distribution? -Yes. This is a good way to fund the further development of the fonts. Keep in mind, however, that if the font is distributed to others it must be under the OFL. You won't be able to recover your investment by exclusively selling the font, but you will be making a valuable contribution to the community. Please remember how you have benefited from the contributions of others. - -3.5 I need to make substantial revisions to the font to make it work with my program. It will be a lot of work, and a big investment, and I want to be sure that it can only be distributed with my program. Can I restrict its use? -No. If you redistribute a Modified Version of the font it must be under the OFL. You may not restrict it in any way beyond what the OFL permits and requires. This is intended to ensure that all released improvements to the fonts become available to everyone. But you will likely get an edge over competitors by being the first to distribute a bundle with the enhancements. Again, please remember how you have benefited from the contributions of others. - -3.6 Do I have to make any derivative fonts (including extended source files, build scripts, documentation, etc.) publicly available? -No, but please consider sharing your improvements with others. You may find that you receive in return more than what you gave. - -3.7 If a trademark is claimed in the OFL font, does that trademark need to remain in modified fonts? -Yes. Any trademark notices must remain in any derivative fonts to respect trademark laws, but you may add any additional trademarks you claim, officially registered or not. For example if an OFL font called "Foo" contains a notice that "Foo is a trademark of Acme", then if you rename the font to "Bar" when creating a Modified Version, the new trademark notice could say "Foo is a trademark of Acme Inc. - Bar is a trademark of Roadrunner Technologies Ltd.". Trademarks work alongside the OFL and are not subject to the terms of the licensing agreement. The OFL does not grant any rights under trademark law. Bear in mind that trademark law varies from country to country and that there are no international trademark conventions as there are for copyright. You may need to significantly invest in registering and defending a trademark for it to remain valid in the countries you are interested in. This may be costly for an individual independent designer. - -3.8 If I commit changes to a font (or publish a branch in a DVCS) as part of a public open source software project, do I have to change the internal font names? -Only if there are declared RFNs. Making a public commit or publishing a public branch is effectively redistributing your modifications, so any change to the font will require that you do not use the RFNs. Even if there are no RFNs, it may be useful to change the name or add a suffix indicating that a particular version of the font is still in development and not released yet. This will clearly indicate to users and fellow designers that this particular font is not ready for release yet. See section 5 for more details. - - -4 LICENSING YOUR ORIGINAL FONTS UNDER THE OFL - -4.1 Can I use the SIL OFL for my own fonts? -Yes! We heartily encourage everyone to use the OFL to distribute their own original fonts. It is a carefully constructed license that allows great freedom along with enough artistic integrity protection for the work of the authors as well as clear rules for other contributors and those who redistribute the fonts. The licensing model is used successfully by various organisations, both for-profit and not-for-profit, to release fonts of varying levels of scope and complexity. - -4.2 What do I have to do to apply the OFL to my font? -If you want to release your fonts under the OFL, we recommend you do the following: - -4.2.1 Put your copyright and Reserved Font Names information at the beginning of the main OFL.txt file in place of the dedicated placeholders (marked with the <> characters). Include this file in your release package. - -4.2.2 Put your copyright and the OFL text with your chosen Reserved Font Name(s) into your font files (the copyright and license fields). A link to the OFL text on the OFL web site is an acceptable (but not recommended) alternative. Also add this information to any other components (build scripts, glyph databases, documentation, test files, etc). Accurate metadata in your font files is beneficial to you as an increasing number of applications are exposing this information to the user. For example, clickable links can bring users back to your website and let them know about other work you have done or services you provide. Depending on the format of your fonts and sources, you can use template human-readable headers or machine-readable metadata. You should also double-check that there is no conflicting metadata in the font itself contradicting the license, such as the fstype bits in the os2 table or fields in the name table. - -4.2.3 Write an initial FONTLOG.txt for your font and include it in the release package (see Section 6 and Appendix A for details including a template). - -4.2.4 Include the relevant practical documentation on the license by adding the current OFL-FAQ.txt file in your package. - -4.2.5 If you wish you can use the OFL graphics (http://scripts.sil.org/OFL_logo) on your website. - -4.3 Will you make my font OFL for me? -We won't do the work for you. We can, however, try to answer your questions, unfortunately we do not have the resources to review and check your font packages for correct use of the OFL. We recommend you turn to designers, foundries or consulting companies with experience in doing open font design to provide this service to you. - -4.4 Will you distribute my OFL font for me? -No, although if the font is of sufficient quality and general interest we may include a link to it on our partial list of OFL fonts on the OFL web site. You may wish to consider other open font catalogs or hosting services, such as the Unifont Font Guide (http://unifont.org/fontguide), The League of Movable Type (http://theleagueofmovabletype.com) or the Open Font Library (http://openfontlibrary.org/), which despite the name has no direct relationship to the OFL or SIL. We do not endorse any particular catalog or hosting service - it is your responsibility to determine if the service is right for you and if it treats authors with fairness. - -4.5 Why should I use the OFL for my fonts? -- to meet needs for fonts that can be modified to support lesser-known languages -- to provide a legal and clear way for people to respect your work but still use it (and reduce piracy) -- to involve others in your font project -- to enable your fonts to be expanded with new weights and improved writing system/language support -- to allow more technical font developers to add features to your design (such as OpenType, Graphite or AAT support) -- to renew the life of an old font lying on your hard drive with no business model -- to allow your font to be included in Libre Software operating systems like Ubuntu -- to give your font world status and wide, unrestricted distribution -- to educate students about quality typeface and font design -- to expand your test base and get more useful feedback -- to extend your reach to new markets when users see your metadata and go to your website -- to get your font more easily into one of the web font online services -- to attract attention for your commercial fonts -- to make money through web font services -- to make money by bundling fonts with applications -- to make money adjusting and extending existing open fonts -- to get a better chance that foundations/NGOs/charities/companies who commission fonts will pick you -- to be part of a sharing design and development community -- to give back and contribute to a growing body of font sources - - -5 CHOOSING RESERVED FONT NAMES - -5.1 What are Reserved Font Names? -These are font names, or portions of font names, that the author has chosen to reserve for use only with the Original Version of the font, or for Modified Version(s) created by the original author. - -5.2 Why can't I use the Reserved Font Names in my derivative font names? I'd like people to know where the design came from. -The best way to acknowledge the source of the design is to thank the original authors and any other contributors in the files that are distributed with your revised font (although no acknowledgement is required). The FONTLOG is a natural place to do this. Reserved Font Names ensure that the only fonts that have the original names are the unmodified Original Versions. This allows designers to maintain artistic integrity while allowing collaboration to happen. It eliminates potential confusion and name conflicts. When choosing a name, be creative and avoid names that reuse almost all the same letters in the same order or sound like the original. It will help everyone if Original Versions and Modified Versions can easily be distinguished from one another and from other derivatives. Any substitution and matching mechanism is outside the scope of the license. - -5.3 What do you mean by "primary name as presented to the user"? Are you referring to the font menu name? -Yes, this applies to the font menu name and other mechanisms that specify a font in a document. It would be fine, however, to keep a text reference to the original fonts in the description field, in your modified source file or in documentation provided alongside your derivative as long as no one could be confused that your modified source is the original. But you cannot use the Reserved Font Names in any way to identify the font to the user (unless the Copyright Holder(s) allow(s) it through a separate agreement). Users who install derivatives (Modified Versions) on their systems should not see any of the original Reserved Font Names in their font menus, for example. Again, this is to ensure that users are not confused and do not mistake one font for another and so expect features only another derivative or the Original Version can actually offer. - -5.4 Am I not allowed to use any part of the Reserved Font Names? -You may not use individual words from the Reserved Font Names, but you would be allowed to use parts of words, as long as you do not use any word from the Reserved Font Names entirely. We do not recommend using parts of words because of potential confusion, but it is allowed. For example, if "Foobar" was a Reserved Font Name, you would be allowed to use "Foo" or "bar", although we would not recommend it. Such an unfortunate choice would confuse the users of your fonts as well as make it harder for other designers to contribute. - -5.5 So what should I, as an author, identify as Reserved Font Names? -Original authors are encouraged to name their fonts using clear, distinct names, and only declare the unique parts of the name as Reserved Font Names. For example, the author of a font called "Foobar Sans" would declare "Foobar" as a Reserved Font Name, but not "Sans", as that is a common typographical term, and may be a useful word to use in a derivative font name. Reserved Font Names should also be single words for simplicity and legibility. A font called "Flowing River" should have Reserved Font Names "Flowing" and "River", not "Flowing River". You also need to be very careful about reserving font names which are already linked to trademarks (whether registered or not) which you do not own. - -5.6 Do I, as an author, have to identify any Reserved Font Names? -No. RFNs are optional and not required, but we encourage you to use them. This is primarily to avoid confusion between your work and Modified Versions. As an author you can release a font under the OFL and not declare any Reserved Font Names. There may be situations where you find that using no RFNs and letting your font be changed and modified - including any kind of modification - without having to change the original name is desirable. However you need to be fully aware of the consequences. There will be no direct way for end-users and other designers to distinguish your Original Version from many Modified Versions that may be created. You have to trust whoever is making the changes and the optimizations to not introduce problematic changes. The RFNs you choose for your own creation have value to you as an author because they allow you to maintain artistic integrity and keep some control over the distribution channel to your end-users. For discussion of RFNs and web fonts see section 2. - -5.7 Are any names (such as the main font name) reserved by default? -No. That is a change to the license as of version 1.1. If you want any names to be Reserved Font Names, they must be specified after the copyright statement(s). - -5.8 Is there any situation in which I can use Reserved Font Names for a Modified Version? -The Copyright Holder(s) can give certain trusted parties the right to use any of the Reserved Font Names through separate written agreements. For example, even if "Foobar" is a RFN, you could write up an agreement to give company "XYZ" the right to distribute a modified version with a name that includes "Foobar". This allows for freedom without confusion. The existence of such an agreement should be made as clear as possible to downstream users and designers in the distribution package and the relevant documentation. They need to know if they are a party to the agreement or not and what they are practically allowed to do or not even if all the details of the agreement are not public. - -5.9 Do font rebuilds require a name change? Do I have to change the name of the font when my packaging workflow includes a full rebuild from source? -Yes, all rebuilds which change the font data and the smart code are Modified Versions and the requirements of the OFL apply: you need to respect what the Author(s) have chosen in terms of Reserved Font Names. However if a package (or installer) is simply a wrapper or a compressed structure around the final font - leaving them intact on the inside - then no name change is required. Please get in touch with the author(s) and copyright holder(s) to inquire about the presence of font sources beyond the final font file(s) and the recommended build path. That build path may very well be non-trivial and hard to reproduce accurately by the maintainer. If a full font build path is made available by the upstream author(s) please be aware that any regressions and changes you may introduce when doing a rebuild for packaging purposes is your own responsibility as a package maintainer since you are effectively creating a separate branch. You should make it very clear to your users that your rebuilt version is not the canonical one from upstream. - -5.10 Can I add other Reserved Font Names when making a derivative font? -Yes. List your additional Reserved Font Names after your additional copyright statement, as indicated with example placeholders at the top of the OFL.txt file. Be sure you do not remove any existing RFNs but only add your own. RFN statements should be placed next to the copyright statement of the relevant author as indicated in the OFL.txt template to make them visible to designers wishing to make their separate version. - - -6 ABOUT THE FONTLOG - -6.1 What is this FONTLOG thing exactly? -It has three purposes: 1) to provide basic information on the font to users and other designers and developers, 2) to document changes that have been made to the font or accompanying files, either by the original authors or others, and 3) to provide a place to acknowledge authors and other contributors. Please use it! - -6.2 Is the FONTLOG required? -It is not a requirement of the license, but we strongly recommend you have one. - -6.3 Am I required to update the FONTLOG when making Modified Versions? -No, but users, designers and other developers might get very frustrated with you if you don't. People need to know how derivative fonts differ from the original, and how to take advantage of the changes, or build on them. There are utilities that can help create and maintain a FONTLOG, such as the FONTLOG support in FontForge. - -6.4 What should the FONTLOG look like? -It is typically a separate text file (FONTLOG.txt), but can take other formats. It commonly includes these four sections: - -- brief header describing the FONTLOG itself and name of the font family -- Basic Font Information - description of the font family, purpose and breadth -- ChangeLog - chronological listing of changes -- Acknowledgements - list of authors and contributors with contact information - -It could also include other sections, such as: where to find documentation, how to make contributions, information on contributing organizations, source code details, and a short design guide. See Appendix A for an example FONTLOG. - - -7 MAKING CONTRIBUTIONS TO OFL PROJECTS - -7.1 Can I contribute work to OFL projects? -In many cases, yes. It is common for OFL fonts to be developed by a team of people who welcome contributions from the wider community. Contact the original authors for specific information on how to participate in their projects. - -7.2 Why should I contribute my changes back to the original authors? -It would benefit many people if you contributed back in response to what you've received. Your contributions and improvements to the fonts and other components could be a tremendous help and would encourage others to contribute as well and 'give back'. You will then benefit from other people's contributions as well. Sometimes maintaining your own separate version takes more effort than merging back with the original. Be aware that any contributions, however, must be either your own original creation or work that you own, and you may be asked to affirm that clearly when you contribute. - -7.3 I've made some very nice improvements to the font. Will you consider adopting them and putting them into future Original Versions? -Most authors would be very happy to receive such contributions. Keep in mind that it is unlikely that they would want to incorporate major changes that would require additional work on their end. Any contributions would likely need to be made for all the fonts in a family and match the overall design and style. Authors are encouraged to include a guide to the design with the fonts. It would also help to have contributions submitted as patches or clearly marked changes - the use of smart source revision control systems like subversion, mercurial, git or bzr is a good idea. Please follow the recommendations given by the author(s) in terms of preferred source formats and configuration parameters for sending contributions. If this is not indicated in a FONTLOG or other documentation of the font, consider asking them directly. Examples of useful contributions are bug fixes, additional glyphs, stylistic alternates (and the smart font code to access them) or improved hinting. Keep in mind that some kinds of changes (esp. hinting) may be technically difficult to integrate. - -7.4 How can I financially support the development of OFL fonts? -It is likely that most authors of OFL fonts would accept financial contributions - contact them for instructions on how to do this. Such contributions would support future development. You can also pay for others to enhance the fonts and contribute the results back to the original authors for inclusion in the Original Version. - - -8 ABOUT THE LICENSE ITSELF - -8.1 I see that this is version 1.1 of the license. Will there be later changes? -Version 1.1 is the first minor revision of the OFL. We are confident that version 1.1 will meet most needs, but are open to future improvements. Any revisions would be for future font releases, and previously existing licenses would remain in effect. No retroactive changes are possible, although the Copyright Holder(s) can re-release the font under a revised OFL. All versions will be available on our web site: http://scripts.sil.org/OFL. - -8.2 Does this license restrict the rights of the Copyright Holder(s)? -No. The Copyright Holder(s) still retain(s) all the rights to their creation; they are only releasing a portion of it for use in a specific way. For example, the Copyright Holder(s) may choose to release a 'basic' version of their font under the OFL, but sell a restricted 'enhanced' version under a different license. They may also choose to release the same font under both the OFL and some other license. Only the Copyright Holder(s) can do this, and doing so does not change the terms of the OFL as it applies to that font. - -8.3 Is the OFL a contract or a license? -The OFL is a worldwide license based on international copyright agreements and conventions. It is not a contract and so does not require you to sign it to have legal validity. By using, modifying and redistributing components under the OFL you indicate that you accept the license. - -8.4 I really like the terms of the OFL, but want to change it a little. Am I allowed to take ideas and actual wording from the OFL and put them into my own custom license for distributing my fonts? -We strongly recommend against creating your very own unique open licensing model. Using a modified or derivative license will likely cut you off - along with the font(s) under that license - from the community of designers using the OFL, potentially expose you and your users to legal liabilities, and possibly put your work and rights at risk. The OFL went though a community and legal review process that took years of effort, and that review is only applicable to an unmodified OFL. The text of the OFL has been written by SIL (with review and consultation from the community) and is copyright (c) 2005-2013 SIL International. You may re-use the ideas and wording (in part, not in whole) in another non-proprietary license provided that you call your license by another unambiguous name, that you do not use the preamble, that you do not mention SIL and that you clearly present your license as different from the OFL so as not to cause confusion by being too similar to the original. If you feel the OFL does not meet your needs for an open license, please contact us. - -8.5 Can I translate the license and the FAQ into other languages? -SIL certainly recognises the need for people who are not familiar with English to be able to understand the OFL and its use. Making the license very clear and readable has been a key goal for the OFL, but we know that people understand their own language best. - -If you are an experienced translator, you are very welcome to translate the OFL and OFL-FAQ so that designers and users in your language community can understand the license better. But only the original English version of the license has legal value and has been approved by the community. Translations do not count as legal substitutes and should only serve as a way to explain the original license. SIL - as the author and steward of the license for the community at large - does not approve any translation of the OFL as legally valid because even small translation ambiguities could be abused and create problems. - -SIL gives permission to publish unofficial translations into other languages provided that they comply with the following guidelines: - -- Put the following disclaimer in both English and the target language stating clearly that the translation is unofficial: - -"This is an unofficial translation of the SIL Open Font License into . It was not published by SIL International, and does not legally state the distribution terms for fonts that use the OFL. A release under the OFL is only valid when using the original English text. However, we recognize that this unofficial translation will help users and designers not familiar with English to better understand and use the OFL. We encourage designers who consider releasing their creation under the OFL to read the OFL-FAQ in their own language if it is available. Please go to http://scripts.sil.org/OFL for the official version of the license and the accompanying OFL-FAQ." - -- Keep your unofficial translation current and update it at our request if needed, for example if there is any ambiguity which could lead to confusion. - -If you start such a unofficial translation effort of the OFL and OFL-FAQ please let us know. - -8.6 Does the OFL have an explicit expiration term? -No, the implicit intent of the OFL is that the permissions granted are perpetual and irrevocable. - - -9 ABOUT SIL INTERNATIONAL - -9.1 Who is SIL International and what do they do? -SIL serves language communities worldwide, building their capacity for sustainable language development, by means of research, translation, training and materials development. SIL makes its services available to all without regard to religious belief, political ideology, gender, race, or ethnic background. SIL's members and volunteers share a Christian commitment. - -9.2 What does this have to do with font licensing? -The ability to read, write, type and publish in one's own language is one of the most critical needs for millions of people around the world. This requires fonts that are widely available and support lesser-known languages. SIL develops - and encourages others to develop - a complete stack of writing systems implementation components available under open licenses. This open stack includes input methods, smart fonts, smart rendering libraries and smart applications. There has been a need for a common open license that is specifically applicable to fonts and related software (a crucial component of this stack), so SIL developed the SIL Open Font License with the help of the Free/Libre and Open Source Software community. - -9.3 How can I contact SIL? -Our main web site is: http://www.sil.org/ -Our site about complex scripts is: http://scripts.sil.org/ -Information about this license (and contact information) is at: http://scripts.sil.org/OFL - - -APPENDIX A - FONTLOG EXAMPLE - -Here is an example of the recommended format for a FONTLOG, although other formats are allowed. - ------ -FONTLOG for the GlobalFontFamily fonts - -This file provides detailed information on the GlobalFontFamily Font Software. This information should be distributed along with the GlobalFontFamily fonts and any derivative works. - -Basic Font Information - -GlobalFontFamily is a Unicode typeface family that supports all languages that use the Latin script and its variants, and could be expanded to support other scripts. - -NewWorldFontFamily is based on the GlobalFontFamily and also supports Greek, Hebrew, Cyrillic and Armenian. - -More specifically, this release supports the following Unicode ranges... -This release contains... -Documentation can be found at... -To contribute to the project... - -ChangeLog - -10 December 2010 (Fred Foobar) GlobalFontFamily-devel version 1.4 -- fix new build and testing system (bug #123456) - -1 August 2008 (Tom Parker) GlobalFontFamily version 1.2.1 -- Tweaked the smart font code (Branch merged with trunk version) -- Provided improved build and debugging environment for smart behaviours - -7 February 2007 (Pat Johnson) NewWorldFontFamily Version 1.3 -- Added Greek and Cyrillic glyphs - -7 March 2006 (Fred Foobar) NewWorldFontFamily Version 1.2 -- Tweaked contextual behaviours - -1 Feb 2005 (Jane Doe) NewWorldFontFamily Version 1.1 -- Improved build script performance and verbosity -- Extended the smart code documentation -- Corrected minor typos in the documentation -- Fixed position of combining inverted breve below (U+032F) -- Added OpenType/Graphite smart code for Armenian -- Added Armenian glyphs (U+0531 -> U+0587) -- Released as "NewWorldFontFamily" - -1 Jan 2005 (Joe Smith) GlobalFontFamily Version 1.0 -- Initial release - -Acknowledgements - -If you make modifications be sure to add your name (N), email (E), web-address (if you have one) (W) and description (D). This list is in alphabetical order. - -N: Jane Doe -E: jane@university.edu -W: http://art.university.edu/projects/fonts -D: Contributor - Armenian glyphs and code - -N: Fred Foobar -E: fred@foobar.org -W: http://foobar.org -D: Contributor - misc Graphite fixes - -N: Pat Johnson -E: pat@fontstudio.org -W: http://pat.fontstudio.org -D: Designer - Greek & Cyrillic glyphs based on Roman design - -N: Tom Parker -E: tom@company.com -W: http://www.company.com/tom/projects/fonts -D: Engineer - original smart font code - -N: Joe Smith -E: joe@fontstudio.org -W: http://joe.fontstudio.org -D: Designer - original Roman glyphs - -Fontstudio.org is an not-for-profit design group whose purpose is... -Foobar.org is a distributed community of developers... -Company.com is a small business who likes to support community designers... -University.edu is a renowned educational institution with a strong design department... ------ - diff --git a/output/output-1431728330.pdf b/output/output-1431728330.pdf deleted file mode 100644 index d434ca0..0000000 Binary files a/output/output-1431728330.pdf and /dev/null differ diff --git a/output/output-1431799689.pdf b/output/output-1431799689.pdf deleted file mode 100644 index 5426d12..0000000 Binary files a/output/output-1431799689.pdf and /dev/null differ diff --git a/output/output-1433887077-v4.pdf b/output/output-1433887077-v4.pdf deleted file mode 100644 index 5b0e51d..0000000 Binary files a/output/output-1433887077-v4.pdf and /dev/null differ diff --git a/output/output-1435269833.pdf b/output/output-1435269833.pdf deleted file mode 100644 index f098cbf..0000000 Binary files a/output/output-1435269833.pdf and /dev/null differ diff --git a/output/output-1435783018.pdf b/output/output-1435783018.pdf deleted file mode 100644 index 15ab8f2..0000000 Binary files a/output/output-1435783018.pdf and /dev/null differ diff --git a/output/output-1435785837.pdf b/output/output-1435785837.pdf deleted file mode 100644 index 5a9cf2e..0000000 Binary files a/output/output-1435785837.pdf and /dev/null differ diff --git a/output/output-1441489087-v5.pdf b/output/output-1441489087-v5.pdf deleted file mode 100644 index ff095f4..0000000 Binary files a/output/output-1441489087-v5.pdf and /dev/null differ diff --git a/output/output-1450119307.pdf b/output/output-1450119307.pdf deleted file mode 100644 index 2f05327..0000000 Binary files a/output/output-1450119307.pdf and /dev/null differ diff --git a/output/output-1455231122.pdf b/output/output-1455231122.pdf deleted file mode 100644 index 35df199..0000000 Binary files a/output/output-1455231122.pdf and /dev/null differ diff --git a/output/output-1455309164.pdf b/output/output-1455309164.pdf deleted file mode 100644 index dbc4683..0000000 Binary files a/output/output-1455309164.pdf and /dev/null differ diff --git a/output/output-1455405624-v6.pdf b/output/output-1455405624-v6.pdf deleted file mode 100644 index 40e37c9..0000000 Binary files a/output/output-1455405624-v6.pdf and /dev/null differ diff --git a/output/output-1455818691-v7.pdf b/output/output-1455818691-v7.pdf deleted file mode 100644 index cfce2b4..0000000 Binary files a/output/output-1455818691-v7.pdf and /dev/null differ diff --git a/output/output-1459619886.pdf b/output/output-1459619886.pdf deleted file mode 100644 index ffc93af..0000000 Binary files a/output/output-1459619886.pdf and /dev/null differ diff --git a/output/output-1459620032.pdf b/output/output-1459620032.pdf deleted file mode 100644 index c780a0b..0000000 Binary files a/output/output-1459620032.pdf and /dev/null differ diff --git a/output/output-1459620270.pdf b/output/output-1459620270.pdf deleted file mode 100644 index 01b6d98..0000000 Binary files a/output/output-1459620270.pdf and /dev/null differ diff --git a/output/output-1459621030-hk-grotesk.pdf b/output/output-1459621030-hk-grotesk.pdf deleted file mode 100644 index e06117f..0000000 Binary files a/output/output-1459621030-hk-grotesk.pdf and /dev/null differ diff --git a/output/output-1459627134-roboto.pdf b/output/output-1459627134-roboto.pdf deleted file mode 100644 index 63e0ca5..0000000 Binary files a/output/output-1459627134-roboto.pdf and /dev/null differ diff --git a/output/output-1459632510.pdf b/output/output-1459632510.pdf deleted file mode 100644 index 78abeef..0000000 Binary files a/output/output-1459632510.pdf and /dev/null differ diff --git a/output/output-1459632685.pdf b/output/output-1459632685.pdf deleted file mode 100644 index 4f44c12..0000000 Binary files a/output/output-1459632685.pdf and /dev/null differ diff --git a/output/output-1459892345.pdf b/output/output-1459892345.pdf deleted file mode 100644 index ac5e8e9..0000000 Binary files a/output/output-1459892345.pdf and /dev/null differ diff --git a/output/output-archivo.pdf b/output/output-archivo.pdf deleted file mode 100644 index 510e288..0000000 Binary files a/output/output-archivo.pdf and /dev/null differ diff --git a/output/output-breite.pdf b/output/output-breite.pdf deleted file mode 100644 index 5bcef33..0000000 Binary files a/output/output-breite.pdf and /dev/null differ diff --git a/output/output-cardo.pdf b/output/output-cardo.pdf deleted file mode 100644 index 7b009f7..0000000 Binary files a/output/output-cardo.pdf and /dev/null differ diff --git a/output/output-inconsesi.pdf b/output/output-inconsesi.pdf deleted file mode 100644 index 8d51701..0000000 Binary files a/output/output-inconsesi.pdf and /dev/null differ diff --git a/output/output-limousine.pdf b/output/output-limousine.pdf deleted file mode 100644 index 29ab040..0000000 Binary files a/output/output-limousine.pdf and /dev/null differ diff --git a/output/output-sophia-nubian.pdf b/output/output-sophia-nubian.pdf deleted file mode 100644 index 4fdc103..0000000 Binary files a/output/output-sophia-nubian.pdf and /dev/null differ diff --git a/output/output-verdana.pdf b/output/output-verdana.pdf deleted file mode 100644 index b7f03e5..0000000 Binary files a/output/output-verdana.pdf and /dev/null differ diff --git a/scripts/build.sh b/scripts/build.sh index 0efbc07..429d450 100644 --- a/scripts/build.sh +++ b/scripts/build.sh @@ -11,9 +11,16 @@ INPUT="../content/meta.txt ../content/manifestos/*.*" ## ../content/intro.txt TEMP="../temp/newfile.txt" TEMP2="../temp/newfile2.txt" -TIMESTAMP=$(date +"%s") -OUTPUT="../output/output-"$TIMESTAMP".pdf" +##TIMESTAMP=$(date +"%s") +TIMESTAMP=$(date --utc +%Y%m%d_%H%M%SZ) +OUTPUT="../output/Manifestos_for_the_Internet_Age-"$TIMESTAMP".pdf" +if [ ! -d ~/.fonts ]; then + mkdir ~/.fonts +fi + +##cp ../fonts/*.otf ~/.fonts/ +##fc-cache -fv ## 2: AWK Method @@ -54,18 +61,16 @@ END { ## Monoid - by Andreas Larsen ## HK Grotesk - by Alfredo Marco Pradil, Hanken Design Co. -pandoc -f markdown -o $OUTPUT --template=../templates/customV2 $TEMP --latex-engine=xelatex \ +pandoc -f markdown --template=../templates/customV2 $TEMP --latex-engine=xelatex \ --variable mainfont="HKGrotesk-Regular" \ --variable boldfont="LinLibertineOB" \ --variable italicfont="LinLibertineOI" \ - --variable bolditalicfont="LinLibertineOBI" \ - --variable sansfont=Futura \ - --variable monofont=Inconsesi \ --variable fontsize=9pt \ --variable urlcolor=black \ --variable linkcolor=black \ --variable documentclass=book \ --toc --toc-depth=1 \ - --include-before-body=../content/intro.txt + --include-before-body=../content/intro.txt \ + -o $OUTPUT ## End of file