Paul,

This is one way that I handle it (taken from Stayton's book)

I use ENTITY statements. Our product is currently named EDGE. However,
in a few months it will be renamed. So what I do is have an include file
with ENTITY statements in it. The entry for the NAME of EDGE would be:
    <!ENTITY  EDGE  "EDGE" >

This is in a file (eec-edge-defs.mod) that is included in every source
file:

<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
"http://www.docbook.org/xml/4.4/docbookx.dtd";[
      <!ENTITY % edge-defs SYSTEM "eec-edge-defs.mod">
      %edge-defs;
      ]>

Then every place where the word "EDGE" is referenced, I replace it with
"&EDGE;". So in your case, you will only have to do the search and
replace operation once. 

Now when the name is changed in a few months I just change one file and
everything changes. Its kind of like a "#define" in the C/C++ language.


Hope this helps.

Dean Nelson   
Enterprise Electronics Corp




-----Original Message-----
From: Paul Moloney [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, May 02, 2007 10:43 AM
To: docbook-apps
Subject: [docbook-apps] Replacing Terms


I understand the concept in DocBook of profiling, or conditional text.
In a 
particular situation, I have a case where we need to produce custom 
documentation from a core version, the custom documentation only
differing 
by the fact that certain terms are called something else (essentially,
just 
a global find and replace).

Rather than using the phrase element as recommended in the section on 
"Marking small bits of text", as described in 
http://www.sagehill.net/docbookxsl/MarkTextBits.html, I was wondering if

anyone else had ever instead done some kind of processing step before 
running Saxon?

Regards,

-pm

http://oceanclub.blogspot.com

"I can win an argument on any topic, against any opponent. People know
this, and steer clear of me at parties. Often, as a sign of their great
respect, they don't even invite me."
 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to