Programming

17366 readers

487 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

How do you handle language files? (lemmy.world)

submitted 1 year ago by BetaSalmon@lemmy.world to c/programming@programming.dev

29 comments fedilink hide all child comments

For a current project, I’ve been struggling with my language files. They’re all JSON files, and will always fallback to English if translations aren’t available.

My problem is that when a new key is required, I use my english file by default. This leads to situations where my client wants to translate new keys to other languages, and I have to spend time looking at all files, figuring out which keys i haven’t added there.

Essentially I want to get to a point where I can give all the translation files to my client, and he returns them with the translated content.

What do you guys use for managing this? And how would you solve the situation i’ve found myself in.

you are viewing a single comment's thread
view the rest of the comments

[–] starman@programming.dev 5 points 1 year ago* (last edited 1 year ago) (3 children)

You could write a script that updates other files based on english file. It could put someting like

"key": "UNTRANSLATED"

to missing fields.

[–] coloredgrayscale@programming.dev 1 points 1 year ago (2 children)

Usually a translation system might return the key value if the translation is missing. By translating with "untranslated" as a default you'd get just that text filled as fallback.

Unless you reinvent the wheel for lookup and can just ignore your magic value, or put an if on every value lookup.

Might be a risk there.

[–] starman@programming.dev 1 points 1 year ago (1 children)

You're right, I didn't think about it

[–] Vorpal@programming.dev 1 points 1 year ago

Your idea will work with minor changes (if comments are supported in your file format). At work our tooling create entries like 123="English text" // UNTRANSLATED. Obviously not quite the same format, but it should be adaptable to any format that supports comments.