i18n - Githubissues

sebo-b / warp

Workspace Autonomous Reservation Program - a system to help you efficiently manage hybrid (assigned, hot-desks, etc) office space.

MIT License

139 stars 60 forks source link

i18n #9

Closed jpboehm closed 2 years ago

jpboehm commented 2 years ago

Hi, whenever I have set, like the doku says, the language in the WARP_LANGUAGE_FILE and restarted the app with a "custom" language (german in this case), all entries and links disappear. Unfortunately, the app does not load the additional i18n file. Do you have an idea what could be causing this?

sebo-b commented 2 years ago

Hi, can you please upload your german translation file? It's hard to say what's wrong without it.

jpboehm commented 2 years ago

Hi, yes this could be helpful ;-) https://github.com/jpboehm/warp/blob/6eebe99fd2be206d37428d4b14aa74f3cfa157ef/warp/static/i18n/de.js

sebo-b commented 2 years ago

Hi,

so it seems that the file is correct, which means that it is not accessible by the app. How do you run the app, in a container? If so, had you added this file to static folder before you built the docker image?

jpboehm commented 2 years ago

Hi, I'm a newbie to docker unfortunately (any tips?). But I have started the app in a container. About the file: I put the de.js in the Static folder (next to the English and Polish variants), adjusted the demo_compose.yaml and fired it up (in one variant also the config.py) and it doesn't work. The app actually does not find the de.js. Have I forgotten essential steps? I am curious how and if it works in "porduction", if I get there.

Thank you already for the quick answer and support.

sebo-b commented 2 years ago

ok, so please do the following steps:

(just to be sure) check out the project again (git clone ...)
copy your de.js to warp/static/i18n directory
add WARP_LANGUAGE_FILE: 'i18n/en.js' to environment section in demo_compose.yaml
rebuild containers without cache: docker compose -f demo_compose.yaml build --no-cache
run container: docker compose -f demo_compose.yaml up

sebo-b commented 2 years ago

the problem you had is that docker used cached versions of containers where your de.js file was not present

jpboehm commented 2 years ago

You are right, it was a caching issue :-). Thank you so much for support/the hint and this app.

sebo-b commented 2 years ago

you are welcome - enjoy!

sebo-b commented 2 years ago

ahh.. and feel free to make a pull request with your DE translation (when you think it is completed)

jpboehm commented 2 years ago

I will test it and do so!