From: Andrew Cagney <cagney@gnu.org>
To: Baurjan Ismagulov <ibr@ata.cs.hun.edu.tr>
Cc: gdb-patches@sources.redhat.com
Subject: Re: i18n, part 2
Date: Sun, 12 Dec 2004 18:35:00 -0000 [thread overview]
Message-ID: <41BC8E8B.5020200@gnu.org> (raw)
In-Reply-To: <20041204195702.GA25306@ata.cs.hun.edu.tr>
Baurjan Ismagulov wrote:
> /* Add a command to allow the user to force the FPU model. */
> new_set = add_set_enum_cmd
> ("fpu", no_class, fp_model_strings, ¤t_fp_model,
> - "Set the floating point type.\n"
> - "auto - Determine the FP typefrom the OS-ABI.\n"
> - "softfpa - Software FP, mixed-endian doubles on little-endian ARMs.\n"
> - "fpa - FPA co-processor (GCC compiled).\n"
> - "softvfp - Software FP with pure-endian doubles.\n"
> - "vfp - VFP co-processor.",
> + _("Set the floating point type.\n\
> +auto - Determine the FP typefrom the OS-ABI.\n\
> +softfpa - Software FP, mixed-endian doubles on little-endian ARMs.\n\
> +fpa - FPA co-processor (GCC compiled).\n\
> +softvfp - Software FP with pure-endian doubles.\n\
> +vfp - VFP co-processor."),
> &setarmcmdlist);
> set_cmd_sfunc (new_set, set_fp_model_sfunc);
> set_cmd_sfunc (deprecated_add_show_from_set (new_set, &showarmcmdlist),
You might want to consider focusing on these set/show commands, and
across all files. They need to be switched to the add_setshow_..._cmd
form vis:
> /* Debugging flag. */
> - add_setshow_boolean_cmd ("arm", class_maintenance, &arm_debug, "\
> -Set ARM debugging.", "\
> -Show ARM debugging.", "\
> -When on, arm-specific debugging is enabled.", "\
> -ARM debugging is %s.",
> + add_setshow_boolean_cmd ("arm", class_maintenance, &arm_debug,
> + _("Set ARM debugging."),
> + _("Show ARM debugging."),
> + _("When on, arm-specific debugging is enabled."),
> + _("ARM debugging is %s."),
> NULL, NULL,
> &setdebuglist, &showdebuglist);
> }
as the former involves deprecated_add_show_from_set and what that does
under the hood is very i18n-unfriendly.
The current add_setshow_.._cmd implementation also has problems (it
doesn't yet use the SHOW string) but at least all strings are present
and correct.
Andrew
PS: Also recall my suggestion for adding something like _XXX or _FIXME
as a way to mark that a string needs to be fixed on a second pass.
next prev parent reply other threads:[~2004-12-12 18:33 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-04 20:06 Baurjan Ismagulov
2004-12-04 21:52 ` Daniel Jacobowitz
2004-12-04 22:17 ` Baurjan Ismagulov
2004-12-04 23:59 ` Daniel Jacobowitz
2004-12-05 21:41 ` Eli Zaretskii
2004-12-05 23:39 ` Daniel Jacobowitz
2004-12-06 2:19 ` Baurjan Ismagulov
2004-12-06 4:59 ` Eli Zaretskii
2004-12-06 0:00 ` Baurjan Ismagulov
2004-12-15 0:50 ` Baurjan Ismagulov
2004-12-15 21:48 ` Eli Zaretskii
2004-12-06 18:53 ` Kevin Buettner
2004-12-06 20:59 ` Eli Zaretskii
2004-12-06 23:04 ` Kevin Buettner
2004-12-07 5:08 ` Eli Zaretskii
2004-12-07 5:10 ` Daniel Jacobowitz
2004-12-07 17:28 ` Kevin Buettner
2004-12-07 19:59 ` Eli Zaretskii
2004-12-07 20:28 ` Andreas Schwab
2004-12-12 19:50 ` Andrew Cagney
2004-12-12 22:08 ` Eli Zaretskii
2004-12-12 18:23 ` Andrew Cagney
2004-12-12 21:49 ` Eli Zaretskii
2004-12-07 22:02 ` Eli Zaretskii
2004-12-12 18:35 ` Andrew Cagney [this message]
2004-12-26 4:46 ` Baurjan Ismagulov
2004-12-26 23:25 ` Eli Zaretskii
2005-01-05 15:48 ` Andrew Cagney
2005-01-05 16:07 ` Baurjan Ismagulov
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=41BC8E8B.5020200@gnu.org \
--to=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=ibr@ata.cs.hun.edu.tr \
/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