# I18n\_app\_xx.properties has been modified

**URL:** <https://community.dhis2.org/t/i18n-app-xx-properties-has-been-modified/63904>\
**Category:** Implementation - Implémentation\
**Tags:** tracker\
**Created:** [4 March 2025 15:09 UTC](https://community.dhis2.org/t/i18n-app-xx-properties-has-been-modified/63904 "2025-03-04T15:09:52Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Stephan\_Mestach](https://dhis2.b-cdn.net/user_avatar/community.dhis2.org/stephan_mestach/32/40053_2.png) [@Stephan\_Mestach](https://community.dhis2.org/u/Stephan_Mestach)\
**Post date:** [4 March 2025 15:09 UTC](https://community.dhis2.org/t/i18n-app-xx-properties-has-been-modified/63904/1 "2025-03-04T15:09:52Z")

</div>

On a dhis2 instance, the label for the enrollment has been modified for everyone.

I can’t find how it happened. Is there a mechanism to override the “system” translations ?

I mean the content of : [tracker-capture-app/i18n/i18n\_app\_fr.properties at master · dhis2/tracker-capture-app · GitHub](https://github.com/dhis2/tracker-capture-app/blob/master/i18n/i18n_app_fr.properties#L148)  
unzipped in tomcat is different for the key “enrollment”  
(all timestamps looks unzipped/installed at the same time)

```auto
cat target/tomcat.8080/webapps/expanded/dhis-web-tracker-capture/i18n/i18n_app_fr.properties | grep Admi
enrollment=Admission du (de la) survivant (e)

```

I’ve looks in `/api/i18n` but haven’t found how it could have been modified through the api

is there such api ?  
is possible that the person rebuilt the app and deployed it ?

---

<div class="post-metadata">

**Author:** ![Stephan\_Mestach](https://dhis2.b-cdn.net/user_avatar/community.dhis2.org/stephan_mestach/32/40053_2.png) [@Stephan\_Mestach](https://community.dhis2.org/u/Stephan_Mestach)\
**Post date:** [4 March 2025 15:31 UTC](https://community.dhis2.org/t/i18n-app-xx-properties-has-been-modified/63904/2 "2025-03-04T15:31:00Z")

</div>

ok the translation is “bad” in the released war  
downloading [https://releases.dhis2.org/40/dhis2-stable-40.5.0.war](https://releases.dhis2.org/40/dhis2-stable-40.5.0.war)  
unzipping and looking at /dhis-web-tracker-capture/i18n/i18n\_app\_fr.properties  
and I have the same translation

---

<div class="post-metadata">

**Author:** ![Gassim](https://dhis2.b-cdn.net/user_avatar/community.dhis2.org/gassim/32/35347_2.png) [@Gassim](https://community.dhis2.org/u/Gassim)\
**Post date:** [4 March 2025 20:56 UTC](https://community.dhis2.org/t/i18n-app-xx-properties-has-been-modified/63904/3 "2025-03-04T20:56:20Z")

</div>

Hi @Stephan_Mestach

The DHIS2 Core Team uses Transifex to manage the translations (read more here: [Localization of DHIS2 - DHIS2 Documentation](https://docs.dhis2.org/en/implement/maintenance-and-use/localization-of-dhis2.html?h=transifex#translation-server))

If there are specific strings that are mistranslated and you’d like to share them here, it will help @christiansaka (HISP WCA) and team review them.

Thanks!

---

<div class="post-metadata">

**Author:** ![Stephan\_Mestach](https://dhis2.b-cdn.net/user_avatar/community.dhis2.org/stephan_mestach/32/40053_2.png) [@Stephan\_Mestach](https://community.dhis2.org/u/Stephan_Mestach)\
**Post date:** [5 March 2025 06:50 UTC](https://community.dhis2.org/t/i18n-app-xx-properties-has-been-modified/63904/4 "2025-03-05T06:50:19Z")

</div>

Well the original translation `Enrôlement` and `Profile` was probably better (less medical, more compact, less noisy) but I don’t have the background on the decision to change it to `Admission du (de la) survivant (e)` and `Identification du (de la) survivant (e)` but clearly “survivant” should become “suivant” or “patient” (following vs survivor)

note it affects 40.x, 41.3.0 looks back to “normal”.

---

<div class="post-metadata">

**Author:** ![Christiansaka](https://dhis2.b-cdn.net/user_avatar/community.dhis2.org/christiansaka/32/34457_2.png) [@Christiansaka](https://community.dhis2.org/u/Christiansaka)\
**Post date:** [6 March 2025 07:21 UTC](https://community.dhis2.org/t/i18n-app-xx-properties-has-been-modified/63904/5 "2025-03-06T07:21:40Z")

</div>

Hi @Stephan_Mestach

Thanks a lot for your feedback!

As the lead of the translation team, may I ask you to be more specific about the issue? I mean you mention the specific terms together with the translation issues related to them!

Thanks

---

<div class="post-metadata">

**Author:** ![Christiansaka](https://dhis2.b-cdn.net/user_avatar/community.dhis2.org/christiansaka/32/34457_2.png) [@Christiansaka](https://community.dhis2.org/u/Christiansaka)\
**Post date:** [6 March 2025 08:23 UTC](https://community.dhis2.org/t/i18n-app-xx-properties-has-been-modified/63904/6 "2025-03-06T08:23:57Z")

</div>

![image](https://dhis2.b-cdn.net/uploads/default/original/3X/9/8/98117f8ec66923a1935fca6e5b28bb18ba01a3db.png)

Regarding the term “Profile” I have seen the issue. The translator should have simply translated by “Profil” to avoid any confusion. We will correct that.

I have checked “Enrollment” as well. Within the team, we have agreed to translate if by “Inscription”. However, I have noticed that it is being translated by by “Enrôlement” by translator outside our team. We will do our best so as to haormonize. Thanks

---

<div class="post-metadata">

**Author:** ![Stephan\_Mestach](https://dhis2.b-cdn.net/user_avatar/community.dhis2.org/stephan_mestach/32/40053_2.png) [@Stephan\_Mestach](https://community.dhis2.org/u/Stephan_Mestach)\
**Post date:** [19 March 2025 06:50 UTC](https://community.dhis2.org/t/i18n-app-xx-properties-has-been-modified/63904/7 "2025-03-19T06:50:37Z")

</div>

Do you know if a 40.x will fix that ?

---

<div class="post-metadata">

**Author:** ![phil](https://dhis2.b-cdn.net/user_avatar/community.dhis2.org/phil/32/26881_2.png) [@phil](https://community.dhis2.org/u/phil)\
**Post date:** [1 April 2025 06:50 UTC](https://community.dhis2.org/t/i18n-app-xx-properties-has-been-modified/63904/8 "2025-04-01T06:50:22Z")

</div>

Hi @Stephan_Mestach

Every weekend, the latest translation updates are synchronised to the development branches of the maintained versions. This means that, as long as changes are made more than a couple of weeks before a patch release, they _should_ just go into the patch automatically.  
You can also check the [dev](https://play.im.dhis2.org/dev-2-40) version on our play site; if that contains the fix, then it will be in the next patch (_unless the patch has been frozen for our release testing, which happens about one week before the target release date_).

So the answer to your question is, “yes”. Although the next v40 patch is a couple of months away.
