public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: other/2857: i18n, translations does not work
Date: Fri, 25 May 2001 02:56:00 -0000	[thread overview]
Message-ID: <20010525095603.11183.qmail@sourceware.cygnus.com> (raw)

The following reply was made to PR other/2857; it has been noted by GNATS.

From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: Philipp Thomas <pthomas@suse.de>
Cc: Dennis Bjorklund <db@zigo.dhs.org>, Zack Weinberg <zackw@Stanford.EDU>, 
    Mark Mitchell <mark@codesourcery.com>, 
     <Gabriel.Dos-Reis@cmla.ens-cachan.fr>,  <gcc-gnats@gcc.gnu.org>, 
     <gcc-bugs@gcc.gnu.org>,  <gcc-patches@gcc.gnu.org>
Subject: Re: other/2857: i18n, translations does not work
Date: Fri, 25 May 2001 10:51:12 +0100 (BST)

 On Fri, 25 May 2001, Philipp Thomas wrote:
 
 > > Question: do the release scripts need to generate the compiled .gmo files?
 > > As those are binary, we surely don't want to put them in CVS.
 > 
 > Yes, they would need to do so, according to GNU standards, as the user
 > should not need to have the tools to create them.
 
 Since it looks like the Makefiles by default create catalogs in the build 
 directory, could you make the necessary changes - either to the release 
 script Mark posted, or to the Makefiles to build them in the source 
 directory instead - for them to be included in release tarballs?
 
 -- 
 Joseph S. Myers
 jsm28@cam.ac.uk
 


             reply	other threads:[~2001-05-25  2:56 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-25  2:56 Joseph S. Myers [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-06-13  0:56 Dennis Bjorklund
2001-05-25  8:16 Zack Weinberg
2001-05-25  8:06 Zack Weinberg
2001-05-25  3:26 Joseph S. Myers
2001-05-25  3:06 Philipp Thomas
2001-05-25  2:46 Philipp Thomas
2001-05-25  2:46 Philipp Thomas
2001-05-25  2:46 Philipp Thomas
2001-05-24 10:26 Zack Weinberg
2001-05-24  9:36 Joseph S. Myers
2001-05-24  9:26 Dennis Bjorklund
2001-05-24  9:16 Joseph S. Myers
2001-05-24  7:16 Dennis Bjorklund
2001-05-24  5:36 Joseph S. Myers
2001-05-24  4:36 Dennis Bjorklund
2001-05-24  1:36 Joseph S. Myers
2001-05-24  1:26 Zack Weinberg
2001-05-24  0:56 Joseph S. Myers
2001-05-24  0:46 Zack Weinberg
2001-05-23 10:36 Dennis Bjorklund
2001-05-23  0:56 Dennis Bjorklund
2001-05-23  0:26 Mark Mitchell
2001-05-23  0:16 Dennis Bjorklund
2001-05-22 23:06 Mark Mitchell
2001-05-22 22:56 Zack Weinberg
2001-05-22 22:36 Dennis Bjorklund
2001-05-22 12:56 Gabriel Dos Reis
2001-05-22 11:06 Zack Weinberg
2001-05-17 11:26 db

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=20010525095603.11183.qmail@sourceware.cygnus.com \
    --to=jsm28@cam.ac.uk \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).