GNOME Bugzilla – Bug 348778
Help system (yelp) not implemented on Windows
Last modified: 2009-05-10 13:51:56 UTC
The welcome message when first starting up Evolution invites me to press F1 for help - this doesn't seem to do anything. Disk spins for about a minute then nothing happens, not even a failure dialog (ie help not installed/working).
Can't reproduce. F1 fires off yelp, displaying the "Evolution User Guide". WORKSFORME, Evolution 2.6.2, GNOME 2.14.2. Linux. Note that Richard is running Evolution 2.6.2 on windows XP SP2. The Evolution help uses Yelp, the GNOME help application. Do you even have Yelp installed? Cc'ing Tor. NEEDINFO. No help available on the current Windows builds likely is to be expected.
Yelp hasn't yet been ported to Windows. I don't recall if I even had a look at it; quite possibly it depends on something that's "hard" to port. Changing the Summary to be more descriptive. Also accepting the bug, although whether I will actually be allocated time to work on it is another matter.
As guenther says on IRC, a more natural approach than porting yelp might be to make the help files viewable with the system default web browser instead, i.e. generate HTML from them.
Actually, that's not quite true. ;) I wondered out loud, if this is a port of *Evolution* to Windows, or a port of *GNOME*. If this is a port of Evolution, we probably should use the OS/Desktop default way for displaying help. Which would mean, using the Windows help system, rather than porting Yelp. The "browser" part was just an analogy. Evolution ported to Windows uses the Windows default browser when clicking on HTTP links, right? It does not depend on gnome-preferred-applications-properties (or control-center in general), but uses the Desktop defaut. The same likely should apply to the help system...
*** Bug 353397 has been marked as a duplicate of this bug. ***
*** Bug 368398 has been marked as a duplicate of this bug. ***
*** Bug 426231 has been marked as a duplicate of this bug. ***
*** Bug 526622 has been marked as a duplicate of this bug. ***
*** Bug 545255 has been marked as a duplicate of this bug. ***
Bug 576478 has more recent information about this problem. Closing as duplicate. *** This bug has been marked as a duplicate of 576478 ***