Hello Tuheen,
> 1. If someone is writing a brand new port for WebKit,
> should he first ensure that he is able to get all these
> libs for his platform? Is there any other way out?
Especially for the libicu functionality, there is a way out if you find
a way to implement the same functionality using platform unicode/text
libraries.
https://bugs.webkit.org/show_bug.cgi?id=15914 shows a way to do this on
platforms where glib is availble. On Symbian, I would assume it's
possible, too. Symbian has support for a large variety of text codecs
and supports UCS2 natively. The patch attached to the bug report might
give you an idea of which parts of the webkit codebase need to be
changed.
For libxml2, it looks like the qt port has integrated its own xml parser
(see XMLTokenizer.cpp and the #ifdef'ed sections for USE_QXMLSTREAM). It
might be possible to replace WebKit's libxml2 dependency by a
stream-based XML parser available on Symbian (if you can find one that
has publicly documented API). However, you will most probably lose the
capability of doing xslt transformations, as libxml2 and libxslt's data
structures are closely linked.
Regards,
Dominik
_______________________________________________
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
