DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=27773.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=27773.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
I also don't think WebStart can help us here. I'd like to add a comment
here. Considerations like this are currently running hot within the ASF.
We need to divide two problems:
1. The ASF is restricted in what it can distribute. There's a policy
forming. I hope all FOP committers are subscribed to
Well, the list may not be complete as the Unicode standard in always in
flux. At any rate, I think the character name list is used to map the
names to unicode character, so you can map unicode characters to a
font's glyph index. So it's primarily a matter for custom multibyte
fonts like TrueType
(comments inline)
On 17.03.2004 04:53:46 Peter B. West wrote:
snip/
As you've seen the Document class is a central class in font handling.
It currently (not in my ideas) provides direct access to font metric
information and to the list of fonts actually used in a rendering run
(we don't
