Stephan Bergmann-2 wrote > > Not sure we need either this dialog box or any localization at all: > > On other platforms, soffice -h outputs to stdout (or maybe stderr). > Given that adding command line arguments (what soffice -h educates > about) is presumably done mostly through some terminal, anyway, I'm not > sure there is any demand to display this help information in a dialog > instead of on stdout/err. I don't know what the current status of GUI > applications like soffice routinely printing to stdout/err is on current > Windows versions, so I don't know if this hack to use a dialog is still > needed. (The unopkg executable used to go to pains to be able to use > stdin/out/err even though it is a GUI application, wrapping unopkg.exe > in a unopkg.com that does the necessary console magic.) >
As a long time Windows "Power User", I agree with this comment and also with Tor's comments on the Bug report mentioned. If a Windows user is knowledgeable enough to pass command line switches (in my experience that would be 1% or less :) ) he expects the output of such switches to be displayed as text on the terminal window (aka DOS box :) ) Otherwise any other Help that requires a GUI, l10n and formatting belongs in the Help file Just my 2 (non-dev) cents. -- Pedro -- View this message in context: http://nabble.documentfoundation.org/UI-disaster-on-Windows-soffice-h-tp3641073p3644284.html Sent from the Dev mailing list archive at Nabble.com. _______________________________________________ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
