[Geany] Geany Newsletter Vol. 2

[Lex Trotman]

> Given that:
>
>  * the various markup formats and their tools can all easily produce
> nice-looking html, pdf, and text output
>  * people have their own preferences regarding doc markup formats
>  * different people at different times may produce a given newsletter
>  * no one ever has to go back and edit old newsletters

Agree

>
> I don't think it makes much sense to debate which format to use.
> Whomever is producing the current newsletter should decide which
> markup format and tools they want to use. [The markup-languages page]
> should simply provide requirements for the output (as it already does)
> and provide guidance on how to produce a newsletter using the various
> tools for those writers who don't have a favorite.
>
> [The markup-languages page]: http://wiki.geany.org/newsletter/markuplanguages

Good idea.

>
> That page might also provide some default newsletter css source for
> those wanting to make their output look like one or another newsletter
> (though, variety is the spice of life :) ).

But I suspect that it might get annoying if every newsletter looked
different, too spicey :-)

The css would have to be per markup and tool since the tools don't use
the same class and id names for the things we want to style (why
should they, there is no standard).

>
> If someone wants to contribute to a given newsletter but is unfamiliar
> with the markup format that the producer is using, they should just
> send in their content in whatever format they know and the producer
> should do the conversion.

Yes, so long as the formats are all lightweight markup languages and
stick to sections, images and very simple tables then the conversions
should be simple, eg asciidoc paragraphs and sections are valid rst
but not markdown and links images and tables are all slightly
different.  Kinda annoying for the newsletter producer, as I said
before wish there were more converters.

Cheers
Lex