# Help with Translation/displaying labels correctly

**URL:** https://meta.discourse.org/t/help-with-translation-displaying-labels-correctly/341250
**Category:** Development
**Created:** [December 8, 2024, 8:08pm UTC](https://meta.discourse.org/t/help-with-translation-displaying-labels-correctly/341250 "2024-12-08T20:08:49Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![Moin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/moin/32/554653_2.png) [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [December 8, 2024, 9:20pm UTC](https://meta.discourse.org/t/help-with-translation-displaying-labels-correctly/341250/2 "2024-12-08T21:20:33Z")

</div>

Why do you create the texts as settings instead of putting them directly in en.yml?

> [@Add localizable strings to themes and theme components](https://meta.discourse.org/t/add-localizable-strings-to-themes-and-theme-components/109867):
>
> For those looking to add custom languages and translations to a Discourse theme or theme component, they [can now include](https://github.com/discourse/discourse/commit/880311dd4d2b367e54cc8244fba60fce69e121c3) localised strings, which are made available for use in UI components. Translations are stored in the same format as core/plugin translations, and can be used in almost the same way. Themes can supply translation files in a format like /locales/{locale}.yml. These files should be valid YAML, with a single top level key equal to the locale being defined. These can be defined us…

I think [Composer Footnote Button](https://meta.discourse.org/t/composer-footnote-button/243487) is a helpful example

---

_[View the full topic](https://meta.discourse.org/t/help-with-translation-displaying-labels-correctly/341250)._
