Conversation
|
Yes, I checked Crowdin. I actually started filling in lines there, but realized that reaching 100% coverage manually would take a significant amount of time. I absolutely love the idea of community contributions, but for non-English speakers, an app with partial translations is often unusable. My goal here is to provide an immediate baseline so the tool is useful for everyone today, rather than waiting for organic contributions to fill the gaps. Could we find a middle ground? We could use this PR as the new baseline and keep Crowdin for further improvements. Crucially, I did not overwrite any existing translations. I only filled in the missing gaps using AI, so we retained the high-quality human work while solving the "missing text" issue for new users. |
|
I'm not against using machine translations as a starting point, but you would have to remove all of the other additions / scaffolding that you have added here. If you want to submit a bulk update just to the translation files we can look at that, or there may be a way to generate those and upload via crowdin (which would be my preference) |
|
Thanks for the feedback, @SchrodingersGat. That sounds like a fair compromise. I understand the importance of keeping the repository clean of external tooling. I will proceed with cleaning up this PR to remove the scripts and scaffolding, leaving strictly the updated translation files (.arb) and the necessary locale registration. I'll get this done shortly and update the branch. |
Regarding your preference for Crowdin:I am fully open to that approach as I understand it maintains the single source of truth. However, I don't have the permissions or experience to perform a bulk import/upload to your Crowdin project myself. To facilitate this, would it work if I proceed with cleaning up this PR (leaving only the generated .arb translation files)? That way, you would have the raw data available in this branch to upload to Crowdin yourself if you prefer that over a direct merge. Please let me know if you need the data in a different format or if there is another way I can assist with the Crowdin transfer. |
sancho11
force-pushed
the
feature/spanish-translation
branch
from
1b97570 to
bf2d6db
Compare
sancho11
force-pushed
the
feature/spanish-translation
branch
from
c039c13 to
facac1a
Compare
That would be fine, please remove all other changes - if you have other bug fixes / improvements I would prefer to see those on a separate PR |
2 participants
Summary
This PR introduces full localization support across the application, with a specific focus on achieving 100% coverage for Spanish. It addresses previous gaps where certain UI cases were not covered by translation files and updates all supported languages using AI-assisted translation.
Key Changes
Global Update: Applied these coverage improvements to all supported languages, ensuring feature parity across the board.
Validation & Quality Verification
Emulator Testing:
All changes were verified in a controlled emulator environment to ensure application stability and correct rendering.
Bug Fixes (RTL/Display):
Addressed and resolved display issues affecting Arabic and other languages, ensuring they are now correctly rendered by the application.
Spanish (Native Verification):
The Spanish translations have been manually reviewed by a native speaker. The results are excellent with zero complaints, ensuring a high-quality experience for Spanish-speaking users.
Other Languages:
Cost Efficiency:
The entire translation process for all languages was completed with a total cost of approximately $0.30.
Motivation
This update is critical for deploying the application to non-English speaking environments. While the primary immediate need was for full Spanish support, this approach safeguards the codebase for wider international adoption.