summaryrefslogtreecommitdiff
path: root/doc/ref/api-io.texi
diff options
context:
space:
mode:
authorMichael Gran <spk121@yahoo.com>2010-01-19 08:42:44 -0800
committerMichael Gran <spk121@yahoo.com>2010-01-19 08:42:44 -0800
commit912a8702466f07ca3f4c673a895361e5d7775b7b (patch)
treeeb399f66b47f06405c5e3174a541a6da78c43316 /doc/ref/api-io.texi
parentadfb42846617f6ed11cbe6ca9f0256e48a0cbb49 (diff)
downloadguile-912a8702466f07ca3f4c673a895361e5d7775b7b.tar.gz
Document modal encodings problem in ref doc
* doc/ref/api-io.texi (Ports): note that modal encodings are not supported
Diffstat (limited to 'doc/ref/api-io.texi')
-rw-r--r--doc/ref/api-io.texi6
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/ref/api-io.texi b/doc/ref/api-io.texi
index a1f4221e2..c97b920d2 100644
--- a/doc/ref/api-io.texi
+++ b/doc/ref/api-io.texi
@@ -76,6 +76,12 @@ how characters and strings written to the port are converted to bytes.
When ports are created, they inherit their character encoding from the
current locale, but, that can be modified after the port is created.
+Currently, the ports only work with @emph{non-modal} encodings. Most
+encodings are non-modal, meaning that the conversion of bytes to a
+string doesn't depend on its context: the same byte sequence will always
+return the same string. A couple of modal encodings are in common use,
+like ISO-2022-JP and ISO-2022-KR, and they are not yet supported.
+
Each port also has an associated conversion strategy: what to do when
a Guile character can't be converted to the port's encoded character
representation for output. There are three possible strategies: to