git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Stimming <stimming@tuhh.de>
To: Paul Mackerras <paulus@samba.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 4/9] gitk i18n: Initial German translation.
Date: Fri, 21 Dec 2007 11:50:25 +0100	[thread overview]
Message-ID: <200712211150.25753.stimming@tuhh.de> (raw)

Dear Paul,

thanks a lot for applying the i18n patches to the gitk master at 
git.kernel.org. This looks all fine, except for one mistake that slipped in: 
The character encoding of the newly added po/de.po translation was messed up. 
The file must be in UTF-8 encoding (and I submitted it this way), but the one 
that ended up in the repository is in ISO-8859 encoding.

Could you please do 

  recode latin1..utf8 po/de.po

and commit the result? Otherwise a simple "make" will fail, because when 
msgfmt tries to "compile" the de.po it rightfully complains about the file 
not being in valid utf8, although the po file header claims "Content-Type: 
text/plain; charset=UTF-8".

Thank you very much.

Christian

             reply	other threads:[~2007-12-21 10:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-21 10:50 Christian Stimming [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-11-07 17:39 [PATCH 1/9] gitk i18n implementation: Add Makefile with rules for po file creation and installation Christian Stimming
2007-11-07 17:40 ` [PATCH 2/9] gitk i18n implementation: Import msgcat for message string translation; load translation catalogs Christian Stimming
2007-11-07 17:42   ` [PATCH 3/9] gitk i18n implementation: Markup many strings for translation Christian Stimming
2007-11-07 17:44     ` [PATCH 4/9] gitk i18n: Initial German translation Christian Stimming
2007-12-11 23:22       ` Paul Mackerras
2007-12-12  8:23         ` Christian Stimming

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200712211150.25753.stimming@tuhh.de \
    --to=stimming@tuhh.de \
    --cc=git@vger.kernel.org \
    --cc=paulus@samba.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).