Re: [PHP-DOC] Re: Getting more people involved.. bye bye Docbook

On Aug 12, 2013, at 10:47 PM, Christian Weiske wrote: > Hello Hannes, > > >> As an update.. Here is an actually generated page[1] into this new >> markdown/rST style format, and its html rendering[2] using the new >> tool, wtfm[3]. >> >> I still haven't received any suggested pure rST version

Re: [PHP-DOC] Re: Getting more people involved.. bye bye Docbook

Markdown or anything easier than Docbook seems brilliant but What will happen to right to left languages? We couldn't solve the rtl problem in Docbook. Will the problem persist in the new format? On Tue, Aug 13, 2013 at 9:17 AM, Hannes Magnusson < hannes.magnus...@gmail.com> wrote: > As an up

Re: [PHP-DOC] Getting more people involved.. bye bye Docbook

On Mon, Aug 12, 2013 at 11:48 PM, Stas Malyshev wrote: > Hi! > >> This means that the users/writers of doc have to learn the syntax >> anyway. So in my opinion it would be easier to teach them >> rST+Less-Extra-Rules than Mardown+More-Extra-Rules. > > From what I see in rST (and please correct me

Re: [PHP-DOC] Re: Getting more people involved.. bye bye Docbook

Excellent question. Do you know of any rtl examples using formats like markdown or rst? I've never really given it any thought. -Hannes On Tue, Aug 13, 2013 at 12:18 AM, pedram salehpoor wrote: > Markdown or anything easier than Docbook seems brilliant but What will > happen to right to left

Re: [PHP-DOC] Getting more people involved.. bye bye Docbook

On Mon, Aug 12, 2013 at 11:42 PM, Christian Stoller wrote: >>> At work we chose reStructuredText[1], because it gives you way more >>> elements than markdown and is only slighter harder to write. Plain >>> markdown e.g. has no tables, and definition lists, while rST has it out >>> of the box. >> >

Re: [PHP-DOC] Re: Getting more people involved.. bye bye Docbook

I was unable to find any decent rtl extension for Markdown except some javascript stuff but Docutils uses Python code and CSS to give bidirectional support to rst. It seems no rtl language has ever given any thought to use these in large scale or maybe I was unable to find them. On Tue, Aug 13,

Re: [PHP-DOC] Getting more people involved.. bye bye Docbook

On 10/08/13 07:34, Hannes Magnusson wrote: I've been thinking lately about how we can make it easier for people to contribute to the project.. The OE was a great improvement and made it whole lot simpler to get going for users and did its job pretty well. Editing xml however isn't something the

Re: [PHP-DOC] Getting more people involved.. bye bye Docbook

Bjori example's seems easier to figure out what's going to happen. I vote Markdown ratter than Wiki, because you can learn just reading another person's work. Um abraço, :: Rafael Jaques (phpit.com.br ) :: Cristão - Professor - Evangelista PHP :: "Se confessarmos os nosso

Re: [PHP-DOC] Getting more people involved.. bye bye Docbook

Hello Nikola, > Have you people considered simply moving the documentation to a wiki? > For example, MediaWiki? > > * Build time in seconds. > * Wikitext syntax is as simple as any other presented so far. No. Mediawiki's syntax is a pile of stinking something. There is not even a formal syntax

Re: [PHP-DOC] Getting more people involved.. bye bye Docbook

On 13/08/13 19:28, Rafael Jaques wrote: Bjori example's seems easier to figure out what's going to happen. I vote Markdown ratter than Wiki, because you can learn just reading another person's work. I wouldn't know, I don't see how is # DESCRIPTION or DESCRIPTION === any easier to

Re: [PHP-DOC] Getting more people involved.. bye bye Docbook

On 14/08/13 06:04, Christian Weiske wrote: Have you people considered simply moving the documentation to a wiki? For example, MediaWiki? * Build time in seconds. * Wikitext syntax is as simple as any other presented so far. No. Mediawiki's syntax is a pile of stinking something. There is not e