linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Thierry Vignaud <tvignaud@mandriva.com>,
	ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH e2fsprogs] - remove timestamps from .po files
Date: Tue, 6 Nov 2007 09:55:20 -0500	[thread overview]
Message-ID: <20071106145520.GB9086@thunk.org> (raw)
In-Reply-To: <47307B3D.2010708@redhat.com>

On Tue, Nov 06, 2007 at 08:33:33AM -0600, Eric Sandeen wrote:
> Apparently there was some issue with this, once upon a time, which
> resulted in our rpms needing to update the po files... I guess I need to
> do a bit more code archeology / research.  It looks like sct added this
> when the pkg updated to 1.36, though there is no comment about why.

One potential reason could be that we are using ancient libintl files,
and there was some compatibility problem --- although I can't think of
a reason that would require updating the po files.

I know there is currently an issue on Debian because the po files are
getting intstalled in the wrong locations and the gettext shared
libraries are looking for them somewhere else, but I only vaguely
recall what was going on.  I had only enough time to start doing a
quick investigation to see why the translation files were getting
ignored, and didn't have time to try to fix it.

If someone would like to update the po directory and the configure.in
hunks for -po to something less antediluvian, patches would be greatly
appreciated....

						- Ted

      reply	other threads:[~2007-11-06 14:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-05 21:13 [PATCH e2fsprogs] - remove timestamps from .po files Eric Sandeen
2007-11-05 22:06 ` Theodore Tso
2007-11-05 22:12   ` Eric Sandeen
2007-11-06 10:24 ` Thierry Vignaud
2007-11-06 14:33   ` Eric Sandeen
2007-11-06 14:55     ` Theodore Tso [this message]

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=20071106145520.GB9086@thunk.org \
    --to=tytso@mit.edu \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --cc=tvignaud@mandriva.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).