- Google Chrome
Dubsar Mobile has been tested on an array of iOS and Android devices. Except as noted in the Dubsar issue list , the application is known to work well in all tested mobile environments.
WordA dictionary entry with a unique name and part of speech.
SenseThe intersection (or join table, in database terms) of words and synsets. Each occurrence of one word in one synset is a sense of that word. A sense is a specific meaning of a single word.
PointerA lexical or semantic relationship between senses or synsets. A lexical pointer points from one sense to another (one specific meaning of one word to a specific meaning of another word). A semantic pointer points from one synset to another and hence relates two meanings. There are many specific pointer types.
- lexical file name
- broad categories associated with each word sense
- adjective marker
- for some adjective senses, a limitation on the syntactic position of the adjective when used in this sense (see below)
- frequency count
- number of times this word sense occurs in a reference text
- verb frames
- generic sentence frames applicable to this verb sense
- sample sentences
- sample sentences for the synset
Adjective markersSome adjective senses may only be used in certain syntactic positions:
- (a) attributive The left side of the road.
- (ip) immediately postnominal I live in the city proper.
- (p) predicate It is well he did not go.
|one way of saying it
|another way of saying it
|words opposite in meaning
|more generic terms
|classes of which this is an instance
|more specific terms
|instances of this class
|wholes of which this is a member
|wholes of which this is an ingredient
|wholes of which this is a part
|derivationally related form
|domain of synset (topic)
|member of this domain (topic)
|entries under this topic
|domain of synset (region)
|member of this domain (region)
|things relevant to this region
|domain of synset (usage)
|pertinent to usage
|member of this domain (usage)
|relevant by usage
|origin or reason
|near in meaning, but not exact
|participle of verb
|derived from/pertains to
|adj: pertinent noun; adv: source noun
A. All search results use full text searching, similar to the behavior of most search engines, against the inflections table. All searching is case-insensitive. Results include all search terms. An asterisk (*) may be used to match any non-whitespace string, including nothing. Certain operators may also be used, in all uppercase, like "law OR order." Exact matches (results where the matching inflection is exactly the search term as it was typed) are sorted to the top. Other results are sorted in ASCII order, so all capital letters come before all lowercase letters.
The autocompleter results are determined by looking first for an exact match, then by searching for search terms*, i.e., appending an asterisk to the search terms. So if you type in frus, which has no exact match, you will see the results of searching for frus*, which returns all results containing a term beginning with frus.
Exact matching is case-sensitive, so if you search for Fruit, the word fruit will not appear at the top of the list. In fact, it will not show up in the autocompleter at all. If you perform a search for Fruit, fruit will appear sorted in with the rest of the results.
A. Yes. Dubsar uses two cookies, one of which is persistent:
|store the user's choice of light or dark display theme
|maintain session state (used by Ruby on Rails®)
The only persistent cookie Dubsar uses is dubsar_theme, which simply registers your choice of display theme. The first time the page is visited, this cookie is set to "light." It has a lifetime of thirty days.
The other cookie is transient, limited to a single browser session.
Dubsar has no knowledge of your identity when you visit the site. There is no authentication, no login, no user ID. The _dubsar_session cookie identifies you to the server in an anonymous way, which is useful, for example, when returning error messages. This is a standard technique, and it's built into Ruby on Rails®.
A. The OpenSearch protocol allows some supported browsers (Internet Explorer 8, Firefox and Google Chome) to add Dubsar to the browser's list of search engines so that you can search Dubsar, complete with live suggestions, from your browser's search bar. The browser will recognize Dubsar's OpenSearch plug-in on its own. Chrome automatically adds all discovered search providers. Firefox will prompt you by highlighting the search-provider combo box.
See Wikipedia for more information.
A. Contact firstname.lastname@example.org for any technical support issues.
A. Dubsar searches now work similarly to most search engines.
- All searching is case-insensitive.
- Search results will include anything that contains all search terms.
- An asterisk (*) stands for any non-whitespace string (including nothing). So searching for count* matches anything containing a discrete term that begins with count.
- Certain operators are recognized in all caps (e.g., law OR order ).
- Results are sorted in ASCII order, with all capital letters coming before all lower-case letters. But case-sensitive exact matches (including inflections) are sorted to the top.