Concise representations: translation groups, meaning groups, and sources

[aarppe]

Following up on #88, we'd want to prefer more concise representations for reasons of space.

1. Indication of sources as superscripts of source acronym, currently one of the following two (corresponding to the id variable in the source element):

CW: Cree / Words : nêhiyawêwin / itwêwina; and
MD: Maskwacîs Cree Dictionary

Clicking on source acronym should produce a pop-up with a fuller reference to the source (and eventually perhaps even a link to the source website, if such exists - that is the case for CW but not for MD). The full title could come from the <title> fields in the <source id="..."> sections in the beginning of the dictionary source XML.

2. Multiple translation groups (<tg>...</tg>) on same line, separated by a semicolon, with source acronym after each <tg>, superscripted as in 1.

Multiple translations (<t>...</t>) within a translation group would be presented on the same line (we haven't used multiple translations, though in principle we could split e.g. longer CW glosses, based on semicolons in the CSV source). But the source acronyms would pertain to each translation group.

3. Multiple meaning groups (<mg>...</mg>) on separate bulleted lines, with translation groups as in 2.

[eddieantonio]

Blocked: need #89 before I can write integration tests for this issue

[eddieantonio]

No longer blocked. Changes needed:

• Change <ul> to a series of <cite> tags.
• Style <cite> tags to be superscript, with links
• Update the XML dictionary specification to have <url> child for <source> elements Add a <url> to <source> elements in the dictionary #98
• Hover or touch to enable a pop-up with the full name source, and optional link
• Separate translations within translation groups with a semicolon (blocked by Entries that should have two translation groups have two meaning groups instead #102)

[eddieantonio]

Note: once hovering is implemented, this will also close #11!

[eddieantonio]

Remaining task is blocked by #102. Upon closing it, delete the .skip() in the test for this issue, and this issue will be closed as well!