I wouldn’t go as far as asking for a separate spanish translation set for both Argentinians and Uruguayans, but I definitely would point out the need to distinguish between Spaniard spanish and Latinamerican spanish.
Nobody from Tijuana (dare I say Chicago?) all the way down to Patagonia calls their computer an “ordenador”; we’d rather say “computadora”. We don’t accentuate the “i” in video either.
This is more important (more margin for error) with splash screens and dialogues where the developer has the space to write full sentences, than is the case with buttons, of course.
Same goes with all those lovely extra vowels when comparing UK english with US english.
Not trying to be a smarty-pants here.
Just saying; I could be wrong and I’ve ZERO developer expertise.
Update: The Spanish localization of Agenda is now officially underway , with @joseantoniolopezpaye, @alvaro87, @brauliop.3, @goliliana, and @Kathleen_T_Burns taking a first stab at the first round of translation. As outlined here , we’ll add a number of reviewers once they have concluded the first round and will give all of you access to the test builds as things progress. We’re looking forward to your feedback. To be continued…
Agreed–Spanish should be split into two variants, especially since technical vocabulary varies a LOT in Spanish. The same goes for English, for that matter. MacOS also uses two Spanish variants, and it’d be nice to match Apple’s standards if we have the people for it.
I can see that Finder indeed has an es.lproj and es_419.lproj, the latter being for latin America. Once the main spanish translation is there we can duplicate and create the 419 variant.
♂:muscle:t3:
♂
dare I say Chicago?
, with 
Panorama