Forgive me if I am wrong. This is a proposal.
For what I can read from the man tidy (see red arrow), and if this is relevant to the integrated Tidy we have within Sigil, it seems that it would be enough for Sigil to create some permanent tidyconfig.ini (or any other name) file and to document its creation in its code. Normally, this file would stay blank ( or contain all the configuration options currently enacted...).
However, if need be, the user could write its own configuration options on this file (or just modify some pre-set values).
Last edited by roger64; 05-29-2013 at 10:48 AM.
|