# \[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:** 1
**Showing post:** 22

<div class="post-metadata">

### Author: ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@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")

</div>

> [@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

---

_[View the full topic](https://community.mp3tag.de/t/f-incorrect-language-in-ui/19567)._