Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tag a chapter title as an unnumbered chapter #402

Closed
vkbo opened this issue Aug 15, 2020 · 2 comments · Fixed by #406
Closed

Tag a chapter title as an unnumbered chapter #402

vkbo opened this issue Aug 15, 2020 · 2 comments · Fixed by #406
Assignees
Labels
discussion Meta: Feature discussions enhancement Request: New feature or improvement potential feature Request: May be considered later

Comments

@vkbo
Copy link
Owner

vkbo commented Aug 15, 2020

The Issue

Currently, a chapter title must be in a file with layout "Unnumbered" for the chapter counter to be skipped. This removes the flexibility of writing a draft of a novel in a single file, or a set of files not split by chapter. The only title layout feature affected in this way is the the unnumbered chapter.

Proposed Solution

It should be possible to tag a chapter title heading as an unnumbered title heading as an additional alternative to the file layout option. In LaTeX, the * modifies a chapter or section to not be assigned a number. A similar approach here could be one of the following two options:

  1. ##* Chapter Tile where the * is added to the ##.
  2. ## *Chapter Title where the * is the first character of the title itself.

I prefer the latter option as it seems cleaner, and the * don't need to be parsed in most cases like by the syntax highlighter and document viewer (although maybe the viewer should filter it out), just picked up by the header generator in the Build Novel Project tool.

Since this is an alternative and entirely optional way to mark a chapter title as unnumbered, it doesn't really add complication, just another layer of customisability.

@vkbo vkbo added the enhancement Request: New feature or improvement label Aug 15, 2020
@vkbo vkbo self-assigned this Aug 15, 2020
@vkbo vkbo added discussion Meta: Feature discussions potential feature Request: May be considered later labels Aug 15, 2020
@vkbo vkbo added this to To Do (Features) in Release 1.0 - Core Features Aug 15, 2020
@vkbo vkbo linked a pull request Aug 15, 2020 that will close this issue
@vkbo vkbo closed this as completed in #406 Aug 15, 2020
Release 1.0 - Core Features automation moved this from To Do (Features) to Done Aug 15, 2020
@vkbo
Copy link
Owner Author

vkbo commented Aug 15, 2020

The first solution is implemented, using option 2 from above (only three new lines of code added), but leaving the issue open for now in case more changes will be made.

@vkbo vkbo reopened this Aug 15, 2020
Release 1.0 - Core Features automation moved this from Done to In Progress Aug 15, 2020
@vkbo vkbo added this to In Progress in Release 1.0 - Beta Testing Phase Aug 15, 2020
@vkbo vkbo removed this from In Progress in Release 1.0 - Core Features Aug 15, 2020
@vkbo
Copy link
Owner Author

vkbo commented Aug 18, 2020

I think the implemented solution works just fine. I'm closing this.

@vkbo vkbo closed this as completed Aug 18, 2020
Release 1.0 - Beta Testing Phase automation moved this from In Progress to Done Aug 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion Meta: Feature discussions enhancement Request: New feature or improvement potential feature Request: May be considered later
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

1 participant