On 5 July 2012 08:09, ping <[email protected]> wrote:
> experts:
> this is annoying, I tested/researched for 2 hours without a good solution:
>
> how to escape the "<default-chassis>" from being substituted?
>
> [subs="quotes"]
> ----
>    cli> show class-of-service interface ge-0/3/0
>    Physical interface: ge-0/3/0, Index: 138  Queues supported: 4, Queues in
> use: 5
>     Shaping rate: *50000* bps
>     Scheduler map: interface-schedular-map, Index: 58414
>     Input shaping rate: 10000 bps
>     Input scheduler map: schedular-map, Index: 15103
>     Chassis scheduler map: <default-chassis>, Index: 4
>     Congestion-notification: Disabled
> ----
>
> currently it rendered to following , so anything bet < and > got removed.
>
> cli> show class-of-service interface ge-0/3/0
>  Physical interface: ge-0/3/0, Index: 138  Queues supported: 4, Queues in
> use: 5
>   Shaping rate: 50000 bps
>   Scheduler map: interface-schedular-map, Index: 58414
>   Input shaping rate: 10000 bps
>   Input scheduler map: schedular-map, Index: 15103
>   Chassis scheduler map: , Index: 4
>   Congestion-notification: Disabled
>
>
> this is from the FAQ37:
>
> 37. Some elements can’t be escaped with a single backslash
>
> There are a number of exceptions to the usual single backslash rule —
> mostly relating to URL macros that have two syntaxes or quoting ambiguity.
> Here are some non-standard escape examples:
> AsciiDoc        Renders
>
> \[email protected]
> <\[email protected]>
> \mailto:[\[email protected]]
>
>
> [email protected] <[email protected]>
> mailto:[[email protected]]
>
> \http://www.foo1.co.nz
> \\http://www.foobar.com[]
> \\http://www.foobar.com[Foobar Limited]
>
>
> http://www.foo1.co.nz http://www.foobar.com[] http://www.foobar.com[Foobar
> Limited]
>
> A C\++ Library for C++
> \\``double-quotes''
> \*\*F**ile Open\...
>
>
> A C++ Library for C++ ``double-quotes'' **F**ile Open...
>
> The source of this problem is ambiguity across substitution types — the
> first match unescapes allowing the second to substitute. A work-around for
> difficult cases is to side-step the problem using the pass:[] passthrough
> inline macro.
>
> I tried following without good result:
> \<text\>
> \<text>
> <\text>\
> <\text>
>
> the last two get back my "text" but it also displays that
> extra "\"s...
>
> please advice.
>
> --
> You received this message because you are subscribed to the Google Groups
> "asciidoc" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/asciidoc?hl=en.



This is nothing to do with asciidoc, the <> is read by the browser as
HTML markup.  Use the &xx; numeric character codes instead.

Cheers
Lex

-- 
You received this message because you are subscribed to the Google Groups 
"asciidoc" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/asciidoc?hl=en.

Reply via email to