Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#1053 closed defect (fixed)

Small changes (typos, semantic differences) to ES translation

Reported by: GomoX <gomo@…> Owned by: hugo
Component: Translations Version:
Severity: normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

I made some small changes to the current ES translation, added a few missing strings and corrected a few typos.

Attachments (4)

django.po (48.0 KB) - added by GomoX <gomo@…> 9 years ago.
Django.po
djangojs.po (2.8 KB) - added by GomoX <gomo@…> 9 years ago.
Djangojs.po
djangojs.2.po (2.8 KB) - added by GomoX <gomo@…> 9 years ago.
Fixed the encoding header.
djangojs.3.po (2.8 KB) - added by GomoX <gomo@…> 9 years ago.
Zillionth version (it has to work now!)

Download all attachments as: .zip

Change History (9)

Changed 9 years ago by GomoX <gomo@…>

Django.po

Changed 9 years ago by GomoX <gomo@…>

Djangojs.po

comment:1 Changed 9 years ago by hugo

Sorry, but the djangojs.po file is mixed charset: part is utf-8, part is iso-8859-1. It must be either one, but not both (the header talks about uf-8). Please upload a fixed djangojs.po. django.po was already marked in the header as iso-8859-1, so I assume it's fully iso-8859-1 - unless you added some utf-8 chars to it (the compiler can only detect wrong utf-8 chars in files marked as utf-8, not the other way around).

Please bump the ticket when you have checked the files and corrected djangojs.po.

Changed 9 years ago by GomoX <gomo@…>

Fixed the encoding header.

comment:2 Changed 9 years ago by GomoX <gomo@…>

That should be it. I used iso-8859-1 in order to match the other, larger file.

Changed 9 years ago by GomoX <gomo@…>

Zillionth version (it has to work now!)

comment:3 Changed 9 years ago by hugo

  • Resolution set to fixed
  • Status changed from new to closed

(In [1643]) fixes #1053 - updated 'es' translations

comment:4 Changed 9 years ago by Jorge Gajon <gajon@…>

This is not important but, I guess it would be better if all files (of all other languages too) used utf-8. That is, that all translations uses unicode instead of having different encodings each. I don't know, but I think that maybe having all kinds of encodings might cause problems in the future.

comment:5 Changed 9 years ago by anonymous

nope, it's just not needed to do - and actually editing utf-8 files in a non-utf-8 environment (which is the case with many people in western europe) is a pain, so why force it on them? gettext explicitely handles different encodings in the message files (it translates them internally to unicode strings anyway) so there won't be any future problems.

Note: See TracTickets for help on using tickets.
Back to Top