Replies: 20 comments 40 replies
-
Hi @waydabber, I'd like to contribute with PT-BR localization. |
Beta Was this translation helpful? Give feedback.
-
Hi @waydabber PT-PT and PT-BR are similar but not identical. If you should create only one or both of them depends on you. My sugestion, You should create pt-br and if someone wish to do PT-PT then you can create it. |
Beta Was this translation helpful? Give feedback.
-
Hey @waydabber, I'd like to contribute to Turkish language support. |
Beta Was this translation helpful? Give feedback.
-
Hello @waydabber, I'd like to contribute to Korean translation with @Ryan-Dia |
Beta Was this translation helpful? Give feedback.
-
Hi @waydabber, I'd like to contribute to the zh-TW translation. |
Beta Was this translation helpful? Give feedback.
-
Hi @waydabber, I would like to contribute to Korean translation. |
Beta Was this translation helpful? Give feedback.
-
Hi @waydabber is it a deal when i localize it to full german and get a pro license? :-) |
Beta Was this translation helpful? Give feedback.
-
I'd like to contribute to Russian translation. |
Beta Was this translation helpful? Give feedback.
-
Hey @waydabber Thanks a lot |
Beta Was this translation helpful? Give feedback.
-
Hi, I do love BetterDisplay. I'd like to contribute to Italian translation. @waydabber |
Beta Was this translation helpful? Give feedback.
-
Is there any way I can translate, for example, from Portuguese (instead of English) to Spanish in the same window? Because it will be easier to do it in that way, except opening another extra window to see the Portuguese translation. |
Beta Was this translation helpful? Give feedback.
-
Hi All, I moved the downloadable localization files to a separate new repository: https://github.com/waydabber/BetterDisplay-localization I'd like to make contributing to localization much more relaxed than now. You can use existing means and communication channels to work on the localization, but if you are up to it, you can also fork the localization repo, work in a versioned environment (you can use Localization issues are also moved to the new repository: https://github.com/waydabber/BetterDisplay-localization/issues From now on any number of volunteers can work on a localization and tight communication/coordination is not needed anymore. This change seems to be needed because of a number of inactive primary volunteers for a language - new volunteers did emerge, but could not proceed due to lack of communication from sometimes inactive primary volunteers. The lack of communication resulted in no clear way to properly divide up the work or join the effort. Now as localization is properly versioned in GitHub, the process should get simplified and more self-organizing over time (at least that's the hope). I updated the Localization effort discussion opening post accordingly. I hope these changes will not cause a total meltdown in the process (lol) - if they do, we'll figure out something else. 😄 |
Beta Was this translation helpful? Give feedback.
-
Just a note, did a deeper review - there were some texts in the app unreachable with localization. Fixed that, hopefully now all parts of the app is localizable. Updated the localization repo. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
@MapleLeaf14 Can you call me on Discord? |
Beta Was this translation helpful? Give feedback.
-
Ok, I figured out what was wrong with Crowdin (creating a "strings based" translation will not work, it's a new feature and has issues). I created a new Crowdin project, imported all translations and configured the source language and XLIFF export settings so it uses proper titles, file names and export file names as well. https://crowdin.com/project/betterdisplay-pro @MapleLeaf14 @giulianopires - sent you invites, please join to this project (and to avoid confusion, please delete the other projects). If things work out, I'll try to migrate other translators to use Crowdin as well. For now I'll leave things as is for others, but of course anybody can join the Crowdin project. Thank you! |
Beta Was this translation helpful? Give feedback.
-
hi @waydabber I would like to translate Better Display to Portuguese (European) (pt-PT) |
Beta Was this translation helpful? Give feedback.
-
Hi @giulianopires, Here is the new PT-BR file with all lines translated. Can you do a double check ? |
Beta Was this translation helpful? Give feedback.
-
I've jumped in and changed 119 items from US to UK English. I may have missed some less common differences, but the app should now grate less to UK eyes. I hacked this in a text editor (no XCode for me), so the file is not identified as UK. Perhaps that is easy to adjust? I hope it's helpful! |
Beta Was this translation helpful? Give feedback.
-
Please change
to
The current form is just wrong. |
Beta Was this translation helpful? Give feedback.
-
Current localization status
The following table contains the localizations currently being worked on as well as their current completion state.
(last update: 14/11/2024)
The latest localization files are always available in the BetterDisplay-localization repository for download (click the green
Code
button and selectDownload ZIP
.The latest interim builds (with latest localizations at the time) are available under the Assets section here (after a fresh public release the latest app version might be more-up to date):
https://github.com/waydabber/BetterDisplay/releases/tag/pre
Localization process
Every localization gets a GitHub issue in the BetterDisplay-localization repository that can serve as a place for communication for a language. General chat can also happen at the app Discord channel's Localization forum.
Regular volunteers can be assigned to the language specific issue in the BetterDisplay-localization repo.
Note
Contributing to a localization does not require one to volunteer regularly, anybody can fix something or add to a localization by creating a PR in the localization repo or attaching an updated zip file to the language specific issue.
The localization process is rather simple:
xcloc
format) if it is still not available. You can download the localization repository (in zip format) or clone the repository and start working on your language'sxcloc
file using XCode (see below). You can also create a fork using GitHub and work on that.xcloc
file corresponding your language (for examplees.xcloc
for Spanish).NEW
. Enter the translation in the third row (corresponding to the target language).xcloc
(for examplees.xcloc.zip
) file to the language specific GitHub issue asking @waydabber to check it and import it to the project.Contribute to localization via Pull Requests - OPTIONAL
You can fork the (BetterDisplay-localization repository)[https://github.com/waydabber/BetterDisplay-localization] repo for yourself, work in a versioned environment (by using
git
or GitHub Desktop) and create a Pull Request in the (BetterDisplay-localization repository)[https://github.com/waydabber/BetterDisplay-localization].GitHub Issues for Localizations
https://github.com/waydabber/BetterDisplay-localization/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc
FAQ
(Empty string)
does not need to be localized.%
(like%@
,%lld
) it should be incorporated into the translation (these codes denote a programmatically changing value that appears somewhere in the text to be localized).%
values are not needed to be localized (but if they are copied over, that is fine as well).InfoPlist
items are not needed to be localized.If you have any questions regarding or during localization or want to volunteer, just hop to the app Discord channel's Localization forum (or alternatively post a comment here).
Beta Was this translation helpful? Give feedback.
All reactions