This is the mail archive of the docbook-apps@lists.oasis-open.org mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [docbook-apps] Alternative to entities?



Thanks everybody! I lean towards using Jirka's suggestion with the role="ent" attribute on phrase since it will work for both PDF and HTML generation.


However, there is a backside with the solution when using XMLMind (again, I don't like violating things just because a tool prevents me from doing it in a correct way, but that's my situation), that since the <phrase> tag is not visible in the running text view it is easy to edit it and remove the tagging. This happened to me when experimenting and it took a while to figure out what had happened.

I got another idea though: what if I created an xref with some role (or xrefstyle) to remove the link functionality (clickable) and other custom visuals (color) since I am only interesting in the target text (endterm), and in the link end I somehow suppress rendering alltogether? The editor handles Xrefs in a quite nice way.

A problem is my very limited experience in writing customization layers, I mostly copy-paste others examples to produce my desired results... But what about the idea to start with?

/Gurra

From: Colin Paul Adams <colin@colina.demon.co.uk>
To: Jirka Kosek <jirka@kosek.cz>
CC: davep@dpawson.co.uk, Gurra Green <gurra_green@hotmail.com>, Docbook-Apps <docbook-apps@lists.oasis-open.org>
Subject: Re: [docbook-apps] Alternative to entities?
Date: 17 Jan 2005 19:20:17 +0000


>>>>> "Jirka" == Jirka Kosek <jirka@kosek.cz> writes:

    Jirka> Dave Pawson wrote:
    >> Not speaking from experience.  If an xinclude aware processor
    >> is used, could that stand in for XML entities Jirka?

Jirka> Yep, you can use something like

Jirka> <xi:include href="entities.xml#productname"/>

Jirka> to pull element from external file entities.xml:

    Jirka> <root> <phrase xml:id="productname">SuperSoft v3.5</phrase>
    Jirka> ...  </root>


What about using one <xi:include href="...." parse="text"/> element for each phrase to
be substituted (with a different URL for each constant text phrase)?
--
Colin Paul Adams
Preston Lancashire

_________________________________________________________________
It's fast, it's easy and it's free. Get MSN Messenger today! http://www.msn.co.uk/messenger



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]