[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Guile-commits] GNU Guile branch, master, updated. release_1-9-6-173-g91

From: Michael Gran
Subject: [Guile-commits] GNU Guile branch, master, updated. release_1-9-6-173-g912a870
Date: Tue, 19 Jan 2010 16:40:17 +0000

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU Guile".

The branch, master has been updated
       via  912a8702466f07ca3f4c673a895361e5d7775b7b (commit)
      from  adfb42846617f6ed11cbe6ca9f0256e48a0cbb49 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 912a8702466f07ca3f4c673a895361e5d7775b7b
Author: Michael Gran <address@hidden>
Date:   Tue Jan 19 08:42:44 2010 -0800

    Document modal encodings problem in ref doc
    * doc/ref/api-io.texi (Ports): note that modal encodings are not


Summary of changes:
 doc/ref/api-io.texi |    6 ++++++
 1 files changed, 6 insertions(+), 0 deletions(-)

diff --git a/doc/ref/api-io.texi b/doc/ref/api-io.texi
index a1f4221..c97b920 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

GNU Guile

reply via email to

[Prev in Thread] Current Thread [Next in Thread]