2.3.3 Documentation, page 243
In the toolbar search field as well as in both the interactive and the simple web interface you can use
standard and extended Boolean operators, parenthesis, and more to fine-tune your search.
The syntax of the operators is compatible to DEVONagent and EasyFind, the Finder, Spotlight, common
search engines as well as common programming languages such as C, C++, Objective-C, Java, and
All terms are case-insensitive. You may, if you wish, use capitalization for proper names in a query, but
DEVONthink Pro Office will ignore case in interpreting the query.
PRECEDENCE OF TERMS
Search terms and associated operators will be interpreted from left to right, except as modified by
including portions of the query within parentheses.
You can replace parts of words with wildcards matching one, multiple, or a range of characters:
• ?: Matches exactly one character.
• *: Matches none, one, or multiple characters.
• [a-b]: Matches one character of the range 'a' through 'b'.
• [abc...] or [a|b|c|...]: Matches one character out of the given list of characters.
• [^...]: Matches one character that is not contained in the given list or range.
The operators (often called Boolean operators) are words or symbols that establish logical rules for the
terms in the search query. If no operator is given, DEVONthink Pro Office implies AND. The available
Boolean operators are:
• term1 AND term2: Contains term1 AND term2
• term1 BUT term2: Contains term1 AND term2
• term1 OR term2: Contains term1 OR term2
• term1 XOR term2: Contains term1 or term2, but not both
• term1 EOR term2: Contains term1 or term2, but not both
• NOT term: Does not contain term
• "term1": Contains the string term1, in exactly this form
Beside the classic Boolean operators, DEVONthink Pro Office uses a number of operators that can
usually only be found on high-end databases. Use them as a replacement for AND and "quotes" to fine-
tune your query.
• term1 OPT term2: term1 needs to occur, term2 can. If term2 does, the found document
ranks higher in the search results.
• term1 NEAR term2: term1 occurs 10 words or less before or after term2
2.3.3 Documentation, page 244
• term1 NEAR/n term2: term1 occurs n or less words before or after term2
• term1 BEFORE term2: term1 occurs before term2
• term1 BEFORE/n term2: term1 occurs n or less words before term2
• term1 NEXT term2: term1 occurs right before term2 (shortcut for BEFORE/1)
• term1 NEXT/n term2: term 1 occurs n or less words before term2 (synonym for BEFORE/n)
• term1 AFTER term2: term1 occurs after term2
• term1 AFTER/n term2: term1 occurs n or less words after term2
• ~term1: Contains all words that begin or end with term1 (words containing term1 as a part
of the word; depends on the queried search engine)
For convenience, some of these operators can also be abbreviated using commonly used symbols:
• AND: &, &&, +
• OR: |, ||
• XOR: ^, ^^
• NOT: !, -
Note: The symbols above are also used by the Finder and Mac OS X's Spotlight for searches.
Enter the vertical ruler character for the OR operator by pressing Option-7 (e.g. on
Operators are evaluated in the following priority: parenthesis > phrase/hyphens > (NOT) BEFORE/
AFTER/NEAR/NEXT > NOT > AND/OR/XOR/EOR. Terms with same priority but without parenthesis
are evaluated from left to right.
DATE COMPARISON OPERATORS
For comparing dates in smart groups the following operators are available:
• < date: Matches items that were created/edited/viewed before date.
• <= date: Matches items that were created/edited/viewed before or on date.
• >= date: Matches items that were created/edited/viewed after or on date.
• > date: Matches items that were created/edited/viewed after date.
WHITE SPACE HANDLING
Words concatenated by non-white separators (e.g. www.devon-technologies.com or page_id) are treated
like phrases put into "quotes". Words separated by hyphens are handled like word1word2 OR "word1
word2". Characters separated by dots are considered to be abbreviations and therefore handled like
words separated by hyphens, e.g. the term t.a.t.u is equal to "t a t u" OR tatu
Using any or all of the operators and rules layed out above you can create complex queries that find
exactly what you are looking for. Here are some example queries that show how the operators are used.
Example: Devonian Dinosaurs
This query looks for all documents that contain the words 'devonian' and 'dinosaurs'.
Example: (Steve NEAR Jobs) AND iMac BUT NOT MacBook OPT Pro
How to C#: Basic SDK Concept of XDoc.PDF for .NET
PDFTextMgr. This class provides APIs to manipulate text contents in a PDF document. OutLines. This class describes bookmarks in a PDF document. export bookmarks from pdf to excel; add bookmarks to pdf reader
2.3.3 Documentation, page 245
This query looks for documents that contain the words 'Steve' and 'Jobs' not farther away from each
other than ten words as well as the word 'iMac' (no specific position relative to Steve and Jobs) but not
the word 'MacBook'. The word 'Pro' does not need to occur but if it does, the document is ranked higher
in the list of search results.
Example: Paracetamol NEAR (~effect OR impact) AND ((side OR second*) NEAR/2 ~effect)
This query looks for documents containing the word 'Paracetamol' near (within ten words) to words
either starting with 'effect' (and so also 'effects') or being 'impact'. In addition, the document needs to
contain the word 'side' or any word staring with 'second' within two words range from any word starting
VB.NET PDF: Basic SDK Concept of XDoc.PDF
PDFTextMgr. This class provides APIs to manipulate text contents in a PDF document. OutLines. This class describes bookmarks in a PDF document. export pdf bookmarks to text file; split pdf by bookmark
2.3.3 Documentation, page 246
TEMPLATE TAGS FOR WIKI-STYLE LINKS
In DEVONthink Pro Office you can create new documents by first selecting some text in a rich text
document and then making it a link using the contextual menu. When you then click this link,
DEVONthink Pro Office creates the new document using a template you set in the Editing Preferences.
In this template, can use the tags below to automatically insert the name of the link, the current date or
other information. See also p. 74ff
• %@: Name of link
• %%: A '%' character
• %a: Abbreviated weekday name
• %A: Full weekday name
• %b: Abbreviated month name
• %B: Full month name
• %c: Shorthand for 'g%X %x,' the locale format for date and time
• %d: Day of the month as a decimal number (01-31)
• %e: Same as %d, but does not print the leading 0 for days 1 through 9
• %F: Milliseconds as a decimal number (000-999)
• %H: Hour based on a 24-hour clock as a decimal number (00-23)
• %I: Hour based on a 12-hour clock as a decimal number (01-12)
• %j: Day of the year as a decimal number (001-366)
• %m: Month as a decimal number (01-12)
• %M: Minute as a decimal number (00-59)
• %p: AM/PM designation for the locale
• %S: Second as a decimal number (00-59)
• %w: Weekday as a decimal number (0-6), where Sunday is 0
• %x: Date using the date representation for the locale, including the time zone
• %X: Time using the time representation for the locale
• %y: Year without century (00-99)
• %Y: Year with century (such as 1990)
• %Z: Time zone name (such as Pacific Daylight Time)
• %z: Time zone offset in hours and minutes from GMT (HHMM)
2.3.3 Documentation, page 247
DEVONthink Pro Office stores a large number of metadata fields internally when importing documents
from the file system, e.g. from PDF, RTF, MP3, EXIF/IPTC, HTML, and email messages as well as from
all files that deliver metadata through the Spotlight metadata importer. Here's an (incomplete) list of
theoretically supported fields:
PDF and RTF:
• Author email addresses
• Recipient email dddresses
• Email addresses
2.3.3 Documentation, page 248
Release schedules, Mac OS X, and Windows
Mac App Store
Your software license
Do you have questions regarding our licensing policy, our products in the Mac App Store, or specific
questions about DEVONthink Pro Office?
2.3.3 Documentation, page 249
Do you have any job opportunities? Yes, we may. Please visit our Work @ DEVONtechnologies page
for more information about current open jobs at DEVONtechnologies.
Can I be a beta tester? Maybe. Our beta tester selection process is very deliberate; we try and select
our beta testers carefully so that we're not wasting anybody's time, yours and ours. We're looking for
people who can provide us with feedback quickly and clearly, who use different hardware and software
from our other testers, and who are willing to send us their personal data if it's needed for debugging.
If you want to be a beta tester, the best way to catch our eye is to be active in our user forums. We often
ask active participants on the user forums if they can help us test particular features and new products.
You can, of course, simply contact us.
Is the documentation available in my language? The online and PDF documentation is only
available in English at the moment. Localizing documentation and other text-intensive materials to
Deutsch, Francais, etc. is cost-intensive and error-prone so that we have decided to concentrate our
resources on developing stable, robust, and feature-rich software. We will have localizations of the
online help etc. as soon as we feel we have the necessary resources.
Where does the name DEVONtechnologies come from? "Devonian (after Devon County, England),
the geologic period from 410 to 360 million years ago. Also called the Reptile Age or Age of Fishes. First
amphibians appeared on the land, that until then was only inhabited by trees and other plants — it
was the departure into a new age." Named after the Devonian period, the DEVONtechnology marks the
departure into a new age of data processing.
Note: Ray Troll has even created songs and other art about this extremely important
2.3.3 Documentation, page 250
RELEASE SCHEDULES, MAC OS X, AND WINDOWS
When is the next release coming We try not to announce precise timelines or feature lists for future
releases, as we are a small software company with limited development resources; if one of us should
happen to get the sniffles, or if there are other outside factors we need to devote our limited time to, it
can easily impact our intended development schedules.
In planning releases, we try to strike a balance among:
• responding to customer requests,
• the needs of our partners,
• supporting new operating systems features,
• providing consistent features across the product line,
• working efficiently within the structure of the code, (similar features often get handled at
the same time),
• various business needs.
We cannot make any assumptions on how those various factors will impact our daily workflow; in fact,
it's often impossible to predict the final release date accurately when we start new projects. We try to
plan our releases with a long term perspective so that they ultimately serve the needs of our customers,
even if they don't necessarily get in everyone's favorite feature request every time.
Why are your applications not compatible with my pre-release version of Mac OS X? In the
past, we've noted that compatibility issues with a new major release of the operating system are usually
resolved by Apple in the final stages before its release, and don't require any action on our part. If
you are already using a pre-release version of Mac OS X, please check if our applications work with a
newer pre-release, or wait until it reaches the release candidate status. We will then make all necessary
adjustments for making our apps run on the first official release of the new version of Mac OS X.
Any chance of a Windows versions of your products? We're very commited to Mac OS X and the
superior Cocoa environment. For most of our applications, porting them to Windows would take longer
than it would to rewrite them from scratch on the Mac. If you need to use Windows software but still
don't want to miss our products consider running Windows on a Mac.
Documents you may be interested
Documents you may be interested