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 me
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 :
> there is: please use fo:cha
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 '닢쫔teststring', if I specify
font-family="Times,
The wiki[2] same as web[1] for 'Font Selection Strategies'. But 'Word-by-Word'
can't meet my case. For string '닢쫔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. '닢') as a
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 th
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=11829738402&r=1&w=2
[2] http://marc.info/?t=11780260132&r=1&w=2
[3] https:/
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."
On Jun 27, 2007, at 23:31, Jeremias Maerki wrote:
I've noted some things here:
http://wiki.apache.org/xmlgraphics-fop/FontSelectionStrategy
It's best to use that page to gather thoughts and come up with a
plan to
implement that feature.
Sorry, completely missed that Wiki update.
One thing
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 look
all.
> >
> > I do 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 a
I do 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. Im
mplement 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.
So my question is, what would it take to implement support for
12 matches
Mail list logo
