Would appreciate others to take a look at too, so we make sure that we are using the best/common terminology possible. Here are some examples that had me thinking:
cifrar vs encriptar
nombre clave vs pseudónimo
odd-length secret (not sure if the literal translation is okay)
Anyhow, will review it against application later on. Taking a break now.
@bmeson thank you for revising. I appreciate it. I went through them, and the only one that bothers me, is when translating or not the “Google Authenticador”. I am using both, like this “Autenticador de Google (Google Authenticator”, en caso the application doesn’t change name in spanish speaking countries.
@daniel I think that is a reasonable trade-off, it makes the strings a bit longer but I think still reasonable. I verified that its “Autenticador Google” in the App Store so we can keep "“Autenticador de Google”. I think we can “lock” the translations where you are comfortable, that way we have a 100% translated language before string freeze.
It happened a few days ago, November 17th, meaning the strings found in the SecureDrop sources will not change until the release scheduled December 5th. But you have until the last minute to fix translations
A suggestion: At least on this end the drop button for languages doesn’t look like a drop down button to me. Would be better to write the languages names below instead? Something like shown in the following image: