starred/audiobookshelf-advplyr

Fork 0

mirror of https://github.com/advplyr/audiobookshelf.git synced 2026-03-02 22:46:55 -05:00

[Enhancement]: Add option to enable/disable bold, italic, and underline for a chapter title to highlight different sections of a book #2257

New issue

Closed

opened 2026-02-20 10:17:37 -05:00 by deekerman · 4 comments

deekerman commented

2026-02-20 10:17:37 -05:00

Owner

Originally created by @ZLoth on GitHub (Sep 14, 2024).

Type of Enhancement

Web Interface/Frontend

Describe the Feature/Enhancement

In the chapter editor, it would be nice to flag an entire chapter title to have bold, italic, and/or underline enabled when displayed in the chapter list in either the web browser or ABS application.

Why would this be helpful?

In some audiobooks, the book is divided into different parts to sections. This can either be sub-books within the same book (e.g. Lord of the Rings", day designation (e.g Friday, January 21st), specific time period, specific sections, and so on. It would be nice to either toggle the entire chapter title so that the text is highlighted when displaying the chapter list in the app or on the web browser to emphasize different sections by the author.

Future Implementation (Screenshot)

Chapter editor

Example screenshots:

Audiobookshelf Server Version

v2.13.4

Current Implementation (Screenshot)

Originally created by @ZLoth on GitHub (Sep 14, 2024). ### Type of Enhancement Web Interface/Frontend ### Describe the Feature/Enhancement In the chapter editor, it would be nice to flag an entire chapter title to have bold, italic, and/or underline enabled when displayed in the chapter list in either the web browser or ABS application. ### Why would this be helpful? In some audiobooks, the book is divided into different parts to sections. This can either be sub-books within the same book (e.g. Lord of the Rings", day designation (e.g Friday, January 21st), specific time period, specific sections, and so on. It would be nice to either toggle the entire chapter title so that the text is highlighted when displaying the chapter list in the app or on the web browser to emphasize different sections by the author. ### Future Implementation (Screenshot) Chapter editor ![image](https://github.com/user-attachments/assets/c3d8d09f-2776-481f-8d24-aa966434e4ef) Example screenshots: ![image](https://github.com/user-attachments/assets/4a51f479-bf4f-43d2-85b7-02976a72e496) ![image](https://github.com/user-attachments/assets/d386ff78-bf82-479d-b928-5c22a1ce49e1) ![image](https://github.com/user-attachments/assets/5172f42a-0328-4dd0-9b2c-1e64ec588917) ### Audiobookshelf Server Version v2.13.4 ### Current Implementation (Screenshot) ![image](https://github.com/user-attachments/assets/a92316ba-e5d0-42e2-806e-1664773a0297)

deekerman

2026-02-20 10:17:37 -05:00

closed this issue
added the
enhancement
label

deekerman commented

2026-02-20 10:17:38 -05:00

Author

Owner

@ZLoth commented on GitHub (Sep 14, 2024):

Another idea is to have a "Section" checkbox on the chapter editor, and define how Sections should be styled as a all-user setting.

@ZLoth commented on GitHub (Sep 14, 2024): Another idea is to have a "Section" checkbox on the chapter editor, and define how Sections should be styled as a all-user setting.

deekerman commented

2026-02-20 10:17:38 -05:00

Author

Owner

@advplyr commented on GitHub (Sep 18, 2024):

Rich text for chapters is not going to be supported because we want the chapter names to also be embeddable in audio files. If it was rich text we would have to either store a rich text version of the name separately that we would have to keep in sync during scans or strip the rich text before embedding.
I can see how there are cases where it would be helpful to have that but the effort required to implement that outweighs the benefits to me.

@advplyr commented on GitHub (Sep 18, 2024): Rich text for chapters is not going to be supported because we want the chapter names to also be embeddable in audio files. If it was rich text we would have to either store a rich text version of the name separately that we would have to keep in sync during scans or strip the rich text before embedding. I can see how there are cases where it would be helpful to have that but the effort required to implement that outweighs the benefits to me.

deekerman commented

2026-02-20 10:17:38 -05:00

Author

Owner

@ZLoth commented on GitHub (Sep 18, 2024):

Rich text for chapters is not going to be supported because we want the chapter names to also be embeddable in audio files. If it was rich text we would have to either store a rich text version of the name separately that we would have to keep in sync during scans or strip the rich text before embedding.

I was looking at this from a database/client level as a flag to toggle the formatting in the ABS app or web client. In the file itself, it should be plain text.

@ZLoth commented on GitHub (Sep 18, 2024): > Rich text for chapters is not going to be supported because we want the chapter names to also be embeddable in audio files. If it was rich text we would have to either store a rich text version of the name separately that we would have to keep in sync during scans or strip the rich text before embedding. I was looking at this from a database/client level as a flag to toggle the formatting in the ABS app or web client. In the file itself, it should be plain text.

deekerman commented

2026-02-20 10:17:38 -05:00

Author

Owner

@ZLoth commented on GitHub (Feb 6, 2025):

In re-reviewing this issue, the bold/italic/underline should be set at metadata.json level. Example given:

    {
      "id": 1,
      "start": 299.9673,
      "end": 2029.537856,
      "title": "Chapter 1",
      "format": "bold, italic"
    },

We should not be touching the actual audio file data as it would remain localized with ABS.

@ZLoth commented on GitHub (Feb 6, 2025): In re-reviewing this issue, the bold/italic/underline should be set at metadata.json level. Example given: ``` { "id": 1, "start": 299.9673, "end": 2029.537856, "title": "Chapter 1", "format": "bold, italic" }, ``` We should _not_ be touching the actual audio file data as it would remain localized with ABS.

deekerman referenced this issue

2026-02-20 11:00:55 -05:00

[Enhancement]: Download SRT in Mobile App #3149