I just want to know if I can use the script for a Spanish site.
Spanish is one of the more complete translations.
110 strings to translate
Totalmente de acuerdo, y lo que no está traducido, lo estamos traduciendo
Anyway, do you know how “validate” translates @Mittineague ?
Ah, I need to be “Reviewer”
Sorry, but I don’t know what you’re asking.
“validar”, but you must know that.
I referer to this:
I think that discourse “team” have “reviewers” to “validate” translations.
PS, I think that @techapj can help here
I just made you reviewer of Spanish Argentina
Thanks, I’ve already copy es_ES to es_AR, now I review, and I’ll change to argentinian idioms
Now Spanish from Argentina is translated in 100% too
If you need help reviewing es_ES, just let me know.
Also made you reviewer of the
I completed the spanish version now to 100%, but reviewers have some work hehe
A doubt @zogstrip, why is there a “ES” version, and then other “es_AR”, “es_ES”, etc.
The “es” version for what purpose exist?
See RFC 4646 - Tags for Identifying Languages “Tags for Identifying Languages” for example. The bare “es” is just Spanish (español). Bare “en” is just English. If you want a specific version, you ask for the version with your region (hyphen country code, not underscore). And absent that specific version, you want to fall back to the general one: just “es”.
Thanks @elijah, but in this case “es” version is equal for “es_ES” version.
As a reviewer, I can not review both versions, it’s a waste of time.
Yes, I was a bit confused on why there would be both. Seems redundant to me.
I’m guessing the more general “es” was started before it was realized that country specific translations would be needed