On 03/06/12 18:22, gymka wrote:
2012.06.03 19:13, Enrico Tröger rašė:
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.
peoples for thousands of years lived in caves, but one day someone decided to build house... if it always was so, not means that is good. count bugs in software which are not reported... they exists, everybody sees them but noone takes theirs precious time and reports it...
for the record: in archlinux repository, geany builded same as i builded from git, so atleast asrchlinux users sees that by default.
I just built Geany on ArchLinux from the official PKGBUILD and the Pos and Style strings are not included in the statusbar. This is obvious, because Geany is not built with debug support by the ArchLinux PKGBUILD.
Sorry, either you are talking about the GIT Geany ArchLinux package (which is built with debug support because it is the GIT version) or you made something wrong :(.
Regards, Enrico
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
2012.06.03 19:44, Enrico Tröger rašė:
On 03/06/12 18:22, gymka wrote:
2012.06.03 19:13, Enrico Tröger rašė:
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.
peoples for thousands of years lived in caves, but one day someone decided to build house... if it always was so, not means that is good. count bugs in software which are not reported... they exists, everybody sees them but noone takes theirs precious time and reports it...
for the record: in archlinux repository, geany builded same as i builded from git, so atleast asrchlinux users sees that by default.
I just built Geany on ArchLinux from the official PKGBUILD and the Pos and Style strings are not included in the statusbar. This is obvious, because Geany is not built with debug support by the ArchLinux PKGBUILD.
Sorry, either you are talking about the GIT Geany ArchLinux package (which is built with debug support because it is the GIT version) or you made something wrong :(.
looks like i all life used git version and not archlinux:) but still better too much translated, then too less. i translated geany from 0, so from translator point of view can say: it's not hard to translate few additional strings. - -- gymka GPG ID: 21C70548
I just built Geany on ArchLinux from the official PKGBUILD and the Pos and Style strings are not included in the statusbar. This is obvious, because Geany is not built with debug support by the ArchLinux PKGBUILD.
Sorry, either you are talking about the GIT Geany ArchLinux package (which is built with debug support because it is the GIT version) or you made something wrong :(.
looks like i all life used git version and not archlinux:) but still better too much translated, then too less. i translated geany from 0, so from translator point of view can say: it's not hard to translate few additional strings.
So it's up to Frank to keep his commit or revert it.
Votes have been made :).
@Frank: in case you don't decide to revert it, you probably should run make update-po again to provide up2date message catalogues to the translators.
Regards, Enrico
Am 03.06.2012 18:59, schrieb Enrico Tröger:
I just built Geany on ArchLinux from the official PKGBUILD and the Pos and Style strings are not included in the statusbar. This is obvious, because Geany is not built with debug support by the ArchLinux PKGBUILD.
Sorry, either you are talking about the GIT Geany ArchLinux package (which is built with debug support because it is the GIT version) or you made something wrong :(.
looks like i all life used git version and not archlinux:) but still better too much translated, then too less. i translated geany from 0, so from translator point of view can say: it's not hard to translate few additional strings.
So it's up to Frank to keep his commit or revert it.
Votes have been made :).
@Frank: in case you don't decide to revert it, you probably should run make update-po again to provide up2date message catalogues to the translators.
I don't see the point to revert the commit as it might could help someone to understand what's going (wr)on(g). The po files have already been updated with d0fe947a6f - at least if I don't mess it up ;)
Cheers, Frank