From: "Eli Zaretskii" <eliz@gnu.org>
To: "M.M. Kettenis" <m.m.kettenis@alumnus.utwente.nl>
Cc: kevinb@redhat.com, kettenis@gnu.org, gdb@sources.redhat.com,
cagney@gnu.org
Subject: Re: i18n and internal errors
Date: Tue, 15 Feb 2005 14:35:00 -0000 [thread overview]
Message-ID: <01c5131a$Blat.v2.4$98b1e540@zahav.net.il> (raw)
In-Reply-To: <731992780126277@weblx058.utsp.utwente.nl> (m.m.kettenis@alumnus.utwente.nl)
> From: "M.M. Kettenis" <m.m.kettenis@alumnus.utwente.nl>
> Date: Tue, 15 Feb 2005 02:10:01 +0000
> Cc: cagney@gnu.org
>
> > As for the difficulty in fixing the bugs, the fatal messages typically
> > include a file name and a line number which point to the place where
> > the bug was caught. I think that alleviates some of the difficulties.
>
> Although line numbers might be a bit off compared to the current CVS version or even compared to the release.
True, but hopefully not by a lot.
> > Also, it is customary for users to translate the messages into English
> > when reporting bugs (a case in point is messages from the OS utilities
> > that have some relevance to the bug being reported), since the users
> > generally understand that English is a better language to talk to
> > maintainers.
>
> So we should update the bug reporting instructions to instruct users to run gdb with env LC_ALL="C". Hmm, hopefully that doesn't make the bug
> disappear.
We should indeed ask them to reproduce in the C locale, and if the bug
disappears, to translate the message(s) into English as best as they
can.
next prev parent reply other threads:[~2005-02-15 4:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-12 3:51 Mark Kettenis
2005-02-12 6:26 ` Kevin Buettner
2005-02-12 11:57 ` Eli Zaretskii
2005-02-14 20:38 ` Andrew Cagney
2005-02-15 0:52 ` Eli Zaretskii
2005-02-15 4:55 ` M.M. Kettenis
2005-02-15 14:35 ` Eli Zaretskii [this message]
2005-02-12 13:40 ` Joel Brobecker
2005-02-12 19:57 Paul Schlie
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='01c5131a$Blat.v2.4$98b1e540@zahav.net.il' \
--to=eliz@gnu.org \
--cc=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=kettenis@gnu.org \
--cc=kevinb@redhat.com \
--cc=m.m.kettenis@alumnus.utwente.nl \
/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