- transcode_import_modules(1), documenting import modules, options,
gotchas and quirks
- transcode_filter_modules(1), same as above for filters
- transcode_export_modules(1), same as above for export modules
transcode_import transcode_export transcode_filter?
Some of us have RSI... :)
An alternative is to split each module off into its own page
export_mp2 and so on.
{import,export,filter}_* is unusual enough not to need transcode_
prefixed, as well as reflecting the file names.
That might encourage people to document better what the filters do how
to use them. That would also enable us to install the manual pages for
the modules that are actually included in a particular installation,
and if, as you say, they can autogenerated that might be easier to
implement and maintain.
One thing though, an option "transcode -[xyJ] help", to list the
available modules, would be an improvement on "ls
/usr/.../transcode/import_*" and similar.
Of course, the real answer is to convert everything to docbook, then
generate "info" pages, manual pages and a printable manual from those,
but that's a lot of work...
M
