# \[F\] Incorrect language in UI
**URL:** https://community.mp3tag.de/t/f-incorrect-language-in-ui/19567
**Category:** Fixed Bugs
**Tags:** bug-fixed
**Created:** [November 30, 2017, 7:28am UTC](https://community.mp3tag.de/t/f-incorrect-language-in-ui/19567 "2017-11-30T07:28:02Z")
**Posts on this page:** 9
**Page:** 2
### Author:  [@poster](https://community.mp3tag.de/u/poster)
#### Post date: [December 2, 2017, 11:37am UTC](https://community.mp3tag.de/t/f-incorrect-language-in-ui/19567/21 "2017-12-02T11:37:46Z")
> [@Florian](#):
>
> I think Mp3tag can detect which fields are changed and which are not, and auto-translate those unchanged fields. This comes with some implementation effort, but I think it's worth the effort given the amount of discussion and confusion which is otherwise produced.
Does that mean that Mp3Tag has a look at the tag-field itself, looks at the name of the tag-field and if this name is "original" changes it according to the language?
So you regard a special name for a tag-field in each language as original?
Are there "original" names beyond the predefined column- and tagpanel-view?
---
### Author:  [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [December 2, 2017, 11:51am UTC](https://community.mp3tag.de/t/f-incorrect-language-in-ui/19567/22 "2017-12-02T11:51:50Z")
> [@poster](#):
>
> Does that mean that Mp3Tag has a look at the tag-field itself, looks at the name of the tag-field and if this name is "original" changes it according to the language?
Yes. For the tag-panel fields I'd check the default ones (currently ALBUMARTIST, COMPOSER, and DISCNUMBER) and use the translated names for them on language change. Same applies to the columns of the file view.
> [@](#):
>
> So you regard a special name for a tag-field in each language as original?
I'm not sure, if I fully understand what you mean by "special name". I'd look at the internal representation which is the field name that is used internally (same as, e.g., in format strings) and use this one as a means for detecting "original" fields. Then compare the language-specific name of this default field (e.g., Kompozitorius for composer in Lithuanian) and only then auto-translate to the target language.
> [@](#):
>
> Are there "original" names beyond the predefined column- and tagpanel-view?
No. If you add a "real" user-defined entry to the Tag Panel, e.g., "Sortierung Interpret" for ARTISTSORT, Mp3tag would leave this untouched.
— Florian
---
### Author:  [@DetlevD](https://community.mp3tag.de/u/DetlevD)
#### Post date: [December 2, 2017, 11:55am UTC](https://community.mp3tag.de/t/f-incorrect-language-in-ui/19567/23 "2017-12-02T11:55:16Z")
> [@Florian](#):
>
> Detlev, maybe you didn't take the time to read my post above ...
Sorry, I did not saw and read your statement until after I sent my message.
DD.20171202.1355.CET
Florian, would have your planned change affect this file?
[Kopie\_von\_usrfields.ini.txt](https://community.mp3tag.de/uploads/default/original/2X/e/eae1f6ef95e314a70d6280ac81f6f3ec8d422c49.txt) (874 Bytes)
DD.20171202.1410.CET
[Kopie\_von\_usrfields.ini.txt](https://community.mp3tag.de/uploads/default/original/2X/e/eae1f6ef95e314a70d6280ac81f6f3ec8d422c49.txt) (874 Bytes)
---
### Author:  [@poster](https://community.mp3tag.de/u/poster)
#### Post date: [December 2, 2017, 12:38pm UTC](https://community.mp3tag.de/t/f-incorrect-language-in-ui/19567/24 "2017-12-02T12:38:12Z")
> [@Florian](#):
>
> I'm not sure, if I fully understand what you mean by "special name". I'd look at the internal representation which is the field name that is used internally (same as, e.g., in format strings) and use this one as a means for detecting "original" fields. Then compare the language-specific name of this default field (e.g., Kompozitorius for composer in Lithuanian) and only then auto-translate to the target language.
Yes, that is exactly what I meant. I used "special name" as synonym for "Language Specific Original Name" and have to agree that it was not a suitable term for clearness.
> [@](#):
>
> No. If you add a "real" user-defined entry to the Tag Panel, e.g., "Sortierung Interpret" for ARTISTSORT, Mp3tag would leave this untouched.
O.k. So I understood you right.
Anyway. After 8 years using MP3Tag I have to make a fresh installation to recognize which columns are original and which added or changed by me.
I think a list about these original names in the help-file would be helpful.
---
### Author:  [@dauma](https://community.mp3tag.de/u/dauma)
#### Post date: [December 2, 2017, 1:58pm UTC](https://community.mp3tag.de/t/f-incorrect-language-in-ui/19567/25 "2017-12-02T13:58:46Z")
> [@ohrenkino](#):
>
> Hello user dauma,
>
> No one doubts that your initial observation is right.
> You have also had the chance to see the reasoning behind the function that you grade as buggy behaviour.
>
> What I would like to hear from you is how you think that the behaviour could become less bug-ridden and include the preservation user-defined labels and field definitions.
Hi.
U'd like to hear me as a developer? 🙂 I'm not sure if I have a permission or ability to do that.
To be clear, as poster said, it's a situation where many reasonable answer could be done. So there were other discussions. There were some tests by me, you can do these too. Let's make mp3tag better. That's what I'd like. Not arguing, not depressing, not bug related. I'm sorry I'm lithuanian and saw that.
And žirniai for all ya.
PS I think it's bug.
---
### Author:  [@Bobeca](https://community.mp3tag.de/u/Bobeca)
#### Post date: [December 4, 2017, 12:22pm UTC](https://community.mp3tag.de/t/f-incorrect-language-in-ui/19567/26 "2017-12-04T12:22:55Z")
I definitely think that this is a bug. It isn't normal for programs not to change fully their language.
My easy workaround:
-Install mp3tag but don't run it!
- Go to install dir and then go to the "lang" folder and delete all the language files that you don't need (just leave the one that you want).
-Start mp3tag and everything will be in one language.
If you have already run mp3tag the workaround won't work. You will have to uninstall it and install it again.
---
### Author:  [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [December 4, 2017, 12:26pm UTC](https://community.mp3tag.de/t/f-incorrect-language-in-ui/19567/27 "2017-12-04T12:26:05Z")
> [@Bobeca](#):
>
> I definitely think that this is a bug. It isn't normal for programs not to change fully their language.
> ...
If you read post #22 [[F] Incorrect language in UI](https://community.mp3tag.de/t/19567/22) carefully, you will see that some labels will also not change in the future:
> [@](#):
>
> If you add a "real" user-defined entry to the Tag Panel, e.g., "Sortierung Interpret" for ARTISTSORT, Mp3tag would leave this untouched.
Just to not let expectations rise too high.
---
### Author:  [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [January 8, 2018, 1:04pm UTC](https://community.mp3tag.de/t/f-incorrect-language-in-ui/19567/28 "2018-01-08T13:04:16Z")
I've added the proposed auto-translation of the default fields with the current [Development Build](http://developer.mp3tag.de) Mp3tag v2.85k.
Thanks to all involved for participating in the discussion and for patience with me changing my mind about the topic.
Kind regards
— Florian
---
### Author:  [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [December 28, 2018, 2:10pm UTC](https://community.mp3tag.de/t/f-incorrect-language-in-ui/19567/29 "2018-12-28T14:10:38Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
[Previous page](https://community.mp3tag.de/t/f-incorrect-language-in-ui/19567.md?page=1)