Le lundi 07 septembre 2009, Lukas Theussl a écrit :
> > - it works nicely with 2.1.2+
>
> So in other words, r811631 is not needed anymore, just use pir 2.1.2 and
> everything is fine, or is there some downside?
I don't know any downside
Regards,
Hervé
---
Hervé BOUTEMY wrote:
Le lundi 07 septembre 2009, Lukas Theussl a écrit :
Hi Guys,
Just some remarks:
\u0092 is not a valid xhtml character entity reference [1] (ie it is not
defined by the xhtml 1.0 DTD),
not really.
\u0092 has no named character entity, but it can be represented as a numer
Le lundi 07 septembre 2009, Lukas Theussl a écrit :
> Hi Guys,
>
> Just some remarks:
>
> \u0092 is not a valid xhtml character entity reference [1] (ie it is not
> defined by the xhtml 1.0 DTD),
not really.
\u0092 has no named character entity, but it can be represented as a numeric
character ref
Hi Guys,
Just some remarks:
\u0092 is not a valid xhtml character entity reference [1] (ie it is not defined
by the xhtml 1.0 DTD), so IMO MPIR should not use it in the first place. I think
that \u0027 (apos) should be used instead but MPIR-136 states that this leads to
test failures? I'd gu
Hi Hervé,
2009/9/5 Hervé BOUTEMY :
> I'm not convinced this is a good idea: MPIR is fixed now, but this hack will
> prevent anybody to output \u0092 when it is the real character they want.
Using \u0092 char will be displayed as # in the pdf so I don't think
user want to use this char.
MPIR 2.1.
I'm not convinced this is a good idea: MPIR is fixed now, but this hack will
prevent anybody to output \u0092 when it is the real character they want.
Regards,
Hervé
Le samedi 05 septembre 2009, vsive...@apache.org a écrit :
> Author: vsiveton
> Date: Sat Sep 5 12:46:15 2009
> New Revision: 81
