Re: PHP Language Spec

From: Date: Thu, 24 Jul 2014 20:37:38 +0000
Subject: Re: PHP Language Spec
References: 1  Groups: php.standards 
Request: Send a blank email to standards-+get-105@lists.php.net to get a copy of this message
Sara, Could I suggest ReST (ReStructuredText) as an alternative to Markdown, as it supports cross-references and includes directly? The overall syntax is very similar, but there are some minor differences. Anthony On Thu, Jul 24, 2014 at 4:35 PM, Sara Golemon <pollita@php.net> wrote: > Restarting this thread on the standards list. > > We're working on getting everything converted/formatted/ready for > serious collaboration on github and have three format front-runners: > > 1) Markdown - Works natively on github, simple syntax and fairly > expressive. Downshot: Cross-references are hacky, and it's fairly > important to have these working right. > > 2) LaTeX - Much more descriptive syntax without being horribly > over-verbose and is still collaboration friendly. Downshot: A bit > arcane in the syntax department, needs an explicit render step to > verify changes. > > 3) Docbook - This is what we use for the PHP manual, so it would make > sense to not fragment our toolchain. Downshot: XML is really verbose > and generating renders from docbook is a bit sluggish (the phpdoc > teams knows all these pain points all too well). > > Of course, we can always convert later-on, but it'd be really helpful > to start with something sensible and avoid that transition point if we > can. What are people's thoughts and reactions to these options? Is > there a fourth, better option which you'd like to champion? > > -Sara > > -- > PHP Naming Standardization Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php >

« previous php.standards (#105) next »