update FAQ with info on extended charset support in text indexes

git-svn-id: https://svn.code.sf.net/p/jackcess/code/jackcess/trunk@258 f203690c-595d-4dc9-a70b-905162fa7fd2

diff --git a/src/site/fml/faq.fml b/src/site/fml/faq.fml
index 4ae538400220382535d09b42192d4c5e06f1b3d0..3297e3068a180092d47ee1c83ac73877df5b92f2 100644 (file)
--- a/src/site/fml/faq.fml
+++ b/src/site/fml/faq.fml
@@ -169,18 +169,21 @@
           simple to reverse engineer, so it is not likely that Jackcess will
           support this anytime soon.
         </p>
+        <p>
+          Update: As of the 1.1.13 release, the text index handling supports
+          the entire ISO-8859-1 character set.  Consequently table names can
+          (as of this release) contain any character in this character set.
+        </p>
         <p>
           Some suggestions:
         </p>
         <ul>
-          <li>Use only ascii characters in table names if at all
-          possible</li>
-          <li>If tables with international characters are required, create
-          the tables using Access, then update the tables using
-          jackcess.</li>
-          <li>For indexes on user created tables, populate the table
-          without indexes in jackcess, then add the index using
-          Access.</li>
+          <li>Use only ascii (or ISO-8859-1 as of 1.1.13) characters in table
+              names if at all possible</li>
+          <li>If tables with international characters are required, create the
+              tables using Access, then update the tables using jackcess.</li>
+          <li>For indexes on user created tables, populate the table without
+              indexes in jackcess, then add the index using Access.</li>
         </ul>
       </answer>
     </faq>