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
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
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 specifi
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
> tools/bugzilla/te
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
>
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.
O
On Tue, Jan 4, 2011 at 7:14 PM, Eric Seidel 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 feature" in
On Wed, Jan 5, 2011 at 5:07 AM, Patrick Gansterer 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
> problem whe
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,
> 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
http://lists.webkit.org/mailman/listi
Alex Milowski:
> On Tue, Jan 4, 2011 at 7:05 PM, Alexey Proskuryakov 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
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 t
12 matches
Mail list logo
