Hi,
i am using docbook xsl 1.78.1 that comes bundled with the oxygem xml editor
version 16.0. I think there is a problem (a bug?) in handling relative
filenames defined as entities in the stylesheets for xhtml output.
I have an article with an image. The image is defined as an unparsed entity,
On 22.5.2014 16:05, Frank Steimke wrote:
I have an article with an image. The image is defined as an unparsed entity,
its value is an relative filename. Something like
!ENTITY img SYSTEM image.png NDATA PNG
Used as
imagedata entityref=img/
In my article.
Is there any reason why you are
Hi all,
I am (I think) trying to accomplish the same thing as Frank. I have multiple
docs which use the same copy, but require different figures. I was hoping to
define those figures in entity files so they would be easier to maintain. The
references do not appear to be making it into the
On 22.5.2014 16:42, Fletcher, Brett wrote:
I am (I think) trying to accomplish the same thing as Frank. I have
multiple docs which use the same copy, but require different figures.
I was hoping to define those figures in entity files so they would be
easier to maintain. The references do not
On 15.5.2014 9:06, Bergfrid Skaara wrote:
At this point I get validation errors like group of string or data
element. How do I tweak the docbookxi.rng (in my customization layer rng
file) to allow this construction with semicolons, which is clearly allowed
by the shema without enforcing
On 22.5.2014 17:12, Fletcher, Brett wrote:
First, Thank you for replying! I will gladly take your advice of eliminating
Entities.
Please, next time reply to all, so answer is sent back to the whole
mailing list.
As far as the solution you provided, could you provide an example of how it
You made my day
-Original Message-
From: Jirka Kosek [mailto:ji...@kosek.cz]
Sent: Thursday, May 22, 2014 10:17 AM
To: Fletcher, Brett; docbook-apps@lists.oasis-open.org
Subject: Re: [docbook-apps] Problem with images given as entity in xhtml output
(template process.image)
On
-- try to eliminate usage of entities in your documents. In XML entities will
give you more troubles then advantages
OK, but as far as I understand, the same problem would come up if I would use a
@fileref with an absolute filename like file:/C:/temp/image.png.
Question is, whether this is a
On 22.5.2014 17:22, Frank Steimke wrote:
OK, but as far as I understand, the same problem would come up if I would use
a @fileref with an absolute filename like file:/C:/temp/image.png.
You shouldn't use absolute filenames because that way your documents are
not portable.
Question is,
Thank you Jirka,
actually i am not shure wheter there is a bug, and, if so, i fit is in the
stylesheets or in the xslt engine. But the answer should definitively not
depend on my own definition of correctness, since this may vary from time to
time ...
I will try to get some help from the
Hi Thomas,
This looks like a bug to me. It isn't just the snapshots, it is the
same in 1.78.1/xhtml. It must happen when the xhtml is generated during
the build. Can you please file a bug report so this can get cleared up?
Thanks.
BTW, you said:
The profile-chunk-code.xsl is missing in
Jirka,
Upon further inspection, the path to my images in the HTML output file appears
to have duplicate references to the source path.
Example using entities:
In the *.ent file:
!ENTITY createRole_002 SYSTEM img/createRole_002.png NDATA PNG
In the *.xml file:
parainlinemediaobject
Hi Bob,
Am Donnerstag, 22. Mai 2014, 11:05:17 schrieb Bob Stayton:
This looks like a bug to me. It isn't just the snapshots, it is the
same in 1.78.1/xhtml. It must happen when the xhtml is generated during
the build. Can you please file a bug report so this can get cleared up?
Sure, find
13 matches
Mail list logo
