A user posted on the Gramps Reddit that a update to Gramps openSuse from 15.6 to 16.0 fragged his Date parser’s English recognition.
I am assuming that during previous use, the operating system had been swapped back and forth between the user’s native locale and en_US several times. And probably the Gramps environmental variable were toggled a few times too.
It is jumbled enough that there little chance that we can reproduce their exact condition when the installer was run. (An inquiry about the Gramps versions and locales was posted.)
But now, when running in localized mode, Gramps no longer parses English dates nor span/range words. (It did so before the upgrade.)
ProcedureLive8470
LC_ALL=en_US.UTF-8 /usr/bin/gramps appears to work, but sadly I have to recreate affected events :)
Something to note… the Gramps installer for Windows says it defaults to en_GB (even though the Translation is actually US english). And the user set the LC_ALL override to US english. Maybe there was some internal confusion between the British/American english for the Date Parser?
Dictionaries Translations
PR#2319 docs(man): document LANGUAGE environment variable
refers to MantisBT issue 0010443: To run using a desired language need to set both LANG and LANGUAGE
Investigating output of ‘gramps -v’ finally I figured out that I need run GRAMPS as
LANG=ru_RU.utf8 LANGUAGE=ru gramps
The installer shows this is not an official release of Gramps. Is the reddit user using an unreleased build?
The screen captures were from a version on my test box. We don’t yet know which version they were using.
However, the odd GB english default has existed in every Windows installer for Gramps for at least a decade.
Yes. It’s the build that we are using for the FamilySearch Integration testing.
No. They are not using THAT version.
I just used my testbox to screen capture how the pre-selected an non-optional languages appear in ALL Windows installer versions.
As a question of whether there could be locale interaction.
Considering that:
- the Installer says
en_GB.
- What actually installed is
en_US.
- there is a Dictionary for
en_US that not selected by default
- there is no Translation listing for
en_us
- the user set
LC_ALL=en_US.UTF-8
- there is an old tech note that says the setting should be
LANG=en_US.utf8 LANGUAGE=en
That is a LOT of (possibly) interacting settings. Perhaps there is something that isn’t being set the way it ought to be?
There is not any Locale preference setting within the Gramps GUI. But it seems like something that should be possible to add. (Although it will probably require restarting Gramps after selecting a different Locale.)
This was a diagnostic gramplet that Claude AI wish-coded. It might be adaptable
