id	summary	reporter	owner	description	type	status	priority	milestone	component	resolution	keywords	cc
712	Parser 2 unit tests fail with timeout	mitcho.com	mitcho.com	"As per our discussion over a couple weeks, we've decided to use a gettext-style string translation approach to command localization. This means user-generated natural language attributes such as names, help, etc. will stay in their monolingual forms in the commands and a replacement will be attempted automagically, while strings in preview() and execute() will require wrapping by a utility function _().

(Note: Nountype translation will *not* be a goal of the 0.1.9 milestone, nor will the synchronization/distribution/sharing of localizations.)

This ticket is part 3/3 of this process: setting up an environment so localizers can get involved in localizing strings for commands, and actually getting commands localized for some languages.

The format we will use for localizations will be the stringbundle, due to native XPCOM support and familiarity for Fx localizers: https://developer.mozilla.org/en/XUL/stringbundle"	defect	accepted	blocker		builtin-commands		try-to-reproduce