This makes reading docs on the system it’s being installed on a PITA. Especially for the install, upgrade, and database guides which usually have to be referred to on install, why not provide them as text?
I don’t mean to sound whiny about a free product that works very well. I just noticed as I installed Openfire for probably the tenth time that I was thinking the same thing I thought every other time, and that I can’t be the only one.
thanks
Kevin
I can read (rendered) HTML far better then plain text, which gives you no formatting and no links.
So can I - if I’m working on a machine with a GUI and a browser and a console. I should have included that especially for Linux, Openfire will often be installed on a headless system, and even more often on a GUI-less and browser-less system.
I think it is mostly because of convenience to use same htmls to post docs on the website and to include in the installation package.