Hi, Is there someone can tell me how to change the ICU libraries as the icudt36.dll is too large? If this can do, how many files should be modify and what are the main files?
Best wishes -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, September 24, 2008 10:00 PM To: [email protected] Subject: webkit-dev Digest, Vol 40, Issue 25 Send webkit-dev mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev or, via email, send a message with subject or body 'help' to [EMAIL PROTECTED] You can reach the person managing the list at [EMAIL PROTECTED] When replying, please edit your Subject line so it is more specific than "Re: Contents of webkit-dev digest..." Today's Topics: 1. SQE PPC Support (Jon Shier) 2. Re: SQE PPC Support (Darin Adler) 3. Fwd: Rename TypeInfo -> JSTypeInfo? (Kevin Ollivier) 4. Re: Fwd: Rename TypeInfo -> JSTypeInfo? (David Kilzer) 5. Webkit unicode question (Sherif) 6. Re: Webkit unicode question (Alexey Proskuryakov) 7. iPhone + SVG (Nikolas Zimmermann) 8. Re: iPhone + SVG (David Kilzer) 9. Re: iPhone + SVG (David Hyatt) 10. Re: Webkit unicode question (Sherif) 11. Re: Webkit unicode question (Darin Adler) 12. Re: Fwd: Rename TypeInfo -> JSTypeInfo? (Kevin Ollivier) 13. Re: Fwd: Rename TypeInfo -> JSTypeInfo? (Maciej Stachowiak) ---------------------------------------------------------------------- Message: 1 Date: Tue, 23 Sep 2008 11:04:44 -0500 From: Jon Shier <[EMAIL PROTECTED]> Subject: [webkit-dev] SQE PPC Support To: [email protected] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="UTF-8" I'm interested in trying to add PPC support to the native code generation recently added, but I have a few questions. First, am I correct in thinking that some refactoring needs to be done before other architectures can be supported? Things like X86Assembler and whatnot seem to be architecture specific and would replicate code if an *Assembler was added for every arch. Is this being worked on, or would I have to do it as part of adding PPC support? Second, a bit of an overview on what would need to be done would be nice, since I've never worked with the JSC code before. Jon Shier ------------------------------ Message: 2 Date: Tue, 23 Sep 2008 09:10:02 -0700 From: Darin Adler <[EMAIL PROTECTED]> Subject: Re: [webkit-dev] SQE PPC Support To: Jon Shier <[EMAIL PROTECTED]> Cc: WebKit Development <[email protected]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes On Sep 23, 2008, at 9:04 AM, Jon Shier wrote: > First, am I correct in thinking that some refactoring needs to be > done before other architectures can be supported? We plan to do the refactoring as we add new architectures. The best person to talk to about that is Gavin Barraclough. The next architecture on the roadmap is X86-64. -- Darin ------------------------------ Message: 3 Date: Tue, 23 Sep 2008 09:11:19 -0700 From: Kevin Ollivier <[EMAIL PROTECTED]> Subject: [webkit-dev] Fwd: Rename TypeInfo -> JSTypeInfo? To: [email protected] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Hi all, I sent this message to the mailing list yesterday, but it seems it never made it, so I'm resending. Kevin Begin forwarded message: > From: Kevin Ollivier <[EMAIL PROTECTED]> > Date: September 22, 2008 12:13:24 PM PDT > To: [email protected] > Subject: Rename TypeInfo -> JSTypeInfo? > > Hi all, > > We're having a problem on the Windows version of wxWebKit where > #include <typeinfo> is actually now including JavaScriptCore/kjs/ > TypeInfo.h, which needless to say is not a good thing. ;-) I think > this problem stems from the fact that we (the wx port, that is) > don't use the 'framework' approach for JSC headers yet (and thus > need JavaScriptCore/kjs on our include path), but I think in general > it's good practice to avoid using system header names just for > readability purposes. Does anyone see a problem with renaming > TypeInfo to JS(C)TypeInfo, both header name and class? > > Thanks, > > Kevin ------------------------------ Message: 4 Date: Tue, 23 Sep 2008 09:32:20 -0700 (PDT) From: David Kilzer <[EMAIL PROTECTED]> Subject: Re: [webkit-dev] Fwd: Rename TypeInfo -> JSTypeInfo? To: Kevin Ollivier <[EMAIL PROTECTED]> Cc: [email protected] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=us-ascii Hi Kevin, The original message did make it to the list, but no one replied. I think the best approach is to simply create a bug on bugs.webkit.org and attach a patch for review (since the wx port is apparently the only one "feeling the pain" right now :). Dave On Tue, 9/23/08, Kevin Ollivier <[EMAIL PROTECTED]> wrote: > Hi all, > > I sent this message to the mailing list yesterday, but it > seems it > never made it, so I'm resending. > > Kevin > > Begin forwarded message: > > > From: Kevin Ollivier <[EMAIL PROTECTED]> > > Date: September 22, 2008 12:13:24 PM PDT > > To: [email protected] > > Subject: Rename TypeInfo -> JSTypeInfo? > > > > Hi all, > > > > We're having a problem on the Windows version of > wxWebKit where > > #include <typeinfo> is actually now including > JavaScriptCore/kjs/ > > TypeInfo.h, which needless to say is not a good thing. > ;-) I think > > this problem stems from the fact that we (the wx port, > that is) > > don't use the 'framework' approach for JSC > headers yet (and thus > > need JavaScriptCore/kjs on our include path), but I > think in general > > it's good practice to avoid using system header > names just for > > readability purposes. Does anyone see a problem with > renaming > > TypeInfo to JS(C)TypeInfo, both header name and class? > > > > Thanks, > > > > Kevin > > _______________________________________________ > webkit-dev mailing list > [email protected] > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev ------------------------------ Message: 5 Date: Tue, 23 Sep 2008 18:47:50 +0300 From: Sherif <[EMAIL PROTECTED]> Subject: [webkit-dev] Webkit unicode question To: [email protected] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Hello Guys, i want to ask, does webkit supports unicode? If not, is it possible to interfere it with python to support unicode? waiting your reply, regards, Sherif ------------------------------ Message: 6 Date: Tue, 23 Sep 2008 20:59:45 +0400 From: Alexey Proskuryakov <[EMAIL PROTECTED]> Subject: Re: [webkit-dev] Webkit unicode question To: Sherif <[EMAIL PROTECTED]> Cc: [email protected] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes On Sep 23, 2008, at 7:47 PM, Sherif wrote: > i want to ask, does webkit supports unicode? Yes. Are you interested in some particular aspect of Unicode support? I'm not sure how Python could be related to your question. > If not, is it possible to interfere it with python to support unicode? - WBR, Alexey Proskuryakov ------------------------------ Message: 7 Date: Tue, 23 Sep 2008 19:40:25 +0200 From: Nikolas Zimmermann <[EMAIL PROTECTED]> Subject: [webkit-dev] iPhone + SVG To: [email protected] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=US-ASCII; format=flowed Good evening WebKit crowd, I came around a page using SVG on the iPhone today, and I'm puzzled - it actually displays SVG content. That means, iPhone supports SVG?! Since when is it included? Must have been the last firmware update 2.1? It amazes me that I've not read an announcment anywhere about this. Would be great if someone from Apple could comment. Greetings, Niko ------------------------------ Message: 8 Date: Tue, 23 Sep 2008 11:42:48 -0700 (PDT) From: David Kilzer <[EMAIL PROTECTED]> Subject: Re: [webkit-dev] iPhone + SVG To: Nikolas Zimmermann <[EMAIL PROTECTED]> Cc: [email protected] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=us-ascii On Tue, 9/23/08, Nikolas Zimmermann <[EMAIL PROTECTED]> wrote: > I came around a page using SVG on the iPhone today, and > I'm puzzled - > it actually displays SVG content. That means, iPhone > supports SVG?! > Since when is it included? Must have been the last firmware > update 2.1? Yes, SVG was enabled in iPhone OS 2.1. Dave ------------------------------ Message: 9 Date: Tue, 23 Sep 2008 14:37:38 -0500 From: David Hyatt <[EMAIL PROTECTED]> Subject: Re: [webkit-dev] iPhone + SVG To: Nikolas Zimmermann <[EMAIL PROTECTED]> Cc: [email protected] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Yes, it was flipped on in 2.1. http://ajaxian.com/archives/svg-working-on-the-iphone dave ([EMAIL PROTECTED]) On Sep 23, 2008, at 12:40 PM, Nikolas Zimmermann wrote: > Good evening WebKit crowd, > > I came around a page using SVG on the iPhone today, and I'm puzzled - > it actually displays SVG content. That means, iPhone supports SVG?! > Since when is it included? Must have been the last firmware update > 2.1? > > It amazes me that I've not read an announcment anywhere about this. > Would be great if someone from Apple could comment. > > Greetings, > Niko > > _______________________________________________ > webkit-dev mailing list > [email protected] > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev ------------------------------ Message: 10 Date: Tue, 23 Sep 2008 23:28:49 +0300 From: Sherif <[EMAIL PROTECTED]> Subject: Re: [webkit-dev] Webkit unicode question To: Alexey Proskuryakov <[EMAIL PROTECTED]> Cc: [email protected] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Hi Alexey, the problem on the iphone starts to appear with arabic, farsi, and bangali website. Characters appear unconnected to each other without letter shaping. Could somebody give me a tip on how to fix it? thanks in advance, regards, Sherif Alexey Proskuryakov wrote: > > On Sep 23, 2008, at 7:47 PM, Sherif wrote: > >> i want to ask, does webkit supports unicode? > > > Yes. Are you interested in some particular aspect of Unicode support? > I'm not sure how Python could be related to your question. > >> If not, is it possible to interfere it with python to support unicode? > > - WBR, Alexey Proskuryakov > > > ------------------------------ Message: 11 Date: Tue, 23 Sep 2008 15:05:27 -0700 From: Darin Adler <[EMAIL PROTECTED]> Subject: Re: [webkit-dev] Webkit unicode question To: Sherif <[EMAIL PROTECTED]> Cc: WebKit Development <[email protected]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes On Sep 23, 2008, at 1:28 PM, Sherif wrote: > the problem on the iphone starts to appear with arabic, farsi, and > bangali website. Characters appear unconnected to each other without > letter shaping. Understood. You can report bugs in Apple products at http://bugreport.apple.com and that's the best thing to do about this case. But I happen to know that this is a known and understood limitation in current versions of Safari on iPhone. > Could somebody give me a tip on how to fix it? Fixing it is up to Apple's iPhone team. As a WebKit contributor there's nothing you can do or need to do to get this fixed. WebKit already has what's needed. -- Darin ------------------------------ Message: 12 Date: Tue, 23 Sep 2008 15:59:50 -0700 From: Kevin Ollivier <[EMAIL PROTECTED]> Subject: Re: [webkit-dev] Fwd: Rename TypeInfo -> JSTypeInfo? To: [EMAIL PROTECTED] Cc: [email protected] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Hi David, Okay, will do! Thanks, and sorry for the spam. I didn't see the message in my own list archives, which is why I thought it never made it. Now I just have to figure out what happened on my end. ;-) Kevin On Sep 23, 2008, at 9:32 AM, David Kilzer wrote: > Hi Kevin, > > The original message did make it to the list, but no one replied. > > I think the best approach is to simply create a bug on > bugs.webkit.org and attach a patch for review (since the wx port is > apparently the only one "feeling the pain" right now :). > > Dave > > > On Tue, 9/23/08, Kevin Ollivier <[EMAIL PROTECTED]> wrote: > >> Hi all, >> >> I sent this message to the mailing list yesterday, but it >> seems it >> never made it, so I'm resending. >> >> Kevin >> >> Begin forwarded message: >> >>> From: Kevin Ollivier <[EMAIL PROTECTED]> >>> Date: September 22, 2008 12:13:24 PM PDT >>> To: [email protected] >>> Subject: Rename TypeInfo -> JSTypeInfo? >>> >>> Hi all, >>> >>> We're having a problem on the Windows version of >> wxWebKit where >>> #include <typeinfo> is actually now including >> JavaScriptCore/kjs/ >>> TypeInfo.h, which needless to say is not a good thing. >> ;-) I think >>> this problem stems from the fact that we (the wx port, >> that is) >>> don't use the 'framework' approach for JSC >> headers yet (and thus >>> need JavaScriptCore/kjs on our include path), but I >> think in general >>> it's good practice to avoid using system header >> names just for >>> readability purposes. Does anyone see a problem with >> renaming >>> TypeInfo to JS(C)TypeInfo, both header name and class? >>> >>> Thanks, >>> >>> Kevin >> >> _______________________________________________ >> webkit-dev mailing list >> [email protected] >> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev ------------------------------ Message: 13 Date: Tue, 23 Sep 2008 19:01:35 -0700 From: Maciej Stachowiak <[EMAIL PROTECTED]> Subject: Re: [webkit-dev] Fwd: Rename TypeInfo -> JSTypeInfo? To: [EMAIL PROTECTED] Cc: [email protected] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes On Sep 23, 2008, at 9:32 AM, David Kilzer wrote: > Hi Kevin, > > The original message did make it to the list, but no one replied. > > I think the best approach is to simply create a bug on > bugs.webkit.org and attach a patch for review (since the wx port is > apparently the only one "feeling the pain" right now :). Since this change builds ok on other Windows-based ports, in my opinion it would be better to fix the Wx port's build system than to change the header name or class name. Regards, Maciej > > > Dave > > > On Tue, 9/23/08, Kevin Ollivier <[EMAIL PROTECTED]> wrote: > >> Hi all, >> >> I sent this message to the mailing list yesterday, but it >> seems it >> never made it, so I'm resending. >> >> Kevin >> >> Begin forwarded message: >> >>> From: Kevin Ollivier <[EMAIL PROTECTED]> >>> Date: September 22, 2008 12:13:24 PM PDT >>> To: [email protected] >>> Subject: Rename TypeInfo -> JSTypeInfo? >>> >>> Hi all, >>> >>> We're having a problem on the Windows version of >> wxWebKit where >>> #include <typeinfo> is actually now including >> JavaScriptCore/kjs/ >>> TypeInfo.h, which needless to say is not a good thing. >> ;-) I think >>> this problem stems from the fact that we (the wx port, >> that is) >>> don't use the 'framework' approach for JSC >> headers yet (and thus >>> need JavaScriptCore/kjs on our include path), but I >> think in general >>> it's good practice to avoid using system header >> names just for >>> readability purposes. Does anyone see a problem with >> renaming >>> TypeInfo to JS(C)TypeInfo, both header name and class? >>> >>> Thanks, >>> >>> Kevin >> >> _______________________________________________ >> webkit-dev mailing list >> [email protected] >> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev > _______________________________________________ > webkit-dev mailing list > [email protected] > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev ------------------------------ _______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev End of webkit-dev Digest, Vol 40, Issue 25 ****************************************** _______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
