Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

anchor-links are broken in utf-8 document in 0.6.0b1 #253

Closed
PhenX opened this issue Dec 6, 2012 · 2 comments
Closed

anchor-links are broken in utf-8 document in 0.6.0b1 #253

PhenX opened this issue Dec 6, 2012 · 2 comments

Comments

@PhenX
Copy link
Member

PhenX commented Dec 6, 2012

Original author: abahl...@gmail.com (March 12, 2011 17:28:09)

What steps will reproduce the problem?

Create a document:

  1. create an utf-8 document
  2. put some anchors in the document, <a href="http://somesite.com&quot;&gt;example&lt;/a> e.g.

See also attachment.

Prepare Times New Roman:

  1. In windows xp, convert your Times New Roman font with the webbased font-load tool [http://eclecticgeek.com/dompdf/load_font.php]
  2. Install the fonts from the resulting zip in the dompdf installation

What is the expected output? What do you see instead?
Expected output is a correctly working link, but all links, no matter what the href attribute says do link to a bogus address *if the styling with font-family "Times New Roman" is applied to it.

The built-in Times doesn't have that problem.

What version of the product are you using? On what operating system?
0.6.0b1 on windows xp
In 0.6.0b2 this has been solved, but this version is unusable due to the rendering bugs.

Please provide any additional information below.

In the output we can see things like this for incorrect urls.

35 0 obj
<< /Type /Action
/S /URI
/URI (��
endobj

Original issue: http://code.google.com/p/dompdf/issues/detail?id=247

@PhenX
Copy link
Member Author

PhenX commented Dec 6, 2012

From eclecticgeek on March 15, 2011 18:35:20
This appears to be valid. It looks like dompdf is Unicode-encoding the link text, which is what's causing the problem.

@PhenX
Copy link
Member Author

PhenX commented Dec 6, 2012

From fabien.menager on May 14, 2011 23:30:24
This issue was closed by revision r394.

@PhenX PhenX closed this as completed Dec 6, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant