Bug#206782: Fixes for the Vim spanish translation

Alejandro López-Valencia Alejandro López-Valencia , 206782@bugs.debian.org
Sun, 27 Mar 2005 07:38:30 -0500

I've taken the freedom of corecting the CC'ed address from "maintainer 
at vim dot org" to the working address  "bugs at vim dot org". BTW, 
that's in vim's online documentation, see  ":h bugs" or ":h 
bug-reports".  Please correct the reporting address if it is mentioned  
somewhere in the Debian documentation!!!!

Please notice that the protocol for reporting bugs on any contributed 
file to vim is to contact the file maintainer first, the vim developers 
list (in case the maintainer listens there, most of us do) second and  
the vim maintainer (at the address mentioned above) third. In general 
bug reports to Linux distros that are not related to packaging problems 
directly get lost in the cracks, unless it is some orphaned application 
adopted by member projects (something I appreciate deeply in Debian, btw).

Javier Fernández-Sanguino Peña wrote:

>tag 206782 - wontfix
>On Sat, Mar 26, 2005 at 02:18:07PM +0100, Pierre HABOUZIT wrote:
>>tag 206782 + wontfix
>>  I'm sorry to tell you that, but since your patch really doesn't apply
>>to current locale anymore, and that I don't think we have spanish naive
>>speaker in the team, we won't be able to use your patch.
>I've revised the spanish translation of vim...
As already said: current locale is way ahead of the curve. In fact I 
have already contributed a version using the ORCA glossary as guideline, 
same used by Javier. My last update to the file is dated  January 10, 
2005. I guess it wasn't updated in the official vim distribution 
<ftp://ftp.vim.org/pub/vim/messages/>  yet.

I've taken to keeping copies of the latest working versions at 
<http://dradul.tripod.com/vim/> so you may want to keep an eye there. 
Anyway, I find some of your corrections valid and in fact a valuable 
help in my work. Be assured that I am integrating them into my working 
copies as I write this and will submit new copies to the Vim maintainer 
and upload them to my web site. In fact I am very appreciative of the 
fact that you, Javier, are the first person to report bugs on the 
translation (of which I'm sure there are many). It is just that you 
didn't follow protocol so this has taken more effort and tolled more 
energy on you than necessary :-).

>>  So if you think current es l10n of vim is now good (in vim 6.3) pleas=
>>close the bug, else please update the diff, and I'll integrate ASAP.
As suggested above, I strongly disagree with forking the translation 
without official adoption. This only brings about effort dispersion. 
Now, if I suddenly dropped dead, or wasn't able or williing to keep 
maintaining the translation, I already know that Javier could continue 
the work. :-).

>Updated is a new es.po file based on the latest one in vim 6.3. I'm CCin=
>also the last translator for his information. This new po file fixes som=
>of the issues which I found and fixed in the last translation revision s=
>to this bug report. Alejandro fixed some of them, but there are still a
>number of incorrect translations which are related to bad terminology
>translations. Commands, for example, was translated to 'comandos' instea=
>of 'órdenes', a 'comando' is a green beret, not a command :-)
Ahh! Those" faux amis" that always bite you back and hard. I appreciate 
that you have taken the time to do editing work, it is really important 
to have peer review when doing a translation.

>Hopefully you will apply this revision, please also forward it to the 
>upstream  (in CC:) so that the translation can be useful for other 
>distributions too.
I would say that I'd much rather have you send me a (context or unified) 
diff file. You made the corrections on an older version of the file, so 
I'll have to integrate the changes by hand anyway.

And as you mention other distros besides Debian..., I'd much rather 
prefer to receive the bug reports and suggested changes directly so that 
eveyone can have an homogeneous version of the message catalog. That's 
why my address is in the file header. :-)