Oops, use debug() rather than log().

[mkws-moved-to-github.git] / tools / htdocs / whitepaper.markdown

diff --git a/tools/htdocs/whitepaper.markdown b/tools/htdocs/whitepaper.markdown
index fd1d25c..dce4f30 100644 (file)
--- a/tools/htdocs/whitepaper.markdown
+++ b/tools/htdocs/whitepaper.markdown
@@ -19,13 +19,13 @@ Index Data provides several different toolkits for communicating with
 its metasearching middleware, trading off varying degrees of
 flexibility against convenience:
 
-* libpz2.js -- a low-level JavaScript library for interrogating the
+* pz2.js -- a low-level JavaScript library for interrogating the
   Service Proxy and Pazpar2. It allows the HTML/JavaScript programmer
   to create JavaScript applications display facets, records, etc. that
   are fetched from the metasearching middleware.
 
 * masterkey-ui-core -- a higher-level, complex JavaScript library that
-  uses libpz2.js to provide the pieces needed for building a
+  uses pz2.js to provide the pieces needed for building a
   full-featured JavaScript application.
 
 * MasterKey Demo UI -- an example of a searching application built on
@@ -358,15 +358,15 @@ structure.
 
 Support for another UI language can be added by providing an entry in
 the `mkws_config` object whose name is `language_` followed by the
-name of the language: for example, `language_Arabic` to support
-Arabic. Then value of this entry must be a key-value lookup table,
+name of the language: for example, `language_French` to support
+French. Then value of this entry must be a key-value lookup table,
 mapping the English-language strings of the UI into their equivalents
 in the specified language. For example:
 
             var mkws_config = {
-              language_Arabic: {
-                "Authors": "الكتاب",
-                "Subjects": "المواضيع",
+              language_French: {
+                "Authors": "Auteurs",
+                "Subjects": "Sujets",
                 // ... and others ...
               }
             }