> For the complete documentation index, see [llms.txt](https://medievalbook.gitbook.io/digitizing-medieval-archives/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://medievalbook.gitbook.io/digitizing-medieval-archives/week-6.md).

# Week 6 - Palæography

In class this week we will discuss medieval scripts, how they developed and some ideas about why they developed the way they did. The key idea to take away is that the standardized scripts that come to be used for books (also called bookhands) have a history and this history is useful for both understanding the history of communication, but also for dating manuscripts (because scripts go in and out of fashion). 

In class, we will spend an hour or so trying to reproduce medieval scripts with modern writing instruments.

At home, after class you have two tasks: 

First, navigate to the *Ad fontes* website and attempt to transcribe [this fourteenth-century document](https://www.adfontes.uzh.ch/en/3171/training/lateinische-transkriptionsuebungen/brevier/brevier-aufgabe1) written in *gothica textualis*. Unlike your folio, if you click the "show transcription" box at the bottom of the page, whenever you hover the cursor over the word you are deciphering, it will show you the answer (I suggest this as a first stage to lessen the initial frustration of decipering and unpacking medieval writing).

The next stage will be attempting to transcribe your document in a text file after you have installed a medieval unicode font. To do so, go to the next step.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://medievalbook.gitbook.io/digitizing-medieval-archives/week-6.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.