NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
pub.dev
A Flutter package for parsing Bible texts in OSIS, USFX, and ZEFANIA formats with direct parsing and database-backed approaches. Includes desktop app for database creation and management.
Last release 4 months ago
28 May 2026
Release timing varies
gaps range from 1 weeks to 5 months
Nearly every release is documented
notes for 15 of 15 stable releases
Nothing withdrawn
no release was ever pulled
1 years old
15 releases · first in 2025
One column per month.
Book toc fields from USFX ` ` tags
<toc> tags
Book.longTitle — full descriptive title (toc level 1), e.g. "The First Book of Moses, Commonly Called Genesis"Book.shortTitle — common short title (toc level 2), e.g. "Genesis"Book.abbreviation — standard abbreviation (toc level 3), e.g. "Gen"null when not present in the source XML)long_title, short_title, abbreviation on books table (database version 6)ALTER TABLE — existing data is preservedbooks table gains: long_title TEXT, short_title TEXT, abbreviation TEXTusfx_toc_test.dartFootnote parsing for USFX format - tags are now fully parsed
<f> tags are now fully parsed
Footnote class with id, marker, and content fieldsTextSegment entries with attributes['footnote'] set¹, ², ³...) auto-assigned per verseverse.hasFootnotes convenience gettersegment.isFootnoteMarker and segment.footnoteId getters on TextSegmentverse_footnotes table (database version 5)getVerses, getVerse, and searchVersesFootnote exported from main library entry pointnull for footnotes.verse_footnotes (id, verse_id, footnote_id, marker, content)usfx_footnote_test.dartComplete desktop app for Bible database creation
Major Features:
Enhancements:
This release transforms the package from a parsing library to a complete Bible database management solution.
dbfiles/ directoryflutter run sessionsbible_parser_flutter/
├── lib/ # Core parsing library
├── desktop_app/ # New desktop application
│ ├── lib/main.dart # Desktop app UI and logic
│ ├── test/ # Desktop app tests
│ └── macos/ # macOS platform files
└── doc/ # Updated documentation
This release transforms the package from a parsing library to a complete Bible database management solution. Developers can now:
Code quality improvements - Fixed string concatenation linting issues
+ operator with string interpolation in USFX parsercurrentVerse.text + ' ' + trimmedText to '${currentVerse.text} $trimmedText'parseBooks() and parseVerses() methodsflutter analyze lib/ now reports no issuesAdded text support for USFX format - Track translator additions (italicized text) in USFX files
<add> tags in USFX XMLtransChange: 'added' attribute as OSIS format for consistency<wj> tags) when both are presenteng-kjv-2006.usfx.xml, eng-asv.usfx.xml, eng-webu.usfx.xml// USFX added text is tracked the same way as OSIS
for (final segment in verse.segments ?? []) {
if (segment.isAdded) {
// Render in italics (translator addition)
print('Italic: ${segment.text}');
} else if (segment.isJesus) {
// Render in red (Jesus' words)
print('Red: ${segment.text}');
}
}Version 0.2.3 - Critical bug fix for duplicate verses
Version 0.2.3 - Critical bug fix for duplicate verses
verseEndedWithEID flag to prevent duplicate verse insertion when processing <verse eID=""/> format (affects KJV and similar OSIS files)(book_id, chapter_num, verse_num) in verses table to prevent duplicates at database levelparseBooks() and parseVerses() methods now handle eID format correctlyThe duplicate verses issue had two contributing factors:
<verse eID=""/> tagsConflictAlgorithm.ignoreTransChange support for OSIS format to track added/italicized text
<transChange type="added"> tags in OSIS XMLtransChange getter on TextSegment classisAdded convenience getter to identify added text segments// Check if a segment is added text (typically italicized)
for (final segment in verse.segments ?? []) {
if (segment.isAdded) {
// Render in italics
print('Italic: ${segment.text}');
} else {
print('Normal: ${segment.text}');
}
}
Critical iOS/Android compatibility issue - Fixed SQLite error 14 (SQLITE_CANTOPEN) on iOS devices
sqflite for iOS and Android instead of FFIsqflite_common_ffiFixes #4
Updated example app to demonstrate red-letter Bible feature
[JESUS: ...] markersThis major feature release adds support for identifying and styling Jesus' words in OSIS and USFX Bible formats.
This major feature release adds support for identifying and styling Jesus' words in OSIS and USFX Bible formats.
TextSegment class for styled text segments with attributessegments field in Verse class for tracking speaker information<q who="Jesus"> tags in OSIS XML<wj> (Words of Jesus) tags in USFX XMLhasJesusWords convenience getter on Verse classverse_segments table for storing text segmentsOsisParser, UsfxParser, ZefaniaParser) for direct useVerse class is backward compatible - existing code continues to workBibleRepository now persists and retrieves segments automatically/doc/red-letter-bible-support.mdPublished to pub.dev: https://pub.dev/packages/bible_parser_flutter
TextSegment class for styled text segments with attributessegments field in Verse class for tracking speaker information and other attributes<q who="Jesus"> tags in OSIS XML to identify Jesus' words<wj> (Words of Jesus) tags in USFX XMLhasJesusWords convenience getter on Verse classverse_segments table for storing text segmentsOsisParser, UsfxParser, ZefaniaParser) for direct useVerse class is backward compatible - existing code continues to workBibleRepository now persists and retrieves segments automatically/doc/red-letter-bible-support.mdSupport for multiple Bible XML formats:
Added note about tested XML file compatibility in README
N/A
Fixed verse text concatenation with proper space handling and empty text checks
N/A
Fixed USFX parser to properly handle chapter endings and ensure all chapters are added to books
Fixed handling of footnotes and cross-references in USFX parser
Your coding agent can read these notes before it upgrades. Set up the MCP server →