/usr/lib/python3/dist-packages/ufo2ft-1.1.0.egg-info/PKG-INFO is in python3-ufo2ft 1.1.0-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 | Metadata-Version: 1.1
Name: ufo2ft
Version: 1.1.0
Summary: A bridge between UFOs and FontTools.
Home-page: https://github.com/googlei18n/ufo2ft
Author: James Godfrey-Kittle
Author-email: jamesgk@google.com
License: MIT
Description-Content-Type: UNKNOWN
Description: |Travis CI Status| |Appveyor CI Status| |PyPI Version| |Codecov|
ufo2ft
======
ufo2ft ("UFO to FontTools") is a fork of
`ufo2fdk <https://github.com/typesupply/ufo2fdk>`__ whose goal is to
generate OpenType font binaries from UFOs without the FDK dependency.
The library provides two functions, ``compileOTF`` and ``compileTTF``,
which work exactly the same way:
.. code:: python
from defcon import Font
from ufo2ft import compileOTF
ufo = Font('MyFont-Regular.ufo')
otf = compileOTF(ufo)
otf.save('MyFont-Regular.otf')
In most cases, the behavior of ufo2ft should match that of ufo2fdk,
whose documentation is retained below (and hopefully is still accurate).
Naming Data
~~~~~~~~~~~
As with any OpenType compiler, you have to set the font naming data to a
particular standard for your naming to be set correctly. In ufo2fdk, you
can get away with setting *two* naming attributes in your font.info
object for simple fonts:
- familyName: The name for your family. For example, "My Garamond".
- styleName: The style name for this particular font. For example,
"Display Light Italic"
ufo2fdk will create all of the other naming data based on thse two
fields. If you want to use the fully automatic naming system, all of the
other name attributes should be set to ``None`` in your font. However,
if you want to override the automated system at any level, you can
specify particular naming attributes and ufo2fdk will honor your
settings. You don't have to set *all* of the attributes, just the ones
you don't want to be automated. For example, in the family "My Garamond"
you have eight weights. It would be nice to style map the italics to the
romans for each weight. To do this, in the individual romans and
italics, you need to set the style mapping data. This is done through
the ``styleMapFamilyName`` and ``styleMapStyleName`` attributes. In each
of your roman and italic pairs you would do this:
**My Garamond-Light.ufo**
- familyName = "My Garamond"
- styleName = "Light"
- styleMapFamilyName = "My Garamond Display Light"
- styleMapStyleName = "regular"
**My Garamond-Light Italic.ufo**
- familyName = "My Garamond"
- styleName = "Display Light Italic"
- styleMapFamilyName = "My Garamond Display Light"
- styleMapStyleName = "italic"
**My Garamond-Book.ufo**
- familyName = "My Garamond"
- styleName = "Book"
- styleMapFamilyName = "My Garamond Display Book"
- styleMapStyleName = "regular"
**My Garamond-Book Italic.ufo**
- familyName = "My Garamond"
- styleName = "Display Book Italic"
- styleMapFamilyName = "My Garamond Display Book"
- styleMapStyleName = "italic"
**etc.**
Additionally, if you have defined any naming data, or any data for that
matter, in table definitions within your font's features that data will
be honored.
Feature generation
~~~~~~~~~~~~~~~~~~
If your font's features do not contain kerning/mark/mkmk features,
ufo2ft will create them based on your font's kerning/anchor data.
In addition to
`Adobe OpenType feature files <http://www.adobe.com/devnet/opentype/afdko/topic_feature_file_syntax.html>`__,
ufo2ft also supports the
`MTI/Monotype format <http://monotype.github.io/OpenType_Table_Source/otl_source.html>`__.
For example, a GPOS table in this format would be stored within the UFO at
``data/com.github.googlei18n.ufo2ft.mtiFeatures/GPOS.mti``.
Fallbacks
~~~~~~~~~
Most of the fallbacks have static values. To see what is set for these,
look at ``fontInfoData.py`` in the source code.
In some cases, the fallback values are dynamically generated from other
data in the info object. These are handled internally with functions.
Merging TTX
~~~~~~~~~~~
If the UFO data directory has a ``com.github.fonttools.ttx`` folder with TTX
files ending with ``.ttx``, these will be merged in the generated font.
The index TTX (generated when using using ``ttx -s``) is not required.
.. |Travis CI Status| image:: https://travis-ci.org/googlei18n/ufo2ft.svg
:target: https://travis-ci.org/googlei18n/ufo2ft
.. |Appveyor CI status| image:: https://ci.appveyor.com/api/projects/status/jaw9bi221plmjlny/branch/master?svg=true
:target: https://ci.appveyor.com/project/fonttools/ufo2ft/branch/master
.. |PyPI Version| image:: https://img.shields.io/pypi/v/ufo2ft.svg
:target: https://pypi.org/project/ufo2ft/
.. |Codecov| image:: https://codecov.io/gh/googlei18n/ufo2ft/branch/master/graph/badge.svg
:target: https://codecov.io/gh/googlei18n/ufo2ft
Platform: UNKNOWN
Classifier: Development Status :: 4 - Beta
Classifier: Environment :: Console
Classifier: Environment :: Other Environment
Classifier: Intended Audience :: Developers
Classifier: Intended Audience :: End Users/Desktop
Classifier: License :: OSI Approved :: MIT License
Classifier: Natural Language :: English
Classifier: Operating System :: OS Independent
Classifier: Programming Language :: Python
Classifier: Programming Language :: Python :: 2
Classifier: Programming Language :: Python :: 3
Classifier: Topic :: Multimedia :: Graphics
Classifier: Topic :: Multimedia :: Graphics :: Graphics Conversion
Classifier: Topic :: Multimedia :: Graphics :: Editors :: Vector-Based
Classifier: Topic :: Software Development :: Libraries :: Python Modules
|