aboutsummaryrefslogtreecommitdiff
path: root/README.utf-8
diff options
context:
space:
mode:
authorSteve Bennett <steveb@workware.net.au>2011-12-02 20:54:36 +1000
committerSteve Bennett <steveb@workware.net.au>2011-12-02 20:56:48 +1000
commit6757f5c6f30f6630f728fcbd99d7ce4a50135706 (patch)
treead47403fc3f50ff18deb26a836223d9b215eaa0e /README.utf-8
parent21d7fc318bcda4c718d32dc82e1249e4861cc5f9 (diff)
downloadjimtcl-6757f5c6f30f6630f728fcbd99d7ce4a50135706.zip
jimtcl-6757f5c6f30f6630f728fcbd99d7ce4a50135706.tar.gz
jimtcl-6757f5c6f30f6630f728fcbd99d7ce4a50135706.tar.bz2
Correct the documentation for 'local'
Also some general documentation cleanups and trailing white space removal. Signed-off-by: Steve Bennett <steveb@workware.net.au>
Diffstat (limited to 'README.utf-8')
-rw-r--r--README.utf-82
1 files changed, 1 insertions, 1 deletions
diff --git a/README.utf-8 b/README.utf-8
index eca528c..7128d76 100644
--- a/README.utf-8
+++ b/README.utf-8
@@ -12,7 +12,7 @@ nulls, however it has had no support for multi-byte character encodings.
In some fields, such as when dealing with the web, or other user-generated content,
support for multi-byte character encodings is necessary.
In these cases it would be very useful for Jim Tcl to be able to process strings
-as multi-byte character strings rather than simply binary bytes.
+as multi-byte character strings rather than simply binary bytes.
Supporting multiple character encodings and translation between those encodings
is beyond the scope of Jim Tcl. Therefore, Jim has been enhanced to add support