diff options
| author | Lukas Larsson <[email protected]> | 2012-08-24 11:11:40 +0200 |
|---|---|---|
| committer | Lukas Larsson <[email protected]> | 2012-08-30 15:37:31 +0200 |
| commit | c9034896271dd9fc8f8e19810e06baf46198336d (patch) | |
| tree | 77edb7c427a92a436be47fd3ae043fbbff410085 | |
| parent | 74dc5ada9156ed1dd8bb73d6b298b2cdcf3cf3dc (diff) | |
| download | otp-c9034896271dd9fc8f8e19810e06baf46198336d.tar.gz otp-c9034896271dd9fc8f8e19810e06baf46198336d.tar.bz2 otp-c9034896271dd9fc8f8e19810e06baf46198336d.zip | |
Fix broken links
| -rw-r--r-- | lib/stdlib/doc/src/unicode_usage.xml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/lib/stdlib/doc/src/unicode_usage.xml b/lib/stdlib/doc/src/unicode_usage.xml index b7b5d497d0..acd36d2125 100644 --- a/lib/stdlib/doc/src/unicode_usage.xml +++ b/lib/stdlib/doc/src/unicode_usage.xml @@ -212,7 +212,7 @@ Eshell V5.7 (abort with ^G) <section> <title>Unicode in environment variables and parameters</title> <p>Environment variables and their interpretation is handled much in the same way as file names. If Unicode file names are enabled, environment variables as well as parameters to the Erlang VM are expected to be in Unicode.</p> -<p>If Unicode file names are enabled, the calls to <seealso marker="kernel:os#os_getenv/0"><c>os:getenv/0</c></seealso>, <seealso marker="kernel:os#os_getenv/1"><c>os:getenv/1</c></seealso> and <seealso marker="kernel:os#os_putenv/2"><c>os:putenv/2</c></seealso> will handle Unicode strings. On Unix-like platforms, the built-in functions will translate environment variables in UTF-8 to/from Unicode strings, possibly with codepoints > 255. On Windows the Unicode versions of the environment system API will be used, also allowing for codepoints > 255.</p> +<p>If Unicode file names are enabled, the calls to <seealso marker="kernel:os#getenv/0"><c>os:getenv/0</c></seealso>, <seealso marker="kernel:os#getenv/1"><c>os:getenv/1</c></seealso> and <seealso marker="kernel:os#putenv/2"><c>os:putenv/2</c></seealso> will handle Unicode strings. On Unix-like platforms, the built-in functions will translate environment variables in UTF-8 to/from Unicode strings, possibly with codepoints > 255. On Windows the Unicode versions of the environment system API will be used, also allowing for codepoints > 255.</p> <p>On Unix-like operating systems, parameters are expected to be UTF-8 without translation if Unicode file names are enabled.</p> </section> <section> |