On Aug 2, 2005, at 6:03 PM, Ken Krugler wrote:
Thanks for your work in this area! I assume it's RFC 2070 :)
Yes. :-)
1. Server doesn't provide any charset info.
Very common in my experience.
2. Server provides incorrect charset info.
a. Charset is a subset (e.g. 8859-1 vs. 1252)
b. Charset is just plain wrong (e.g. 8859-1 vs. 1251)
3. Server provides an invalid charset name.
a. Charset could be mapped, with a table (e.g. ".UTF8")
b. Charset is unknown (e.g. "X-USER-DEFINED").
Yes... I don't know about now, but a few years ago, the data that
*was* sent back from the server was, for the most part not worth
counting on.
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Nutch-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nutch-developers
