On 11 March 2014 05:38, Kurt Callaway <[email protected]> wrote:
> On Tuesday, February 25, 2014 6:22:51 PM UTC-6, Lex Trotman wrote:
>>
>> [...]
>> > That applies to all macro parameters that contain commas, because
>> > commas normally separate parameters they need to be quoted to include
>> > them in the parameter.
>>
>> > In the tradition of "Just Too Late" I found the reference just after
>> > posting http://www.methods.co.nz/asciidoc/userguide.html#X21
>> > Cheers
>> > Lex
>>
> Thanks much for the confirmation!  Always great to hear the experts say one
> is on the right track.
>
> There's one additional index-related anomoly that I encountered and fixed,
> that I'll mention now too.
>
> I have labeled list entries, and each is immediately followed by an
> indexterm[] macro call that essentially echos the contents of its proceeding
> list entry.  This works well -- except when the list entry's string has hard
> brackets as part of its contents.  Asciidoc (which of course uses hard
> brackets to delimit the indexterm macro) seemed to get confused.
>
> Escaping the close-bracket content character (as recommended in Users Guide
> #21, bullet 4) didn't work for me -- the escaped close-bracket didn't
> display, the index term didn't appear in the index, and any index term
> characters after the contained close-bracket, such as the close quote and
> "real" close-bracket later, ended up appended on the end of the list entry.
> Here's an example:
>
> Asciidoc lines:
> *ERR10* :: *Invalid IP address [<address 1>, <address 2>]*
> indexterm:["ERR10  Invalid IP address [<address 1>, <address 2>\]"]
>
> The Labelled list entry that actually appears in the PDF output:
> ERR10             Invalid IP address [<address 1>, <address 2>] "]
>
> I finally solved this by replacing the escaped close-bracket within the
> indexterm line (not in the list entry line) with the unicode rep &#93;.  No
> backslash needed for that.  Display of the content close-bracket is as
> expected, and the index term shows up properly later in the Index section.

Weird, this is gonna annoy you greatly but, it works for me (tm)

The lines:

*ERR10* :: *Invalid IP address [<address 1>, <address 2>]*
indexterm:["ERR10  Invalid IP address [<address 1>, <address 2>\]"]

generate the docbook:

<term>
<emphasis role="strong">ERR10</emphasis>
</term>
<listitem>
<simpara>
<emphasis role="strong">Invalid IP address [&lt;address 1&gt;,
&lt;address 2&gt;]</emphasis>
<indexterm>
  <primary>ERR10  Invalid IP address [&lt;address 1&gt;, &lt;address
2&gt;]</primary>
</indexterm>
</simpara>
</listitem>

which looks exactly right to me.  And the PDF is right too.

Cheers
Lex

>
> Hoping this helps someone down the road,
> Kurt Callaway
> Houston, Texas
>
> --
> You received this message because you are subscribed to the Google Groups
> "asciidoc" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/asciidoc.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"asciidoc" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/asciidoc.
For more options, visit https://groups.google.com/d/optout.

Reply via email to