-
-
Notifications
You must be signed in to change notification settings - Fork 431
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Review Spanish localization since CotEditor 4.6.0 #1543
Comments
Because all the localizable strings were migrated to new String Catalog format, the previous diff may not work anymore. If you have further questions about the new String Catalog, feel free to let me know. |
hi @1024jp , I'm a native Spanish speaker, so if this is still open I can help and review the translation |
@bucanero Thank you for the kind offer! I actually have just decided to find a new maintainer for the Spanish localization recently. cf. Localization maintenance instruction for CotEditor project Well, have you experienced localizing applications for Apple products using Xcode? Reviewing process for existing localization stringsFork the CotEditor repo (this one) and open All strings to be reviewed are marked as Repeat the process for all localizable files. The current Spanish strings to be reviewed are written by me using machine translation and my poor knowledge of Spanish. If you have any question, feel free to ask me. |
I close this issue to transfer the recruitment to #1709 |
@bucanero Please let me know whether you are still interested in reviewing. Just a one-time reviewing the existing strings is also helpful. |
@techagus In CotEditor 4.6.0, I updated the Spanish localization by myself by using machine translation in 761b7cb.
CotEditor 4.6.0 has already been released on 25 Sep. 2023, but I'm still not sure whether my change is acceptable as Spanish localization.
So, when you have time, please review them to see whether they have any odd translations.
Originally posted by @1024jp in #1519 (comment)
The text was updated successfully, but these errors were encountered: