<newsletter:website> Merge commit 'cafead8e0595a284a4414f9bdcbcbcb54e13b78f' into website
Dominic Hopf
git-noreply at xxxxx
Tue Aug 23 22:06:54 UTC 2011
Updating branch refs/heads/website
to a5054a0a26d96b87ef159e6192b79a89fbebf80f (commit)
from 8ee146e5c651e170c7586201b2a7f330c2ec5ec5 (commit)
commit a5054a0a26d96b87ef159e6192b79a89fbebf80f
Merge: 8ee146e cafead8
Author: Dominic Hopf <dmaphy at fedoraproject.org>
Date: Wed Aug 24 00:02:19 2011 +0200
Merge commit 'cafead8e0595a284a4414f9bdcbcbcb54e13b78f' into website
Conflicts:
Makefile
vol_1/newsletter_1.rst
vol_3/newsletter_3.rst
commit cafead8e0595a284a4414f9bdcbcbcb54e13b78f
Author: Frank Lanitz <frank at frank.uvena.de>
Date: Mon Aug 22 22:24:02 2011 +0200
Applying a patch with a couple of gram. changes and wording changes
provided by Russell
commit a6c05897a911eddcffb8eddc56aa909a8c464514
Author: Frank Lanitz <frank at frank.uvena.de>
Date: Tue Aug 16 22:26:32 2011 +0200
Add preview not yet final version of html and pdf for issue 3
commit 059bdd2da38967419394ca67d55b6d6b1c67abcb
Author: Frank Lanitz <frank at frank.uvena.de>
Date: Tue Aug 16 22:24:51 2011 +0200
Make line wrapping/breaking methods as a section title
commit e5ff0d2935b0d74a580c4456aa178c3e16e2e794
Author: Frank Lanitz <frank at frank.uvena.de>
Date: Tue Aug 16 22:10:11 2011 +0200
Minor reformating of spellcheck section
commit e837872de589aee910defb80a1c4a078a254b99e
Author: Frank Lanitz <frank at frank.uvena.de>
Date: Tue Aug 16 21:44:11 2011 +0200
Even there have been a couple of new plugins none info about by now, so postponed maybe to upcoming newsletter
commit 5d423f5d7c7172c7c386f272337fccc668de5e14
Author: Frank Lanitz <frank at frank.uvena.de>
Date: Tue Aug 16 21:37:49 2011 +0200
Adding some content about the wiki
commit 148d52111ce0b49d7dd2f67d173b896aff702d86
Author: frlan <frank at frank.uvena.de>
Date: Sat Aug 6 10:31:33 2011 +0200
Some gram. updates provided by Russell
commit 31f511e641c44e174a74eebac88c440166cf57f3
Author: Dominic Hopf <dmaphy at fedoraproject.org>
Date: Wed Jul 27 21:33:25 2011 +0200
fix some styling issues with the navion/content listing
commit df8f74f1ee0aa55e03882268a12ec5c21abeeec7
Author: Dominic Hopf <dmaphy at fedoraproject.org>
Date: Tue Jul 26 21:31:50 2011 +0200
correct some RST syntax issues in listings in vol_1
commit 5223c45a375e92fb966f3d74ca13d06a13756366
Author: Frank Lanitz <frank at frank.uvena.de>
Date: Tue Jul 26 20:35:53 2011 +0200
Geany 0.20.1 will not make it until newsletter release.
commit 583c134e46136da31b2d7d827926ecde40e66c7b
Author: Dominic Hopf <dmaphy at fedoraproject.org>
Date: Tue Jul 26 00:27:49 2011 +0200
avoid redundant styling, improve stylings and do some
"code beutifications"
commit d58bfb44edc7991691b91298076ae04043ca4940
Author: Dominic Hopf <dmaphy at fedoraproject.org>
Date: Mon Jul 25 23:23:16 2011 +0200
small styling improvements for the navigation menu
commit 94ef34c771f2525f13a843b1562708544a790c05
Author: Dominic Hopf <dmaphy at fedoraproject.org>
Date: Mon Jul 25 23:01:17 2011 +0200
don't style blockquotes the same as code
commit deda747d4a547d708aa1257b59fbc254d8746174
Author: Dominic Hopf <dmaphy at fedoraproject.org>
Date: Thu Jul 21 14:17:50 2011 +0200
small css cleanups
commit 06679394ba6e975fe6d3b834f25d72df38944be9
Author: Dominic Hopf <dmaphy at fedoraproject.org>
Date: Thu Jul 21 12:40:39 2011 +0200
use the geany.png from img directory
commit 89bb91f9c8852e84843dd0f0700c5b031c24b9e3
Author: Dominic Hopf <dmaphy at fedoraproject.org>
Date: Thu Jul 21 12:33:13 2011 +0200
the newsletters now can all be generated via the make command
commit 415a7bdbcea1e8fe73020b3a2a59ebd76a404073
Author: Dominic Hopf <dmaphy at fedoraproject.org>
Date: Thu Jul 21 12:17:11 2011 +0200
use stylesheets/mainstyle.css to for generated HTML documents
commit e077176ab6cdb571ba02a688590f92453b1a3a09
Author: Dominic Hopf <dmaphy at fedoraproject.org>
Date: Thu Jul 21 12:11:17 2011 +0200
merge stuff from style.css into stylesheets/mainstyle.css,
idea is to have just one css file for all HTML code
commit e31bcbac079b3f31a7a005cb4497f4d5675caca1
Author: Dominic Hopf <dmaphy at fedoraproject.org>
Date: Wed Jul 20 16:43:00 2011 +0200
fix broken links
commit 3b842caf179140ff08f8322721d786da48312e7f
Merge: a0a948f 9ba6881
Author: Frank Lanitz <frank at frank.uvena.de>
Date: Sat Jul 16 18:11:02 2011 +0200
Merge revisited 'build system' for plugins into master branch. Now newsletters are generated via rst and LaTeX is used for PDF-generation
commit 9ba68811067340ac26f76632e6c4246928d38136
Author: Frank Lanitz <frank at frank.uvena.de>
Date: Sat Jul 16 18:06:28 2011 +0200
Refresh PDF version of newsletter issue 2
commit 2e92f9fe3c9ea23fbba5c42864847c2f285c6ff9
Author: Frank Lanitz <frank at frank.uvena.de>
Date: Sat Jul 16 18:01:10 2011 +0200
Refresh generated HTML and PDF for issue 1
commit 28d50565b0169c693f15627659bc7097027f56b7
Author: Frank Lanitz <frank at frank.uvena.de>
Date: Sat Jul 16 17:59:42 2011 +0200
Remove not needed anymore tex file from version control
commit a0a948f4c657af5b8c5544c210f7bc488080170b
Author: Frank Lanitz <frank at frank.uvena.de>
Date: Sat Jul 16 17:52:20 2011 +0200
Add odt-files to ignore list.
Even its a possible way for distribution, we do not publish them officially at the moment
commit 4d7670d7ab3a1d45e0e100a608d419a1f42356dd
Author: Frank Lanitz <frank at frank.uvena.de>
Date: Sat Jul 16 17:50:27 2011 +0200
Some more minor line breaking things
commit 256be04eec950581d5c07d5f85429fae3f27d4e2
Author: Frank Lanitz <frank at frank.uvena.de>
Date: Sat Jul 16 17:48:10 2011 +0200
Rebreak a couple of lines as well as adding some quoting marks
commit df4328acbca8669e90dd977c55b35653e5ff8180
Author: Frank Lanitz <frank at frank.uvena.de>
Date: Sat Jul 16 17:46:22 2011 +0200
Minimal change a usage of LATEX to LaTeX.
commit 6a7dd3060ddf891dd3fa747c59a1f50f0a2647f8
Merge: 5f12698 86b0581
Author: Frank Lanitz <frank at frank.uvena.de>
Date: Sat Jul 16 17:39:49 2011 +0200
Merge master into branch
commit 86b0581c2181253849182aff92d97a1347474401
Author: Frank Lanitz <frank at frank.uvena.de>
Date: Sun Jun 19 22:11:29 2011 +0200
Adding small about this newsletter section based on vol 2
commit 6471704a630841cdb49abe7d0a1ba7d9740eb504
Author: Frank Lanitz <frank at frank.uvena.de>
Date: Sun Jun 19 22:10:21 2011 +0200
Adding a little section about dependency bump of Geany-Plugins 0.21
commit 5f1269833b69c3a00f4b3e905ca96852adbd339c
Author: Frank Lanitz <frank at frank.uvena.de>
Date: Sun Jun 19 22:11:29 2011 +0200
Adding small about this newsletter section based on vol 2
commit d7d1edfa2bb9a97ac43f58d80d684b87da1759b2
Author: Frank Lanitz <frank at frank.uvena.de>
Date: Sun Jun 19 22:10:21 2011 +0200
Adding a little section about dependency bump of Geany-Plugins 0.21
commit e850a37f414260eea16660af040a81ae38cf2f09
Merge: bb38d3d 9621eaa
Author: Frank Lanitz <frank at frank.uvena.de>
Date: Sun Jun 19 22:03:21 2011 +0200
Merge master into branch
commit bb38d3d86077958cc9f17484645116ae8ed6c04c
Author: Frank Lanitz <frank at frank.uvena.de>
Date: Sun Jun 19 22:01:07 2011 +0200
Update of generated pdf and html file
commit 8bee9279a0757cfd5c99bb1d628ef2ef5ea32782
Author: Frank Lanitz <frank at frank.uvena.de>
Date: Sun Jun 19 21:58:56 2011 +0200
Try to fix some quotations
commit 9621eaa3440275b9d103a1024cbfffd19efa43e9
Author: Enrico Tröger <enrico.troeger at uvena.de>
Date: Sun Jun 19 13:14:46 2011 +0200
fix more typos
commit 0f57cee082e98cdf03034f1dbeb0148f49c4dd84
Author: Colomban Wendling <ban at herbesfolles.org>
Date: Sat Jun 18 18:57:05 2011 +0200
And one more typo is gone...
commit 15aad952214ecdef2e7d041abe8bfe70f8a55bf0
Author: Colomban Wendling <ban at herbesfolles.org>
Date: Sat Jun 18 18:54:24 2011 +0200
Fix a typo in my given name and a few whitespace inconsistencies
commit ac492640bf4af42f4bc048f5f2fca43f60573cc4
Author: Colomban Wendling <ban at herbesfolles.org>
Date: Sat Jun 18 18:53:25 2011 +0200
Reword a little sentence about dependency bump
commit fce1eedd62a68c99d7c04c5200f20445438ca4fb
Author: Frank Lanitz <frank at frank.uvena.de>
Date: Sat Jun 18 17:35:44 2011 +0200
Extend ignore list by tex file for newsletter generated with make pdf
commit d434b811f8a81bd770271bad67f3ada6c3a2a39f
Author: Frank Lanitz <frank at frank.uvena.de>
Date: Sat Jun 18 17:23:35 2011 +0200
Issue 1: Fixing list on WebHelper section
commit 1e240b6a58a4f2a8ec8ebdf124578acfa07d585b
Merge: 9dd2a2b e380b3b
Author: frlan <frank at frank.uvena.de>
Date: Sat Jun 18 08:36:32 2011 +0200
Merge current master into branch
Conflicts:
Makefile
commit 9dd2a2b70d8be1719c0ce7b31eab3c8863a826cf
Author: frlan <frank at frank.uvena.de>
Date: Sat Jun 18 08:29:15 2011 +0200
Insert image again
commit 29b9068a043031844f76aa152d3242f5a38e82f1
Author: frlan <frank at frank.uvena.de>
Date: Sat Jun 18 08:25:40 2011 +0200
Remove not anymore used files
commit e380b3b078bd5b82cbe0b35d95985261a076b247
Author: Frank Lanitz <frank at frank.uvena.de>
Date: Mon Jun 13 22:46:24 2011 +0200
Adding some note about bumping glib and gtk dependency on current svn version
commit 2347e21a65352cbab2cb524faf837ad30bdff400
Author: Frank Lanitz <frank at frank.uvena.de>
Date: Mon Jun 13 19:57:32 2011 +0200
Bump Makefile to generate vol 3 as default as we are currently working on
commit ff59e68c2a997899d97291458ed051f459f5297d
Author: frlan <frank at frank.uvena.de>
Date: Mon Jun 13 11:05:18 2011 +0200
Fix list on Geany 0.20 release section
commit 85d04b8bb46957fea0cb741fa8ff68f445a8cd74
Author: frlan <frank at frank.uvena.de>
Date: Sun Jun 12 11:08:30 2011 +0200
Remove hint for newsletter version 1 as it will be also compilable with the script in future
commit 24fcc7e14ec6afd0b65f9b0465097d7766d65498
Author: frlan <frank at frank.uvena.de>
Date: Sun Jun 12 11:07:46 2011 +0200
Started to convert newsletter issue 1 to rst.
Starting with the txt version, this is a version where at least the structure is already fitting.
commit ae08e90b31a1d94c233cae83b44c4e88211a5e3b
Merge: 472b8be f1901c8
Author: Frank Lanitz <frank at frank.uvena.de>
Date: Sat Jun 11 01:31:56 2011 +0200
Merge Colombans changes to make better usage of LaTeX for creating PDF into master
commit 472b8be18364e6d1c2a9904285625b77010252da
Author: Russell Dickenson <russelldickenson at gmail.com>
Date: Mon Jun 6 08:19:30 2011 +1000
Extra content to Feature and Plugin focus sections
modified: newsletter_3.rst
commit 70bbbc3afe2426de9f0bd0d4aa4a08d5b55b15fc
Author: Russell <russelldickenson at gmail.com>
Date: Fri May 27 20:57:09 2011 +1000
Volume 3
* added draft articles about spell checking
* and line breaking/wrapping
new file: ../img/issue3_linewrapping.png
new file: ../img/issue3_spellcheck.png
modified: newsletter_3.rst
commit b3c1951c8c87dada104b1d1f1fc7e2ad57afb308
Author: Dominic Hopf <dmaphy at fedoraproject.org>
Date: Sun Jun 5 16:06:23 2011 +0200
make the newsletter the landing page via symlink
commit f1901c86ee14dc49063c3b68d7e8cb1e02df8a33
Author: Colomban Wendling <ban at herbesfolles.org>
Date: Thu May 26 18:56:11 2011 +0200
Place images on a minipage
Because it looks better to be.
commit 45faa66a66cced087fc0b46ef45a78333b12cd5d
Author: Jonathan Michalon <jonathan at michalon.eu>
Date: Thu May 26 18:24:13 2011 +0200
Arrange images in rst2latex generated newsletters
Signed-off-by: Jonathan Michalon <jonathan at michalon.eu>
Signed-off-by: Colomban Wendling <ban at herbesfolles.org>
commit c5af486f6eca2c890c0961617d30f6f6d7726595
Author: Colomban Wendling <ban at herbesfolles.org>
Date: Wed May 25 17:35:30 2011 +0200
Drop latex preamble
It is not supported by rst2latex < 0.7, and we try to remove it anyway.
commit 101c639085fdd78a3e7a9f16065bb1088ef5709a
Author: Colomban Wendling <ban at herbesfolles.org>
Date: Wed May 25 17:26:35 2011 +0200
Correctly report rst2latex failures
commit da6935e81f8c1ade30d766918926e5e25ae85542
Author: Colomban Wendling <ban at herbesfolles.org>
Date: Tue May 24 20:54:45 2011 +0200
Properly forward commands failure (oops)
commit 731e8034e5dc9d4a52ebf9a29950da4d5761df59
Author: Colomban Wendling <ban at herbesfolles.org>
Date: Tue May 24 17:04:34 2011 +0200
Don't fail if one of the temporary files don't exist
commit bf1361a04b754afd2f2d9e4f7b9a33a1bf6cbde8
Author: Colomban Wendling <ban at herbesfolles.org>
Date: Tue May 24 15:48:34 2011 +0200
Try an alternative way to generate PDF
This is a bit ugly since it post-processes rst2latex output with sed,
but the input template isn't totally flexible enough.
Makefile | 4 +-
README | 3 +-
images/geany.png | Bin 4361 -> 0 bytes
newsletters.php | 2 +-
style.css | 56 ------
stylesheets/mainstyle.css | 137 ++++++++--------
vol_1/newsletter_1.rst | 102 ++++++------
vol_3/newsletter_3.html | 414 +++++++++++++++++++++++++++++++++++++++++++++
vol_3/newsletter_3.pdf | Bin 0 -> 158036 bytes
vol_3/newsletter_3.rst | 241 ++++++++++++++++++++++++++
10 files changed, 777 insertions(+), 182 deletions(-)
diff --git a/Makefile b/Makefile
index bf0c345..8ab5c09 100644
--- a/Makefile
+++ b/Makefile
@@ -32,7 +32,7 @@ clean:
rm -f $(OUTPUTS)
.rst.html:
- rst2html --stylesheet=style.css --toc-top-backlinks $< > $@
+ rst2html --stylesheet=stylesheets/mainstyle.css --toc-top-backlinks $< > $@
.tex.pdf:
maxpasses=5; \
@@ -53,5 +53,5 @@ clean:
rst2odt $< > $@
# extra dependencies we cannot add to suffix rules
-$(OUTPUT_HTML): style.css
+$(OUTPUT_HTML): stylesheets/mainstyle.css
$(OUTPUT_TEX): template.tex rst2latex.sed
diff --git a/README b/README
index 7a8e2f5..56e1174 100644
--- a/README
+++ b/README
@@ -32,8 +32,7 @@ How to compile
Compiling the newsletter is as simple as is couldn't be. Just define an
evironment variable named VOL and run make either wihtout parameters to
compile all, or with one of the parameters html, pdf, latex, odt to compile
-just that file. Note this will only work with Newsletters greater or equal
-than Vol. 2.
+just that file.
Examples:
diff --git a/images/geany.png b/images/geany.png
deleted file mode 100644
index efe5b35..0000000
Binary files a/images/geany.png and /dev/null differ
diff --git a/newsletters.php b/newsletters.php
index d54bb6b..6aeb29a 100644
--- a/newsletters.php
+++ b/newsletters.php
@@ -48,7 +48,7 @@ print '<?xml version="1.0"?>';
<body>
<div id="header">
<a href="./">
- <img src="./images/geany.png" alt="Geany Logo" style="width: 48px; height: 48px; float: left; margin-right: 5%;" /></a>
+ <img src="./img/geany.png" alt="Geany Logo" style="width: 48px; height: 48px; float: left; margin-right: 5%;" /></a>
<h1>Geany Newsletters</h1>
</div>
diff --git a/style.css b/style.css
deleted file mode 100644
index dcc0f90..0000000
--- a/style.css
+++ /dev/null
@@ -1,56 +0,0 @@
-html { font-family: sans-serif; }
-
-
-div.document
-{
- width: 80%;
- margin-left: auto; margin-right: auto;
-}
-
-
-h1 { font-size: 1.4em }
-h2 { font-size: 1.3em }
-h3 { font-size: 1.2em }
-h4 { font-size: 1.1em }
-h5 { font-size: 1.0em }
-h6 { font-size: 0.9em }
-
-
-a:link, a:visited
-{
- color: #9e8100;
- text-decoration: none;
-}
-
-a:hover
-{
- color: #a40000;
- text-decoration: underline;
-}
-
-
-div#contents
-{
- width: 30%; float: left;
- margin-bottom: 10px; margin-right: 20px;
- padding-top: 10px; padding-bottom: 10px;
- padding-left: 1em;
- background-color: #eeeeef;
- font-size: 10pt;
- position: static;
- border-radius: 20px;
- -moz-border-radius: 20px;
- -webkit-border-radius: 20px;
- overflow: hidden;
-}
-
-
-div#contents ul
-{
- list-style-type: none;
- margin-left: -26pt;
- list-style-type: none;
- list-style-position: outside;
- margin-bottom: 1em; margin-left: 0;
- padding-left: 10px;
-}
diff --git a/stylesheets/mainstyle.css b/stylesheets/mainstyle.css
index a9a9783..a146a5d 100644
--- a/stylesheets/mainstyle.css
+++ b/stylesheets/mainstyle.css
@@ -1,111 +1,128 @@
+html { font-family: sans-serif; }
+
+
body
{
font-family: sans-serif;
- width: 80%; height: 600px;
+ width: 80%;
margin-left: auto; margin-right: auto;
margin-top: 2%;
}
-img { border-width: 0; }
-div#header
+h1 { font-size: 1.4em }
+h2 { font-size: 1.3em }
+h3 { font-size: 1.2em }
+h4 { font-size: 1.1em }
+h5 { font-size: 1.0em }
+h6 { font-size: 0.9em }
+
+
+a:link, a:visited
{
- line-height: 48px;
+ color: #9e8100;
+ text-decoration: none;
}
-
-div#navigation
+a:hover
{
- width: 180px; float: left;
- margin-bottom: 10px; margin-right: 20px;
- padding-top: 10px; padding-bottom: 10px;
- padding-left: 1em;
- background-color: #eeeeef;
- font-size: 10pt;
- position: static;
- border-radius: 20px;
- -moz-border-radius: 20px;
- -webkit-border-radius: 20px;
+ color: #a40000;
+ text-decoration: underline;
}
-div#navigation h1
+img { border-width: 0; }
+
+
+hr
{
- font-size: 1em;
+ border-style: solid;
+ border-color: #babdb6;
}
-div#navigation hr
+table
{
- width: 180px;
- margin-left: -1em;
-/*
+ margin-top: 20px;
+}
- margin-right: -4em;
-*/
+table, th, td
+{
+ border-style:1px solid;
+ border-color: #babdb6;
}
-div#navigation ul
+div.document
{
- list-style-type: none;
- list-style-position: outside;
- margin-bottom: 20px; margin-left: 0;
- padding-left: 10px;
+ width: 80%;
+ margin-left: auto; margin-right: auto;
}
-div#navigation ul li
+div#header
{
- margin-bottom: 4px;
+ line-height: 48px;
}
-div#navigation a
+div#contents, div#navigation
{
- display: block;
- text-decoration: none;
+ width: 30%; float: left;
+ margin-bottom: 10px; margin-right: 1em;
+ padding: 1.5em;
+ background-color: #F2F2F3;
+ font-size: 10pt;
+ position: static;
+ border-radius: 20px;
+ -moz-border-radius: 20px;
+ -webkit-border-radius: 20px;
+ overflow: hidden;
}
-
-div#navigation a:link, a:visited
+div#contents ul, div#navigation ul
{
- color: #9e8100;
+ list-style-type: none;
+ list-style-position: outside;
+ margin-bottom: 0.2em;
+ padding-left: 0.8em;
}
+div#contents ul li, div#navigation ul li
+{
+ margin-top: 0.4em;
+}
-div#navigation a:hover
+div#navigation h1
{
- color: #a40000;
+ font-size: 1em;
}
-div#content
+div#navigation hr
{
- overflow: auto;
+ width: 100%;
+ margin: 0; padding: 0;
}
-
-div#content ul
+div#navigation ul li
{
- list-style-position: inside;
+ margin-bottom: 4px;
}
-div#content a:link, a:visited
+div#navigation a
{
- color: #9e8100;
+ display: block;
text-decoration: none;
}
-
-div#content a:hover
+div.section, div#content
{
- color: #a40000;
- text-decoration: underline;
+ overflow: auto;
}
-code, blockquote, pre.literal-block
+code, pre.literal-block
{
display: block;
padding-left: 4px;
@@ -119,24 +136,6 @@ code, blockquote, pre.literal-block
}
-hr
-{
- border-style: solid;
- border-color: #babdb6;
-}
-
-table
-{
- margin-top: 20px;
-}
-
-table, th, td
-{
- border-style:1px solid;
- border-color: #babdb6;
-}
-
-
/*
* This is for the pages with a content section. The heading of the content
* generated from rst2html looks like this:
diff --git a/vol_1/newsletter_1.rst b/vol_1/newsletter_1.rst
index 170d1cc..7460c1b 100644
--- a/vol_1/newsletter_1.rst
+++ b/vol_1/newsletter_1.rst
@@ -20,25 +20,25 @@ the release contained a number of bug fixes as well as improvements and new
features.
Some of the highlights:
- * Improve compatibility with GVfs using GIO to save documents (Alexey Antipov).
- * Fix occasional crashes when closing a modified document and choosing
- "Save".
- * Reorganize Find in Files dialog and add Files pattern to filter search
- results.
- * Show mimetype icon in sidebar Documents list and notebook popup menu
- (Colomban Wendling).
- * Add per-document indent width setting (Jiri Techet).
- * Fix passing quoted arguments when using "Send Selection to". This
- means e.g. sed ’s/\./(dot)/g’ now works.
- * Add alternative color scheme based on Python colors (View-Editor-Color
- Schemes - not all filetypes supported yet).
- * Auto-indent after an HTML/XML line without a closing tag (Eugene Arshinov).
- * Add Forth filetype (Thomas Huth).
- * Add Lisp filetype (Mário Silva).
- * Add Erlang filetype (Taylor Venable).
- * Add translations: kk.
- * Update translations: cs, de, en_GB, es, fi, fr, hu, ja, nl, pt, sl,
- sv, tr, zh_CN.
+* Improve compatibility with GVfs using GIO to save documents (Alexey Antipov).
+* Fix occasional crashes when closing a modified document and choosing
+ "Save".
+* Reorganize Find in Files dialog and add Files pattern to filter search
+ results.
+* Show mimetype icon in sidebar Documents list and notebook popup menu
+ (Colomban Wendling).
+* Add per-document indent width setting (Jiri Techet).
+* Fix passing quoted arguments when using "Send Selection to". This
+ means e.g. sed ’s/\./(dot)/g’ now works.
+* Add alternative color scheme based on Python colors (View-Editor-Color
+ Schemes - not all filetypes supported yet).
+* Auto-indent after an HTML/XML line without a closing tag (Eugene Arshinov).
+* Add Forth filetype (Thomas Huth).
+* Add Lisp filetype (Mário Silva).
+* Add Erlang filetype (Taylor Venable).
+* Add translations: kk.
+* Update translations: cs, de, en_GB, es, fi, fr, hu, ja, nl, pt, sl,
+ sv, tr, zh_CN.
Geany-Plugins 0.20 have been released
=====================================
@@ -65,11 +65,11 @@ WebHelper is a plugin that provides some web development facilities, such
as a web page preview and some debugging tools (web inspector). The plugin
implements the following features:
- * A basic web view, allowing the display of any web page (using WebKit);
- * Possible automatic reloading of the web view upon document saving;
- * A web inspector/debugging tool for the web view’s content (including a
- JavaScript console, a viewer and editor of processed HTML and CSS, a
- network usage analysis tool and many more, thanks to WebKit).
+* A basic web view, allowing the display of any web page (using WebKit);
+* Possible automatic reloading of the web view upon document saving;
+* A web inspector/debugging tool for the web view’s content (including a
+ JavaScript console, a viewer and editor of processed HTML and CSS, a
+ network usage analysis tool and many more, thanks to WebKit).
Updates & Bugfixes
^^^^^^^^^^^^^^^^^^
@@ -78,45 +78,44 @@ Also there have been a lot of bugfixes and updates on plugins. For further
details please check the Release notes and/or the ChangeLog of plugins. A few
selected changes are:
-
GeanyExtraSel
*************
- * Respect "Smart" home key (Geany does now).
- * Fixed Scintilla Shift+movement key conversion of rectangle selection.
- * Virtual spaces support.
- * Per-file column mode.
- * Added "Set Anchor", "Select to Anchor" and "Rectangle Select to Anchor".
+* Respect "Smart" home key (Geany does now).
+* Fixed Scintilla Shift+movement key conversion of rectangle selection.
+* Virtual spaces support.
+* Per-file column mode.
+* Added "Set Anchor", "Select to Anchor" and "Rectangle Select to Anchor".
GeanyGenDoc
***********
- * Bump dependency on CTPL to 0.3.
- * Add a popup menu for common actions in the documentation type selector.
- * Fix indentation of inserted documentation blocs.
- * Documentation type now defaults to Doxygen (rather than nothing).
- * Add policy PASS to completely ignore a symbol.
- * Add basic rules for PHP.
- * Fix build against GTK+ 2.16.
- * Don’t copy the system configuration file to the user’s one when hitting
- "Edit Current Language Configuration", only write it when saving changes.
+* Bump dependency on CTPL to 0.3.
+* Add a popup menu for common actions in the documentation type selector.
+* Fix indentation of inserted documentation blocs.
+* Documentation type now defaults to Doxygen (rather than nothing).
+* Add policy PASS to completely ignore a symbol.
+* Add basic rules for PHP.
+* Fix build against GTK+ 2.16.
+* Don’t copy the system configuration file to the user’s one when hitting
+ "Edit Current Language Configuration", only write it when saving changes.
GeanyLaTeX
**********
- * Move LaTeX-menu to a separate menu inside Geany main menu.
- * Add a feature to auto-capitalize letters on typing the beginning of a
- sentence.
- * Add a way to put an icon for LaTeX-wizard into Geany’s main toolbar.
- * Added a dialog for inserting BibTeX references based on available \*.bib- files.
+* Move LaTeX-menu to a separate menu inside Geany main menu.
+* Add a feature to auto-capitalize letters on typing the beginning of a
+ sentence.
+* Add a way to put an icon for LaTeX-wizard into Geany’s main toolbar.
+* Added a dialog for inserting BibTeX references based on available \*.bib- files.
TreeBrowser
***********
- * Added bookmarks support.
- * Added keybindings support.
- * Added mime type icons in the tree.
- * Many bugfixes and code improvements.
+* Added bookmarks support.
+* Added keybindings support.
+* Added mime type icons in the tree.
+* Many bugfixes and code improvements.
Geany-Development
@@ -211,7 +210,6 @@ chat. You will find us next to the Xfce guys.
Details for this convention can be find on their homepage at
http://chemnitzer.linux-tage.de/2011/
-
Let us introduce you....
========================
@@ -256,9 +254,9 @@ When writing source code or in a markup language, it’s often necessary to mark
one or more lines as a comment. Geany offers several functions from the Edit
-> Format sub-menu which make this very easy:
- * Comment Line(s)
- * Uncomment Line(s)
- * Toggle Line Commentation
+* Comment Line(s)
+* Uncomment Line(s)
+* Toggle Line Commentation
To use these options on a single line, put the cursor on that line and select
the menu option. To use them on a block of code, select the whole block then
diff --git a/vol_3/newsletter_3.html b/vol_3/newsletter_3.html
new file mode 100644
index 0000000..cfb791d
--- /dev/null
+++ b/vol_3/newsletter_3.html
@@ -0,0 +1,414 @@
+<?xml version="1.0" encoding="utf-8" ?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+<meta name="generator" content="Docutils 0.7: http://docutils.sourceforge.net/" />
+<title>Geany Newsletter #3</title>
+<style type="text/css">
+
+html { font-family: sans-serif; }
+
+
+body
+{
+ font-family: sans-serif;
+ width: 80%;
+ margin-left: auto; margin-right: auto;
+ margin-top: 2%;
+}
+
+
+h1 { font-size: 1.4em }
+h2 { font-size: 1.3em }
+h3 { font-size: 1.2em }
+h4 { font-size: 1.1em }
+h5 { font-size: 1.0em }
+h6 { font-size: 0.9em }
+
+
+a:link, a:visited
+{
+ color: #9e8100;
+ text-decoration: none;
+}
+
+a:hover
+{
+ color: #a40000;
+ text-decoration: underline;
+}
+
+
+img { border-width: 0; }
+
+
+hr
+{
+ border-style: solid;
+ border-color: #babdb6;
+}
+
+
+table
+{
+ margin-top: 20px;
+}
+
+table, th, td
+{
+ border-style:1px solid;
+ border-color: #babdb6;
+}
+
+
+div.document
+{
+ width: 80%;
+ margin-left: auto; margin-right: auto;
+}
+
+
+div#header
+{
+ line-height: 48px;
+}
+
+
+div#contents, div#navigation
+{
+ width: 30%; float: left;
+ margin-bottom: 10px; margin-right: 1em;
+ padding: 1.5em;
+ background-color: #F2F2F3;
+ font-size: 10pt;
+ position: static;
+ border-radius: 20px;
+ -moz-border-radius: 20px;
+ -webkit-border-radius: 20px;
+ overflow: hidden;
+}
+
+div#contents ul, div#navigation ul
+{
+ list-style-type: none;
+ list-style-position: outside;
+ margin-bottom: 0.2em;
+ padding-left: 0.8em;
+}
+
+div#contents ul li, div#navigation ul li
+{
+ margin-top: 0.4em;
+}
+
+div#navigation h1
+{
+ font-size: 1em;
+}
+
+
+div#navigation hr
+{
+ width: 100%;
+ margin: 0; padding: 0;
+}
+
+div#navigation ul li
+{
+ margin-bottom: 4px;
+}
+
+
+div#navigation a
+{
+ display: block;
+ text-decoration: none;
+}
+
+div.section, div#content
+{
+ overflow: auto;
+}
+
+code, pre.literal-block
+{
+ display: block;
+ padding-left: 4px;
+ margin-left: 25px; margin-top: 5px;
+ font-family: monospace;
+ background-color: #eeeeef;
+ border-left-width: 2px; border-right-width: 0;
+ border-top-width: 0; border-bottom-width: 0;
+ border-style: solid; border-color: #babdb6;
+ overflow-x: auto;
+}
+
+
+/*
+ * This is for the pages with a content section. The heading of the content
+ * generated from rst2html looks like this:
+ * <p class="topic-title first">
+ * Contents
+ * </p>
+ * So we format it as general h3 headers look like in the browser (tested with
+ * Midori, Firefox and Opera, all work fine).
+ * FIXME: ideally the mentioned code block should be a h3 header instead
+ */
+p.topic-title
+{
+ font-size: 1.17em;
+ font-weight: bold;
+ margin: 1em 0px;
+}
+
+
+div#footer
+{
+ clear: both;
+ text-align: center;
+ font-size: smaller;
+ margin-top: 3em;
+}
+
+</style>
+</head>
+<body>
+<div class="document" id="geany-newsletter-3">
+<h1 class="title">Geany Newsletter #3</h1>
+
+<div class="contents topic" id="contents">
+<p class="topic-title first">Contents</p>
+<ul class="simple">
+<li><a class="reference internal" href="#about-geany" id="id1">About Geany</a></li>
+<li><a class="reference internal" href="#geany-development" id="id2">Geany Development</a><ul>
+<li><a class="reference internal" href="#bumping-dependencies-for-gtk2-and-glib" id="id3">Bumping dependencies for GTK2 and GLib</a></li>
+</ul>
+</li>
+<li><a class="reference internal" href="#plugins" id="id4">Plugins</a><ul>
+<li><a class="reference internal" href="#bumping-dependencies-for-geany-plugins-project-at-geany-0-21-and-gtk2-2-12" id="id5">Bumping dependencies for Geany-Plugins project at Geany 0.21 and GTK2 2.12</a></li>
+</ul>
+</li>
+<li><a class="reference internal" href="#geany-universe" id="id6">Geany Universe</a><ul>
+<li><a class="reference internal" href="#new-geany-wiki" id="id7">New Geany Wiki</a></li>
+</ul>
+</li>
+<li><a class="reference internal" href="#let-us-introduce-you" id="id8">Let us introduce you...</a><ul>
+<li><a class="reference internal" href="#plugin-focus" id="id9">Plugin Focus</a><ul>
+<li><a class="reference internal" href="#spell-check" id="id10">Spell Check</a></li>
+</ul>
+</li>
+<li><a class="reference internal" href="#feature-focus" id="id11">Feature Focus</a><ul>
+<li><a class="reference internal" href="#line-breaking-vs-line-wrapping" id="id12">Line Breaking vs Line Wrapping</a><ul>
+<li><a class="reference internal" href="#line-breaking" id="id13">Line Breaking</a></li>
+<li><a class="reference internal" href="#line-wrapping" id="id14">Line Wrapping</a></li>
+</ul>
+</li>
+</ul>
+</li>
+</ul>
+</li>
+<li><a class="reference internal" href="#people-behind-geany-interview" id="id15">People behind Geany -- Interview</a><ul>
+<li><a class="reference internal" href="#columban-wendling" id="id16">Columban Wendling</a></li>
+</ul>
+</li>
+<li><a class="reference internal" href="#about-this-newsletter" id="id17">About this newsletter</a></li>
+</ul>
+</div>
+<div class="section" id="about-geany">
+<h1><a class="toc-backref" href="#contents">About Geany</a></h1>
+<p>Geany is a small and lightweight Integrated Development Environment.
+It was developed to provide a small and fast IDE, which has only a
+few dependencies from other packages. Another goal was to be as
+independent as possible from a special Desktop Environment like KDE
+or GNOME - Geany only requires the GTK2 runtime libraries.</p>
+<p>More information about Geany can be found at
+<a class="reference external" href="http://www.geany.org/">geany.org</a>.</p>
+</div>
+<div class="section" id="geany-development">
+<h1><a class="toc-backref" href="#contents">Geany Development</a></h1>
+<div class="section" id="bumping-dependencies-for-gtk2-and-glib">
+<h2><a class="toc-backref" href="#contents">Bumping dependencies for GTK2 and GLib</a></h2>
+<p>Starting with SVN r5839 Geany depends on GTK2 >= 2.12 and GLib >= 2.16 to
+make use of some new features introduced with these releases and to avoid
+maintaining duplicate code and complicated #ifdef structures.</p>
+</div>
+</div>
+<div class="section" id="plugins">
+<h1><a class="toc-backref" href="#contents">Plugins</a></h1>
+<div class="section" id="bumping-dependencies-for-geany-plugins-project-at-geany-0-21-and-gtk2-2-12">
+<h2><a class="toc-backref" href="#contents">Bumping dependencies for Geany-Plugins project at Geany 0.21 and GTK2 2.12</a></h2>
+<p>Starting with SVN 2095 the general section of the combined Geany-Plugins
+project depends on Geany 0.21 and similarly Geany depends on GTK2 >= 2.12.</p>
+</div>
+</div>
+<div class="section" id="geany-universe">
+<h1><a class="toc-backref" href="#contents">Geany Universe</a></h1>
+<div class="section" id="new-geany-wiki">
+<h2><a class="toc-backref" href="#contents">New Geany Wiki</a></h2>
+<p>Several weeks ago the Geany wiki was created, in which interesting
+facts around Geany can be collected. Some pages are still empty and
+some topics might be missing, but a good start has been made. Check
+out the pages at <a class="reference external" href="http://wiki.geany.org/">wiki.geany.org</a>. Please
+contribute whatever you can, including your favorite snippets, color
+schemes etc.</p>
+</div>
+</div>
+<div class="section" id="let-us-introduce-you">
+<h1><a class="toc-backref" href="#contents">Let us introduce you...</a></h1>
+<p>This section is intended to introduce particular plugins or features
+on a regular basis.</p>
+<div class="section" id="plugin-focus">
+<h2><a class="toc-backref" href="#contents">Plugin Focus</a></h2>
+<div class="section" id="spell-check">
+<h3><a class="toc-backref" href="#contents">Spell Check</a></h3>
+<p>Although Geany is primarily an editor aimed at programming tasks,
+it's often used to write plain text. All of us would like to think
+that we can spell correctly but, especially for foreign words, a
+little help is always welcome: Geany's Spell Check plugin can help,
+either checking on demand or as you type.</p>
+<p>To check the spelling of the current document on demand, select
+Tools > Spell Check > [language] from the main menu. If you often
+use this feature consider creating a keyboard shortcut to make
+activating it easier.</p>
+<p>In case you would prefer to have your spelling checked immediately,
+enable the "Check spelling while typing" option in the plugin's
+preferences: Edit > Plugin Preferences > Spell Check.</p>
+<p>The default language used by Spell Check is configured in Spell
+Check's preferences.</p>
+<img alt="../img/issue3_spellcheck.png" src="../img/issue3_spellcheck.png" />
+<p>The Spell Check plugin can offer suggestions for misspelled words in
+the Message window, in the context menu or both. Choose whichever
+option suits you best by checking the options in the plugin's
+preferences.</p>
+<p>Any suspect words are marked with a red squiggly underline. To
+correct these, right-click on them and highlight the "Spelling
+Suggestions" item in the context menu. From there you can either
+select from a list of suggested words, add the word to your personal
+dictionary or ignore it. You can install extra dictionaries in
+Myspell format which is especially useful if you're often using
+words which are not in a standard dictionary.</p>
+</div>
+</div>
+<div class="section" id="feature-focus">
+<h2><a class="toc-backref" href="#contents">Feature Focus</a></h2>
+<div class="section" id="line-breaking-vs-line-wrapping">
+<h3><a class="toc-backref" href="#contents">Line Breaking vs Line Wrapping</a></h3>
+<p>In the Document menu are check boxes Line Breaking and Line
+Wrapping. Although their names are similar, they behave differently.</p>
+<div class="section" id="line-breaking">
+<h4><a class="toc-backref" href="#contents">Line Breaking</a></h4>
+<p>When the Line Breaking option is enabled and you type a word past
+the "Line breaking column" (set in Preferences), Geany will input a
+carriage return at the end of the line and put the cursor on the
+line below. This option is best used with plain text files when you
+you want to keep every line to a maximum length. It's not
+recommended for code since you might not notice the line break occur
+and later have to debug the result.</p>
+<p>Line Breaking is activated only when you move the cursor past the
+"Line breaking column" while editing. This means that an already
+long line will simply get longer if you add text before the "Line
+breaking column". When this happens you can use the "Reflow
+Lines/Block" function (in the Edit > Format menu) to adjust all
+lines so that they're within the line breaking column. Line Breaking
+must be enabled per document via the menu option Document > Line
+Breaking.</p>
+</div>
+<div class="section" id="line-wrapping">
+<h4><a class="toc-backref" href="#contents">Line Wrapping</a></h4>
+<p>The Line Wrapping option is similar to Line Breaking but the lines
+are only wrapped visually; no carriage returns or line feeds are
+added. This option is best used when you want to be able to see the
+entire file within the current window. So that it's obvious which
+lines have been wrapped, a visual indicator is added to the end of
+each wrapped line. Line Wrapping is very CPU-intensive and can slow
+down Geany if it's enabled while editing a very large file.</p>
+<p>If you prefer to have Line Wrapping enabled by default, there is an
+option for this in the Preferences dialog box Editor > Features.
+With this option enabled, you can disable Line Wrapping via the menu
+option Document > Line Wrapping.</p>
+<img alt="../img/issue3_linewrapping.png" src="../img/issue3_linewrapping.png" />
+</div>
+</div>
+</div>
+</div>
+<div class="section" id="people-behind-geany-interview">
+<h1><a class="toc-backref" href="#contents">People behind Geany -- Interview</a></h1>
+<p>This is the first in a series of interviews with Geany's
+contributors: core developers, plugin developers, translators, wiki
+maintainers and any other job we can think of. The purpose of the
+interviews is to get to know each of these people a little better:
+their hopes, dreams, plans and favourite Geany plugin.</p>
+<div class="section" id="columban-wendling">
+<h2><a class="toc-backref" href="#contents">Columban Wendling</a></h2>
+<p>Thank you to Colomban Wendling for agreeing to an interview and
+congratulations for being the very first. Now on to the questions...</p>
+<p><em>What motivates you to develop Geany?</em></p>
+<blockquote>
+I use Geany on a daily basis, so I'm concerned about its
+development and improvement. I'm also happy to give back a
+little bit of all the good Geany given me through the years I
+used it :) And don't be silly: the FAME! :D</blockquote>
+<p><em>Why do you develop for free instead of devoting this time to paid
+projects?</em></p>
+<blockquote>
+<p>Philosophy, naivety... Actually I don't "develop for free" if it
+only means "without being paid", I develop for free "as in
+freedom" software because I like the ideology behind it. Not
+being paid is only a concern in the way I need to do some other
+stuff beside to get money in.</p>
+<p>What I probably prefer in free software is the fact one can
+learn from reading the code. It was a great source of help and
+knowledge when I started learning programming, and it still is.
+A related thing is the ability to modify the software to better
+fit my needs, or simply to fix a bug that concerns me. It serves
+me from time to time (once I discover an annoying bug ^^) and
+allows me to send back the fix to upstream developers, hopefully
+helping other users.</p>
+<p>I won't give all the philosophy behind free software, I think
+you've got my point :)</p>
+</blockquote>
+<p><em>Do you do development on other projects that are of interest to you?</em></p>
+<blockquote>
+Not really beside my personal projects. As said above, I send
+patches from time to time to developers of software I use, but
+I'm not really involved in any other project than Geany.</blockquote>
+<p><em>Do you have a favourite Geany feature and if so, what is it?</em></p>
+<blockquote>
+Most probably the tag completion; but also that almost
+everything is configurable to fit ones needs.</blockquote>
+<p><em>Do you have a favourite Geany plugin and if so, what is it?</em></p>
+<blockquote>
+If I'd not fear to sound selfish, I'd say GeanyGenDoc :D
+Otherwise, SpellCheck without a doubt.</blockquote>
+<p><em>What do you do when you're not developing Geany?</em></p>
+<blockquote>
+I continue studying programming, or work on personal projects
+though it's almost the same thing.</blockquote>
+<p><em>What do you use Geany for?</em></p>
+<blockquote>
+Every one of my programming tasks, and some other text editing.</blockquote>
+<p><em>Do you use any editors other than Geany? (Of course the answer here
+should be "Absolutely not!" but I'm asking it anyway. :)</em></p>
+<blockquote>
+I use Nano for commit messages and administration tasks I need
+to do as root, but for all serious text editing I use Geany.</blockquote>
+<p><em>In which environments do you use Geany?</em></p>
+<blockquote>
+GNU/Linux (with GNOME), and occasionally Windows (but only when
+I'm forced to use Windows).</blockquote>
+</div>
+</div>
+<div class="section" id="about-this-newsletter">
+<h1><a class="toc-backref" href="#contents">About this newsletter</a></h1>
+<p>This newsletter has been created in cooperation by people from
+Geany's international community. Contributors to this newsletter and
+the infrastructure behind it, ordered by alphabet:</p>
+<p>Colomban Wendling,
+Enrico Tröger,
+Frank Lanitz,
+Russell Dickenson</p>
+</div>
+</div>
+</body>
+</html>
diff --git a/vol_3/newsletter_3.pdf b/vol_3/newsletter_3.pdf
new file mode 100644
index 0000000..ccd5c42
Binary files /dev/null and b/vol_3/newsletter_3.pdf differ
diff --git a/vol_3/newsletter_3.rst b/vol_3/newsletter_3.rst
new file mode 100644
index 0000000..08b7ecc
--- /dev/null
+++ b/vol_3/newsletter_3.rst
@@ -0,0 +1,241 @@
+Geany Newsletter #3
+-------------------
+
+.. contents::
+
+About Geany
+===========
+
+Geany is a small and lightweight Integrated Development Environment.
+It was developed to provide a small and fast IDE, which has only a
+few dependencies from other packages. Another goal was to be as
+independent as possible from a special Desktop Environment like KDE
+or GNOME - Geany only requires the GTK2 runtime libraries.
+
+More information about Geany can be found at
+`geany.org <http://www.geany.org/>`_.
+
+
+
+Geany Development
+=================
+
+Bumping dependencies for GTK2 and GLib
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Starting with SVN r5839 Geany depends on GTK2 >= 2.12 and GLib >= 2.16 to
+make use of some new features introduced with these releases and to avoid
+maintaining duplicate code and complicated #ifdef structures.
+
+
+Plugins
+=======
+
+Bumping dependencies for Geany-Plugins project at Geany 0.21 and GTK2 2.12
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Starting with SVN 2095 the general section of the combined Geany-Plugins
+project depends on Geany 0.21 and similarly Geany depends on GTK2 >= 2.12.
+
+
+Geany Universe
+==============
+
+New Geany Wiki
+^^^^^^^^^^^^^^
+
+Several weeks ago the Geany wiki was created, in which interesting
+facts around Geany can be collected. Some pages are still empty and
+some topics might be missing, but a good start has been made. Check
+out the pages at `wiki.geany.org <http://wiki.geany.org/>`_. Please
+contribute whatever you can, including your favorite snippets, color
+schemes etc.
+
+
+Let us introduce you...
+=======================
+
+This section is intended to introduce particular plugins or features
+on a regular basis.
+
+
+Plugin Focus
+^^^^^^^^^^^^
+
+Spell Check
+***********
+
+Although Geany is primarily an editor aimed at programming tasks,
+it's often used to write plain text. All of us would like to think
+that we can spell correctly but, especially for foreign words, a
+little help is always welcome: Geany's Spell Check plugin can help,
+either checking on demand or as you type.
+
+To check the spelling of the current document on demand, select
+Tools > Spell Check > [language] from the main menu. If you often
+use this feature consider creating a keyboard shortcut to make
+activating it easier.
+
+In case you would prefer to have your spelling checked immediately,
+enable the "Check spelling while typing" option in the plugin's
+preferences: Edit > Plugin Preferences > Spell Check.
+
+The default language used by Spell Check is configured in Spell
+Check's preferences.
+
+.. image:: ../img/issue3_spellcheck.png
+
+The Spell Check plugin can offer suggestions for misspelled words in
+the Message window, in the context menu or both. Choose whichever
+option suits you best by checking the options in the plugin's
+preferences.
+
+Any suspect words are marked with a red squiggly underline. To
+correct these, right-click on them and highlight the "Spelling
+Suggestions" item in the context menu. From there you can either
+select from a list of suggested words, add the word to your personal
+dictionary or ignore it. You can install extra dictionaries in
+Myspell format which is especially useful if you're often using
+words which are not in a standard dictionary.
+
+
+Feature Focus
+^^^^^^^^^^^^^
+
+Line Breaking vs Line Wrapping
+******************************
+
+In the Document menu are check boxes Line Breaking and Line
+Wrapping. Although their names are similar, they behave differently.
+
+Line Breaking
+#############
+
+When the Line Breaking option is enabled and you type a word past
+the "Line breaking column" (set in Preferences), Geany will input a
+carriage return at the end of the line and put the cursor on the
+line below. This option is best used with plain text files when you
+you want to keep every line to a maximum length. It's not
+recommended for code since you might not notice the line break occur
+and later have to debug the result.
+
+Line Breaking is activated only when you move the cursor past the
+"Line breaking column" while editing. This means that an already
+long line will simply get longer if you add text before the "Line
+breaking column". When this happens you can use the "Reflow
+Lines/Block" function (in the Edit > Format menu) to adjust all
+lines so that they're within the line breaking column. Line Breaking
+must be enabled per document via the menu option Document > Line
+Breaking.
+
+Line Wrapping
+#############
+
+The Line Wrapping option is similar to Line Breaking but the lines
+are only wrapped visually; no carriage returns or line feeds are
+added. This option is best used when you want to be able to see the
+entire file within the current window. So that it's obvious which
+lines have been wrapped, a visual indicator is added to the end of
+each wrapped line. Line Wrapping is very CPU-intensive and can slow
+down Geany if it's enabled while editing a very large file.
+
+If you prefer to have Line Wrapping enabled by default, there is an
+option for this in the Preferences dialog box Editor > Features.
+With this option enabled, you can disable Line Wrapping via the menu
+option Document > Line Wrapping.
+
+.. image:: ../img/issue3_linewrapping.png
+
+
+People behind Geany -- Interview
+=================================
+
+This is the first in a series of interviews with Geany's
+contributors: core developers, plugin developers, translators, wiki
+maintainers and any other job we can think of. The purpose of the
+interviews is to get to know each of these people a little better:
+their hopes, dreams, plans and favourite Geany plugin.
+
+Columban Wendling
+^^^^^^^^^^^^^^^^^
+
+Thank you to Colomban Wendling for agreeing to an interview and
+congratulations for being the very first. Now on to the questions...
+
+
+*What motivates you to develop Geany?*
+
+ I use Geany on a daily basis, so I'm concerned about its
+ development and improvement. I'm also happy to give back a
+ little bit of all the good Geany given me through the years I
+ used it :) And don't be silly: the FAME! :D
+
+*Why do you develop for free instead of devoting this time to paid
+projects?*
+
+ Philosophy, naivety... Actually I don't "develop for free" if it
+ only means "without being paid", I develop for free "as in
+ freedom" software because I like the ideology behind it. Not
+ being paid is only a concern in the way I need to do some other
+ stuff beside to get money in.
+
+ What I probably prefer in free software is the fact one can
+ learn from reading the code. It was a great source of help and
+ knowledge when I started learning programming, and it still is.
+ A related thing is the ability to modify the software to better
+ fit my needs, or simply to fix a bug that concerns me. It serves
+ me from time to time (once I discover an annoying bug ^^) and
+ allows me to send back the fix to upstream developers, hopefully
+ helping other users.
+
+ I won't give all the philosophy behind free software, I think
+ you've got my point :)
+
+*Do you do development on other projects that are of interest to you?*
+
+ Not really beside my personal projects. As said above, I send
+ patches from time to time to developers of software I use, but
+ I'm not really involved in any other project than Geany.
+
+*Do you have a favourite Geany feature and if so, what is it?*
+
+ Most probably the tag completion; but also that almost
+ everything is configurable to fit ones needs.
+
+*Do you have a favourite Geany plugin and if so, what is it?*
+
+ If I'd not fear to sound selfish, I'd say GeanyGenDoc :D
+ Otherwise, SpellCheck without a doubt.
+
+*What do you do when you're not developing Geany?*
+
+ I continue studying programming, or work on personal projects
+ though it's almost the same thing.
+
+*What do you use Geany for?*
+
+ Every one of my programming tasks, and some other text editing.
+
+*Do you use any editors other than Geany? (Of course the answer here
+should be "Absolutely not!" but I'm asking it anyway. :)*
+
+ I use Nano for commit messages and administration tasks I need
+ to do as root, but for all serious text editing I use Geany.
+
+*In which environments do you use Geany?*
+
+ GNU/Linux (with GNOME), and occasionally Windows (but only when
+ I'm forced to use Windows).
+
+
+About this newsletter
+=====================
+
+This newsletter has been created in cooperation by people from
+Geany's international community. Contributors to this newsletter and
+the infrastructure behind it, ordered by alphabet:
+
+Colomban Wendling,
+Enrico Tröger,
+Frank Lanitz,
+Russell Dickenson
More information about the Newsletter-Commits
mailing list