# Add 2 languages in config **URL:** \ **Category:** Rasa Open Source\ **Created:** [February 15, 2023, 2:59pm UTC](https://forum.rasa.com/t/add-2-languages-in-config/57224 "2023-02-15T14:59:47Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![NikolaMr](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.rasa.com/nikolamr/32/22347_2.png) [@NikolaMr](https://forum.rasa.com/u/NikolaMr)\ **Post date:** [February 17, 2023, 1:07pm UTC](https://forum.rasa.com/t/add-2-languages-in-config/57224/2 "2023-02-17T13:07:12Z")
Hi there, Rasa doesn’t support having multiple languages inside of the same config file. If you want to implement a multilingual bot you could refer to [What is the best way to create a multilingual chatbot?](https://forum.rasa.com/t/what-is-the-best-way-to-create-a-multilingual-chatbot/49430) There are multiple ways to tackle this problem. Recently I had a client that wanted both multilingual input and output. For that use case, I used a language agnostic config file (no language specific models even though I’ve stated that the config language is english), Rasa’s LabSE [rasa/LaBSE · Hugging Face](https://huggingface.co/rasa/LaBSE) for featurization, defined custom components to account for language specifics (for example, a custom component for wrapping duckling so multiple languages could be processed), etc. For the response part, you could use NLG server or overwrite the default implementation of CollectingDispatcher, as I did, and do all the required translations in there 🙂 However, if I were you, I’d experiment with NLG, it looks like a neater solution from my perspective now. Regards, Nikola --- _[View the full topic](https://forum.rasa.com/t/add-2-languages-in-config/57224)._