The problem with the status bar is that it is freeform text, the user can type
anything in it, so there is no way to translate it.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3620#issuecomment-1773785633
You are receiving this because you are
No but i tried with -c now and then i get the translated string.
But does they mean that all users have to manually figure out how to get a
fresh configuration when changes are made to the translation?
Then if i switch between languages like if i want to test Geany in danish and
afterwards in
@scootergrisen did you use a fresh configuration? C.f.
> It works for me, but note that this is the default value for a preference, so
> it won't ever be updated on an existing installation. Try with `geany -c
> /tmp/nonexistant`, you should see the translation.
You should also be able to
I downloaded and installed https://download.geany.org/geany-2.0_setup.exe again
and that fixes missing translations like
https://github.com/geany/geany/issues/3621 but the status bar is still partly
in english.
`line: %l / %L col: %c sel: %s %w %t %mEOL: %M
The Geany Windows installer has been replaced with updated translation files
(binaries are untouched).
@scootergrisen could you test the installer again?
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3620#issuecomment-1773418145
You are receiving
I should have done as well.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3620#issuecomment-1773206928
You are receiving this because you are subscribed to this thread.
Message ID:
> @techee might be the macOS builds affected by this as well?
I used meson for Geany itself (not usre if it suffers from the same problem)
and autotools for plugins. In any case I made a completely clean build from
release tarballs so I hope it's alright.
--
Reply to this email directly or
Ah funny, G-P behaves differently. There is no `update-gmo` target and the
files seem to have been updated yesterday when building.
This reminds me of the change to `autopoint` (#2938) which we did not yet do
for G-P and so maybe the stale `*.gmo` problem is rather new.
I think I will update
Unfortunately, this is possible and after some testing even likely.
But this raises more questions :(.
First I deleted po/da.gmo, expecting that `make` or `make install` will
regenerate it. But they didn't. Instead `make install` raised an error:
```
/usr/bin/install: cannot stat './da.gmo': No
OK no, it works fine here, I just had a stale `da.gmo` in my local directory,
but the content of the tarball is OK. @eht16 is it possible you didn't build
the Windows binaries from a fresh clone, and had a stale thing as well?
--
Reply to this email directly or view it on GitHub:
Hum, scratch that, doesn't seem to work for Danish…
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3620#issuecomment-1772764720
You are receiving this because you are subscribed to this thread.
Message ID:
It works for me, but note that this is the default value for a preference, so
it won't ever be updated on an existing installation. Try with `geany -c
/tmp/nonexistant`, you should see the translation.
--
Reply to this email directly or view it on GitHub:
12 matches
Mail list logo
