Hi folks,
I was thinking about an idea I'm not sure whether somebody would be interesting in.
As the Geany family is growing it might become more difficult to keep track on current developments inside the project as well as the close environment like new or updated plugins, important updates on GTK or some other used library in case you don't read every mail on the mailing list or hanging around all time inside IRC.
As I know from a couple of other projects some kind of a project newsletter has been set up by a couple of people to help to keep on track with latest updates. So I'd like to suggest setting up something like this also for Geany and its plugins etc..
In difference to the newsletters around Debian or PostgresSQL I was thinking about a monthly one maintained by a small team of maybe three people monitoring the mailing list, IRC as well as they are open for input of users and (plugin) developers. Based on this they could compile a newsletter and send it out to either geany-user mailing list or maybe some newly created one.
I could imagine of topics inside the 'newsletter' (unsorted list): * Geany Core * Reviews inside press, blogs, wikis etc. * Major updates/bugfixes/improvements on svn trunk * New releases and updates * HowTos for working with Geany * Plugins * New plugins available * Major updates/improvements/bugfixes on plugins * General * Important updates of used libraries * News out of community (of importance for Geany)
So question are: Who would like to see such a thing? Who would be able to help compiling such a newsletter? Any other ideas or suggestions?
Cheers, Frank
On 01/02/2011 03:11 PM, Frank Lanitz wrote:
Hi folks,
I was thinking about an idea I'm not sure whether somebody would be interesting in.
As the Geany family is growing it might become more difficult to keep track on current developments inside the project as well as the close environment like new or updated plugins, important updates on GTK or some other used library in case you don't read every mail on the mailing list or hanging around all time inside IRC.
As I know from a couple of other projects some kind of a project newsletter has been set up by a couple of people to help to keep on track with latest updates. So I'd like to suggest setting up something like this also for Geany and its plugins etc..
In difference to the newsletters around Debian or PostgresSQL I was thinking about a monthly one maintained by a small team of maybe three people monitoring the mailing list, IRC as well as they are open for input of users and (plugin) developers. Based on this they could compile a newsletter and send it out to either geany-user mailing list or maybe some newly created one.
I could imagine of topics inside the 'newsletter' (unsorted list):
- Geany Core
- Reviews inside press, blogs, wikis etc.
- Major updates/bugfixes/improvements on svn trunk
- New releases and updates
- HowTos for working with Geany
- Plugins
- New plugins available
- Major updates/improvements/bugfixes on plugins
- General
- Important updates of used libraries
- News out of community (of importance for Geany)
So question are: Who would like to see such a thing? Who would be able to help compiling such a newsletter? Any other ideas or suggestions?
Cheers, Frank
Geany mailing list Geany@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany
Sounds interesting. As for me, I would definitely enjoy reading such a newsletter.
Regards, Laurent
Hi Frank!
Le 02/01/2011 15:11, Frank Lanitz a écrit :
Hi folks,
I was thinking about an idea I'm not sure whether somebody would be interesting in.
As the Geany family is growing it might become more difficult to keep track on current developments inside the project as well as the close environment like new or updated plugins, important updates on GTK or some other used library in case you don't read every mail on the mailing list or hanging around all time inside IRC.
As I know from a couple of other projects some kind of a project newsletter has been set up by a couple of people to help to keep on track with latest updates. So I'd like to suggest setting up something like this also for Geany and its plugins etc..
In difference to the newsletters around Debian or PostgresSQL I was thinking about a monthly one maintained by a small team of maybe three people monitoring the mailing list, IRC as well as they are open for input of users and (plugin) developers. Based on this they could compile a newsletter and send it out to either geany-user mailing list or maybe some newly created one.
I could imagine of topics inside the 'newsletter' (unsorted list):
- Geany Core
- Reviews inside press, blogs, wikis etc.
- Major updates/bugfixes/improvements on svn trunk
- New releases and updates
- HowTos for working with Geany
- Plugins
- New plugins available
- Major updates/improvements/bugfixes on plugins
- General
- Important updates of used libraries
- News out of community (of importance for Geany)
So question are: Who would like to see such a thing? Who would be able to help compiling such a newsletter? Any other ideas or suggestions?
Cheers, Frank
I think such a newsletter is a good idea, and would help many people (even those who actually follow the ML) to have an overview of the recent changes, life of Geany. For example, I follow the ML, but don't read each and every thread, so I probably misses some interesting/important stuff I would be interested about.
Something I would add would be "future plans" when something big is planned. This may even encourage some interested people to contribute :)
This said, I don't propose myself for the job, sorry... but great idea IMHO!
Regards, Colomban
On Sun, 02 Jan 2011 20:49:27 +0100, Colomban wrote:
Hey,
I think such a newsletter is a good idea, and would help many people
Same here, I'm all for it!
Regards, Enrico
On Sun, 02 Jan 2011 20:49:27 +0100 Colomban Wendling lists.ban@herbesfolles.org wrote:
I think such a newsletter is a good idea, and would help many people (even those who actually follow the ML) to have an overview of the recent changes, life of Geany. For example, I follow the ML, but don't read each and every thread, so I probably misses some interesting/important stuff I would be interested about.
Yes, same here. Already nearly impossible at some week to read every mail when its getting a bit more busy at work.
Something I would add would be "future plans" when something big is planned. This may even encourage some interested people to contribute :)
Good ideas.
This said, I don't propose myself for the job, sorry... but great idea IMHO!
OK. So we only need somebody who will do it :D
Cheers, Frank
On 3 January 2011 10:24, Frank Lanitz frank@frank.uvena.de wrote:
On Sun, 02 Jan 2011 20:49:27 +0100 Colomban Wendling lists.ban@herbesfolles.org wrote:
I think such a newsletter is a good idea, and would help many people (even those who actually follow the ML) to have an overview of the recent changes, life of Geany. For example, I follow the ML, but don't read each and every thread, so I probably misses some interesting/important stuff I would be interested about.
Yes, same here. Already nearly impossible at some week to read every mail when its getting a bit more busy at work.
+1
Something I would add would be "future plans" when something big is planned. This may even encourage some interested people to contribute :)
Good ideas.
This said, I don't propose myself for the job, sorry... but great idea IMHO!
OK. So we only need somebody who will do it :D
-1, I have not had time enough to do any more on the build system I'm afraid and don't watch all ML and in wrong time zone for IRC.
Cheers lex
Cheers, Frank -- http://frank.uvena.de/en/
Geany mailing list Geany@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany
On Sun, 2011-01-02 at 15:11 +0100, Frank Lanitz wrote:
thinking about a monthly one maintained by a small team of maybe three
Who would like to see such a thing?
Yes, I would like to see and read such a thing, but bi-monthly (ie every two months) is good enough for me. egbert
On Sun, 2 Jan 2011 15:11:39 +0100 Frank Lanitz frank@frank.uvena.de wrote:
[...]
So question are: Who would like to see such a thing? Who would be able to help compiling such a newsletter? Any other ideas or suggestions?
After a a bunch of feedback I'd say that most of the people would like to have opportunity of an newsletter with extract for a period. Unfortunately no further author by now.... :)
However, to get this thing started there need to be some kind of collaborating tool to create the text. I know from some groups which are using a wiki or Etherpad for doing this. As Geany is an IDE and I feel a bit more comfortable with a VCS I'd suggest to make usage of a git/svn/hg/* here to collect and edit the texts for the newsletter before sending them out. Maybe we could use git.uvena.de also for hosting of these. What do you think?
Cheers, Frank
Am Mittwoch, den 05.01.2011, 23:52 +0100 schrieb Frank Lanitz:
On Sun, 2 Jan 2011 15:11:39 +0100 Frank Lanitz frank@frank.uvena.de wrote:
[...]
So question are: Who would like to see such a thing? Who would be able to help compiling such a newsletter? Any other ideas or suggestions?
After a a bunch of feedback I'd say that most of the people would like to have opportunity of an newsletter with extract for a period. Unfortunately no further author by now.... :)
However, to get this thing started there need to be some kind of collaborating tool to create the text. I know from some groups which are using a wiki or Etherpad for doing this. As Geany is an IDE and I feel a bit more comfortable with a VCS I'd suggest to make usage of a git/svn/hg/* here to collect and edit the texts for the newsletter before sending them out. Maybe we could use git.uvena.de also for hosting of these. What do you think?
It should be git.geany.org, in my opinion. (Even if it lands on the same machine ;) )
Regards, Dominic
On Sat, 08 Jan 2011 03:51:10 +0100 Dominic Hopf dmaphy@googlemail.com wrote:
Am Mittwoch, den 05.01.2011, 23:52 +0100 schrieb Frank Lanitz:
On Sun, 2 Jan 2011 15:11:39 +0100 Frank Lanitz frank@frank.uvena.de wrote:
[...]
So question are: Who would like to see such a thing? Who would be able to help compiling such a newsletter? Any other ideas or suggestions?
After a a bunch of feedback I'd say that most of the people would like to have opportunity of an newsletter with extract for a period. Unfortunately no further author by now.... :)
However, to get this thing started there need to be some kind of collaborating tool to create the text. I know from some groups which are using a wiki or Etherpad for doing this. As Geany is an IDE and I feel a bit more comfortable with a VCS I'd suggest to make usage of a git/svn/hg/* here to collect and edit the texts for the newsletter before sending them out. Maybe we could use git.uvena.de also for hosting of these. What do you think?
It should be git.geany.org, in my opinion. (Even if it lands on the same machine ;) )
Yepp, as its geany related you are right ;)
Cheers, Frank
Le 05/01/2011 23:52, Frank Lanitz a écrit :
On Sun, 2 Jan 2011 15:11:39 +0100 Frank Lanitz frank@frank.uvena.de wrote:
[...]
So question are: Who would like to see such a thing? Who would be able to help compiling such a newsletter? Any other ideas or suggestions?
After a a bunch of feedback I'd say that most of the people would like to have opportunity of an newsletter with extract for a period. Unfortunately no further author by now.... :)
However, to get this thing started there need to be some kind of collaborating tool to create the text. I know from some groups which are using a wiki or Etherpad for doing this. As Geany is an IDE and I feel a bit more comfortable with a VCS I'd suggest to make usage of a git/svn/hg/* here to collect and edit the texts for the newsletter before sending them out. Maybe we could use git.uvena.de also for hosting of these. What do you think?
A bit late, but that's a good idea -- Git, of course :D
Though I still don't propose myself as an author, I might try to help a bit the process by reviewing, commenting and perhaps sometimes writing a bit. No full-time job as you see, but if it can help, I'll try to.
Cheers, Colomban
Hi,
On Fri, 14 Jan 2011 17:21:23 +0100 Colomban Wendling lists.ban@herbesfolles.org wrote:
Le 05/01/2011 23:52, Frank Lanitz a écrit :
On Sun, 2 Jan 2011 15:11:39 +0100 Frank Lanitz frank@frank.uvena.de wrote:
[...]
So question are: Who would like to see such a thing? Who would be able to help compiling such a newsletter? Any other ideas or suggestions?
After a a bunch of feedback I'd say that most of the people would like to have opportunity of an newsletter with extract for a period. Unfortunately no further author by now.... :)
However, to get this thing started there need to be some kind of collaborating tool to create the text. I know from some groups which are using a wiki or Etherpad for doing this. As Geany is an IDE and I feel a bit more comfortable with a VCS I'd suggest to make usage of a git/svn/hg/* here to collect and edit the texts for the newsletter before sending them out. Maybe we could use git.uvena.de also for hosting of these. What do you think?
A bit late, but that's a good idea -- Git, of course :D
Though I still don't propose myself as an author, I might try to help a bit the process by reviewing, commenting and perhaps sometimes writing a bit. No full-time job as you see, but if it can help, I'll try to.
Just send in some text if you have some ;)
Cheers, Frank
Le 15/01/2011 04:23, Frank Lanitz a écrit :
Hi,
On Fri, 14 Jan 2011 17:21:23 +0100 Colomban Wendling lists.ban@herbesfolles.org wrote:
Le 05/01/2011 23:52, Frank Lanitz a écrit :
On Sun, 2 Jan 2011 15:11:39 +0100 Frank Lanitz frank@frank.uvena.de wrote:
[...]
So question are: Who would like to see such a thing? Who would be able to help compiling such a newsletter? Any other ideas or suggestions?
After a a bunch of feedback I'd say that most of the people would like to have opportunity of an newsletter with extract for a period. Unfortunately no further author by now.... :)
However, to get this thing started there need to be some kind of collaborating tool to create the text. I know from some groups which are using a wiki or Etherpad for doing this. As Geany is an IDE and I feel a bit more comfortable with a VCS I'd suggest to make usage of a git/svn/hg/* here to collect and edit the texts for the newsletter before sending them out. Maybe we could use git.uvena.de also for hosting of these. What do you think?
A bit late, but that's a good idea -- Git, of course :D
Though I still don't propose myself as an author, I might try to help a bit the process by reviewing, commenting and perhaps sometimes writing a bit. No full-time job as you see, but if it can help, I'll try to.
Just send in some text if you have some ;)
Unfortunately I have none yet :/ Is there a repo already?
On 3 January 2011 00:11, Frank Lanitz frank@frank.uvena.de wrote:
Hi folks,
I was thinking about an idea I'm not sure whether somebody would be interesting in.
As the Geany family is growing it might become more difficult to keep track on current developments inside the project as well as the close environment like new or updated plugins, important updates on GTK or some other used library in case you don't read every mail on the mailing list or hanging around all time inside IRC.
As I know from a couple of other projects some kind of a project newsletter has been set up by a couple of people to help to keep on track with latest updates. So I'd like to suggest setting up something like this also for Geany and its plugins etc..
In difference to the newsletters around Debian or PostgresSQL I was thinking about a monthly one maintained by a small team of maybe three people monitoring the mailing list, IRC as well as they are open for input of users and (plugin) developers. Based on this they could compile a newsletter and send it out to either geany-user mailing list or maybe some newly created one.
I could imagine of topics inside the 'newsletter' (unsorted list):
- Geany Core
* Reviews inside press, blogs, wikis etc. * Major updates/bugfixes/improvements on svn trunk * New releases and updates * HowTos for working with Geany
- Plugins
* New plugins available * Major updates/improvements/bugfixes on plugins
- General
* Important updates of used libraries * News out of community (of importance for Geany)
So question are: Who would like to see such a thing? Who would be able to help compiling such a newsletter? Any other ideas or suggestions?
Cheers, Frank -- Frank Lanitz frank@frank.uvena.de
I think this is a *great* idea and am willing to volunteer as a member of the newsletter team. I'm happy to "give it a go" and will let others judge my work. My time is rather limited at the moment but I believe I could make a useful contribution. I speak (and write) only English, I'm afraid, so I couldn't contribute to translations in any way.
In thinking about the format, I wonder if a blog-style format might be better than a regular newsletter. I say this only because a newsletter can be delayed solely because one item is not quite ready. I am the author and editor of the Frugalware Linux newsletter, so I have some experience in this area. For the moment I'll await further details and team members. :)
Hi,
Sorry for the late coming back. Somehow I missed this mail ...
On Fri, 21 Jan 2011 22:08:15 +1000 Russell Dickenson russelldickenson@gmail.com wrote:
I think this is a *great* idea and am willing to volunteer as a member of the newsletter team.
Cool. Great to hear.
I'm happy to "give it a go" and will let others judge my work. My time is rather limited at the moment but I believe I could make a useful contribution. I speak (and write) only English, I'm afraid, so I couldn't contribute to translations in any way.
As we should start in English, a native speaker could be a great help beside of contributing content also on spell checking, grammar and stuff.
In thinking about the format, I wonder if a blog-style format might be better than a regular newsletter. I say this only because a newsletter can be delayed solely because one item is not quite ready. I am the author and editor of the Frugalware Linux newsletter, so I have some experience in this area. For the moment I'll await further details and team members. :)
Well, I'm not sure how this could look like. Can you give a more detailed exampled?
Right now I started to put some content together into a LaTeX-file which will be compiled to PDF and plain text and send out later once its done.
Cheers, Frank
On 7 February 2011 03:00, Frank Lanitz frank@frank.uvena.de wrote:
Hi,
Sorry for the late coming back. Somehow I missed this mail ...
On Fri, 21 Jan 2011 22:08:15 +1000 Russell Dickenson russelldickenson@gmail.com wrote:
I think this is a *great* idea and am willing to volunteer as a member of the newsletter team.
Cool. Great to hear.
I'm happy to "give it a go" and will let others judge my work. My time is rather limited at the moment but I believe I could make a useful contribution. I speak (and write) only English, I'm afraid, so I couldn't contribute to translations in any way.
As we should start in English, a native speaker could be a great help beside of contributing content also on spell checking, grammar and stuff.
I'll do my best. :)
In thinking about the format, I wonder if a blog-style format might be better than a regular newsletter. I say this only because a newsletter can be delayed solely because one item is not quite ready. I am the author and editor of the Frugalware Linux newsletter, so I have some experience in this area. For the moment I'll await further details and team members. :)
Well, I'm not sure how this could look like. Can you give a more detailed exampled?
For examples of "my" work for Frugalware Linux, look here - http://www.frugalware.org and click on the links in the newsletter announcements.
The question is: in what format would people like to see the newsletter published? The Ubuntu newsletter is published as a weekly email, for example. The Frugalware Linux newsletter is published on a web site in HTML format. Personally I would prefer that the newsletter's content be hosted on a web site instead of sent out via email. The hosted method makes it easier to correct errors which may occur occasionally. Of course we could announce the latest newsletter in the usual Geany ML(s).
Right now I started to put some content together into a LaTeX-file which will be compiled to PDF and plain text and send out later once its done.
Would you mind sending the finished product to me?
A question to Frank and others - do you mind in what format the newsletter's content is written in? I only have experience in using HTML and AsciiDoc (http://www.methods.co.nz/asciidoc/). I would *much* prefer to use AsciiDoc because it "is a text document format for writing notes, documentation, articles, books, ebooks, slideshows, web pages, man pages and blogs. AsciiDoc files can be translated to many formats including HTML, PDF, EPUB, man page." I know that there are similar tools such as "plain text" markup languages but AsciiDoc is the one with which I have most experience.
Assuming we were using AsciiDoc, we could have a master document which then draws in content from various contributors and is then converted to various formats. This method would make the job of the newsletter's editor a little easier since each piece can be edited separately, then combined into one document.
Cheers, Frank
Thanks for your reply.
Another question to everyone - since I am the only person to have volunteered so far I'm putting my thoughts out for everyone to read. Am I going too far in suggesting formats and tools?
On 7 February 2011 09:24, Russell Dickenson russelldickenson@gmail.com wrote:
On 7 February 2011 03:00, Frank Lanitz frank@frank.uvena.de wrote:
Hi,
Sorry for the late coming back. Somehow I missed this mail ...
On Fri, 21 Jan 2011 22:08:15 +1000 Russell Dickenson russelldickenson@gmail.com wrote:
I think this is a *great* idea and am willing to volunteer as a member of the newsletter team.
Cool. Great to hear.
I'm happy to "give it a go" and will let others judge my work. My time is rather limited at the moment but I believe I could make a useful contribution. I speak (and write) only English, I'm afraid, so I couldn't contribute to translations in any way.
As we should start in English, a native speaker could be a great help beside of contributing content also on spell checking, grammar and stuff.
I'll do my best. :)
In thinking about the format, I wonder if a blog-style format might be better than a regular newsletter. I say this only because a newsletter can be delayed solely because one item is not quite ready. I am the author and editor of the Frugalware Linux newsletter, so I have some experience in this area. For the moment I'll await further details and team members. :)
Well, I'm not sure how this could look like. Can you give a more detailed exampled?
For examples of "my" work for Frugalware Linux, look here - http://www.frugalware.org and click on the links in the newsletter announcements.
Thats the sort of thing I imagined when Frank raised the possibility. (but larger type please)
The question is: in what format would people like to see the newsletter published? The Ubuntu newsletter is published as a weekly email, for example. The Frugalware Linux newsletter is published on a web site in HTML format. Personally I would prefer that the newsletter's content be hosted on a web site instead of sent out via email. The hosted method makes it easier to correct errors which may occur occasionally. Of course we could announce the latest newsletter in the usual Geany ML(s).
+1 for website, then I can't delete it and an archive can be kept in case it contains stuff that lasts beyond this month.
Which actually would be a good idea, Geany has a fair bit of "hidden" functionality and a "function of the month" exposing functions of Geany that people tend to forget would be good, I know I keep (re)learning new shortcuts.
And a "Plugin of the month" too :-)
Right now I started to put some content together into a LaTeX-file which will be compiled to PDF and plain text and send out later once its done.
Would you mind sending the finished product to me?
A question to Frank and others - do you mind in what format the newsletter's content is written in? I only have experience in using HTML and AsciiDoc (http://www.methods.co.nz/asciidoc/). I would *much* prefer to use AsciiDoc because it "is a text document format for writing notes, documentation, articles, books, ebooks, slideshows, web pages, man pages and blogs. AsciiDoc files can be translated to many formats including HTML, PDF, EPUB, man page." I know that there are similar tools such as "plain text" markup languages but AsciiDoc is the one with which I have most experience.
-1 for Latex, I know Frank is a Latexpert but they are a bit thin on the ground, so having to do contributions in Latex would be limiting (or would require Frank to do lots of conversion, and we want him to have more time for other things :-).
As an occasional Asciidoc contributor I hate to say this but...
Perhaps the project should stick to one markup language? Geany's documentation is done in reST, a part of Python's docutils which is used to produce the Python docs. (see http://docs.python.org/documenting/index.html ). reST is a "lightweight markup language" quite similar to Asciidoc and as you can see from the Geany help file produces HTML (and others too IIRC).
Personal comment, I moved from reST to Asciidoc because I prefer its source and its output, but the difference in the source isn't huge so I doubt Russell will have much difficulty.
Assuming we were using AsciiDoc, we could have a master document which then draws in content from various contributors and is then converted to various formats. This method would make the job of the newsletter's editor a little easier since each piece can be edited separately, then combined into one document.
Anything that simplifies the process is good if it reduces the time required of the editor and contributors. This leads to more contributions and more regular publication.
Cheers, Frank
Thanks for your reply.
Another question to everyone - since I am the only person to have volunteered so far I'm putting my thoughts out for everyone to read. Am I going too far in suggesting formats and tools?
Since it seems to be only you and Frank ATM both of you need to be happy about the tools.
Cheers Lex
-- Russell _______________________________________________ Geany mailing list Geany@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany
On 7 February 2011 09:53, Lex Trotman elextr@gmail.com wrote:
On 7 February 2011 09:24, Russell Dickenson russelldickenson@gmail.com wrote:
On 7 February 2011 03:00, Frank Lanitz frank@frank.uvena.de wrote:
Hi,
Sorry for the late coming back. Somehow I missed this mail ...
On Fri, 21 Jan 2011 22:08:15 +1000 Russell Dickenson russelldickenson@gmail.com wrote:
I think this is a *great* idea and am willing to volunteer as a member of the newsletter team.
Cool. Great to hear.
I'm happy to "give it a go" and will let others judge my work. My time is rather limited at the moment but I believe I could make a useful contribution. I speak (and write) only English, I'm afraid, so I couldn't contribute to translations in any way.
As we should start in English, a native speaker could be a great help beside of contributing content also on spell checking, grammar and stuff.
I'll do my best. :)
In thinking about the format, I wonder if a blog-style format might be better than a regular newsletter. I say this only because a newsletter can be delayed solely because one item is not quite ready. I am the author and editor of the Frugalware Linux newsletter, so I have some experience in this area. For the moment I'll await further details and team members. :)
Well, I'm not sure how this could look like. Can you give a more detailed exampled?
For examples of "my" work for Frugalware Linux, look here - http://www.frugalware.org and click on the links in the newsletter announcements.
Thats the sort of thing I imagined when Frank raised the possibility. (but larger type please)
Good. I agree that larger type is desireable, given that my eyes are aging. :) Some CSS changes were made on the Frugalware web site and I agree that the new type size is a little too small.
The question is: in what format would people like to see the newsletter published? The Ubuntu newsletter is published as a weekly email, for example. The Frugalware Linux newsletter is published on a web site in HTML format. Personally I would prefer that the newsletter's content be hosted on a web site instead of sent out via email. The hosted method makes it easier to correct errors which may occur occasionally. Of course we could announce the latest newsletter in the usual Geany ML(s).
+1 for website, then I can't delete it and an archive can be kept in case it contains stuff that lasts beyond this month.
Thanks.
Which actually would be a good idea, Geany has a fair bit of "hidden" functionality and a "function of the month" exposing functions of Geany that people tend to forget would be good, I know I keep (re)learning new shortcuts.
And a "Plugin of the month" too :-)
I agree. A feature/plugin focus of the month would be useful. I know that it takes me a while to get to know an application like Geany well. Focusing on a particular feature would make the learning process easier for people like me. As someone who likes to tweak configuration settings, hints on these topics would also be useful I believe.
Right now I started to put some content together into a LaTeX-file which will be compiled to PDF and plain text and send out later once its done.
Would you mind sending the finished product to me?
A question to Frank and others - do you mind in what format the newsletter's content is written in? I only have experience in using HTML and AsciiDoc (http://www.methods.co.nz/asciidoc/). I would *much* prefer to use AsciiDoc because it "is a text document format for writing notes, documentation, articles, books, ebooks, slideshows, web pages, man pages and blogs. AsciiDoc files can be translated to many formats including HTML, PDF, EPUB, man page." I know that there are similar tools such as "plain text" markup languages but AsciiDoc is the one with which I have most experience.
-1 for Latex, I know Frank is a Latexpert but they are a bit thin on the ground, so having to do contributions in Latex would be limiting (or would require Frank to do lots of conversion, and we want him to have more time for other things :-).
Yes. Sorry, but I not likely to contribute if I have to learn something like Latex. It's not something I'm using now, nor likely to use any time in the near future so I'm simply not motivated to learn it.
As an occasional Asciidoc contributor I hate to say this but...
Perhaps the project should stick to one markup language? Geany's documentation is done in reST, a part of Python's docutils which is used to produce the Python docs. (see http://docs.python.org/documenting/index.html ). reST is a "lightweight markup language" quite similar to Asciidoc and as you can see from the Geany help file produces HTML (and others too IIRC).
That's the one I was trying to think of! Thanks, Lex, for reminding me. I included AsciiDoc only as an example. I don't want to complicate things too much so would be happy to use reST. I currently use AsciiDoc for other projects but I see no reason to try to force it upon other people when a similar tool is already in use and doing its job well.
Personal comment, I moved from reST to Asciidoc because I prefer its source and its output, but the difference in the source isn't huge so I doubt Russell will have much difficulty.
Perhaps you don't know me too well. :P Seriously though, I'm confident I could handle reST.
Assuming we were using AsciiDoc, we could have a master document which then draws in content from various contributors and is then converted to various formats. This method would make the job of the newsletter's editor a little easier since each piece can be edited separately, then combined into one document.
Anything that simplifies the process is good if it reduces the time required of the editor and contributors. This leads to more contributions and more regular publication.
I'll look into options available via reST. Even if it doesn't offer a "master document" option natively, I'm sure a custom solution could easily be created.
Cheers, Frank
Thanks for your reply.
Another question to everyone - since I am the only person to have volunteered so far I'm putting my thoughts out for everyone to read. Am I going too far in suggesting formats and tools?
Since it seems to be only you and Frank ATM both of you need to be happy about the tools.
I'm happy so far. :P I just want to make sure people don't see me rushing into this, forcing my opinions onto others.
On Mon, 7 Feb 2011 12:21:00 +1000 Russell Dickenson russelldickenson@gmail.com wrote:
The question is: in what format would people like to see the newsletter published? The Ubuntu newsletter is published as a weekly email, for example. The Frugalware Linux newsletter is published on a web site in HTML format. Personally I would prefer that the newsletter's content be hosted on a web site instead of sent out via email. The hosted method makes it easier to correct errors which may occur occasionally. Of course we could announce the latest newsletter in the usual Geany ML(s).
+1 for website, then I can't delete it and an archive can be kept in case it contains stuff that lasts beyond this month.
Thanks.
I guess depending on the markup language we are choosing in the end, generating a HTML with some nice cc should be the smallest issue as nearly all of them do support such thing.
Which actually would be a good idea, Geany has a fair bit of "hidden" functionality and a "function of the month" exposing functions of Geany that people tend to forget would be good, I know I keep (re)learning new shortcuts.
And a "Plugin of the month" too :-)
I agree. A feature/plugin focus of the month would be useful. I know that it takes me a while to get to know an application like Geany well. Focusing on a particular feature would make the learning process easier for people like me. As someone who likes to tweak configuration settings, hints on these topics would also be useful I believe.
In fact this is a nice idea. I'm asking who like to take over this task and provide something like this on a monthly basis for the newsletter?
Right now I started to put some content together into a LaTeX-file which will be compiled to PDF and plain text and send out later once its done.
Would you mind sending the finished product to me?
A question to Frank and others - do you mind in what format the newsletter's content is written in? I only have experience in using HTML and AsciiDoc (http://www.methods.co.nz/asciidoc/). I would *much* prefer to use AsciiDoc because it "is a text document format for writing notes, documentation, articles, books, ebooks, slideshows, web pages, man pages and blogs. AsciiDoc files can be translated to many formats including HTML, PDF, EPUB, man page." I know that there are similar tools such as "plain text" markup languages but AsciiDoc is the one with which I have most experience.
-1 for Latex, I know Frank is a Latexpert but they are a bit thin on the ground, so having to do contributions in Latex would be limiting (or would require Frank to do lots of conversion, and we want him to have more time for other things :-).
Yes. Sorry, but I not likely to contribute if I have to learn something like Latex. It's not something I'm using now, nor likely to use any time in the near future so I'm simply not motivated to learn it.
I don't care much about the markup language. LaTeX on our level is not more complicated as writing ReST etc. I guess.
As an occasional Asciidoc contributor I hate to say this but...
Perhaps the project should stick to one markup language? Geany's documentation is done in reST, a part of Python's docutils which is used to produce the Python docs. (see http://docs.python.org/documenting/index.html ). reST is a "lightweight markup language" quite similar to Asciidoc and as you can see from the Geany help file produces HTML (and others too IIRC).
That's the one I was trying to think of! Thanks, Lex, for reminding me. I included AsciiDoc only as an example. I don't want to complicate things too much so would be happy to use reST. I currently use AsciiDoc for other projects but I see no reason to try to force it upon other people when a similar tool is already in use and doing its job well.
OK. Let's give ReST a try. I guess we will need to have a makefile which is generating the output we need. Who likes to do this? Also I think this should be done after volume 1 has been send to public.
Assuming we were using AsciiDoc, we could have a master document which then draws in content from various contributors and is then converted to various formats. This method would make the job of the newsletter's editor a little easier since each piece can be edited separately, then combined into one document.
Anything that simplifies the process is good if it reduces the time required of the editor and contributors. This leads to more contributions and more regular publication.
I'll look into options available via reST. Even if it doesn't offer a "master document" option natively, I'm sure a custom solution could easily be created.
As mentioned: With usage of git there is no real need to have such thing like a master document as its possible to edit without having unsolvable conflicts.
Cheers, Frank
On 8 February 2011 04:21, Frank Lanitz frank@frank.uvena.de wrote:
On Mon, 7 Feb 2011 12:21:00 +1000 Russell Dickenson russelldickenson@gmail.com wrote:
The question is: in what format would people like to see the newsletter published? The Ubuntu newsletter is published as a weekly email, for example. The Frugalware Linux newsletter is published on a web site in HTML format. Personally I would prefer that the newsletter's content be hosted on a web site instead of sent out via email. The hosted method makes it easier to correct errors which may occur occasionally. Of course we could announce the latest newsletter in the usual Geany ML(s).
+1 for website, then I can't delete it and an archive can be kept in case it contains stuff that lasts beyond this month.
Thanks.
I guess depending on the markup language we are choosing in the end, generating a HTML with some nice cc should be the smallest issue as nearly all of them do support such thing.
Sorry but I don't understand what "cc" means. :P
Which actually would be a good idea, Geany has a fair bit of "hidden" functionality and a "function of the month" exposing functions of Geany that people tend to forget would be good, I know I keep (re)learning new shortcuts.
And a "Plugin of the month" too :-)
I agree. A feature/plugin focus of the month would be useful. I know that it takes me a while to get to know an application like Geany well. Focusing on a particular feature would make the learning process easier for people like me. As someone who likes to tweak configuration settings, hints on these topics would also be useful I believe.
In fact this is a nice idea. I'm asking who like to take over this task and provide something like this on a monthly basis for the newsletter?
I'll volunteer for this role. You need to know, though, that I am learning Geany so my explanations are likely to be quite simple. This may be a good thing because as I learn I can write about what I have learned in the newsletter. I'll need someone who is more familiar with Geany to check my work though.
Right now I started to put some content together into a LaTeX-file which will be compiled to PDF and plain text and send out later once its done.
Would you mind sending the finished product to me?
A question to Frank and others - do you mind in what format the newsletter's content is written in? I only have experience in using HTML and AsciiDoc (http://www.methods.co.nz/asciidoc/). I would *much* prefer to use AsciiDoc because it "is a text document format for writing notes, documentation, articles, books, ebooks, slideshows, web pages, man pages and blogs. AsciiDoc files can be translated to many formats including HTML, PDF, EPUB, man page." I know that there are similar tools such as "plain text" markup languages but AsciiDoc is the one with which I have most experience.
-1 for Latex, I know Frank is a Latexpert but they are a bit thin on the ground, so having to do contributions in Latex would be limiting (or would require Frank to do lots of conversion, and we want him to have more time for other things :-).
Yes. Sorry, but I not likely to contribute if I have to learn something like Latex. It's not something I'm using now, nor likely to use any time in the near future so I'm simply not motivated to learn it.
I don't care much about the markup language. LaTeX on our level is not more complicated as writing ReST etc. I guess.
I would prefer not to have to learn something like LaTeX but since there's a Geany plugin available, I'm happy to stick with LaTeX for the moment. As you suggest, Frank, since we're not writing complex documents I don't expect the LaTeX markup used to be very complex. I'll probably be doing a little cut-and-pasting if that's OK.
As an occasional Asciidoc contributor I hate to say this but...
Perhaps the project should stick to one markup language? Geany's documentation is done in reST, a part of Python's docutils which is used to produce the Python docs. (see http://docs.python.org/documenting/index.html ). reST is a "lightweight markup language" quite similar to Asciidoc and as you can see from the Geany help file produces HTML (and others too IIRC).
That's the one I was trying to think of! Thanks, Lex, for reminding me. I included AsciiDoc only as an example. I don't want to complicate things too much so would be happy to use reST. I currently use AsciiDoc for other projects but I see no reason to try to force it upon other people when a similar tool is already in use and doing its job well.
OK. Let's give ReST a try. I guess we will need to have a makefile which is generating the output we need. Who likes to do this? Also I think this should be done after volume 1 has been send to public.
In fact perhaps we should stick with LaTeX for the moment, Frank? Since you have experience with this already, creating the necessary Makefile should be easier than creating one for reST (or is it ReST ?).
Assuming we were using AsciiDoc, we could have a master document which then draws in content from various contributors and is then converted to various formats. This method would make the job of the newsletter's editor a little easier since each piece can be edited separately, then combined into one document.
Anything that simplifies the process is good if it reduces the time required of the editor and contributors. This leads to more contributions and more regular publication.
I'll look into options available via reST. Even if it doesn't offer a "master document" option natively, I'm sure a custom solution could easily be created.
As mentioned: With usage of git there is no real need to have such thing like a master document as its possible to edit without having unsolvable conflicts.
I am using a master document for the Frugalware Linux newsletter for various reasons which probably don't apply to the Geany newsletter. I am comfortable using Git and agree that there's no need at the moment for a master document.
Cheers, Frank -- http://frank.uvena.de/en/
Thanks.
On 8 February 2011 09:50, Russell Dickenson russelldickenson@gmail.com wrote:
On 8 February 2011 04:21, Frank Lanitz frank@frank.uvena.de wrote:
On Mon, 7 Feb 2011 12:21:00 +1000 Russell Dickenson russelldickenson@gmail.com wrote:
The question is: in what format would people like to see the newsletter published? The Ubuntu newsletter is published as a weekly email, for example. The Frugalware Linux newsletter is published on a web site in HTML format. Personally I would prefer that the newsletter's content be hosted on a web site instead of sent out via email. The hosted method makes it easier to correct errors which may occur occasionally. Of course we could announce the latest newsletter in the usual Geany ML(s).
+1 for website, then I can't delete it and an archive can be kept in case it contains stuff that lasts beyond this month.
Thanks.
I guess depending on the markup language we are choosing in the end, generating a HTML with some nice cc should be the smallest issue as nearly all of them do support such thing.
Sorry but I don't understand what "cc" means. :P
Maybe Frank means css style sheets?
Which actually would be a good idea, Geany has a fair bit of "hidden" functionality and a "function of the month" exposing functions of Geany that people tend to forget would be good, I know I keep (re)learning new shortcuts.
And a "Plugin of the month" too :-)
I agree. A feature/plugin focus of the month would be useful. I know that it takes me a while to get to know an application like Geany well. Focusing on a particular feature would make the learning process easier for people like me. As someone who likes to tweak configuration settings, hints on these topics would also be useful I believe.
In fact this is a nice idea. I'm asking who like to take over this task and provide something like this on a monthly basis for the newsletter?
I'll volunteer for this role. You need to know, though, that I am learning Geany so my explanations are likely to be quite simple. This may be a good thing because as I learn I can write about what I have learned in the newsletter. I'll need someone who is more familiar with Geany to check my work though.
I can do quick check, just post when committed.
Right now I started to put some content together into a LaTeX-file which will be compiled to PDF and plain text and send out later once its done.
Would you mind sending the finished product to me?
A question to Frank and others - do you mind in what format the newsletter's content is written in? I only have experience in using HTML and AsciiDoc (http://www.methods.co.nz/asciidoc/). I would *much* prefer to use AsciiDoc because it "is a text document format for writing notes, documentation, articles, books, ebooks, slideshows, web pages, man pages and blogs. AsciiDoc files can be translated to many formats including HTML, PDF, EPUB, man page." I know that there are similar tools such as "plain text" markup languages but AsciiDoc is the one with which I have most experience.
-1 for Latex, I know Frank is a Latexpert but they are a bit thin on the ground, so having to do contributions in Latex would be limiting (or would require Frank to do lots of conversion, and we want him to have more time for other things :-).
Yes. Sorry, but I not likely to contribute if I have to learn something like Latex. It's not something I'm using now, nor likely to use any time in the near future so I'm simply not motivated to learn it.
I don't care much about the markup language. LaTeX on our level is not more complicated as writing ReST etc. I guess.
I would prefer not to have to learn something like LaTeX but since there's a Geany plugin available, I'm happy to stick with LaTeX for the moment. As you suggest, Frank, since we're not writing complex documents I don't expect the LaTeX markup used to be very complex. I'll probably be doing a little cut-and-pasting if that's OK.
As an occasional Asciidoc contributor I hate to say this but...
Perhaps the project should stick to one markup language? Geany's documentation is done in reST, a part of Python's docutils which is used to produce the Python docs. (see http://docs.python.org/documenting/index.html ). reST is a "lightweight markup language" quite similar to Asciidoc and as you can see from the Geany help file produces HTML (and others too IIRC).
That's the one I was trying to think of! Thanks, Lex, for reminding me. I included AsciiDoc only as an example. I don't want to complicate things too much so would be happy to use reST. I currently use AsciiDoc for other projects but I see no reason to try to force it upon other people when a similar tool is already in use and doing its job well.
OK. Let's give ReST a try. I guess we will need to have a makefile which is generating the output we need. Who likes to do this? Also I think this should be done after volume 1 has been send to public.
In fact perhaps we should stick with LaTeX for the moment, Frank? Since you have experience with this already, creating the necessary Makefile should be easier than creating one for reST (or is it ReST ?).
Shrug?? Its spelled reStructuredText so I guessed little re but who knows.
Cheers Lex
Assuming we were using AsciiDoc, we could have a master document which then draws in content from various contributors and is then converted to various formats. This method would make the job of the newsletter's editor a little easier since each piece can be edited separately, then combined into one document.
Anything that simplifies the process is good if it reduces the time required of the editor and contributors. This leads to more contributions and more regular publication.
I'll look into options available via reST. Even if it doesn't offer a "master document" option natively, I'm sure a custom solution could easily be created.
As mentioned: With usage of git there is no real need to have such thing like a master document as its possible to edit without having unsolvable conflicts.
I am using a master document for the Frugalware Linux newsletter for various reasons which probably don't apply to the Geany newsletter. I am comfortable using Git and agree that there's no need at the moment for a master document.
Cheers, Frank -- http://frank.uvena.de/en/
Thanks.
-- Russell _______________________________________________ Geany mailing list Geany@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany
On 8 February 2011 09:08, Lex Trotman elextr@gmail.com wrote:
On 8 February 2011 09:50, Russell Dickenson russelldickenson@gmail.com wrote:
On 8 February 2011 04:21, Frank Lanitz frank@frank.uvena.de wrote:
On Mon, 7 Feb 2011 12:21:00 +1000 Russell Dickenson russelldickenson@gmail.com wrote:
The question is: in what format would people like to see the newsletter published? The Ubuntu newsletter is published as a weekly email, for example. The Frugalware Linux newsletter is published on a web site in HTML format. Personally I would prefer that the newsletter's content be hosted on a web site instead of sent out via email. The hosted method makes it easier to correct errors which may occur occasionally. Of course we could announce the latest newsletter in the usual Geany ML(s).
+1 for website, then I can't delete it and an archive can be kept in case it contains stuff that lasts beyond this month.
Thanks.
I guess depending on the markup language we are choosing in the end, generating a HTML with some nice cc should be the smallest issue as nearly all of them do support such thing.
Sorry but I don't understand what "cc" means. :P
Maybe Frank means css style sheets?
That's what I thought but I'll wait in eager anticipation to hear from Frank. :)
Which actually would be a good idea, Geany has a fair bit of "hidden" functionality and a "function of the month" exposing functions of Geany that people tend to forget would be good, I know I keep (re)learning new shortcuts.
And a "Plugin of the month" too :-)
I agree. A feature/plugin focus of the month would be useful. I know that it takes me a while to get to know an application like Geany well. Focusing on a particular feature would make the learning process easier for people like me. As someone who likes to tweak configuration settings, hints on these topics would also be useful I believe.
In fact this is a nice idea. I'm asking who like to take over this task and provide something like this on a monthly basis for the newsletter?
I'll volunteer for this role. You need to know, though, that I am learning Geany so my explanations are likely to be quite simple. This may be a good thing because as I learn I can write about what I have learned in the newsletter. I'll need someone who is more familiar with Geany to check my work though.
I can do quick check, just post when committed.
Thanks.
I'll start writing my first article and we'll see how it goes.
> Right now I started to put some content together into a LaTeX-file > which will be compiled to PDF and plain text and send out later > once its done.
Would you mind sending the finished product to me?
A question to Frank and others - do you mind in what format the newsletter's content is written in? I only have experience in using HTML and AsciiDoc (http://www.methods.co.nz/asciidoc/). I would *much* prefer to use AsciiDoc because it "is a text document format for writing notes, documentation, articles, books, ebooks, slideshows, web pages, man pages and blogs. AsciiDoc files can be translated to many formats including HTML, PDF, EPUB, man page." I know that there are similar tools such as "plain text" markup languages but AsciiDoc is the one with which I have most experience.
-1 for Latex, I know Frank is a Latexpert but they are a bit thin on the ground, so having to do contributions in Latex would be limiting (or would require Frank to do lots of conversion, and we want him to have more time for other things :-).
Yes. Sorry, but I not likely to contribute if I have to learn something like Latex. It's not something I'm using now, nor likely to use any time in the near future so I'm simply not motivated to learn it.
I don't care much about the markup language. LaTeX on our level is not more complicated as writing ReST etc. I guess.
I would prefer not to have to learn something like LaTeX but since there's a Geany plugin available, I'm happy to stick with LaTeX for the moment. As you suggest, Frank, since we're not writing complex documents I don't expect the LaTeX markup used to be very complex. I'll probably be doing a little cut-and-pasting if that's OK.
As an occasional Asciidoc contributor I hate to say this but...
Perhaps the project should stick to one markup language? Geany's documentation is done in reST, a part of Python's docutils which is used to produce the Python docs. (see http://docs.python.org/documenting/index.html ). reST is a "lightweight markup language" quite similar to Asciidoc and as you can see from the Geany help file produces HTML (and others too IIRC).
That's the one I was trying to think of! Thanks, Lex, for reminding me. I included AsciiDoc only as an example. I don't want to complicate things too much so would be happy to use reST. I currently use AsciiDoc for other projects but I see no reason to try to force it upon other people when a similar tool is already in use and doing its job well.
OK. Let's give ReST a try. I guess we will need to have a makefile which is generating the output we need. Who likes to do this? Also I think this should be done after volume 1 has been send to public.
In fact perhaps we should stick with LaTeX for the moment, Frank? Since you have experience with this already, creating the necessary Makefile should be easier than creating one for reST (or is it ReST ?).
Shrug?? Its spelled reStructuredText so I guessed little re but who knows.
Shrug!? I'm sorry but this sort of attitude can only lead to utter chaos and anarchy. :P The world *must* have order and this includes getting ALL cApItaLisAtiOn correct!
Cheers Lex
Assuming we were using AsciiDoc, we could have a master document which then draws in content from various contributors and is then converted to various formats. This method would make the job of the newsletter's editor a little easier since each piece can be edited separately, then combined into one document.
Anything that simplifies the process is good if it reduces the time required of the editor and contributors. This leads to more contributions and more regular publication.
I'll look into options available via reST. Even if it doesn't offer a "master document" option natively, I'm sure a custom solution could easily be created.
As mentioned: With usage of git there is no real need to have such thing like a master document as its possible to edit without having unsolvable conflicts.
I am using a master document for the Frugalware Linux newsletter for various reasons which probably don't apply to the Geany newsletter. I am comfortable using Git and agree that there's no need at the moment for a master document.
Cheers, Frank -- http://frank.uvena.de/en/
Thanks.
-- Russell
On 8 February 2011 10:13, Russell Dickenson russelldickenson@gmail.com wrote:
On 8 February 2011 09:08, Lex Trotman elextr@gmail.com wrote:
On 8 February 2011 09:50, Russell Dickenson russelldickenson@gmail.com wrote:
On 8 February 2011 04:21, Frank Lanitz frank@frank.uvena.de wrote:
On Mon, 7 Feb 2011 12:21:00 +1000 Russell Dickenson russelldickenson@gmail.com wrote:
> The question is: in what format would people like to see the > newsletter published? The Ubuntu newsletter is published as a > weekly email, for example. The Frugalware Linux newsletter is > published on a web site in HTML format. Personally I would prefer > that the newsletter's content be hosted on a web site instead of > sent out via email. The hosted method makes it easier to correct > errors which may occur occasionally. Of course we could announce > the latest newsletter in the usual Geany ML(s).
+1 for website, then I can't delete it and an archive can be kept in case it contains stuff that lasts beyond this month.
Thanks.
I guess depending on the markup language we are choosing in the end, generating a HTML with some nice cc should be the smallest issue as nearly all of them do support such thing.
Sorry but I don't understand what "cc" means. :P
Maybe Frank means css style sheets?
That's what I thought but I'll wait in eager anticipation to hear from Frank. :)
Which actually would be a good idea, Geany has a fair bit of "hidden" functionality and a "function of the month" exposing functions of Geany that people tend to forget would be good, I know I keep (re)learning new shortcuts.
And a "Plugin of the month" too :-)
I agree. A feature/plugin focus of the month would be useful. I know that it takes me a while to get to know an application like Geany well. Focusing on a particular feature would make the learning process easier for people like me. As someone who likes to tweak configuration settings, hints on these topics would also be useful I believe.
In fact this is a nice idea. I'm asking who like to take over this task and provide something like this on a monthly basis for the newsletter?
I'll volunteer for this role. You need to know, though, that I am learning Geany so my explanations are likely to be quite simple. This may be a good thing because as I learn I can write about what I have learned in the newsletter. I'll need someone who is more familiar with Geany to check my work though.
I can do quick check, just post when committed.
Thanks.
I'll start writing my first article and we'll see how it goes.
>> Right now I started to put some content together into a LaTeX-file >> which will be compiled to PDF and plain text and send out later >> once its done. > > Would you mind sending the finished product to me? > > A question to Frank and others - do you mind in what format the > newsletter's content is written in? I only have experience in using > HTML and AsciiDoc (http://www.methods.co.nz/asciidoc/). I would > *much* prefer to use AsciiDoc because it "is a text document > format for writing notes, documentation, articles, books, ebooks, > slideshows, web pages, man pages and blogs. AsciiDoc files can be > translated to many formats including HTML, PDF, EPUB, man page." I > know that there are similar tools such as "plain text" markup > languages but AsciiDoc is the one with which I have most > experience.
-1 for Latex, I know Frank is a Latexpert but they are a bit thin on the ground, so having to do contributions in Latex would be limiting (or would require Frank to do lots of conversion, and we want him to have more time for other things :-).
Yes. Sorry, but I not likely to contribute if I have to learn something like Latex. It's not something I'm using now, nor likely to use any time in the near future so I'm simply not motivated to learn it.
I don't care much about the markup language. LaTeX on our level is not more complicated as writing ReST etc. I guess.
I would prefer not to have to learn something like LaTeX but since there's a Geany plugin available, I'm happy to stick with LaTeX for the moment. As you suggest, Frank, since we're not writing complex documents I don't expect the LaTeX markup used to be very complex. I'll probably be doing a little cut-and-pasting if that's OK.
As an occasional Asciidoc contributor I hate to say this but...
Perhaps the project should stick to one markup language? Geany's documentation is done in reST, a part of Python's docutils which is used to produce the Python docs. (see http://docs.python.org/documenting/index.html ). reST is a "lightweight markup language" quite similar to Asciidoc and as you can see from the Geany help file produces HTML (and others too IIRC).
That's the one I was trying to think of! Thanks, Lex, for reminding me. I included AsciiDoc only as an example. I don't want to complicate things too much so would be happy to use reST. I currently use AsciiDoc for other projects but I see no reason to try to force it upon other people when a similar tool is already in use and doing its job well.
OK. Let's give ReST a try. I guess we will need to have a makefile which is generating the output we need. Who likes to do this? Also I think this should be done after volume 1 has been send to public.
In fact perhaps we should stick with LaTeX for the moment, Frank? Since you have experience with this already, creating the necessary Makefile should be easier than creating one for reST (or is it ReST ?).
Shrug?? Its spelled reStructuredText so I guessed little re but who knows.
Shrug!? I'm sorry but this sort of attitude can only lead to utter chaos and anarchy. :P The world *must* have order and this includes getting ALL cApItaLisAtiOn correct!
Not to mention capitaliZation if your spull chucker is set to US English :-)
English is *such* a very standard language .... everyone has their own standard!
Cheers Lex
Cheers Lex
> Assuming we were using AsciiDoc, we could have a master document > which then draws in content from various contributors and is then > converted to various formats. This method would make the job of > the newsletter's editor a little easier since each piece can be > edited separately, then combined into one document.
Anything that simplifies the process is good if it reduces the time required of the editor and contributors. This leads to more contributions and more regular publication.
I'll look into options available via reST. Even if it doesn't offer a "master document" option natively, I'm sure a custom solution could easily be created.
As mentioned: With usage of git there is no real need to have such thing like a master document as its possible to edit without having unsolvable conflicts.
I am using a master document for the Frugalware Linux newsletter for various reasons which probably don't apply to the Geany newsletter. I am comfortable using Git and agree that there's no need at the moment for a master document.
Cheers, Frank -- http://frank.uvena.de/en/
Thanks.
-- Russell
-- Russell _______________________________________________ Geany mailing list Geany@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany
On 8 February 2011 09:31, Lex Trotman elextr@gmail.com wrote:
[snip]
Shrug?? Its spelled reStructuredText so I guessed little re but who knows.
Shrug!? I'm sorry but this sort of attitude can only lead to utter chaos and anarchy. :P The world *must* have order and this includes getting ALL cApItaLisAtiOn correct!
Not to mention capitaliZation if your spull chucker is set to US English :-)
That's the next challenge...which version of English is the newsletter to be written in? I'd suggest we accept whatever people write in. I see no reason to change someone else's spelling from American to British etc.
English is *such* a very standard language .... everyone has their own standard!
[snip]
I heard long ago some saying "The great thing about standards is that there are so many to choose from." :)
Am 08.02.2011 00:57, schrieb Russell Dickenson:
On 8 February 2011 09:31, Lex Trotman elextr@gmail.com wrote:
[snip]
Shrug?? Its spelled reStructuredText so I guessed little re but who knows.
Shrug!? I'm sorry but this sort of attitude can only lead to utter chaos and anarchy. :P The world *must* have order and this includes getting ALL cApItaLisAtiOn correct!
Not to mention capitaliZation if your spull chucker is set to US English :-)
That's the next challenge...which version of English is the newsletter to be written in? I'd suggest we accept whatever people write in. I see no reason to change someone else's spelling from American to British etc.
Well. I'd say this is step 2. Most of Geany is written using AE as its the most popular from I guess. Persoanlly I prefer to read BE as its cleaner -- but don't ask me I've got my issues either ;)
English is *such* a very standard language .... everyone has their own standard!
[snip]
I heard long ago some saying "The great thing about standards is that there are so many to choose from." :)
;)
Cheers, Frank
Am 08.02.2011 00:08, schrieb Lex Trotman:
On 8 February 2011 09:50, Russell Dickenson russelldickenson@gmail.com wrote:
In fact perhaps we should stick with LaTeX for the moment, Frank? Since you have experience with this already, creating the necessary Makefile should be easier than creating one for reST (or is it ReST ?).
Shrug?? Its spelled reStructuredText so I guessed little re but who knows.
Well, let's use the long version :D
Am 08.02.2011 11:28, schrieb Frank Lanitz:
Am 08.02.2011 00:08, schrieb Lex Trotman:
On 8 February 2011 09:50, Russell Dickenson russelldickenson@gmail.com wrote:
In fact perhaps we should stick with LaTeX for the moment, Frank? Since you have experience with this already, creating the necessary Makefile should be easier than creating one for reST (or is it ReST ?).
Shrug?? Its spelled reStructuredText so I guessed little re but who knows.
Well, let's use the long version :D
Ha! At http://docutils.sourceforge.net/rst.html the are suing at least one time ReST ;D (but reST too .... )
On 8 February 2011 21:30, Frank Lanitz frank@frank.uvena.de wrote:
Am 08.02.2011 11:28, schrieb Frank Lanitz:
Am 08.02.2011 00:08, schrieb Lex Trotman:
On 8 February 2011 09:50, Russell Dickenson russelldickenson@gmail.com wrote:
In fact perhaps we should stick with LaTeX for the moment, Frank? Since you have experience with this already, creating the necessary Makefile should be easier than creating one for reST (or is it ReST ?).
Shrug?? Its spelled reStructuredText so I guessed little re but who knows.
Well, let's use the long version :D
Ha! At http://docutils.sourceforge.net/rst.html the are suing at least one time ReST ;D (but reST too .... )
And this is why I don't use cAmelcAse identifiers, they're too damn hard to type consistently, my shift key is always behind my typing :-D
Cheers Lex
Geany mailing list Geany@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany
Dnia wtorek, 8 lutego 2011 o 11:30:16 Frank Lanitz napisał(a):
Ha! At http://docutils.sourceforge.net/rst.html the are suing at least one time ReST ;D (but reST too .... )
reST suing ReST? OMG BUHAHA LOL !!!
Am 07.02.2011 23:50, schrieb Russell Dickenson:
On 8 February 2011 04:21, Frank Lanitz frank@frank.uvena.de wrote:
On Mon, 7 Feb 2011 12:21:00 +1000 Russell Dickenson russelldickenson@gmail.com wrote:
The question is: in what format would people like to see the newsletter published? The Ubuntu newsletter is published as a weekly email, for example. The Frugalware Linux newsletter is published on a web site in HTML format. Personally I would prefer that the newsletter's content be hosted on a web site instead of sent out via email. The hosted method makes it easier to correct errors which may occur occasionally. Of course we could announce the latest newsletter in the usual Geany ML(s).
+1 for website, then I can't delete it and an archive can be kept in case it contains stuff that lasts beyond this month.
Thanks.
I guess depending on the markup language we are choosing in the end, generating a HTML with some nice cc should be the smallest issue as nearly all of them do support such thing.
Sorry but I don't understand what "cc" means. :P
Should have been CSS ;)
Which actually would be a good idea, Geany has a fair bit of "hidden" functionality and a "function of the month" exposing functions of Geany that people tend to forget would be good, I know I keep (re)learning new shortcuts.
And a "Plugin of the month" too :-)
I agree. A feature/plugin focus of the month would be useful. I know that it takes me a while to get to know an application like Geany well. Focusing on a particular feature would make the learning process easier for people like me. As someone who likes to tweak configuration settings, hints on these topics would also be useful I believe.
In fact this is a nice idea. I'm asking who like to take over this task and provide something like this on a monthly basis for the newsletter?
I'll volunteer for this role. You need to know, though, that I am learning Geany so my explanations are likely to be quite simple. This may be a good thing because as I learn I can write about what I have learned in the newsletter. I'll need someone who is more familiar with Geany to check my work though.
Great! Welcome aboard! Just ask if you have any question. I'm sure the list likes helping you out!
Right now I started to put some content together into a LaTeX-file which will be compiled to PDF and plain text and send out later once its done.
Would you mind sending the finished product to me?
A question to Frank and others - do you mind in what format the newsletter's content is written in? I only have experience in using HTML and AsciiDoc (http://www.methods.co.nz/asciidoc/). I would *much* prefer to use AsciiDoc because it "is a text document format for writing notes, documentation, articles, books, ebooks, slideshows, web pages, man pages and blogs. AsciiDoc files can be translated to many formats including HTML, PDF, EPUB, man page." I know that there are similar tools such as "plain text" markup languages but AsciiDoc is the one with which I have most experience.
-1 for Latex, I know Frank is a Latexpert but they are a bit thin on the ground, so having to do contributions in Latex would be limiting (or would require Frank to do lots of conversion, and we want him to have more time for other things :-).
Yes. Sorry, but I not likely to contribute if I have to learn something like Latex. It's not something I'm using now, nor likely to use any time in the near future so I'm simply not motivated to learn it.
I don't care much about the markup language. LaTeX on our level is not more complicated as writing ReST etc. I guess.
I would prefer not to have to learn something like LaTeX but since there's a Geany plugin available, I'm happy to stick with LaTeX for the moment. As you suggest, Frank, since we're not writing complex documents I don't expect the LaTeX markup used to be very complex. I'll probably be doing a little cut-and-pasting if that's OK.
;) You can have a look at
http://git.geany.org/newsletter/tree/newsletter_1.tex
Maybe its getting interesting at http://git.geany.org/newsletter/tree/newsletter_1.tex#n38
Let's see how it goes. ;)
As an occasional Asciidoc contributor I hate to say this but...
Perhaps the project should stick to one markup language? Geany's documentation is done in reST, a part of Python's docutils which is used to produce the Python docs. (see http://docs.python.org/documenting/index.html ). reST is a "lightweight markup language" quite similar to Asciidoc and as you can see from the Geany help file produces HTML (and others too IIRC).
That's the one I was trying to think of! Thanks, Lex, for reminding me. I included AsciiDoc only as an example. I don't want to complicate things too much so would be happy to use reST. I currently use AsciiDoc for other projects but I see no reason to try to force it upon other people when a similar tool is already in use and doing its job well.
OK. Let's give ReST a try. I guess we will need to have a makefile which is generating the output we need. Who likes to do this? Also I think this should be done after volume 1 has been send to public.
In fact perhaps we should stick with LaTeX for the moment, Frank? Since you have experience with this already, creating the necessary Makefile should be easier than creating one for reST (or is it ReST ?).
Yes, I can do it. I suggest outpout shall be plain text for email newsletter. PDF for FTP and HTML for some homepage, right?
Assuming we were using AsciiDoc, we could have a master document which then draws in content from various contributors and is then converted to various formats. This method would make the job of the newsletter's editor a little easier since each piece can be edited separately, then combined into one document.
Anything that simplifies the process is good if it reduces the time required of the editor and contributors. This leads to more contributions and more regular publication.
I'll look into options available via reST. Even if it doesn't offer a "master document" option natively, I'm sure a custom solution could easily be created.
As mentioned: With usage of git there is no real need to have such thing like a master document as its possible to edit without having unsolvable conflicts.
I am using a master document for the Frugalware Linux newsletter for various reasons which probably don't apply to the Geany newsletter. I am comfortable using Git and agree that there's no need at the moment for a master document.
Maybe using a masterdocument would be nice if somebody is working on some content and its not clear which 'release' it will be added. So we could do something like a busstop strategy for newsletter. But this is far away from being needed I guess.
Cheers, Frank
On 8 February 2011 20:26, Frank Lanitz frank@frank.uvena.de wrote:
Am 07.02.2011 23:50, schrieb Russell Dickenson:
On 8 February 2011 04:21, Frank Lanitz frank@frank.uvena.de wrote:
On Mon, 7 Feb 2011 12:21:00 +1000 Russell Dickenson russelldickenson@gmail.com wrote:
The question is: in what format would people like to see the newsletter published? The Ubuntu newsletter is published as a weekly email, for example. The Frugalware Linux newsletter is published on a web site in HTML format. Personally I would prefer that the newsletter's content be hosted on a web site instead of sent out via email. The hosted method makes it easier to correct errors which may occur occasionally. Of course we could announce the latest newsletter in the usual Geany ML(s).
+1 for website, then I can't delete it and an archive can be kept in case it contains stuff that lasts beyond this month.
Thanks.
I guess depending on the markup language we are choosing in the end, generating a HTML with some nice cc should be the smallest issue as nearly all of them do support such thing.
Sorry but I don't understand what "cc" means. :P
Should have been CSS ;)
OK
Which actually would be a good idea, Geany has a fair bit of "hidden" functionality and a "function of the month" exposing functions of Geany that people tend to forget would be good, I know I keep (re)learning new shortcuts.
And a "Plugin of the month" too :-)
I agree. A feature/plugin focus of the month would be useful. I know that it takes me a while to get to know an application like Geany well. Focusing on a particular feature would make the learning process easier for people like me. As someone who likes to tweak configuration settings, hints on these topics would also be useful I believe.
In fact this is a nice idea. I'm asking who like to take over this task and provide something like this on a monthly basis for the newsletter?
I'll volunteer for this role. You need to know, though, that I am learning Geany so my explanations are likely to be quite simple. This may be a good thing because as I learn I can write about what I have learned in the newsletter. I'll need someone who is more familiar with Geany to check my work though.
Great! Welcome aboard! Just ask if you have any question. I'm sure the list likes helping you out!
I've had great help so far.
> Right now I started to put some content together into a LaTeX-file > which will be compiled to PDF and plain text and send out later > once its done.
Would you mind sending the finished product to me?
A question to Frank and others - do you mind in what format the newsletter's content is written in? I only have experience in using HTML and AsciiDoc (http://www.methods.co.nz/asciidoc/). I would *much* prefer to use AsciiDoc because it "is a text document format for writing notes, documentation, articles, books, ebooks, slideshows, web pages, man pages and blogs. AsciiDoc files can be translated to many formats including HTML, PDF, EPUB, man page." I know that there are similar tools such as "plain text" markup languages but AsciiDoc is the one with which I have most experience.
-1 for Latex, I know Frank is a Latexpert but they are a bit thin on the ground, so having to do contributions in Latex would be limiting (or would require Frank to do lots of conversion, and we want him to have more time for other things :-).
Yes. Sorry, but I not likely to contribute if I have to learn something like Latex. It's not something I'm using now, nor likely to use any time in the near future so I'm simply not motivated to learn it.
I don't care much about the markup language. LaTeX on our level is not more complicated as writing ReST etc. I guess.
I would prefer not to have to learn something like LaTeX but since there's a Geany plugin available, I'm happy to stick with LaTeX for the moment. As you suggest, Frank, since we're not writing complex documents I don't expect the LaTeX markup used to be very complex. I'll probably be doing a little cut-and-pasting if that's OK.
;) You can have a look at
http://git.geany.org/newsletter/tree/newsletter_1.tex
Maybe its getting interesting at http://git.geany.org/newsletter/tree/newsletter_1.tex#n38
The content already looks good. Well done!
Let's see how it goes. ;)
As an occasional Asciidoc contributor I hate to say this but...
Perhaps the project should stick to one markup language? Geany's documentation is done in reST, a part of Python's docutils which is used to produce the Python docs. (see http://docs.python.org/documenting/index.html ). reST is a "lightweight markup language" quite similar to Asciidoc and as you can see from the Geany help file produces HTML (and others too IIRC).
That's the one I was trying to think of! Thanks, Lex, for reminding me. I included AsciiDoc only as an example. I don't want to complicate things too much so would be happy to use reST. I currently use AsciiDoc for other projects but I see no reason to try to force it upon other people when a similar tool is already in use and doing its job well.
OK. Let's give ReST a try. I guess we will need to have a makefile which is generating the output we need. Who likes to do this? Also I think this should be done after volume 1 has been send to public.
In fact perhaps we should stick with LaTeX for the moment, Frank? Since you have experience with this already, creating the necessary Makefile should be easier than creating one for reST (or is it ReST ?).
Yes, I can do it. I suggest outpout shall be plain text for email newsletter. PDF for FTP and HTML for some homepage, right?
Those options look OK to me. Does anyone have thoughts on how the newsletter might be presented on the Geany web site. Perhaps a page on the wiki with links to the issues in the two formats - PDF and HTML (wiki ?).
Assuming we were using AsciiDoc, we could have a master document which then draws in content from various contributors and is then converted to various formats. This method would make the job of the newsletter's editor a little easier since each piece can be edited separately, then combined into one document.
Anything that simplifies the process is good if it reduces the time required of the editor and contributors. This leads to more contributions and more regular publication.
I'll look into options available via reST. Even if it doesn't offer a "master document" option natively, I'm sure a custom solution could easily be created.
As mentioned: With usage of git there is no real need to have such thing like a master document as its possible to edit without having unsolvable conflicts.
I am using a master document for the Frugalware Linux newsletter for various reasons which probably don't apply to the Geany newsletter. I am comfortable using Git and agree that there's no need at the moment for a master document.
Maybe using a masterdocument would be nice if somebody is working on some content and its not clear which 'release' it will be added. So we could do something like a busstop strategy for newsletter. But this is far away from being needed I guess.
Yes, this is where a master document could be useful. It seems we agree that there's no need for such a document now, but perhaps it will become necessary in the future.
Am 08.02.2011 14:50, schrieb Russell Dickenson:
On 8 February 2011 20:26, Frank Lanitz frank@frank.uvena.de wrote:
Yes, I can do it. I suggest outpout shall be plain text for email newsletter. PDF for FTP and HTML for some homepage, right?
Those options look OK to me. Does anyone have thoughts on how the newsletter might be presented on the Geany web site. Perhaps a page on the wiki with links to the issues in the two formats - PDF and HTML (wiki ?).
Plaintext via email to mailing list. Its the most efficient way to reach the ppl on mailing list.
Cheers, Frank
Le 08/02/2011 14:52, Frank Lanitz a écrit :
Am 08.02.2011 14:50, schrieb Russell Dickenson:
On 8 February 2011 20:26, Frank Lanitz frank@frank.uvena.de wrote:
Yes, I can do it. I suggest outpout shall be plain text for email newsletter. PDF for FTP and HTML for some homepage, right?
I personally don't see a need for a PDF -- though I've nothing against it.
Those options look OK to me. Does anyone have thoughts on how the newsletter might be presented on the Geany web site. Perhaps a page on the wiki with links to the issues in the two formats - PDF and HTML (wiki ?).
Plaintext via email to mailing list. Its the most efficient way to reach the ppl on mailing list.
Agreed, ML's the best :p
However, I wouldn't mind if the newsletter is posted on a website and I get a notification via email (and so need to open a link on my browser) as somebody suggested
Thanks to make this actually happen! I'll try to contribute a bit (as I already promised...) when I find some time to. Though, I currently will probably more be able provide feedback, review and such than real writings.
Cheers, Colomban
On Tue, 08 Feb 2011 15:18:02 +0100, Colomban wrote:
Le 08/02/2011 14:52, Frank Lanitz a écrit :
Am 08.02.2011 14:50, schrieb Russell Dickenson:
On 8 February 2011 20:26, Frank Lanitz frank@frank.uvena.de wrote:
Yes, I can do it. I suggest outpout shall be plain text for email newsletter. PDF for FTP and HTML for some homepage, right?
I personally don't see a need for a PDF -- though I've nothing against it.
Those options look OK to me. Does anyone have thoughts on how the newsletter might be presented on the Geany web site. Perhaps a page on the wiki with links to the issues in the two formats - PDF and HTML (wiki ?).
Plaintext via email to mailing list. Its the most efficient way to reach the ppl on mailing list.
Agreed, ML's the best :p
Unasked, I'll share my two cents: (:D)
I'd suggest to send out good old plain text via mail to this list and at the top or bottom add a link to a fancy HTML version of the same content easily viewable in a web browser.
I'd further suggest to simply put the newsletter as HTML on http://newsletter.geany.org (which I would create if wished) and also link to this site from www.geany.org once a new one is released.
Regards, Enrico
2011/2/9 Enrico Tröger enrico.troeger@uvena.de:
On Tue, 08 Feb 2011 15:18:02 +0100, Colomban wrote:
Le 08/02/2011 14:52, Frank Lanitz a écrit :
Am 08.02.2011 14:50, schrieb Russell Dickenson:
On 8 February 2011 20:26, Frank Lanitz frank@frank.uvena.de wrote:
Yes, I can do it. I suggest outpout shall be plain text for email newsletter. PDF for FTP and HTML for some homepage, right?
I personally don't see a need for a PDF -- though I've nothing against it.
Those options look OK to me. Does anyone have thoughts on how the newsletter might be presented on the Geany web site. Perhaps a page on the wiki with links to the issues in the two formats - PDF and HTML (wiki ?).
Plaintext via email to mailing list. Its the most efficient way to reach the ppl on mailing list.
Agreed, ML's the best :p
Unasked, I'll share my two cents: (:D)
I'd suggest to send out good old plain text via mail to this list and at the top or bottom add a link to a fancy HTML version of the same content easily viewable in a web browser.
I'd further suggest to simply put the newsletter as HTML on http://newsletter.geany.org (which I would create if wished) and also link to this site from www.geany.org once a new one is released.
Regards, Enrico
Those all sound like reasonable options.
Regarding the format in which the newsletter is to be written, this is not (AFAIK) fixed in stone. Frank has started writing in LaTeX and, since he's the only one to make a contribution so far, I'm happy to continue. Once we have the first issue out then we'll revisit the question of source format. It's likely that we would accept contributions in plain text format and mark them up for inclusion in the newsletter.
Frank - do you have a deadline in mind for the first issue?
On Wed, 9 Feb 2011 07:32:53 +1000 Russell Dickenson russelldickenson@gmail.com wrote:
2011/2/9 Enrico Tröger enrico.troeger@uvena.de:
On Tue, 08 Feb 2011 15:18:02 +0100, Colomban wrote:
Le 08/02/2011 14:52, Frank Lanitz a écrit :
Am 08.02.2011 14:50, schrieb Russell Dickenson:
On 8 February 2011 20:26, Frank Lanitz frank@frank.uvena.de wrote:
Yes, I can do it. I suggest outpout shall be plain text for email newsletter. PDF for FTP and HTML for some homepage, right?
I personally don't see a need for a PDF -- though I've nothing against it.
Those options look OK to me. Does anyone have thoughts on how the newsletter might be presented on the Geany web site. Perhaps a page on the wiki with links to the issues in the two formats - PDF and HTML (wiki ?).
Plaintext via email to mailing list. Its the most efficient way to reach the ppl on mailing list.
Agreed, ML's the best :p
Unasked, I'll share my two cents: (:D)
I'd suggest to send out good old plain text via mail to this list and at the top or bottom add a link to a fancy HTML version of the same content easily viewable in a web browser.
I'd further suggest to simply put the newsletter as HTML on http://newsletter.geany.org (which I would create if wished) and also link to this site from www.geany.org once a new one is released.
Regards, Enrico
Those all sound like reasonable options.
Regarding the format in which the newsletter is to be written, this is not (AFAIK) fixed in stone. Frank has started writing in LaTeX and, since he's the only one to make a contribution so far, I'm happy to continue. Once we have the first issue out then we'll revisit the question of source format. It's likely that we would accept contributions in plain text format and mark them up for inclusion in the newsletter.
I agree.
Frank - do you have a deadline in mind for the first issue?
My goal was to send out first upcoming weekend. Even I know its not this many content its a start point I don't want to delay more then needed. But right now I don't have the feeling its done.
Cheers, Frank
On 9 February 2011 09:02, Frank Lanitz frank@frank.uvena.de wrote:
On Wed, 9 Feb 2011 07:32:53 +1000 Russell Dickenson russelldickenson@gmail.com wrote:
2011/2/9 Enrico Tröger enrico.troeger@uvena.de:
On Tue, 08 Feb 2011 15:18:02 +0100, Colomban wrote:
Le 08/02/2011 14:52, Frank Lanitz a écrit :
Am 08.02.2011 14:50, schrieb Russell Dickenson:
On 8 February 2011 20:26, Frank Lanitz frank@frank.uvena.de wrote: > > Yes, I can do it. > I suggest outpout shall be plain text for email newsletter. PDF > for FTP and HTML for some homepage, right?
I personally don't see a need for a PDF -- though I've nothing against it.
Those options look OK to me. Does anyone have thoughts on how the newsletter might be presented on the Geany web site. Perhaps a page on the wiki with links to the issues in the two formats - PDF and HTML (wiki ?).
Plaintext via email to mailing list. Its the most efficient way to reach the ppl on mailing list.
Agreed, ML's the best :p
Unasked, I'll share my two cents: (:D)
I'd suggest to send out good old plain text via mail to this list and at the top or bottom add a link to a fancy HTML version of the same content easily viewable in a web browser.
I'd further suggest to simply put the newsletter as HTML on http://newsletter.geany.org (which I would create if wished) and also link to this site from www.geany.org once a new one is released.
Regards, Enrico
Those all sound like reasonable options.
Regarding the format in which the newsletter is to be written, this is not (AFAIK) fixed in stone. Frank has started writing in LaTeX and, since he's the only one to make a contribution so far, I'm happy to continue. Once we have the first issue out then we'll revisit the question of source format. It's likely that we would accept contributions in plain text format and mark them up for inclusion in the newsletter.
I agree.
Frank - do you have a deadline in mind for the first issue?
My goal was to send out first upcoming weekend. Even I know its not this many content its a start point I don't want to delay more then needed. But right now I don't have the feeling its done.
I have already read through the existing document and Lex's (?) suggested changes and believe it is ready to be published. I won't be able to make a contribution to this issue because I am not available this weekend.
On Wed, 9 Feb 2011 00:02:47 +0100 Frank Lanitz frank@frank.uvena.de wrote:
On Wed, 9 Feb 2011 07:32:53 +1000 Russell Dickenson russelldickenson@gmail.com wrote:
2011/2/9 Enrico Tröger enrico.troeger@uvena.de:
On Tue, 08 Feb 2011 15:18:02 +0100, Colomban wrote:
Le 08/02/2011 14:52, Frank Lanitz a écrit :
Am 08.02.2011 14:50, schrieb Russell Dickenson:
On 8 February 2011 20:26, Frank Lanitz frank@frank.uvena.de wrote: > > Yes, I can do it. > I suggest outpout shall be plain text for email newsletter. > PDF for FTP and HTML for some homepage, right?
I personally don't see a need for a PDF -- though I've nothing against it.
Those options look OK to me. Does anyone have thoughts on how the newsletter might be presented on the Geany web site. Perhaps a page on the wiki with links to the issues in the two formats - PDF and HTML (wiki ?).
Plaintext via email to mailing list. Its the most efficient way to reach the ppl on mailing list.
Agreed, ML's the best :p
Unasked, I'll share my two cents: (:D)
I'd suggest to send out good old plain text via mail to this list and at the top or bottom add a link to a fancy HTML version of the same content easily viewable in a web browser.
I'd further suggest to simply put the newsletter as HTML on http://newsletter.geany.org (which I would create if wished) and also link to this site from www.geany.org once a new one is released.
Regards, Enrico
Those all sound like reasonable options.
Regarding the format in which the newsletter is to be written, this is not (AFAIK) fixed in stone. Frank has started writing in LaTeX and, since he's the only one to make a contribution so far, I'm happy to continue. Once we have the first issue out then we'll revisit the question of source format. It's likely that we would accept contributions in plain text format and mark them up for inclusion in the newsletter.
I agree.
Frank - do you have a deadline in mind for the first issue?
My goal was to send out first upcoming weekend. Even I know its not this many content its a start point I don't want to delay more then needed. But right now I don't have the feeling its done.
Well, I will not be able to catch this. But should be done early this week.
Cheers, Frank
On Tue, 8 Feb 2011 18:20:33 +0100 Enrico Tröger enrico.troeger@uvena.de wrote:
I'd suggest to send out good old plain text via mail to this list and at the top or bottom add a link to a fancy HTML version of the same content easily viewable in a web browser.
I second this.
I'd further suggest to simply put the newsletter as HTML on http://newsletter.geany.org (which I would create if wished) and also link to this site from www.geany.org once a new one is released.
Great. Could you set up the subdomain?
Cheers, Frank
On Wed, 9 Feb 2011 00:04:01 +0100, Frank wrote:
On Tue, 8 Feb 2011 18:20:33 +0100 Enrico Tröger enrico.troeger@uvena.de wrote:
I'd suggest to send out good old plain text via mail to this list and at the top or bottom add a link to a fancy HTML version of the same content easily viewable in a web browser.
I second this.
I'd further suggest to simply put the newsletter as HTML on http://newsletter.geany.org (which I would create if wished) and also link to this site from www.geany.org once a new one is released.
Great. Could you set up the subdomain?
Done. If everything could be as easy as creating a new sub domain...:).
Regards, Enrico
On Wed, 9 Feb 2011 20:59:37 +0100 Enrico Tröger enrico.troeger@uvena.de wrote:
On Wed, 9 Feb 2011 00:04:01 +0100, Frank wrote:
On Tue, 8 Feb 2011 18:20:33 +0100 Enrico Tröger enrico.troeger@uvena.de wrote:
I'd suggest to send out good old plain text via mail to this list and at the top or bottom add a link to a fancy HTML version of the same content easily viewable in a web browser.
I second this.
I'd further suggest to simply put the newsletter as HTML on http://newsletter.geany.org (which I would create if wished) and also link to this site from www.geany.org once a new one is released.
Great. Could you set up the subdomain?
Done. If everything could be as easy as creating a new sub domain...:).
;) Yeep, thats true.
On 9 February 2011 00:18, Colomban Wendling lists.ban@herbesfolles.org wrote:
Le 08/02/2011 14:52, Frank Lanitz a écrit :
Am 08.02.2011 14:50, schrieb Russell Dickenson:
On 8 February 2011 20:26, Frank Lanitz frank@frank.uvena.de wrote:
Yes, I can do it. I suggest outpout shall be plain text for email newsletter. PDF for FTP and HTML for some homepage, right?
I personally don't see a need for a PDF -- though I've nothing against it.
Those options look OK to me. Does anyone have thoughts on how the newsletter might be presented on the Geany web site. Perhaps a page on the wiki with links to the issues in the two formats - PDF and HTML (wiki ?).
Plaintext via email to mailing list. Its the most efficient way to reach the ppl on mailing list.
Agreed, ML's the best :p
However, I wouldn't mind if the newsletter is posted on a website and I get a notification via email (and so need to open a link on my browser) as somebody suggested
Thanks to make this actually happen! I'll try to contribute a bit (as I already promised...) when I find some time to. Though, I currently will probably more be able provide feedback, review and such than real writings.
Reviews and feedback are a very useful contribution. People sometimes forget that. :)
Le 07/02/2011 23:50, Russell Dickenson a écrit :
On 8 February 2011 04:21, Frank Lanitz frank@frank.uvena.de wrote:
On Mon, 7 Feb 2011 12:21:00 +1000 Russell Dickenson russelldickenson@gmail.com wrote:
<snip> >>>> Right now I started to put some content together into a LaTeX-file >>>> which will be compiled to PDF and plain text and send out later >>>> once its done. >>> >>> Would you mind sending the finished product to me? >>> >>> A question to Frank and others - do you mind in what format the >>> newsletter's content is written in? I only have experience in using >>> HTML and AsciiDoc (http://www.methods.co.nz/asciidoc/). I would >>> *much* prefer to use AsciiDoc because it "is a text document >>> format for writing notes, documentation, articles, books, ebooks, >>> slideshows, web pages, man pages and blogs. AsciiDoc files can be >>> translated to many formats including HTML, PDF, EPUB, man page." I >>> know that there are similar tools such as "plain text" markup >>> languages but AsciiDoc is the one with which I have most >>> experience. >> >> -1 for Latex, I know Frank is a Latexpert but they are a bit thin on >> the ground, so having to do contributions in Latex would be limiting >> (or would require Frank to do lots of conversion, and we want him to >> have more time for other things :-). > > Yes. Sorry, but I not likely to contribute if I have to learn > something like Latex. It's not something I'm using now, nor likely to > use any time in the near future so I'm simply not motivated to learn > it.
I don't care much about the markup language. LaTeX on our level is not more complicated as writing ReST etc. I guess.
I would prefer not to have to learn something like LaTeX but since there's a Geany plugin available, I'm happy to stick with LaTeX for the moment. As you suggest, Frank, since we're not writing complex documents I don't expect the LaTeX markup used to be very complex. I'll probably be doing a little cut-and-pasting if that's OK.
I'd personally prefer not to have to write LaTeX since I hardly know it, and I'm not sure we need what LaTeX can give us that something like reST couldn't.
However, since I'll probably not contribute that much (in the near future at least), my POV doesn't matter that much. More a "2¢" then ^^
Cheers, Colomban
Le 07/02/2011 19:21, Frank Lanitz a écrit :
As an occasional Asciidoc contributor I hate to say this but...
Perhaps the project should stick to one markup language? Geany's documentation is done in reST, a part of Python's docutils which is used to produce the Python docs. (see http://docs.python.org/documenting/index.html ). reST is a "lightweight markup language" quite similar to Asciidoc and as you can see from the Geany help file produces HTML (and others too IIRC).
That's the one I was trying to think of! Thanks, Lex, for reminding me. I included AsciiDoc only as an example. I don't want to complicate things too much so would be happy to use reST. I currently use AsciiDoc for other projects but I see no reason to try to force it upon other people when a similar tool is already in use and doing its job well.
OK. Let's give ReST a try. I guess we will need to have a makefile which is generating the output we need. Who likes to do this? Also I think this should be done after volume 1 has been send to public.
I can probably handle this if needed :)
Le 07/02/2011 03:21, Russell Dickenson a écrit :
On 7 February 2011 09:53, Lex Trotman elextr@gmail.com wrote:
Which actually would be a good idea, Geany has a fair bit of "hidden" functionality and a "function of the month" exposing functions of Geany that people tend to forget would be good, I know I keep (re)learning new shortcuts.
And a "Plugin of the month" too :-)
I agree. A feature/plugin focus of the month would be useful. I know that it takes me a while to get to know an application like Geany well. Focusing on a particular feature would make the learning process easier for people like me. As someone who likes to tweak configuration settings, hints on these topics would also be useful I believe.
+1, that's a really good idea Lex :)
On Tue, 08 Feb 2011 15:26:04 +0100, Colomban wrote:
Le 07/02/2011 03:21, Russell Dickenson a écrit :
On 7 February 2011 09:53, Lex Trotman elextr@gmail.com wrote:
Which actually would be a good idea, Geany has a fair bit of "hidden" functionality and a "function of the month" exposing functions of Geany that people tend to forget would be good, I know I keep (re)learning new shortcuts.
And a "Plugin of the month" too :-)
I agree. A feature/plugin focus of the month would be useful. I know that it takes me a while to get to know an application like Geany well. Focusing on a particular feature would make the learning process easier for people like me. As someone who likes to tweak configuration settings, hints on these topics would also be useful I believe.
+1, that's a really good idea Lex :)
Ack, another +1 from me.
Regards, Enrico
2011/2/9 Enrico Tröger enrico.troeger@uvena.de:
On Tue, 08 Feb 2011 15:26:04 +0100, Colomban wrote:
Le 07/02/2011 03:21, Russell Dickenson a écrit :
On 7 February 2011 09:53, Lex Trotman elextr@gmail.com wrote:
Which actually would be a good idea, Geany has a fair bit of "hidden" functionality and a "function of the month" exposing functions of Geany that people tend to forget would be good, I know I keep (re)learning new shortcuts.
And a "Plugin of the month" too :-)
I agree. A feature/plugin focus of the month would be useful. I know that it takes me a while to get to know an application like Geany well. Focusing on a particular feature would make the learning process easier for people like me. As someone who likes to tweak configuration settings, hints on these topics would also be useful I believe.
+1, that's a really good idea Lex :)
Ack, another +1 from me.
Regards, Enrico
Well I'll write something on configuring the build system since it seems to cause some confusion, but it won't be for this issue and I don't guarantee next either
Cheers Lex .
-- Get my GPG key from http://www.uvena.de/pub.asc
Geany mailing list Geany@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany
Hi,
On Mon, 7 Feb 2011 08:24:52 +1000 Russell Dickenson russelldickenson@gmail.com wrote:
On 7 February 2011 03:00, Frank Lanitz frank@frank.uvena.de wrote:
Hi,
Sorry for the late coming back. Somehow I missed this mail ...
On Fri, 21 Jan 2011 22:08:15 +1000 Russell Dickenson russelldickenson@gmail.com wrote:
I think this is a *great* idea and am willing to volunteer as a member of the newsletter team.
Cool. Great to hear.
I'm happy to "give it a go" and will let others judge my work. My time is rather limited at the moment but I believe I could make a useful contribution. I speak (and write) only English, I'm afraid, so I couldn't contribute to translations in any way.
As we should start in English, a native speaker could be a great help beside of contributing content also on spell checking, grammar and stuff.
I'll do my best. :)
In thinking about the format, I wonder if a blog-style format might be better than a regular newsletter. I say this only because a newsletter can be delayed solely because one item is not quite ready. I am the author and editor of the Frugalware Linux newsletter, so I have some experience in this area. For the moment I'll await further details and team members. :)
Well, I'm not sure how this could look like. Can you give a more detailed exampled?
For examples of "my" work for Frugalware Linux, look here - http://www.frugalware.org and click on the links in the newsletter announcements.
The question is: in what format would people like to see the newsletter published? The Ubuntu newsletter is published as a weekly email, for example.
I prefer this way in combination with an optional HTML/PDF-offer.
The Frugalware Linux newsletter is published on a web site in HTML format. Personally I would prefer that the newsletter's content be hosted on a web site instead of sent out via email. The hosted method makes it easier to correct errors which may occur occasionally. Of course we could announce the latest newsletter in the usual Geany ML(s).
I do see such a newsletter more like some kind of a snapshot with no need for an update.
Right now I started to put some content together into a LaTeX-file which will be compiled to PDF and plain text and send out later once its done.
Would you mind sending the finished product to me?
The current status is available at http://git.geany.org/newsletter/ There are still a lot of typos inside I guess. You will need to install a LaTeX-distribution to create a PDF from it.
A question to Frank and others - do you mind in what format the newsletter's content is written in?
Not this much.
I only have experience in using HTML and AsciiDoc (http://www.methods.co.nz/asciidoc/). I would *much* prefer to use AsciiDoc because it "is a text document format for writing notes, documentation, articles, books, ebooks, slideshows, web pages, man pages and blogs. AsciiDoc files can be translated to many formats including HTML, PDF, EPUB, man page." I know that there are similar tools such as "plain text" markup languages but AsciiDoc is the one with which I have most experience.
In Geany context we using a lot of ReST. Personally I prefer LateX ;) I'm not sure about AsciiDoc. Maybe its worth a view but persoanlly I'd prefer to don't have a look onto some other markup language....
Assuming we were using AsciiDoc, we could have a master document which then draws in content from various contributors and is then converted to various formats. This method would make the job of the newsletter's editor a little easier since each piece can be edited separately, then combined into one document.
I don't care much about structure as long its a working one. When using git, its not a problem two people working inside the smae document in most cases differing from edit the whole page with e.g. typical wiki software as Mediawiki.
Thanks for your reply.
Another question to everyone - since I am the only person to have volunteered so far I'm putting my thoughts out for everyone to read. Am I going too far in suggesting formats and tools?
No, its fine :)
Cheers, Frank
Hi friends of Geany,
I've started to work on first version of newsletter. Right now I did it in LaTeX as it was the easiest from my point of view and to be honest I didn't thought about something else until I've already started. Dominic already mentioned to use ReST in future... We will see :)
However, My plan is to finish the first volume during the next so we have some starting point.
You can check the current status at http://git.geany.org/newsletter/ and checkout using git with git clone http://git.geany.org/newsletter
Also there will be a mailing list for commit messages available shortly.
A huge thanks to Enrico for setting up the repository!
Cheers, Frank
On 7 February 2011 12:13, Frank Lanitz frank@frank.uvena.de wrote:
Hi friends of Geany,
I've started to work on first version of newsletter. Right now I did it in LaTeX as it was the easiest from my point of view and to be honest I didn't thought about something else until I've already started. Dominic already mentioned to use ReST in future... We will see :)
However, My plan is to finish the first volume during the next so we have some starting point.
You can check the current status at http://git.geany.org/newsletter/ and checkout using git with git clone http://git.geany.org/newsletter
Also there will be a mailing list for commit messages available shortly.
A huge thanks to Enrico for setting up the repository!
Cheers, Frank
Frank (and Enrico),
Thanks for getting started on this. Since there hadn't been much feedback since I volunteered to help I thought no-one was interested.
As I have said in another thread, I'd like to use reST but I'll try and fit in as best I can. I already use git (although I am not an expert by any means) so I'm happy to work with it.
I'll have a look at the work in progress and perhaps provide feedback here.
On 7 February 2011 12:42, Russell Dickenson russelldickenson@gmail.com wrote:
On 7 February 2011 12:13, Frank Lanitz frank@frank.uvena.de wrote:
Hi friends of Geany,
I've started to work on first version of newsletter. Right now I did it in LaTeX as it was the easiest from my point of view and to be honest I didn't thought about something else until I've already started. Dominic already mentioned to use ReST in future... We will see :)
Oh wow! That already looks great! Now all I need to do is work out what I can contribute. You already seem to have covered everything, Frank.
In summary we have the following topics (so far): * Release announcements - in this case: Geany and Geany Plugins * New plugins * Updates and bug fixes * Geany development
Am 07.02.2011 04:20, schrieb Russell Dickenson:
In summary we have the following topics (so far):
- Release announcements - in this case: Geany and Geany Plugins
- New plugins
- Updates and bug fixes
- Geany development
Yes. I'd like to add some more inside devel section. And of course, further content is welcome :D
Cheers, Frank
Hi Frank,
I get the following error when running Latex->DVI in Geany:
./newsletter_1.tex:24: LaTeX Error: Cannot determine size of graphic in img/geany.png (no BoundingBox)
Cheers Lex
PS As I'm Latex illiterate, all I can do is run it from Geany, the toolchain is only installed to support other tools that use it. Version info is:
This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/Debian)
On 7 February 2011 13:13, Frank Lanitz frank@frank.uvena.de wrote:
Hi friends of Geany,
I've started to work on first version of newsletter. Right now I did it in LaTeX as it was the easiest from my point of view and to be honest I didn't thought about something else until I've already started. Dominic already mentioned to use ReST in future... We will see :)
However, My plan is to finish the first volume during the next so we have some starting point.
You can check the current status at http://git.geany.org/newsletter/ and checkout using git with git clone http://git.geany.org/newsletter
Also there will be a mailing list for commit messages available shortly.
A huge thanks to Enrico for setting up the repository!
Cheers, Frank -- http://frank.uvena.de/en/
Geany mailing list Geany@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany
On 7 February 2011 14:11, Lex Trotman elextr@gmail.com wrote:
Hi Frank,
I get the following error when running Latex->DVI in Geany:
./newsletter_1.tex:24: LaTeX Error: Cannot determine size of graphic in img/geany.png (no BoundingBox)
Cheers Lex
PS As I'm Latex illiterate,
Sigh, generally illiterate as well :-D I didn't notice Latex->PDF as option two on the menu or that Frank said to make a PDF
Cheers Lex
all I can do is run it from Geany, the
toolchain is only installed to support other tools that use it. Version info is:
This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/Debian)
On 7 February 2011 13:13, Frank Lanitz frank@frank.uvena.de wrote:
Hi friends of Geany,
I've started to work on first version of newsletter. Right now I did it in LaTeX as it was the easiest from my point of view and to be honest I didn't thought about something else until I've already started. Dominic already mentioned to use ReST in future... We will see :)
However, My plan is to finish the first volume during the next so we have some starting point.
You can check the current status at http://git.geany.org/newsletter/ and checkout using git with git clone http://git.geany.org/newsletter
Also there will be a mailing list for commit messages available shortly.
A huge thanks to Enrico for setting up the repository!
Cheers, Frank -- http://frank.uvena.de/en/
Geany mailing list Geany@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany
On 7 February 2011 14:31, Lex Trotman elextr@gmail.com wrote:
On 7 February 2011 14:11, Lex Trotman elextr@gmail.com wrote:
Hi Frank,
I get the following error when running Latex->DVI in Geany:
./newsletter_1.tex:24: LaTeX Error: Cannot determine size of graphic in img/geany.png (no BoundingBox)
Cheers Lex
PS As I'm Latex illiterate,
Sigh, generally illiterate as well :-D I didn't notice Latex->PDF as option two on the menu or that Frank said to make a PDF
Cheers Lex
all I can do is run it from Geany, the
toolchain is only installed to support other tools that use it. Version info is:
This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/Debian)
On 7 February 2011 13:13, Frank Lanitz frank@frank.uvena.de wrote:
Hi friends of Geany,
I've started to work on first version of newsletter. Right now I did it in LaTeX as it was the easiest from my point of view and to be honest I didn't thought about something else until I've already started. Dominic already mentioned to use ReST in future... We will see :)
However, My plan is to finish the first volume during the next so we have some starting point.
You can check the current status at http://git.geany.org/newsletter/ and checkout using git with git clone http://git.geany.org/newsletter
Hi Frank,
Nice start :-)
A patch with my lunchtime contribution of some Englishifications attached. Hope I havn't broken any markup.
Cheers Lex
Also there will be a mailing list for commit messages available shortly.
A huge thanks to Enrico for setting up the repository!
Cheers, Frank -- http://frank.uvena.de/en/
Geany mailing list Geany@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany
Am 07.02.2011 04:59, schrieb Lex Trotman:
On 7 February 2011 14:31, Lex Trotman elextr@gmail.com wrote:
On 7 February 2011 14:11, Lex Trotman elextr@gmail.com wrote:
Hi Frank,
I get the following error when running Latex->DVI in Geany:
./newsletter_1.tex:24: LaTeX Error: Cannot determine size of graphic in img/geany.png (no BoundingBox)
Cheers Lex
PS As I'm Latex illiterate,
Sigh, generally illiterate as well :-D I didn't notice Latex->PDF as option two on the menu or that Frank said to make a PDF
Cheers Lex
all I can do is run it from Geany, the
toolchain is only installed to support other tools that use it. Version info is:
This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/Debian)
On 7 February 2011 13:13, Frank Lanitz frank@frank.uvena.de wrote:
Hi friends of Geany,
I've started to work on first version of newsletter. Right now I did it in LaTeX as it was the easiest from my point of view and to be honest I didn't thought about something else until I've already started. Dominic already mentioned to use ReST in future... We will see :)
However, My plan is to finish the first volume during the next so we have some starting point.
You can check the current status at http://git.geany.org/newsletter/ and checkout using git with git clone http://git.geany.org/newsletter
Hi Frank,
Nice start :-)
A patch with my lunchtime contribution of some Englishifications attached. Hope I havn't broken any markup.
Thanks for the patch. Will have a look onto it later today.
Cheers, Frank
On 7 February 2011 19:39, Frank Lanitz frank@frank.uvena.de wrote:
Am 07.02.2011 04:59, schrieb Lex Trotman:
On 7 February 2011 14:31, Lex Trotman elextr@gmail.com wrote:
On 7 February 2011 14:11, Lex Trotman elextr@gmail.com wrote:
Hi Frank,
I get the following error when running Latex->DVI in Geany:
./newsletter_1.tex:24: LaTeX Error: Cannot determine size of graphic in img/geany.png (no BoundingBox)
Cheers Lex
PS As I'm Latex illiterate,
Sigh, generally illiterate as well :-D I didn't notice Latex->PDF as option two on the menu or that Frank said to make a PDF
Cheers Lex
all I can do is run it from Geany, the
toolchain is only installed to support other tools that use it. Version info is:
This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/Debian)
On 7 February 2011 13:13, Frank Lanitz frank@frank.uvena.de wrote:
Hi friends of Geany,
I've started to work on first version of newsletter. Right now I did it in LaTeX as it was the easiest from my point of view and to be honest I didn't thought about something else until I've already started. Dominic already mentioned to use ReST in future... We will see :)
However, My plan is to finish the first volume during the next so we have some starting point.
You can check the current status at http://git.geany.org/newsletter/ and checkout using git with git clone http://git.geany.org/newsletter
Hi Frank,
Nice start :-)
A patch with my lunchtime contribution of some Englishifications attached. Hope I havn't broken any markup.
Thanks for the patch. Will have a look onto it later today.
Cheers, Frank
Ok, BTW congratulations on the neatest best laid out example of a Latex input file that I have ever seen, I could even read it. Maybe I have only seen poor examples but most are hard to read and a real turnoff from using Latex. But I still don't think I would be persuaded to write stuff in Latex, sorry.
Cheers Lex
Geany mailing list Geany@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany
Am 07.02.2011 10:36, schrieb Lex Trotman:
On 7 February 2011 19:39, Frank Lanitz frank@frank.uvena.de wrote:
Am 07.02.2011 04:59, schrieb Lex Trotman:
On 7 February 2011 14:31, Lex Trotman elextr@gmail.com wrote:
On 7 February 2011 14:11, Lex Trotman elextr@gmail.com wrote:
Hi Frank,
I get the following error when running Latex->DVI in Geany:
./newsletter_1.tex:24: LaTeX Error: Cannot determine size of graphic in img/geany.png (no BoundingBox)
Cheers Lex
PS As I'm Latex illiterate,
Sigh, generally illiterate as well :-D I didn't notice Latex->PDF as option two on the menu or that Frank said to make a PDF
Cheers Lex
all I can do is run it from Geany, the
toolchain is only installed to support other tools that use it. Version info is:
This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/Debian)
On 7 February 2011 13:13, Frank Lanitz frank@frank.uvena.de wrote:
Hi friends of Geany,
I've started to work on first version of newsletter. Right now I did it in LaTeX as it was the easiest from my point of view and to be honest I didn't thought about something else until I've already started. Dominic already mentioned to use ReST in future... We will see :)
However, My plan is to finish the first volume during the next so we have some starting point.
You can check the current status at http://git.geany.org/newsletter/ and checkout using git with git clone http://git.geany.org/newsletter
Hi Frank,
Nice start :-)
A patch with my lunchtime contribution of some Englishifications attached. Hope I havn't broken any markup.
Thanks for the patch. Will have a look onto it later today.
Cheers, Frank
Ok, BTW congratulations on the neatest best laid out example of a Latex input file that I have ever seen, I could even read it. Maybe I have only seen poor examples but most are hard to read and a real turnoff from using Latex. But I still don't think I would be persuaded to write stuff in Latex, sorry.
Hehe, I was thinking about to build a sty for the newsletter which is doing the header stuff for you. But in fact, the newsletter is far awy from being good style LaTeX I guess ;)
I assume you did see plain TeX without the LaTeX macros which is even for me a pain ...
Cheers, Frank
Am 07.02.2011 04:31, schrieb Lex Trotman:
On 7 February 2011 14:11, Lex Trotman elextr@gmail.com wrote:
Hi Frank,
I get the following error when running Latex->DVI in Geany:
./newsletter_1.tex:24: LaTeX Error: Cannot determine size of graphic in img/geany.png (no BoundingBox)
Cheers Lex
PS As I'm Latex illiterate,
Sigh, generally illiterate as well :-D I didn't notice Latex->PDF as option two on the menu or that Frank said to make a PDF
Yepp, the std. LaTeX command is compiling it to dvi and its not supporting png.
Cheers, Frank