Jim Meyering <[EMAIL PROTECTED]> writes:
> Simon Josefsson <[EMAIL PROTECTED]> wrote:
>> Hi! I looked over the base64 tool a bit, and found two minor issues.
>
>> Subject: [PATCH] Improve comments.
> ...
>
> Thanks! Applied.
That was quick, thanks. I went over the documentation as well.
/Simon
>From 450da29a8766003e35891e7f5209e4fa135d2845 Mon Sep 17 00:00:00 2001
From: Simon Josefsson <[EMAIL PROTECTED]>
Date: Sun, 1 Jun 2008 13:51:14 +0200
Subject: [PATCH] use RFC 4648 as base64 specification, and move the URL down a
bit in the text
---
doc/coreutils.texi | 7 ++++---
1 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/doc/coreutils.texi b/doc/coreutils.texi
index dbc8a8b..020cb00 100644
--- a/doc/coreutils.texi
+++ b/doc/coreutils.texi
@@ -1860,8 +1860,7 @@ address.
@command{base64} transforms data read from a file, or standard input,
into (or from) base64 encoded form. The base64 encoded form uses
-printable @acronym{ASCII} characters to represent binary data, see
[EMAIL PROTECTED]://ftp.rfc-editor.org/in-notes/rfc3548.txt, RFC 3548}.
+printable @acronym{ASCII} characters to represent binary data.
Synopses:
@smallexample
@@ -1869,7 +1868,9 @@ base64 [EMAIL PROTECTED]@dots{} [EMAIL PROTECTED]
base64 --decode [EMAIL PROTECTED]@dots{} [EMAIL PROTECTED]
@end smallexample
-The base64 encoding expands data to roughly 133% of the original.
+The base64 encoding expands data to roughly 133% of the original. The
+format conforms to
[EMAIL PROTECTED]://ftp.rfc-editor.org/in-notes/rfc4648.txt, RFC 4648}.
The program accepts the following options. Also see @ref{Common options}.
--
1.5.5.1
_______________________________________________
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils
