Revision: 16773
Author:   [email protected]
Date:     Tue Sep 17 13:04:41 2013 UTC
Log:      Initial commit
http://code.google.com/p/v8/source/detail?r=16773

Added:
 /wiki/I18NSupport.wiki

=======================================
--- /dev/null
+++ /wiki/I18NSupport.wiki      Tue Sep 17 13:04:41 2013 UTC
@@ -0,0 +1,46 @@
+#summary Controlling i18n (ECMAScript 402) support in V8
+
+= ECMAScript 402 =
+
+V8 optionally implements the [http://www.ecma-international.org/ecma-402/1.0/ ECMAScript 402] API. The API is enabled by default, but can be turned off at compile time.
+
+
+== Prerequisites ==
+
+The i18n implementation adds a dependency on ICU. If you run
+
+{{{
+make dependencies
+}}}
+
+a suitable version of ICU is checked out into {{{third_party/icu}}}.
+
+
+=== Alternative ICU checkout ===
+
+You can check out the ICU sources at a different location and define the gyp variable {{{icu_gyp_path}}} to point at the {{{icu.gyp}}} file.
+
+
+=== System ICU ===
+
+Last but not least, you can compile V8 against a version of ICU installed in your system. To do so, specify the gyp variable {{{use_system_icu=1}}}. If you also have {{{want_separate_host_toolset}}} enabled, the bundled ICU will still be compiled to generate the V8 snapshot. The system ICU will only be used for the target architecture.
+
+
+== Embedding V8 ==
+
+If you embed V8 in your application, but your application itself doesn't use ICU, you will need to initialize ICU before calling into V8 by executing:
+
+{{{
+v8::V8::InitializeICU();
+}}}
+
+It is safe to invoke this method if ICU was not compiled in, then it does nothing.
+
+
+== Compiling without i18n support ===
+
+To build V8 without i18n support use
+
+{{{
+make i18nsupport=off native
+}}}

--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
--- You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to