Re: [docbook] xi:include problem

["Dew, Simon" <Simon.Dew@sbdinc.com>]

Hi

On 12/12/13 19:12, maxwell wrote:

> On 2013-12-12 14:04, Alex Kleider wrote:
>> The problem (already aluded to in the thread from which I've spun off
>> this one) with
>> a) using xmllint to expand xIncludes
>> and then
>> b) validating with jing,
>> is that the validation must be done on the output of xmllint and when
>> jing reports an error it provides a location in the output file, but
>> we want to fix the problem in the original file.
>
> A kludge might be to put an XML comment at the top and bottom of each
> file identifying the file's name, e.g.
>      <!--XML source file = foobar.xml -->
> and then searching up or down in the output file from the error site
> (and maybe doing some arithmetic on the line numbers to come up with the
> line # in the original file--that assumes newlines are preserved in the
> process, which I think they can be).

That would work. I just search upwards in the output file for the 
nearest xml:base attribute. That shows the name and location of the 
original file.

Simon Dew

Technical Author | Stanley Security Solutions
1 Park Gate Close, Bredbury, Stockport SK6 2SZ, U.K.

Simon.Dew@SBDInc.com | +44 (0) 161 406 3400
www.stanleysecuritysolutions.co.uk

Registered Office: Stanley House, Bramble Road, Swindon
Registered in England and Wales No. 181585 VAT No. 232 2446 95