April 3rd, 2005
|
| A reader, not an expert | | Join Date: January 11th, 2003 Location: Canada
Posts: 4,613
| |
Here's the best I could find about the kinds of searches and characters allowed. http://www.the-gdf.org/wiki/index.ph...ng_the_Network Quote:
The Search Criteria is text, and it has never been specified which charset that text was encoded with. Therefore, servents MUST assume it is pure ASCII only. If any byte with the 7th bit set (high bit) is found, then either there is a GGEP extension specifying the encoding used, or the servent SHOULD guess the proper encoding. Most likely, it will be ISO-latin-1 or UTF-8.
Exactly how to interpret the Search Criteria is not specified either, but here are some guidelines for interoperability between servents:
The Search Criteria is a string of keywords. A servent SHOULD only respond with files that has all the keywords. It is RECOMMENDED to break up the words on any non-alphanumeric characters (anything but letters and numbers). A space is the standard separator between words.
Servents MAY also require that all matching terms be present in the same number and order as in the query.
Regular expressions are not supported and common regexp "meta- characters" such as "*" or "." will either stand for themselves or be ignored. The matching SHOULD be case insensitive. Empty queries or queries containing only 1-letter words SHOULD be ignored.
| So, looks like a # character will cause a break in the search terms sent, or be ignored if it is a single letter.  |
Similar Threads 
Threaded Mode
