# What are the components of a localization? **URL:** \ **Category:** Development\ **Created:** [February 25, 2024, 5:28pm UTC](https://gramps.discourse.group/t/what-are-the-components-of-a-localization/4984 "2024-02-25T17:28:18Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\ **Post date:** [February 25, 2024, 5:28pm UTC](https://gramps.discourse.group/t/what-are-the-components-of-a-localization/4984/1 "2024-02-25T17:28:18Z")
Scott just mentioned the flatpak will be just English. In the past, the solution for making Gramps multilingual required a Re-install. What are the requisite parts needed to supported a translation and a dictionary? Is there any way that these can be added as a separate install? ---
**Author:** ![S.Mackay](https://avatars.discourse-cdn.com/v4/letter/s/b5a626/32.png) [@S.Mackay](https://gramps.discourse.group/u/S.Mackay)\ **Post date:** [February 25, 2024, 6:02pm UTC](https://gramps.discourse.group/t/what-are-the-components-of-a-localization/4984/2 "2024-02-25T18:02:55Z")
The Gramps flatpak from flathub uses system locales just fine. It is only the archived flatpaks at gramps-project github that are only English for now, and that is because my github workflow is missing the command to allow the use of system locales after compiling. Once someone at the flathub discourse gives me the command, I can recompile the gramps-project archives to use system locales. ---
**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\ **Post date:** [February 25, 2024, 6:13pm UTC](https://gramps.discourse.group/t/what-are-the-components-of-a-localization/4984/3 "2024-02-25T18:13:25Z")
Thanks. The question about adding a localization as a post-install ptocess has come up before. Just taking the opportunity as is presents itself. ---
**Author:** ![S.Mackay](https://avatars.discourse-cdn.com/v4/letter/s/b5a626/32.png) [@S.Mackay](https://gramps.discourse.group/u/S.Mackay)\ **Post date:** [February 26, 2024, 9:48pm UTC](https://gramps.discourse.group/t/what-are-the-components-of-a-localization/4984/4 "2024-02-26T21:48:01Z")
I got the answer from Flathub about why their flatpaks use the user’s system locale, but not the flatpaks compiled with the Github workflows. It isn’t a command from the compiler that makes the difference, but rather that Flathub sends a separate Locale file with the flatpaks and runtimes based on the user’s system locale. So setting the locale is done automatically by Flathub. By bypassing the Flathub installation of Gramps, the appropriate locale does not get sent to the user’s computer. The workaround for the Gramps archived flatpaks at the gramps-project github was to add a command in the manifest to leave out separate-locales during the build process, so that the archive would have to use system settings. ---
**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\ **Post date:** [February 26, 2024, 10:02pm UTC](https://gramps.discourse.group/t/what-are-the-components-of-a-localization/4984/5 "2024-02-26T22:02:05Z")
Does that mean that is is harder to install specific languages when they are not the OS selection? I’ve been installing English, French, German and Finnish on my Windows testbox. (Since those are the languages that some of my transcribed Notes include. I want the dictionaries and Date parsers for them.) ---
**Author:** ![S.Mackay](https://avatars.discourse-cdn.com/v4/letter/s/b5a626/32.png) [@S.Mackay](https://gramps.discourse.group/u/S.Mackay)\ **Post date:** [February 26, 2024, 11:28pm UTC](https://gramps.discourse.group/t/what-are-the-components-of-a-localization/4984/6 "2024-02-26T23:28:51Z")
I have not verified that all system locales get installed for flatpaks. In my testing VM, I did install the Gramps flatpak while the system was in English and in the same session added the Debian system language pack for Spanish. Then I rebooted the VM, changed the system language to Spanish, and made sure that the Gramps flatpak displayed Spanish (although I think the Prerequisites Add-on stayed in English, everything else in Gramps was Spanish). So while I haven’t tested enough to give a solid answer, my understanding is that flathub sends locale data for all languages in the system. Here is a discussion about locales at Flathub > **[What command from the appstream workflow enables localizations?](https://discourse.flathub.org/t/what-command-from-the-appstream-workflow-enables-localizations/6178/3)** > > This is: The only way to make this work is to set separate-locales: false in your manifest. I’ll also note that it is possible (though inconvenient) to install old versions of an app from Flathub: Tips and Tricks - Flatpak documentation ---
**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/gramps/original/1X/2ac1e712b7adf612e31ca08a55419f4cf37c0158.png) [@system](https://gramps.discourse.group/u/system)\ **Post date:** [March 27, 2024, 11:29pm UTC](https://gramps.discourse.group/t/what-are-the-components-of-a-localization/4984/7 "2024-03-27T23:29:17Z")
Closed on March 27, 2024, 11:29pm UTC This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.