# Everlasting Summer (Defold edition)

**URL:** <https://forum.defold.com/t/everlasting-summer-defold-edition/3395>\
**Category:** Dev diaries\
**Created:** [November 14, 2016, 10:09am UTC](https://forum.defold.com/t/everlasting-summer-defold-edition/3395 "2016-11-14T10:09:22Z")\
**Posts on this page:** 1\
**Showing post:** 23

<div class="post-metadata">

**Author:** ![britzl](https://forum-defold.b-cdn.net/user_avatar/forum.defold.com/britzl/32/23_2.png) [@britzl](https://forum.defold.com/u/britzl)\
**Post date:** [November 29, 2016, 6:49am UTC](https://forum.defold.com/t/everlasting-summer-defold-edition/3395/23 "2016-11-29T06:49:52Z")

</div>

> [@stormarchitextor](#):
>
> Think how to manage multilanguage support. Maybe translation files?

Yup, I’d put my translations into either a json file or directly into a Lua table in a module and then use another Lua module to do lookups of string values based on device language (read from sys.get\_sys\_info().device\_language). I created a small example to show what I mean:

[publicexamples/examples/localization at master · britzl/publicexamples · GitHub](https://github.com/britzl/publicexamples/tree/master/examples/localization) (SOURCE)  
[Localization 0.0](http://britzl.github.io/publicexamples/localization/index.html) (DEMO)

---

_[View the full topic](https://forum.defold.com/t/everlasting-summer-defold-edition/3395)._