Libris Translate 0.28.0 · User guide

Category: Context and consistency

Translator’s notes for readers

Explain a term that does not translate, right where the reader meets it.

Translator’s notes for readers in the fictional Libris Translate demonstration.
Actual interface with simulated demonstration data. Open the full-size screenshot.

Steps

  1. In the book’s Glossary tab, the “Translator’s notes” card lists the “Accepted terms to annotate”. A note is written for readers and is separate from the glossary’s internal description.
  2. Write the “Reader-facing note” and choose its “Note placement”: “First occurrence of the term”, “Every occurrence of the term” or “Do not publish this note”. Click “Save the reader note”.
  3. For drafts, click “Suggest cultural notes”. The job calls your provider and is billed; it suggests at most 200 notes, for accepted terms that have none. “Use this proposal as a draft” loads one into the form, and nothing is published until you save it.
  4. Export and check the result: footnotes in EPUB 3, notes at the end of the chapter in text and Markdown, comments in Word.

What to know

The first occurrence is the first in the volume for EPUB and text, and the first in the excerpt for a partial Word export. Glossary files in JSON, CSV and TBX carry the note and its placement, both on export and on import. A suggestion is never published on its own: turning it into a note is always a person’s decision.

Fictional example

Add a note to a fictional cultivation rank such as “Foundation Establishment”, place it at the first occurrence, then export a bilingual EPUB and read it as a footnote.

Continue