[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#351025: ITP: ttf-sil-charis smart Unicode font family for Roman or Cyrillic-based writing systems



Package: wnpp
Severity: wishlist

Description: The goal for Charis SIL was to provide a single
Unicode-based font family that would contain a comprehensive inventory
of glyphs needed for almost any Roman- or Cyrillic-based writing system,
whether used for phonetic or orthographic needs. In addition, there is
provision for other characters and symbols useful to linguists. This
font makes use of state-of-the-art font technologies to support complex
typographic issues, such as the need to position arbitrary combinations
of base glyphs and diacritics optimally.

 Four fonts from this typeface family are included in this release:
    * Charis SIL Regular
    * Charis SIL Bold
    * Charis SIL Italic
    * Charis SIL Bold Italic
 .
 Charis SIL is a TrueType font with "smart font" capabilities added
using the Graphite, OpenType(r), and AAT font technologies. This means
that complex typographic issues such as the placement of diacritics or
the formation of ligatures are handled by the font, provided you are
running an application that provides an adequate level of support for
one of these smart font technologies.
 .
 Charis SIL is released under the SIL Open Font License.
 Charis SIL is a trademark of SIL International.
 .
 See the OFL and OFL-FAQ for details of the SIL Open Font License.
 See the FONTLOG for information on this and previous releases.
 See the CharisSIL4FontDocumentation.pdf or the font FAQ
 (http://scripts.sil.org/DoulosSILfontFAQ) for frequently
 asked questions and their answers.

License:
The OFL may be found at http://scripts.sil.org/OFL
It is listed on http://www.fsf.org/licensing/licenses/index_html as a
license suitable for fonts.
debian-legal hasn't come to a consensus about the license yet so I won't
upload until that happens. I will be sponsoring the upload on behalf of
an upstream maintainer.

Regards,
Daniel



Reply to: