[pkg] Upstream: Licence-patch .vfb/VTT .ttf/.cfg
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ubuntu Font Family |
Confirmed
|
Low
|
Paul Sladen | ||
Bug Description
The upstream packaging is done by unpackaging and running:
http://
Further additions are needed, in order to patch licence information into the source files themselves:
* Prepend a filled out 'copyright.txt' to the CacheTT .cfg (easy)
* Execute 'patch-truetype' over the VTT .ttfs (easy)
* investigate the .vfb format and work out how to patch that internally (unknown)
Non-licensing:
* RELEASENOTES.txt: run through recode to remove the MS Windows magic quotes
* FONTLOG: fix URLs and spelling of 'foundry'
* TRADEMARKS.txt: link to http://
* SOURCES.txt: note limited/trial version for FS5. Fix spelling error.
| description: | updated |
| Changed in ubuntu-font-family: | |
| assignee: | nobody → Paul Sladen (sladen) |
| importance: | Undecided → Low |
| status: | New → Confirmed |
| summary: |
- Upstream: Licence-patch .vfb/VTT .ttf/.cfg + [pkg] Upstream: Licence-patch .vfb/VTT .ttf/.cfg |
| Paul Sladen (sladen) wrote | #1 |
Probably 5 minutes + 1 hour + 2 hours.
The blocker for patching in variable-length (possibly longer) strings is to confirm that the VTT/VFB files remain usable.
To add of note is that Volt is now used for the Arabic Hebrew build. This format needs investigation.
A quicker solution would be blank out any problematic strings with ' ' spaces, and then keep all the copyright information relating to the intermediate source files in an external file.