Hi,
Create an issue in JIRA with your code change appended as a .patch or
.diff file against the current trunk.
The change should not break the existing API (i.e. existing use code
should still work with the new library) or it can't be included in 2.*
but only in the trunk. It should include an example, and if
possible/useful, tests of your new code.
Tilman
Am 11.02.2018 um 16:01 schrieb Aaron Madlon-Kay:
Hello.
A while ago I inquired about creating PDFs with vertical text in the user list:
https://lists.apache.org/thread.html/2825e7a67fcc3f923b102eeedc29c44b48a3b0d1b681d6d82b8da1c1@%3Cusers.pdfbox.apache.org%3E
For my immediate needs I ended up following the advice I received from John
Hewson and froze the ‘vert’ feature into my font, and brute-force set the
encoding to Identity-V. However I thought it would be nice to have a proper
solution for the future, so I have implemented it here:
https://github.com/amake/pdfbox/tree/vertical
This branch includes:
- GSUB table parsing (everything but LookupTables other than type 1)
- GSUB lookup (excluding features that need LookupTables other than type 1)
- An API for loading a TTF as a vertical font, with ‘vrt2’ or ‘vert’
substitution
- An API for specifying additional GSUB features
- Applying ‘vhea’ and ‘vmtx’ to CIDFont: on load, when subsetting, or when
embedding without subsetting
I would like to contribute this to the project. Any advice on how to proceed
would be greatly appreciated.
Thanks,
Aaron
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
