Dear translators and friends of Geany,
We are on the final road to Geany 1.36.
In preparation I've just 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 two weeks so we can include it to the next release. Deadline will be 2019-09-26 24:00h CET. I know it's a unusual short period this time but I'm totally sure you will make it ;)
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@jabber.ccc.de or via Mail: look above or some of the mailing lists.
Thanks and happy translating Frank
Hi,
Here is Japanese file updates.
Hi there, the updated es.po file for Spanish is here: https://www.codexion.com/files/l10n/geany/1.36/es.po
Thank you all for the hard work put into this release. -- Lucas Vieites lucas.vieites@gmail.com Blog @ codexion.com http://blog.codexion.com/ LinkedIn http://www.linkedin.com/in/lucasvieites
On Sun, Sep 22, 2019 at 12:00 PM Frank Lanitz frank@frank.uvena.de wrote:
Dear translators and friends of Geany,
We are on the final road to Geany 1.36.
In preparation I've just 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 two weeks so we can include it to the next release. Deadline will be 2019-09-26 24:00h CET. I know it's a unusual short period this time but I'm totally sure you will make it ;)
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@jabber.ccc.de or via Mail: look above or some of the mailing lists.
Thanks and happy translating Frank
I18n mailing list I18n@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/i18n
Am 22.09.19 um 15:47 schrieb Lucas Vieites:
the updated es.po file for Spanish is here: https://www.codexion.com/files/l10n/geany/1.36/es.po
Thank you very much. Just updated git/master.
Cheers, Frank
Hi all,
attached updates to both geany and geany-plugins v1.36 for pt_PT.
I got a msgfmt accelerator error in geany-plugins, at line 1148, msgid 'translator_credits'. May I humbly suggest a replacement of the underscore with a dash?
Many thanks for all your work, Pedro Albuquerque
Em 22/09/2019 às 10:59, Frank Lanitz frank@frank.uvena.de escreveu:
Dear translators and friends of Geany,
We are on the final road to Geany 1.36.
In preparation I've just 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 two weeks so we can include it to the next release. Deadline will be 2019-09-26 24:00h CET. I know it's a unusual short period this time but I'm totally sure you will make it ;)
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@jabber.ccc.de or via Mail: look above or some of the mailing lists.
Thanks and happy translating Frank
--- This email has been checked for viruses by AVG. https://www.avg.com
Am 22.09.19 um 17:52 schrieb Pedro Albuquerque:
I got a msgfmt accelerator error in geany-plugins, at line 1148, msgid 'translator_credits'. May I humbly suggest a replacement of the underscore with a dash?
This is a good point. IIRC this was under discussion anyway but yet not sure about the outcome ;)
.f
translator_credits is a special string in gettext, I'm not sure that it can be replaced. Have a look at https://wiki.gnome.org/TranslationProject/LocalisationGuide for some more background information.
Kind regards,
Le 23/09/2019 à 07:43, Lucas Vieites a écrit :
translator_credits is a special string in gettext, I'm not sure that it can be replaced. Have a look at https://wiki.gnome.org/TranslationProject/LocalisationGuide for some more background information.
AFAIK it's not special per se, it's just used specially inside GNOME. I wonder if there's really a reason why it's not "translator-credits" indeed, because I fail to see any technical reason why this would be problematic and it would solve right away the confusion with accelerators (which is mentioned in the linked document as well).
This said, in our particular case this string is pointless, because it comes from an embedded library but that very string is never displayed, so it could even be dropped.
@Matthew, how would you feel about changing this to translator-credits or another way to prevent the issue at hand, given that IIUC anyway the library doesn't have an upstream anymore?
Cheers, Colomban
Den 23-09-2019 kl. 16:23 skrev Colomban Wendling:
Le 23/09/2019 à 07:43, Lucas Vieites a écrit :
translator_credits is a special string in gettext, I'm not sure that it can be replaced. Have a look at https://wiki.gnome.org/TranslationProject/LocalisationGuide for some more background information.
AFAIK it's not special per se, it's just used specially inside GNOME. I wonder if there's really a reason why it's not "translator-credits" indeed, because I fail to see any technical reason why this would be problematic and it would solve right away the confusion with accelerators (which is mentioned in the linked document as well).
This said, in our particular case this string is pointless, because it comes from an embedded library but that very string is never displayed, so it could even be dropped.
@Matthew, how would you feel about changing this to translator-credits or another way to prevent the issue at hand, given that IIUC anyway the library doesn't have an upstream anymore?
Cheers, Colomban _______________________________________________ I18n mailing list I18n@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/i18n
It seems in the GNOME po file i have "translator-credits" is mostly being used with a few "translator_credits" so maybe they have switched from _ to -.