# Repository for localization files **URL:** \ **Category:** General\ **Created:** [December 13, 2022, 8:39am UTC](https://forum.geoprismregistry.com/t/repository-for-localization-files/28 "2022-12-13T08:39:08Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![rfromthecastle](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.geoprismregistry.com/rfromthecastle/32/28_2.png) [@rfromthecastle](https://forum.geoprismregistry.com/u/rfromthecastle)\ **Post date:** [December 13, 2022, 8:39am UTC](https://forum.geoprismregistry.com/t/repository-for-localization-files/28/1 "2022-12-13T08:39:08Z")
For Laos, a fully translated localization file for the Lao language is available for v1.0.0. This file is currently stored locally on one of the Ministry of Health staff’s computers, and available to download from the Laos instance of GeoPrism Registry. For languages that are also spoken in multiple countries, it may be useful for localization files (the UI Text tab in particular) to be shared publicly, for example, the Portuguese localization file for the Mozambique instance may be useful for a deployment in, say, Brazil or Portugal. Would there be a repository/platform where localization files can be easily shared and worked on collaboratively? ---
**Author:** ![jlewis](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.geoprismregistry.com/jlewis/32/14_2.png) [@jlewis](https://forum.geoprismregistry.com/u/jlewis)\ **Post date:** [December 13, 2022, 8:28pm UTC](https://forum.geoprismregistry.com/t/repository-for-localization-files/28/2 "2022-12-13T20:28:06Z")
Good idea! What do you think about having a GitHub repo (TerraFrame can host this) that is dedicated to collaboration on these files. The files can be downloaded with a button click and GitHub is particularly good at facilitating collaboration and tracking historical changes. The biggest downside is that it’s slightly more techy than something like Google Drive. ---
**Author:** ![rfromthecastle](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.geoprismregistry.com/rfromthecastle/32/28_2.png) [@rfromthecastle](https://forum.geoprismregistry.com/u/rfromthecastle)\ **Post date:** [December 14, 2022, 3:11am UTC](https://forum.geoprismregistry.com/t/repository-for-localization-files/28/3 "2022-12-14T03:11:49Z")
Keeping it central on GitHub sounds great! ---
**Author:** ![jlewis](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.geoprismregistry.com/jlewis/32/14_2.png) [@jlewis](https://forum.geoprismregistry.com/u/jlewis)\ **Post date:** [December 14, 2022, 5:20am UTC](https://forum.geoprismregistry.com/t/repository-for-localization-files/28/4 "2022-12-14T05:20:14Z")
Here’s the first attempt at a language repository that can grow with additional languages and their geographic variations. > **[GitHub - terraframe/geoprism-registry-localization: A repository for sharing...](https://github.com/terraframe/geoprism-registry-localization)** > > A repository for sharing opensource GeoPrism Registry language translations. - GitHub - terraframe/geoprism-registry-localization: A repository for sharing opensource GeoPrism Registry language tra... ---
**Author:** ![rfromthecastle](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.geoprismregistry.com/rfromthecastle/32/28_2.png) [@rfromthecastle](https://forum.geoprismregistry.com/u/rfromthecastle)\ **Post date:** [January 18, 2023, 4:18am UTC](https://forum.geoprismregistry.com/t/repository-for-localization-files/28/5 "2023-01-18T04:18:19Z")
Hi @jlewis! @Mc7434 Is currently finalizing the Lao localization file for GeoPrism Registry, and we’d love to share it on this repository. However, the Registry Metadata tab in here will contain translations for data specific to the Laos instance. What should we do about this tab? ---
**Author:** ![jlewis](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.geoprismregistry.com/jlewis/32/14_2.png) [@jlewis](https://forum.geoprismregistry.com/u/jlewis)\ **Post date:** [January 25, 2023, 12:30am UTC](https://forum.geoprismregistry.com/t/repository-for-localization-files/28/6 "2023-01-25T00:30:33Z")
Good question. I think the best process to follow now is to delete all the records from that tab that are not default properties. This might be a little tricky right now but we’ll look into a way to either indicate in the spreadsheet which are default vs custom or exclude non-default properties entirely. Any records that are deleted simply won’t set localization for that property. Those non-default properties are redundant anyway because their localization is managed in the UI.