On Wed, 11 Feb 2004, Radovan Garabik wrote:
> I know, but that does not solve the original problem - if the page
> I want to pluck uses e.g. iso-8859-2 repertoire and it has a link to page that
> uses iso-8859-1 (or koi8-r or anything, or even worse, characters from more
> codepages). As I said, support in plucker is _almost_ there and I am willing
> to work on it - but only if there is an interest in developpers' comunity
> to include the support in plucker.
One concern is that if we roll our own solution for this, then along may
come a future OS version with native Unicode support. We could just wait
for that. In fact, I think that if a future OS version with native
Unicode support comes along, we're basically ready. Plucker has full
multi-byte char support. If the OS uses that mechanism for unicode, it'll
be just a matter of updating the parser.
The number of users who need to pluck sites that use multiple code pages
in ways that matter. For most English pages, for instance, it is no
disaster if you pretend the page is in some other encoding--at most a few
characters will be mixed up--and one expects that most, though not all,
multilanguage plucks are going to be Some Other Language plus English,
rather than two non-English languages. So I am not sure that it is worth
supporting this. It may slow down rendering. It will make maintenance
more work for all the developers.
Alex
--
Dr. Alexander R. Pruss || e-mail: [EMAIL PROTECTED]
Philosophy Department || online papers and home page:
Georgetown University || www.georgetown.edu/faculty/ap85
Washington, DC 20057 ||
U.S.A. ||
-----------------------------------------------------------------------------
"Philosophiam discimus non ut tantum sciamus, sed ut boni efficiamur."
- Paul of Worczyn (1424)
_______________________________________________
plucker-dev mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
