When I render a document using XSL 1.58.1, the page numbers listed after the
index term are in descending instead of ascending order (i.e 120, 98, 13
instead of 13, 98, 120). Is this a known bug ? Is there a simple fix I can
make to have it sorted properly.
I tried to dig into the code but could
Daniel Veillard writes:
On Tue, Dec 17, 2002 at 10:58:04AM -0500, Jeff Beal wrote:
I'm getting the following error when parsing my documentation with xmllint:
[...]
When I edit my local copy of the DocBook DTD and remove the following line
from the iso-num.ent file, everything works:
You have to be sure that a Central European font is installed in FOP's
configuration file (see FOP documentation for details) and that the Central
European font is specified in the FO. By default, the DocBook stylesheets
use the Helvetica font, which must not have the character #x142;
* ABX; [EMAIL PROTECTED] on 19 Dec, 2002 wrote:
Is there anything I can do to get language specific character to be displayed
correctly in PDF output using Adobe Reader on Windowses ?
I use lstrok; entity as second letter in my original name 'Wlodzimierz'. It
is rendered (xsltproc + 1.58) in
ABX wrote:
supported). I have no problems with characters like 'Jeacute;rocirc;me' for
example. I'm sure fonts on my computer has that letter installed and I'm sure
I have no separated Helvetica installed. Any ideas?
Character you requested is not in ISO Latin 1 which is covered by
standard
Togan Muftuoglu wrote:
It is Adobe limitation you have to embed the font that has the glyph for
the character. If you try XEP the result will be the same. Only with
PassiveTeX it works out of the box weird but true
It is not limitation of Adobe nor PDF format. This is completely tool
issue.
Togan Muftuoglu wrote:
Because even though you can use diffrent fonts in the document they are
not possible in the bookmarks since they only use the Adobe defined
fonts which have the limited PDF encoding
Bookmarks are different issue. They are not displayed with embeded font,
they always use
specify Unicode encoding vector for bookmarks, but AFAIK Acrobat Reader
support this from version 5.0, earlier versions contained some bugs in
this. For that reason almost all PDF creation tools supported only ISO
Latin 1 characters in bookmars as this was pretty safe.
RenderX XEP generates
David Tolpin wrote:
RenderX XEP generates Unicode annotations (bookmarks) by default and has a
backend option to switch it off (that is basically to use ISO Latin 1 encoding
for annotations).
Nice to know. Is this feature available only in version 3.x, or also in
2.77 (we had licence only for
* David Tolpin; [EMAIL PROTECTED] on 20 Dec, 2002 wrote:
specify Unicode encoding vector for bookmarks, but AFAIK Acrobat Reader
support this from version 5.0, earlier versions contained some bugs in
this. For that reason almost all PDF creation tools supported only ISO
Latin 1 characters in
RenderX XEP generates Unicode annotations (bookmarks) by default and has a
backend option to switch it off (that is basically to use ISO Latin 1 encoding
for annotations).
Strange I am using 2.77 (academic Licence) and could not get Turkish
characters in the bookmarks.
May I please
Turkish language specific characters as long as a font file is used that
is covering the glyphs. Fonst coming with XEP do not include these
glyphs. The bookmarks are not displaying the Turkish characters and
actually they change the text ( this could be the feature of Docbook
StyleSheets )
* David Tolpin; [EMAIL PROTECTED] on 20 Dec, 2002 wrote:
Turkish language specific characters as long as a font file is used that
is covering the glyphs. Fonst coming with XEP do not include these
glyphs. The bookmarks are not displaying the Turkish characters and
actually they change the text (
13 matches
Mail list logo
