git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Laszlo Papp <djszapi@archlinux.us>,
	Laszlo Papp <djszapi2@gmail.com>,
	git@vger.kernel.org
Subject: Re: [PATCH 2/2] Add gitk-git Hungarian translation
Date: Mon, 14 Dec 2009 14:28:16 +1100	[thread overview]
Message-ID: <20091214032816.GB24152@drongo> (raw)
In-Reply-To: <7vskbejmrw.fsf@alter.siamese.dyndns.org>

On Sun, Dec 13, 2009 at 06:46:11PM -0800, Junio C Hamano wrote:
> Paul Mackerras <paulus@samba.org> writes:
> 
> > In any case, your patch has problems: I applied it and then ran
> > make to update the message catalogs, and I got these errors:
> >
> > Generating catalog po/hu.msg
> > msgfmt --statistics --tcl po/hu.po -l hu -d po/
> > po/hu.po:41: end-of-line within string
> > po/hu.po:41:4: syntax error
> > po/hu.po:42: end-of-line within string
> > po/hu.po:666: end-of-line within string
> > po/hu.po:666:10: syntax error
> > po/hu.po:667: end-of-line within string
> > msgfmt: found 6 fatal errors
> > make: *** [po/hu.msg] Error 1
> >
> > so I reverted it.
> 
> Syntactically there seem to be only two line-wrapping caused by MUA on the
> originating side that caused this.  Munging the problematic lines seems to
> fix the above.

It didn't look to me as though it was just MUA line-wrapping, since
there was a '+' at the start of the line following the one that didn't
have a closing quote.  Also, git am didn't complain about it, which it
would have done if it had been MUA line-wrapping.

> Now, I don't read _any_ Hungarian, so it could very well be that my fix-up
> is wrong and there shouldn't be any SP between two words in 'fájlon belül'
> and 'még nincsenek'; if we hear from some Hungarian capable readers that the
> fix-up below makes sense, perhaps squashing it in would be the easiest way
> to move forward?

I also don't read any Hungarian, which is why I didn't want to try to
fix up problems that were more than just MUA line-wrapping.  As you
say, if a Hungarian speaker can verify that your fix is correct, we
could fix up the original patch.  A clean re-post with a suitable
subject would be nicer, though.

Paul.

  reply	other threads:[~2009-12-14  3:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-15 11:23 [PATCH 2/2] Add gitk-git Hungarian translation Laszlo Papp
2009-11-19  9:07 ` Paul Mackerras
2009-11-22  8:05   ` Laszlo Papp
2009-11-29  2:33     ` Laszlo Papp
2009-12-13 18:30       ` Laszlo Papp
2009-12-13 19:03         ` Štěpán Němec
2009-12-13 20:56         ` Sverre Rabbelier
2009-12-13 23:03         ` Paul Mackerras
2009-12-13 23:59           ` Sverre Rabbelier
2009-12-14  1:54             ` Paul Mackerras
2009-12-14  2:46           ` Junio C Hamano
2009-12-14  3:28             ` Paul Mackerras [this message]
2009-12-14  4:43               ` Junio C Hamano
2009-12-14 12:30             ` Miklos Vajna
2009-12-14 13:12               ` [PATCH 0/2] gitk Hungarian translation updates Miklos Vajna
2009-12-14 13:12                 ` [PATCH 1/2] Fix up gitk-git Hungarian translation Miklos Vajna
2009-12-14 13:12                   ` [PATCH 2/2] Update " Miklos Vajna

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=20091214032816.GB24152@drongo \
    --to=paulus@samba.org \
    --cc=djszapi2@gmail.com \
    --cc=djszapi@archlinux.us \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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).