Ok.
Thanks,
Vincent
Jeremias Maerki wrote:
> Hi Vincent,
>
> in the long term, I agree with you. But as long as so many other parts
> of FOP (like Font.mapChar()) use "char", there's no point to use "int"
> in the backend. There will never be any characters outside the basic
> plane until the w
Hi Vincent,
in the long term, I agree with you. But as long as so many other parts
of FOP (like Font.mapChar()) use "char", there's no point to use "int"
in the backend. There will never be any characters outside the basic
plane until the whole process from input through layout engine to
rendering
Sorry, I wasn't paying enough attention.
Yes, when dealing with individual character interfaces, you need to provide
codepoint as well as char. The relationship between codepoints and strings is
not straightforward, however.
Peter West
"Lord, to whom shall we go?"
On 22/05/2010, at 12:14 AM
Hi,
> Author: jeremias
> Date: Thu May 20 09:52:27 2010
> New Revision: 946585
>
> URL: http://svn.apache.org/viewvc?rev=946585&view=rev
> Log:
> Changed many variables and parameters from "int" to "char" because AFP font
> support mostly uses Unicode code points unlike Type 1 and TrueType suppo
