It concludes what was said. And Pascal's remark is about the issue that
was solved. But you try it with FOP Trunk and decide whether it is
sufficiently solved. If not, provide a reproducible example
(reproducible with the latest build) .
My talk about character-by-character is a known issue and is unrelated
to your bug report and is sufficiently covered on other places.
Benson Margulies wrote:
Does this add up to a reason to reopen the bz?
On Mon, Jan 4, 2010 at 11:19 AM, Pascal Sancho <pascal.san...@takoma.fr> wrote:
Abel Braaksma a écrit :
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.
No, FOP replaces missing characters "#" character. I suspect a wrong
character selection
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
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
