David Barrett wrote:

-----Original Message-----
From: Joel

Honestly, I am not quite happy with these "simpler" markups.
I've just moved the Boost.Python tutorial over to quickbook and
had to manually tweak some text which were mistakenly formatted.
As I mentioned in the previous quickbook doc (prior to this),
it's easy to make mistakes with these markups. It is common,
for us C++ people, to use /, *, _ and = when writing documentation.

I'd like to hear your opinions. Shall we keep it or kill it?
It's also possible to have a command line flag for this feature.
Some people might like it. Thoughts?


I maintain an open-source PHP wiki called QwikiWiki
(http://www.qwikiwiki.com), and thus I've grappled with a similar question.
The final syntax I settled on can be found here:

http://quinthar.com/qwikiwiki/index.php?page=QwikiSyntax

I decided to keep the shorthand formatting, as it seems to work 99% of the
time in the real world.  However, getting all my other patterns to work in
concert with shorthand formatting was a bit of a chore.  For examples, check
out:

http://quinthar.com/qwikiwiki/index.php?page=QwikiSyntaxTest

Regardless, I think it was worth the effort for me (and my users), so I'd
vote that you keep it too.

Hi David,

It's not clear what rules you are using for Format Detection.
Could you expound a little bit? As you know, these formatting
rules are very ambiguous and rather context sensitive. I'd have
to write that in Spirit's EBNF. Fortunately, Spirit allows
context sensitivity and ambiguous grammars to some extent
but there still has to be some formality. Let's focus with the
*bold* markup. When does it apply and when does it not? For
example, how do you detect that 3*4*5 will not make the 4 bold?

<< BTW, no underline markup? >>

Regards,
--
Joel de Guzman
http://www.boost-consulting.com
http://spirit.sf.net




------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ Boost-docs mailing list [EMAIL PROTECTED] Unsubscribe and other administrative requests: https://lists.sourceforge.net/lists/listinfo/boost-docs

Reply via email to