From: "Eli Zaretskii" <eliz@gnu.org>
To: Mark Kettenis <kettenis@gnu.org>
Cc: gdb@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: Bring back the intl subdirectory please
Date: Sun, 23 Jan 2005 21:45:00 -0000 [thread overview]
Message-ID: <01c50194$Blat.v2.4$74f49220@zahav.net.il> (raw)
In-Reply-To: <200501231413.j0NEDHo3069791@elgar.sibelius.xs4all.nl> (message from Mark Kettenis on Sun, 23 Jan 2005 15:13:17 +0100 (CET))
> Date: Sun, 23 Jan 2005 15:13:17 +0100 (CET)
> From: Mark Kettenis <kettenis@gnu.org>
> CC: eliz@gnu.org, gdb@sources.redhat.com, binutils@sources.redhat.com
>
> 1. Drop intl/ and only enable NLS if an external libintl is available
> (which on GNU/Linux systems is available as part of glibc). We'll
> need to upgrade the configuration magic in bfd/, opcodes/, gdb/,
> binutila/, gas/ and ld/. I've tried this for bfd/, opcode/ and
> gdb/ which seems to work reasonably well.
>
> 2. Update intl/. We can either upgrade to the gettext used by GCC or
> a more recent version. The GCC version is probably easier since it
> already has the modifications needed for the layout of our source
> tree.
>
> There is of course the third option:
>
> 3. We give shit about anything that's not GNU. GNU/Linux is now so
> dominant that we don't care about other systems. Users of non-free
> software deserve what they get and should not complain.
>
> I hope that option doesn't have any backers.
Me too.
> Anyway, the argument for option #1 is that intl/ might not build
> properly on some (presumably) non-GNU systems.
Even if that is true, it couldn't do any more harm than now, since
i18n in GDB is currently broken on _all_ non-GNU systems.
> Personaly I don't really care about internationalization, so I'd vote
> for #1.
Even if we don't care about i18n, it wouldn't be nice to go for #1
because of the i18n-related work already invested in GDB (by Baurjan
and others).
next prev parent reply other threads:[~2005-01-23 21:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-22 16:04 Mark Kettenis
2005-01-22 18:53 ` Eli Zaretskii
2005-01-22 19:12 ` Andreas Schwab
2005-01-23 14:09 ` Mark Kettenis
2005-01-24 19:51 ` Andrew Cagney
2005-01-24 20:29 ` Mark Kettenis
2005-01-24 21:24 ` Andrew Cagney
2005-01-25 20:51 ` Mark Kettenis
2005-01-26 15:56 ` Andrew Cagney
2005-01-26 16:20 ` Mark Kettenis
2005-01-26 20:07 ` Andrew Cagney
2005-01-26 23:28 ` Mark Kettenis
2005-01-23 14:13 ` Mark Kettenis
2005-01-23 21:45 ` Eli Zaretskii [this message]
2005-01-24 18:03 ` Ian Lance Taylor
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='01c50194$Blat.v2.4$74f49220@zahav.net.il' \
--to=eliz@gnu.org \
--cc=binutils@sources.redhat.com \
--cc=gdb@sources.redhat.com \
--cc=kettenis@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