David Abrahams wrote:
> If the matching markup cannot be found within a line, the formatting
> will not be applied. This is to ensure that un-matched formatting
> markups, which can be a common mistake, does not corrupt anything
> past a single line. We do not want the rest of the document to be
> rendered bold just because we forgot a trailing '*'.
>
> I think that rule is needlessly strict. Simple markup could (should)
> end by the end of a block (so only one-paragraph documents would have
> the above problem), and anyway quickbook ought to issue a syntax error
> if you fail to close your simple markup. Also a good syntax
> highligher will show you when you don't have the closing delimiter in
> place.
I'm not sure. It will make it more complicated to support text like
the one in the More Formatting Samples (example 7):
3*4*5 = 60 (no bold)
inside blocks like lists and tables. The tendency is to gobble up
everything. I'm wary of giving the simple-markups more power than
they already have. It's too adhoc(**). After all, you also have the
more behaved and nestable style markups.
(**) I wasn't even sure that Spirit, being more or less a formal
EBNF parser, can handle the context sensitivity and ambiguity.
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
