This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: i18n mark-up

From: Andrew Cagney <cagney at gnu dot org>
To: Eli Zaretskii <eliz at gnu dot org>
Cc: gdb at sources dot redhat dot com
Date: Sun, 08 Aug 2004 11:16:38 -0400
Subject: Re: i18n mark-up
References: <41153799.3080306@gnu.org> <1190-Sun08Aug2004065623+0300-eliz@gnu.org>

Date: Sat, 07 Aug 2004 16:12:09 -0400
From: Andrew Cagney <cagney@gnu.org>
Does anyone have any suggestions on how we should approach the task of marking up GDB's source for i18n?

Any reason why it shouldn't be done as for any other program?  That
is, use gettext tools to extract messages to a catalogue, then wrap
each message string in the sources with the _() macro call, and add
the rest of the infrastructure for the translated catalogues?

and all have been implemented as you suggest.

Well, almost. We've still got the tinyiest of tasks of marking up GDB's source with those _() macros :-)

Andrew

Follow-Ups:
- Re: i18n mark-up
  - From: Eli Zaretskii

References:
- i18n mark-up
  - From: Andrew Cagney
- Re: i18n mark-up
  - From: Eli Zaretskii

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]