automatic import of python-statmake

3 files changed, 216 insertions, 0 deletions

diff --git a/.gitignore b/.gitignore
index e69de29..2093a27 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/statmake-0.6.0.tar.gz
diff --git a/python-statmake.spec b/python-statmake.spec
new file mode 100644
index 0000000..a8d7de1
--- /dev/null
+++ b/python-statmake.spec
@@ -0,0 +1,214 @@
+%global _empty_manifest_terminate_build 0
+Name:		python-statmake
+Version:	0.6.0
+Release:	1
+Summary:	Applies STAT information from a Stylespace to a variable font.
+License:	MIT
+URL:		https://github.com/daltonmaag/statmake
+Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/53/48/af7ad7214f6b90ae4f396e93e2053e7056ebe6b5ef04b5bbc255ad44ec7e/statmake-0.6.0.tar.gz
+BuildArch:	noarch
+
+Requires:	python3-attrs
+Requires:	python3-cattrs
+Requires:	python3-fonttools[ufo]
+Requires:	python3-importlib_metadata
+
+%description
+# statmake
+
+`statmake` takes a user-written Stylespace that defines [OpenType `STAT` information](https://docs.microsoft.com/en-us/typography/opentype/spec/stat) for an entire font family and then (potentially subsets and) applies it to a specific variable font. This spares users from having to deal with [raw TTX dumps](https://github.com/fonttools/fonttools/) and juggling with nameIDs.
+
+## Installation
+
+The easiest way is by installing it with `pip`. You need at least Python 3.7.
+
+```
+pip3 install statmake
+```
+
+## Usage
+
+
+### External Stylespace file, stand-alone or referenced from a Designspace file
+
+If you are producing more than one variable font (i.e. you have multiple Designspace files), you can avoid duplicated information by writing a single all-encompassing Stylespace file which statmake will subset for each variable font.
+
+**Attention:** A `STAT` table is supposed to describe a font's relationship to the _entire_ family. If you have separate upright and italic variable fonts with a `wght` axis each, you need to mark each font's position on the `ital` axis _in the Designspace lib `org.statmake.additionalLocations` key_. The Designspace `<axes>` elements are not supposed to hold this information, so it must be done in a separate lib key.
+
+1. Write a Stylespace file that describes each stop of all axes available in the entire family. See [tests/data/Test.stylespace](tests/data/Test.stylespace) for an annotated example. You can also use it as a starting point.
+2. You can have the file stand-alone or use the Designspace lib's `org.statmake.stylespacePath` key to store the path to the Stylespace file relative to the Designspace file. See [tests/data/TestExternalStylespace.designspace](tests/data/TestExternalStylespace.designspace) for an example.
+3. If you have one or more Designspace files which do not define all axes available to the family, you have to annotate them with the missing axis locations to get a complete `STAT` table. See the lib key at the bottom of [tests/data/Test_Wght_Upright.designspace](tests/data/Test_Wght_Upright.designspace) and [tests/data/Test_Wght_Italic.designspace](tests/data/Test_Wght_Italic.designspace) for an example.
+4. Generate the variable font(s) as normal
+5. If...
+    1. ... you store the Stylespace file stand-alone: run `statmake --designspace variable_font.designspace --stylespace your.stylespace variable_font.ttf`.
+    2. ... you store the Stylespace inline in the Designspace file or as a stand-alone file and added the relative path to it in the Designspace's `org.statmake.stylespacePath` key: run `statmake --designspace variable_font.designspace variable_font.ttf`
+
+Be sure to use the Designspace file that was used to generate the font to get the correct missing axis location definitions.
+
+### Designspace file with inline Stylespace data
+
+If you are producing a single variable font containing an entire family, this approach will save you an external file.
+
+1. Write the file as above, point 1.
+2. Insert it into the Designspace file's lib under the `org.statmake.stylespace` key. See [tests/data/TestInlineStylespace.designspace](tests/data/TestInlineStylespace.designspace) for an example.
+3. Proceed from point 3 above.
+
+## Q: Can I please have something other than a .plist file?
+
+Yes, but you have to convert it to `.plist` yourself, as statmake currently only read `.plist` files. One possible converter is Adam Twardoch's [yaplon](https://pypi.org/project/yaplon/).
+
+## Q: I'm getting errors about how statmake doesn't like the way I wrote the Stylespace, but I want the data to be that way?
+
+Use a custom script with the https://fonttools.readthedocs.io/en/latest/otlLib/builder.html#fontTools.otlLib.builder.buildStatTable API instead.
+
+
+%package -n python3-statmake
+Summary:	Applies STAT information from a Stylespace to a variable font.
+Provides:	python-statmake
+BuildRequires:	python3-devel
+BuildRequires:	python3-setuptools
+BuildRequires:	python3-pip
+%description -n python3-statmake
+# statmake
+
+`statmake` takes a user-written Stylespace that defines [OpenType `STAT` information](https://docs.microsoft.com/en-us/typography/opentype/spec/stat) for an entire font family and then (potentially subsets and) applies it to a specific variable font. This spares users from having to deal with [raw TTX dumps](https://github.com/fonttools/fonttools/) and juggling with nameIDs.
+
+## Installation
+
+The easiest way is by installing it with `pip`. You need at least Python 3.7.
+
+```
+pip3 install statmake
+```
+
+## Usage
+
+
+### External Stylespace file, stand-alone or referenced from a Designspace file
+
+If you are producing more than one variable font (i.e. you have multiple Designspace files), you can avoid duplicated information by writing a single all-encompassing Stylespace file which statmake will subset for each variable font.
+
+**Attention:** A `STAT` table is supposed to describe a font's relationship to the _entire_ family. If you have separate upright and italic variable fonts with a `wght` axis each, you need to mark each font's position on the `ital` axis _in the Designspace lib `org.statmake.additionalLocations` key_. The Designspace `<axes>` elements are not supposed to hold this information, so it must be done in a separate lib key.
+
+1. Write a Stylespace file that describes each stop of all axes available in the entire family. See [tests/data/Test.stylespace](tests/data/Test.stylespace) for an annotated example. You can also use it as a starting point.
+2. You can have the file stand-alone or use the Designspace lib's `org.statmake.stylespacePath` key to store the path to the Stylespace file relative to the Designspace file. See [tests/data/TestExternalStylespace.designspace](tests/data/TestExternalStylespace.designspace) for an example.
+3. If you have one or more Designspace files which do not define all axes available to the family, you have to annotate them with the missing axis locations to get a complete `STAT` table. See the lib key at the bottom of [tests/data/Test_Wght_Upright.designspace](tests/data/Test_Wght_Upright.designspace) and [tests/data/Test_Wght_Italic.designspace](tests/data/Test_Wght_Italic.designspace) for an example.
+4. Generate the variable font(s) as normal
+5. If...
+    1. ... you store the Stylespace file stand-alone: run `statmake --designspace variable_font.designspace --stylespace your.stylespace variable_font.ttf`.
+    2. ... you store the Stylespace inline in the Designspace file or as a stand-alone file and added the relative path to it in the Designspace's `org.statmake.stylespacePath` key: run `statmake --designspace variable_font.designspace variable_font.ttf`
+
+Be sure to use the Designspace file that was used to generate the font to get the correct missing axis location definitions.
+
+### Designspace file with inline Stylespace data
+
+If you are producing a single variable font containing an entire family, this approach will save you an external file.
+
+1. Write the file as above, point 1.
+2. Insert it into the Designspace file's lib under the `org.statmake.stylespace` key. See [tests/data/TestInlineStylespace.designspace](tests/data/TestInlineStylespace.designspace) for an example.
+3. Proceed from point 3 above.
+
+## Q: Can I please have something other than a .plist file?
+
+Yes, but you have to convert it to `.plist` yourself, as statmake currently only read `.plist` files. One possible converter is Adam Twardoch's [yaplon](https://pypi.org/project/yaplon/).
+
+## Q: I'm getting errors about how statmake doesn't like the way I wrote the Stylespace, but I want the data to be that way?
+
+Use a custom script with the https://fonttools.readthedocs.io/en/latest/otlLib/builder.html#fontTools.otlLib.builder.buildStatTable API instead.
+
+
+%package help
+Summary:	Development documents and examples for statmake
+Provides:	python3-statmake-doc
+%description help
+# statmake
+
+`statmake` takes a user-written Stylespace that defines [OpenType `STAT` information](https://docs.microsoft.com/en-us/typography/opentype/spec/stat) for an entire font family and then (potentially subsets and) applies it to a specific variable font. This spares users from having to deal with [raw TTX dumps](https://github.com/fonttools/fonttools/) and juggling with nameIDs.
+
+## Installation
+
+The easiest way is by installing it with `pip`. You need at least Python 3.7.
+
+```
+pip3 install statmake
+```
+
+## Usage
+
+
+### External Stylespace file, stand-alone or referenced from a Designspace file
+
+If you are producing more than one variable font (i.e. you have multiple Designspace files), you can avoid duplicated information by writing a single all-encompassing Stylespace file which statmake will subset for each variable font.
+
+**Attention:** A `STAT` table is supposed to describe a font's relationship to the _entire_ family. If you have separate upright and italic variable fonts with a `wght` axis each, you need to mark each font's position on the `ital` axis _in the Designspace lib `org.statmake.additionalLocations` key_. The Designspace `<axes>` elements are not supposed to hold this information, so it must be done in a separate lib key.
+
+1. Write a Stylespace file that describes each stop of all axes available in the entire family. See [tests/data/Test.stylespace](tests/data/Test.stylespace) for an annotated example. You can also use it as a starting point.
+2. You can have the file stand-alone or use the Designspace lib's `org.statmake.stylespacePath` key to store the path to the Stylespace file relative to the Designspace file. See [tests/data/TestExternalStylespace.designspace](tests/data/TestExternalStylespace.designspace) for an example.
+3. If you have one or more Designspace files which do not define all axes available to the family, you have to annotate them with the missing axis locations to get a complete `STAT` table. See the lib key at the bottom of [tests/data/Test_Wght_Upright.designspace](tests/data/Test_Wght_Upright.designspace) and [tests/data/Test_Wght_Italic.designspace](tests/data/Test_Wght_Italic.designspace) for an example.
+4. Generate the variable font(s) as normal
+5. If...
+    1. ... you store the Stylespace file stand-alone: run `statmake --designspace variable_font.designspace --stylespace your.stylespace variable_font.ttf`.
+    2. ... you store the Stylespace inline in the Designspace file or as a stand-alone file and added the relative path to it in the Designspace's `org.statmake.stylespacePath` key: run `statmake --designspace variable_font.designspace variable_font.ttf`
+
+Be sure to use the Designspace file that was used to generate the font to get the correct missing axis location definitions.
+
+### Designspace file with inline Stylespace data
+
+If you are producing a single variable font containing an entire family, this approach will save you an external file.
+
+1. Write the file as above, point 1.
+2. Insert it into the Designspace file's lib under the `org.statmake.stylespace` key. See [tests/data/TestInlineStylespace.designspace](tests/data/TestInlineStylespace.designspace) for an example.
+3. Proceed from point 3 above.
+
+## Q: Can I please have something other than a .plist file?
+
+Yes, but you have to convert it to `.plist` yourself, as statmake currently only read `.plist` files. One possible converter is Adam Twardoch's [yaplon](https://pypi.org/project/yaplon/).
+
+## Q: I'm getting errors about how statmake doesn't like the way I wrote the Stylespace, but I want the data to be that way?
+
+Use a custom script with the https://fonttools.readthedocs.io/en/latest/otlLib/builder.html#fontTools.otlLib.builder.buildStatTable API instead.
+
+
+%prep
+%autosetup -n statmake-0.6.0
+
+%build
+%py3_build
+
+%install
+%py3_install
+install -d -m755 %{buildroot}/%{_pkgdocdir}
+if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi
+if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi
+if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi
+if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi
+pushd %{buildroot}
+if [ -d usr/lib ]; then
+	find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst
+fi
+if [ -d usr/lib64 ]; then
+	find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst
+fi
+if [ -d usr/bin ]; then
+	find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst
+fi
+if [ -d usr/sbin ]; then
+	find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst
+fi
+touch doclist.lst
+if [ -d usr/share/man ]; then
+	find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst
+fi
+popd
+mv %{buildroot}/filelist.lst .
+mv %{buildroot}/doclist.lst .
+
+%files -n python3-statmake -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Mon May 15 2023 Python_Bot <Python_Bot@openeuler.org> - 0.6.0-1
+- Package Spec generated
diff --git a/sources b/sources
new file mode 100644
index 0000000..ffc555f
--- /dev/null
+++ b/sources
@@ -0,0 +1 @@
+c774d56019e2815c42b37b57d5df0c13  statmake-0.6.0.tar.gz