Hi translators and friends of Geany,
Time is passing by and it's time for doing a new release of Geany! To manage all translation coming in in time we are having a string freeze for upcoming Geany 1.22, which will be release around June, 18th.
The list of changes done for this release is long and so a lot of string have changed or were added. I like to ask all translators to check the translations.
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 2012-06-15. To make it more easy for you I've already uploaded updated versions of the po files (and now this is new) to git master at github. You can either download the direct via web or by cloning the repository from https://github.com/geany/geany
This can be done e.g. with
git clone https://github.com/geany/geany.git
Also at http://i18n.geany.org/ are statistics and daily updated files available.
As mentioned before, we are trying to have all translations complete by 2012-06-15.
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.
Thanks and happy translating ;) Frank
P.S. As we are used to on previous releases also the combined geany-plugins project will have a new stable release. Its currently scheduled two weeks after Geany 1.22 with a string freeze around release date of Geany. If you like to provide also some translation for, it would be much appreciated. ;)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
2012.06.03 11:36, Frank Lanitz rašė:
Hi translators and friends of Geany,
Time is passing by and it's time for doing a new release of Geany! To manage all translation coming in in time we are having a string freeze for upcoming Geany 1.22, which will be release around June, 18th.
The list of changes done for this release is long and so a lot of string have changed or were added. I like to ask all translators to check the translations.
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 2012-06-15. To make it more easy for you I've already uploaded updated versions of the po files (and now this is new) to git master at github. You can either download the direct via web or by cloning the repository from https://github.com/geany/geany
This can be done e.g. with
git clone https://github.com/geany/geany.git
Also at http://i18n.geany.org/ are statistics and daily updated files available.
As mentioned before, we are trying to have all translations complete by 2012-06-15.
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.
Thanks and happy translating ;) Frank
P.S. As we are used to on previous releases also the combined geany-plugins project will have a new stable release. Its currently scheduled two weeks after Geany 1.22 with a string freeze around release date of Geany. If you like to provide also some translation for, it would be much appreciated. ;)
then i sent previous translation update i sent and report about untranslatable strings... these strings still not fixed. for 2 from 3 issues i wrote patch(for third couldn't, because i code in php and python, not in c) in file geany/src/search.c there is line(there are two with same string):
ngettext("Found %d match for "%s".","Found %d matches for "%s".", count), count, search_data.original_text);
that line is translatable, but in application still appears in English. eg. mark some text in geany, then "geany->Search->More->Find usage" in bottom of window appears "Found 6 matches for "x."" but everything is translated and my pot is up-to-date.
attached files: 1. updated Lithuanian geany translation 2. patch to make strings "pos:" and "style:" translatable
- -- gymka GPG ID: 21C70548
Hey,
I'm not sure about the search string problem.
- patch to make strings "pos:" and "style:" translatable
But those two strings are not translatable on purpose. They are only used when Geany was built with debug information enabled and are not meant to be end-user visible.
Regards, Enrico
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
2012.06.03 18:48, Enrico Tröger rašė:
Hey,
I'm not sure about the search string problem.
- patch to make strings "pos:" and "style:" translatable
But those two strings are not translatable on purpose. They are only used when Geany was built with debug information enabled and are not meant to be end-user visible.
1. i builded geany with default options, i didn't enabled anything, so by default everybody see those strings. 2. maybe i changed wrong line, look to geany bottom line there is "line:x/x" col:x sel:x INS TAB mode: Unix(LF) encoding: UTF-8 filetype:x scope:unknwn pos:x style:x" all these are translatable except "pos" and "style". so either by default disable that line or make all strings translatable. it looks bad then 7 strings is translated and two strings are still in english.
- -- gymka GPG ID: 21C70548
On 03/06/12 18:02, gymka wrote:
2012.06.03 18:48, Enrico Tröger rašė:
Hey,
I'm not sure about the search string problem.
- patch to make strings "pos:" and "style:" translatable
But those two strings are not translatable on purpose. They are only used when Geany was built with debug information enabled and are not meant to be end-user visible.
- i builded geany with default options, i didn't enabled anything, so
by default everybody see those strings.
I guess you built Geany from GIT? If so, debug support is enabled automatically. But it is not when built from a normal release tarball.
- maybe i changed wrong line, look to geany bottom line there is
"line:x/x" col:x sel:x INS TAB mode: Unix(LF) encoding: UTF-8 filetype:x scope:unknwn pos:x style:x" all these are translatable except "pos" and "style". so either by default disable that line or make all strings translatable. it looks bad then 7 strings is translated and two strings are still in english.
As said, this is not meant for normal users. Frank already applied your patch. Either he keeps it and all translators have to live with translating two more strings for no real benefit or he reverts it and saves all the others translaters the trouble. Those strings exists for years already and never were translatable, this is nothing new.
Regards, Enrico
On 03/06/2012 17:13, Enrico Tröger wrote:
- i builded geany with default options, i didn't enabled anything, so
by default everybody see those strings.
I guess you built Geany from GIT? If so, debug support is enabled automatically. But it is not when built from a normal release tarball.
- maybe i changed wrong line, look to geany bottom line there is
"line:x/x" col:x sel:x INS TAB mode: Unix(LF) encoding: UTF-8 filetype:x scope:unknwn pos:x style:x" all these are translatable except "pos" and "style". so either by default disable that line or make all strings translatable. it looks bad then 7 strings is translated and two strings are still in english.
As said, this is not meant for normal users. Frank already applied your patch. Either he keeps it and all translators have to live with translating two more strings for no real benefit or he reverts it and saves all the others translaters the trouble. Those strings exists for years already and never were translatable, this is nothing new.
+1, the unnecessary translations should be removed.
Here is new ja.po file
Chikahiro Masami
2012-06-03 (日) の 10:36 +0200 に Frank Lanitz さんは書きました:
Hi translators and friends of Geany,
Time is passing by and it's time for doing a new release of Geany! To manage all translation coming in in time we are having a string freeze for upcoming Geany 1.22, which will be release around June, 18th.
The list of changes done for this release is long and so a lot of string have changed or were added. I like to ask all translators to check the translations.
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 2012-06-15. To make it more easy for you I've already uploaded updated versions of the po files (and now this is new) to git master at github. You can either download the direct via web or by cloning the repository from https://github.com/geany/geany
This can be done e.g. with
git clone https://github.com/geany/geany.git
Also at http://i18n.geany.org/ are statistics and daily updated files available.
As mentioned before, we are trying to have all translations complete by 2012-06-15.
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.
Thanks and happy translating ;) Frank
P.S. As we are used to on previous releases also the combined geany-plugins project will have a new stable release. Its currently scheduled two weeks after Geany 1.22 with a string freeze around release date of Geany. If you like to provide also some translation for, it would be much appreciated. ;)
Geany-i18n mailing list Geany-i18n@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-i18n
On Mon, 04 Jun 2012 17:59:27 +0900 Masami Chikahiro chestnutsburr@sannet.ne.jp wrote:
Here is new ja.po file
I've just pushed it to git master. Thank you very much.
Cheers, Frank
Le 03/06/2012 10:36, Frank Lanitz a écrit :
Hi translators and friends of Geany,
Time is passing by and it's time for doing a new release of Geany! To manage all translation coming in in time we are having a string freeze for upcoming Geany 1.22, which will be release around June, 18th.
Hello everyone,
I'm currently updating the french translation and I have a couple questions about some new strings :
- Should we translate the copyright string in src/about.c ? The "All rights reserved." part may be localized, thought I'm unsure if this really is useful.
- There is a "Goto Field" string in src/toolbar.c:390 that may be incorrect. The string, present in the Customize Toolbar menu, designates the toolbar action for jumping to a line by entering its number. This action is called "Go to Line" everywhere else, so I think this text should be changed to "Go to Line" to match the other strings.
- In src/highlighting.c (lines 1343/1344), I'm not sure I fully understand the meaning of the warning message. Is this warning displayed when the user selected the filetype manually from the menu instead of letting Geany detect it automatically ?
Thanks for this new release and congratulations on the switch to git and github. I'll try to submit a pull request this time instead of sending the full fr.po to the ML. Hopefully I'll do it right :)
-- Jean-Philippe Moal
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
2012.06.07 10:58, Jean-Philippe Moal rašė:
Le 03/06/2012 10:36, Frank Lanitz a écrit :
Hi translators and friends of Geany,
Time is passing by and it's time for doing a new release of Geany! To manage all translation coming in in time we are having a string freeze for upcoming Geany 1.22, which will be release around June, 18th.
Hello everyone,
I'm currently updating the french translation and I have a couple questions about some new strings :
- Should we translate the copyright string in src/about.c ? The
"All rights reserved." part may be localized, thought I'm unsure if this really is useful.
are there programmers which don't speak/code in english? all programming languages are based on english. so maybe we don't need to localize at all?
- -- gymka GPG ID: 21C70548
Hi, I'm attaching the updated Simplified Chinese translation file.
On Thu, Jun 7, 2012 at 5:08 PM, gymka gymka@archlinux.lt wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
2012.06.07 10:58, Jean-Philippe Moal rašė:
Le 03/06/2012 10:36, Frank Lanitz a écrit :
Hi translators and friends of Geany,
Time is passing by and it's time for doing a new release of Geany! To manage all translation coming in in time we are having a string freeze for upcoming Geany 1.22, which will be release around June, 18th.
Hello everyone,
I'm currently updating the french translation and I have a couple questions about some new strings :
- Should we translate the copyright string in src/about.c ? The
"All rights reserved." part may be localized, thought I'm unsure if this really is useful.
are there programmers which don't speak/code in english? all programming languages are based on english. so maybe we don't need to localize at all?
gymka GPG ID: 21C70548
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux)
iQEcBAEBAgAGBQJP0G96AAoJEAVeyH4hxwVIxEYH/1aQPTEIByjemPXF+9+tviqQ AKhUj2IMidtFuieODOB9kWJOhivyJ5BXnMozLEy8zvMwkg0BUnQLRX3ZgZm8Aixt e4NbL75zdfPH1ShnoiqSQwSHniNgZiSZMnWD9hq0iCbNgZ8znTLUy0Aagh35dJgQ hdrEOirsc37H8LibYggPMYEn6tB+m+/mwKTM50xWwrNw8lG6Sp3pxHs+7zwgkavr +eP0t14rFWBKlR7kg8NIZwiNvRS+6gzT2C4KJIwEiVq5AKp7p57tkSRqL60EKfv/ xUmRhsGLTZKWFC8oSAIc9lm4Sp1WOpqTi7KBYq23kZ+OwbMvl8SDJ9Fpwktug/Y= =J5Yw -----END PGP SIGNATURE-----
Geany-i18n mailing list Geany-i18n@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-i18n
On Fri, 8 Jun 2012 09:39:07 +0800 Xhacker Liu liu.dongyuan@gmail.com wrote:
I'm attaching the updated Simplified Chinese translation file.
Thank you very much. I've just added it to master.
Cheers, Frank
On Thu, 07 Jun 2012 12:08:10 +0300 gymka gymka@archlinux.lt wrote:
are there programmers which don't speak/code in english? all programming languages are based on english. so maybe we don't need to localize at all?
I disagree. I think we should also translate such strings as there are people outside which are doing programming work/scripting work without knowing English very well. E.g. I know an 11 year old which is hacking Python as there is no tomorrow - I don't need to say his English isn't as advanced as he can use Geany in LANG=C.
Cheers, Frank
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
2012.06.09 11:40, Frank Lanitz rašė:
On Thu, 07 Jun 2012 12:08:10 +0300 gymka gymka@archlinux.lt wrote:
are there programmers which don't speak/code in english? all programming languages are based on english. so maybe we don't need to localize at all?
I disagree. I think we should also translate such strings as there are people outside which are doing programming work/scripting work without knowing English very well. E.g. I know an 11 year old which is hacking Python as there is no tomorrow - I don't need to say his English isn't as advanced as he can use Geany in LANG=C.
for the record: my message was sarcasm.
- -- gymka GPG ID: 21C70548
Hi,
On Thu, 07 Jun 2012 09:58:28 +0200 Jean-Philippe Moal skateinmars@skateinmars.net wrote:
I'm currently updating the french translation and I have a couple questions about some new strings :
- Should we translate the copyright string in src/about.c ?
The "All rights reserved." part may be localized, thought I'm unsure if this really is useful.
I think as American understanding of copyright differs a lot from European understanding in this part we should translate it in best way so users are able understand this part better.
- There is a "Goto Field" string in src/toolbar.c:390 that may be
incorrect. The string, present in the Customize Toolbar menu, designates the toolbar action for jumping to a line by entering its number. This action is called "Go to Line" everywhere else, so I think this text should be changed to "Go to Line" to match the other strings.
Well, I don't a need to change this in prior of release. Maybe caused by the fact that I don't see a need to change at all at this point. But I'm really without any big emotions here. Both strings suit in my opinion.
- In src/highlighting.c (lines 1343/1344), I'm not sure I fully
understand the meaning of the warning message. Is this warning displayed when the user selected the filetype manually from the menu instead of letting Geany detect it automatically ?
No. This should be part of the new highlighting color code and have been introduced by Nick only a couple of days ago. The commit message was this:
Warn user if current filetype might not support color schemes If the 'default' style isn't set to a named style, then probably the filetype styles have been overridden with manual colors and may not work properly with color schemes. Note: HTML-based filetypes won't show a warning because they don't have a 'default' style (they use 'html_default' instead). This is a simple heuristic, but is worth having to avoid some spurious bug reports when using the color schemes dialog.
Thanks for this new release and congratulations on the switch to git and github. I'll try to submit a pull request this time instead of sending the full fr.po to the ML. Hopefully I'll do it right :)
I'm looking forward to it ;)
Cheers, Frank
Hello,
- There is a "Goto Field" string in src/toolbar.c:390 that may be
incorrect. The string, present in the Customize Toolbar menu, designates the toolbar action for jumping to a line by entering its number. This action is called "Go to Line" everywhere else, so I think this text should be changed to "Go to Line" to match the other strings.
Well, I don't a need to change this in prior of release. Maybe caused by the fact that I don't see a need to change at all at this point. But I'm really without any big emotions here. Both strings suit in my opinion.
I agree this is a bit late to change this. Given the context the current string should be understandable by everyone.
- In src/highlighting.c (lines 1343/1344), I'm not sure I fully
understand the meaning of the warning message. Is this warning displayed when the user selected the filetype manually from the menu instead of letting Geany detect it automatically ?
No. This should be part of the new highlighting color code and have been introduced by Nick only a couple of days ago. The commit message was this:
Warn user if current filetype might not support color schemes If the 'default' style isn't set to a named style, then probably the filetype styles have been overridden with manual colors and may not work properly with color schemes.
I get it now, thanks.
Thanks for this new release and congratulations on the switch to git and github. I'll try to submit a pull request this time instead of sending the full fr.po to the ML. Hopefully I'll do it right :)
I'm looking forward to it ;)
Here it is : https://github.com/geany/geany/pull/46
Looks like it worked :)
-- Jean-Philippe
On Sat, 09 Jun 2012 20:05:11 +0200 Jean-Philippe Moal skateinmars@skateinmars.net wrote:
Here it is : https://github.com/geany/geany/pull/46
I just cherry-picked your commit and will it push shortly.
Cheers, Frank
Hi, Frank.
Attached is the pt-BR.po file. Any problems, please let me know.
Regards, Adrovane.
2012/6/3 Frank Lanitz frank@frank.uvena.de:
Hi translators and friends of Geany,
Time is passing by and it's time for doing a new release of Geany! To manage all translation coming in in time we are having a string freeze for upcoming Geany 1.22, which will be release around June, 18th.
The list of changes done for this release is long and so a lot of string have changed or were added. I like to ask all translators to check the translations.
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 2012-06-15. To make it more easy for you I've already uploaded updated versions of the po files (and now this is new) to git master at github. You can either download the direct via web or by cloning the repository from https://github.com/geany/geany
This can be done e.g. with
git clone https://github.com/geany/geany.git
Also at http://i18n.geany.org/ are statistics and daily updated files available.
As mentioned before, we are trying to have all translations complete by 2012-06-15.
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.
Thanks and happy translating ;) Frank
P.S. As we are used to on previous releases also the combined geany-plugins project will have a new stable release. Its currently scheduled two weeks after Geany 1.22 with a string freeze around release date of Geany. If you like to provide also some translation for, it would be much appreciated. ;)
Geany-i18n mailing list Geany-i18n@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-i18n
On Fri, 15 Jun 2012 20:36:59 -0300 Adrovane Kade adrovane@gmail.com wrote:
Attached is the pt-BR.po file. Any problems, please let me know.
I've added it to master.
Cheers, Frank