Comment #6 on issue 8198 by [email protected]: Need to upgrade ICU in third_party http://code.google.com/p/chromium/issues/detail?id=8198
The last one was fixed by back-porting the change made in ICU trunk to our copy of ICU 3.8. Two other issues (both RE) were not back-ported. For Chrome 2.0 release, I think we should just go with ICU 3.8 (there are a lot of portings to do if we want to upgrade 4.x.) and back-port fixes for two above. For post-2.0, we should go directly to ICU 4.2 (that will be released soon) and get rid of a bunch of back-ports. BTW, in the chrome-proper (outside Webkit), we don't use RE iirc. Of course, we can use it any day :-) Mac OS X 10.4 has ICU 3.2 (really old) and 10.5 has ICU 3.6. Apple may or may not have ported security fixes (like invalid sequences in an MBCS being a potential XSS attack vector). As agl wrote, I guess Safari on Win comes with ICU 4.0 -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
