Bug 51697 - gdict is not finding all definitions
Summary: gdict is not finding all definitions
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: gnome-utils   
(Show other bugs)
Version: 7.3
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Alexander Larsson
QA Contact: Ben Levenson
Depends On:
TreeView+ depends on / blocked
Reported: 2001-08-13 23:20 UTC by Michal Jaegermann
Modified: 2007-03-27 03:48 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-08-15 19:50:19 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Michal Jaegermann 2001-08-13 23:20:27 UTC
Description of Problem:
'gdict' asked to show definitions stops on the first dictionary.
Neither 'kdict', nor a command line 'dict', suffer from the same

I have 'localhost' configured as a dict server, bunch of dictionaries
and clients directed accordingly.  For example for a word "basic"
five definitions should be found (in Webster, WorldNet 1.7, Jargon,
foldoc and VERA).  'gdict' stops on the first one which happens
to be (in my configuration?) a chemical meaning from Webster.
Similarly with "font" four definitions should be found with two
different ones in Webster plus in WN and foldoc.  This is not
the result.

When asked to show a definition from a specific dictionary, instead
of "all", then gdict does not have any problems and shows _both_
"font" definitions from Webster; but picking up explicitely
dictionaries from "Settings->Preferences" and clicking on "Apply"
grows old pretty quick.

Comment 1 Alexander Larsson 2001-11-26 21:25:32 UTC
I moved this bug to the gnome bugtracker where the gdict authors can see it.
The bug is availble at http://bugzilla.gnome.org/show_bug.cgi?id=65441

If you want to keep up to date with the bug, please add yourself to the CC line
of it.

Note You need to log in before you can comment on or make changes to this bug.