-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Should be able to disable "2nd class" outputs in admin settings #1154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I agree. I'm not sure of the statistics of the number of users producing pdf/epub output, but i think exposing these as options some how to the user would reduce confusion -- especially since pdf builds can be intermittent problematic in our build evironment. We're trying to reduce the config options, as the user experience is awful, but this might be a large enough configuration option to warrant a UI element for configuration. |
@agjohnson it seems like pdf/epub are defaulted to on, so wouldn't it be all projects end up producing those? Or am I missing something? |
@tisdall i suppose i meant using pdf output, this is the number I'm not sure of. You are correct that all projects default with pdf/epub output enabled. |
Our builder code knows how build all the types separately. The main thing On Wed, May 6, 2015 at 1:57 PM, Anthony [email protected] wrote:
Eric Holscher |
This is done with the merge of #1344. |
@gregmuellegger, thank you! |
At the moment, PDF and ePub formats are "2nd class" outputs of the system, in that the author does not get notified of production failures specific to those formats. (see, e.g. #1121 which impacted users as described in #1120)
Since lossless conversion to the 2nd class formats can't be guaranteed, an author may need to invest additional time to produce source that will convert cleanly. I think that choice should be up to the author, not a (hidden) cost of using read the docs.
Adding checkboxes to enable/disable production of these alternate formats to the administration page would be one way to implement.
The text was updated successfully, but these errors were encountered: