+1 for a)
On 21.10.2005 02:28:42 Manuel Mall wrote:
See the response at
http://lists.w3.org/Archives/Public/xsl-editors/2005OctDec/0006.html.
We have taken the opposite approach and added the property values to the
property defintions.
We could now:
a) just remove them
or
b)
Had to scratch a little itch. :-) I hope nobody minds that. Two
advantages:
- we now only have one place (build.xml) where we set the version.
- we hopefully get better feedback what version people are using when
they report a problem.
On 21.10.2005 12:17:38 jeremias wrote:
Author: jeremias
On Oct 21, 2005, at 08:40, Jeremias Maerki wrote:
On 21.10.2005 02:28:42 Manuel Mall wrote:
We have taken the opposite approach and added the property values
to the
property defintions.
We could now:
a) just remove them
or
b) leave the values in and issue a warning when used
+1 for a)
On Oct 20, 2005, at 5:28 PM, Manuel Mall wrote:
See the response at
http://lists.w3.org/Archives/Public/xsl-editors/2005OctDec/0006.html.
We have taken the opposite approach and added the property values to
the
property defintions.
We could now:
a) just remove them
or
b) leave the values
On Fri, Oct 21, 2005 at 08:28:42AM +0800, Manuel Mall wrote:
See the response at
http://lists.w3.org/Archives/Public/xsl-editors/2005OctDec/0006.html.
We have taken the opposite approach and added the property values to the
property defintions.
We could now:
a) just remove them
Hello,
I'm using FOP and I have the following problem :
I transform a .FO to a PDF but this .FO contains Eastern european
characters (ISO-8859-2/UTF-8 compatible), when looking at the resulting
PDF I have
a '#' for each eastern character. If I try another output different of
PDF, the
JAPISoft wrote:
I transform a .FO to a PDF but this .FO contains Eastern european
characters (ISO-8859-2/UTF-8 compatible), when looking at the resulting
PDF I have
a '#' for each eastern character.
[...]
This is as if the PDF font was ignoring my eastern characters. But I
feel the problem
