id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
23	JSON format where possible	kowey	somebody	"The lexicon and test suite have no business using a custom ad-hoc format.  Now that I know a perfectly acceptable lightweight standard language exists for this this thing (JSON), I should just use it to make life simpler for everybody.

Backward compatibility would be nice.  I guess we'll have to support both, maybe even extend geniconvert?

Macros file probably unchanged.  No real gain from JSON-ifying that.
Feature structures may be tricky.  We'll have to think about this a bit"	enhancement	closed	major		core		wontfix