Re: [PATCH 1/2] AX_PROG_EMACS: New submission

Thien-Thi Nguyen <[email protected]> Thu, 06 Apr 2017 15:59:28 +0200
Newsgroups gmane.comp.sysutils.autoconf.archive-maintainers
Message-ID <87fuhleiwv.fsf@zigzag>
() Peter Simons <[email protected]>
() Thu, 06 Apr 2017 13:24:13 +0200

   thank you very much for the submissions!

You're welcome!

   I pushed them to the repository.

Cool, thanks.

   I also made two small edits to make sure that the m4 files
   don't rely on any particular character encoding: [...]
   I hope those edits don't cause any problems?

Fine by me.  I should have thought of that; sorry for the
inconvenience; thanks for taking care of this detail.  Here is a
small doc patch that helps jog my memory (for the next time):


-- 
Thien-Thi Nguyen -----------------------------------------------
 (defun responsep (query)
   (pcase (context query)
     (`(technical ,ml) (correctp ml))
     ...))                              748E A0E8 1CB8 A748 9BFA
--------------------------------------- 6CE4 6703 2224 4C80 7502
0001-doc-Add-character-encoding-guideline.patch (text/x-diff, 1 KB)
From 721074b998bd01ba2c1d152bc446f86dbf7946e5 Mon Sep 17 00:00:00 2001
From: Thien-Thi Nguyen <[email protected]>
Date: Thu, 6 Apr 2017 15:54:36 +0200
Subject: [PATCH] [doc] Add character-encoding guideline

* doc/contribute.texi (Macro Format):
Add a blurb on the preferred character encoding
and an example of applying the guideline.
---
 doc/contribute.texi | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/doc/contribute.texi b/doc/contribute.texi
index 61922aa..019ea14 100644
--- a/doc/contribute.texi
+++ b/doc/contribute.texi
@@ -3,6 +3,9 @@
 Each macro in the Archive has an all-upper-case name with the prefix
 @code{AX_}.  The macro is stored in a file with the same name, in lower case,
 and with the suffix @code{.m4}.
+Unless absolutely necessary, the file contents should be in ASCII.
+For example, use apostrophe (U+27) for quoting identifiers
+instead of Unicode quotation mark characters U+2018, U+2019.
 
 The file should begin with a header comment containing three named sections:
 synopsis, description, and license.
-- 
1.9.1
signature.asc (application/pgp-signature, 197 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAljmScUACgkQZwMiJEyAdQI1kgCglFLhTq7dRUVZRVMEJQhv1lMC
H64AnR1kXfKw9KuRVe9OR+1p4aFS36Cr
=ckyy
-----END PGP SIGNATURE-----