From: Daniel Jacobowitz <drow@false.org>
To: Hojin Choi <hojin.choi@gmail.com>
Cc: gdb@sources.redhat.com
Subject: Re: I18N: GDB Translation works?
Date: Fri, 07 Oct 2005 12:56:00 -0000 [thread overview]
Message-ID: <20051007125638.GB19002@nevyn.them.org> (raw)
In-Reply-To: <01d801c5cb09$927962a0$136410ac@lorthlorien>
On Fri, Oct 07, 2005 at 03:37:20PM +0900, Hojin Choi wrote:
> Hi, all
> I am a newbie in this list. I have joined just now :)
>
> I am interested in gdb strings to translate.
> Is there any translation guides for gdb pot file to localize?
>
> I just found some mails about gdb 6.4 about a year ago.
> http://sourceware.org/ml/gdb/2004-11/msg00029.html
> And no more official pages or cvs-versioned pot file. (Only pot build script I found)
No, there aren't. We've started adding i18n markup to GDB, but there
are no translations or infrastructure for translating yet. I'm not
sure what else needs to be done.
--
Daniel Jacobowitz
CodeSourcery, LLC
prev parent reply other threads:[~2005-10-07 12:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-07 6:38 Hojin Choi
2005-10-07 12:56 ` Daniel Jacobowitz [this message]
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=20051007125638.GB19002@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=hojin.choi@gmail.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