Dear translators and friends of Geany,
Another few months went by and we are on the last steps for Geany
1.30. In preparation I've updated po-files for Geany core project
inside github repositories and asking you whether you could update
translations, review them or maybe add new languages.
I'd be very happy if you could send a patch, a pull request or single
file with translation to either the geany-i18n mailing list or direct
to me within the next week so we can include it to the next
release. Deadline will be 2017-03-04 24:00hCET.
To get most recent files you could just clone the repositories from
Geany: https://github.com/geany/geany
This can be done e.g. with
git clone https://github.com/geany/geany.git
You can find daily updated po files at http://i18n.geany.org too, which
includes some statistics.
If your language was translated by two or more in past, please double
check directly with them or by pinging me, so we don't need to
translate same things two or three times. Also please feel to ping me
for every question or if you like to start a new translation for an
unsupported language.
If you have any questions, don't hesitate to ping me directly via
IRC: geany @freenode
Jabber/XMPP: frlan(a)jabber.ccc.de
or via Mail: look above or some of the mailing lists.
Thanks and happy translating
Frank
Hello,
Before you release 1.30:
1. Ada parser in ctags directory does not exist.
2. Can you use this one instead? https://github.com/universal-ctags/ctags
3. The universal-ctags does have an Ada parser.
4. Can you make the description field in the pipe format active?
I've tried to produce an ada ctags file but it does not work. I've used the
pipe format.
So I looked (tag manager ) and I could not see an ada parser. Does it
matter?
Thanks.
Hi translators,
As Geany is getting a new major release, the plugins are getting updated
too. This time we are on the way of preparing 1.30.
In preparation I have updated the po-files for Geany-Plugins at github
and asking you whether you could update translations, review them or
maybe add new languages.
As on Geany core, I'd be very happy if you could send a patch, a pull
request or single file with translation to either the geany-i18n mailing
list or direct to me within the next week so we can include it to
the next release. Deadline will be also 2017-03-04 CET.
To get most recent files you could just clone the repositories from
Geany: https://github.com/geany/geany-plugins
This can be done e.g. with
git clone https://github.com/geany/geany-plugins.git
Also at http://i18n.geany.org/plugins are statistics and daily updated
files available.
If you have any questions, don't hesitate to ping me directly via
IRC: geany @freenode (frlan)
Jabber/XMPP: frlan(a)jabber.ccc.de
or via Mail: look above or some of the mailing lists.
Happy translating!
Cheers,
Frank
Hi,
I have a small Geany plugin that needs some settings per Geany project.
Currently, I do it as follows: the user manually writes a special
section in the .geany project file, which my plugin reads as a generic
INI file.
I really like this approach (as a user) because it keeps all Geany
project-related settings in one file.
But is this approach OK in the eyes of Geany core?
--
Vasiliy
Hi all,
I hope you don't mind a quick mention of a little new Geany plugin:
https://github.com/vfaronov/geany-pynav
I've been using it privately for months, and I find that it makes my
Python experience in Geany quite a bit better.
Thanks to Matthew and everyone for GeanyPy, on which this plugin is based.
--
Vasiliy