Bug#617718: ITP: libgraphite2-2.0.0 -- a "smart font" rendering engine -- library
On Thu, Mar 10, 2011 at 9:14 PM, Rene Engelhard <rene@debian.org> wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Rene Engelhard <rene@debian.org>
>
> * Package name : libgraphite2-2.0.0
> Version : 0.9.3
> Upstream Author : SIL International
> * URL : http://sf.net/projects/silgraphite
> * License : LGPL
> Programming Lang: C++
> Description : a "smart font" rendering engine -- library
>
> Graphite is a system that can be used to create and use "smart fonts" capable
> of displaying writing systems with various complex behaviors, such as:
> contextual shaping, ligatures, reordering, split glyphs, bidirectionality,
> stacking diacritics and complex positioning.
> .
> This library was designed and developed by the NRSI (Non-Roman Script
> Initiative) within SIL International (www.sil.org) to act as a complement to
> other smart font rendering technologies with limited practical local
> extensability. Its purpose is to help meet the needs of a very large number
> of "minority language" communities for local extensibility of complex script
> behaviors.
> .
> The behavior of the rendering engine for a given writing system is specified
> through extra tables added to a TrueType font. These tables are generated by
> compiling a GDL (Graphite Description Language) source file into a font using
> grcompiler.
> .
> This package contains the shared library.
>
> This seems to be the successor of silgraphite2.0(sic!) which is libgraphite3 and
> LibreOffice is going to switch to graphite2.
Indeed
> Daniel, would you want to (co-)maintain it? I have a package (on upstreams
> Debian packaging fixed up) here already :-)
Hi Rene,
Funnily enough I was starting to fix up upstreams packaging myself
earlier. Yes, I'd like to co-maintain it. I think it is good for the
LibreOffice packaging team to be part of maintaining it to make sure
there are no breakages there. And I can hopefully be a good link with
upsteam.
I think we should upload to experimental first as it is still under
development heading for the 1.0 release.
Thanks,
Daniel
Reply to: