Authorized Version (KJV) with some unique features

Link: https://github.com/pmbauer/av-obsidian

av-obsidian

A King James (Authorized Version) text that is formatted for import into an Obsidian vault.

It uses Obsidian markdown, block reference, and LaTeX features to approximate the original print as much as possible.

Features

  1. One chapter per note, one verse per line.
  2. Uses obsidian block references for linking and embedding verses.
  3. Navigational links: Previous/Next chapter links.
  4. italicized words to indicate translation additions
  5. YHWH formatted LORD as in the original print
  6. original print paragraph markings and chapter notes
  7. KJV Cambridge
  8. _index and Book index pages

Usage

  1. Download the current release and extract locally
  2. Copy av into your obsidian vault.
### Chapter link
[[Genesis 1]]

### Verse Link
[[Genesis 1#^1]]

### Verse Link With Alias
[[Genesis 1#^4|Genesis 1:4]]

### Verse Transclusion
![[Malachi 4#^5]]
![[Malachi 4#^6]]

### Chapter Transclusion
![[1 John 3#1 John 3]]

Styling

The default Obsidian theme (and most themes) create excess whitespace around transcluded verses. I use the following CSS in a snippet to make notes with transcluded scriptures look nicer.

.markdown-embed-title { display:none; }
.markdown-preview-view .markdown-embed-content p:first-child { margin: 0 !important;}
.markdown-preview-view .markdown-embed-content p:last-child { margin: 0 !important;}

.markdown-preview-view .markdown-embed, .markdown-embed .markdown-preview-view {
    padding:0px 15px 0px 3px !important;
    margin:0 !important;
    max-height: unset !important;
}

/* the link on the top right corner */
.markdown-embed-link {
    top: 3px !important;
    right: 5px !important;
    padding:0 !important;
    margin:0 !important;
}

Normal

Styled

1 Like

Note, this is only the King James Version. For a setup that lets you manage multiple translations, @Joschua 's Bible Study in Obsidian Kit is what you want.

Many thanks, you’ve saved me (and many others I’m sure) a tremendous amount of prep time and work. Now before I go too far, I’m curious what your workflow will be to enter notes (such as those in a wide margin Bible) or linking to other material, etc? In short, how are you using this daily?

1 Like

I’m curious what your workflow will be to enter notes (such as those in a wide margin Bible) or linking to other material

I link to or embed (transclude) the scriptures from notes on sermons or devotions, as you see in the “Usage” section above. The other way I link or embed scriptures quickly is via [[^^ which lets you full-text-search based on phrases or words you remember.

The av-obsidian project uses a generic source format for the scripture text and transforms it into the release format - indexes, chapter-per-file, verse-per-line, backlink references, etc. I’ve gone through multiple iterations of how to structure the text in obsidian. As a result, I don’t put notes in the source text and only link into it so I can change the representation later. A previous iteration had book-per-file and chapters separated by headings.

This will probably sound like a dumb question, but when I put the av folder into my vault, I don’t see where the actual scriptures are. I see that there is a file called av.input, but I don’t know how to open it so that it shows up in my vault.

Check out the install instructions in the readme and in the parent post. The files you want are in the release archive, not the github repo.

Thank you! That worked!

1 Like