Use 'icu::' namespace explicitly

Use 'icu::' namespace explicitly throughout Chrome tree instead of relying on 'using namespace icu'.

This is Chrome's counterpart to the ICU header change that disables
'using namespace icu' (http://codereview.chromium.org/171010/show), which is required to avoid the name colission between Chrome's StringPiece (in base) and ICU's StringPiece.

The webkit change (which is minor) will be dealt with in the webkit bugzilla.

This can go in before the ICU change/upgrade without affecting anything. 


BUG=8198
TEST=All the targets are built without an error on all platforms.

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=23613

[jungshik at Google, 2009-08-15 08:28:14]

I'll also send an email to chromium-dev to announce that C++ names of ICU must
be qualified with 'icu::'.

[darin (slow to review), 2009-08-16 18:58:18]

LGTM

[Mark Mentovai, 2009-08-16 19:48:31]

http://codereview.chromium.org/171012/diff/54/1012
File net/base/net_util.cc (right):

http://codereview.chromium.org/171012/diff/54/1012#newcode592
Line 592: "[[\\u0020\\u00bc\\u00bd\\u01c3\\u0337\\u0338"
You're losing "\\ " from the set here.  Intentional?

[jungshik at Google, 2009-08-17 04:08:40]

http://codereview.chromium.org/171012/diff/54/1012
File net/base/net_util.cc (right):

http://codereview.chromium.org/171012/diff/54/1012#newcode592
Line 592: "[[\\u0020\\u00bc\\u00bd\\u01c3\\u0337\\u0338"
On 2009/08/16 19:48:31, Mark Mentovai wrote:
> You're losing "\\ " from the set here.  Intentional?

I didn't mean to include this part in the CL, but it seems harmless.

Anyway, '\\ ' is to represent 'SPACE' (U+0020). '\\ ' is turned to '\ ' in
memory and passed to UnicodeSet ctor, which does its own string escaping to get
' ' (U+0020).  Yeah, it's confusing. 

 The previous code is a bit fishy with '\uXXXX' although it worked (otherwise,
unittest would have failed). 

 To avoid the confusion,  '\\u0020' is used in its place.