Italian language file (Language_it.properties) has wrong and Spanish translations
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Problem Statement
The Italian message file dotCMS/src/main/webapp/WEB-INF/messages/Language_it.properties contains:
- Incorrect meaning for at least one key
- message.contentlet.publish.future.date is a success message in English (“Your content has been scheduled for publication in the future”) but in Italian it is translated as an error (“Impossibile pubblicare contenuti programmati per essere pubblicati in prossima data” — “Unable to publish content scheduled…”). Users with Italian locale see the wrong message type (error instead of success).
- Spanish text used instead of Italian
Several keys in the Italian file contain Spanish, e.g.:
addpage.dialog = “Agregar página HTML” (Spanish)
select.the.type.of.htmlpage.you.wish.to.upload = “Seleccione el tipo de página que desea crear” (Spanish)
Additional keys (e.g. various message.htmlpage.*, message.folder.refresh, workflow actionlet name, etc.) also use Spanish wording (e.g. “La información”, “El idioma”, “Ya existe”, “Bloquear página”, “Metadatos de la página”).
This affects any user with Italian locale (Language_it) in the admin UI and possibly on the front end where these keys are used. Impact: wrong UX (success vs error), wrong language (Spanish instead of Italian), and inconsistent Italian experience.
Steps to Reproduce
- Set dotCMS (or browser/profile) to use Italian locale so the UI loads Language_it.properties.
- Wrong-message check: Schedule content for future publication and complete the action. Observe the message for message.contentlet.publish.future.date: it shows an “impossibile pubblicare” (error) style message instead of a “scheduled for publication” (success) message.
- Spanish-in-Italian check: Open the “Add HTML Page” flow (or any UI that uses addpage.dialog and select.the.type.of.htmlpage.you.wish.to.upload). Observe that labels/text are in Spanish (e.g. “Agregar página HTML”, “Seleccione el tipo de página que desea crear”) instead of Italian.
- Optionally search Language_it.properties for Spanish markers (e.g. “Agregar”, “Seleccione”, “desea”, “página”, “La información”, “El idioma”) to find other keys still in Spanish.
Acceptance Criteria
- message.contentlet.publish.future.date in Language_it.properties is translated to reflect the English meaning: “Your content has been scheduled for publication in the future” (e.g. “Il tuo contenuto è stato programmato per la pubblicazione futura” or equivalent).
- All keys in Language_it.properties that currently contain Spanish text are replaced with correct Italian translations (including at least addpage.dialog, select.the.type.of.htmlpage.you.wish.to.upload, and the other Spanish keys identified in the file).
- No Spanish-only wording remains in Language_it.properties (no keys copied from Language_es.properties without translation).
- Italian locale UI shows the corrected success message and Italian (not Spanish) labels for the affected flows.
dotCMS Version
Latest
26.01.22-01
Severity
Low - Minor issue or cosmetic
Links
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open dotCMS/src/main/webapp/WEB-INF/messages/Language_it.properties and inspect message.contentlet.publish.future.date, addpage.dialog, select.the.type.of.htmlpage.you.wish.to.upload, and the other keys containing Spanish markers. Compare wording with the English and Spanish message files, then replace Spanish or incorrect text with Italian equivalents. Done means no Spanish-only wording remains and the affected Italian UI messages reflect their English meaning.
Written by the indexing model from the issue text.
Assessment
- Domain
- localization
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 68/100