On Sat, Nov 7, 2009 at 9:55 AM, Jürgen Spitzmüller <[email protected]> wrote: > Uwe Stöhr wrote: >> > Fortunately, Jürgen's work will improve this situation a good deal for >> > 1.7. But we still have, and will still have, the question what should be >> > the default. >> >> This issue can only be solved by treating the HTML converters like we >> already treat the PDF converters. > > Why don't you think my approach does not solve this?
Let me answer that. Your approach is a long-term solution to the problem (for the 1.7 or 2.0 timeframe), but unfortunately we don't know when it's going to be ready. (And it's hard enough that not many people can help, at least now I know I cannot. And I very much like your solution -- having a different format for every converter like html1, html2 is ugly as a mountain troll.) Meanwhile it would not hurt to configure in all HTML converters for 1.6.x and let the user decide which one to use. There would be a certain amount of menu clutter for some users, sure, but it's not that bad. It might also encourage other people to see the clutter problem and lend a hand. In case nobody is bothered to change the status quo it would mean that the clutter problem is not bad enough. So we have a dirty short-term solution (at the expense of menu clutter) and a clean long-term solution (at the cost of having to wait a little longer). Given that the dirty solution does not collude with the long-term solution, or does not make it any harder for its implementation, and that it can be removed in a second without impacting any other developments, I think both have their place. Let me know if I am missing anything. Alex.
