Document that app names and nodes names are restricted to latin-1

2 files changed, 12 insertions, 10 deletions

diff --git a/lib/stdlib/doc/src/unicode_usage.xml b/lib/stdlib/doc/src/unicode_usage.xml
index a8ef8ff5c5..1e7f08db86 100644
--- a/lib/stdlib/doc/src/unicode_usage.xml
+++ b/lib/stdlib/doc/src/unicode_usage.xml
@@ -63,9 +63,9 @@
 	<item><p>In Erlang/OTP 17.0, the encoding default for Erlang
 	source files was switched to UTF-8.</p></item>
 
-	<item><p>In Erlang/OTP 20.0, atoms and function can contain
-	Unicode characters. Module names are still restricted to
-	the ISO-Latin-1 range.</p></item>
+	<item><p>In Erlang/OTP 20.0, atoms and function names can contain
+	Unicode characters. Module names, application names, and node
+	names are still restricted to the ISO Latin-1 range.</p></item>
       </list>
 
     <p>This section outlines the current Unicode support and gives some
@@ -345,10 +345,11 @@
         <p>Having the source code in UTF-8 also allows you to write string
           literals, function names, and atoms containing Unicode
 	  characters with code points &gt; 255.
-          Module names are still restricted to the ISO Latin-1 range.
-	  Binary literals, where you use type
+          Module names, application names, and node names are still restricted
+	  to the ISO Latin-1 range. Binary literals, where you use type
           <c>/utf8</c>, can also be expressed using Unicode characters &gt; 255.
-          Having module names using characters other than 7-bit ASCII can cause
+          Having module names or application names using characters other than
+	  7-bit ASCII can cause
           trouble on operating systems with inconsistent file naming schemes,
           and can hurt portability, so it is not recommended.</p>
         <p>EEP 40 suggests that the language is also to allow for Unicode
@@ -444,8 +445,8 @@ external_charlist() = maybe_improper_list(char() | external_unicode_binary() |
     marker="stdlib:epp#encoding"><c>epp(3)</c></seealso> module.  As
     from Erlang/OTP R16, strings and comments can be written using
     Unicode.  As from Erlang/OTP 20, also atoms and functions can be
-    written using Unicode. Modules names must still be named using
-    characters from the ISO Latin-1 character set.  (These
+    written using Unicode. Modules, applications, and nodes must still be
+    named using characters from the ISO Latin-1 character set.  (These
     restrictions in the language are independent of the encoding of
     the source file.)</p>
 
@@ -773,7 +774,7 @@ Eshell V5.10.1  (abort with ^G)
     filenames or directory names. If the file system content is
     listed, you also get Unicode lists as return value. The support
     lies in the Kernel and STDLIB modules, which is why
-    most applications (that does not explicitly require the filenames
+    most applications (that do not explicitly require the filenames
     to be in the ISO Latin-1 range) benefit from the Unicode support
     without change.</p>
 
diff --git a/system/doc/reference_manual/character_set.xml b/system/doc/reference_manual/character_set.xml
index 1129ad63d8..8e41142fb4 100644
--- a/system/doc/reference_manual/character_set.xml
+++ b/system/doc/reference_manual/character_set.xml
@@ -110,7 +110,8 @@
        Guide</seealso>.</p>
        <p>From Erlang/OTP 20, atoms and function names are also allowed
        to contain Unicode characters outside the ISO-Latin-1 range.
-       Module names are still restricted to the ISO-Latin-1 range.</p>
+       Module names, application names, and node names are still
+       restricted to the ISO-Latin-1 range.</p>
   </section>
   <section>
     <title>Source File Encoding</title>