/b16022ece329197f72f47943085d45b56e26806e
> Add support for font-selection-strategy=character-by-character
> --
>
> Key: FOP-3139
> URL: https://issues.apache.org/jira/browse/FOP-3139
>
[
https://issues.apache.org/jira/browse/FOP-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner updated FOP-3139:
---
Description:
fop test.fo out.pdf
All glyphs should map to a font
> Add support for font-select
[
https://issues.apache.org/jira/browse/FOP-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner updated FOP-3139:
---
Attachment: test2.fo
> Add support for font-selection-strategy=character-by-charac
Simon Steiner created FOP-3139:
--
Summary: Add support for
font-selection-strategy=character-by-character
Key: FOP-3139
URL: https://issues.apache.org/jira/browse/FOP-3139
Project: FOP
Issue
Dongsheng,
looks like you'll have to wait for proper character selection to be
implemented - this should solve your problems. For now you could try to
add a space between your characters and the rest of the word, or use a
full unicode font such as DejaVu.
Max
Dongsheng Song schrieb:
Did you
Dear Dongsheng Song,
the patch you refer to is outdated and the issue of character handling
has changed since your quoted messages. I have just now updated the Wiki
to reflect the changes. Please email back to the list if anything is
unclear.
Max
Dongsheng Song schrieb:
II have been googled
The wiki[2] same as web[1] for 'Font Selection Strategies'. But 'Word-by-Word'
can't meet my case. For string '#xB2E2;#xCAD4;teststring', if I specify
font-family=Times, SimSun, FOP paint using Times characters, not SimSun,
so I got missing glyphs.
I's there a way treat a single Chinese char(e.g.
Dongshen,
there is: please use fo:character, which should work just as expected.
hth
Max
Am 15.01.2009 15:02, schrieb Dongsheng Song:
The wiki[2] same as web[1] for 'Font Selection Strategies'. But 'Word-by-Word'
can't meet my case. For string '#xB2E2;#xCAD4;teststring', if I specify
Did you mean this example[1] ? It great increase the fo file size,
and I use DocBook, don't know how to use this feather in xsl,
can you give me some advice ?
[1] http://www.zvon.org/HowTo/Output/FOP0.18.1_examples_character.php
Dongsheng Song
2009/1/16 Max Berger m...@berger.name:
there is:
II have been googled the discuss[1,2], and Max Berger's patch[3], and
the wiki[4].
The patch or wiki is too old, not apply to the trunk.
What's the current status, can someone update it ? I
[1] http://marc.info/?t=11829738402r=1w=2
[2] http://marc.info/?t=11780260132r=1w=2
[3]
Dear Fop-Devs,
I've started some work on that in a patch I've submitted a while ago
(which needs cleanup - lots of cleanup)
http://issues.apache.org/bugzilla/show_bug.cgi?id=39422
I've also implemented character-by-character font selection for JEuclid,
which may serve as a reference. Please
On Jun 28, 2007, at 18:32, Andreas L Delmelle wrote:
... calls an implementation of FontInfo.fontLookup() that just
returns the first family in the list...
Of course this should be supplemented: ... that is supported in the
current configuration.
-by-
character font selection strategy in XSLT, even if I could figure out
how to do it. Nor do I believe it is practical to try to create some
custom font that supports all languages and embed that in all my PDFs.
So my question is, what would it take to implement support for the
font
not believe it is practical to try to implement a character-by-
character font selection strategy in XSLT, even if I could figure
out how to do it. Nor do I believe it is practical to try to
create some custom font that supports all languages and embed that
in all my PDFs.
I agree. Implementing
I must say (from a pure FOP-POV), that I'm looking forward to see what
Vincent will come up with with your help. WRT font-selection-strategy I
believe that character-by-character will be a huge step forward for our
two FO processors and should cover 98% of all use cases. If anyone needs
more we
FOP-devs:
WRT font-selection-strategy, I think the new aXSL methods provide the means
to client applications to implement the character-by-character option.
My current reading of the spec is that the auto option is merely an
opportunity, a hook if you will, for an implementation to do something
16 matches
Mail list logo
