public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Zack Weinberg" <zackw@Stanford.EDU> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: other/2857: i18n, translations does not work Date: Thu, 24 May 2001 01:26:00 -0000 [thread overview] Message-ID: <20010524082600.16921.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR other/2857; it has been noted by GNATS. From: "Zack Weinberg" <zackw@Stanford.EDU> To: "Joseph S. Myers" <jsm28@cam.ac.uk> Cc: Dennis Bjorklund <db@zigo.dhs.org>, Mark Mitchell <mark@codesourcery.com>, Philipp Thomas <pthomas@suse.de>, 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: Thu, 24 May 2001 01:16:47 -0700 On Thu, May 24, 2001 at 08:48:40AM +0100, Joseph S. Myers wrote: > On Thu, 24 May 2001, Zack Weinberg wrote: > > > On the other hand, it might be more useful to have a known place to > > work from, which would argue for leaving gcc.pot in CVS and updating > > it periodically. > > But that known place for translators of GNU software is > > http://www.iro.umontreal.ca/contrib/po/pot/ I *thought* there was some sort of web page like that, but I couldn't remember where it lived. > though we should, at least, have a defined tag in the repository (maybe a > snapshot or release tag) for the sources from which a .pot was generated, > if the .pot doesn't go in CVS. We ought to be regularly uploading revised .pot files, and checking for completed translations. Did anyone know that there are complete Danish and Japanese translations (for a gcc.pot from 2000-06-07, but still...) sitting there? -- zw They are calling true what their heart desires; what they would have be true, and if the iron bones of the earth or the light in the width of the sky say different, they will not permit these things to be knowledge within them, nor grant regard to any who do. -- Graydon Saunders
next reply other threads:[~2001-05-24 1:26 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-05-24 1:26 Zack Weinberg [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:56 Joseph S. Myers 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 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=20010524082600.16921.qmail@sourceware.cygnus.com \ --to=zackw@stanford.edu \ --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: linkBe 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).