From 437943f77f3fb9d2a12c659e52c8d35e3e24fbc6 Mon Sep 17 00:00:00 2001
From: Richard Carlsson
Available control sequences:
@@ -277,10 +277,9 @@ ok1> T = [{attributes,[[{id,age,1.50000},{mode,explicit}, {typename,"INTEGER"}], [{id,cho},{mode,explicit},{typename,'Cho'}]]}, @@ -302,7 +301,7 @@ ok {mode,implicit}] ok
The field width specifies the maximum line length.
- Defaults to 80. The precision specifies the initial
+ It defaults to 80. The precision specifies the initial
indentation of the term. It defaults to the number of
characters printed on this line in the same call to
Binaries that look like UTF-8 encoded strings are - output with the string syntax if the Unicode translation - modifier is specified:
+The Unicode translation modifier
+8> io:fwrite("~p~n",[list_to_atom([1024])]). +'\x{400}' +ok +9> io:fwrite("~tp~n",[list_to_atom([1024])]). +'Ѐ' +ok+
By default, Erlang only detects lists of characters
+ in the Latin-1 range as strings, but the
+10> io:fwrite("~p~n",[[214]]). +"Ö" +ok +11> io:fwrite("~p~n",[[1024]]). +[1024] +ok +12> io:fwrite("~tp~n",[[1024]]). +[1024] +ok ++
but if Erlang was started with
-9> io:fwrite("~p~n",[[1024]]). +13> io:fwrite("~p~n",[[1024]]). [1024] -10> io:fwrite("~tp~n",[[1024]]). -"\x{400}" -11> io:fwrite("~tp~n", [<<128,128>>]). +ok +14> io:fwrite("~tp~n",[[1024]]). +"Ѐ" +ok+
Similarly, binaries that look like UTF-8 encoded strings
+ are output with the binary string syntax if the
+15> io:fwrite("~p~n", [<<208,128>>]). +<<208,128>> +ok +16> io:fwrite("~tp~n", [<<208,128>>]). +<<"Ѐ"/utf8>> +ok +17> io:fwrite("~tp~n", [<<128,128>>]). <<128,128>> -12> io:fwrite("~tp~n", [<<208,128>>]). -<<"\x{400}"/utf8>> ok