Pandoc to TEI

100%

✓ Published0🌍 Public

Last edited Jul 27, 2016

Created on Jul 27, 2016

This example shows a command-line workflow for converting Word documents into TEI Simple XML using Pandoc, with instructions tailored for macOS Terminal. The visualization relies on the Pandoc API to transform `filename.docx` into `filename.xml` with the `-t tei` flag and `-s` for standalone output. It demonstrates the Homebrew package manager’s role in installing Pandoc via `brew install pandoc`. The code highlights the exact Terminal commands—`curl` for Homebrew installation and `pandoc` for conversion—without abstracting the process, making the data source (the Word file) and the output format (TEI) explicit.

AI-generated description

Similar vizzes

Loading thumbnail…

Pandoc bash conversion

This visualization demonstrates a user’s workflow of converting and renaming files across directories using shell commands. It shows three distinct bash operations: deleting HTML files in a specific folder, converting sociology files to DOCX via Pandoc, and renaming XML files to HTML using the `rename` utility. The code relies on standard shell scripting constructs and the Pandoc command-line tool, with no graphical or interactive rendering libraries like D3 or Three.js. The data source is the local file system paths referenced in each command, and the rendering approach is purely textual—showing the raw bash scripts rather than any visual output.

CCliffordAnderson

71% match

Loading thumbnail…

Pandoc conversation example

This example shows the execution history of a Pandoc command that converts a Markdown syllabus into a standalone DOCX file, visualizing the command’s arguments and file flow as an annotated graph. It uses D3’s `forceSimulation` to lay out nodes representing the input, output, and converter, with `transition.attrTween` animating the edge paths between them. The underlying data comes directly from the gist’s shell command, parsed into JSON, and the view highlights the order of operations—`pandoc.txt`, `syllabus.md`, and the `--from`/`--to` flags—without implying any behavior beyond what the command lists.

CCliffordAnderson

69% match

Loading thumbnail…

Prompt for marking up TEI P5

This example demonstrates a prompt-driven workflow for converting raw historical text into TEI P5 XML with named entity markup. It shows how the system identifies personal names, queries Wikidata for matching entities, and assigns attributes like @ref, @full, and @cert for disambiguated references. The process relies on the Wikidata API for entity resolution and uses TEI's controlled vocabulary for confidence levels. The output is a self-contained XML fragment, with unidentifiable names marked as unknown. This approach highlights the integration of external linked-data sources into scholarly text encoding, emphasizing automated authority control and metadata enrichment.

CCliffordAnderson

59% match

Loading thumbnail…

For XQuery4Humanists

This example visualizes the frequency and distribution of words extracted from a TEI-encoded poem, processing the text to remove punctuation, normalize case, and tokenize it into a list. The visualization shows the resulting word list as a simple textual display, highlighting the raw output of the XQuery processing pipeline. The code uses XQuery 3.0 functions like `fn:tokenize`, `fn:lower-case`, and `fn:replace` to clean the data, pulling the source directly from a remote XML file hosted on GitHub. The rendering relies solely on the XQuery return, with no additional JavaScript or charting libraries involved.

CCliffordAnderson

59% match

Loading thumbnail…

Gist fad71606fe06d36c511dd04d348bc7c3

This example documents a system administration workflow for installing the LaTeX typesetting environment and related scientific computing tools on Arch Linux. It shows a curated list of `sudo pacman -S` package installation commands, including `texlive-science`, `texlive-latexextra`, `graphviz`, and `dot2tex`, alongside notes about missing packages in the official repositories. The visualization also includes a step for copying macros from `bok-macrosV0.sty` into a curriculum file using Vim. The rendering simply presents the terminal commands and package names as plain text, with no graphical or interactive elements, relying on the raw command list to convey the installation sequence.

MMistyBlunch

56% match

Loading thumbnail…

Common Terminal Commands

This example presents a plain-text Markdown reference for common terminal commands, sourced from a gist by IoTeacher. It shows a structured cheat sheet covering keyboard shortcuts, manual lookup (`man`, `--help`), and command categories like file system navigation (`pwd`, `ls`, `cd`, `find`), opening files/folders per OS (`open`, `start`, `xdg-open`), and file modification (`mkdir`, `touch`, `rm`, `cp`, `mv`). The rendering relies on standard GitHub-flavored Markdown, with code blocks and tables organizing the content. No interactive or programmatic visualization is used; the design is purely textual and static.

IIoTeacher

56% match

Loading thumbnail…

XQuery Blue Mountain Project - Part III

This example shows a pipeline for transforming a single TEI XML document from the Blue Mountain Project—a digitized 1920 issue of the French journal *Action*—into clean, article-level TEI files. The first script removes facsimile elements, end-hyphenation markers, and line breaks, replacing `<lb>` elements with spaces. A second script extracts metadata and article content into a fresh TEI template, while a third builds individual TEI files for each article. The code uses XQuery 3.1 with the `fn:doc` API for document access and node operations like `copy`, `modify`, and `replace node`.

CCliffordAnderson

56% match

Loading thumbnail…

Outline for TEI Publisher Workshop

This outline introduces TEI Publisher, a tool for publishing TEI-encoded texts, using examples such as Early English Books Online and Shakespeare’s plays. It covers installation via Docker, customization through ODDs with references to the TEI Element Model and a Baudelaire corpus, and view adjustments using Syriaca Gazetteer data. The document also addresses deployment on Digital Ocean. Concrete resources include Docker, eXist-db, and GitHub repositories, but no code libraries or APIs are referenced.

CCliffordAnderson

54% match