Closed GoogleCodeExporter closed 9 years ago
This may be a problem with the version of PHP, but we would need to run some
tests to
confirm. I have a few variants of linux on which I can test, but I'll have to
see if
I can set up an older release of PHP. Can you supply a sample HTML document
against
which we can test?
Original comment by eclecticgeek
on 3 May 2010 at 8:11
So while I was testing that html code before sending it to you, I found out that
without the "é", it was rendering fine on both my dev comp and the server...
and when
I changed the � for "é" I had the same problem again. It was rendering fine
on my
comp but not on the serv.
I thought utf-8 characters was suported in the beta version :/
I will keep working on that. Let me know if you find anything and how it render
on
your servers/comps. What I don't understand is that on my dev comp it's
rendering fine...
Original comment by JiPi00...@gmail.com
on 4 May 2010 at 12:45
For some reasons, the file that I uploaded was empty
try #2:
Original comment by JiPi00...@gmail.com
on 4 May 2010 at 12:49
Attachments:
So I was doing some test and I found out something intersting.
As you will be able to see on those 2 screenshots(both from the server which I
have
trouble with), it looks like it is working fine with"é" but when it is in
cap("É") it
is not rendering like I want.
Thats kinda wierd.
Original comment by JiPi00...@gmail.com
on 4 May 2010 at 1:50
Attachments:
Hmmm this is definatly a special characters problems, but not with capital
letters.
Look at these 2 new screenshots I made.
Maybe it's a problem with the interpretation of the length of the special
characters
with linux?
Ok i'm gonna stop spamming your mailbox and wait for your answer,
thanks again for the help :)
Original comment by JiPi00...@gmail.com
on 4 May 2010 at 2:21
Attachments:
Have you looked at it and started to work on a solution?
If not could you tell me where I should start looking at to find what is
causing this and how I can fix it because I will have to get this working in
the next few weeks.
Thanks
Original comment by JiPi00...@gmail.com
on 17 Jun 2010 at 3:43
It's hard to work on a solution as we have yet to confirm the problem. I
haven't been able to reproduce your issue using PHP 5.2.1 on a linux system.
Also, I don't have access to CentOS so it's difficult to know if there's a
library on the OS causing a problem.
I think I know what's happening, but I'm not sure why right now. There have
been some adjustments to how DOMPDF works with text since the beta 1 release.
Can you try the latest developer code from the subversion repository to see if
your issue has been fixed?
If you're not familiar with subversion, you can download a copy of the most
recent code base here:
http://eclecticgeek.com/dompdf/
Original comment by eclecticgeek
on 17 Jun 2010 at 9:22
Well there is a good news and a bad news. The original problem is fix which is
the good news! However, it look like all the "v" are replaced by a space (" ")
Any thought on this?
Original comment by JiPi00...@gmail.com
on 18 Jun 2010 at 2:36
Attachments:
I believe this is a compatibility problem with the PCRE library included with
CentOS. I haven't had confirmation, but you should be able to work around the
issue by adjusting the regular expression used with preg_replace(). See
http://code.google.com/p/dompdf/issues/detail?id=144
Original comment by eclecticgeek
on 18 Jun 2010 at 10:06
Alright it's working! thanks a lot for taking time to help me.
Cheers
Original comment by JiPi00...@gmail.com
on 21 Jun 2010 at 2:14
Since this report covers a few bugs I'm marking it invalid. The issues are
reported elsewhere and will be fixed or have already been addressed in trunk.
Original comment by eclecticgeek
on 21 Jun 2010 at 5:48
Original comment by eclecticgeek
on 30 May 2013 at 5:15
Original issue reported on code.google.com by
JiPi00...@gmail.com
on 3 May 2010 at 7:53Attachments: