From 9cb1ba34778b0ed4d1202d405c98b30bf45f1fed Mon Sep 17 00:00:00 2001
From: dchandler <dchandler>
Date: Sun, 11 Apr 2004 15:48:30 +0000
Subject: [PATCH] Clarified the TMW->ACIP converter's treatment of 0fbc, 0fbb,
 and 0f6a.  0fba doesn't come up because ACIP has both "V" and "W".

---
 htdocs/TMW_or_TM_To_X_Converters.html | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/htdocs/TMW_or_TM_To_X_Converters.html b/htdocs/TMW_or_TM_To_X_Converters.html
index 74b255c..3868e16 100644
--- a/htdocs/TMW_or_TM_To_X_Converters.html
+++ b/htdocs/TMW_or_TM_To_X_Converters.html
@@ -177,6 +177,14 @@
   output, but it will be amidst the successfully converted text.
 </p>
 
+<p>
+  You will see such messages for non-<a
+  href="ACIP_To_Tibetan_Converter.html#native">native</a> glyphs that
+  have full-formed, subjoined RA or YA (U+0FBC or U+0FBB) or
+  full-formed superscribed RA (U+0F6A).&nbsp; This is because the ACIP
+  scheme does not say when R or Y indicates this unusual form.
+</p>
+
 <h3>TMW to Wylie (i.e., EWTS)</h3>
 
 <p>