Differences

This shows you the differences between two versions of the page.

--- kb:exhibit [2010/07/29 11:13] – created kalvesmaki
+++ kb:exhibit [2017/11/22 16:00] (current) – bwiernik
@@ Line 1: / Line 1: @@
+**These directions have not been updated in some time and may no longer be up to date.**
 ===How do I get my Zotero collection to work with an Exhibit or Citeline presentation?===
-The [[http://simile.mit.edu/|Simile Project]], sponsored by MIT, has developed several Javascript applications that help a Zotero user integrate a collection into a website.
+The [[http://simile.mit.edu/|Simile Project]], sponsored by MIT, has developed several JavaScript applications that help a Zotero user integrate a bibliography into a website.
+[[http://citeline.mit.edu/|Citeline]], under Simile's purview, has a Firefox plugin called Zotz to streamline the conversion process. This plug-in, however, works only with Firefox 2.0. Further, when importing the BibTeX file, the Citeline filter incorrectly handles Unicode characters beyond the Basic Latin set. Boxes or question marks are frequently encountered. At this time Citeline is not able to provide support for non-Latin characters.
-[[http://citeline.mit.edu/|Citeline]], still under Simile's purview, has a Firefox plugin called Zotz to streamline the conversion process. This plug-in, however, works only with Firefox 2.0. Further, when importing the BibTeX file, the Citeline filter incorrectly handles Unicode characters beyond the Basic Latin set. Boxes or question marks are frequently encountered.
+[[http://www.simile-widgets.org/exhibit/|Exhibit]], now supported independent of Simile, is very similar to Citeline, but is more powerful and customizable. Exhibit has a page explaining how to [[http://www.simile-widgets.org/wiki/How_to_make_a_publications_exhibit|generate a publications exhibit]]. But a different kind of problem is encountered here: one must convert a Zotero collection to Exhibit's JSON format. And Zotero does not directly export to a JSON format.
-[[http://www.simile-widgets.org/exhibit/|Exhibit]], now run independent of Simile, is very similar to Citeline, but its range of applications is much greater. But a different problem is encountered, here, namely that one must convert a Zotero collection to Exhibit's
+The handiest conversion tool is Simile's [[http://service.simile-widgets.org/babel/|Babel converter]] ([[http://simile.mit.edu/babel/|alternate link]]). But in using Babel one encounters conversion problems similar to those found in the Citeline conversion. Exhibit calls for Unicode characters rendered as UTF-32, but Babel renders them UTF-8. Further, the characters < and > are converted to {\\textless} and {\\textgreater}. And if you have started with a Zotero-generated BibTeX file, you may find curled braces {} in fields where they do not belong (an [[/forum/discussion/31/bibtex-export|idiosyncrasy]] in Zotero's BibTeX converter). So some cleanup is necessary before the JSON file exported by Babel is ready for interaction with Exhibit.
- When an upper-level character is encountered, it signals frequently introduces a new character
+Here is a detailed explanation of the problems in the Babel conversion process: when Babel encounters a character outside the Basic Latin table (but less than value U+0800), Babel replaces it with two new character sequences: one a multiplicand (e.g., \u00C3 and upward, depending upon how large the target Unicode number is) and the other the Unicode value of the character point in the Basic Latin plane that is an exact multiple of 64 less than the intended Unicode value. For example, é (Unicode value U+00E9) is translated by Babel, not as \u00E9 (as Exhibit calls for) but into \u00C3\u00A9, which displays as Ã©.
+{{tag>kb}}