summaryrefslogtreecommitdiff
path: root/doc/ref/api-data.texi
diff options
context:
space:
mode:
authorMark H Weaver <mhw@netris.org>2013-04-01 12:28:25 -0400
committerMark H Weaver <mhw@netris.org>2013-04-01 12:35:24 -0400
commit369294866dd7ee01ebf821df2a119ea55b1e68fd (patch)
tree1f4aba315c9ae04070584927ec5ebac1b13a4478 /doc/ref/api-data.texi
parentde2bc673bba931a70e3b96336cab6512a47541fe (diff)
downloadguile-369294866dd7ee01ebf821df2a119ea55b1e68fd.tar.gz
Fix broken texinfo markup in (ice-9 iconv) docs.
* doc/ref/api-data.texi (Representing Strings as Bytes): Fix broken @deffn syntax.
Diffstat (limited to 'doc/ref/api-data.texi')
-rw-r--r--doc/ref/api-data.texi6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/ref/api-data.texi b/doc/ref/api-data.texi
index 0a5a2de77..dc1b76125 100644
--- a/doc/ref/api-data.texi
+++ b/doc/ref/api-data.texi
@@ -4222,7 +4222,7 @@ Unlike the rest of the procedures in this section, you have to load the
(use-modules (ice-9 iconv))
@end example
-@deffn string->bytevector string encoding [conversion-strategy]
+@deffn {Scheme Procedure} string->bytevector string encoding [conversion-strategy]
Encode @var{string} as a sequence of bytes.
The string will be encoded in the character set specified by the
@@ -4236,7 +4236,7 @@ bytevectors. @xref{Ports}, for more on character encodings and
conversion strategies.
@end deffn
-@deffn bytevector->string bytevector encoding [conversion-strategy]
+@deffn {Scheme Procedure} bytevector->string bytevector encoding [conversion-strategy]
Decode @var{bytevector} into a string.
The bytes will be decoded from the character set by the @var{encoding}
@@ -4247,7 +4247,7 @@ argument to modify this behavior. @xref{Ports}, for more on character
encodings and conversion strategies.
@end deffn
-@deffn call-with-output-encoded-string encoding proc [conversion-strategy]
+@deffn {Scheme Procedure} call-with-output-encoded-string encoding proc [conversion-strategy]
Like @code{call-with-output-string}, but instead of returning a string,
returns a encoding of the string according to @var{encoding}, as a
bytevector. This procedure can be more efficient than collecting a