Skip to content

Major update for el_GR to comply with latest translation requirements… - #14507

Open
fermosan wants to merge 1 commit into
apache:mainfrom
fermosan:el-gr-translations
Open

fermosan wants to merge 1 commit into
apache:mainfrom
fermosan:el-gr-translations

Conversation

@fermosan

Copy link
Copy Markdown
Contributor

Description

This PR completes and reviews the Greek (el_GR) UI translation in ui/public/locales/el_GR.json.

Missing translations

  • Adds Greek translations for the 1850 keys that were in en.json but missing from el_GR.json. el_GR.json now has all 4521 keys in en.json.

Cleanup

  • Removes 17 keys that no longer exist in en.json. One of them is message.delete.account, which was dropped from en.json in Extra checks in UI when deleting accounts #10760 and isn't shown by the account-deletion popup.
  • Merges 29 keys that appeared twice in the file into one entry each. The value kept is the one the UI already showed (JSON.parse uses the last one). Four of those values were broken (e.g. label.requireshvm = "Hεικονικής μηχανής"), so the correct value was used instead.

Review of existing translations
Every existing Greek string was checked against the English and corrected where it was wrong or confusing. Some examples:

  • Compute Offerings: "Υπολογιστικά Νέφη" (clouds) → "Προσφορές υπολογιστικών πόρων"
  • By state: "Ανά κράτος" (by country) → "Ανά κατάσταση"
  • Mine: "Εξόρυξη" (mining) → "Δικά μου"
  • RADOS/Ceph pool: "Πισίνα" (swimming pool) → "Δεξαμενή"
  • OpenDaylight / NetScaler were translated literally → kept as product names
  • Unavailable: "Διαθέσιμη" (available) → "Μη διαθέσιμο"
  • Some messages said the opposite of the English (e.g. "backups will also be deleted" where the English says they will not) or had dropped part of the text (e.g. "except NSX zones").
  • Words broken by earlier automatic "vm" replacements are fixed (e.g. "Kεικονικής μηχανής" → "KVM", "εικονικής μηχανήςware" → "VMware").
  • Typos are fixed throughout ("αποδεύσμευση", "Netsccaler", "αυ8εντικοποίησης", "στιγμιότυπου" → "στιγμιοτύπου", "καταχώρηση" → "καταχώριση").

Consistent terminology

  • Cluster → "συστοιχία". It was "ομάδα", the same word used for security, instance and affinity groups.
  • Kubernetes is no longer translated as "Κυβερνήτες".
  • Offerings use one naming scheme: "Προσφορά υπολογιστικών πόρων / δίσκου / δικτύου / υπηρεσίας".
  • One term each for load balancer ("εξισορροπητής φόρτου"), firewall ("τείχος προστασίας"), host ("κεντρικός διακομιστής"), storage pool ("δεξαμενή αποθήκευσης"), root disk ("δίσκος root") and expunge ("οριστική διαγραφή").
  • VPC/VPN use the Greek forms already in the file, with correct grammatical case.
  • Buttons use nouns as is usual in Greek UIs ("Εφαρμογή", "Διαμόρφωση", "Συνέχεια", "Υποβολή").

Product names, protocols and setting names (KVM, NSX, vm.userdata.max.length, etc.) are kept in English. "Pod" stays "συνομοταξία".

Only ui/public/locales/el_GR.json changes. No code changes.

Types of changes

  • Breaking change (fix or feature that would cause existing functionality to change)
  • New feature (non-breaking change which adds functionality)
  • Bug fix (non-breaking change which fixes an issue)
  • Enhancement (improves an existing feature and functionality)
  • Cleanup (Code refactoring and cleanup, that may add test cases)
  • Build/CI
  • Test (unit or integration test code)

Feature/Enhancement Scale or Bug Severity

Feature/Enhancement Scale

  • Major
  • Minor

Screenshots (if appropriate):

How Has This Been Tested?

  • Checked by script that el_GR.json is valid JSON and has exactly the same keys as en.json (4521), with no missing, extra or duplicate keys.
  • Checked by script that every string keeps the same {placeholders}, %x/%y/%z markers and HTML tags as its English source.
  • Searched for leftover old terms (e.g. "ομάδα" used for cluster, "Κυβερνήτες", broken "vm" replacements, misspelled "τοίχος").
  • New lines are added next to their position in en.json and existing lines keep their order, to keep the diff readable.

How did you try to break this feature and the system with this change?

The change only touches the Greek locale file, and vue-i18n falls back to English for any missing key, so other locales and UI code are unaffected.

@JoaoJandre

Copy link
Copy Markdown
Contributor

@fermosan I'm not sure we have anyone else active in the community that knows greek. @DaanHoogland do you know of anyone? (except @fermosan obviously). If there is no one... I guess we trust @fermosan that his translations are accurate?

@fermosan

Copy link
Copy Markdown
Contributor Author

@JoaoJandre We did the original translation as well back in the day if that helps.

@codecov

codecov Bot commented Oct 28, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 20.67%. Comparing base (fd6b755) to head (27bbd14).
⚠️ Report is 10 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff              @@
##               main   #14507      +/-   ##
============================================
+ Coverage     20.63%   20.67%   +0.03%     
- Complexity    21695    21723      +28     
============================================
  Files          6489     6492       +3     
  Lines        590136   590728     +592     
  Branches      72361    72448      +87     
============================================
+ Hits         121788   122108     +320     
- Misses       455100   455347     +247     
- Partials      13248    13273      +25     
Flag Coverage Δ
uitests 3.88% <ø> (+0.13%) ⬆️
unittests 21.97% <ø> (+0.02%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@DaanHoogland

Copy link
Copy Markdown
Contributor

@fermosan , you are now solely responsible ;) or more serious; keep an eye on this please.

@fermosan

Copy link
Copy Markdown
Contributor Author

@RosiKyu Kindly consider this as well as it is long time overdue on our part.

@fermosan

fermosan commented Oct 28, 2026 •

Copy link
Copy Markdown
Contributor Author

@fermosan , you are now solely responsible ;) or more serious; keep an eye on this please.

You are right, we need to find time before every release and work on changes for translation. There is quite a number of people working with that translation on production systems that we know or support.

@DaanHoogland

Copy link
Copy Markdown
Contributor

@RosiKyu @nvazquez I think we'll have to trust @fermosan on this one. cc @JoaoJandre .

@nvazquez nvazquez added this to the 24.0 milestone Oct 28, 2026

@nvazquez nvazquez left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM (trusting the translations are correct)

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants