Italian translation ready — locale file, email templates, and i18n proposal

[111blackeagle111]

Hi,

I've been running xyOps for a while and needed it in Italian for my team. Ended up translating the whole thing — about 1600 strings across the UI, email templates, and docs.

Rather than just keeping it for myself, I figured it might be useful as a starting point for i18n support in xyOps. Especially since a lot of the infrastructure is already there (conf/locale/en-US.json, internal/intl.json, the language/region picker in user preferences).

I put together three things:

• conf/locale/it-IT.json — all translations in a structured JSON file, organized by page and component. Could plug into a getString(key, fallback) function without touching existing behavior.
• conf/emails/it/ — all 17 email templates translated. If email folders were organized by language (emails/en/, emails/it/), the right one could be picked at send time based on user prefs.
• I18N-PROPOSAL.md — a short write-up on how this could fit into the codebase with minimal changes. Incremental migration, English fallbacks, nothing breaks.

Everything is in a branch on my fork:
https://github.com/111blackeagle111/xyops/tree/i18n-italian

I also have a working Docker overlay that applies the translations on top of the official image — tested all 25 pages, JS syntax clean, JSON valid. Happy to share that too if it helps.

Couldn't open a PR (collaborator restriction), so dropping this here instead. Let me know if any of this is useful or if you'd prefer a different format.

Thanks for building xyOps — it's a great tool.

[jhuckaby]

WOW! This is amazing! Incredible work!

So, translations are on the list for later this year, but I haven't yet prepared all of the code to accept strings from a JSON file... Only a small subset does currently.

Much of the xyOps front-end code still has hard-coded English strings inside the JavaScript source files. How did you handle those in your version? Is that your Docker overlay that does that work? I'd love to see how it does that.

Sorry about the PR restriction -- it won't be there forever, it's just that xyOps is brand new, under heavy development, and I didn't want to lose control of the project. I will open PRs in the future once everything is stable.

I'd LOVE to incorporate your Italian translation into the main project once I get all the architecture and code ready for multi-locale.

[111blackeagle111]

Thanks a lot for the kind words!

For the hardcoded frontend strings, I went with a Docker overlay approach: I translated the JS files directly and rebuilt the _combo.js bundle at build time. The sidebar menu labels (search filters like "All Completed", "My Drafts", etc.) are stored in setup.json and config.json, so I patched those with a small Python script during the Docker build.

I also translated all 17 email templates and put together a structured locale file (conf/locale/it-IT.json) with roughly 540 EN→IT pairs, organized by section. It should be ready to plug in whenever you get the multi-locale architecture in place.

The Docker image is public, anyone can try it out:

docker run -d --name xyops-it -p 5522:5522 amaccafeoo/xyops-it:1.0.38-it

Then just open http://localhost:5522

All the source code is on the i18n-italian branch of my fork. Happy to help whenever you start working on the i18n infrastructure — looking forward to it!

[jhuckaby]

This is exceedingly clever, and my hat is off to you 😃

You've inspired me to fast-track the multi-locale support. I'll try to fit it into a future major release soon!

Basically my plan is to complete the move of all the UI strings into internal/ui.json (many are already there) and then allow that file to be localized (i.e. replaced) at installation time, likely by environment variable (e.g. XYOPS_locale).

There are a bunch of edge cases tho, like error messages (which come from the server), log messages, notifications, and other strings that live outside of the front-end, but end up being displayed in the UI.

But your idea of dynamically replacing things is very, very interesting.

Thanks again, this is awesome! I can't wait to have the proper framework for you to incorporate your work.

❤️

[github-actions]

This issue has had no activity for 7 days, so it is being marked stale. If there is still no follow-up in 3 more days, it will be closed automatically.

[jhuckaby]

Bad bot! I added the enhancement label so it won't auto-close this. Localization prep project still in progress!