To recap: apparently the problem was that for individual letters not
available in a font, the wrong selection was made, resulting in the
question mark (for missing letter) appearing.
While this was apparently fixed, note that character-by-character is
still not supported. Meaning, in "AXB", where X is a Japanese (or other)
character not available in font Candara (or other), but available in MS
PMincho, it will still display as a question mark. Change it to "A X B"
and it should work.
If your only issue is with Japanese text, this can easily be solved in
the XSLT step (using codepoints ranges), in case you have this type of
exceptional cases in your text.
Good to know that the issue is solved, Pascal.
-- Abel --
Pascal Sancho wrote:
Hi Benson,
What you need is implemented in FOP TRUNK.
See [1] for further details.
I'll close the bug since I cannot reproduce it in FOP TRUNK, but you
feel free to reopen.
[1]
http://xmlgraphics.apache.org/fop/trunk/fonts.html#truetype-collections-metrics
Pascal
Benson Margulies a écrit :
Please see bz https://issues.apache.org/bugzilla/show_bug.cgi?id=48481.
On Mon, Jan 4, 2010 at 7:46 AM, Abel Braaksma <[email protected]>
wrote:
Can you clarify? Because that's precisely what I wrote. Perhaps we
have some
misunderstanding on what the font-selection-strategy means and/or what
"picked" means (who picks what by what criteria?).
Can you provide a simple input (XML) output (XSL-FO) example that
currently
renders incorrectly, but which is a little bit more elaborate then the
"A=E3=81=82" string example? I.e., how would you deal with the
selection of
the font and what do you expect FOP to do for you?
Benson Margulies wrote:
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
