[Refdb-cvs] CVS: refdb/doc chapter-data-input.xml,1.1.2.1,1.1.2.2

[Markus H. <mho...@us...>]

Update of /cvsroot/refdb/refdb/doc
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv28086/doc

Modified Files:
      Tag: Release_0_9_5_stable
	chapter-data-input.xml 
Log Message:
Reference Manaager uses ANSI, not Latin-1

Index: chapter-data-input.xml
===================================================================
RCS file: /cvsroot/refdb/refdb/doc/Attic/chapter-data-input.xml,v
retrieving revision 1.1.2.1
retrieving revision 1.1.2.2
diff -u -U2 -r1.1.2.1 -r1.1.2.2
--- chapter-data-input.xml	8 Jan 2006 21:53:40 -0000	1.1.2.1
+++ chapter-data-input.xml	5 Apr 2006 20:11:28 -0000	1.1.2.2
@@ -62,5 +62,5 @@
     <sect2>
       <title>Character encodings</title>
-      <para>The RIS specification has not built-in means to specify the character encoding of the data. Commercial applications apparently expect the data to be encoded as ISO-8859-1, aka Latin-1. refdb does not have this limitation, you are free to use any encoding available on your platform (except UTF-16 and UTF-32). However, you should be aware that this may cause an interchange issue if you plan to use these data in a commercial reference management program. In any case, as the datasets do not specify their encoding, you have to use <option>-E</option> option of the <link linkend="app-c-command-getref">getref</link> command if your input data use an encoding different from the default (ISO-8859-1).</para>
+      <para>The RIS specification has no built-in means to specify the character encoding of the data. Commercial applications usually expect the data to be supplied in a particular encoding (e.g. Reference Manager uses the Windows ANSI character set). refdb does not have this limitation, you are free to use any encoding available on your platform (except UTF-16 and UTF-32). However, you should be aware that this may cause an interchange issue if you plan to use these data in a commercial reference management program. In any case, as the datasets do not specify their encoding, you have to use <option>-E</option> option of the <link linkend="app-c-command-getref">getref</link> command if your input data use an encoding different from the default (ISO-8859-1).</para>
     </sect2>
     <sect2>