From: Jeffrey A Law <law@upchuck.cygnus.com>
To: kthomas@gwdg.de (Philipp Thomas)
Cc: egcs@egcs.cygnus.com
Subject: Re: i18n of egcs
Date: Fri, 30 Apr 1999 23:15:00 -0000 [thread overview]
Message-ID: <26503.925456977@upchuck.cygnus.com> (raw)
Message-ID: <19990430231500.BX5EvBoNcfSh2gBa8HVES9uxsZLD6KNZbeo7o3NcSeA@z> (raw)
In-Reply-To: <3728dd6b.52244689@mailer.gwdg.de>
In message < 3728dd6b.52244689@mailer.gwdg.de >you write:
> Some points should be noted for the future though. The generation of the
> basic gcc.pot needs a modified gettext 0.10.35 (patch in ABOUT-GCC-NLS).
> So in order to not require that an egcs user has to patch his gettext
> package, your release scripts should generate a gcc.pot for inclusion into
> the egcs releases,
Err, look in the "intl" subdirectory. Isn't that the gettext code we need? Is
there some reason it is not being used? I thought the whole point behind
having a copy of the intl subdirectory was to deal with this issue.
jeff
next prev parent reply other threads:[~1999-04-30 23:15 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-27 11:43 Philipp Thomas
1999-04-27 13:06 ` Gabriel Dos_Reis
1999-04-27 13:33 ` Philipp Thomas
1999-04-28 0:46 ` Steinar Bang
1999-04-28 5:37 ` Gabriel Dos_Reis
1999-04-30 23:15 ` Gabriel Dos_Reis
1999-04-28 6:05 ` craig
1999-04-28 6:47 ` alex.buell
1999-04-28 6:53 ` craig
1999-04-28 7:17 ` alex.buell
1999-04-28 15:41 ` Martin v. Loewis
1999-04-28 15:46 ` Zack Weinberg
1999-04-28 23:16 ` Martin v. Loewis
1999-04-28 23:25 ` Gabriel Dos_Reis
1999-04-28 23:55 ` Joe Buck
1999-04-29 8:00 ` craig
1999-04-29 8:17 ` Joern Rennecke
1999-04-30 12:40 ` Philipp Thomas
1999-04-30 23:15 ` Philipp Thomas
1999-05-05 1:43 ` Steinar Bang
1999-05-31 21:36 ` Steinar Bang
1999-04-30 23:15 ` Joern Rennecke
1999-04-30 23:15 ` craig
1999-04-30 23:15 ` Joe Buck
1999-04-30 23:15 ` Gabriel Dos_Reis
1999-04-29 13:19 ` Richard Henderson
1999-04-30 23:15 ` Richard Henderson
1999-04-30 23:15 ` Martin v. Loewis
1999-04-30 23:15 ` Zack Weinberg
1999-04-30 23:15 ` Martin v. Loewis
1999-04-30 23:15 ` alex.buell
1999-04-30 23:15 ` craig
1999-04-30 23:15 ` alex.buell
1999-04-28 6:54 ` Gabriel Dos_Reis
1999-04-30 23:15 ` Gabriel Dos_Reis
1999-04-30 23:15 ` craig
1999-04-30 23:15 ` Steinar Bang
1999-04-30 23:15 ` Philipp Thomas
1999-04-27 22:24 ` Jeffrey A Law
1999-04-30 23:15 ` Jeffrey A Law
1999-04-30 23:15 ` Gabriel Dos_Reis
1999-04-30 0:27 ` Jeffrey A Law [this message]
1999-04-30 2:22 ` Andreas Schwab
1999-04-30 23:15 ` Andreas Schwab
1999-04-30 15:06 ` Philipp Thomas
1999-04-30 23:15 ` Philipp Thomas
1999-05-04 0:33 ` Jeffrey A Law
1999-05-31 21:36 ` Jeffrey A Law
1999-07-09 2:56 ` Jeffrey A Law
1999-07-31 23:33 ` Jeffrey A Law
1999-04-30 23:15 ` Jeffrey A Law
1999-04-30 23:15 ` Philipp Thomas
-- strict thread matches above, loose matches on Subject: below --
1999-04-28 9:17 Mike Stump
1999-04-30 23:15 ` Mike Stump
1999-04-05 17:27 Mike Stump
1999-04-30 23:15 ` Mike Stump
1999-03-25 3:43 Philipp Thomas
1999-03-31 23:46 ` Philipp Thomas
1999-04-03 21:29 ` Jeffrey A Law
1999-04-04 18:00 ` Philipp Thomas
1999-04-30 23:15 ` Philipp Thomas
1999-04-30 23:15 ` Jeffrey A Law
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=26503.925456977@upchuck.cygnus.com \
--to=law@upchuck.cygnus.com \
--cc=egcs@egcs.cygnus.com \
--cc=kthomas@gwdg.de \
/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).