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] Programlistingco issue

Hash: SHA1

On 06/21/2012 04:53 PM, Carlos Araya wrote:
> We had an earlier conversation about using area spec with 
> programlistingco and how it would not work giving coordinates, and 
> arrived to examples like the one below:
> When switching to Jing as my validator I get the following error
> for all the programco examples.
> /Users/carlos/experiment/docbook-epub/docbook-howto.xml:76:17:
> error: element "programlisting" not allowed yet; missing required
> element "areaspec"
> I've worked around this by inserting a dummy areaspec tag and its 
> children. Is there a way for me to eliminate the need to have
> areaspec as part of programlistinco? Is there a reason why I need
> to have the areaspec in an example that doesn't use them? Am I
> missing anything?

Hi Carlos,
I don't know the details of the previous discussion, but we only use
<programlistingco> when we're also xincluding the code sample in (with
parse="text"). That way we can define the line and column number at
which the callout should appear in the code listing.

If we've got a code listing directly in the DocBook file, we instead
add <co> elements like you do in the example above. In that case, the
programlistingco element is not needed.

I believe you have to have the callout extensions set up for the
areaspec method to work.

As usual, Bob's book [1] has lots of valuable information.


[1] http://www.sagehill.net/docbookxsl/AnnotateListing.html
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/


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