Re: [webkit-dev] MathML renderer

2011-01-05 Thread Dirk Schulze
Am 05.01.2011 um 06:14 schrieb Maciej Stachowiak: It might make sense to use subdirectories of rendering/, as svg has started to (although this seems incomplete - SVG folks, is the plan to move the remaining SVG-related rendering files from rendering/ to rendering/svg?). Yes it is on the

Re: [webkit-dev] libxml2 override encoding support

2011-01-05 Thread Patrick Gansterer
Alex Milowski: On Tue, Jan 4, 2011 at 7:05 PM, Alexey Proskuryakov a...@webkit.org wrote: 04.01.2011, в 18:40, Alex Milowski написал(а): Looking at the libxml2 API, I've been baffled myself about how to control the character encoding from the outside. This looks like a serious lack of

Re: [webkit-dev] Handling of feature dependencies

2011-01-05 Thread Konstantin Tokarev
Example from WinCE5: There's a limit of 32MB per process, so every byte is important. My case is similar (but 32 MB per device :) -- Regards, Konstantin ___ webkit-dev mailing list webkit-dev@lists.webkit.org

Re: [webkit-dev] Best way to track feature evolution from release-to-release

2011-01-05 Thread Tom Bahnck
Thank you. If my understanding is correct wrt to Apple's release process, when given the chance, Apple tags the WebKit trunk under the name Safari-### in the /tags directory. This contains all source from the WebKit trunk, including tools/bugzilla/test/etc. code. When making a Safari release,

Re: [webkit-dev] libxml2 override encoding support

2011-01-05 Thread Alex Milowski
On Wed, Jan 5, 2011 at 5:07 AM, Patrick Gansterer par...@paroga.com wrote: Is there a reason why we can't pass the raw data to libxml2? E.g. when the input file is UTF-8 we convert it into UTF-16 and then libxml2 converts it back into UTF-8 (its internal format). This is a real performance

Re: [webkit-dev] libxml2 override encoding support

2011-01-05 Thread Alex Milowski
On Tue, Jan 4, 2011 at 7:14 PM, Eric Seidel e...@webkit.org wrote: You should feel encouraged to speak with dv (http://veillard.com/) more about this issue. Certainly I'd love to get rid of the hack, but I gave up after that email exchange. In the shorter term, fixing this bug or lack of

Re: [webkit-dev] libxml2 override encoding support

2011-01-05 Thread Darin Adler
On Jan 5, 2011, at 5:07 AM, Patrick Gansterer wrote: Is there a reason why we can't pass the raw data to libxml2? Because libxml2 does its own encoding detection which is not even close to what’s specified in HTML5, and supports far fewer encodings. If you make a test suite you will see. On

Re: [webkit-dev] libxml2 override encoding support

2011-01-05 Thread Patrick Gansterer
Darin Adler: On Jan 5, 2011, at 5:07 AM, Patrick Gansterer wrote: Is there a reason why we can't pass the raw data to libxml2? Because libxml2 does its own encoding detection which is not even close to what’s specified in HTML5, and supports far fewer encodings. If you make a test

Re: [webkit-dev] Best way to track feature evolution from release-to-release

2011-01-05 Thread Darin Adler
On Jan 5, 2011, at 7:06 AM, Tom Bahnck wrote: If my understanding is correct wrt to Apple's release process, when given the chance, Apple tags the WebKit trunk under the name Safari-### in the /tags directory. This contains all source from the WebKit trunk, including

Re: [webkit-dev] libxml2 override encoding support

2011-01-05 Thread Darin Adler
On Jan 5, 2011, at 8:38 AM, Patrick Gansterer wrote: Darin Adler: On Jan 5, 2011, at 5:07 AM, Patrick Gansterer wrote: Is there a reason why we can't pass the raw data to libxml2? Because libxml2 does its own encoding detection which is not even close to what’s specified in HTML5, and

[webkit-dev] WebCore, WebKit, WebKit2 moving to Source this weekend

2011-01-05 Thread Adam Barth
People of WebKit, If the stars align, I'm going to move WebCore, WebKit, and WebKit2 to the Source directory this weekend. As with the JavaScriptCore move, I'll teach svn-apply how to apply patches that reference the old locations, which should help you avoid merge conflicts as before. Adam

[webkit-dev] JavaScriptCore Binding Problem

2011-01-05 Thread Alex Milowski
I've got a new IDL class I'm working of for some experiments in XML and I've run into an interesting snag. I have a call to a parse method from Javascript where the string argument seems to be getting mangled. The IDL for the method looks like: boolean parse(in DOMString str); and the