Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: Andrew Cagney <ac131313@ges.redhat.com>,
	Jim Blandy <jimb@redhat.com>,
	gdb-patches@sources.redhat.com
Subject: Re: [PATCH RFC] Character set support
Date: Fri, 13 Sep 2002 12:15:00 -0000	[thread overview]
Message-ID: <20020913191557.GA3392@nevyn.them.org> (raw)
In-Reply-To: <1020913191142.ZM19189@localhost.localdomain>

On Fri, Sep 13, 2002 at 12:11:42PM -0700, Kevin Buettner wrote:
> On Sep 13,  2:42pm, Andrew Cagney wrote:
> 
> > > On Fri, Sep 13, 2002 at 12:02:29PM -0500, Jim Blandy wrote:
> > > 
> > >> Daniel Jacobowitz <drow@mvista.com> writes:
> > > 
> > >> > I'm not suggesting reading wchar_t's from the target; that's not
> > >> > terribly useful a thing to do.  You _want_ the host wchar_t.  It is
> > >> > a host type capable of holding a wide character; the type changes
> > >> > based on platform and on whether or not the platform actually has
> > >> > wide character support.
> > > 
> > >> If you're suggesting using the host's wchar_t to hold characters after
> > >> conversion from the target charset to the host charset, then I'm with
> > >> you.
> > >> 
> > >> If you're suggesting using the host's wchar_t to hold character values
> > >> that have been read from the target, but not yet converted to the
> > >> host's charset, then I really disagree.  The target's wchar_t could be
> > >> 32 bits, while the host's might be 16 bits.
> > > 
> > > Precisely.  I was suggesting using host wchar_t after conversion to
> > > host format.
> > 
> > Sounds like we need a WCHAREST :-)
> 
> Yes, or something equivalent.
> 
> What I'd like to determine is whether Daniel thinks that the notion of
> a wchar_t *must* be added to Jim's work before the patch can go in. 
> (IMO, the wchar_t changes should be done as an incremental improvement.)

Certainly not; sorry if I gave that impression.  I think we should take
it as-is now, and then try to find someone with better i18n experience
to make it multibyte-friendly; Debian usually has an excess of such
people, so I'll go looking later :)

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-09-13 19:15 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-12 17:31 Kevin Buettner
2002-09-12 17:41 ` Daniel Jacobowitz
2002-09-12 20:24   ` Jim Blandy
2002-09-12 20:45     ` Andrew Cagney
2002-09-13 10:05       ` Jim Blandy
2002-09-13 11:39         ` Andrew Cagney
2002-09-13 19:06           ` Jim Blandy
2002-09-16 22:25             ` Andrew Cagney
2002-09-19 12:52               ` Jim Blandy
2002-09-19 13:27                 ` Kevin Buettner
2002-09-20 13:49                   ` Eli Zaretskii
2002-09-13  7:02     ` Daniel Jacobowitz
2002-09-13 10:16       ` Jim Blandy
2002-09-13 10:33         ` Daniel Jacobowitz
2002-09-13 11:42           ` Andrew Cagney
2002-09-13 12:11             ` Kevin Buettner
2002-09-13 12:15               ` Daniel Jacobowitz [this message]
2002-09-12 17:53 ` Andrew Cagney
2002-09-12 18:08   ` Kevin Buettner
2002-09-19 17:36 ` Kevin Buettner
2002-09-19 17:46   ` Kevin Buettner
2002-09-19 18:12   ` Andrew Cagney
2002-09-20  0:12     ` Kevin Buettner
2002-09-20  9:08       ` Andrew Cagney
2002-09-20 14:58         ` Kevin Buettner
2002-09-20 16:33           ` Andrew Cagney
2002-09-21  1:26           ` Eli Zaretskii
2002-09-20 16:55         ` Kevin Buettner
2002-09-20  8:59 ` Eli Zaretskii
2002-09-20 17:34   ` Kevin Buettner

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=20020913191557.GA3392@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=ac131313@ges.redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@redhat.com \
    --cc=kevinb@redhat.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