I had the feeling that nearly every suggestion wasn't searching for a
compromise we as contributors to the newsletter can work with but
pointing the mentioned solution as the only one - which is a valid way,
but well you know.
Ah well, nobody is going to bother to put forward something
Am 27.05.2011 04:01, schrieb 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
Please fill in the wikipage by using the feature list I provided.
There will be a poll in maybe 1 week and we will do the decission. No
big further discussion here please.
Well thats one way of doing it, maybe...
To be honest I'm really sick of this discussion, as changing to ReST
wasn't
Am 25.05.2011 19:07, schrieb Colomban Wendling:
Le 25/05/2011 18:27, Frank Lanitz a écrit :
Sound good ;)
I will give it a try tomorrow.
BUT: PDF already looks very well. Huge Thanks!
No problem :)
The point I think that should be improved is image sizing/placement, but
I can't tell how
Le 26/05/2011 10:46, Frank Lanitz a écrit :
Am 25.05.2011 19:07, schrieb Colomban Wendling:
Le 25/05/2011 18:27, Frank Lanitz a écrit :
Sound good ;)
I will give it a try tomorrow.
BUT: PDF already looks very well. Huge Thanks!
No problem :)
The point I think that should be improved is
Le 26/05/2011 04:10, Lex Trotman a écrit :
Hi All,
I made a version of the newsletter using asciidoc and generated HTML,
PDF and text.
Don't look too different from ReST, good.
See:
https://github.com/elextr/geany_stuff/commit/d094fb77d37bd00c4172041ea95be08ba294460c
The HTML has the
On Wed, May 25, 2011 at 10:10 PM, Lex Trotman ele...@gmail.com wrote:
Hi All,
I made a version of the newsletter using asciidoc and generated HTML,
PDF and text.
See: {snip}
Given that:
* the various markup formats and their tools can all easily produce
nice-looking html, pdf, and text
On 27 May 2011 03:04, Colomban Wendling lists@herbesfolles.org wrote:
Le 26/05/2011 04:10, Lex Trotman a écrit :
Hi All,
I made a version of the newsletter using asciidoc and generated HTML,
PDF and text.
Don't look too different from ReST, good.
That was the point :-) (for HTML
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
Am 24.05.2011 23:33, schrieb Frank Lanitz:
On Tue, 24 May 2011 17:07:52 +0200
Colomban Wendling lists@herbesfolles.org wrote:
Le 24/05/2011 16:14, Frank Lanitz a écrit :
Not sure what I'm doing wrong, but not working:
frlan@ubuntu:~/git/newsletter$ LANG=C vol=2 make pdf
maxpasses=5; \
Le 25/05/2011 15:45, Frank Lanitz a écrit :
Am 24.05.2011 23:33, schrieb Frank Lanitz:
On Tue, 24 May 2011 17:07:52 +0200
Colomban Wendling lists@herbesfolles.org wrote:
Le 24/05/2011 16:14, Frank Lanitz a écrit :
Not sure what I'm doing wrong, but not working:
On Wed, 25 May 2011 18:11:16 +0200
Colomban Wendling lists@herbesfolles.org wrote:
Le 25/05/2011 15:45, Frank Lanitz a écrit :
Am 24.05.2011 23:33, schrieb Frank Lanitz:
On Tue, 24 May 2011 17:07:52 +0200
Colomban Wendling lists@herbesfolles.org wrote:
Le 24/05/2011 16:14,
Le 25/05/2011 18:27, Frank Lanitz a écrit :
Sound good ;)
I will give it a try tomorrow.
BUT: PDF already looks very well. Huge Thanks!
No problem :)
The point I think that should be improved is image sizing/placement, but
I can't tell how to fix this without adding one more sed replacement,
Hi All,
I made a version of the newsletter using asciidoc and generated HTML,
PDF and text.
See:
https://github.com/elextr/geany_stuff/commit/d094fb77d37bd00c4172041ea95be08ba294460c
The HTML has the images embedded just to make it a single file, they
link by default.
Commands used:
For
Am 24.05.2011 03:21, schrieb Lex Trotman:
Actually now I do, same as your problem, you need to run pdflatex
several times for it to work, but nothing says how many times. And
thats only one of the reasons I don't like latex.
In most cases running 2 times is enough. But there are also build
Hey,
Le 23/05/2011 11:05, Frank Lanitz a écrit :
Am 23.05.2011 10:50, schrieb Lex Trotman:
I thought PDF was generated via latex and I wasn't about to try to
tell *you* how to get Latex to do the numbering :-)
With change to ReST this has been changed as the TeX export is causing
Le 24/05/2011 03:28, Russell Dickenson a écrit :
Is anyone open to idea of switching to AsciiDoc markup and set of
tools? It can definitely output plain text, HTML and PDF, with and
without Table Of Contents.
I don't really mind, but:
1) is AsciiDoc really more flexible or does it only have
Am 24.05.2011 15:58, schrieb Colomban Wendling:
Hey,
Le 23/05/2011 11:05, Frank Lanitz a écrit :
Am 23.05.2011 10:50, schrieb Lex Trotman:
I thought PDF was generated via latex and I wasn't about to try to
tell *you* how to get Latex to do the numbering :-)
With change to ReST this has
Le 24/05/2011 16:14, Frank Lanitz a écrit :
Not sure what I'm doing wrong, but not working:
frlan@ubuntu:~/git/newsletter$ LANG=C vol=2 make pdf
maxpasses=5; \
file=`basename vol_2/newsletter_2.tex .tex`; \
cd `dirname vol_2/newsletter_2.tex` \
pdflatex -interaction
On Tue, 24 May 2011 17:07:52 +0200
Colomban Wendling lists@herbesfolles.org wrote:
Le 24/05/2011 16:14, Frank Lanitz a écrit :
Not sure what I'm doing wrong, but not working:
frlan@ubuntu:~/git/newsletter$ LANG=C vol=2 make pdf
maxpasses=5; \
file=`basename
Am 23.05.2011 04:13, schrieb John Gabriele:
On Sun, May 22, 2011 at 1:25 PM, Frank Lanitz fr...@frank.uvena.de wrote:
Geany Newsletter #2
---
Contents
{snip}
Great newsletter!
Would be helpful if there were a link at the top of the newsletter
email pointing
Me too. Unfortunately I wasn't able to create this by using RST but
failed. Input is welcome.
Replace the h1 and h2 CSS definitions with the following:
body { counter-reset: counter1; counter-reset: counter2; }
h1:before { content: counter(counter1) ; }
h1.title:before { content: ; }
h1 {
Am 23.05.2011 10:08, schrieb Lex Trotman:
Me too. Unfortunately I wasn't able to create this by using RST but
failed. Input is welcome.
Replace the h1 and h2 CSS definitions with the following:
body { counter-reset: counter1; counter-reset: counter2; }
h1:before { content:
On 23 May 2011 18:33, Frank Lanitz fr...@frank.uvena.de wrote:
Am 23.05.2011 10:08, schrieb Lex Trotman:
Me too. Unfortunately I wasn't able to create this by using RST but
failed. Input is welcome.
Replace the h1 and h2 CSS definitions with the following:
body { counter-reset: counter1;
Am 23.05.2011 10:50, schrieb Lex Trotman:
I thought PDF was generated via latex and I wasn't about to try to
tell *you* how to get Latex to do the numbering :-)
With change to ReST this has been changed as the TeX export is causing
nightmares to me in current state.
Cheers,
Frank
Am 23.05.2011 10:50, schrieb Lex Trotman:
And like a great man once said: all interesting programs have at
least one counter, at least one loop and at least one bug, so the
first line should read
body { counter-reset: counter1 -1 counter2; }
otherwise the heading counts as 1.
Hehe.
Hi John,
Yeah pandoc is a useful tool, but everytime I have used it in the past
it does nearly everything not quite perfectly :-)
Here it is as html
http://www.unexpected-vortices.com/temp/geany/newsletter_2.html ,
produced using [Pandoc] via the following command: `pandoc -s --toc -N
On Mon, May 23, 2011 at 7:43 PM, Lex Trotman ele...@gmail.com wrote:
Hi John,
Yeah pandoc is a useful tool, but everytime I have used it in the past
it does nearly everything not quite perfectly :-)
I like it because the markup is pretty (and easy and fast to type),
and it's easy to process
I like it because the markup is pretty (and easy and fast to type),
and it's easy to process into multiple formats.
I presume you mean markdown markup, pun intended I'm sure. Its just
another lightweight markup language, not much between any of them, my
personal favorite is Asciidoc but more
Is anyone open to idea of switching to AsciiDoc markup and set of
tools? It can definitely output plain text, HTML and PDF, with and
without Table Of Contents.
If there are no loud objections I'll put together samples of the
newsletter's source file in AsciiDoc markup converted into plain
On Mon, May 23, 2011 at 9:34 PM, Lex Trotman ele...@gmail.com wrote:
Is anyone open to idea of switching to AsciiDoc markup and set of
tools? It can definitely output plain text, HTML and PDF, with and
without Table Of Contents.
If there are no loud objections I'll put together samples of
Hi John,
Let me declare at the outset that I have contributed a few minor
patches to Asciidoc and respond to some mailing list queries and I am
using it within a Python project, so I am not an unbiased observer.
:-)
Sphinx utilizes reST and the docutils tools under the covers. BTW, all
the
Geany Newsletter #2
---
Contents
About Geany
Geany Development
Update to Scintilla 2.25
Real-time tag parsing
Automatic indentation width detection
Fixes to template encoding
Plugins
New plugins
geanycfp
On Sun, May 22, 2011 at 1:25 PM, Frank Lanitz fr...@frank.uvena.de wrote:
Geany Newsletter #2
---
Contents
{snip}
Great newsletter!
Would be helpful if there were a link at the top of the newsletter
email pointing to the online html version:
34 matches
Mail list logo
