Opened 3 years ago

Closed 2 years ago

#1220 closed enhancement (timeout)

Spanish language file totally corrected

Reported by: Lingüista Owned by:
Priority: normal Milestone:
Component: Localisation Version: 2.1.8
Severity: minor Keywords:
Cc: Platform: All
Sub Component:

Description

And so, converted to español de España.

Attachments (5)

aegisub.mo (93.2 KB) - added by Lingüista 3 years ago.
Spanish language file totally corrected, the now official one is awful…
aegisub.2.po (132.5 KB) - added by tomman 3 years ago.
Updated spanish translation, with merged corrections and some fixes
es.po (132.3 KB) - added by verm 3 years ago.
File from #1245
aegisub.po (132.4 KB) - added by Lingüista 3 years ago.
The PO file for the Spanish language file correction.
aegisub (spanish).po (132.4 KB) - added by Lingüista 2 years ago.
Some more corrections.

Download all attachments as: .zip

Change History (21)

Changed 3 years ago by Lingüista

Spanish language file totally corrected, the now official one is awful...

comment:1 Changed 3 years ago by verm

Noone told us this was happening, I wish you had waited since we're going to be releasing milestone:2.1.9 soon which has quite a few changes from milestone:2.1.8..

Also I need the .po file, the .mo is useless.

comment:2 Changed 3 years ago by Lingüista

Yes, that's the problem, people don't care much about linguistics...
OK, I uploaded the PO file. Well, I hope you can use my correction for future releases. If not, I will be pleased to correct the new file. Just tell me. :)
Regards.

comment:3 Changed 3 years ago by verm

I'll have to contact tomman first, the current maintainer with these changes, I'll send him an email tonight letting him know about this ticket.

comment:4 Changed 3 years ago by tomman

OK, i'm on the case. Let me check the updated translation for see which interesting fixes are there.

Changed 3 years ago by tomman

Updated spanish translation, with merged corrections and some fixes

comment:5 Changed 3 years ago by tomman

Finished my review. Nice job! I totally forgot that "fotograma" is a more accurate translation for "frame", so i've updated the translation to make it consistent with that term. Aside of some minor corrections, everything else is OK. As long as we keep the translation in "neutral Spanish", every fix should be cool.

comment:6 Changed 3 years ago by Lingüista

Yes, we should keep the neutral Spanish, but sometimes that's difficult (for example, vídeo is the etymological accent for that word, but in Latin America they usually say video for some reason...).

Thank you. :)

Changed 3 years ago by verm

File from #1245

comment:7 Changed 3 years ago by verm

This file you recently uploaded appears to be Castillan. This is not a replacement of the current translation but an entirely new one.

Are you willing to maintain this for future releases?

Changed 3 years ago by Lingüista

The PO file for the Spanish language file correction.

comment:8 Changed 3 years ago by Lingüista

The file I've corrected is the same, but with a lot of corrections. It is not Castilian or Spain Spanish, is the same but corrected. Anyway, we should try to keep a neutral or international translation instead of various with the only difference of some vocabulary and orthographical errors. Regards.

comment:9 Changed 3 years ago by tomman

A few remarks on your corrections:

1) You used "fotograma" for "frame" in the earliest revisions, but didn't do in the latest versions. Actually it's the correct technical word, since "cuadro" is too... generic.

2) Almost nobody says "vídeo" in Latin America (maybe in Argentina some people may use that accent). I don't know the exact reasons, but it's not time to change or correct a entire continent. So i say that we should stick to "video".

3) Could you generate a complete list of what you did fixed, and what was "awful"? This is my major inquiry with this ticket... The idea is to have a neutral and clean translation, but without knowing what exactly is wrong, this is quite difficult. Just saying "it sucks, have a corrected file" isn't very helpful.

comment:10 Changed 3 years ago by Lingüista

  1. Fotograma is the proper word in Spanish.
  2. In Latin America they say a lot of things. As I said, the etymological accent for video is vídeo (just listen how the users of English language pronounce it). I think it would be a very great thing to correct that word, or better make a language file for Latin America and other for Spain.
  3. I cannot generate a list like that because I corrected everything bad or improper that I saw, and that's very much. Grammar, orthography, vocabulary... All based in Real Academia Española rules (the official, or traditional ones) and recommendations. If the complete correction of the file doesn't help, I don't know what can help...

Regards.

Last edited 3 years ago by Lingüista (previous) (diff)

comment:11 Changed 3 years ago by tomman

Considering your answer, and given the wide differences between both dialects (the RAE rules are the same for everybody, but the big problem here is the vocabulary, the differences are quite important), i actually agree on having separate locales for Latin America and Spain would be the best option - it makes much more sense, IMO.

English is not the same as Castillan Spanish or Latin American Spanish, so i see no comparison point there. Please look at this:
http://en.wikipedia.org/wiki/Spanish_dialects_and_varieties

comment:12 Changed 3 years ago by Lingüista

Yeah, that’s the best option, no doubt of it. In fact, the most programs use two different translations for Castilian or Spain Spanish and American or Latin Spanish. Tell me if you need help, although I’ve already sent two totally corrected files for Aegisub Spanish translation, one for 2.1.8 and other for 2.1.9.
Why I would need to read again that Wikipedia article?
Regards.

Last edited 3 years ago by Lingüista (previous) (diff)

comment:13 Changed 3 years ago by tomman

OK, no problem then. Now let's wait for the call for translators for the upcoming versions.

Changed 2 years ago by Lingüista

Some more corrections.

comment:14 Changed 2 years ago by Lingüista

I've done some more corrections to Spanish translation.

But I write here once more to complain or suggest... I just downloaded the latest version of Aegisub, 2.1.8, and I've seen that there's still one Spanish type, supposeddly neutral, but it's clearly “Latin American”.

I'd like to inform, too, that some strings are not appearing in PO, nor POT, files, so it remain untranslated, or it is not possible to modify them, just like “Bold” (translated as “Gruesa”, when it should be “Negrita” [see “Ortografía de la lengua española” of 2010 by ASALE]). Why is this happening?

I think Aegisub is a good program, so I want the Spanish translation be good enough as well.

Regards.

comment:15 Changed 2 years ago by nielsm

  • Milestone set to 2.1.9

The POT file for 2.1.9 has been finalised.

If this European Spanish translation is updated for the 2.1.9 strings, I will include both it and tomman's Latin American Spanish translations.

comment:16 Changed 2 years ago by nielsm

  • Component changed from General to Localisation
  • Milestone 2.1.9 deleted
  • Resolution set to timeout
  • Status changed from new to closed
  • Type changed from defect to enhancement

I guess this is called off, the submitter of the ticket hasn't left any means of contact.

Note: See TracTickets for help on using tickets.