diff --git a/common/schemas/kps/README.md b/common/schemas/kps/README.md
index aea03f2a5b9..87ca0a30d01 100644
--- a/common/schemas/kps/README.md
+++ b/common/schemas/kps/README.md
@@ -2,6 +2,19 @@
Master version: https://github.com/keymanapp/api.keyman.com/blob/master/schemas/kps/17.0/kps.xsd
+See https://github.com/keymanapp/
+
+## 2024-11-29 18.0
+* Version 18.0 adds:
+ - Files/File/Source - a remote source for the file, or 'local'
+* Version 18.0 modifies:
+ - Files/File/Name - may be either a local file, relative to .kps (or absolute
+ path, not recommended) or a permanent URL on github.com
+* Version 18.0 deprecates (for later removal):
+ - Files/File/CopyLocation
+ - Files/File/Description
+ - Files/File/FileType
+
## 2023-10-19 17.0
* Version 17.0 adds:
- LicenseFile - a .md file, usually named LICENSE.md
@@ -10,7 +23,7 @@ Master version: https://github.com/keymanapp/api.keyman.com/blob/master/schemas/
- RelatedPackages - a list of other packages which relate to this one, or are deprecated by it
- Keyboards/Keyboard/Examples - a list of typing examples for the keyboard
- Keyboarsd/Keyboard/WebOSKFonts - a list of font filenames (not necessarily in package) suitable for rendering the on screen keyboard
- - Keyboarsd/Keyboard/WebDisplayFonts - a list of font filenames (not necessarily in package) suitable for use with the keyboard
+ - Keyboards/Keyboard/WebDisplayFonts - a list of font filenames (not necessarily in package) suitable for use with the keyboard
* Version 17.0 removes:
- LexicalModels/LexicalModel/Version - version information is not stored in the models, but only in the package metadata (was unused)
diff --git a/common/schemas/kps/kps.xsd b/common/schemas/kps/kps.xsd
index 292f0c8fc6a..c722324b766 100644
--- a/common/schemas/kps/kps.xsd
+++ b/common/schemas/kps/kps.xsd
@@ -6,7 +6,10 @@
Supports KPS files for Keyman Developer 7+
- Expects FileVersion 7.0
+ Expects FileVersion:
+ - 7.0 - minimum version
+ - 12.0 - supports lexical models, kmp.json
+ - 18.0 - supports Files/File/Source
-->
@@ -89,9 +92,10 @@
-
-
-
+
+
+
+
diff --git a/developer/docs/help/reference/file-types/kps.md b/developer/docs/help/reference/file-types/kps.md
index ef4095d9aee..26410259d48 100644
--- a/developer/docs/help/reference/file-types/kps.md
+++ b/developer/docs/help/reference/file-types/kps.md
@@ -17,11 +17,172 @@ Details:
Distributed with keyboard:
: No. This is a development file and should not be distributed.
-## File format
+# File format
+## Schema
+
+The schema for .kps is documented at:
+https://github.com/keymanapp/keyman/tree/master/common/schemas/kps
+
+## Strings
The optional `` section of the file can be included to
customise the text in the bootstrap installer. The default strings are
found in the file:
[strings.xml](https://github.com/keymanapp/keyman/blob/stable-14.0/windows/src/desktop/setup/locale/en/strings.xml).
You can add your own strings for a given package which are used when
compiling as a bundled installer.
+
+
+## File.Name
+
+The `Name` element may be either a local filename, or a GitHub raw permanent
+URL, conforming to the pattern:
+
+```
+https://github.com/{owner}/{repo}/raw/{commit}/[path/]{filename}
+```
+
+## File.Source
+
+The `
+
+
For more details on the Khmer Angkor Keyboard, please find the documentation included in this package.
+ With the users' pitfall in typing Khmer words in mind, Khmer Angkor focuses on the unification of the character orders and spelling rules. These make Khmer Angkor uniquely different from any other keyboards. Khmer Angkor's keyboard layouts were adopted from NiDA keyboard which is widely used at the present.
+
+
+
+
diff --git a/developer/src/kmc-keyboard-info/test/fixtures/no-kmp/source/splash.gif b/developer/src/kmc-keyboard-info/test/fixtures/no-kmp/source/splash.gif
new file mode 100644
index 00000000000..93b44e9d16e
Binary files /dev/null and b/developer/src/kmc-keyboard-info/test/fixtures/no-kmp/source/splash.gif differ
diff --git a/developer/src/kmc-keyboard-info/test/fixtures/no-kmp/source/welcome/welcome.htm b/developer/src/kmc-keyboard-info/test/fixtures/no-kmp/source/welcome/welcome.htm
new file mode 100644
index 00000000000..124d9d20e66
--- /dev/null
+++ b/developer/src/kmc-keyboard-info/test/fixtures/no-kmp/source/welcome/welcome.htm
@@ -0,0 +1,54 @@
+
+
+
+ Khmer Angkor Keyboard
+
+
+
Khmer Angkor Keyboard
+
+
+ Khmer Angkor Keyboard is an OpenSource. It is free and more than just a user you can also contribute to the betterment of the keyboard if you would like to.
+
+
+
Keyboards
+
+ With the users' pitfall in typing Khmer words in mind, Khmer Angkor focuses on the unification of the character orders and spelling rules. These make Khmer Angkor uniquely different from any other keyboards. Khmer Angkor's keyboard layouts were adopted from NiDA keyboard which is widely used at the present.
+ Here is the keyboard layout:
+
+
+
+
+
+
You can simply use Khmer Angkor as you would for any NiDA based keyboard. You may type a word in an order of how it is spelled, not how it appears to be, especially when the vowel is to the left of the consonant. For example, to type the word “តែ” which means ‘tea’, one should type the consonant first and then the vowel (i.e. press key “T” and then “Shift E”).
+
+
+
\ No newline at end of file
diff --git a/developer/src/kmc-keyboard-info/test/fixtures/no-license-in-kps-sources/LICENSE.md b/developer/src/kmc-keyboard-info/test/fixtures/no-license-in-kps-sources/LICENSE.md
new file mode 100644
index 00000000000..0a8c9054319
--- /dev/null
+++ b/developer/src/kmc-keyboard-info/test/fixtures/no-license-in-kps-sources/LICENSE.md
@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2015-2022 SIL International
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
diff --git a/developer/src/kmc-keyboard-info/test/fixtures/no-license-in-kps-sources/source/khmer_angkor.kps b/developer/src/kmc-keyboard-info/test/fixtures/no-license-in-kps-sources/source/khmer_angkor.kps
index fab90076b57..418a756e195 100644
--- a/developer/src/kmc-keyboard-info/test/fixtures/no-license-in-kps-sources/source/khmer_angkor.kps
+++ b/developer/src/kmc-keyboard-info/test/fixtures/no-license-in-kps-sources/source/khmer_angkor.kps
@@ -41,24 +41,12 @@
0.js
-
- ..\build\khmer_angkor.kvk
- File khmer_angkor.kvk
- 0
- .kvk
- ..\build\khmer_angkor.kmxKeyboard Khmer Angkor0.kmx
-
- welcome\keyboard_layout.png
- File keyboard_layout.png
- 0
- .png
- welcome\welcome.htmFile welcome.htm
@@ -66,59 +54,29 @@
.htm
- ..\shared\fonts\khmer\mondulkiri\FONTLOG.txt
+ ..\..\shared\fonts\khmer\mondulkiri\FONTLOG.txtFile FONTLOG.txt0.txt
- ..\shared\fonts\khmer\mondulkiri\Mondulkiri-B.ttf
- Font Khmer Mondulkiri Bold
- 0
- .ttf
-
-
- ..\shared\fonts\khmer\mondulkiri\Mondulkiri-BI.ttf
- Font Khmer Mondulkiri Bold Italic
- 0
- .ttf
-
-
- ..\shared\fonts\khmer\mondulkiri\Mondulkiri-I.ttf
- Font Khmer Mondulkiri Italic
- 0
- .ttf
-
-
- ..\shared\fonts\khmer\mondulkiri\Mondulkiri-R.ttf
+ ..\..\shared\fonts\khmer\mondulkiri\Mondulkiri-R.ttfFont Khmer Mondulkiri0.ttf
- ..\shared\fonts\khmer\mondulkiri\OFL.txt
+ ..\..\shared\fonts\khmer\mondulkiri\OFL.txtFile OFL.txt0.txt
- ..\shared\fonts\khmer\mondulkiri\OFL-FAQ.txt
+ ..\..\shared\fonts\khmer\mondulkiri\OFL-FAQ.txtFile OFL-FAQ.txt0.txt
-
- welcome\KAK_Documentation_EN.pdf
- File KAK_Documentation_EN.pdf
- 0
- .pdf
-
-
- welcome\KAK_Documentation_KH.pdf
- File KAK_Documentation_KH.pdf
- 0
- .pdf
- readme.htmFile readme.htm
@@ -126,13 +84,7 @@
.htm
- welcome\image002.png
- File image002.png
- 0
- .png
-
-
- ..\shared\fonts\khmer\busrakbd\khmer_busra_kbd.ttf
+ ..\..\shared\fonts\khmer\busrakbd\khmer_busra_kbd.ttfFont KhmerBusraKbd0.ttf
@@ -149,8 +101,8 @@
Khmer Angkorkhmer_angkor1.3
- ..\shared\fonts\khmer\busrakbd\khmer_busra_kbd.ttf
- ..\shared\fonts\khmer\mondulkiri\Mondulkiri-R.ttf
+ ..\..\shared\fonts\khmer\busrakbd\khmer_busra_kbd.ttf
+ ..\..\shared\fonts\khmer\mondulkiri\Mondulkiri-R.ttfCentral Khmer (Khmer, Cambodia)
diff --git a/developer/src/kmc-keyboard-info/test/fixtures/no-license-in-kps-sources/source/readme.htm b/developer/src/kmc-keyboard-info/test/fixtures/no-license-in-kps-sources/source/readme.htm
new file mode 100644
index 00000000000..36a95d92482
--- /dev/null
+++ b/developer/src/kmc-keyboard-info/test/fixtures/no-license-in-kps-sources/source/readme.htm
@@ -0,0 +1,23 @@
+
+
+
+
+ Khmer Angkor Keyboard
+
+
+
+
+
Khmer Angkor Keyboard
+
+
+ With the users' pitfall in typing Khmer words in mind, Khmer Angkor focuses on the unification of the character orders and spelling rules. These make Khmer Angkor uniquely different from any other keyboards. Khmer Angkor's keyboard layouts were adopted from NiDA keyboard which is widely used at the present.
+
+
+
+
diff --git a/developer/src/kmc-keyboard-info/test/fixtures/no-license-in-kps-sources/source/splash.gif b/developer/src/kmc-keyboard-info/test/fixtures/no-license-in-kps-sources/source/splash.gif
new file mode 100644
index 00000000000..93b44e9d16e
Binary files /dev/null and b/developer/src/kmc-keyboard-info/test/fixtures/no-license-in-kps-sources/source/splash.gif differ
diff --git a/developer/src/kmc-keyboard-info/test/fixtures/no-license-in-kps-sources/source/welcome/welcome.htm b/developer/src/kmc-keyboard-info/test/fixtures/no-license-in-kps-sources/source/welcome/welcome.htm
new file mode 100644
index 00000000000..124d9d20e66
--- /dev/null
+++ b/developer/src/kmc-keyboard-info/test/fixtures/no-license-in-kps-sources/source/welcome/welcome.htm
@@ -0,0 +1,54 @@
+
+
+
+ Khmer Angkor Keyboard
+
+
+
Khmer Angkor Keyboard
+
+
+ Khmer Angkor Keyboard is an OpenSource. It is free and more than just a user you can also contribute to the betterment of the keyboard if you would like to.
+
+
+
Keyboards
+
+ With the users' pitfall in typing Khmer words in mind, Khmer Angkor focuses on the unification of the character orders and spelling rules. These make Khmer Angkor uniquely different from any other keyboards. Khmer Angkor's keyboard layouts were adopted from NiDA keyboard which is widely used at the present.
+ Here is the keyboard layout:
+
+
+
+
+
+
You can simply use Khmer Angkor as you would for any NiDA based keyboard. You may type a word in an order of how it is spelled, not how it appears to be, especially when the vowel is to the left of the consonant. For example, to type the word “តែ” which means ‘tea’, one should type the consonant first and then the vowel (i.e. press key “T” and then “Shift E”).
+ Ahom Star keyboard is designed for Ahom language which is a part of the Tai Kadai language family spoken by the Tai Ahom people of Assam and Northeast India.
+
+
+
+
diff --git a/developer/src/kmc-package/test/fixtures/kmp.json/shared/fonts/noto/Ahom/NotoSerifAhom-Regular.ttf b/developer/src/kmc-package/test/fixtures/kmp.json/shared/fonts/noto/Ahom/NotoSerifAhom-Regular.ttf
new file mode 100644
index 00000000000..44d0fcd7e6e
Binary files /dev/null and b/developer/src/kmc-package/test/fixtures/kmp.json/shared/fonts/noto/Ahom/NotoSerifAhom-Regular.ttf differ
diff --git a/developer/src/kmc-package/test/fixtures/kmp.json/welcome/desktop_layout_default.png b/developer/src/kmc-package/test/fixtures/kmp.json/welcome/desktop_layout_default.png
new file mode 100644
index 00000000000..7bfc8f25fe5
Binary files /dev/null and b/developer/src/kmc-package/test/fixtures/kmp.json/welcome/desktop_layout_default.png differ
diff --git a/developer/src/kmc-package/test/fixtures/kmp.json/welcome/desktop_layout_shift.png b/developer/src/kmc-package/test/fixtures/kmp.json/welcome/desktop_layout_shift.png
new file mode 100644
index 00000000000..cd3a4f4d7ad
Binary files /dev/null and b/developer/src/kmc-package/test/fixtures/kmp.json/welcome/desktop_layout_shift.png differ
diff --git a/developer/src/kmc-package/test/fixtures/kmp.json/welcome/phone_default.png b/developer/src/kmc-package/test/fixtures/kmp.json/welcome/phone_default.png
new file mode 100644
index 00000000000..f082682d894
Binary files /dev/null and b/developer/src/kmc-package/test/fixtures/kmp.json/welcome/phone_default.png differ
diff --git a/developer/src/kmc-package/test/fixtures/kmp.json/welcome/phone_longpress.png b/developer/src/kmc-package/test/fixtures/kmp.json/welcome/phone_longpress.png
new file mode 100644
index 00000000000..c7547a16137
Binary files /dev/null and b/developer/src/kmc-package/test/fixtures/kmp.json/welcome/phone_longpress.png differ
diff --git a/developer/src/kmc-package/test/fixtures/kmp.json/welcome/phone_numeric.png b/developer/src/kmc-package/test/fixtures/kmp.json/welcome/phone_numeric.png
new file mode 100644
index 00000000000..b855fd10b53
Binary files /dev/null and b/developer/src/kmc-package/test/fixtures/kmp.json/welcome/phone_numeric.png differ
diff --git a/developer/src/kmc-package/test/fixtures/kmp.json/welcome/phone_shift.png b/developer/src/kmc-package/test/fixtures/kmp.json/welcome/phone_shift.png
new file mode 100644
index 00000000000..b4e693688a9
Binary files /dev/null and b/developer/src/kmc-package/test/fixtures/kmp.json/welcome/phone_shift.png differ
diff --git a/developer/src/kmc-package/test/fixtures/kmp.json/welcome/welcome.htm b/developer/src/kmc-package/test/fixtures/kmp.json/welcome/welcome.htm
new file mode 100644
index 00000000000..33527da1308
--- /dev/null
+++ b/developer/src/kmc-package/test/fixtures/kmp.json/welcome/welcome.htm
@@ -0,0 +1,58 @@
+
+
+
+
+
+ Start Using Ahom Star
+
+
+
+
+
Start Using Ahom Star
+
+
+ Ahom Star keyboard is designed for Ahom language which is a part of the Tai Kadai language family spoken by the Tai Ahom people of Assam and Northeast India.
+
+
+
In order to type the arabic numeral (i.e. 1, 2, 3 etc), press the hash key ( Shift + 3 ) and then any corresponding Ahom numeral.
+
+
Keyboard Layout
+
+
Desktop
+
Default (unshifted)
+
+
Shift
+
+
+
Phone
+
Default (unshifted)
+
+
Shift
+
+
Numeric
+
+
+
Longpress
+
On mobile phone, keys with a little dot on the top right can be pressed and held for more keys.
+
+
+
\ No newline at end of file
diff --git a/developer/src/kmc-package/test/fixtures/kmp_2.0/khmer_angkor.kps b/developer/src/kmc-package/test/fixtures/kmp_2.0/khmer_angkor.kps
index 15867cd2fee..92556636441 100644
--- a/developer/src/kmc-package/test/fixtures/kmp_2.0/khmer_angkor.kps
+++ b/developer/src/kmc-package/test/fixtures/kmp_2.0/khmer_angkor.kps
@@ -63,25 +63,25 @@ Khmer Unicode keyboard layout based on the NiDA keyboard layout. Automatically c
.htm
- ..\shared\fonts\khmer\mondulkiri\FONTLOG.txt
+ .\shared\fonts\khmer\mondulkiri\FONTLOG.txtFile FONTLOG.txt0.txt
- ..\shared\fonts\khmer\mondulkiri\Mondulkiri-R.ttf
+ .\shared\fonts\khmer\mondulkiri\Mondulkiri-R.ttfFont Khmer Mondulkiri0.ttf
- ..\shared\fonts\khmer\mondulkiri\OFL.txt
+ .\shared\fonts\khmer\mondulkiri\OFL.txtFile OFL.txt0.txt
- ..\shared\fonts\khmer\mondulkiri\OFL-FAQ.txt
+ .\shared\fonts\khmer\mondulkiri\OFL-FAQ.txtFile OFL-FAQ.txt0.txt
@@ -111,7 +111,7 @@ Khmer Unicode keyboard layout based on the NiDA keyboard layout. Automatically c
.png
- ..\shared\fonts\khmer\busrakbd\khmer_busra_kbd.ttf
+ .\shared\fonts\khmer\busrakbd\khmer_busra_kbd.ttfFont KhmerBusraKbd0.ttf
@@ -138,8 +138,8 @@ Khmer Unicode keyboard layout based on the NiDA keyboard layout. Automatically c
Khmer Angkorkhmer_angkor1.3
- ..\shared\fonts\khmer\busrakbd\khmer_busra_kbd.ttf
- ..\shared\fonts\khmer\mondulkiri\Mondulkiri-R.ttf
+ .\shared\fonts\khmer\busrakbd\khmer_busra_kbd.ttf
+ .\shared\fonts\khmer\mondulkiri\Mondulkiri-R.ttfCentral Khmer (Khmer, Cambodia)
diff --git a/developer/src/kmc-package/test/fixtures/kmp_2.0/khmer_angkor.kvk b/developer/src/kmc-package/test/fixtures/kmp_2.0/khmer_angkor.kvk
new file mode 100644
index 00000000000..c6ad3369070
Binary files /dev/null and b/developer/src/kmc-package/test/fixtures/kmp_2.0/khmer_angkor.kvk differ
diff --git a/developer/src/kmc-package/test/fixtures/kmp_2.0/readme.htm b/developer/src/kmc-package/test/fixtures/kmp_2.0/readme.htm
new file mode 100644
index 00000000000..b7113f711c1
--- /dev/null
+++ b/developer/src/kmc-package/test/fixtures/kmp_2.0/readme.htm
@@ -0,0 +1,23 @@
+
+
+
+
+ Khmer Angkor Keyboard
+
+
+
+
+
Khmer Angkor Keyboard
+
+
+ With the users' pitfall in typing Khmer words in mind, Khmer Angkor focuses on the unification of the character orders and spelling rules. These make Khmer Angkor uniquely different from any other keyboards. Khmer Angkor's keyboard layouts were adopted from NiDA keyboard which is widely used at the present.
+
+
+
+
diff --git a/developer/src/kmc-package/test/fixtures/kmp_2.0/shared/fonts/khmer/busrakbd/khmer_busra_kbd.ttf b/developer/src/kmc-package/test/fixtures/kmp_2.0/shared/fonts/khmer/busrakbd/khmer_busra_kbd.ttf
new file mode 100644
index 00000000000..2169a408930
Binary files /dev/null and b/developer/src/kmc-package/test/fixtures/kmp_2.0/shared/fonts/khmer/busrakbd/khmer_busra_kbd.ttf differ
diff --git a/developer/src/kmc-package/test/fixtures/kmp_2.0/shared/fonts/khmer/mondulkiri/FONTLOG.txt b/developer/src/kmc-package/test/fixtures/kmp_2.0/shared/fonts/khmer/mondulkiri/FONTLOG.txt
new file mode 100644
index 00000000000..21acd963908
--- /dev/null
+++ b/developer/src/kmc-package/test/fixtures/kmp_2.0/shared/fonts/khmer/mondulkiri/FONTLOG.txt
@@ -0,0 +1,123 @@
+FONTLOG
+The Mondulkiri Font Family
+Khmer Unicode Fonts
+========================
+
+
+This file provides detailed information on the Khmer Mondulkiri family of fonts.
+This information should be distributed along with the Mondulkiri fonts and
+any derivative works.
+
+Basic Font Information
+----------------------
+
+The Mondulkiri fonts provide Unicode support for the Khmer script.
+"Mondulkiri" is the name of a province in north-eastern Cambodia,
+These fonts are provided free of charge. Previous versions of the fonts have
+been available since 2003 but are now available on the SIL website.
+
+The following fonts from the Mondulkiri typeface family are included in this
+release:
+
+ * Khmer Mondulkiri Regular
+ * Khmer Mondulkiri Bold
+ * Khmer Mondulkiri Italic
+ * Khmer Mondulkiri Bold Italic
+ * Khmer Busra Regular
+ * Khmer Busra Bold
+ * Khmer Busra Italic
+ * Khmer Busra Bold Italic
+
+ChangeLog
+---------
+(This should list both major and minor changes, most recent first.)
+8 September 2014 (Diethelm Kanjahn) Mondulkiri Font Family version 7.100
+- Mondulkiri changes:
+ * The hinting has been improved, the difference between regular and bold
+ is visible on screen in much smaller font sizes than before.
+ * A few bugs were addressed: the disappearing of glyphs on Mac in certain
+ strings that do not occur in correctly typed text, a positioning problem
+ in some Tampuan words on Mac, one syllable in Bunong text on Windows/Linux.
+ * Minor changes in diacritic placement, mostly on Mac. Coeng Kho and coeng
+ Ttha were modified.
+ * Glyphs were added - mostly in the phonetic symbols section. The shaping
+ tables for Mac were streamlined and are now the same as for the Busra font.
+- Busra changes:
+ * The fonts now have AAT tables so that they work on Mac OS X
+ * many glyphs were added, the glyph range is the same as in Mondulkiri 7.100
+ * many glyph shapes and diacritic placements were improved slightly
+ * the ligatures of some consonants with the ‘sra-a’, ‘sra-oo’ and ‘sra-ou’
+ have changed and are now the same as in Mondulkiri.
+ * hinting has been improved
+ * most other changes from Mondulkiri 5.300 to 5.513 are now also in Busra 7.100
+ * The descender value was changed which may affect line spacing.
+
+31 October 2012 (Diethelm Kanjahn) Mondulkiri Font Family version 5.300
+- Split Khmer Mondulkiri fonts from older fonts release
+- Support for Apple's AAT rendering system (tested in OS X 10.6.8) as well as
+ Microsoft OpenType tables.
+- Support for typographical features to be used under OS X with software that
+ does support them (like Pages or TextEdit, but apparently not MS Word or
+ LibreOffice).
+- Support for 'Stylistic Sets' that provide similar options in OpenType as the
+ ‘typographical features’ in OS X. These Stylistic Sets work in Adobe software
+ (tested with CS5 and 5.5 on PC), but not in MS Word. MS Word 2010 does support
+ Stylistic Sets, but apparently only for Latin scripts.
+- Support for Khmer Unicode in Adobe CS5 and CS5.5. Two of the Stylistic Sets
+ address the remaining problems. Please refer to the documentation on stylistic
+ sets.
+- Many Latin script characters have been added. The bold fonts now have also
+ bold Latin characters.
+- Some of the vowel-a ligatures have been changed (e.g. Cho-AA).
+- Many characters have been slightly modified. Most significantly the ‘hooks’ or
+ ‘hair’ of some coengs have been removed(e.g. coeng-Kho, coeng-Ha, coeng-Qa).
+- The positioning of many characters was modified.
+- Many other smaller modifications of glyphs and rules.
+- To prevent register shifters from being rendered as subscript
+ zero-width-non-joiner has now to be inserted before the register shifter in
+ accordance with The Unicode Standard. Also zero-width-joiner has to be in this
+ position now to force the alternative rendering.
+- Increased the descender by a small amount so that second level elements are no
+ longer cut off.
+- For users of the Tampuan language: coeng-vo after coeng-ro and shifting of
+ samyuk before reahmuk are now enabled by default. The Tampuan option now only
+ covers the width of space and the permission to use samyuk after reahmuk.
+- The support for the use of vowels and coengs with independent vowels in OS X
+ is limited. If there is a real need for improvement please contact the font
+ designer.
+- Changed position of quotes (U+2018-9, 201C-D) and mirrored U+201C.
+
+09 November 2010 (Diethelm Kanjahn) Mondulkiri Font Family version 5.300
+- First version released under the SIL Open Font License
+- First version released on http://scripts.sil.org
+- Added fonts: Ratanakiri, all italic typefaces
+- Renamed fonts: Busra and Oureang
+- Major OpenType code revisions
+- Corrections of outlines to comply with TTF conventions
+- Many small edits of the outlines
+- Outlines are now TrueType outlines
+- Improved hinting
+- Added characters
+- Size of Khmer base characters now equivalent to Roman capital letters.
+
+2005-09-16 (Diethelm Kanjahn) Mondulkiri Font Family version 1.1
+ - OpenType and Graphite test fonts
+
+2003-04-12 (Diethelm Kanjahn) Mondulkiri Font Family version 0.9
+- first public release as legacy fonts
+
+
+Acknowledgements
+----------------
+
+N: Diethelm Kanjahn
+E: fonts@sil.org
+W: http://scripts.sil.org/
+D: Designer and font engineer
+
+For more information please visit The Mondulkiri Font Family page on SIL
+International's
+Computers and Writing systems website:
+http://scripts.sil.org/Mondulkiri
+
+Support through the website: http://scripts.sil.org/Support
diff --git a/developer/src/kmc-package/test/fixtures/kmp_2.0/shared/fonts/khmer/mondulkiri/Mondulkiri-R.ttf b/developer/src/kmc-package/test/fixtures/kmp_2.0/shared/fonts/khmer/mondulkiri/Mondulkiri-R.ttf
new file mode 100644
index 00000000000..e109ed60287
Binary files /dev/null and b/developer/src/kmc-package/test/fixtures/kmp_2.0/shared/fonts/khmer/mondulkiri/Mondulkiri-R.ttf differ
diff --git a/developer/src/kmc-package/test/fixtures/kmp_2.0/shared/fonts/khmer/mondulkiri/OFL-FAQ.txt b/developer/src/kmc-package/test/fixtures/kmp_2.0/shared/fonts/khmer/mondulkiri/OFL-FAQ.txt
new file mode 100644
index 00000000000..0893d7cf52b
--- /dev/null
+++ b/developer/src/kmc-package/test/fixtures/kmp_2.0/shared/fonts/khmer/mondulkiri/OFL-FAQ.txt
@@ -0,0 +1,425 @@
+OFL FAQ - Frequently Asked Questions about the SIL Open Font License (OFL)
+Version 1.1-update3 - Sept 2013
+(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. Only the Copyright Holder(s) can do this.
+
+8.3 Is the OFL a contract or a license?
+The OFL is a license and 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.
+
+
+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/developer/src/kmc-package/test/fixtures/kmp_2.0/shared/fonts/khmer/mondulkiri/OFL.txt b/developer/src/kmc-package/test/fixtures/kmp_2.0/shared/fonts/khmer/mondulkiri/OFL.txt
new file mode 100644
index 00000000000..aef2579114f
--- /dev/null
+++ b/developer/src/kmc-package/test/fixtures/kmp_2.0/shared/fonts/khmer/mondulkiri/OFL.txt
@@ -0,0 +1,95 @@
+This Font Software is Copyright (c) 2003-2014, SIL International
+(http://scripts.sil.org/). with Reserved Font Names "Mondulkiri",
+"Busra", "Oureang" and "Ratanakiri".
+
+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/developer/src/kmc-package/test/fixtures/kmp_2.0/splash.gif b/developer/src/kmc-package/test/fixtures/kmp_2.0/splash.gif
new file mode 100644
index 00000000000..93b44e9d16e
Binary files /dev/null and b/developer/src/kmc-package/test/fixtures/kmp_2.0/splash.gif differ
diff --git a/developer/src/kmc-package/test/fixtures/kmp_2.0/welcome/KAK_Documentation_EN.pdf b/developer/src/kmc-package/test/fixtures/kmp_2.0/welcome/KAK_Documentation_EN.pdf
new file mode 100644
index 00000000000..23b6f62b8fe
Binary files /dev/null and b/developer/src/kmc-package/test/fixtures/kmp_2.0/welcome/KAK_Documentation_EN.pdf differ
diff --git a/developer/src/kmc-package/test/fixtures/kmp_2.0/welcome/KAK_Documentation_KH.pdf b/developer/src/kmc-package/test/fixtures/kmp_2.0/welcome/KAK_Documentation_KH.pdf
new file mode 100644
index 00000000000..85bd8c0b0b7
Binary files /dev/null and b/developer/src/kmc-package/test/fixtures/kmp_2.0/welcome/KAK_Documentation_KH.pdf differ
diff --git a/developer/src/kmc-package/test/fixtures/kmp_2.0/welcome/image002.png b/developer/src/kmc-package/test/fixtures/kmp_2.0/welcome/image002.png
new file mode 100644
index 00000000000..40ea6a2e8e4
Binary files /dev/null and b/developer/src/kmc-package/test/fixtures/kmp_2.0/welcome/image002.png differ
diff --git a/developer/src/kmc-package/test/fixtures/kmp_2.0/welcome/keyboard_layout.png b/developer/src/kmc-package/test/fixtures/kmp_2.0/welcome/keyboard_layout.png
new file mode 100644
index 00000000000..8ca8b04b337
Binary files /dev/null and b/developer/src/kmc-package/test/fixtures/kmp_2.0/welcome/keyboard_layout.png differ
diff --git a/developer/src/kmc-package/test/fixtures/kmp_2.0/welcome/welcome.htm b/developer/src/kmc-package/test/fixtures/kmp_2.0/welcome/welcome.htm
new file mode 100644
index 00000000000..124d9d20e66
--- /dev/null
+++ b/developer/src/kmc-package/test/fixtures/kmp_2.0/welcome/welcome.htm
@@ -0,0 +1,54 @@
+
+
+
+ Khmer Angkor Keyboard
+
+
+
Khmer Angkor Keyboard
+
+
+ Khmer Angkor Keyboard is an OpenSource. It is free and more than just a user you can also contribute to the betterment of the keyboard if you would like to.
+
+
+
Keyboards
+
+ With the users' pitfall in typing Khmer words in mind, Khmer Angkor focuses on the unification of the character orders and spelling rules. These make Khmer Angkor uniquely different from any other keyboards. Khmer Angkor's keyboard layouts were adopted from NiDA keyboard which is widely used at the present.
+ Here is the keyboard layout:
+
+
+
+
+
+
You can simply use Khmer Angkor as you would for any NiDA based keyboard. You may type a word in an order of how it is spelled, not how it appears to be, especially when the vowel is to the left of the consonant. For example, to type the word “តែ” which means ‘tea’, one should type the consonant first and then the vowel (i.e. press key “T” and then “Shift E”).
+ With the users' pitfall in typing Khmer words in mind, Khmer Angkor focuses on the unification of the character orders and spelling rules. These make Khmer Angkor uniquely different from any other keyboards. Khmer Angkor's keyboard layouts were adopted from NiDA keyboard which is widely used at the present.
+
+
+
+
diff --git a/developer/src/kmc-package/test/fixtures/normalize_paths/source/splash.gif b/developer/src/kmc-package/test/fixtures/normalize_paths/source/splash.gif
new file mode 100644
index 00000000000..93b44e9d16e
Binary files /dev/null and b/developer/src/kmc-package/test/fixtures/normalize_paths/source/splash.gif differ
diff --git a/developer/src/kmc-package/test/fixtures/normalize_paths/source/welcome/welcome.htm b/developer/src/kmc-package/test/fixtures/normalize_paths/source/welcome/welcome.htm
new file mode 100644
index 00000000000..124d9d20e66
--- /dev/null
+++ b/developer/src/kmc-package/test/fixtures/normalize_paths/source/welcome/welcome.htm
@@ -0,0 +1,54 @@
+
+
+
+ Khmer Angkor Keyboard
+
+
+
Khmer Angkor Keyboard
+
+
+ Khmer Angkor Keyboard is an OpenSource. It is free and more than just a user you can also contribute to the betterment of the keyboard if you would like to.
+
+
+
Keyboards
+
+ With the users' pitfall in typing Khmer words in mind, Khmer Angkor focuses on the unification of the character orders and spelling rules. These make Khmer Angkor uniquely different from any other keyboards. Khmer Angkor's keyboard layouts were adopted from NiDA keyboard which is widely used at the present.
+ Here is the keyboard layout:
+
+
+
+
+
+
You can simply use Khmer Angkor as you would for any NiDA based keyboard. You may type a word in an order of how it is spelled, not how it appears to be, especially when the vowel is to the left of the consonant. For example, to type the word “តែ” which means ‘tea’, one should type the consonant first and then the vowel (i.e. press key “T” and then “Shift E”).
+
+
+
\ No newline at end of file
diff --git a/developer/src/kmc-package/test/fixtures/online/api.github.com/#repos#silnrsi#fonts#commits#main b/developer/src/kmc-package/test/fixtures/online/api.github.com/#repos#silnrsi#fonts#commits#main
new file mode 100644
index 00000000000..690ef170170
--- /dev/null
+++ b/developer/src/kmc-package/test/fixtures/online/api.github.com/#repos#silnrsi#fonts#commits#main
@@ -0,0 +1,913 @@
+{
+ "sha": "044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "node_id": "C_kwDOGD8YNtoAKDA0NGExMDQyNmNkYWJmYTNkZDNiMTNkMDQwYTU2ZDRiNzBlYTQwNTg",
+ "commit": {
+ "author": {
+ "name": "Lorna Evans",
+ "email": "LornaSIL@users.noreply.github.com",
+ "date": "2024-10-29T17:41:20Z"
+ },
+ "committer": {
+ "name": "Lorna Evans",
+ "email": "LornaSIL@users.noreply.github.com",
+ "date": "2024-10-29T17:41:20Z"
+ },
+ "message": "Update Abyssinica to v2.300 after running updatefamilydata.py.",
+ "tree": {
+ "sha": "3ac7e29c3c1b12b239dc69e110b3aa7e87195e1c",
+ "url": "https://api.github.com/repos/silnrsi/fonts/git/trees/3ac7e29c3c1b12b239dc69e110b3aa7e87195e1c"
+ },
+ "url": "https://api.github.com/repos/silnrsi/fonts/git/commits/044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "comment_count": 0,
+ "verification": {
+ "verified": false,
+ "reason": "unsigned",
+ "signature": null,
+ "payload": null,
+ "verified_at": null
+ }
+ },
+ "url": "https://api.github.com/repos/silnrsi/fonts/commits/044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "html_url": "https://github.com/silnrsi/fonts/commit/044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "comments_url": "https://api.github.com/repos/silnrsi/fonts/commits/044a10426cdabfa3dd3b13d040a56d4b70ea4058/comments",
+ "author": {
+ "login": "LornaSIL",
+ "id": 7071907,
+ "node_id": "MDQ6VXNlcjcwNzE5MDc=",
+ "avatar_url": "https://avatars.githubusercontent.com/u/7071907?v=4",
+ "gravatar_id": "",
+ "url": "https://api.github.com/users/LornaSIL",
+ "html_url": "https://github.com/LornaSIL",
+ "followers_url": "https://api.github.com/users/LornaSIL/followers",
+ "following_url": "https://api.github.com/users/LornaSIL/following{/other_user}",
+ "gists_url": "https://api.github.com/users/LornaSIL/gists{/gist_id}",
+ "starred_url": "https://api.github.com/users/LornaSIL/starred{/owner}{/repo}",
+ "subscriptions_url": "https://api.github.com/users/LornaSIL/subscriptions",
+ "organizations_url": "https://api.github.com/users/LornaSIL/orgs",
+ "repos_url": "https://api.github.com/users/LornaSIL/repos",
+ "events_url": "https://api.github.com/users/LornaSIL/events{/privacy}",
+ "received_events_url": "https://api.github.com/users/LornaSIL/received_events",
+ "type": "User",
+ "user_view_type": "public",
+ "site_admin": false
+ },
+ "committer": {
+ "login": "LornaSIL",
+ "id": 7071907,
+ "node_id": "MDQ6VXNlcjcwNzE5MDc=",
+ "avatar_url": "https://avatars.githubusercontent.com/u/7071907?v=4",
+ "gravatar_id": "",
+ "url": "https://api.github.com/users/LornaSIL",
+ "html_url": "https://github.com/LornaSIL",
+ "followers_url": "https://api.github.com/users/LornaSIL/followers",
+ "following_url": "https://api.github.com/users/LornaSIL/following{/other_user}",
+ "gists_url": "https://api.github.com/users/LornaSIL/gists{/gist_id}",
+ "starred_url": "https://api.github.com/users/LornaSIL/starred{/owner}{/repo}",
+ "subscriptions_url": "https://api.github.com/users/LornaSIL/subscriptions",
+ "organizations_url": "https://api.github.com/users/LornaSIL/orgs",
+ "repos_url": "https://api.github.com/users/LornaSIL/repos",
+ "events_url": "https://api.github.com/users/LornaSIL/events{/privacy}",
+ "received_events_url": "https://api.github.com/users/LornaSIL/received_events",
+ "type": "User",
+ "user_view_type": "public",
+ "site_admin": false
+ },
+ "parents": [
+ {
+ "sha": "7d5dfbbb67a38c1fa4a9612154ec63abb27a56a9",
+ "url": "https://api.github.com/repos/silnrsi/fonts/commits/7d5dfbbb67a38c1fa4a9612154ec63abb27a56a9",
+ "html_url": "https://github.com/silnrsi/fonts/commit/7d5dfbbb67a38c1fa4a9612154ec63abb27a56a9"
+ }
+ ],
+ "stats": {
+ "total": 2209,
+ "additions": 1578,
+ "deletions": 631
+ },
+ "files": [
+ {
+ "sha": "0bbe26ca19ecabe1d80ff524ba00ed2bf32392d7",
+ "filename": "basefiles/abyssinicasil_base.json",
+ "status": "modified",
+ "additions": 2,
+ "deletions": 2,
+ "changes": 4,
+ "blob_url": "https://github.com/silnrsi/fonts/blob/044a10426cdabfa3dd3b13d040a56d4b70ea4058/basefiles%2Fabyssinicasil_base.json",
+ "raw_url": "https://github.com/silnrsi/fonts/raw/044a10426cdabfa3dd3b13d040a56d4b70ea4058/basefiles%2Fabyssinicasil_base.json",
+ "contents_url": "https://api.github.com/repos/silnrsi/fonts/contents/basefiles%2Fabyssinicasil_base.json?ref=044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "patch": "@@ -4,10 +4,10 @@\n \"family\": \"Abyssinica SIL\",\n \"familyid\": \"abyssinicasil\",\n \"license\": \"OFL\",\n- \"packageurl\": \"https://software.sil.org/downloads/r/abyssinica/AbyssinicaSIL-2.201.zip\",\n+ \"packageurl\": \"https://software.sil.org/downloads/r/abyssinica/AbyssinicaSIL-2.300.zip\",\n \"siteurl\": \"https://software.sil.org/abyssinica/\",\n \"source\": \"SIL\",\n \"status\": \"current\",\n- \"ziproot\": \"AbyssinicaSIL-2.201\"\n+ \"ziproot\": \"AbyssinicaSIL-2.300\"\n }\n }\n\\ No newline at end of file"
+ },
+ {
+ "sha": "2a96dde5b4a6612e94c20c573142f712d289912a",
+ "filename": "families.json",
+ "status": "modified",
+ "additions": 6,
+ "deletions": 6,
+ "changes": 12,
+ "blob_url": "https://github.com/silnrsi/fonts/blob/044a10426cdabfa3dd3b13d040a56d4b70ea4058/families.json",
+ "raw_url": "https://github.com/silnrsi/fonts/raw/044a10426cdabfa3dd3b13d040a56d4b70ea4058/families.json",
+ "contents_url": "https://api.github.com/repos/silnrsi/fonts/contents/families.json?ref=044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "patch": "@@ -29,17 +29,17 @@\n \"family\": \"Abyssinica SIL\",\n \"familyid\": \"abyssinicasil\",\n \"files\": {\n- \"AbyssinicaSIL-Regular.ttf\": { \"axes\": { \"ital\": 0, \"wght\": 400.0 }, \"flourl\": \"https://fonts.languagetechnology.org/fonts/sil/abyssinicasil/AbyssinicaSIL-Regular.ttf\", \"packagepath\": \"AbyssinicaSIL-Regular.ttf\", \"url\": \"https://github.com/silnrsi/fonts/raw/main/fonts/sil/abyssinicasil/AbyssinicaSIL-Regular.ttf\", \"zippath\": \"AbyssinicaSIL-2.201/AbyssinicaSIL-Regular.ttf\" },\n- \"AbyssinicaSIL-Regular.woff\": { \"axes\": { \"ital\": 0, \"wght\": 400.0 }, \"flourl\": \"https://fonts.languagetechnology.org/fonts/sil/abyssinicasil/web/AbyssinicaSIL-Regular.woff\", \"packagepath\": \"web/AbyssinicaSIL-Regular.woff\", \"url\": \"https://github.com/silnrsi/fonts/raw/main/fonts/sil/abyssinicasil/web/AbyssinicaSIL-Regular.woff\", \"zippath\": \"AbyssinicaSIL-2.201/web/AbyssinicaSIL-Regular.woff\" },\n- \"AbyssinicaSIL-Regular.woff2\": { \"axes\": { \"ital\": 0, \"wght\": 400.0 }, \"flourl\": \"https://fonts.languagetechnology.org/fonts/sil/abyssinicasil/web/AbyssinicaSIL-Regular.woff2\", \"packagepath\": \"web/AbyssinicaSIL-Regular.woff2\", \"url\": \"https://github.com/silnrsi/fonts/raw/main/fonts/sil/abyssinicasil/web/AbyssinicaSIL-Regular.woff2\", \"zippath\": \"AbyssinicaSIL-2.201/web/AbyssinicaSIL-Regular.woff2\" }\n+ \"AbyssinicaSIL-Regular.ttf\": { \"axes\": { \"ital\": 0, \"wght\": 400.0 }, \"flourl\": \"https://fonts.languagetechnology.org/fonts/sil/abyssinicasil/AbyssinicaSIL-Regular.ttf\", \"packagepath\": \"AbyssinicaSIL-Regular.ttf\", \"url\": \"https://github.com/silnrsi/fonts/raw/main/fonts/sil/abyssinicasil/AbyssinicaSIL-Regular.ttf\", \"zippath\": \"AbyssinicaSIL-2.300/AbyssinicaSIL-Regular.ttf\" },\n+ \"AbyssinicaSIL-Regular.woff\": { \"axes\": { \"ital\": 0, \"wght\": 400.0 }, \"flourl\": \"https://fonts.languagetechnology.org/fonts/sil/abyssinicasil/web/AbyssinicaSIL-Regular.woff\", \"packagepath\": \"web/AbyssinicaSIL-Regular.woff\", \"url\": \"https://github.com/silnrsi/fonts/raw/main/fonts/sil/abyssinicasil/web/AbyssinicaSIL-Regular.woff\", \"zippath\": \"AbyssinicaSIL-2.300/web/AbyssinicaSIL-Regular.woff\" },\n+ \"AbyssinicaSIL-Regular.woff2\": { \"axes\": { \"ital\": 0, \"wght\": 400.0 }, \"flourl\": \"https://fonts.languagetechnology.org/fonts/sil/abyssinicasil/web/AbyssinicaSIL-Regular.woff2\", \"packagepath\": \"web/AbyssinicaSIL-Regular.woff2\", \"url\": \"https://github.com/silnrsi/fonts/raw/main/fonts/sil/abyssinicasil/web/AbyssinicaSIL-Regular.woff2\", \"zippath\": \"AbyssinicaSIL-2.300/web/AbyssinicaSIL-Regular.woff2\" }\n },\n \"license\": \"OFL\",\n- \"packageurl\": \"https://software.sil.org/downloads/r/abyssinica/AbyssinicaSIL-2.201.zip\",\n+ \"packageurl\": \"https://software.sil.org/downloads/r/abyssinica/AbyssinicaSIL-2.300.zip\",\n \"siteurl\": \"https://software.sil.org/abyssinica/\",\n \"source\": \"SIL\",\n \"status\": \"current\",\n- \"version\": \"2.201\",\n- \"ziproot\": \"AbyssinicaSIL-2.201\"\n+ \"version\": \"2.300\",\n+ \"ziproot\": \"AbyssinicaSIL-2.300\"\n },\n \"akatab\": {\n \"defaults\": {"
+ },
+ {
+ "sha": "e126900d9d86cab08a1be685e5b049c8e0a0e977",
+ "filename": "fonts/sil/abyssinicasil/AbyssinicaSIL-Regular.ttf",
+ "status": "modified",
+ "additions": 0,
+ "deletions": 0,
+ "changes": 0,
+ "blob_url": "https://github.com/silnrsi/fonts/blob/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2FAbyssinicaSIL-Regular.ttf",
+ "raw_url": "https://github.com/silnrsi/fonts/raw/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2FAbyssinicaSIL-Regular.ttf",
+ "contents_url": "https://api.github.com/repos/silnrsi/fonts/contents/fonts%2Fsil%2Fabyssinicasil%2FAbyssinicaSIL-Regular.ttf?ref=044a10426cdabfa3dd3b13d040a56d4b70ea4058"
+ },
+ {
+ "sha": "f83c5e0702ad5a50b6fafb12df73b2dfe6359b08",
+ "filename": "fonts/sil/abyssinicasil/FONTLOG.txt",
+ "status": "modified",
+ "additions": 51,
+ "deletions": 8,
+ "changes": 59,
+ "blob_url": "https://github.com/silnrsi/fonts/blob/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2FFONTLOG.txt",
+ "raw_url": "https://github.com/silnrsi/fonts/raw/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2FFONTLOG.txt",
+ "contents_url": "https://api.github.com/repos/silnrsi/fonts/contents/fonts%2Fsil%2Fabyssinicasil%2FFONTLOG.txt?ref=044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "patch": "@@ -20,20 +20,19 @@ Latin characters and symbols. This font makes use of state-of-the-art font\n technologies to support the need to position arbitrary combinations of \n *Ethiopic* base glyphs and combining marks optimally. It also supports\n almost 200 kerning pairs. This version of the font also supports Character \n-Variants (OpenType) or Features (Graphite) which make glyph alternates \n-available for a number of Ethiopic and punctuation characters. \n+Variants (OpenType) which make glyph alternates available for a number of \n+Ethiopic and punctuation characters. \n \n One font from this typeface family is included in this release:\n \n * Abyssinica SIL Regular \n \n-\n A Note Regarding the Open Font License and TypeTuner\n ----------------------------------------------------\n \n The OFL prohibits the use of Reserved Font Names \"Abyssinica\" and \"SIL\" in\n the name of any font that is derived from the Original Version of \n-Abyssinica SIL. However, SIL International (the Copyright Holder) grants \n+Abyssinica SIL. However, SIL Global (the Copyright Holder) grants \n through this separate written agreement the right to use the Reserved Font\n Names in any Modified Version of this font created by using TypeTuner as \n long as the feature information contained in the Original Version is used, \n@@ -54,6 +53,50 @@ ChangeLog\n ---------\n (This should list both major and minor changes, most recent first.)\n \n+### 29 Oct 2024 (WSTech Team) Abyssinica SIL version 2.300\n+\n+#### Improved\n+\n+- Adjusted glyph shapes for\n+ - 1214 ETHIOPIC SYLLABLE HHEE\n+ - 1264 ETHIOPIC SYLLABLE BEE\n+ - 126C ETHIOPIC SYLLABLE VEE\n+ - 129C ETHIOPIC SYLLABLE NYEE\n+ - 12DC ETHIOPIC SYLLABLE ZEE\n+ - 1334 ETHIOPIC SYLLABLE PHEE\n+ - 133C ETHIOPIC SYLLABLE TSEE\n+ - AB14 ETHIOPIC SYLLABLE DZEE\n+ - AB2C ETHIOPIC SYLLABLE BBEE\n+ - 1E7E4 ETHIOPIC SYLLABLE HHYEE\n+ - 1E7EA ETHIOPIC SYLLABLE HHWEE\n+- Improve diacritic position to support multiple above diacritics\n+\n+#### Added\n+\n+- Added gzi Ligature\n+- 2080 SUBSCRIPT ZERO\n+- 2081 SUBSCRIPT ONE\n+- 2082 SUBSCRIPT TWO\n+- 2083 SUBSCRIPT THREE\n+- 2084 SUBSCRIPT FOUR\n+- 2085 SUBSCRIPT FIVE\n+- 2086 SUBSCRIPT SIX\n+- 2087 SUBSCRIPT SEVEN\n+- 2088 SUBSCRIPT EIGHT\n+- 2089 SUBSCRIPT NINE\n+- 2460 CIRCLED DIGIT ONE\n+- 2461 CIRCLED DIGIT TWO\n+- 2462 CIRCLED DIGIT THREE\n+- 2463 CIRCLED DIGIT FOUR\n+- 2464 CIRCLED DIGIT FIVE\n+- 2465 CIRCLED DIGIT SIX\n+- 2466 CIRCLED DIGIT SEVEN\n+- 2467 CIRCLED DIGIT EIGHT\n+- 2468 CIRCLED DIGIT NINE\n+\n+#### Remove\n+- Graphite\n+\n ### 23 June 2023 (WSTech Team) Abyssinica SIL version 2.201\n - Fixed bug in TypeTuner support for cv46 tswa alternate\n \n@@ -111,7 +154,7 @@ to best submit your contributions.\n \n To enable us to accept contributions in a way that honors your contribution \n and respects your copyright while preserving long-term flexibility for open \n-source licensing, you would also need to agree to the SIL International \n+source licensing, you would also need to agree to the SIL Global \n Contributor License Agreement for Font Software (v1.0) prior to sending us \n your contribution. To read more about this requirement and find out how to \n submit the required form, please visit the CLA information page\n@@ -173,14 +216,14 @@ D: Designer\n N: Daniel Yacob\n E: yacob@geez.org\n W: https://www.geez.org/, https://github.com/geezorg\n-D: Font designer, contributed significant input on the design of extended Ethiopic\n+D: Font designer, contributed significant input on the design of extended Ethiopic and additional digit forms\n \n N: Kjell Magne Yri\n D: Font based on his original calligraphic design\n \n-The Abyssinica SIL project is maintained by SIL International.\n+The Abyssinica SIL project is maintained by SIL Global.\n \n-For more information please visit the Abyssinica SIL page on SIL International's\n+For more information please visit the Abyssinica SIL page on SIL Global's\n Computers and Writing systems website:\n https://software.sil.org/abyssinica\n "
+ },
+ {
+ "sha": "63fc8b1e0ba81c8849ba0f2a1dbc4e1e8d3c8fab",
+ "filename": "fonts/sil/abyssinicasil/OFL-FAQ.txt",
+ "status": "modified",
+ "additions": 98,
+ "deletions": 83,
+ "changes": 181,
+ "blob_url": "https://github.com/silnrsi/fonts/blob/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2FOFL-FAQ.txt",
+ "raw_url": "https://github.com/silnrsi/fonts/raw/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2FOFL-FAQ.txt",
+ "contents_url": "https://api.github.com/repos/silnrsi/fonts/contents/fonts%2Fsil%2Fabyssinicasil%2FOFL-FAQ.txt?ref=044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "patch": "@@ -1,13 +1,13 @@\n-OFL FAQ - Frequently Asked Questions about the SIL Open Font License (OFL)\n-Version 1.1-update6 - December 2020\n-The OFL FAQ is copyright (c) 2005-2020 SIL International.\n+OFL FAQ - Frequently Asked Questions about the SIL Open Font License (OFL)\n+Version 1.1-update7 - November 2023\n+The OFL FAQ is Copyright (c) 2005-2023, SIL International (https://www.sil.org)\n Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.\n-(See https://scripts.sil.org/OFL for updates)\n+(See https://openfontlicense.org/ofl-faq for updates)\n \n \n CONTENTS OF THIS FAQ\n 1 USING AND DISTRIBUTING FONTS LICENSED UNDER THE OFL\n-2 USING OFL FONTS FOR WEB PAGES AND ONLINE WEB FONT SERVICES\n+2 USING OFL FONTS FOR WEBPAGES AND ONLINE WEBFONT SERVICES\n 3 MODIFYING OFL-LICENSED FONTS\n 4 LICENSING YOUR ORIGINAL FONTS UNDER THE OFL\n 5 CHOOSING RESERVED FONT NAMES\n@@ -18,8 +18,7 @@ CONTENTS OF THIS FAQ\n APPENDIX A - FONTLOG EXAMPLE\n \n 1 USING AND DISTRIBUTING FONTS LICENSED UNDER THE OFL\n-\n-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?\n+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?\n 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.\n \n 1.1.1 Does that restrict the license or distribution of that artwork?\n@@ -29,13 +28,13 @@ No. You remain the author and copyright holder of that newly derived graphic or\n 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.\n \n 1.2 Can the fonts be included with Free/Libre and Open Source Software collections such as GNU/Linux and BSD distributions and repositories?\n-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.)\n+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 entry 5.9 about rebuilding from source.)\n \n-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?\n+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?\n 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.\n \n 1.4 Can I sell a software package that includes these fonts?\n-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.\n+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: text editors, word processors, design and publishing applications, training and educational software, games and entertainment software, mobile device applications, etc.\n \n 1.5 Can I include the fonts on a CD of freeware or commercial fonts?\n Yes, as long some other font or software is also on the disk, so the OFL font is not sold by itself.\n@@ -46,14 +45,14 @@ The intent is to keep people from making money by simply redistributing the font\n 1.7 What about sharing OFL fonts with friends on a CD, DVD or USB stick?\n 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.\n \n-1.8 Can I host the fonts on a web site for others to use?\n-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.\n+1.8 Can I host the fonts on a website for others to use?\n+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 webfonts in Section 2.\n \n 1.9 Can I host the fonts on a server for use over our internal network?\n 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.\n \n 1.10 Does the full OFL license text always need to accompany the font?\n-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 https://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.\n+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 https://openfontlicense.org, 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.\n \n 1.11 What do you mean by 'embedding'? How does that differ from other means of distribution?\n 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.\n@@ -62,7 +61,7 @@ By 'embedding' we mean inclusion of the font in a document or file in a way that\n 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.\n \n 1.13 Does embedding alter the license of the document itself?\n-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.\n+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 the OFL does not make the resulting artwork subject to the OFL.\n \n 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)?\n 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.\n@@ -74,85 +73,90 @@ Certain document formats may allow the inclusion of an unmodified font within th\n 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.\n \n 1.17 Can Font Software released under the OFL be subject to URL-based access restrictions methods or DRM (Digital Rights Management) mechanisms?\n-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.\n+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.\n \n 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?\n 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.\n \n 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?\n-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.\n+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 website 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.\n \n-1.20 I'm writing a small app for mobile platforms, do I need to include the whole package? \n+1.20 I'm writing a small app for mobile platforms, do I need to include the whole package? \n 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.\n \n-1.21 What about including OFL fonts by default in my firmware or dedicated operating system? \n+1.21 What about including OFL fonts by default in my firmware or dedicated operating system? \n 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.\n \n-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?\n-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).\n+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?\n+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 entry 1.4 for details and examples about selling bundles).\n \n 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?\n 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.\n \n 1.24 Can services that provide or distribute OFL fonts restrict my use of them?\n 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.\n \n+1.25 Can a font released under the OFL be used as a source by an AI (Artificial Intelligence), an ML (Machine Learning) model, a NN (neural network), or similar system to create a new font and release it under a different license?\n+No. Any font produced from such systems whose input or training data contains any source file from a font project licensed under the OFL should be considered a derivative work. All Font Software released under the OFL and marked as such by the author(s) must remain under the OFL regardless of the way the sources might have been transformed, in whole or in part. If you would like to use font sources to produce a font to be released under a different license, then you need to contact the corresponding authors directly to ask for their explicit permission.\n \n-2 USING OFL FONTS FOR WEBPAGES AND ONLINE WEB FONT SERVICES\n+1.26 Can OFL fonts be used by AI-based design tools?\n+Yes, as long as the resulting work is not intended to be a font. Using such automated systems to produce graphical output - something that is not a font - is considered similar to normal usage. It is equivalent to using an OFL font in the graphic design process as discussed in question 1.1.\n \n-NOTE: This section often refers to a separate paper on 'Web Fonts & RFNs'. This is available at https://scripts.sil.org/OFL_web_fonts_and_RFNs\n \n-2.1 Can I make webpages using these fonts?\n-Yes! Go ahead! Using CSS (Cascading Style Sheets) is recommended. Your three best options are: \n-- referring directly in your stylesheet to open fonts which may be available on the user's system\n-- providing links to download the full package of the font - either from your own website or from elsewhere - so users can install it themselves\n-- 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.\n+2 USING OFL FONTS FOR WEBPAGES AND ONLINE WEBFONT SERVICES\n \n-2.2 Can I make and use WOFF (Web Open Font Format) versions of OFL fonts?\n-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:\n+NOTE: This section often refers to a separate paper on 'Webfonts and Reserved Font Names'. This is available at https://openfontlicense.org/webfonts-and-reserved-font-names\n \n-- the original font data remains unchanged except for WOFF compression, and\n-- WOFF-specific metadata is either omitted altogether or present and includes, unaltered, the contents of all equivalent metadata in the original font.\n+2.1 Can I make webpages using OFL fonts?\n+Yes! Go ahead! You could ask visitors to download and install the fonts, but loading the fonts dynamically as webfonts through CSS @font-face declarations is a much better method. The referenced fonts can be hosted on the same server as other site assets and content, or loaded from a separate webfont service. This is recommended and explicitly allowed by the licensing model because it is distribution.\n+\n+2.2 Can I make and use WOFF (Web Open Font Format) versions of OFL fonts?\n+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 and WOFF2 formats, however, it is possible to create a WOFF/WOFF2 version that is not considered modification, and so would not require a name change.\n \n-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.\n+2.2.1 How can I make sure that a WOFF/WOFF2 version is not considered modification?\n+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.\n \n-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.\n+2.2.2 Do WOFF conversion tools and services automatically meet these requirements?\n+No. Some 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.\n \n-2.3 What about other web font formats such as EOT/EOTLite/CWT/etc.?\n-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 https://scripts.sil.org/OFL_web_fonts_and_RFNs \n+2.3 What about other webfont formats such as EOT/EOTLite/CWT/etc.?\n+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 https://openfontlicense.org/webfonts-and-reserved-font-names\n \n-2.4 Can I make OFL fonts available through web font online services?\n-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).\n+2.4 Can I make OFL fonts available through webfont online services?\n+Yes, you are welcome to include OFL fonts in online webfont 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 entry 1.17 for details related to URL-based access restrictions methods or DRM mechanisms).\n \n-2.5 Some web font formats and services provide ways of \"optimizing\" the font for a particular website or web application; is that allowed? \n+2.5 Some webfont formats and services provide ways of 'optimizing' the font for a particular website or web application; is that allowed? \n 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.\n \n-2.6 Is subsetting a web font considered modification?\n-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 https://scripts.sil.org/OFL_web_fonts_and_RFNs\n+2.6 Is subsetting a webfont considered modification?\n+Yes. Removing any parts of the font when delivering a webfont 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 entry 2.8 and https://openfontlicense.org/webfonts-and-reserved-font-names\n \n-2.7 Are there any situations in which a modified web font could use RFNs?\n-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.\n+2.7 Are there any situations in which a modified webfont could use RFNs?\n+Yes. If a webfont is optimized only in ways that preserve Functional Equivalence (see entry 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 webfont service or provider to sign a separate agreement with the author(s) that allows the use of RFNs for Modified Versions.\n \n-2.8 How do you know if an optimization to a web font preserves Functional Equivalence?\n-Functional Equivalence is described in full in the 'Web fonts and RFNs' paper at https://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:\n+2.8 How do you know if an optimization to a webfont preserves Functional Equivalence?\n+Functional Equivalence is described in full in the 'Webfonts and Reserved Font Names' paper at https://openfontlicense.org/webfonts-and-reserved-font-names, in general, an optimized font is deemed to be Functionally Equivalent (FE) to the Original Version if it:\n \n-- 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. \n+- 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 webpage, will display properly.\n - 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.\n - Presents text with no obvious degradation in visual quality. The lettershapes should be equally (or more) readable, within limits of the rendering platform.\n - 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.\n \n 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.\n \n-2.9 Isn't use of web fonts another form of embedding?\n-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 https://scripts.sil.org/OFL_web_fonts_and_RFNs\n+2.9 Can fonts released under the OFL be used with Incremental Font Transfer (IFT) or similar on-the-fly subsetting and compression technologies?\n+Yes, if they provide a sufficient level of Functional Equivalence. Extra care should be taken to make sure that such processes - both on the server and on the client - do not break glyph coverage and smart features especially for lesser-known and lesser-resourced languages in the resulting document or app. See the 'Webfonts and Reserved Font Names' paper on https://openfontlicense.org/webfonts-and-reserved-font-names for more about the goals and the rationale.\n \n-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?\n-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.\n+2.10 Isn't use of webfonts another form of embedding?\n+No. Unlike embedded fonts in a PDF, webfonts 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 webfonts used by a document may be identified and downloaded for desktop use demonstrates that they are philosophically and technically separate from the webpages that specify them. See https://openfontlicense.org/webfonts-and-reserved-font-names\n \n-2.11 What should an agreement for the use of RFNs say? Are there any examples?\n-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.\n+2.11 So would it be better to not use RFNs at all if you want your font to be distributed by a webfont service?\n+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 webfont services. If that webfont 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.\n \n-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 https://scripts.sil.org/OFL_web_fonts_and_RFNs\n+2.12 What should an agreement for the use of RFNs say? Are there any examples?\n+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 webfont services to clearly state when they have established such agreements, so that the public understands clearly that their service is operating appropriately.\n+\n+See the separate paper on 'Webfonts and Reserved Font Names' for in-depth discussion of issues related to the use of RFNs for webfonts. This is available at https://openfontlicense.org/webfonts-and-reserved-font-names\n \n \n 3 MODIFYING OFL-LICENSED FONTS\n@@ -178,7 +182,7 @@ No, but please consider sharing your improvements with others. You may find that\n 3.7 If a trademark is claimed in the OFL font, does that trademark need to remain in modified fonts?\n 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.\n \n-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? \n+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? \n 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.\n \n \n@@ -192,21 +196,23 @@ If you want to release your fonts under the OFL, we recommend you do the followi\n \n 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.\n \n-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.\n+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 website 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.\n \n 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).\n \n 4.2.4 Include the relevant practical documentation on the license by adding the current OFL-FAQ.txt file in your package.\n \n-4.2.5 If you wish you can use the OFL graphics (https://scripts.sil.org/OFL_logo) on your website. \n+4.2.5 If you wish you can use the OFL graphics (https://openfontlicense.org/promotion) on your website. \n \n 4.3 Will you make my font OFL for me?\n-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. \n+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.\n \n 4.4 Will you distribute my OFL font for me?\n-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 (https://unifont.org/fontguide), The League of Movable Type (https://www.theleagueofmoveabletype.com/) or the Open Font Library (https://fontlibrary.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. \n+No. The easiest way for users to always get the most current version of the font is for you to distribute it through your own website. You can also distribute your own font source files, or host them on services such as GitHub or GitLab. You can use various channels, including social media, to promote and get attention to your project. If you want someone else to distribute the font, consider services and sites that already distribute OFL fonts. Some of those are listed on the OFL website (https://openfontlicense.org/ofl-fonts). Contact them to find out how to submit fonts to them. 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.\n \n 4.5 Why should I use the OFL for my fonts?\n+Here are a few of the many good reasons:\n+\n - to meet needs for fonts that can be modified to support lesser-known languages\n - to provide a legal and clear way for people to respect your work but still use it (and reduce piracy)\n - to involve others in your font project\n@@ -218,15 +224,21 @@ No, although if the font is of sufficient quality and general interest we may in\n - to educate students about quality typeface and font design\n - to expand your test base and get more useful feedback \n - to extend your reach to new markets when users see your metadata and go to your website\n-- to get your font more easily into one of the web font online services\n+- to get your font more easily into one of the webfont online services\n - to attract attention for your commercial fonts\n-- to make money through web font services\n+- to make money through webfont services\n - to make money by bundling fonts with applications\n - to make money adjusting and extending existing open fonts\n-- to get a better chance that foundations/NGOs/charities/companies who commission fonts will pick you \n+- to get a better chance that foundations, NGOs, charities, or companies who commission fonts will pick you \n - to be part of a sharing design and development community \n - to give back and contribute to a growing body of font sources\n \n+4.6 Can I cancel or undo the OFL license for a font that I've already released under it?\n+No, as an author, you cannot cancel or undo the permissions you have granted earlier by releasing a font under the OFL. But as an original author of that specific font you can always re-release it separately under another license of your own choosing. Of course, you cannot re-license a font for which you are not the author. If there are multiple authors they need to be all in official written agreement with the re-licensing. For practical reasons, a different name than an existing and publicly available open font should be chosen.\n+\n+4.7 Should I apply the OFL early in the design process, even before the font is complete, or wait until I want to release a completed version?\n+It is really up to you and the circumstances of your project. But in any case, we would recommend you place appropriate warning messages in your public repository or website to say something like \"Please wait for a finished release before using and redistributing this font\". We recommend you have a clear versioning scheme and repository tagging to make it as easy as possible to see if the font is a released version or still under development. You can also consider choosing a separate name (or suffix) for the development version, and only give the final name to a released version.\n+\n \n 5 CHOOSING RESERVED FONT NAMES\n \n@@ -237,7 +249,7 @@ These are font names, or portions of font names, that the author has chosen to r\n 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.\n \n 5.3 What do you mean by \"primary name as presented to the user\"? Are you referring to the font menu name?\n-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. \n+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.\n \n 5.4 Am I not allowed to use any part of the Reserved Font Names?\n 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.\n@@ -246,13 +258,13 @@ You may not use individual words from the Reserved Font Names, but you would be\n 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.\n \n 5.6 Do I, as an author, have to identify any Reserved Font Names?\n-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.\n+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 webfonts see section 2.\n \n 5.7 Are any names (such as the main font name) reserved by default?\n 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).\n \n 5.8 Is there any situation in which I can use Reserved Font Names for a Modified Version?\n-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.\n+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 an 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.\n \n 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?\n 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.\n@@ -270,7 +282,7 @@ It has three purposes: 1) to provide basic information on the font to users and\n It is not a requirement of the license, but we strongly recommend you have one.\n \n 6.3 Am I required to update the FONTLOG when making Modified Versions?\n-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.\n+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.\n \n 6.4 What should the FONTLOG look like?\n It is typically a separate text file (FONTLOG.txt), but can take other formats. It commonly includes these four sections:\n@@ -301,7 +313,7 @@ It is likely that most authors of OFL fonts would accept financial contributions\n 8 ABOUT THE LICENSE ITSELF\n \n 8.1 I see that this is version 1.1 of the license. Will there be later changes?\n-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: https://scripts.sil.org/OFL.\n+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 website: https://openfontlicense.org.\n \n 8.2 Does this license restrict the rights of the Copyright Holder(s)?\n 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.\n@@ -310,14 +322,14 @@ No. The Copyright Holder(s) still retain(s) all the rights to their creation; th\n 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.\n \n 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?\n-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-2017 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.\n+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-2023 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.\n \n 8.5 Can I quote from the OFL FAQ?\n Yes, SIL gives permission to quote from the OFL FAQ (OFL-FAQ.txt), in whole or in part, provided that the quoted text is:\n \n - unmodified,\n - used to help explain the intent of the OFL, rather than cause misunderstanding, and\n-- accompanied with the following attribution: \"From the OFL FAQ (OFL-FAQ.txt), copyright (c) 2005-2020 SIL International. Used by permission. https://scripts.sil.org/OFL-FAQ_web\".\n+- accompanied with the following attribution: \"From the OFL FAQ (OFL-FAQ.txt), copyright (c) 2005-2023 SIL International. Used by permission. https://openfontlicense.org/OFL-FAQ\".\n \n 8.6 Can I translate the license and the FAQ into other languages?\n 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.\n@@ -326,30 +338,33 @@ If you are an experienced translator, you are very welcome to translate the OFL\n \n SIL gives permission to publish unofficial translations into other languages provided that they comply with the following guidelines:\n \n-- Put the following disclaimer in both English and the target language stating clearly that the translation is unofficial:\n+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 https://openfontlicense.org for the official version of the license and the accompanying OFL-FAQ.\"\n \n-\"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 https://scripts.sil.org/OFL for the official version of the license and the accompanying OFL-FAQ.\"\n+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 an unofficial translation effort of the OFL and OFL-FAQ please let us know.\n \n-- 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. \n+8.7 Does the OFL have an explicit expiration term?\n+No, the implicit intent of the OFL is that the permissions granted are perpetual and irrevocable.\n \n-If you start such a unofficial translation effort of the OFL and OFL-FAQ please let us know.\n+8.8 Why is there no automatic upgrade clause, a 'version 1.1 or later' like in the GPL?\n+This is by design, with the goals of establishing clear trust and of preventing any situation where the actual terms could be changed from underneath any user of the license. That would introduce uncertainty and confusion. Any perceived benefits of automatic incremental licensing under newer versions is strongly outweighed by the inherent risks and confusion it would cause. If a new version becomes officially available, Copyright Holder(s) can review the new version and decide whether to re-release their fonts under it. Derivative fonts could not be re-licensed unless the original versions were re-released first.\n \n-8.7 Does the OFL have an explicit expiration term?\n-No, the implicit intent of the OFL is that the permissions granted are perpetual and irrevocable. \n+8.9 How do you pronounce the name of the license?\n+The OFL is pronounced as three individual letters /ˈɑː.əf.əl/ or OH-EFF-ELL.\n \n \n 9 ABOUT SIL INTERNATIONAL\n \n 9.1 Who is SIL International and what do they do?\n-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.\n+SIL is a global, faith-based nonprofit that works with local communities around the world to develop language solutions that expand possibilities for a better life. 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.\n \n 9.2 What does this have to do with font licensing?\n 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.\n \n 9.3 How can I contact SIL?\n-Our main web site is: https://www.sil.org/\n-Our site about complex scripts is: https://scripts.sil.org/\n-Information about this license (and contact information) is at: https://scripts.sil.org/OFL\n+Our main website is: https://www.sil.org/\n+Our main site about fonts and software is: https://software.sil.org/\n+Our site about complex scripts is: https://scriptsource.org/\n+Information about this license (and contact information) is at: https://openfontlicense.org \n \n \n APPENDIX A - FONTLOG EXAMPLE\n@@ -378,7 +393,7 @@ ChangeLog\n - fix new build and testing system (bug #123456)\n \n 1 August 2008 (Tom Parker) GlobalFontFamily version 1.2.1\n-- Tweaked the smart font code (Branch merged with trunk version)\n+- Tweaked the smart font code (Branch merged with main)\n - Provided improved build and debugging environment for smart behaviours\n \n 7 February 2007 (Pat Johnson) NewWorldFontFamily Version 1.3\n@@ -405,27 +420,27 @@ If you make modifications be sure to add your name (N), email (E), web-address (\n \n N: Jane Doe\n E: jane@university.edu\n-W: http://art.university.edu/projects/fonts\n+W: https://art.university.edu/projects/fonts\n D: Contributor - Armenian glyphs and code\n \n N: Fred Foobar\n E: fred@foobar.org\n-W: http://foobar.org\n+W: https://foobar.org\n D: Contributor - misc Graphite fixes\n \n N: Pat Johnson\n E: pat@fontstudio.org\n-W: http://pat.fontstudio.org\n+W: https://pat.fontstudio.org\n D: Designer - Greek & Cyrillic glyphs based on Roman design\n \n N: Tom Parker\n E: tom@company.com\n-W: http://www.company.com/tom/projects/fonts\n+W: https://www.company.com/tom/projects/fonts\n D: Engineer - original smart font code\n \n N: Joe Smith\n E: joe@fontstudio.org\n-W: http://joe.fontstudio.org\n+W: https://joe.fontstudio.org\n D: Designer - original Roman glyphs\n \n Fontstudio.org is an not-for-profit design group whose purpose is..."
+ },
+ {
+ "sha": "1da0bc6aaf40387d9a4edbc7ddc9466313351bd3",
+ "filename": "fonts/sil/abyssinicasil/OFL.txt",
+ "status": "modified",
+ "additions": 2,
+ "deletions": 2,
+ "changes": 4,
+ "blob_url": "https://github.com/silnrsi/fonts/blob/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2FOFL.txt",
+ "raw_url": "https://github.com/silnrsi/fonts/raw/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2FOFL.txt",
+ "contents_url": "https://api.github.com/repos/silnrsi/fonts/contents/fonts%2Fsil%2Fabyssinicasil%2FOFL.txt?ref=044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "patch": "@@ -1,11 +1,11 @@\n-This Font Software is Copyright (c) 2000-2023, SIL International (https://www.sil.org/)\n+This Font Software is Copyright (c) 2000-2024, SIL Global (https://www.sil.org/)\n with Reserved Font Names \"Abyssinica\" and \"SIL\".\n \n Modern Gurage glyphs Copyright (c) 2021-2022 The Ge'ez Frontier Foundation.\n \n This Font Software is licensed under the SIL Open Font License, Version 1.1.\n This license is copied below, and is also available with a FAQ at:\n-https://scripts.sil.org/OFL\n+https://openfontlicense.org/\n \n \n "
+ },
+ {
+ "sha": "8d30ec7505089b67192f0d40d59c65728bdcb932",
+ "filename": "fonts/sil/abyssinicasil/README.txt",
+ "status": "modified",
+ "additions": 3,
+ "deletions": 6,
+ "changes": 9,
+ "blob_url": "https://github.com/silnrsi/fonts/blob/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2FREADME.txt",
+ "raw_url": "https://github.com/silnrsi/fonts/raw/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2FREADME.txt",
+ "contents_url": "https://api.github.com/repos/silnrsi/fonts/contents/fonts%2Fsil%2Fabyssinicasil%2FREADME.txt?ref=044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "patch": "@@ -9,7 +9,7 @@ Abyssinica SIL provides glyphs for a wide range of Ethiopic and Latin.\n Please read the online documentation to see what ranges are supported. \n \n Abyssinica SIL is released under the SIL Open Font License.\n-Abyssinica SIL is a trademark of SIL International.\n+Abyssinica SIL is a trademark of SIL Global.\n \t\n See the OFL and OFL-FAQ for details of the SIL Open Font License.\n See the FONTLOG for information on this and previous releases.\n@@ -71,14 +71,11 @@ glyphs (symbols) in a font and allow you to enter them by clicking on the\n glyph you want.\n \n Rendering:\n-This font is designed to work with either of two advanced font technologies, \n-Graphite or OpenType. To take advantage of the advanced typographic \n-capabilities of this font, you must be using applications that provide an\n-adequate level of support for Graphite or OpenType. \n+This font is designed to work with the OpenType font technology. To take advantage of the advanced typographic capabilities of this font, you must be using applications that provide an adequate level of support for OpenType. The OpenType advanced capabilities provide access to the variant character forms used in some languages.\n \n CONTACT\n ========\n-For more information please visit the Abyssinica SIL page on SIL International's\n+For more information please visit the Abyssinica SIL page on SIL Global's\n Computers and Writing systems website:\n https://software.sil.org/abyssinica/\n "
+ },
+ {
+ "sha": "290ddfca5f598d93efcfad44a124dec1464d2237",
+ "filename": "fonts/sil/abyssinicasil/documentation/about.html",
+ "status": "modified",
+ "additions": 67,
+ "deletions": 18,
+ "changes": 85,
+ "blob_url": "https://github.com/silnrsi/fonts/blob/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fabout.html",
+ "raw_url": "https://github.com/silnrsi/fonts/raw/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fabout.html",
+ "contents_url": "https://api.github.com/repos/silnrsi/fonts/contents/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fabout.html?ref=044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "patch": "@@ -15,35 +15,84 @@\n
Abyssinica SIL - About
\n \n
About this project
\n-
Abyssinica SIL is based on Ethiopic calligraphic traditions. The Ethiopic script is used for writing many of the languages of Ethiopia and Eritrea. This project is intended to provide a free and open font for all current languages and writing systems that use the Ethiopic script. It supports the complete range of Unicode characters for Ethiopic.
\n-
For more information on the visual characteristics of the font see Design.
\n+
Abyssinica SIL is based on Ethiopic calligraphic traditions. The\n+ Ethiopic script is used for writing many of the languages of\n+ Ethiopia and Eritrea. This project is intended to provide a free and\n+ open font for all current languages and writing systems that use the\n+ Ethiopic script. It supports the complete range of Unicode\n+ characters for Ethiopic.
\n+
For more information on the visual characteristics of the font\n+ see Design.
\n
Future plans
\n-
This font is actively maintained and improved, and recent changes to its development process will enable more frequent releases.
\n-
The highest priorities for future additions and enhancements are mainly driven by:
\n+
This font is actively maintained and improved, and recent changes\n+ to its development process will enable more frequent releases.
\n+
The highest priorities for future additions and enhancements are\n+ mainly driven by:
Requests from language communities using the fonts
\n
Needs of the linguistic and academic community
\n
\n-
Please send us your requests using the form on the font website. If you are interested in helping us make the font better see the Developer page.
\n+
Please send us your requests using the form on\n+ the font website. If you are interested in helping us make the\n+ font better see the Developer page.
\n
Announcement list
\n-
If you wish to receive announcements about updates to any of our SIL fonts, please subscribe to our SIL Font News Announcement List. This is an announcement-only list with messages approximately once a month. It does not allow any discussion.
\n+
If you wish to receive announcements about updates to any of our\n+ SIL fonts, please subscribe to our SIL\n+ Font News Announcement List. This is an announcement-only list\n+ with messages approximately once a month. It does not allow any\n+ discussion.
\n
You can subscribe using either of the two following options.
\n
\n-
If you use a Google profile and join the group, you will be able to access the group and control your subscription and notification options with a web browser. Make sure you are logged in to your Google profile and go to the SIL Font News Google Group. Click on Join group.
\n-
If you would rather not use a Google profile, you can subscribe any email address by sending a message to sil-font-news+subscribe@groups.sil.org and following the instructions you get in the confirmation message.
\n+
If you use a Google profile and join the group, you will be\n+ able to access the group and control your subscription and\n+ notification options with a web browser. Make sure you are logged in\n+ to your Google profile and go to the SIL\n+ Font News Google Group. Click on Join\n+ group.
\n+
If you would rather not use a Google profile, you can\n+ subscribe any email address by sending a message to sil-font-news+subscribe@groups.sil.org\n+ and following the instructions you get in the confirmation\n+ message.
\n
\n-
Our font announcements are also available through Twitter [@silfonts](https://twitter.com/silfonts).
\n+
Our font announcements are also available through X (formerly\n+ Twitter) @silfonts.
\n
Supporting the project
\n-
This font is provided at no cost, however it is expensive to produce and maintain. Please consider donating to SIL’s font development efforts to support future development. Go to SIL’s Give Direct page and designate your gift for Scripts & Fonts. Thank you!
\n-
About SIL International
\n-
SIL International is a global, faith-based nonprofit that works with local communities around the world to develop language solutions that expand possibilities for a better life.
\n-
We are involved in approximately 1,350 active language projects in 104 countries. These projects impact more than 1.1 billion people within 1,600 local communities. SIL’s work brings together more than 4,300 staff from 89 countries who work alongside thousands more local partners and community volunteers worldwide. Our services are available without regard to religious belief, political ideology, gender, race or ethnic background.
\n-
Our Vision: We long to see people flourishing in community using the languages they value most.
\n-
Our Mission: Inspired by God’s love, we advocate, build capacity, and work with local communities to apply language expertise that advances meaningful development, education, and engagement with Scripture.
These fonts are provided at no cost; however, they are expensive\n+ to produce and maintain. Please consider donating to SIL’s font\n+ development efforts to support future development. Go to SIL’s Give Direct page.\n+ Thank you!
\n+
About SIL Global
\n+
SIL Global is a global,\n+ faith-based nonprofit that works with local communities around the\n+ world to develop language solutions that expand possibilities for a\n+ better life.
\n+
We are involved in approximately 1,350 active language projects\n+ in 104 countries. These projects impact more than 1.1 billion people\n+ within 1,600 local communities. SIL’s work brings together more than\n+ 4,300 staff from 89 countries who work alongside thousands more\n+ local partners and community volunteers worldwide. Our services are\n+ available without regard to religious belief, political ideology,\n+ gender, race or ethnic background.
\n+
Our Vision: We long to see people flourishing in community using\n+ the languages they value most.
\n+
Our Mission: Inspired by God’s love, we advocate, build capacity,\n+ and work with local communities to apply language expertise that\n+ advances meaningful development, education, and engagement with\n+ Scripture.
This is a minor release. Changes for this version include the following:
\n+
This is a minor release. Changes for this version include the\n+ following:
\n+
Improved
\n
\n-
Fixed bug in TypeTuner support for cv46 tswa alternate
\n+
Adjusted glyph shapes for\n+
\n+
1214 ETHIOPIC SYLLABLE HHEE
\n+
1264 ETHIOPIC SYLLABLE BEE
\n+
126C ETHIOPIC SYLLABLE VEE
\n+
129C ETHIOPIC SYLLABLE NYEE
\n+
12DC ETHIOPIC SYLLABLE ZEE
\n+
1334 ETHIOPIC SYLLABLE PHEE
\n+
133C ETHIOPIC SYLLABLE TSEE
\n+
AB14 ETHIOPIC SYLLABLE DZEE
\n+
AB2C ETHIOPIC SYLLABLE BBEE
\n+
1E7E4 ETHIOPIC SYLLABLE HHYEE
\n+
1E7EA ETHIOPIC SYLLABLE HHWEE
\n+
\n+
Improve diacritic position to support multiple above\n+ diacritics
\n+
\n+
Added
\n+
\n+
Added gzi Ligature
\n+
2080 SUBSCRIPT ZERO
\n+
2081 SUBSCRIPT ONE
\n+
2082 SUBSCRIPT TWO
\n+
2083 SUBSCRIPT THREE
\n+
2084 SUBSCRIPT FOUR
\n+
2085 SUBSCRIPT FIVE
\n+
2086 SUBSCRIPT SIX
\n+
2087 SUBSCRIPT SEVEN
\n+
2088 SUBSCRIPT EIGHT
\n+
2089 SUBSCRIPT NINE
\n+
2460 CIRCLED DIGIT ONE
\n+
2461 CIRCLED DIGIT TWO
\n+
2462 CIRCLED DIGIT THREE
\n+
2463 CIRCLED DIGIT FOUR
\n+
2464 CIRCLED DIGIT FIVE
\n+
2465 CIRCLED DIGIT SIX
\n+
2466 CIRCLED DIGIT SEVEN
\n+
2467 CIRCLED DIGIT EIGHT
\n+
2468 CIRCLED DIGIT NINE
\n+
\n+
Remove
\n+
\n+
Graphite
\n
\n-
Known issues
\n+
Known issues
\n
\n
There are no known issues.
\n
\n-
Download the release packages from the Download Page.
\n+
Both desktop and web fonts are provided in a single,\n+ all-platforms package on the Download\n+ page.
\n \n \n "
+ },
+ {
+ "sha": "504ffd50c76d09f5e83a9edf6e51c162cbe450fb",
+ "filename": "fonts/sil/abyssinicasil/documentation/assets/css/theme.css",
+ "status": "modified",
+ "additions": 5,
+ "deletions": 5,
+ "changes": 10,
+ "blob_url": "https://github.com/silnrsi/fonts/blob/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fassets%2Fcss%2Ftheme.css",
+ "raw_url": "https://github.com/silnrsi/fonts/raw/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fassets%2Fcss%2Ftheme.css",
+ "contents_url": "https://api.github.com/repos/silnrsi/fonts/contents/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fassets%2Fcss%2Ftheme.css?ref=044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "patch": "@@ -1,8 +1,7 @@\n /*\n-This file is from the Abyssinica SIL project (https://software.sil.org/abyssinica/).\n-Copyright (c) 2000-2023 SIL International (https://www.sil.org/) with Reserved\n-Font Names \"Abyssinica\" and \"SIL\". This Font Software is licensed under the SIL\n-Open Font License, Version 1.1 (https://scripts.sil.org/OFL).\n+This file is from the SIL Fontdocs project (https://github.com/silnrsi/fontdocs).\n+Copyright (c) 2021-2024 SIL Global (https://www.sil.org/). This Font Software is\n+released under the MIT license (https://opensource.org/licenses/MIT).\n */\n html {\n font-family: sans-serif;\n@@ -38,7 +37,7 @@ body {\n font-weight: 400;\n line-height: 1.4;\n color: #000000;\n- text-align: left;\n+ text-align: start;\n background-color: #fff;\n }\n \n@@ -195,6 +194,7 @@ kbd{\n footer {\n margin-top: 2rem;\n margin-bottom: 1rem;\n+ color: #999999;\n }\n \n .affects {"
+ },
+ {
+ "sha": "b379540d709ecf7047cb72a274c6383d2edf5837",
+ "filename": "fonts/sil/abyssinicasil/documentation/assets/css/themepdf.css",
+ "status": "modified",
+ "additions": 5,
+ "deletions": 5,
+ "changes": 10,
+ "blob_url": "https://github.com/silnrsi/fonts/blob/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fassets%2Fcss%2Fthemepdf.css",
+ "raw_url": "https://github.com/silnrsi/fonts/raw/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fassets%2Fcss%2Fthemepdf.css",
+ "contents_url": "https://api.github.com/repos/silnrsi/fonts/contents/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fassets%2Fcss%2Fthemepdf.css?ref=044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "patch": "@@ -1,8 +1,7 @@\n /*\n-This file is from the Abyssinica SIL project (https://software.sil.org/abyssinica/).\n-Copyright (c) 2000-2023 SIL International (https://www.sil.org/) with Reserved\n-Font Names \"Abyssinica\" and \"SIL\". This Font Software is licensed under the SIL\n-Open Font License, Version 1.1 (https://scripts.sil.org/OFL).\n+This file is from the SIL Fontdocs project (https://github.com/silnrsi/fontdocs).\n+Copyright (c) 2021-2024 SIL Global (https://www.sil.org/). This Font Software is\n+released under the MIT license (https://opensource.org/licenses/MIT).\n */\n html {\n font-family: sans-serif;\n@@ -39,7 +38,7 @@ body {\n font-weight: 400;\n line-height: 1.4;\n color: #000000;\n- text-align: left;\n+ text-align: start;\n background-color: #fff;\n }\n \n@@ -194,6 +193,7 @@ kbd{\n footer {\n margin-top: 2rem;\n margin-bottom: 1rem;\n+ color: #999999;\n }\n \n .affects {"
+ },
+ {
+ "sha": "8d5d3d57300218062349567a784e011f0ebdf7c9",
+ "filename": "fonts/sil/abyssinicasil/documentation/assets/css/webfonts.css",
+ "status": "modified",
+ "additions": 2,
+ "deletions": 2,
+ "changes": 4,
+ "blob_url": "https://github.com/silnrsi/fonts/blob/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fassets%2Fcss%2Fwebfonts.css",
+ "raw_url": "https://github.com/silnrsi/fonts/raw/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fassets%2Fcss%2Fwebfonts.css",
+ "contents_url": "https://api.github.com/repos/silnrsi/fonts/contents/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fassets%2Fcss%2Fwebfonts.css?ref=044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "patch": "@@ -1,8 +1,8 @@\n /*\n This file is from the Abyssinica SIL project (https://software.sil.org/abyssinica/).\n-Copyright (c) 2000-2023 SIL International (https://www.sil.org/) with Reserved\n+Copyright (c) 2000-2024 SIL Global (https://www.sil.org/) with Reserved\n Font Names \"Abyssinica\" and \"SIL\". This Font Software is licensed under the SIL\n-Open Font License, Version 1.1 (https://scripts.sil.org/OFL).\n+Open Font License, Version 1.1 (https://openfontlicense.org/).\n */\n @font-face {\n font-family: AbyssinicaSIL-R;"
+ },
+ {
+ "sha": "4568a1031f809abf01c728fcb2d0a3362357128c",
+ "filename": "fonts/sil/abyssinicasil/documentation/assets/css/webfontsttf.css",
+ "status": "modified",
+ "additions": 2,
+ "deletions": 2,
+ "changes": 4,
+ "blob_url": "https://github.com/silnrsi/fonts/blob/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fassets%2Fcss%2Fwebfontsttf.css",
+ "raw_url": "https://github.com/silnrsi/fonts/raw/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fassets%2Fcss%2Fwebfontsttf.css",
+ "contents_url": "https://api.github.com/repos/silnrsi/fonts/contents/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fassets%2Fcss%2Fwebfontsttf.css?ref=044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "patch": "@@ -1,8 +1,8 @@\n /*\n This file is from the Abyssinica SIL project (https://software.sil.org/abyssinica/).\n-Copyright (c) 2000-2023 SIL International (https://www.sil.org/) with Reserved\n+Copyright (c) 2000-2024 SIL Global (https://www.sil.org/) with Reserved\n Font Names \"Abyssinica\" and \"SIL\". This Font Software is licensed under the SIL\n-Open Font License, Version 1.1 (https://scripts.sil.org/OFL).\n+Open Font License, Version 1.1 (https://openfontlicense.org/).\n */\n @font-face {\n font-family: AbyssinicaSIL-R;"
+ },
+ {
+ "sha": "f6bc4d0ac83bdea5684132e9b384b14a9c4bd178",
+ "filename": "fonts/sil/abyssinicasil/documentation/charset.html",
+ "status": "modified",
+ "additions": 64,
+ "deletions": 76,
+ "changes": 140,
+ "blob_url": "https://github.com/silnrsi/fonts/blob/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fcharset.html",
+ "raw_url": "https://github.com/silnrsi/fonts/raw/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fcharset.html",
+ "contents_url": "https://api.github.com/repos/silnrsi/fonts/contents/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fcharset.html?ref=044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "patch": "@@ -14,7 +14,22 @@\n \n
Because the majority of the PUA characters have now been encoded into Unicode, or they were considered glyph variants, all PUA characters in the font have been removed with the exception of U+E494 () and U+E496 (). Some of the PUA codepoints were actually glyph variants of characters already encoded in Unicode. These are now available through OpenType Character Variants, Graphite features, or TypeTuned fonts. See Font Features.
\n-
PUA characters that were previously in the font are documented here:
A selection of characters from the General Punctuation block,\n+ such as various-sized spaces, are also supported; a utility such as\n+ SIL ViewGlyph\n+ can be used to examine the exact repertoire of this font.
\n+
¹Inclusion of basic Latin repertoire is provided as a\n+ convenience, e.g., for use in menus or for displaying markup in text\n+ files; these fonts are not intended for extensive Latin script\n+ use.
\n+
Private-use (PUA)\n+ characters
\n+
Because the majority of the PUA characters have now been encoded\n+ into Unicode, or they were considered glyph variants, all PUA\n+ characters in the font have been removed with the exception of\n+ U+E494 () and U+E496\n+ (). Some of the PUA\n+ codepoints were actually glyph variants of characters already\n+ encoded in Unicode. These are now available through OpenType\n+ Character Variants or TypeTuned fonts. See Font Features.
\n+
PUA characters that were previously in the font are documented\n+ here:
Abyssinica SIL is a mature product with no major changes anticipated. We will be releasing maintenance updates to fix bugs.
\n+
Abyssinica SIL is a mature product with no major changes\n+ anticipated. We will be releasing maintenance updates to fix\n+ bugs.
\n
Welcome font developers!
\n-
We welcome other developers who wish to get involved in supporting and enhancing this font.
\n-
Abyssinica SIL uses kerning to give a better presentation of characters which might otherwise have too much space between them. If you are a font developer and wish to include kerning in your font, the list of kerning pairs is available here: Ethiopic Kerning Pairs
\n-
Permissions granted by the OFL
\n-
SIL’s fonts are licensed according to the terms of the SIL Open Font License. The OFL allows the fonts to be used, studied, modified and redistributed freely as long as they are not sold by themselves. For details see the OFL.txt and OFL-FAQ.txt files in the package.
\n-
Building the fonts from source code
\n-
The latest source files are available in a Github project.
\n-
Font sources are in the UFO3 format with font family structures defined using designspace. OpenType source code is stored in the .fea format in the UFO (features.fea) but is maintained in a separate file using the more efficient and powerful .feax format.
\n-
The fonts are built using a completely free and open source workflow using industry-standard tools (fontools), a package of custom python scripts (pysilfont), and a build and packaging system (Smith). The whole system is available in a preconfigured virtual machine using VirtualBox and Vagrant.
\n-
Full instructions for setting up the tools and building SIL fonts are available on a dedicated web site: SIL Font Development Notes.
\n-
Contributing to the project
\n-
We warmly welcome contributions to the fonts, such as new glyphs, enhanced smart font code, or bug fixes. The brief overview of contributing changes is a good place to begin. The next step is to contact us by responding to an existing issue or creating an issue in the Github repository and expressing your interest. We can then work together to plan and integrate your contributions.
\n-
To enable us to accept contributions in a way that honors your contribution and respects your copyright while preserving long-term flexibility for open source licensing, you would also need to agree to the SIL International Contributor License Agreement for Font Software (v1.0) prior to sending us your contribution. To read more about this requirement and find out how to submit the required form, please visit the CLA information page.
\n+
We welcome other developers who wish to get involved in\n+ supporting and enhancing these fonts or who want to modify them.
\n+
Abyssinica SIL uses kerning to give a better presentation of\n+ characters which might otherwise have too much space between them.\n+ If you are a font developer and wish to include kerning in your\n+ font, the list of kerning pairs is available here: Ethiopic\n+ Kerning Pairs
\n+
Permissions granted by the\n+ OFL
\n+
SIL’s fonts are licensed according to the terms of the SIL Open Font License. The\n+ OFL allows the fonts to be used, studied, modified and redistributed\n+ freely as long as they are not sold by themselves. For details see\n+ the OFL.txt and OFL-FAQ.txt files in the package.
Font sources are in the UFO3 format\n+ with font family structures defined using designspace.\n+ OpenType source code is stored in the .fea\n+ format in the UFO (features.fea) but is maintained in a separate\n+ file using the more efficient and powerful .feax\n+ format.
\n+
The fonts are built using a completely free and open source\n+ workflow using industry-standard tools (fonttools), a\n+ package of custom python scripts (pysilfont), and a\n+ build and packaging system (Smith). The whole\n+ toolchain is available as a Docker container.
\n+
Full instructions for setting up the tools and building SIL fonts\n+ are available on a dedicated web site: SIL Font Development\n+ Guide.
\n+
Contributing to the\n+ project
\n+
We warmly welcome contributions to the fonts, such as new glyphs,\n+ enhanced smart font code, or bug fixes. The brief\n+ overview of contributing changes is a good place to begin. The\n+ next step is to contact us by responding to an existing issue or\n+ creating an issue in the Github repository and expressing your\n+ interest. We can then work together to plan and integrate your\n+ contributions.
\n+
To enable us to accept contributions in a way that honors your\n+ contribution and respects your copyright while preserving long-term\n+ flexibility for open source licensing, you would also need to agree\n+ to the SIL Global Contributor License Agreement for Font\n+ Software (v1.0) prior to sending us your contribution. To\n+ read more about this requirement and find out how to submit the\n+ required form, please visit the CLA information\n+ page.
If I use the font on a web page do I have to include an acknowledgement?
\n+
If I use the font on a web page do I have to include an\n+ acknowledgement?
\n
The full OFL-FAQ.txt is also included in the font package.
\n
\n
\n-
Here are a few of the most frequently asked questions specifically regarding Abyssinica SIL:
\n-
What is so special about Abyssinica SIL?
\n-
This font is designed to work with two advanced font technologies, Graphite and OpenType. To take advantage of the advanced typographic capabilities of this font, you must be using applications that provide an adequate level of support for Graphite or OpenType. These advanced capabilities provide access to the variant character forms used in some languages.
\n-
Do you supply a keyboard to use with Abyssinica SIL?
\n-
No keyboards are supplied with the font. However, there are suggested keyboards listed in Resources.
\n-
My language uses variant forms of some Ethiopic characters. How do I type these using the Abyssinica SIL font? How do I use features?
\n-
You should type the character the same way you would type the standard form of the character. Then, you need to select the variants to be displayed. If your application supports Graphite or the OpenType Character Variant features, you can use these to access the font features built into the font. See Font Features page for more details.
\n-
If your application does not support Graphite features or the OpenType Character Variants, you can use TypeTunerWeb to customize the font with the variants you require. See Font Features page for more details.
\n-
Why did you remove the Stylistic Sets from ver. 2.000 of the Abyssinica SIL font?
\n-
Originally we added the Stylistic Sets because there was not a good solution for accessing the glyph variants in the font. At one point we also tried encoding them in the Private Use Area (PUA). PUA characters have now almost all been unencoded since the characters are now either encoded in Unicode or the variants are available through Character Variants. The Stylistic Sets were implemented inconsistently, and because of that we chose to remove them rather than attempt to fix them. If you still wish to use a font with Stylistic Sets, ver. 1.500 is still available on the Previous Versions page.
\n-
I have a copy of the SIL Abyssinica font. Can you tell me how this differs from Abyssinica SIL?
\n-
It is best to upgrade to Abyssinica SIL. SIL Abyssinica (and SIL Abyssinica U and SIL Abyssinica G) was an early, unreleased version of Abyssinica SIL. Although a Unicode font, it only supported Unicode 3.0 and thus had a number of PUA characters in it which have since been added to Unicode 4.1 and 6.0. You should convert your data to Unicode 6.0 and use Abyssinica SIL. A mapping file to convert your data from PUA to Unicode 6.0 is available here: sil-pua-unicode. If you do not convert your data to official Unicode codepoints you will never be able to use another Ethiopic font because those are Private codepoints and other fonts do not support them.
\n-
You have characters which are encoded in the PUA area. Is there any likelihood that these will ever be in Unicode? If so, will you update Abyssinica SIL?
\n-
Version 1.500 incorporated all characters that are in Unicode 6.0.
\n-
With version 2.000 we removed almost all of the PUA characters in the font because they are either available through their official Unicode codepoints or through the Character Variants.
\n-
I would like to bundle Abyssinica SIL with my application - can I?
\n-
The SIL Open Font License allows bundling with applications, even commercial ones, with some restrictions.
\n+
Here are a few of the most frequently asked questions\n+ specifically regarding Abyssinica SIL:
\n+
What is so\n+ special about Abyssinica SIL?
\n+
This font is designed to work with the OpenType font technology.\n+ To take advantage of the advanced typographic capabilities of this\n+ font, you must be using applications that provide an adequate level\n+ of support for OpenType. The advanced OpenType capabilities provide\n+ access to the variant character forms used in some languages.
\n+
Why did\n+ you remove Graphite from Abyssinica SIL?
\n+
Until version 2.300 this font included the Graphite advanced font\n+ technology. The OpenType features completely support everything that\n+ Graphite supported. Removing Graphite reduces the size of the font\n+ and some of the complexities of building the font.
\n+
Do\n+ you supply a keyboard to use with Abyssinica SIL?
\n+
No keyboards are supplied with the font. However, there are\n+ suggested keyboards listed in Resources.
\n+
My\n+ language uses variant forms of some Ethiopic characters. How do I\n+ type these using the Abyssinica SIL font? How do I use\n+ features?
\n+
You should type the character the same way you would type the\n+ standard form of the character. Then, you need to select the\n+ variants to be displayed. If your application supports the OpenType\n+ Character Variant features, you can use these to access the font\n+ features built into the font. See Font\n+ Features page for more details.
\n+
If your application does not support the OpenType Character\n+ Variants, you can use TypeTunerWeb to customize the font with the\n+ variants you require. See Font Features\n+ page for more details.
\n+
Why\n+ did you remove the Stylistic Sets from ver. 2.000 of the Abyssinica\n+ SIL font?
\n+
Originally we added the Stylistic Sets because there was not a\n+ good solution for accessing the glyph variants in the font. At one\n+ point we also tried encoding them in the Private Use Area (PUA). PUA\n+ characters have now almost all been unencoded since the characters\n+ are now either encoded in Unicode or the variants are available\n+ through Character Variants. The Stylistic Sets were\n+ implemented inconsistently, and because of that we chose to remove\n+ them rather than attempt to fix them. If you still wish to use a\n+ font with Stylistic Sets, ver. 1.500 is still available on the Previous Versions page.
\n+
I\n+ have a copy of the SIL Abyssinica font. Can you\n+ tell me how this differs from Abyssinica\n+ SIL?
\n+
It is best to upgrade to Abyssinica SIL.\n+ SIL Abyssinica, SIL Abyssinica U,\n+ and SIL Abyssinica G were early, unreleased\n+ versions of Abyssinica SIL. Although Unicode fonts,\n+ they only supported Unicode 3.0 and thus had a number of PUA\n+ characters in them which have since been added to Unicode 4.1 and\n+ 6.0. You should convert your data to Unicode and use\n+ Abyssinica SIL. A mapping file to convert your data\n+ from PUA to Unicode 6.0 is available here: sil-pua-unicode.\n+ If you do not convert your data to official Unicode codepoints you\n+ will never be able to use another Ethiopic font because those are\n+ Private codepoints and other fonts do not support\n+ them.
\n+
You\n+ have characters which are encoded in the PUA area. Is there any\n+ likelihood that these will ever be in Unicode? If so, will you\n+ update Abyssinica SIL?
\n+
Version 1.500 incorporated all characters that are in Unicode\n+ 6.0.
\n+
With version 2.000 we removed almost all of the PUA characters in\n+ the font because they are either available through their official\n+ Unicode codepoints or through the Character Variants.
\n+
I\n+ would like to bundle Abyssinica SIL with my application - can\n+ I?
\n+
The SIL Open Font\n+ License allows bundling with applications, even commercial ones,\n+ with some restrictions.
Abyssinica SIL is a TrueType font with smart font capabilities added using OpenType and Graphite font technologies. The Ethiopic script does not require much rendering except for some combining marks for gemination and vowel length. However, there are some glyph variations for the Ethiopic script. Some applications let the user control certain features such as Character Variants to turn on the rendering of variant characters. However, at this point, most applications do not make use of those features so another solution is needed to show the variant characters. TypeTuner creates tuned fonts that use the variant glyph in place of the standard glyph. TypeTuner also provides the ability to turn on support for the Sebat Bet Gurage and Gumuz languages variants.
\n-
See Using Font Features. Although that page is not targeted at Ethiopic support, it does provide a comprehensive list of applications that make full use of the OpenType and Graphite font technologies.
\n-
Advanced typographic capabilities
\n-
This font supports various advanced typographic capabilities using the Graphite and OpenType font technologies.
\n+
Abyssinica SIL is a TrueType font with smart font capabilities\n+ added using the OpenType font technology. The Ethiopic script does\n+ not require much rendering except for some combining marks for\n+ gemination and vowel length. However, there are some glyph\n+ variations for the Ethiopic script. Some applications let the user\n+ control certain features such as Character Variants to turn on the\n+ rendering of variant characters. However, at this point, most\n+ applications do not make use of those features so another solution\n+ is needed to show the variant characters. TypeTuner\n+ creates tuned fonts that use the variant glyph in place of the\n+ standard glyph. TypeTuner also provides the ability to turn on\n+ support for the Sebat Bet Gurage and Gumuz languages variants.
\n+
See Using Font\n+ Features. Although that page is not targeted at Ethiopic\n+ support, it does provide a comprehensive list of applications that\n+ make full use of the OpenType font technology.
\n+
Advanced typographic\n+ capabilities
\n+
This font supports various advanced typographic capabilities\n+ using the OpenType font technology.
\n
\n-
Auto placement of diacritics (one level only) on Ethiopic syllables only (not on Latin characters)
\n+
Auto placement of diacritics on Ethiopic syllables only (not on\n+ Latin characters)
\n
Kerning of almost 200 pairs of Ethiopic syllables
\n-
OpenType Character Variants or Graphite features (alternately-designed glyphs are also provided for a number of characters for use in particular contexts)
\n-
OpenType and Graphite support for the Sebat Bet Gurage [sgw] and Gumuz [guk] languages
\n+
OpenType Character Variants (alternately-designed glyphs are\n+ also provided for a number of characters for use in particular\n+ contexts)
\n+
OpenType support for the Sebat Bet Gurage [sgw] and Gumuz [guk]\n+ languages
\n
\n-
These capabilities are available in any application that supports the Graphite technology. They are also available via the OpenType technology, though this requires applications that provide a sufficient level of support for OpenType Character Variant features.
\n+
These capabilities are available in any application that supports\n+ OpenType technology, though this requires applications that provide\n+ a sufficient level of support for OpenType Character Variant\n+ features.
\n
A sample of diacritic placement and kerning is shown below:
\n- \n+ \n+ \n \n Abyssinica SIL Sample - Diacritic placement and Kerning\n \n-
This page uses web fonts (WOFF2) to demonstrate font features and should display correctly in all modern browsers. For a more concise example of how to use Abyssinica SIL as a web font see Abyssinica SIL Webfont Example. For detailed information see Using SIL Fonts on Web Pages.
\n-
If this document is not displaying correctly a PDF version is also provided in the documentation/pdf folder of the release package.
\n+
This page uses web fonts (WOFF2) to demonstrate font features and\n+ should display correctly in all modern browsers. For a more concise\n+ example of how to use Abyssinica SIL as a web font see Abyssinica SIL\n+ Webfont Example. For detailed information see Using SIL Fonts on\n+ Web Pages.
\n+
If this document is not displaying correctly a PDF version is\n+ also provided in the documentation/pdf folder of the release\n+ package.
\n
Customizing with TypeTuner
\n-
For applications that do not make use of Graphite or the OpenType Stylistic Sets feature, you can now download fonts customized with the variant glyphs you choose. Read the Font Features page, visit TypeTuner Web, then to choose the variants and download your font.
\n+
For applications that do not make use of the OpenType Character\n+ Variant features, you can now download fonts customized with the\n+ variant glyphs you choose. Read the Font\n+ Features page, visit TypeTuner Web,\n+ then to choose the variants and download your font.
\n
Complete feature list
\n-
There are some Ethiopic character shape differences in different Ethiopian languages. These can be accessed by using Graphite features, OpenType Character Variants, or language support for Sebat Bet Gurage and Gumuz languages. The documents below can be downloaded in order to see all the user-selectable font features that are available in the font. The feature names, feature ids, settings and examples are provided.
\n-
Test rendering engine choice
\n-
Here is a simple test to see if Graphite is working in your browser. If it is, the following will say \"RenderingGraphite\". If your browser does not support Graphite it should say \"RenderingOpentype\". Firefox is currently the only browser that supports Graphite. See the instructions on how to enable Graphite in Firefox.
\n-
\n- \n-
\n-
Check
\n-
RenderingUnknown
\n-
\n- \n-
\n+
There are some Ethiopic character shape differences in different\n+ Ethiopian languages. These can be accessed by using OpenType\n+ Character Variants or language support for Sebat Bet Gurage and\n+ Gumuz languages. The documents below can be downloaded in order to\n+ see all the user-selectable font features that are available in the\n+ font. The feature names, feature ids, settings and examples are\n+ provided.
Alone, John Philip Herbert Mackenzie. 1946 (Fourth edition). The Alone-Stokes Short Manual of the Amharic Language (with vocabularies). Macmillan and Co. Limited: London.
Cohen, Marcel. 1970 Seconde edition. Traité de langue amharique (Abyssinie). Institut d'ethnologie: Paris.
\n-
Leslau, Wolf. 1966. Ethiopians Speak: Studies in Cultural Background. Part 2: Chaha. University of California Publication. Near Eastern Studies, Volume 9. University of California Press: Berkeley
\n-
Praetorius, Franz. 1955. Aethiopische Grammatik mit Paradigmen, Litteratur, Chrestomathie und Glossar. Frederick Ungar Publishing Co. New York.
\n-
¹Chaîne (p 3), Cohen (table 2) ²Cohen (table 2) ³Gumuz language preference ⁴Alone-Stokes, Chaîne (p 3), Cohen (table 1) ⁵Chaîne (p 3) ⁶Archaic Oromo language preference ⁷Sebat Bet language preference ⁸Alone-Stokes (inside back cover) ⁹Bilen language preference ¹⁰Praetorius (p 6) ¹¹Leslau
\n+
Alone, John Philip Herbert Mackenzie. 1946 (Fourth edition).\n+ The Alone-Stokes Short Manual of the Amharic Language (with\n+ vocabularies). Macmillan and Co. Limited: London.
Cohen, Marcel. 1970 Seconde edition. Traité de langue\n+ amharique (Abyssinie). Institut d'ethnologie: Paris.
\n+
Leslau, Wolf. 1966. Ethiopians Speak: Studies in Cultural\n+ Background. Part 2: Chaha. University of California\n+ Publication. Near Eastern Studies, Volume 9. University of\n+ California Press: Berkeley
\n+
Praetorius, Franz. 1955. Aethiopische Grammatik mit\n+ Paradigmen, Litteratur, Chrestomathie und Glossar. Frederick\n+ Ungar Publishing Co. New York.
\n+
¹Chaîne (p 3), Cohen (table 2) ²Cohen (table 2) ³Gumuz language\n+ preference ⁴Alone-Stokes, Chaîne (p 3), Cohen (table 1) ⁵Chaîne (p\n+ 3) ⁶Archaic Oromo language preference ⁷Sebat Bet language preference\n+ ⁸Alone-Stokes (inside back cover) ⁹Bilen language preference\n+ ¹⁰Praetorius (p 6) ¹¹Leslau
Thank you for your interest in the Abyssinica SIL font. This font supports the broad variety of writing systems that use the Ethiopic script.
\n-
This documentation is a set of HTML pages that can be viewed in any modern web browser. PDF versions of these pages are also provided. This content, plus download links and a contact form, are available from the Abyssinica SIL site.
\n+
Thank you for your interest in the Abyssinica SIL font. This font\n+ supports the broad variety of writing systems that use the Ethiopic\n+ script.
\n+
This documentation is a set of HTML pages that can be viewed in\n+ any modern web browser. PDF versions of these pages are also\n+ provided. This content, plus download links and a contact form, are\n+ available from the Abyssinica SIL\n+ site.
\n
\n-
About — Information about this project and SIL International
This font is supported by all major operating systems (macOS, Windows, Linux-based, iOS, and Android), however the extent of that support depends on the individual OS and application.
\n+
This font is supported by all major operating systems (macOS,\n+ Windows, Linux-based, iOS, and Android), however the extent of that\n+ support depends on the individual OS and application.
\n
Installation
\n-
Install the font by decompressing the .zip archive and installing the font using the standard font installation process for .ttf (TrueType/OpenType) fonts for your platform. For additional tips see the help page on Font installation.
\n-
Keyboarding and character set support
\n-
This font does not include keyboards or other software for entering text. To type the symbols in this font use the keyboarding systems provided in your OS or use a separate utility. SIL’s Keyman is a cross-platform keyboarding system and a number of Ethiopic keyboards are available:
\n+
Install the fonts by decompressing the .zip archive and\n+ installing the fonts using the standard font installation process\n+ for .ttf (TrueType/OpenType) fonts for your platform. For additional\n+ tips see the help page on Font\n+ installation.
\n+
Keyboarding and\n+ character set support
\n+
This font does not include keyboards or other software for\n+ entering text. To type the symbols in this font use the keyboarding\n+ systems provided in your OS or use a separate utility. SIL’s Keyman is a cross-platform\n+ keyboarding system and a number of Ethiopic keyboards are\n+ available:
Various other means may be available for different operating-system platforms to create additional input methods. For instance, Windows (Vista and above) provides an Ethiopic IME.
See Character set support for details of the Unicode characters supported by this font.
\n-
Rendering and application support
\n-
This font will work normally like any other font in most applications. If the writing system requires special diacritic positioning the application/OS will need to support OpenType.
\n-
Abyssinica SIL is designed to work with two advanced font technologies, Graphite and OpenType. To take advantage of the advanced typographic capabilities of this font, you must be using applications that provide an adequate level of support for Graphite or OpenType.
Various other means may be available for different\n+ operating-system platforms to create additional input methods. For\n+ instance, Windows (Vista and above) provides an Ethiopic IME.
See Character set support for details\n+ of the Unicode characters supported by this font.
\n+
Rendering and application\n+ support
\n+
This font will work normally like any other font in most\n+ applications. If the writing system requires special diacritic\n+ positioning the application/OS will need to support OpenType.
\n+
If special font features are to be activated the application will\n+ need to provide a way to turn on the feature or choose the feature\n+ setting. Details of current application support, and specific\n+ techniques for activating features, are on the Using Font\n+ Features help page.
\n+
Although this current font supports only OpenType, previous\n+ versions provided support for the Graphite technology. Graphite was\n+ supported through version 2.2. These older versions remain available\n+ from our Previous\n+ Versions archive.
\n
Web fonts
\n-
Web font versions of this font (in WOFF and WOFF2 formats) are available in the web folder. These can be copied to a web server and used as fonts on web pages. A very basic HTML/CSS demo page is also included. For more information on the options and techniques available for using these fonts on web pages see Using SIL Fonts on Web Pages.
\n+
Web font versions of these fonts (in WOFF and WOFF2 formats) are\n+ available in the web folder. These can be copied to a\n+ web server and used as fonts on web pages. A very basic HTML/CSS\n+ demo page is also included. For more information on the options and\n+ techniques available for using these fonts on web pages see Using SIL Fonts on\n+ Web Pages.
In order to use this font with existing data that was created for use with fonts developed using custom-encoded fonts, it is necessary to re-type or convert data to produce data that is encoded in conformance with the Unicode Standard. SIL Converters and/or TECkit can be used for character encoding conversion. TECkit allows users to write their own custom conversion mappings.
\n-
Three TECkit mapping files (compiled and uncompiled) are available as a separate download SIL-Ethiopia (Latin to Fidel) Unicode mapping. They are intended for use where text has been input “phonetically” as a syllable (\"be\", \"ppii\", etc.) and conversion to fidel is desired (U+1264 ቤ, U+1352 ፒ, etc.).
\n-
If you used an earlier version of the Abyssinica SIL font, and used some of the Private Use Area (PUA) codepoints in your data, you may wish to use the PUA to Unicode mapping file to convert your data from PUA codepoints to Unicode 6.0.
\n-
The TECkit package is available for download from SIL’s TECkit Web site.
\n-
The SIL Converters package is available for download from SIL’s SIL Converters Web site.
In order to use this font with existing data that was created for\n+ use with fonts developed using custom-encoded fonts, it is necessary\n+ to re-type or convert data to produce data that is encoded in\n+ conformance with the Unicode Standard. SIL Converters\n+ and/or TECkit can be\n+ used for character encoding conversion. TECkit allows users to write\n+ their own custom conversion mappings.
\n+
Three TECkit\n+ mapping files (compiled and uncompiled) are available as a separate\n+ download SIL-Ethiopia\n+ (Latin to Fidel) Unicode mapping. They are intended for use\n+ where text has been input “phonetically” as a syllable (\"be\",\n+ \"ppii\", etc.) and conversion to fidel is desired (U+1264 ቤ, U+1352\n+ ፒ, etc.).
\n+
If you used an earlier version of the Abyssinica\n+ SIL font, and used some of the Private Use Area (PUA)\n+ codepoints in your data, you may wish to use the PUA\n+ to Unicode mapping file to convert your data from PUA codepoints\n+ to Unicode 6.0.
\n+
The TECkit package is available for download from SIL’s TECkit Web site.
\n+
The SIL Converters package is available for download from SIL’s\n+ SIL Converters\n+ Web site.
This document demonstrates all of the characters in the font. It is organized by Unicode block. Alternate glyphs that are available through features are demonstrated in the Features document. At the end is a sample demonstrating an example of running text.
\n+
This document demonstrates all of the characters in the font. It\n+ is organized by Unicode block. Alternate glyphs that are available\n+ through features are demonstrated in the Features document. At the end is a sample\n+ demonstrating an example of running text.
\n \n \n \n "
+ },
+ {
+ "sha": "b39193ef538fa0e5f31d89799b3bd2930300d2f6",
+ "filename": "fonts/sil/abyssinicasil/documentation/source/about.md",
+ "status": "modified",
+ "additions": 5,
+ "deletions": 6,
+ "changes": 11,
+ "blob_url": "https://github.com/silnrsi/fonts/blob/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fabout.md",
+ "raw_url": "https://github.com/silnrsi/fonts/raw/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fabout.md",
+ "contents_url": "https://api.github.com/repos/silnrsi/fonts/contents/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fabout.md?ref=044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "patch": "@@ -1,6 +1,6 @@\n ---\n title: Abyssinica SIL - About\n-fontversion: 2.201\n+fontversion: 2.300\n ---\n \n ## About this project\n@@ -9,7 +9,6 @@ Abyssinica SIL is based on Ethiopic calligraphic traditions. The Ethiopic script\n \n For more information on the visual characteristics of the font see [Design](design.md).\n \n-\n ## Future plans\n \n This font is actively maintained and improved, and recent changes to its development process will enable more frequent releases.\n@@ -32,15 +31,15 @@ You can subscribe using either of the two following options.\n \n - If you would rather not use a Google profile, you can subscribe any email address by sending a message to [sil-font-news+subscribe@groups.sil.org](mailto:sil-font-news+subscribe@groups.sil.org) and following the instructions you get in the confirmation message.\n \n-Our font announcements are also available through Twitter [@silfonts](https://twitter.com/silfonts).\n+Our font announcements are also available through X (formerly Twitter) [\\@silfonts](https://x.com/silfonts).\n \n ## Supporting the project\n \n-This font is provided at no cost, however it is expensive to produce and maintain. Please consider donating to SIL’s font development efforts to support future development. Go to [SIL’s Give Direct page](https://donate.givedirect.org/?cid=13536&n=206909) and designate your gift for _Scripts & Fonts_. **Thank you!** \n+These fonts are provided at no cost; however, they are expensive to produce and maintain. Please consider donating to SIL’s font development efforts to support future development. Go to [SIL’s Give Direct page](https://give.sil.org/give/485238). **Thank you!** \n \n-## About SIL International\n+## About SIL Global\n \n-[SIL International](https://www.sil.org/) is a global, faith-based nonprofit that works with local communities around the world to develop language solutions that expand possibilities for a better life. \n+[SIL Global](https://www.sil.org/) is a global, faith-based nonprofit that works with local communities around the world to develop language solutions that expand possibilities for a better life. \n \n We are involved in approximately 1,350 active language projects in 104 countries. These projects impact more than 1.1 billion people within 1,600 local communities. SIL’s work brings together more than 4,300 staff from 89 countries who work alongside thousands more local partners and community volunteers worldwide. Our services are available without regard to religious belief, political ideology, gender, race or ethnic background.\n "
+ },
+ {
+ "sha": "6d0cba86de8fc184cc570b992b8f07c303a09d1a",
+ "filename": "fonts/sil/abyssinicasil/documentation/source/announcement.md",
+ "status": "modified",
+ "additions": 44,
+ "deletions": 4,
+ "changes": 48,
+ "blob_url": "https://github.com/silnrsi/fonts/blob/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fannouncement.md",
+ "raw_url": "https://github.com/silnrsi/fonts/raw/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fannouncement.md",
+ "contents_url": "https://api.github.com/repos/silnrsi/fonts/contents/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fannouncement.md?ref=044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "patch": "@@ -1,14 +1,54 @@\n ---\n title: Abyssinica SIL - Announcement\n-fontversion: 2.201\n+fontversion: 2.300\n ---\n \n This is a minor release. Changes for this version include the following:\n \n-- Fixed bug in TypeTuner support for cv46 tswa alternate\n+#### Improved\n \n-#### Known issues\n+- Adjusted glyph shapes for\n+ - 1214 ETHIOPIC SYLLABLE HHEE\n+ - 1264 ETHIOPIC SYLLABLE BEE\n+ - 126C ETHIOPIC SYLLABLE VEE\n+ - 129C ETHIOPIC SYLLABLE NYEE\n+ - 12DC ETHIOPIC SYLLABLE ZEE\n+ - 1334 ETHIOPIC SYLLABLE PHEE\n+ - 133C ETHIOPIC SYLLABLE TSEE\n+ - AB14 ETHIOPIC SYLLABLE DZEE\n+ - AB2C ETHIOPIC SYLLABLE BBEE\n+ - 1E7E4 ETHIOPIC SYLLABLE HHYEE\n+ - 1E7EA ETHIOPIC SYLLABLE HHWEE\n+- Improve diacritic position to support multiple above diacritics\n+\n+#### Added\n+\n+- Added gzi Ligature\n+- 2080 SUBSCRIPT ZERO\n+- 2081 SUBSCRIPT ONE\n+- 2082 SUBSCRIPT TWO\n+- 2083 SUBSCRIPT THREE\n+- 2084 SUBSCRIPT FOUR\n+- 2085 SUBSCRIPT FIVE\n+- 2086 SUBSCRIPT SIX\n+- 2087 SUBSCRIPT SEVEN\n+- 2088 SUBSCRIPT EIGHT\n+- 2089 SUBSCRIPT NINE\n+- 2460 CIRCLED DIGIT ONE\n+- 2461 CIRCLED DIGIT TWO\n+- 2462 CIRCLED DIGIT THREE\n+- 2463 CIRCLED DIGIT FOUR\n+- 2464 CIRCLED DIGIT FIVE\n+- 2465 CIRCLED DIGIT SIX\n+- 2466 CIRCLED DIGIT SEVEN\n+- 2467 CIRCLED DIGIT EIGHT\n+- 2468 CIRCLED DIGIT NINE\n+\n+#### Remove\n+- Graphite\n+\n+### Known issues\n \n - There are no known issues.\n \n-Download the release packages from the [Download Page](https://software.sil.org/abyssinica/download/).\n+Both desktop and web fonts are provided in a single, all-platforms package on the [Download page](https://software.sil.org/abyssinica/download)."
+ },
+ {
+ "sha": "cbbd529df86fe739923cc83b3d063b9031b29f7d",
+ "filename": "fonts/sil/abyssinicasil/documentation/source/charset.md",
+ "status": "modified",
+ "additions": 17,
+ "deletions": 27,
+ "changes": 44,
+ "blob_url": "https://github.com/silnrsi/fonts/blob/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fcharset.md",
+ "raw_url": "https://github.com/silnrsi/fonts/raw/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fcharset.md",
+ "contents_url": "https://api.github.com/repos/silnrsi/fonts/contents/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fcharset.md?ref=044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "patch": "@@ -1,44 +1,34 @@\n ---\n title: Abyssinica SIL - Character Set Support\n-fontversion: 2.201\n+fontversion: 2.300\n ---\n \n This font contains complete coverage of all the characters defined in Unicode for Ethiopic. The Ethiopic script is used for writing many of the languages of Ethiopia and Eritrea. [Ethiopic (U+1200..U+137F)](https://www.unicode.org/charts/PDF/U1200.pdf) was added to Unicode 3.0. [Ethiopic Supplement (U+1380..U+139F)](https://www.unicode.org/charts/PDF/U1380.pdf) and [Ethiopic Extended (U+2D80..U+2DDF)](https://www.unicode.org/charts/PDF/U2D80.pdf) were added to Unicode 4.1. [Ethiopic Extended-A (U+AB00..U+AB2F)](https://www.unicode.org/charts/PDF/UAB00.pdf) was added to Unicode 6.0. [Ethiopic Extended-B U+1E7E0..U+1E7FF)](https://www.unicode.org/charts/PDF/U1E7E0.pdf) was added to Unicode 14.0. *Abyssinica SIL* supports all Ethiopic characters which are in Unicode. As far as we are aware, all languages using the Ethiopic script are now fully represented in Unicode. \n \n-\n ## Supported characters\n \n The following character ranges are supported by this font:\n \n Unicode block | Abyssinica SIL support\n-------------- | ---------------\n-C0 Controls and Basic Latin|U+0020..U+007E\n-C1 Controls and Latin-1 Supplement|U+00A0..U+00FF\n-Latin Extended-A|U+0131, U+0152..U+0153, U+0160..U+0161, U+0178, U+017D..U+017E\n-Latin Extended-B|U+0192\n-Spacing Modifier Letters|U+02C6, U+02C7, U+02D0, U+02D8..U+02DD\n-Combining Diacritical Marks|U+0300..U+0304, U+0307..U+0308, U+030B..U+030C, U+030F, U+034F\n-Greek|U+03C0\n-Ethiopic|U+1200..137C\n-Ethiopic Supplemental|U+1380..U+1399\n-Ethiopic Extended|U+2D80..U+2DDE\n-General Punctuation|U+2000..U+2015, U+2018..U+201A, U+201C..U+201E, U+2020..U+2022, U+2026..U+2030, U+2039..U+203B, U+2044, U+2060\n-Superscripts and Subscripts|U+2070, U+2074..U+2079\n-Currency Symbols|U+20AC\n-Letterlike Symbols|U+2122, U+2126\n-Mathematical Operators|U+2202, U+2205..U+2206, U+220F, U+2211, U+2219..U+221A, U+221E, U+222B, U+2248, U+2260, U+2264..U+2265\n-Control Pictures|U+2423\n-Geometric Shapes|U+25CA, U+25CC\n-Dingbats|U+2713\n-Ethiopic Extended-A|U+AB00..U+AB2E\n-PUA|U+E494, U+E496\n-Alphabetic Presentation Forms|U+FB01..U+FB02\n-Ethiopic Extended-B|U+1E7E0..U+1E7FF\n-\n+:------------- | :---------------\n+Ethiopic| ✓\n+Ethiopic Supplemental | ✓\n+Ethiopic Extended | ✓\n+Ethiopic Extended-A | ✓\n+Ethiopic Extended-B| ✓\n+PUA|E494, E496\n+Combining Diacritical Marks| 0300..0304, 0307..0308, 030B..030C, 030F, 034F\n+Superscripts and Subscripts | 2080..2089\n+Enclosed Alphanumerics | 2460 .. 2468\n+Codepage 1252 (Western)¹ | ✓\n+\n+A selection of characters from the General Punctuation block, such as various-sized spaces, are also supported; a utility such as SIL ViewGlyph can be used to examine the exact repertoire of this font. \n+\n+¹Inclusion of basic Latin repertoire is provided as a convenience, e.g., for use in menus or for displaying markup in text files; these fonts are not intended for extensive Latin script use.\n \n ## Private-use (PUA) characters\n \n-Because the majority of the PUA characters have now been encoded into Unicode, or they were considered glyph variants, all PUA characters in the font have been removed with the exception of U+E494 () and U+E496 (). Some of the PUA codepoints were actually glyph variants of characters already encoded in Unicode. These are now available through OpenType Character Variants, Graphite features, or TypeTuned fonts. See [Font Features](features.md).\n+Because the majority of the PUA characters have now been encoded into Unicode, or they were considered glyph variants, all PUA characters in the font have been removed with the exception of U+E494 () and U+E496 (). Some of the PUA codepoints were actually glyph variants of characters already encoded in Unicode. These are now available through OpenType Character Variants or TypeTuned fonts. See [Font Features](features.md).\n \n PUA characters that were previously in the font are documented here:\n "
+ },
+ {
+ "sha": "163c39eb229b7a6ed007fd5764db171ad3af1502",
+ "filename": "fonts/sil/abyssinicasil/documentation/source/design.md",
+ "status": "modified",
+ "additions": 2,
+ "deletions": 2,
+ "changes": 4,
+ "blob_url": "https://github.com/silnrsi/fonts/blob/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fdesign.md",
+ "raw_url": "https://github.com/silnrsi/fonts/raw/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fdesign.md",
+ "contents_url": "https://api.github.com/repos/silnrsi/fonts/contents/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fdesign.md?ref=044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "patch": "@@ -1,6 +1,6 @@\n ---\n title: Abyssinica SIL - Design\n-fontversion: 2.201\n+fontversion: 2.300\n ---\n \n Abyssinica SIL is based on Ethiopic calligraphic traditions. \n@@ -17,7 +17,7 @@ Type samples showing some of the inventory of glyphs can be found here:\n \n A sample from one page is shown below. \n \n-![Abyssinica SIL Sample - Ethiopic syllables](assets/images/AbyssinicaTypeSamplev2.png){.fullsize}\n+![Abyssinica SIL Sample - Ethiopic syllables](../assets/images/AbyssinicaTypeSamplev2.png){.fullsize}\n \n Abyssinica SIL Sample - Ethiopic syllables\n "
+ },
+ {
+ "sha": "c99f289fb7a10e4bd9125e8b4303f7c072ea49af",
+ "filename": "fonts/sil/abyssinicasil/documentation/source/developer.md",
+ "status": "modified",
+ "additions": 7,
+ "deletions": 8,
+ "changes": 15,
+ "blob_url": "https://github.com/silnrsi/fonts/blob/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fdeveloper.md",
+ "raw_url": "https://github.com/silnrsi/fonts/raw/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fdeveloper.md",
+ "contents_url": "https://api.github.com/repos/silnrsi/fonts/contents/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fdeveloper.md?ref=044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "patch": "@@ -1,33 +1,32 @@\n ---\n title: Abyssinica SIL - Developer information\n-fontversion: 2.201\n+fontversion: 2.300\n ---\n \n Abyssinica SIL is a mature product with no major changes anticipated. We will be releasing maintenance updates to fix bugs. \n \n-\n ## Welcome font developers!\n \n-We welcome other developers who wish to get involved in supporting and enhancing this font.\n+We welcome other developers who wish to get involved in supporting and enhancing these fonts or who want to modify them.\n \n Abyssinica SIL uses kerning to give a better presentation of characters which might otherwise have too much space between them. If you are a font developer and wish to include kerning in your font, the list of kerning pairs is available here: [Ethiopic Kerning Pairs](https://scriptsource.sil.org/entry/w5wqtagy5f)\n \n ## Permissions granted by the OFL\n \n-SIL’s fonts are licensed according to the terms of the [SIL Open Font License](https://scripts.sil.org/OFL). The OFL allows the fonts to be used, studied, modified and redistributed freely as long as they are not sold by themselves. For details see the OFL.txt and OFL-FAQ.txt files in the package.\n+SIL’s fonts are licensed according to the terms of the [SIL Open Font License](https://openfontlicense.org/). The OFL allows the fonts to be used, studied, modified and redistributed freely as long as they are not sold by themselves. For details see the OFL.txt and OFL-FAQ.txt files in the package.\n \n ## Building the fonts from source code\n \n The latest source files are available in a [Github project](https://github.com/silnrsi/font-abyssinica).\n \n-Font sources are in the [UFO3](https://unifiedfontobject.org/versions/ufo3/) format with font family structures defined using [designspace](https://github.com/fonttools/fonttools/tree/master/Doc/source/designspaceLib). OpenType source code is stored in the [.fea](https://adobe-type-tools.github.io/afdko/OpenTypeFeatureFileSpecification.html) format in the UFO (features.fea) but is maintained in a separate file using the more efficient and powerful [.feax](https://github.com/silnrsi/pysilfont/blob/master/docs/feaextensions.rawmd) format.\n+Font sources are in the [UFO3](https://unifiedfontobject.org/versions/ufo3/) format with font family structures defined using [designspace](https://github.com/fonttools/fonttools/tree/master/Doc/source/designspaceLib). OpenType source code is stored in the [.fea](https://adobe-type-tools.github.io/afdko/OpenTypeFeatureFileSpecification.html) format in the UFO (features.fea) but is maintained in a separate file using the more efficient and powerful [.feax](https://github.com/silnrsi/feax/blob/main/docs/feaextensions.md) format.\n \n-The fonts are built using a completely free and open source workflow using industry-standard tools ([fontools](https://github.com/fonttools/fonttools)), a package of custom python scripts ([pysilfont](https://github.com/silnrsi/pysilfont)), and a build and packaging system ([Smith](https://github.com/silnrsi/smith)). The whole system is available in a preconfigured virtual machine using VirtualBox and Vagrant.\n+The fonts are built using a completely free and open source workflow using industry-standard tools ([fonttools](https://github.com/fonttools/fonttools)), a package of custom python scripts ([pysilfont](https://github.com/silnrsi/pysilfont)), and a build and packaging system ([Smith](https://github.com/silnrsi/smith)). The whole toolchain is available as a Docker container. \n \n-Full instructions for setting up the tools and building SIL fonts are available on a dedicated web site: [SIL Font Development Notes](https://silnrsi.github.io/silfontdev/).\n+Full instructions for setting up the tools and building SIL fonts are available on a dedicated web site: [SIL Font Development Guide](https://silnrsi.github.io/silfontdev/).\n \n ## Contributing to the project\n \n We warmly welcome contributions to the fonts, such as new glyphs, enhanced smart font code, or bug fixes. The [brief overview of contributing changes](https://silnrsi.github.io/silfontdev/en-US/Contributing_Changes.html) is a good place to begin. The next step is to contact us by responding to an existing issue or creating an issue in the Github repository and expressing your interest. We can then work together to plan and integrate your contributions.\n \n-To enable us to accept contributions in a way that honors your contribution and respects your copyright while preserving long-term flexibility for open source licensing, you would also need to agree to the **SIL International Contributor License Agreement for Font Software (v1.0)** prior to sending us your contribution. To read more about this requirement and find out how to submit the required form, please visit the [CLA information page](https://software.sil.org/fontcla).\n+To enable us to accept contributions in a way that honors your contribution and respects your copyright while preserving long-term flexibility for open source licensing, you would also need to agree to the **SIL Global Contributor License Agreement for Font Software (v1.0)** prior to sending us your contribution. To read more about this requirement and find out how to submit the required form, please visit the [CLA information page](https://software.sil.org/fontcla)."
+ },
+ {
+ "sha": "23f0ad059cc14b7a4e3b5fec37f89f1ecfd01b1f",
+ "filename": "fonts/sil/abyssinicasil/documentation/source/faq.md",
+ "status": "modified",
+ "additions": 10,
+ "deletions": 7,
+ "changes": 17,
+ "blob_url": "https://github.com/silnrsi/fonts/blob/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Ffaq.md",
+ "raw_url": "https://github.com/silnrsi/fonts/raw/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Ffaq.md",
+ "contents_url": "https://api.github.com/repos/silnrsi/fonts/contents/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Ffaq.md?ref=044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "patch": "@@ -1,6 +1,6 @@\n ---\n title: Abyssinica SIL - Frequently Asked Questions\n-fontversion: 2.201\n+fontversion: 2.300\n ---\n \n Many questions can be answered by consulting the following FAQ pages. Here are a few sample questions answered in each FAQ:\n@@ -12,7 +12,7 @@ Many questions can be answered by consulting the following FAQ pages. Here are a\n - *Will you add support for script...?*\n - *WIll you help me...?*\n \n-- [The SIL Open Font License (OFL-FAQ)](https://scripts.sil.org/OFL-FAQ_web)\n+- [The SIL Open Font License (OFL-FAQ)](https://openfontlicense.org/ofl-faq/)\n - *Can I use this font for...?*\n - *Can I modify the font and then include it in...*\n - *If I use the font on a web page do I have to include an acknowledgement?*\n@@ -21,25 +21,28 @@ Many questions can be answered by consulting the following FAQ pages. Here are a\n Here are a few of the most frequently asked questions specifically regarding Abyssinica SIL:\n \n #### *What is so special about Abyssinica SIL?*\n-This font is designed to work with two advanced font technologies, Graphite and OpenType. To take advantage of the advanced typographic capabilities of this font, you must be using applications that provide an adequate level of support for Graphite or OpenType. These advanced capabilities provide access to the variant character forms used in some languages.\n+This font is designed to work with the OpenType font technology. To take advantage of the advanced typographic capabilities of this font, you must be using applications that provide an adequate level of support for OpenType. The advanced OpenType capabilities provide access to the variant character forms used in some languages.\n+\n+#### *Why did you remove Graphite from Abyssinica SIL?*\n+Until version 2.300 this font included the Graphite advanced font technology. The OpenType features completely support everything that Graphite supported. Removing Graphite reduces the size of the font and some of the complexities of building the font. \n \n #### *Do you supply a keyboard to use with Abyssinica SIL?*\n \n No keyboards are supplied with the font. However, there are suggested keyboards listed in [Resources](resources.md).\n \n #### *My language uses variant forms of some Ethiopic characters. How do I type these using the Abyssinica SIL font? How do I use features?*\n \n-You should type the character the same way you would type the standard form of the character. Then, you need to select the variants to be displayed. If your application supports Graphite or the OpenType Character Variant features, you can use these to access the font features built into the font. See [Font Features](features.md) page for more details.\n+You should type the character the same way you would type the standard form of the character. Then, you need to select the variants to be displayed. If your application supports the OpenType Character Variant features, you can use these to access the font features built into the font. See [Font Features](features.md) page for more details.\n \n-If your application does not support Graphite features or the OpenType Character Variants, you can use TypeTunerWeb to customize the font with the variants you require. See [Font Features](features.md) page for more details. \n+If your application does not support the OpenType Character Variants, you can use TypeTunerWeb to customize the font with the variants you require. See [Font Features](features.md) page for more details. \n \n #### *Why did you remove the Stylistic Sets from ver. 2.000 of the Abyssinica SIL font?*\n \n Originally we added the Stylistic Sets because there was not a good solution for accessing the glyph variants in the font. At one point we also tried encoding them in the Private Use Area (PUA). PUA characters have now almost all been unencoded since the characters are now either encoded in Unicode or the variants are available through **Character Variants**. The Stylistic Sets were implemented inconsistently, and because of that we chose to remove them rather than attempt to fix them. If you still wish to use a font with Stylistic Sets, ver. 1.500 is still available on the [Previous Versions](previous-versions.md) page.\n \n #### *I have a copy of the **SIL Abyssinica** font. Can you tell me how this differs from **Abyssinica SIL**?*\n \n-It is best to upgrade to **Abyssinica SIL**. **SIL Abyssinica** (and **SIL Abyssinica U** and **SIL Abyssinica G**) was an early, unreleased version of **Abyssinica SIL**. Although a Unicode font, it only supported Unicode 3.0 and thus had a number of PUA characters in it which have since been added to Unicode 4.1 and 6.0. You should convert your data to Unicode 6.0 and use **Abyssinica SIL**. A mapping file to convert your data from PUA to Unicode 6.0 is available here: [sil-pua-unicode](https://github.com/silnrsi/wsresources/tree/master/scripts/Ethi/mappings/sil-pua-unicode). If you do not convert your data to official Unicode codepoints you will never be able to use another Ethiopic font because those are **Private** codepoints and other fonts do not support them.\n+It is best to upgrade to **Abyssinica SIL**. **SIL Abyssinica**, **SIL Abyssinica U**, and **SIL Abyssinica G** were early, unreleased versions of **Abyssinica SIL**. Although Unicode fonts, they only supported Unicode 3.0 and thus had a number of PUA characters in them which have since been added to Unicode 4.1 and 6.0. You should convert your data to Unicode and use **Abyssinica SIL**. A mapping file to convert your data from PUA to Unicode 6.0 is available here: [sil-pua-unicode](https://github.com/silnrsi/wsresources/tree/master/scripts/Ethi/mappings/sil-pua-unicode). If you do not convert your data to official Unicode codepoints you will never be able to use another Ethiopic font because those are **Private** codepoints and other fonts do not support them.\n \n #### *You have characters which are encoded in the PUA area. Is there any likelihood that these will ever be in Unicode? If so, will you update Abyssinica SIL?*\n \n@@ -49,5 +52,5 @@ With version 2.000 we removed almost all of the PUA characters in the font becau\n \n #### *I would like to bundle Abyssinica SIL with my application - can I?*\n \n-The [SIL Open Font License](https://scripts.sil.org/OFL) allows bundling with applications, even commercial ones, with some restrictions.\n+The [SIL Open Font License](https://openfontlicense.org/) allows bundling with applications, even commercial ones, with some restrictions.\n "
+ },
+ {
+ "sha": "40a9602a45432600078013b375138c2ac3351af7",
+ "filename": "fonts/sil/abyssinicasil/documentation/source/features.md",
+ "status": "modified",
+ "additions": 20,
+ "deletions": 18,
+ "changes": 38,
+ "blob_url": "https://github.com/silnrsi/fonts/blob/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Ffeatures.md",
+ "raw_url": "https://github.com/silnrsi/fonts/raw/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Ffeatures.md",
+ "contents_url": "https://api.github.com/repos/silnrsi/fonts/contents/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Ffeatures.md?ref=044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "patch": "@@ -1,22 +1,22 @@\n ---\n title: Abyssinica SIL - Font Features\n-fontversion: 2.201\n+fontversion: 2.300\n ---\n \n-Abyssinica SIL is a TrueType font with smart font capabilities added using OpenType and Graphite font technologies. The Ethiopic script does not require much rendering except for some combining marks for gemination and vowel length. However, there are some glyph variations for the Ethiopic script. Some applications let the user control certain features such as Character Variants to turn on the rendering of variant characters. However, at this point, most applications do not make use of those features so another solution is needed to show the variant characters. [TypeTuner](https://scripts.sil.org/ttw/fonts2go.cgi) creates tuned fonts that use the variant glyph in place of the standard glyph. TypeTuner also provides the ability to turn on support for the Sebat Bet Gurage and Gumuz languages variants.\n+Abyssinica SIL is a TrueType font with smart font capabilities added using the OpenType font technology. The Ethiopic script does not require much rendering except for some combining marks for gemination and vowel length. However, there are some glyph variations for the Ethiopic script. Some applications let the user control certain features such as Character Variants to turn on the rendering of variant characters. However, at this point, most applications do not make use of those features so another solution is needed to show the variant characters. [TypeTuner](https://scripts.sil.org/ttw/fonts2go.cgi) creates tuned fonts that use the variant glyph in place of the standard glyph. TypeTuner also provides the ability to turn on support for the Sebat Bet Gurage and Gumuz languages variants.\n \n-See [Using Font Features](https://software.sil.org/fonts/features/). Although that page is not targeted at Ethiopic support, it does provide a comprehensive list of applications that make full use of the OpenType and Graphite font technologies.\n+See [Using Font Features](https://software.sil.org/fonts/features/). Although that page is not targeted at Ethiopic support, it does provide a comprehensive list of applications that make full use of the OpenType font technology.\n \n ## Advanced typographic capabilities\n \n-This font supports various advanced typographic capabilities using the Graphite and OpenType font technologies. \n+This font supports various advanced typographic capabilities using the OpenType font technology. \n \n-* Auto placement of diacritics (one level only) on Ethiopic syllables only (not on Latin characters)\n+* Auto placement of diacritics on Ethiopic syllables only (not on Latin characters)\n * Kerning of almost 200 pairs of Ethiopic syllables\n-* OpenType Character Variants or Graphite features (alternately-designed glyphs are also provided for a number of characters for use in particular contexts) \n-* OpenType and Graphite support for the Sebat Bet Gurage [sgw] and Gumuz [guk] languages\n+* OpenType Character Variants (alternately-designed glyphs are also provided for a number of characters for use in particular contexts) \n+* OpenType support for the Sebat Bet Gurage [sgw] and Gumuz [guk] languages\n \n-These capabilities are available in any application that supports the Graphite technology. They are also available via the OpenType technology, though this requires applications that provide a sufficient level of support for OpenType Character Variant features. \n+These capabilities are available in any application that supports OpenType technology, though this requires applications that provide a sufficient level of support for OpenType Character Variant features. \n \n A sample of diacritic placement and kerning is shown below:\n \n@@ -32,22 +32,14 @@ This page uses web fonts (WOFF2) to demonstrate font features and should display\n \n ## Customizing with TypeTuner\n \n-For applications that do not make use of Graphite or the OpenType Stylistic Sets feature, you can now download fonts customized with the variant glyphs you choose. Read the [Font Features](features.md) page, visit [TypeTuner Web](https://scripts.sil.org/ttw/fonts2go.cgi), then to choose the variants and download your font.\n+For applications that do not make use of the OpenType Character Variant features, you can now download fonts customized with the variant glyphs you choose. Read the [Font Features](features.md) page, visit [TypeTuner Web](https://scripts.sil.org/ttw/fonts2go.cgi), then to choose the variants and download your font.\n \n \n ## Complete feature list\n \n-There are some Ethiopic character shape differences in different Ethiopian languages. These can be accessed by using Graphite features, OpenType Character Variants, or language support for Sebat Bet Gurage and Gumuz languages. The documents below can be downloaded in order to see all the user-selectable font features that are available in the font. The feature names, feature ids, settings and examples are provided. \n+There are some Ethiopic character shape differences in different Ethiopian languages. These can be accessed by using OpenType Character Variants or language support for Sebat Bet Gurage and Gumuz languages. The documents below can be downloaded in order to see all the user-selectable font features that are available in the font. The feature names, feature ids, settings and examples are provided. \n \n \n-### Test rendering engine choice \n-\n-Here is a simple test to see if Graphite is working in your browser. If it is, the following will say \"RenderingGraphite\". If your browser does not support Graphite it should say \"RenderingOpentype\". Firefox is currently the only browser that supports Graphite. See the [instructions on how to enable Graphite in Firefox](https://scripts.sil.org/cms/scripts/page.php?site_id=projects&item_id=graphite_firefox#switchon).\n-\n-| | \n-------------- | --------------- \n-Check | RenderingUnknown\n-\n ### Language \n \n Affects: U+124A, U+124D, U+1298..U+129F, U+12B2, U+12B5, U+12C2, U+12C5, U+1312, U+1313, U+1315, U+1381, U+1385, U+138D \n@@ -325,6 +317,16 @@ Feature | Sample | Feature setting\n Standard | ቍ ኵ ዅ ጕ | `cv85=0`\n Alternate | ቍ ኵ ዅ ጕ⁷ | `cv85=1`\n \n+### Ligatures\n+\n+#### gzi ligature\n+\n+Affects: U+130D U+200D U+12DA\n+\n+Feature | Sample | Feature setting\n+------------- | --------------- | ------------- \n+No Joiner | ግዚ | U+130D U+12DA\n+Using ZWJ | ግዚ | U+130D U+200D U+12DA\n \n \n ## References"
+ },
+ {
+ "sha": "f20d8a9fc0d7f345a8e57a0579bb72ff43cc873a",
+ "filename": "fonts/sil/abyssinicasil/documentation/source/history.md",
+ "status": "modified",
+ "additions": 43,
+ "deletions": 1,
+ "changes": 44,
+ "blob_url": "https://github.com/silnrsi/fonts/blob/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fhistory.md",
+ "raw_url": "https://github.com/silnrsi/fonts/raw/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fhistory.md",
+ "contents_url": "https://api.github.com/repos/silnrsi/fonts/contents/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fhistory.md?ref=044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "patch": "@@ -1,8 +1,50 @@\n ---\n title: Abyssinica SIL - Version History\n-fontversion: 2.201\n+fontversion: 2.300\n ---\n \n+### 29 Oct 2024 (WSTech Team) Abyssinica SIL version 2.300\n+\n+#### Improved\n+- Adjusted glyph shapes for\n+ - 1214 ETHIOPIC SYLLABLE HHEE\n+ - 1264 ETHIOPIC SYLLABLE BEE\n+ - 126C ETHIOPIC SYLLABLE VEE\n+ - 129C ETHIOPIC SYLLABLE NYEE\n+ - 12DC ETHIOPIC SYLLABLE ZEE\n+ - 1334 ETHIOPIC SYLLABLE PHEE\n+ - 133C ETHIOPIC SYLLABLE TSEE\n+ - AB14 ETHIOPIC SYLLABLE DZEE\n+ - AB2C ETHIOPIC SYLLABLE BBEE\n+ - 1E7E4 ETHIOPIC SYLLABLE HHYEE\n+ - 1E7EA ETHIOPIC SYLLABLE HHWEE\n+- Improve diacritic position to support multiple above diacritics\n+\n+#### Added\n+- Added gzi Ligature\n+- 2080 SUBSCRIPT ZERO\n+- 2081 SUBSCRIPT ONE\n+- 2082 SUBSCRIPT TWO\n+- 2083 SUBSCRIPT THREE\n+- 2084 SUBSCRIPT FOUR\n+- 2085 SUBSCRIPT FIVE\n+- 2086 SUBSCRIPT SIX\n+- 2087 SUBSCRIPT SEVEN\n+- 2088 SUBSCRIPT EIGHT\n+- 2089 SUBSCRIPT NINE\n+- 2460 CIRCLED DIGIT ONE\n+- 2461 CIRCLED DIGIT TWO\n+- 2462 CIRCLED DIGIT THREE\n+- 2463 CIRCLED DIGIT FOUR\n+- 2464 CIRCLED DIGIT FIVE\n+- 2465 CIRCLED DIGIT SIX\n+- 2466 CIRCLED DIGIT SEVEN\n+- 2467 CIRCLED DIGIT EIGHT\n+- 2468 CIRCLED DIGIT NINE\n+\n+#### Remove\n+- Graphite\n+\n ### 23 June 2023 (WSTech Team) Abyssinica SIL version 2.201\n - Fixed bug in TypeTuner support for cv46 tswa alternate\n "
+ },
+ {
+ "sha": "38e77c156cc1a8a4c82edd0aaabf67c146aaa6a7",
+ "filename": "fonts/sil/abyssinicasil/documentation/source/index.md",
+ "status": "modified",
+ "additions": 2,
+ "deletions": 2,
+ "changes": 4,
+ "blob_url": "https://github.com/silnrsi/fonts/blob/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Findex.md",
+ "raw_url": "https://github.com/silnrsi/fonts/raw/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Findex.md",
+ "contents_url": "https://api.github.com/repos/silnrsi/fonts/contents/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Findex.md?ref=044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "patch": "@@ -1,13 +1,13 @@\n ---\n title: Abyssinica SIL - Documentation\n-fontversion: 2.201\n+fontversion: 2.300\n ---\n \n Thank you for your interest in the Abyssinica SIL font. This font supports the broad variety of writing systems that use the Ethiopic script.\n \n This documentation is a set of HTML pages that can be viewed in any modern web browser. PDF versions of these pages are also provided. This content, plus download links and a contact form, are available from the [Abyssinica SIL site](https://software.sil.org/abyssinica/).\n \n-- [About](about.md) — Information about this project and SIL International\n+- [About](about.md) — Information about this project and SIL Global\n - [Resources](resources.md) — Help with installation and use\n - [FAQ](faq.md) — Common questions and answers\n - [Design](design.md) — History and background of the design"
+ },
+ {
+ "sha": "9ef79278a5c6b3bf776bd5a7f99436617a732f40",
+ "filename": "fonts/sil/abyssinicasil/documentation/source/makepsmd.py",
+ "status": "modified",
+ "additions": 6,
+ "deletions": 5,
+ "changes": 11,
+ "blob_url": "https://github.com/silnrsi/fonts/blob/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fmakepsmd.py",
+ "raw_url": "https://github.com/silnrsi/fonts/raw/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fmakepsmd.py",
+ "contents_url": "https://api.github.com/repos/silnrsi/fonts/contents/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fmakepsmd.py?ref=044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "patch": "@@ -1,8 +1,8 @@\n #!/usr/bin/env python\n '''Process font documentation .md files for use on product sites '''\n-__url__ = 'https://github.com/silnrsi/fontdocs'\n-__copyright__ = 'Copyright (c) 2021-2023 SIL International (https://www.sil.org)'\n-__license__ = 'Released under the MIT License (https://opensource.org/license/mit/)'\n+__url__ = 'http://github.com/silnrsi/fontdocs'\n+__copyright__ = 'Copyright (c) 2021-2024 SIL Global (https://www.sil.org)'\n+__license__ = 'Released under the MIT License (http://opensource.org/licenses/MIT)'\n __author__ = 'Victor Gaultney'\n \n import re\n@@ -58,13 +58,14 @@ def doit(args):\n temptext = mdimagecap.sub(r\"[caption]\\1[/caption]\", temptext)\n \n # replace local links with site references\n- temptext = temptext.replace(\".md\",\"\")\n+ mdlink = re.compile(r\"\\((?!https://)(?P[^()]*).md\\)\")\n+ temptext = mdlink.sub(r\"(\\g)\",temptext)\n \n # replace links to external markdown files\n temptext = temptext.replace(\".rawmd\",\".md\")\n \n # replace escaped @ in link texts\n- temptext = temptext.replace(\"[\\@\",\"[@\")\n+ temptext = temptext.replace(r\"[\\@\",r\"[@\")\n \n # make a list of new classes needed for font shortcode\n # separate searches for spans with 1, 2, or 3 settings"
+ },
+ {
+ "sha": "0ca243b339ef2040464a4092e9347473ad5ee08b",
+ "filename": "fonts/sil/abyssinicasil/documentation/source/pandocfilters/filter-html.lua",
+ "status": "modified",
+ "additions": 5,
+ "deletions": 3,
+ "changes": 8,
+ "blob_url": "https://github.com/silnrsi/fonts/blob/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fpandocfilters%2Ffilter-html.lua",
+ "raw_url": "https://github.com/silnrsi/fonts/raw/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fpandocfilters%2Ffilter-html.lua",
+ "contents_url": "https://api.github.com/repos/silnrsi/fonts/contents/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fpandocfilters%2Ffilter-html.lua?ref=044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "patch": "@@ -1,10 +1,12 @@\n function Link(el)\n- el.target = string.gsub(el.target, \"%.md\", \".html\")\n+ if string.find(el.target, \"^https?://\") == nil then\n+ el.target = string.gsub(el.target, \"%.md\", \".html\")\n+ end\n el.target = string.gsub(el.target, \"%.rawmd\", \".md\")\n return el\n end\n \n-function CodeBlock(el)\n- el.text = string.gsub(el.text, \"(.+)\", \" %0\")\n+function Image(el)\n+ el.src = string.gsub(el.src, \"../assets\", \"assets\")\n return el\n end"
+ },
+ {
+ "sha": "bf1526c2d4ff0c1c977853e2060fc1a655512403",
+ "filename": "fonts/sil/abyssinicasil/documentation/source/pandocfilters/filter-pdf.lua",
+ "status": "modified",
+ "additions": 10,
+ "deletions": 9,
+ "changes": 19,
+ "blob_url": "https://github.com/silnrsi/fonts/blob/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fpandocfilters%2Ffilter-pdf.lua",
+ "raw_url": "https://github.com/silnrsi/fonts/raw/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fpandocfilters%2Ffilter-pdf.lua",
+ "contents_url": "https://api.github.com/repos/silnrsi/fonts/contents/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fpandocfilters%2Ffilter-pdf.lua?ref=044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "patch": "@@ -1,16 +1,17 @@\n function Link(el)\n- el.target = string.gsub(el.target, \"(.+)\", \"../../pdf/%0\")\n- el.target = string.gsub(el.target, \"%.md\", \".pdf\")\n- el.target = string.gsub(el.target, \"%.rawmd\", \".md\")\n+ if string.find(el.target, \"^https?://\") == nil then\n+ -- While full external links work fine, WeasyPrint doesn't \n+ -- seem capable of creating relative links within PDF files, \n+ -- and thus the resulting PDF files won't work if they are \n+ -- downloaded to a different folder. Until WeasyPrint is fixed,\n+ -- we remove the target from relative links, making them \n+ -- nonfunctioning (even though they remain formatted as a link):\n+ el.target = \"\"\n+ end\n return el\n end\n \n function Image(el)\n- el.src = string.gsub(el.src, \"(.+)\", \"../../%0\")\n- return el\n-end\n-\n-function CodeBlock(el)\n- el.text = string.gsub(el.text, \"(.+)\", \" %0\")\n+ el.src = string.gsub(el.src, \"../assets\", \"../../assets\")\n return el\n end"
+ },
+ {
+ "sha": "474d294605c6f22e2f354ad71e5bd35158d5bd85",
+ "filename": "fonts/sil/abyssinicasil/documentation/source/productsite/about.md",
+ "status": "modified",
+ "additions": 4,
+ "deletions": 5,
+ "changes": 9,
+ "blob_url": "https://github.com/silnrsi/fonts/blob/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fproductsite%2Fabout.md",
+ "raw_url": "https://github.com/silnrsi/fonts/raw/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fproductsite%2Fabout.md",
+ "contents_url": "https://api.github.com/repos/silnrsi/fonts/contents/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fproductsite%2Fabout.md?ref=044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "patch": "@@ -5,7 +5,6 @@ Abyssinica SIL is based on Ethiopic calligraphic traditions. The Ethiopic script\n \n For more information on the visual characteristics of the font see [Design](design).\n \n-\n ## Future plans\n \n This font is actively maintained and improved, and recent changes to its development process will enable more frequent releases.\n@@ -28,15 +27,15 @@ You can subscribe using either of the two following options.\n \n - If you would rather not use a Google profile, you can subscribe any email address by sending a message to [sil-font-news+subscribe@groups.sil.org](mailto:sil-font-news+subscribe@groups.sil.org) and following the instructions you get in the confirmation message.\n \n-Our font announcements are also available through Twitter [@silfonts](https://twitter.com/silfonts).\n+Our font announcements are also available through X (formerly Twitter) [@silfonts](https://x.com/silfonts).\n \n ## Supporting the project\n \n-This font is provided at no cost, however it is expensive to produce and maintain. Please consider donating to SIL’s font development efforts to support future development. Go to [SIL’s Give Direct page](https://donate.givedirect.org/?cid=13536&n=206909) and designate your gift for _Scripts & Fonts_. **Thank you!** \n+These fonts are provided at no cost; however, they are expensive to produce and maintain. Please consider donating to SIL’s font development efforts to support future development. Go to [SIL’s Give Direct page](https://give.sil.org/give/485238). **Thank you!** \n \n-## About SIL International\n+## About SIL Global\n \n-[SIL International](https://www.sil.org/) is a global, faith-based nonprofit that works with local communities around the world to develop language solutions that expand possibilities for a better life. \n+[SIL Global](https://www.sil.org/) is a global, faith-based nonprofit that works with local communities around the world to develop language solutions that expand possibilities for a better life. \n \n We are involved in approximately 1,350 active language projects in 104 countries. These projects impact more than 1.1 billion people within 1,600 local communities. SIL’s work brings together more than 4,300 staff from 89 countries who work alongside thousands more local partners and community volunteers worldwide. Our services are available without regard to religious belief, political ideology, gender, race or ethnic background.\n "
+ },
+ {
+ "sha": "854cfd734a45986eb5ff26888c81b71508886559",
+ "filename": "fonts/sil/abyssinicasil/documentation/source/productsite/announcement.md",
+ "status": "modified",
+ "additions": 43,
+ "deletions": 3,
+ "changes": 46,
+ "blob_url": "https://github.com/silnrsi/fonts/blob/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fproductsite%2Fannouncement.md",
+ "raw_url": "https://github.com/silnrsi/fonts/raw/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fproductsite%2Fannouncement.md",
+ "contents_url": "https://api.github.com/repos/silnrsi/fonts/contents/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fproductsite%2Fannouncement.md?ref=044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "patch": "@@ -1,10 +1,50 @@\n \n This is a minor release. Changes for this version include the following:\n \n-- Fixed bug in TypeTuner support for cv46 tswa alternate\n+#### Improved\n \n-#### Known issues\n+- Adjusted glyph shapes for\n+ - 1214 ETHIOPIC SYLLABLE HHEE\n+ - 1264 ETHIOPIC SYLLABLE BEE\n+ - 126C ETHIOPIC SYLLABLE VEE\n+ - 129C ETHIOPIC SYLLABLE NYEE\n+ - 12DC ETHIOPIC SYLLABLE ZEE\n+ - 1334 ETHIOPIC SYLLABLE PHEE\n+ - 133C ETHIOPIC SYLLABLE TSEE\n+ - AB14 ETHIOPIC SYLLABLE DZEE\n+ - AB2C ETHIOPIC SYLLABLE BBEE\n+ - 1E7E4 ETHIOPIC SYLLABLE HHYEE\n+ - 1E7EA ETHIOPIC SYLLABLE HHWEE\n+- Improve diacritic position to support multiple above diacritics\n+\n+#### Added\n+\n+- Added gzi Ligature\n+- 2080 SUBSCRIPT ZERO\n+- 2081 SUBSCRIPT ONE\n+- 2082 SUBSCRIPT TWO\n+- 2083 SUBSCRIPT THREE\n+- 2084 SUBSCRIPT FOUR\n+- 2085 SUBSCRIPT FIVE\n+- 2086 SUBSCRIPT SIX\n+- 2087 SUBSCRIPT SEVEN\n+- 2088 SUBSCRIPT EIGHT\n+- 2089 SUBSCRIPT NINE\n+- 2460 CIRCLED DIGIT ONE\n+- 2461 CIRCLED DIGIT TWO\n+- 2462 CIRCLED DIGIT THREE\n+- 2463 CIRCLED DIGIT FOUR\n+- 2464 CIRCLED DIGIT FIVE\n+- 2465 CIRCLED DIGIT SIX\n+- 2466 CIRCLED DIGIT SEVEN\n+- 2467 CIRCLED DIGIT EIGHT\n+- 2468 CIRCLED DIGIT NINE\n+\n+#### Remove\n+- Graphite\n+\n+### Known issues\n \n - There are no known issues.\n \n-Download the release packages from the [Download Page](https://software.sil.org/abyssinica/download/).\n+Both desktop and web fonts are provided in a single, all-platforms package on the [Download page](https://software.sil.org/abyssinica/download)."
+ },
+ {
+ "sha": "469ed147bbaa9a6d9829f72380f4699fb971ece1",
+ "filename": "fonts/sil/abyssinicasil/documentation/source/productsite/charset.md",
+ "status": "modified",
+ "additions": 16,
+ "deletions": 26,
+ "changes": 42,
+ "blob_url": "https://github.com/silnrsi/fonts/blob/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fproductsite%2Fcharset.md",
+ "raw_url": "https://github.com/silnrsi/fonts/raw/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fproductsite%2Fcharset.md",
+ "contents_url": "https://api.github.com/repos/silnrsi/fonts/contents/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fproductsite%2Fcharset.md?ref=044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "patch": "@@ -1,40 +1,30 @@\n \n This font contains complete coverage of all the characters defined in Unicode for Ethiopic. The Ethiopic script is used for writing many of the languages of Ethiopia and Eritrea. [Ethiopic (U+1200..U+137F)](https://www.unicode.org/charts/PDF/U1200.pdf) was added to Unicode 3.0. [Ethiopic Supplement (U+1380..U+139F)](https://www.unicode.org/charts/PDF/U1380.pdf) and [Ethiopic Extended (U+2D80..U+2DDF)](https://www.unicode.org/charts/PDF/U2D80.pdf) were added to Unicode 4.1. [Ethiopic Extended-A (U+AB00..U+AB2F)](https://www.unicode.org/charts/PDF/UAB00.pdf) was added to Unicode 6.0. [Ethiopic Extended-B U+1E7E0..U+1E7FF)](https://www.unicode.org/charts/PDF/U1E7E0.pdf) was added to Unicode 14.0. *Abyssinica SIL* supports all Ethiopic characters which are in Unicode. As far as we are aware, all languages using the Ethiopic script are now fully represented in Unicode. \n \n-\n ## Supported characters\n \n The following character ranges are supported by this font:\n \n Unicode block | Abyssinica SIL support\n-------------- | ---------------\n-C0 Controls and Basic Latin|U+0020..U+007E\n-C1 Controls and Latin-1 Supplement|U+00A0..U+00FF\n-Latin Extended-A|U+0131, U+0152..U+0153, U+0160..U+0161, U+0178, U+017D..U+017E\n-Latin Extended-B|U+0192\n-Spacing Modifier Letters|U+02C6, U+02C7, U+02D0, U+02D8..U+02DD\n-Combining Diacritical Marks|U+0300..U+0304, U+0307..U+0308, U+030B..U+030C, U+030F, U+034F\n-Greek|U+03C0\n-Ethiopic|U+1200..137C\n-Ethiopic Supplemental|U+1380..U+1399\n-Ethiopic Extended|U+2D80..U+2DDE\n-General Punctuation|U+2000..U+2015, U+2018..U+201A, U+201C..U+201E, U+2020..U+2022, U+2026..U+2030, U+2039..U+203B, U+2044, U+2060\n-Superscripts and Subscripts|U+2070, U+2074..U+2079\n-Currency Symbols|U+20AC\n-Letterlike Symbols|U+2122, U+2126\n-Mathematical Operators|U+2202, U+2205..U+2206, U+220F, U+2211, U+2219..U+221A, U+221E, U+222B, U+2248, U+2260, U+2264..U+2265\n-Control Pictures|U+2423\n-Geometric Shapes|U+25CA, U+25CC\n-Dingbats|U+2713\n-Ethiopic Extended-A|U+AB00..U+AB2E\n-PUA|U+E494, U+E496\n-Alphabetic Presentation Forms|U+FB01..U+FB02\n-Ethiopic Extended-B|U+1E7E0..U+1E7FF\n-\n+:------------- | :---------------\n+Ethiopic| ✓\n+Ethiopic Supplemental | ✓\n+Ethiopic Extended | ✓\n+Ethiopic Extended-A | ✓\n+Ethiopic Extended-B| ✓\n+PUA|E494, E496\n+Combining Diacritical Marks| 0300..0304, 0307..0308, 030B..030C, 030F, 034F\n+Superscripts and Subscripts | 2080..2089\n+Enclosed Alphanumerics | 2460 .. 2468\n+Codepage 1252 (Western)¹ | ✓\n+\n+A selection of characters from the General Punctuation block, such as various-sized spaces, are also supported; a utility such as SIL ViewGlyph can be used to examine the exact repertoire of this font. \n+\n+¹Inclusion of basic Latin repertoire is provided as a convenience, e.g., for use in menus or for displaying markup in text files; these fonts are not intended for extensive Latin script use.\n \n ## Private-use (PUA) characters\n \n-Because the majority of the PUA characters have now been encoded into Unicode, or they were considered glyph variants, all PUA characters in the font have been removed with the exception of U+E494 () and U+E496 (). Some of the PUA codepoints were actually glyph variants of characters already encoded in Unicode. These are now available through OpenType Character Variants, Graphite features, or TypeTuned fonts. See [Font Features](features).\n+Because the majority of the PUA characters have now been encoded into Unicode, or they were considered glyph variants, all PUA characters in the font have been removed with the exception of U+E494 () and U+E496 (). Some of the PUA codepoints were actually glyph variants of characters already encoded in Unicode. These are now available through OpenType Character Variants or TypeTuned fonts. See [Font Features](features).\n \n PUA characters that were previously in the font are documented here:\n "
+ },
+ {
+ "sha": "479738781202032fe7994b9937ee824c494d35db",
+ "filename": "fonts/sil/abyssinicasil/documentation/source/productsite/developer.md",
+ "status": "modified",
+ "additions": 6,
+ "deletions": 7,
+ "changes": 13,
+ "blob_url": "https://github.com/silnrsi/fonts/blob/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fproductsite%2Fdeveloper.md",
+ "raw_url": "https://github.com/silnrsi/fonts/raw/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fproductsite%2Fdeveloper.md",
+ "contents_url": "https://api.github.com/repos/silnrsi/fonts/contents/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fproductsite%2Fdeveloper.md?ref=044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "patch": "@@ -1,29 +1,28 @@\n \n Abyssinica SIL is a mature product with no major changes anticipated. We will be releasing maintenance updates to fix bugs. \n \n-\n ## Welcome font developers!\n \n-We welcome other developers who wish to get involved in supporting and enhancing this font.\n+We welcome other developers who wish to get involved in supporting and enhancing these fonts or who want to modify them.\n \n Abyssinica SIL uses kerning to give a better presentation of characters which might otherwise have too much space between them. If you are a font developer and wish to include kerning in your font, the list of kerning pairs is available here: [Ethiopic Kerning Pairs](https://scriptsource.sil.org/entry/w5wqtagy5f)\n \n ## Permissions granted by the OFL\n \n-SIL’s fonts are licensed according to the terms of the [SIL Open Font License](https://scripts.sil.org/OFL). The OFL allows the fonts to be used, studied, modified and redistributed freely as long as they are not sold by themselves. For details see the OFL.txt and OFL-FAQ.txt files in the package.\n+SIL’s fonts are licensed according to the terms of the [SIL Open Font License](https://openfontlicense.org/). The OFL allows the fonts to be used, studied, modified and redistributed freely as long as they are not sold by themselves. For details see the OFL.txt and OFL-FAQ.txt files in the package.\n \n ## Building the fonts from source code\n \n The latest source files are available in a [Github project](https://github.com/silnrsi/font-abyssinica).\n \n-Font sources are in the [UFO3](https://unifiedfontobject.org/versions/ufo3/) format with font family structures defined using [designspace](https://github.com/fonttools/fonttools/tree/master/Doc/source/designspaceLib). OpenType source code is stored in the [.fea](https://adobe-type-tools.github.io/afdko/OpenTypeFeatureFileSpecification.html) format in the UFO (features.fea) but is maintained in a separate file using the more efficient and powerful [.feax](https://github.com/silnrsi/pysilfont/blob/master/docs/feaextensions.md) format.\n+Font sources are in the [UFO3](https://unifiedfontobject.org/versions/ufo3/) format with font family structures defined using [designspace](https://github.com/fonttools/fonttools/tree/master/Doc/source/designspaceLib). OpenType source code is stored in the [.fea](https://adobe-type-tools.github.io/afdko/OpenTypeFeatureFileSpecification.html) format in the UFO (features.fea) but is maintained in a separate file using the more efficient and powerful [.feax](https://github.com/silnrsi/feax/blob/main/docs/feaextensions.md) format.\n \n-The fonts are built using a completely free and open source workflow using industry-standard tools ([fontools](https://github.com/fonttools/fonttools)), a package of custom python scripts ([pysilfont](https://github.com/silnrsi/pysilfont)), and a build and packaging system ([Smith](https://github.com/silnrsi/smith)). The whole system is available in a preconfigured virtual machine using VirtualBox and Vagrant.\n+The fonts are built using a completely free and open source workflow using industry-standard tools ([fonttools](https://github.com/fonttools/fonttools)), a package of custom python scripts ([pysilfont](https://github.com/silnrsi/pysilfont)), and a build and packaging system ([Smith](https://github.com/silnrsi/smith)). The whole toolchain is available as a Docker container. \n \n-Full instructions for setting up the tools and building SIL fonts are available on a dedicated web site: [SIL Font Development Notes](https://silnrsi.github.io/silfontdev/).\n+Full instructions for setting up the tools and building SIL fonts are available on a dedicated web site: [SIL Font Development Guide](https://silnrsi.github.io/silfontdev/).\n \n ## Contributing to the project\n \n We warmly welcome contributions to the fonts, such as new glyphs, enhanced smart font code, or bug fixes. The [brief overview of contributing changes](https://silnrsi.github.io/silfontdev/en-US/Contributing_Changes.html) is a good place to begin. The next step is to contact us by responding to an existing issue or creating an issue in the Github repository and expressing your interest. We can then work together to plan and integrate your contributions.\n \n-To enable us to accept contributions in a way that honors your contribution and respects your copyright while preserving long-term flexibility for open source licensing, you would also need to agree to the **SIL International Contributor License Agreement for Font Software (v1.0)** prior to sending us your contribution. To read more about this requirement and find out how to submit the required form, please visit the [CLA information page](https://software.sil.org/fontcla).\n+To enable us to accept contributions in a way that honors your contribution and respects your copyright while preserving long-term flexibility for open source licensing, you would also need to agree to the **SIL Global Contributor License Agreement for Font Software (v1.0)** prior to sending us your contribution. To read more about this requirement and find out how to submit the required form, please visit the [CLA information page](https://software.sil.org/fontcla)."
+ },
+ {
+ "sha": "1c37acee0ccbda15f3f395f6ff25790630591424",
+ "filename": "fonts/sil/abyssinicasil/documentation/source/productsite/faq.md",
+ "status": "modified",
+ "additions": 9,
+ "deletions": 6,
+ "changes": 15,
+ "blob_url": "https://github.com/silnrsi/fonts/blob/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fproductsite%2Ffaq.md",
+ "raw_url": "https://github.com/silnrsi/fonts/raw/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fproductsite%2Ffaq.md",
+ "contents_url": "https://api.github.com/repos/silnrsi/fonts/contents/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fproductsite%2Ffaq.md?ref=044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "patch": "@@ -8,7 +8,7 @@ Many questions can be answered by consulting the following FAQ pages. Here are a\n - *Will you add support for script...?*\n - *WIll you help me...?*\n \n-- [The SIL Open Font License (OFL-FAQ)](https://scripts.sil.org/OFL-FAQ_web)\n+- [The SIL Open Font License (OFL-FAQ)](https://openfontlicense.org/ofl-faq/)\n - *Can I use this font for...?*\n - *Can I modify the font and then include it in...*\n - *If I use the font on a web page do I have to include an acknowledgement?*\n@@ -17,25 +17,28 @@ Many questions can be answered by consulting the following FAQ pages. Here are a\n Here are a few of the most frequently asked questions specifically regarding Abyssinica SIL:\n \n #### *What is so special about Abyssinica SIL?*\n-This font is designed to work with two advanced font technologies, Graphite and OpenType. To take advantage of the advanced typographic capabilities of this font, you must be using applications that provide an adequate level of support for Graphite or OpenType. These advanced capabilities provide access to the variant character forms used in some languages.\n+This font is designed to work with the OpenType font technology. To take advantage of the advanced typographic capabilities of this font, you must be using applications that provide an adequate level of support for OpenType. The advanced OpenType capabilities provide access to the variant character forms used in some languages.\n+\n+#### *Why did you remove Graphite from Abyssinica SIL?*\n+Until version 2.300 this font included the Graphite advanced font technology. The OpenType features completely support everything that Graphite supported. Removing Graphite reduces the size of the font and some of the complexities of building the font. \n \n #### *Do you supply a keyboard to use with Abyssinica SIL?*\n \n No keyboards are supplied with the font. However, there are suggested keyboards listed in [Resources](resources).\n \n #### *My language uses variant forms of some Ethiopic characters. How do I type these using the Abyssinica SIL font? How do I use features?*\n \n-You should type the character the same way you would type the standard form of the character. Then, you need to select the variants to be displayed. If your application supports Graphite or the OpenType Character Variant features, you can use these to access the font features built into the font. See [Font Features](features) page for more details.\n+You should type the character the same way you would type the standard form of the character. Then, you need to select the variants to be displayed. If your application supports the OpenType Character Variant features, you can use these to access the font features built into the font. See [Font Features](features) page for more details.\n \n-If your application does not support Graphite features or the OpenType Character Variants, you can use TypeTunerWeb to customize the font with the variants you require. See [Font Features](features) page for more details. \n+If your application does not support the OpenType Character Variants, you can use TypeTunerWeb to customize the font with the variants you require. See [Font Features](features) page for more details. \n \n #### *Why did you remove the Stylistic Sets from ver. 2.000 of the Abyssinica SIL font?*\n \n Originally we added the Stylistic Sets because there was not a good solution for accessing the glyph variants in the font. At one point we also tried encoding them in the Private Use Area (PUA). PUA characters have now almost all been unencoded since the characters are now either encoded in Unicode or the variants are available through **Character Variants**. The Stylistic Sets were implemented inconsistently, and because of that we chose to remove them rather than attempt to fix them. If you still wish to use a font with Stylistic Sets, ver. 1.500 is still available on the [Previous Versions](previous-versions) page.\n \n #### *I have a copy of the **SIL Abyssinica** font. Can you tell me how this differs from **Abyssinica SIL**?*\n \n-It is best to upgrade to **Abyssinica SIL**. **SIL Abyssinica** (and **SIL Abyssinica U** and **SIL Abyssinica G**) was an early, unreleased version of **Abyssinica SIL**. Although a Unicode font, it only supported Unicode 3.0 and thus had a number of PUA characters in it which have since been added to Unicode 4.1 and 6.0. You should convert your data to Unicode 6.0 and use **Abyssinica SIL**. A mapping file to convert your data from PUA to Unicode 6.0 is available here: [sil-pua-unicode](https://github.com/silnrsi/wsresources/tree/master/scripts/Ethi/mappings/sil-pua-unicode). If you do not convert your data to official Unicode codepoints you will never be able to use another Ethiopic font because those are **Private** codepoints and other fonts do not support them.\n+It is best to upgrade to **Abyssinica SIL**. **SIL Abyssinica**, **SIL Abyssinica U**, and **SIL Abyssinica G** were early, unreleased versions of **Abyssinica SIL**. Although Unicode fonts, they only supported Unicode 3.0 and thus had a number of PUA characters in them which have since been added to Unicode 4.1 and 6.0. You should convert your data to Unicode and use **Abyssinica SIL**. A mapping file to convert your data from PUA to Unicode 6.0 is available here: [sil-pua-unicode](https://github.com/silnrsi/wsresources/tree/master/scripts/Ethi/mappings/sil-pua-unicode). If you do not convert your data to official Unicode codepoints you will never be able to use another Ethiopic font because those are **Private** codepoints and other fonts do not support them.\n \n #### *You have characters which are encoded in the PUA area. Is there any likelihood that these will ever be in Unicode? If so, will you update Abyssinica SIL?*\n \n@@ -45,5 +48,5 @@ With version 2.000 we removed almost all of the PUA characters in the font becau\n \n #### *I would like to bundle Abyssinica SIL with my application - can I?*\n \n-The [SIL Open Font License](https://scripts.sil.org/OFL) allows bundling with applications, even commercial ones, with some restrictions.\n+The [SIL Open Font License](https://openfontlicense.org/) allows bundling with applications, even commercial ones, with some restrictions.\n "
+ },
+ {
+ "sha": "d1b7cca07233eefc1085c79a7ce133f4bf19dcc0",
+ "filename": "fonts/sil/abyssinicasil/documentation/source/productsite/features.md",
+ "status": "modified",
+ "additions": 19,
+ "deletions": 17,
+ "changes": 36,
+ "blob_url": "https://github.com/silnrsi/fonts/blob/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fproductsite%2Ffeatures.md",
+ "raw_url": "https://github.com/silnrsi/fonts/raw/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fproductsite%2Ffeatures.md",
+ "contents_url": "https://api.github.com/repos/silnrsi/fonts/contents/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fproductsite%2Ffeatures.md?ref=044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "patch": "@@ -1,18 +1,18 @@\n \n-Abyssinica SIL is a TrueType font with smart font capabilities added using OpenType and Graphite font technologies. The Ethiopic script does not require much rendering except for some combining marks for gemination and vowel length. However, there are some glyph variations for the Ethiopic script. Some applications let the user control certain features such as Character Variants to turn on the rendering of variant characters. However, at this point, most applications do not make use of those features so another solution is needed to show the variant characters. [TypeTuner](https://scripts.sil.org/ttw/fonts2go.cgi) creates tuned fonts that use the variant glyph in place of the standard glyph. TypeTuner also provides the ability to turn on support for the Sebat Bet Gurage and Gumuz languages variants.\n+Abyssinica SIL is a TrueType font with smart font capabilities added using the OpenType font technology. The Ethiopic script does not require much rendering except for some combining marks for gemination and vowel length. However, there are some glyph variations for the Ethiopic script. Some applications let the user control certain features such as Character Variants to turn on the rendering of variant characters. However, at this point, most applications do not make use of those features so another solution is needed to show the variant characters. [TypeTuner](https://scripts.sil.org/ttw/fonts2go.cgi) creates tuned fonts that use the variant glyph in place of the standard glyph. TypeTuner also provides the ability to turn on support for the Sebat Bet Gurage and Gumuz languages variants.\n \n-See [Using Font Features](https://software.sil.org/fonts/features/). Although that page is not targeted at Ethiopic support, it does provide a comprehensive list of applications that make full use of the OpenType and Graphite font technologies.\n+See [Using Font Features](https://software.sil.org/fonts/features/). Although that page is not targeted at Ethiopic support, it does provide a comprehensive list of applications that make full use of the OpenType font technology.\n \n ## Advanced typographic capabilities\n \n-This font supports various advanced typographic capabilities using the Graphite and OpenType font technologies. \n+This font supports various advanced typographic capabilities using the OpenType font technology. \n \n-* Auto placement of diacritics (one level only) on Ethiopic syllables only (not on Latin characters)\n+* Auto placement of diacritics on Ethiopic syllables only (not on Latin characters)\n * Kerning of almost 200 pairs of Ethiopic syllables\n-* OpenType Character Variants or Graphite features (alternately-designed glyphs are also provided for a number of characters for use in particular contexts) \n-* OpenType and Graphite support for the Sebat Bet Gurage [sgw] and Gumuz [guk] languages\n+* OpenType Character Variants (alternately-designed glyphs are also provided for a number of characters for use in particular contexts) \n+* OpenType support for the Sebat Bet Gurage [sgw] and Gumuz [guk] languages\n \n-These capabilities are available in any application that supports the Graphite technology. They are also available via the OpenType technology, though this requires applications that provide a sufficient level of support for OpenType Character Variant features. \n+These capabilities are available in any application that supports OpenType technology, though this requires applications that provide a sufficient level of support for OpenType Character Variant features. \n \n A sample of diacritic placement and kerning is shown below:\n \n@@ -27,22 +27,14 @@ This page uses web fonts (WOFF2) to demonstrate font features and should display\n \n ## Customizing with TypeTuner\n \n-For applications that do not make use of Graphite or the OpenType Stylistic Sets feature, you can now download fonts customized with the variant glyphs you choose. Read the [Font Features](features) page, visit [TypeTuner Web](https://scripts.sil.org/ttw/fonts2go.cgi), then to choose the variants and download your font.\n+For applications that do not make use of the OpenType Character Variant features, you can now download fonts customized with the variant glyphs you choose. Read the [Font Features](features) page, visit [TypeTuner Web](https://scripts.sil.org/ttw/fonts2go.cgi), then to choose the variants and download your font.\n \n \n ## Complete feature list\n \n-There are some Ethiopic character shape differences in different Ethiopian languages. These can be accessed by using Graphite features, OpenType Character Variants, or language support for Sebat Bet Gurage and Gumuz languages. The documents below can be downloaded in order to see all the user-selectable font features that are available in the font. The feature names, feature ids, settings and examples are provided. \n+There are some Ethiopic character shape differences in different Ethiopian languages. These can be accessed by using OpenType Character Variants or language support for Sebat Bet Gurage and Gumuz languages. The documents below can be downloaded in order to see all the user-selectable font features that are available in the font. The feature names, feature ids, settings and examples are provided. \n \n \n-### Test rendering engine choice \n-\n-Here is a simple test to see if Graphite is working in your browser. If it is, the following will say \"RenderingGraphite\". If your browser does not support Graphite it should say \"RenderingOpentype\". Firefox is currently the only browser that supports Graphite. See the [instructions on how to enable Graphite in Firefox](https://scripts.sil.org/cms/scripts/page.php?site_id=projects&item_id=graphite_firefox#switchon).\n-\n-| | \n-------------- | --------------- \n-Check | RenderingUnknown\n-\n ### Language \n \n Affects: U+124A, U+124D, U+1298..U+129F, U+12B2, U+12B5, U+12C2, U+12C5, U+1312, U+1313, U+1315, U+1381, U+1385, U+138D \n@@ -320,6 +312,16 @@ Feature | Sample | Feature setting\n Standard | ቍ ኵ ዅ ጕ | `cv85=0`\n Alternate | ቍ ኵ ዅ ጕ⁷ | `cv85=1`\n \n+### Ligatures\n+\n+#### gzi ligature\n+\n+Affects: U+130D U+200D U+12DA\n+\n+Feature | Sample | Feature setting\n+------------- | --------------- | ------------- \n+No Joiner | ግዚ | U+130D U+12DA\n+Using ZWJ | ግዚ | U+130D U+200D U+12DA\n \n \n ## References"
+ },
+ {
+ "sha": "7df43311d26981af06d213993ba82560edc8e2ac",
+ "filename": "fonts/sil/abyssinicasil/documentation/source/productsite/history.md",
+ "status": "modified",
+ "additions": 42,
+ "deletions": 0,
+ "changes": 42,
+ "blob_url": "https://github.com/silnrsi/fonts/blob/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fproductsite%2Fhistory.md",
+ "raw_url": "https://github.com/silnrsi/fonts/raw/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fproductsite%2Fhistory.md",
+ "contents_url": "https://api.github.com/repos/silnrsi/fonts/contents/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fproductsite%2Fhistory.md?ref=044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "patch": "@@ -1,4 +1,46 @@\n \n+### 29 Oct 2024 (WSTech Team) Abyssinica SIL version 2.300\n+\n+#### Improved\n+- Adjusted glyph shapes for\n+ - 1214 ETHIOPIC SYLLABLE HHEE\n+ - 1264 ETHIOPIC SYLLABLE BEE\n+ - 126C ETHIOPIC SYLLABLE VEE\n+ - 129C ETHIOPIC SYLLABLE NYEE\n+ - 12DC ETHIOPIC SYLLABLE ZEE\n+ - 1334 ETHIOPIC SYLLABLE PHEE\n+ - 133C ETHIOPIC SYLLABLE TSEE\n+ - AB14 ETHIOPIC SYLLABLE DZEE\n+ - AB2C ETHIOPIC SYLLABLE BBEE\n+ - 1E7E4 ETHIOPIC SYLLABLE HHYEE\n+ - 1E7EA ETHIOPIC SYLLABLE HHWEE\n+- Improve diacritic position to support multiple above diacritics\n+\n+#### Added\n+- Added gzi Ligature\n+- 2080 SUBSCRIPT ZERO\n+- 2081 SUBSCRIPT ONE\n+- 2082 SUBSCRIPT TWO\n+- 2083 SUBSCRIPT THREE\n+- 2084 SUBSCRIPT FOUR\n+- 2085 SUBSCRIPT FIVE\n+- 2086 SUBSCRIPT SIX\n+- 2087 SUBSCRIPT SEVEN\n+- 2088 SUBSCRIPT EIGHT\n+- 2089 SUBSCRIPT NINE\n+- 2460 CIRCLED DIGIT ONE\n+- 2461 CIRCLED DIGIT TWO\n+- 2462 CIRCLED DIGIT THREE\n+- 2463 CIRCLED DIGIT FOUR\n+- 2464 CIRCLED DIGIT FIVE\n+- 2465 CIRCLED DIGIT SIX\n+- 2466 CIRCLED DIGIT SEVEN\n+- 2467 CIRCLED DIGIT EIGHT\n+- 2468 CIRCLED DIGIT NINE\n+\n+#### Remove\n+- Graphite\n+\n ### 23 June 2023 (WSTech Team) Abyssinica SIL version 2.201\n - Fixed bug in TypeTuner support for cv46 tswa alternate\n "
+ },
+ {
+ "sha": "6312d9b3275e91bf5e23622153db8885c74a7fc4",
+ "filename": "fonts/sil/abyssinicasil/documentation/source/productsite/resources.md",
+ "status": "modified",
+ "additions": 5,
+ "deletions": 5,
+ "changes": 10,
+ "blob_url": "https://github.com/silnrsi/fonts/blob/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fproductsite%2Fresources.md",
+ "raw_url": "https://github.com/silnrsi/fonts/raw/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fproductsite%2Fresources.md",
+ "contents_url": "https://api.github.com/repos/silnrsi/fonts/contents/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fproductsite%2Fresources.md?ref=044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "patch": "@@ -5,7 +5,7 @@ This font is supported by all major operating systems (macOS, Windows, Linux-bas\n \n ## Installation\n \n-Install the font by decompressing the .zip archive and installing the font using the standard font installation process for .ttf (TrueType/OpenType) fonts for your platform. For additional tips see the help page on [Font installation](https://software.sil.org/fonts/installation).\n+Install the fonts by decompressing the .zip archive and installing the fonts using the standard font installation process for .ttf (TrueType/OpenType) fonts for your platform. For additional tips see the help page on [Font installation](https://software.sil.org/fonts/installation).\n \n ## Keyboarding and character set support\n \n@@ -38,17 +38,17 @@ See [Character set support](charset) for details of the Unicode characters suppo\n \n This font will work normally like any other font in most applications. If the writing system requires special diacritic positioning the application/OS will need to support OpenType.\n \n-Abyssinica SIL is designed to work with two advanced font technologies, [Graphite](https://graphite.sil.org/) and OpenType. To take advantage of the advanced typographic capabilities of this font, you must be using applications that provide an adequate level of support for Graphite or OpenType.\n+If special font features are to be activated the application will need to provide a way to turn on the feature or choose the feature setting. Details of current application support, and specific techniques for activating features, are on the [Using Font Features](https://software.sil.org/fonts/features) help page.\n \n-Other suggestions are listed here: [Using Font Features](https://software.sil.org/fonts/features/). \n+Although this current font supports only OpenType, previous versions provided support for the Graphite technology. Graphite was supported through version 2.2. These older versions remain available from our [Previous Versions archive](https://software.sil.org/abyssinica/download/previous-versions).\n \n ## Web fonts\n \n-Web font versions of this font (in WOFF and WOFF2 formats) are available in the `web` folder. These can be copied to a web server and used as fonts on web pages. A very basic HTML/CSS demo page is also included. For more information on the options and techniques available for using these fonts on web pages see [Using SIL Fonts on Web Pages](https://software.sil.org/fonts/webfonts).\n+Web font versions of these fonts (in WOFF and WOFF2 formats) are available in the `web` folder. These can be copied to a web server and used as fonts on web pages. A very basic HTML/CSS demo page is also included. For more information on the options and techniques available for using these fonts on web pages see [Using SIL Fonts on Web Pages](https://software.sil.org/fonts/webfonts).\n \n ## Text conversion\n \n-This font is encoded according to [The Unicode Standard](https://unicode.org). If you have text that uses a legacy, non-Unicode encoding there are tools that can help you convert that text for use with Unicode fonts. See [Introduction to Text Conversion and Transliteration](https://scriptsource.org/entry/xlzd6n5aqt).\n+This font is encoded according to [The Unicode Standard](https://www.unicode.org/). If you have text that uses a legacy, non-Unicode encoding there are tools that can help you convert that text for use with Unicode fonts. See [Introduction to Text Conversion and Transliteration](https://scriptsource.org/entry/xlzd6n5aqt).\n \n In order to use this font with existing data that was created for use with fonts developed using custom-encoded fonts, it is necessary to re-type or convert data to produce data that is encoded in conformance with the Unicode Standard. [SIL Converters](https://software.sil.org/silconverters/) and/or [TECkit](https://software.sil.org/teckit/) can be used for character encoding conversion. TECkit allows users to write their own custom conversion mappings.\n "
+ },
+ {
+ "sha": "40ab2ff0a7f44d6eb41a48fbae237358d2d8e081",
+ "filename": "fonts/sil/abyssinicasil/documentation/source/productsite/sample.md",
+ "status": "modified",
+ "additions": 6,
+ "deletions": 3,
+ "changes": 9,
+ "blob_url": "https://github.com/silnrsi/fonts/blob/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fproductsite%2Fsample.md",
+ "raw_url": "https://github.com/silnrsi/fonts/raw/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fproductsite%2Fsample.md",
+ "contents_url": "https://api.github.com/repos/silnrsi/fonts/contents/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fproductsite%2Fsample.md?ref=044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "patch": "@@ -37,8 +37,8 @@ This document demonstrates all of the characters in the font. It is organized by\n –—‘’‚“”„†‡•…‰‹›※⁄\n \n ### Superscripts and Subscripts\n-⁰⁴⁵⁶⁷⁸⁹\n \n+⁰⁴⁵⁶⁷⁸⁹ ₀₁₂₃₄₅₆₇₈₉\n \n ### Currency Symbols:\n \n@@ -48,15 +48,18 @@ This document demonstrates all of the characters in the font. It is organized by\n \n ™Ω ∂∅∆∏∑∙√∞∫≈≠≤≥ ␣ ◊ ◌ ✓\n \n+### Enclosed Alphanumerics\n+\n+①②③④⑤⑥⑦⑧⑨\n+\n ### Ethiopic:\n \n #### Syllables:\n \n ሀሁሂሃሄህሆሇ ለሉሊላሌልሎሏ ሐሑሒሓሔሕሖሗ መሙሚማሜምሞሟ ሠሡሢሣሤሥሦሧ ረሩሪራሬርሮሯ ሰሱሲሳሴስሶሷ ሸሹሺሻሼሽሾሿ ቀቁቂቃቄቅቆቇ ቈቊቋቌቍ ቐቑቒቓቔቕ ቖቘቚቛቜቝ በቡቢባቤብቦቧ ቨቩቪቫቬቭቮቯ ተቱቲታቴትቶቷ ቸቹቺቻቼችቾቿ ኀኁኂኃኄኅኆኇ ኈኊኋኌኍ ነኑኒናኔንኖኗ ኘኙኚኛኜኝኞኟ አኡኢኣኤእኦ ኧከኩኪካኬክኮኯ ኰኲኳኴኵ ኸኹኺኻኼኽኾዀዂዃዄዅ ወዉዊዋዌውዎዏ ዐዑዒዓዔዕዖ ዘዙዚዛዜዝዞዟ ዠዡዢዣዤዥዦዧ የዩዪያዬይዮዯ ደዱዲዳዴድዶዷ ዸዹዺዻዼዽዾዿ ጀጁጂጃጄጅጆጇ ገጉጊጋጌግጎጏጐጒጓጔጕ ጘጙጚጛጜጝጞጟ ጠጡጢጣጤጥጦጧ ጨጩጪጫጬጭጮጯ ጰጱጲጳጴጵጶጷ ጸጹጺጻጼጽጾጿ ፀፁፂፃፄፅፆፇ ፈፉፊፋፌፍፎፏ ፐፑፒፓፔፕፖፗ ፘ ፙ ፚ\n \n #### Combining Marks\n-◌፞◌፟◌፝\n-ሆ፞ሆ፟ሆ፝\n+◌፞◌፟◌፝ሆ፞ሆ፟ሆ፝ ሆ፞́ሆ፟́ሆ፝፟\n \n #### Punctuation\n ፠፡።፣፤፥፦፧፨"
+ },
+ {
+ "sha": "d27bacc40466ba2ff8f46a0c0ef35550d146ee43",
+ "filename": "fonts/sil/abyssinicasil/documentation/source/productsite/support.md",
+ "status": "modified",
+ "additions": 2,
+ "deletions": 2,
+ "changes": 4,
+ "blob_url": "https://github.com/silnrsi/fonts/blob/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fproductsite%2Fsupport.md",
+ "raw_url": "https://github.com/silnrsi/fonts/raw/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fproductsite%2Fsupport.md",
+ "contents_url": "https://api.github.com/repos/silnrsi/fonts/contents/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fproductsite%2Fsupport.md?ref=044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "patch": "@@ -1,7 +1,7 @@\n \n ## Support options\n \n-As this font is distributed at no cost, we are unable to provide a commercial level of personal technical support. We will, however, try to resolve problems that are reported to us.\n+As these fonts are distributed at no cost, we are unable to provide a commercial level of personal technical support. We will, however, try to resolve problems that are reported to us.\n \n Before requesting technical support, please **carefully read all the documentation included with the fonts and linked pages on the web site**. The [Resources page](resources) is a good place to begin.\n \n@@ -15,5 +15,5 @@ If you have a bug to report or a suggestion for how we could improve the font pl\n \n ## Contact form\n \n-If the documentation and community fail to answer your question or need further help using the font, please contact us using [the form on the Abyssinica SIL web site](https://software.sil.org/abyssinica/about/contact/).\n+If the documentation and community fail to answer your question or need further help using the fonts, please contact us using [the form on the Abyssinica SIL web site](https://software.sil.org/abyssinica/about/contact/).\n "
+ },
+ {
+ "sha": "e0d2e243404d8aaa15516e28ff977cadc80ed10d",
+ "filename": "fonts/sil/abyssinicasil/documentation/source/resources.md",
+ "status": "modified",
+ "additions": 6,
+ "deletions": 6,
+ "changes": 12,
+ "blob_url": "https://github.com/silnrsi/fonts/blob/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fresources.md",
+ "raw_url": "https://github.com/silnrsi/fonts/raw/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fresources.md",
+ "contents_url": "https://api.github.com/repos/silnrsi/fonts/contents/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fresources.md?ref=044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "patch": "@@ -1,6 +1,6 @@\n ---\n title: Abyssinica SIL - Resources\n-fontversion: 2.201\n+fontversion: 2.300\n ---\n \n ## Requirements\n@@ -9,7 +9,7 @@ This font is supported by all major operating systems (macOS, Windows, Linux-bas\n \n ## Installation\n \n-Install the font by decompressing the .zip archive and installing the font using the standard font installation process for .ttf (TrueType/OpenType) fonts for your platform. For additional tips see the help page on [Font installation](https://software.sil.org/fonts/installation).\n+Install the fonts by decompressing the .zip archive and installing the fonts using the standard font installation process for .ttf (TrueType/OpenType) fonts for your platform. For additional tips see the help page on [Font installation](https://software.sil.org/fonts/installation).\n \n ## Keyboarding and character set support\n \n@@ -42,17 +42,17 @@ See [Character set support](charset.md) for details of the Unicode characters su\n \n This font will work normally like any other font in most applications. If the writing system requires special diacritic positioning the application/OS will need to support OpenType.\n \n-Abyssinica SIL is designed to work with two advanced font technologies, [Graphite](https://graphite.sil.org/) and OpenType. To take advantage of the advanced typographic capabilities of this font, you must be using applications that provide an adequate level of support for Graphite or OpenType.\n+If special font features are to be activated the application will need to provide a way to turn on the feature or choose the feature setting. Details of current application support, and specific techniques for activating features, are on the [Using Font Features](https://software.sil.org/fonts/features) help page.\n \n-Other suggestions are listed here: [Using Font Features](https://software.sil.org/fonts/features/). \n+Although this current font supports only OpenType, previous versions provided support for the Graphite technology. Graphite was supported through version 2.2. These older versions remain available from our [Previous Versions archive](https://software.sil.org/abyssinica/download/previous-versions).\n \n ## Web fonts\n \n-Web font versions of this font (in WOFF and WOFF2 formats) are available in the `web` folder. These can be copied to a web server and used as fonts on web pages. A very basic HTML/CSS demo page is also included. For more information on the options and techniques available for using these fonts on web pages see [Using SIL Fonts on Web Pages](https://software.sil.org/fonts/webfonts).\n+Web font versions of these fonts (in WOFF and WOFF2 formats) are available in the `web` folder. These can be copied to a web server and used as fonts on web pages. A very basic HTML/CSS demo page is also included. For more information on the options and techniques available for using these fonts on web pages see [Using SIL Fonts on Web Pages](https://software.sil.org/fonts/webfonts).\n \n ## Text conversion\n \n-This font is encoded according to [The Unicode Standard](https://unicode.org). If you have text that uses a legacy, non-Unicode encoding there are tools that can help you convert that text for use with Unicode fonts. See [Introduction to Text Conversion and Transliteration](https://scriptsource.org/entry/xlzd6n5aqt).\n+This font is encoded according to [The Unicode Standard](https://www.unicode.org/). If you have text that uses a legacy, non-Unicode encoding there are tools that can help you convert that text for use with Unicode fonts. See [Introduction to Text Conversion and Transliteration](https://scriptsource.org/entry/xlzd6n5aqt).\n \n In order to use this font with existing data that was created for use with fonts developed using custom-encoded fonts, it is necessary to re-type or convert data to produce data that is encoded in conformance with the Unicode Standard. [SIL Converters](https://software.sil.org/silconverters/) and/or [TECkit](https://software.sil.org/teckit/) can be used for character encoding conversion. TECkit allows users to write their own custom conversion mappings.\n "
+ },
+ {
+ "sha": "93a8e7c600c4d0615272089aefb19c6c89c406a9",
+ "filename": "fonts/sil/abyssinicasil/documentation/source/sample.md",
+ "status": "modified",
+ "additions": 7,
+ "deletions": 4,
+ "changes": 11,
+ "blob_url": "https://github.com/silnrsi/fonts/blob/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fsample.md",
+ "raw_url": "https://github.com/silnrsi/fonts/raw/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fsample.md",
+ "contents_url": "https://api.github.com/repos/silnrsi/fonts/contents/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fsample.md?ref=044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "patch": "@@ -1,6 +1,6 @@\n ---\n title: Abyssinica SIL - Type Sample\n-fontversion: 2.201\n+fontversion: 2.300\n ---\n \n This document demonstrates all of the characters in the font. It is organized by Unicode block. Alternate glyphs that are available through features are demonstrated in the [Features](features.md) document. At the end is a sample demonstrating an example of running text.\n@@ -41,8 +41,8 @@ This document demonstrates all of the characters in the font. It is organized by\n –—‘’‚“”„†‡•…‰‹›※⁄\n \n ### Superscripts and Subscripts\n-⁰⁴⁵⁶⁷⁸⁹\n \n+⁰⁴⁵⁶⁷⁸⁹ ₀₁₂₃₄₅₆₇₈₉\n \n ### Currency Symbols:\n \n@@ -52,15 +52,18 @@ This document demonstrates all of the characters in the font. It is organized by\n \n ™Ω ∂∅∆∏∑∙√∞∫≈≠≤≥ ␣ ◊ ◌ ✓\n \n+### Enclosed Alphanumerics\n+\n+①②③④⑤⑥⑦⑧⑨\n+\n ### Ethiopic:\n \n #### Syllables:\n \n ሀሁሂሃሄህሆሇ ለሉሊላሌልሎሏ ሐሑሒሓሔሕሖሗ መሙሚማሜምሞሟ ሠሡሢሣሤሥሦሧ ረሩሪራሬርሮሯ ሰሱሲሳሴስሶሷ ሸሹሺሻሼሽሾሿ ቀቁቂቃቄቅቆቇ ቈቊቋቌቍ ቐቑቒቓቔቕ ቖቘቚቛቜቝ በቡቢባቤብቦቧ ቨቩቪቫቬቭቮቯ ተቱቲታቴትቶቷ ቸቹቺቻቼችቾቿ ኀኁኂኃኄኅኆኇ ኈኊኋኌኍ ነኑኒናኔንኖኗ ኘኙኚኛኜኝኞኟ አኡኢኣኤእኦ ኧከኩኪካኬክኮኯ ኰኲኳኴኵ ኸኹኺኻኼኽኾዀዂዃዄዅ ወዉዊዋዌውዎዏ ዐዑዒዓዔዕዖ ዘዙዚዛዜዝዞዟ ዠዡዢዣዤዥዦዧ የዩዪያዬይዮዯ ደዱዲዳዴድዶዷ ዸዹዺዻዼዽዾዿ ጀጁጂጃጄጅጆጇ ገጉጊጋጌግጎጏጐጒጓጔጕ ጘጙጚጛጜጝጞጟ ጠጡጢጣጤጥጦጧ ጨጩጪጫጬጭጮጯ ጰጱጲጳጴጵጶጷ ጸጹጺጻጼጽጾጿ ፀፁፂፃፄፅፆፇ ፈፉፊፋፌፍፎፏ ፐፑፒፓፔፕፖፗ ፘ ፙ ፚ\n \n #### Combining Marks\n-◌፞◌፟◌፝\n-ሆ፞ሆ፟ሆ፝\n+◌፞◌፟◌፝ሆ፞ሆ፟ሆ፝ ሆ፞́ሆ፟́ሆ፝፟\n \n #### Punctuation\n ፠፡።፣፤፥፦፧፨"
+ },
+ {
+ "sha": "30f4c5b0a0c2c416f698d6785d6c10183d0a75b2",
+ "filename": "fonts/sil/abyssinicasil/documentation/source/support.md",
+ "status": "modified",
+ "additions": 3,
+ "deletions": 3,
+ "changes": 6,
+ "blob_url": "https://github.com/silnrsi/fonts/blob/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fsupport.md",
+ "raw_url": "https://github.com/silnrsi/fonts/raw/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fsupport.md",
+ "contents_url": "https://api.github.com/repos/silnrsi/fonts/contents/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fsupport.md?ref=044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "patch": "@@ -1,11 +1,11 @@\n ---\n title: Abyssinica SIL - Support\n-fontversion: 2.201\n+fontversion: 2.300\n ---\n \n ## Support options\n \n-As this font is distributed at no cost, we are unable to provide a commercial level of personal technical support. We will, however, try to resolve problems that are reported to us.\n+As these fonts are distributed at no cost, we are unable to provide a commercial level of personal technical support. We will, however, try to resolve problems that are reported to us.\n \n Before requesting technical support, please **carefully read all the documentation included with the fonts and linked pages on the web site**. The [Resources page](resources.md) is a good place to begin.\n \n@@ -19,5 +19,5 @@ If you have a bug to report or a suggestion for how we could improve the font pl\n \n ## Contact form\n \n-If the documentation and community fail to answer your question or need further help using the font, please contact us using [the form on the Abyssinica SIL web site](https://software.sil.org/abyssinica/about/contact/).\n+If the documentation and community fail to answer your question or need further help using the fonts, please contact us using [the form on the Abyssinica SIL web site](https://software.sil.org/abyssinica/about/contact/).\n "
+ },
+ {
+ "sha": "002b9f540852d3f772e773eb940d1a3b683306aa",
+ "filename": "fonts/sil/abyssinicasil/documentation/source/template.html",
+ "status": "modified",
+ "additions": 1,
+ "deletions": 1,
+ "changes": 2,
+ "blob_url": "https://github.com/silnrsi/fonts/blob/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Ftemplate.html",
+ "raw_url": "https://github.com/silnrsi/fonts/raw/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Ftemplate.html",
+ "contents_url": "https://api.github.com/repos/silnrsi/fonts/contents/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Ftemplate.html?ref=044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "patch": "@@ -16,7 +16,7 @@
\n \n $body$\n \n \n "
+ },
+ {
+ "sha": "b3c1ca5e4241bf5ac8444c4ae946e010b673d7d1",
+ "filename": "fonts/sil/abyssinicasil/documentation/source/versions.md",
+ "status": "modified",
+ "additions": 3,
+ "deletions": 3,
+ "changes": 6,
+ "blob_url": "https://github.com/silnrsi/fonts/blob/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fversions.md",
+ "raw_url": "https://github.com/silnrsi/fonts/raw/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fversions.md",
+ "contents_url": "https://api.github.com/repos/silnrsi/fonts/contents/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsource%2Fversions.md?ref=044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "patch": "@@ -1,21 +1,21 @@\n ---\n title: Abyssinica SIL - Versions and Changes\n-fontversion: 2.201\n+fontversion: 2.300\n ---\n \n ## Announcement list\n \n If you would like stay informed of updates to Abyssinica SIL and other SIL fonts, please subscribe to the [SIL Font News Announcement List](https://groups.google.com/a/groups.sil.org/forum/#!forum/sil-font-news). For more information see [About](about.md).\n \n-Our font announcements are also available through Twitter [@silfonts](https://twitter.com/silfonts).\n+Our font announcements are also available through X (formerly Twitter) [\\@silfonts](https://x.com/silfonts).\n \n ## Current versions\n \n The latest version of the font is always available from the [Abyssinica SIL download page](https://software.sil.org/abyssinica/download/) as a .zip archive for all major platforms.\n \n This font package is also available in the [SIL software repository for Ubuntu](https://packages.sil.org/). Users can subscribe to this software repository and get current versions and updates automatically.\n \n-Abyssinica SIL is also available through the [TypeTuner Web](https://scripts.sil.org/ttw/fonts2go.cgi) service, which allows you to choose among the smart font features and download a font with those features preset. This enables them to work in many applications that do not make use of Graphite or OpenType Character Variants.\n+Abyssinica SIL is also available through the [TypeTuner Web](https://scripts.sil.org/ttw/fonts2go.cgi) service, which allows you to choose among the smart font features and download a font with those features preset. This enables them to work in many applications that do not make use of OpenType Character Variants.\n \n ## Previous versions\n "
+ },
+ {
+ "sha": "d4fe29f03a5643edd4328e9933c83b74048ac040",
+ "filename": "fonts/sil/abyssinicasil/documentation/support.html",
+ "status": "modified",
+ "additions": 25,
+ "deletions": 8,
+ "changes": 33,
+ "blob_url": "https://github.com/silnrsi/fonts/blob/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsupport.html",
+ "raw_url": "https://github.com/silnrsi/fonts/raw/044a10426cdabfa3dd3b13d040a56d4b70ea4058/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsupport.html",
+ "contents_url": "https://api.github.com/repos/silnrsi/fonts/contents/fonts%2Fsil%2Fabyssinicasil%2Fdocumentation%2Fsupport.html?ref=044a10426cdabfa3dd3b13d040a56d4b70ea4058",
+ "patch": "@@ -15,16 +15,33 @@\n
Abyssinica SIL - Support
\n \n
Support options
\n-
As this font is distributed at no cost, we are unable to provide a commercial level of personal technical support. We will, however, try to resolve problems that are reported to us.
\n-
Before requesting technical support, please carefully read all the documentation included with the fonts and linked pages on the web site. The Resources page is a good place to begin.
\n-
Language Software Community
\n-
For person-to-person support visit the SIL Language Software Community, where font developers and users can help each other. These support discussions can also help others in the future.
\n-
Reporting bugs and feature requests
\n-
If you have a bug to report or a suggestion for how we could improve the font please create an issue in the Github Abyssinica SIL project or contact us directly.
\n+
As these fonts are distributed at no cost, we are unable to\n+ provide a commercial level of personal technical support. We will,\n+ however, try to resolve problems that are reported to us.
\n+
Before requesting technical support, please carefully\n+ read all the documentation included with the fonts and linked pages\n+ on the web site. The Resources\n+ page is a good place to begin.
\n+
Language Software\n+ Community
\n+
For person-to-person support visit the SIL Language\n+ Software Community, where font developers and users can help\n+ each other. These support discussions can also help others in the\n+ future.
\n+
Reporting bugs and\n+ feature requests
\n+
If you have a bug to report or a suggestion for how we could\n+ improve the font please create an issue in the Github\n+ Abyssinica SIL project or contact us directly.
\n
Contact form
\n-
If the documentation and community fail to answer your question or need further help using the font, please contact us using the form on the Abyssinica SIL web site.
\n+
If the documentation and community fail to answer your question\n+ or need further help using the fonts, please contact us using the form\n+ on the Abyssinica SIL web site.
If you would like stay informed of updates to Abyssinica SIL and other SIL fonts, please subscribe to the SIL Font News Announcement List. For more information see About.
\n-
Our font announcements are also available through Twitter [@silfonts](https://twitter.com/silfonts).
\n+
If you would like stay informed of updates to Abyssinica SIL and\n+ other SIL fonts, please subscribe to the SIL\n+ Font News Announcement List. For more information see About.
\n+
Our font announcements are also available through X (formerly\n+ Twitter) @silfonts.
\n
Current versions
\n-
The latest version of the font is always available from the Abyssinica SIL download page as a .zip archive for all major platforms.
\n-
This font package is also available in the SIL software repository for Ubuntu. Users can subscribe to this software repository and get current versions and updates automatically.
\n-
Abyssinica SIL is also available through the TypeTuner Web service, which allows you to choose among the smart font features and download a font with those features preset. This enables them to work in many applications that do not make use of Graphite or OpenType Character Variants.
\n+
The latest version of the font is always available from the Abyssinica SIL\n+ download page as a .zip archive for all major platforms.
\n+
This font package is also available in the SIL software repository for\n+ Ubuntu. Users can subscribe to this software repository and get\n+ current versions and updates automatically.
\n+
Abyssinica SIL is also available through the TypeTuner Web\n+ service, which allows you to choose among the smart font features\n+ and download a font with those features preset. This enables them to\n+ work in many applications that do not make use of OpenType Character\n+ Variants.