# "package.json" and locale **URL:** \ **Category:** Themes\ **Created:** [March 21, 2025, 2:40am UTC](https://forum.ghost.org/t/package-json-and-locale/56241 "2025-03-21T02:40:33Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![jobdiogenes](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/jobdiogenes/32/35404_2.png) [@jobdiogenes](https://forum.ghost.org/u/jobdiogenes)\ **Post date:** [March 21, 2025, 2:40am UTC](https://forum.ghost.org/t/package-json-and-locale/56241/1 "2025-03-21T02:40:33Z")
I’m a new to Ghost. But my first impression was nice. Ghost is fast and clean. I have experience with several’s CMS platform all using (python) and (php). So I start to customise to my country language. While I translate Casper theme, I saw that some themes templates conditions use option values from **‘package.json’** which are showed in UI. so, it is something to translate. But, jsons files could not receive handlebars translation tags **{{t** nor **(t**, because contents must be in between double quotes. I think that one option could be use a lang value direct in package.json , so, could load and select at runtime. Someone has any idea to deal with that problem?? ---
**Author:** ![Cathy\_Sarisky](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/cathy_sarisky/32/25750_2.png) [@Cathy\_Sarisky](https://forum.ghost.org/u/Cathy_Sarisky)\ **Post date:** [March 21, 2025, 12:06pm UTC](https://forum.ghost.org/t/package-json-and-locale/56241/2 "2025-03-21T12:06:05Z")
I’ve spent a lot more time with i18next than with Ghost’s theme translation engine. This is what would work for i18next. I’m not 100% sure it’ll work in theme files, but I’d start here. My guess would be that you could set them up for translation by doing something like {{t @custom.your\_custom\_value }}, and then adding each possible value of your custom value into the language.json files.