Font family not parsed correctly about dompdf

[GoogleCodeExporter]

Turns out the problem is not that DOMPDF was treating the value of font-family 
as a
single font name. Upon exception DOMPDF was reporting the value of font-family 
as
written. While processing of the list, however, DOMPDF was correctly parsing the
string and attempting to match each individual entry to a font mapping. The 
problem
was that after exploding the font-family string the resulting array of 
alternatives
were not at any point trimmed. This resulted in leading spaces for entries 
after the
first font.

To fix this I used array_map() to pass each value to trim. See
style.cls.php@get_font_family().

Note: We might also consider using trim in font_metrics.cls.php@get_font() to 
further
ensure the font is read correctly. I don't imagine there are many (any) font 
names
with a leading or trailing space.

Original comment by eclecticgeek on 3 Jun 2009 at 5:01

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by eclecticgeek on 31 Jul 2009 at 3:40

• Added labels: Milestone-Release0.6

[GoogleCodeExporter]

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

• Added labels: Restrict-AddIssueComment-Commit