Would be nice, just to keep the number of differences small, between 5.1.5/6, and 5.2. I’m assuming, but did not check, that they come with different Python versions, and some other lib versions too, but my cable modem is fast enough to deal with those 20 MB. 
Another GrampsAIO for you to test. I’ve added the dictionaries back, but there is still no working bsddb3.
Still getting a Console message about no dictionaries… even after selecting a BUNCH of them to install.
I saw the change, but my Gramps keeps speaking English to me, except again in Wine. And I still only see one file (gramps.mo) in the LC_MESSAGES folder. There are about 7 in that folder for 5.1.5, both for en_GB and nl.
Do you have any idea why these files are missing in the new install? They don’t look like dictionaries to me, but apparently they are needed for localization. And for some reason, Wine can live without them, weird.
@emyoulation have you ever tried WinMerge to compare folders? I haven’t done that here yet, for Gramps, but is a quick way to compare installations like these, and on Windows, Gramps AIO 5.1.5, and 5.1.6, and 5.2, can co-exist.
It looks like the installation script is being run from the wrong directory, so all the relative paths will be wrong.
I’ve created another GrampsAIO. This time I check that the dictionaries are in the expected place just before running the makensis script.
Looking at the script, it should copy the locale files to $INSTDIR\share\locale\ and the dictionaries to $INSTDIR\share\enchant\myspell\. Please check to see if they are actually copied.
I selected the US and AU english dictionaries and no additional Translations.
Unfortunately, still getting a dictionary warning.
However, the Preferences now appropriately disables the General tab option to “Enable spell checker” when no dictionaries exist.
Can (or should) you flush the Python __pycache__ directories too? Or exclude them from the AIO archive?
Do the dictionaries get copied to share/enchant/myspell?
Does the sanity check (that looks for the dictionaries and delivers the console message) work with Windows paths? Or is it just linux / macOS dialect URIs?
If it would, I would expect to see an error in the installation logs, but I don’t see anything like that. I can see that the dictionaries are copied, and the gramps.mo is installed, but not the other .mo files that I see in 5.1.6.
Here’s my log for your latest 5.2:
Uitvoermap: C:\Program Files\GrampsAIO64-5.2.0\share\enchant\myspell
Uitpakken: en_GB.aff
Uitpakken: en_GB.dic
Uitvoermap: C:\Program Files\GrampsAIO64-5.2.0\share\enchant\myspell
Uitpakken: nl_NL.aff
Uitpakken: nl_NL.dic
Uitvoermap: C:\Program Files\GrampsAIO64-5.2.0\share\locale
Uitvoermap: C:\Program Files\GrampsAIO64-5.2.0\share\locale\en_GB
Uitvoermap: C:\Program Files\GrampsAIO64-5.2.0\share\locale\en_GB\LC_MESSAGES
Uitpakken: gramps.mo
Uitvoermap: C:\Program Files\GrampsAIO64-5.2.0\share\locale
Uitvoermap: C:\Program Files\GrampsAIO64-5.2.0\share\locale
Uitvoermap: C:\Program Files\GrampsAIO64-5.2.0\share\locale\nl
Uitvoermap: C:\Program Files\GrampsAIO64-5.2.0\share\locale\nl\LC_MESSAGES
Uitpakken: gramps.mo
And here’s the same part for 5.1.6:
Uitvoermap: C:\Program Files\GrampsAIO64-5.1.6\share\enchant\myspell
Uitpakken: en_GB.aff
Uitpakken: en_GB.dic
Uitvoermap: C:\Program Files\GrampsAIO64-5.1.6\share\enchant\myspell
Uitpakken: nl_NL.aff
Uitpakken: nl_NL.dic
Uitvoermap: C:\Program Files\GrampsAIO64-5.1.6\share\locale
Uitvoermap: C:\Program Files\GrampsAIO64-5.1.6\share\locale\en_GB
Uitvoermap: C:\Program Files\GrampsAIO64-5.1.6\share\locale\en_GB\LC_MESSAGES
Uitpakken: glib-networking.mo... 100%
Uitpakken: glib20.mo
Uitpakken: gramps.mo
Uitpakken: gtk30-properties.mo
Uitpakken: gtk30.mo
Uitvoermap: C:\Program Files\GrampsAIO64-5.1.6\share\locale
Uitvoermap: C:\Program Files\GrampsAIO64-5.1.6\share\locale
Uitvoermap: C:\Program Files\GrampsAIO64-5.1.6\share\locale\nl
Uitvoermap: C:\Program Files\GrampsAIO64-5.1.6\share\locale\nl\LC_MESSAGES
Uitpakken: glib-networking.mo
Uitpakken: glib20.mo
Uitpakken: gramps.mo
Uitpakken: gtk30-properties.mo
Uitpakken: gtk30.mo
Uitpakken: gtkspell3.mo
Uitpakken: iso_3166.mo
Uitpakken: iso_639.mo
Uitvoermap = Output folder, Uitpakken = Unpacking.
The only errors that I see, both for 5.1.6 and 5.2, are font related, so I’ll skip those for now.
Is there a way to figure out whether the other .mo files are actually included with the installer?
The latest 5.2 actually bails out in Windows 10, and I can only see what happens when I run cmd:
C:\Program Files\GrampsAIO64-5.2.0>grampsd.exe
(grampsd.exe:7588): GLib-GIO-WARNING **: 19:45:54.581: win32 session dbus binary not found
2023-08-11 19:45:55.271: WARNING: spell.py: line 66: You have no installed dictionaries.
(grampsd.exe:7588): Gtk-WARNING **: 19:45:55.985: Could not load a pixbuf from icon theme.
This may indicate that pixbuf loaders or the mime database could not be found.
**
Gtk:ERROR:../gtk/gtk/gtkiconhelper.c:495:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load C:\Program Files\GrampsAIO64-5.2.0\share\icons\Adwaita\scalable/status\image-missing.svg: Error opening file C:\Program Files\GrampsAIO64-5.2.0\share\icons\Adwaita\scalable\status\image-missing.svg: No such file or directory (g-io-error-quark, 1)
Bail out! Gtk:ERROR:../gtk/gtk/gtkiconhelper.c:495:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load C:\Program Files\GrampsAIO64-5.2.0\share\icons\Adwaita\scalable/status\image-missing.svg: Error opening file C:\Program Files\GrampsAIO64-5.2.0\share\icons\Adwaita\scalable\status\image-missing.svg: No such file or directory (g-io-error-quark, 1)
Here is a new GrampsAIO intended to fix the bsddb3 problem. Thanks to John Ralls for helping out on this.
@Nick-Hall I just read that 7-Zip can extract all files from an NSIS installer. And when I did that, I found that in all LC_MESSAGES directories inside share\locale, there is only one .mo file, being gramps.mo.
And that leads to the question: Where are the other ones? Why are they not included with the installer?
I checked the contents of the 5.1.5 installer too, for NL, and in that, I see all .mo files that I also see in the installer log.
1 Like
The BSDDB convert (from 5.1.6’s XML schema 18 to 5.2’s schema 20) of the Tree worked. And then Gramps loaded it for editing without complaint.
(I thought that testing the Spelling was the objective in that last AIO artifact. The spellcheck still fails but the BSDDB passed.)
I think that you may be able to fix the spelling by setting the ENCHANT_CONFIG_DIR environment variable to point to the share/enchant directory.
1 Like
This GrampsAIO should include the missing mo files.
It does, and more, and it still started in English here. It does run in Dutch when I follow the instructions on our wiki though:
https://gramps-project.org/wiki/index.php?title=Gramps_4.2_Wiki_Manual_-_Settings#MS_Windows
There might be a newer version of this page, but I was lazy, so I used Google to find it.
Last follow-up for tonight:
For the display language, the LANG variable did the work, which means that the current grampsw.exe doesn’t detect it, like it seems to do for 5.1.6, if there is no other setting that I missed.
It’s not a red herring though, in the sense that with this LANG, and an older 5.2 AIO, Gramps speaks Dutch, but I see some English texts in the file selector. And that part speaks Dutch with the latest.
1 Like
We need gtk3.0.mo, but I’m not sure if all the other mo files are necessary.