OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-apps message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: [docbook-apps] Docbook images/graphics. Where do you keep them?

Actually, I do most of my work on Linux, but it is not shared so
I have administrative privileges on it. 

We have a property in our build files that specifies the path to
the directory containing the graphics.  If it is empty, nothing
is done, if it is populated, that directory is created in the 
result directory and then the contents are copied.  Since it is
an Ant build file and we are using a copy task in ant, we can
actually be very specific, not just creating the directory and
copying all contents, but specifying that only the PNG and GIF
images be copied for HTML delivery (which can be a little tricky
since you have to allow for PNG and png and GIF and gif, due to
some Windows tools producing the upper case suffix -- the Linux
tools seem to be more consistent about the use of lower case).

Graphics that are part of the document are delivered into the
directory specified by the user in the Ant property.  The style 
assets are delivered in a different directory.


-----Original Message-----
From: DavePawson [mailto:davep@dpawson.co.uk] 
Sent: Thursday, May 14, 2009 11:45 AM
To: Rowland, Larry
Cc: docbook-apps
Subject: Re: [docbook-apps] Docbook images/graphics. Where do you keep them?

Rowland, Larry wrote:
> I put a copy of our style assets directory at the root of my hard drive.  
We always use the /styles/... type of path on our production pages that 
are aimed at the Web.
That way if I open the file on my Windows system the styles are 
available, too.

Or Linux. Makes perfect sensee... unless you aren't administrator, but 
then I guess you could use an alias.

That makes it work for testing prior to building.

Larry, does your 'build' take the form of that mentioned by Dean,
to scan source XML for graphics etc and define the collection that way?
Then that is the build target for the site or CD... which does leave
a problem how you recognised  'document specific' graphics?
Another attribute to separate the two?


Dave Pawson

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]