Comment 3 for bug 1656331

Bill, I think naming them after the class id as you suggest would be best, actually. First, it reinforces class id uniqueness, and second, it makes it easier for local git repos maintain tweaks to core classes.

Just to spitball about implementation ... Since we have TemplateToolkit as a dep, we could leverage the ttree tool to compile the monolith at will.

Seems i18n will need to learn to deal with (and add DTD includes to) each class file. That shouldn't be hard -- we do directories of files in the template area, no? We could just generate the &entity; files for the i18n-ized version, and when compiling the various monoliths, specify either the static directory or the &entity;-ized one, /and/ a customization directory. Caveat developer, re adding customizations with existing class names, of course, but that's the case today, too. The compiler could easily warn on errors of that kind.