David Abrahams wrote:
> I would like an escaped space to be treated punctuation for the purposes of
> parsing, and removed from the output.
Done. But not for the reason you need below.
> /foo/\ *bar*
>
> would be translated into
>
> <emphasis>foo</emphasis><emphasis role="bold">bar</emphasis>
>
>
> Without this feature it's hard to create adjacent inline markup.
You can do adjacent simple-markups (see last example in Simple
formatting section of docs I committed). Example:
*side-by*/-side/
does the right thing.
David Abrahams wrote:
> /foo \/ bar/
>
> is parsed as
>
> <emphasis>foo \</emphasis> bar/
>
> rather than being identical to
>
> /foo / bar/
>
> i.e.,
>
> <emphasis>foo / bar</emphasis>
>
> Is that as intended?
Yes. Simple markups cannot contain any other form of quickbook markup.
David Abrahams wrote:
> http://tinyurl.com/yxbt6p#quickbook.syntax.phrase.simple_formatting
> (tools/quickbook/doc/html/quickbook/syntax/phrase.html)
>
> has a list of rules for simple formatting. I think it's missing a
> rule that says space or punctuation must precede the opening
> delimiter.
No. Allowing that permits adjacent inline markup as shown above.
Regards,
--
Joel de Guzman
http://www.boost-consulting.com
http://spirit.sf.net
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Boost-docs mailing list
[email protected]
Unsubscribe and other administrative requests:
https://lists.sourceforge.net/lists/listinfo/boost-docs
