[PATCH inputproto] Add minimal asciidoc syntax

Gaetan Nadon memsize at videotron.ca
Fri Mar 18 08:45:17 PDT 2011

On Fri, 2011-03-18 at 10:07 +1000, Peter Hutterer wrote:

> I don't disagree and I certainly haven't use asciidoc in anything more
> complex than a man page. just one comment that I found from a quick
> search,
> suggesting that olink _may_ be possible in asciidoc.
> http://groups.google.com/group/asciidoc/browse_thread/thread/4ff80242da4a3634
> btw, git uses asciidoc and has some extensive asciidoc.conf. might be
> worthwhile to get some tips and tricks from there.

Thanks for the pointer.

We may be victim of the pendulum syndrome. The "too many formats"
with "one size fits all". 

It would be better for the project if there were some consistency in the
chosen format.
It should not be "random" or based on what the developer happens to be
familiar with.

Some heuristics based on content type, size, etc... 

Perhaps doxygen should also be considered in some cases. 
I have not given any thoughts yet, but protocols are heavy on public api
so they seem to be good candidates. Having the code and the docs in the
could go a long way in terms keeping them in sync.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.x.org/archives/xorg-devel/attachments/20110318/13804f67/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL: <http://lists.x.org/archives/xorg-devel/attachments/20110318/13804f67/attachment.pgp>

More information about the xorg-devel mailing list