mirror of
https://github.com/stenzek/duckstation.git
synced 2026-02-04 05:04:33 +00:00
[PR #2820] [MERGED] Spanish translation overhaul + Addition of es-ES alternative #1180
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/stenzek/duckstation/pull/2820
Author: @stenzek
Created: 4/4/2022
Status: ✅ Merged
Merged: 4/4/2022
Merged by: @stenzek
Base:
master← Head:spanish-overhaul📝 Commits (1)
f921236Spanish translation overhaul + Addition of es-ES alternative📊 Changes
6 files changed (+11171 additions, -2057 deletions)
View changed files
➕
extras/android-translation/values-es-ES/arrays.xml(+237 -0)➕
extras/android-translation/values-es-ES/strings.xml(+395 -0)📝
extras/android-translation/values-es/arrays.xml(+130 -109)📝
extras/android-translation/values-es/strings.xml(+292 -243)➕
src/duckstation-qt/translations/duckstation-qt_es-es.ts(+8345 -0)📝
src/duckstation-qt/translations/duckstation-qt_es.ts(+1772 -1705)📄 Description
In its current state, the Spanish translations for Duckstation are a mess of different dialects, multiple translations for the same terms, mistranslations or excessively literal translations, and typos.
It's a shame, because you could feel that the initial translations were done with care, but were muddled with future revisions.
This commit tries to solve all of these and also change the initial decision of the first translator to have an "universal" "neutral" Spanish, as time has proven it's not possible without a dedicated translator who actually wants to have one Spanish language for all Spanish-speakers across the globe.
I'm not going to be that one, so the next option would be to duplicate the Spanish translations into two: one for the Spanish-speaking American people (called "Latin American Spanish", "español de Hispanoamérica", code es-419") and one for the European Spanish speakers (called "Spanish (Spain)", "español de España", code es-ES).
This distinction is used in multiple software applications that managed to have translators for different languages, and should also funnel any future Latin American Spanish and European Spanish translators to the corresponding file.
I have tried to follow as many existing terms and constructions as possible, restoring and/or rewording any phrasal constructions that were disunified by the multiple translators.
Since I have a limited experience with Latin American Spanish, this commit should be sent as a draft for additional revisions. I'm open to stick to having a single Spanish language, but it has to be done RIGHT.
This is an overview of changes across the board:
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.