From 73fb697ec72c7848d867e657201cc243dbda5fd3 Mon Sep 17 00:00:00 2001
From: Richard Brooksby <rb@ravenbrook.com>
Date: Fri, 10 May 2013 19:07:12 +0100
Subject: [PATCH] Cross-referencing to guide.hex.trans.

Copied from Perforce
 Change: 181710
 ServerID: perforce.ravenbrook.com
---
 mps/design/sig.txt | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/mps/design/sig.txt b/mps/design/sig.txt
index c39e4e37715..3f3e1033976 100644
--- a/mps/design/sig.txt
+++ b/mps/design/sig.txt
@@ -46,12 +46,13 @@ There must also be a definition for the valid value for that signature::
 
     #define MessageSig      ((Sig)0x5193e559) /* SIG MESSaGe */
 
-This is a 32-bit hex constant, spelled according to the standard MPS
-transliteration [GRM_1997-04-11]_::
+This is a 32-bit hex constant, spelled according to guide.hex.trans_::
 
     ABCDEFGHIJKLMNOPQRSTUVWXYZ
     ABCDEF9811C7340BC6520F3812
 
+.. _guide.hex.trans: ./guide.hex.trans.txt
+
 This allows the structure to be recognised when looking at memory in a hex
 dump or memory window, or found using memory searches.
 
@@ -139,9 +140,6 @@ undesirable and the problem should be investigated.
 
 A. References
 -------------
-.. [GRM_1997-04-11] "Guide to transliterating the alphabet into hexadecimal";
-   Gavin Matthews; Harlequin; 1997-04-11.
-
 .. [RB_1995-08-25] "design.mps.sig: The design of the Memory Pool System
    Signature System"; Richard Brooksby; Harlequin; 1995-08-25.