raunakbinani / dompdf

Automatically exported from code.google.com/p/dompdf
0 stars 0 forks source link

Special characters problems #94

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1.it does not recognize special chars as € or ´

What is the expected output? What do you see instead?
the same € char as html

What version of the product are you using? On what operating system?
the latest

Please provide any additional information below.

Original issue reported on code.google.com by ajflor...@gmail.com on 23 Nov 2009 at 9:13

GoogleCodeExporter commented 9 years ago
Are you using DOMPDF 0.5.1 or DOMPDF 0.6.0 alpha 2? There have been significant 
improvements in text 
handling with the latter and I believe both of these characters should render 
correctly.

Original comment by eclecticgeek on 23 Nov 2009 at 9:33

GoogleCodeExporter commented 9 years ago
Correct, in 0.6 it shows some of this html tags € and so on.... but still have
problems with chars like º ª

Original comment by ajflor...@gmail.com on 24 Nov 2009 at 11:28

GoogleCodeExporter commented 9 years ago
I'll have to research this a bit more. I believe those characters should be 
supported, so there could be some problems with character set conversion when 
placing the text in the PDF.

In the meantime your best bet for working around the problem would be to use 
Unicode.

Original comment by eclecticgeek on 24 Nov 2009 at 2:46

GoogleCodeExporter commented 9 years ago
Merging with Issue 29 since the problems are similar. As noted in that issue, 
this
problem is partially addressed in the latest development version. Unfortunately,
there are some character set issues which may prevent some characters from 
displaying
correctly unless you use your own font and Unicode encoding.

Original comment by eclecticgeek on 22 Dec 2009 at 7:06

GoogleCodeExporter commented 9 years ago
In 0.6.0 beta 2 it has still problems with Unicode characters as: ● (● - a 
black round centered dot)

Original comment by ukarr...@gmail.com on 5 Apr 2011 at 2:09

GoogleCodeExporter commented 9 years ago
Since that is a Unicode character you will have to enable Unicode in your 
configuration file and use you own font. We're still working on enabling 
expanded character support in the core fonts. You could swap that particular 
character with the standard •

Original comment by eclecticgeek on 21 Apr 2011 at 7:01

GoogleCodeExporter commented 9 years ago

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