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 such file or directory
installing ./da.gmo as /home/enrico/build/build_geany/share/locale/da/LC_MESSAGES/geany.mo

but it continued to install everything else.

After studying po/Makefile a bit, I noticed there is a target update-gmo which regenerates the *.gmo' files. This target is only indirectly by update-po`.
This would explain why @b4n and me had some old files laying around and why we probably have distributed outdated language files on Windows already since a long time.

I wonder if this is normal behavior or something uncommon in our use.

If it is meant like this, I will update the Windows build process to enforce regenerating the gmo files (probably use a clean build clone).

@techee might be the macOS builds affected by this as well?

@scootergrisen if you want, you can try the attached geany.mo file and copy it to C:\Program Files\Geany\share\locale\da\LC_MESSAGES (or whereever you have Geany installed).
geany_gmo_da.zip

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.