jumpstart book does not support different modules per lingua

[Kyle Nitzsche]

The modules file in a jumpstart book lists the paths to modules that are remixed into localized books when the book is built.

However, there are cases where different locales need different a different set of modules. For example, if writing a book about Ubuntu, the CJK locales would want a module on input methods, but this would not be needed for other locales.

[Kyle Nitzsche (knitzsche)]

One can accomplish this manually as follows:
 * build the book multiple times
 * between each build, set modules file as desired for the target linguas, and set the LINGUAS file to list those target linguas.

One might therefore have the following files:
 * modules (the default set of modules)
 * modules.cjk (the set of modules appropriate for cjk linguas)
 * LINGUAS (contains all llinguas except cjk linguas)
 * LINGUAS.cjk (contains cjk linguas)

Build it twice as follows:
doctemplate_make jumpstart # this builds all non-cjk linguas
mv modules modules.orig; mv modules.cjk modules # set up modules for cjk
mv LINGUAS LINGUAS.orig; mv LINGUAS.cjk LINGUAS # set up LINGUAS for cjk
doctemplate_make jumpstart # build for cjk
mv modules.orig modules # restore modules
mv LINGUAS.orig LINGUAS # restore LINGUAS

The question is whether the doctemplate should handle this or whether this degree of manual intervention is appropriate

One can create multiple modules files, named for example with an extension that specifies the locale, like modules.CJK. The 'modules' file has the default set of modules. build the build with a LINGUAS file that contains target linguas but no CJK linguas.

One can also have multiple LINGUAS files, for example LINGUAS (which contains all target linguas except zh_CN), and LINGUAS.zh_CN (which contains Then one