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

Feature: capo declaration #20

Open
Lamera opened this issue Dec 12, 2023 · 3 comments
Open

Feature: capo declaration #20

Lamera opened this issue Dec 12, 2023 · 3 comments
Assignees

Comments

@Lamera
Copy link

Lamera commented Dec 12, 2023

Hello @vojtechkral
Thanks for your continous work. I just updated my songbook to the latest version 2.0.1.

I have many songs that require a capo.
Until now I declared the capo like this:

# song1
## band

K:2

The problem is that the page size is limited and sometimes a page break occurs just because of this one line.
I would like to see a feature that handles this K:2 and places it to the top right of the page so it doesn't take up any more vertical space.
And maybe we can highlight that using a red bold font. What do you think?

@vojtechkral
Copy link
Owner

Hi. I would recommend doing this using a syntax extension, like this

# song1
## band

<capo>2</capo>

See the Custom Extensions documentation on how to do this. Wdyt?

@Lamera
Copy link
Author

Lamera commented Dec 12, 2023

I think this should work.
But I also think this is something that should be defined in the default template.
I just have to figure out on how to place the item to the correct position on the page …

Btw: can we define a custom extension file where all special customizations from a template are stored. And this file would then be loaded into the default template? So it would be more practical to update to a newer template version?

@vojtechkral
Copy link
Owner

But I also think this is something that should be defined in the default template.

I mean, maybe, it's easy to overcomplicate it. I had similar feelings about time signatures (4/4, 3/4, etc.) but ultimately I left them out even though it would be useful sometimes.

Btw: can we define a custom extension file where all special customizations from a template are stored. And this file would then be loaded into the default template? So it would be more practical to update to a newer template version?

Yeah. It's a bit tricky and it would still not guarantee a seamless udpate, but would improve the practicality. So yes, I'll have a look into it at some point.

@vojtechkral vojtechkral self-assigned this Feb 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants