Path to ttf2afm in setup.php does not match files in download package

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Download, unzip 0.6-beta2. Run /www/setup.php.

ttf2afm reports it is not writeable. 
Expected path is [stuff]/dompdf/lib/ttf2ufm/ttf2ufm-src/ttf2pt1.
Actual ttf2ufm directory contains src, not ttf2ufm-src.
Actual src directory contains ttf2pt1.1 and ttf2pt1.c, but not ttf2pt1.

Renaming src and ttf2pt1.1 seems to have solved the problem.

Original issue reported on code.google.com by st...@sillybean.net on 10 Oct 2011 at 7:22

[GoogleCodeExporter]

We've made some changes to the ttf2ufm directory. We'll need to update the path 
referenced by the configuration file, but really you should build your own copy 
of the file. We haven't done thorough testing on the version included ... it's 
just a placeholder at this point.

Hopefully for the final 0.6.0 release we'll have a better option built in.

Original comment by eclecticgeek on 12 Oct 2011 at 2:10

• Changed state: Accepted

[GoogleCodeExporter]

Ah. In that case, just mentioning the need to build a copy of the file in the 
installation instructions would help. I came away with the impression that it 
was all set to work as-is.

Original comment by st...@sillybean.net on 12 Oct 2011 at 2:16

[GoogleCodeExporter]

That would also be a good idea. I think a binary might be included (I'll 
double-check when I address this issue), but I don't know that it's universal.

Original comment by eclecticgeek on 12 Oct 2011 at 2:20

[GoogleCodeExporter]

This is not really an issue, and we'll remove this dependency as we can 
generated UFM files with the php-font-lib now.

Original comment by fabien.menager on 23 Oct 2011 at 2:40

• Changed state: Invalid

[GoogleCodeExporter]

Original comment by eclecticgeek on 30 May 2013 at 5:16

• Added labels: Restrict-AddIssueComment-Commit