Small song information customisation

[DeeTigIT]

Currently, the small song information consists of 2 fields F1 en F2 placed above each other with fixed contents:

F1: title
F2: author (ccli)

If the song is without ccli, then F2 looks like: author
If the song is without author, then F2 looks like: (ccli)
If the song is without ccli and author, F2 is empty.

Can this be made customizable in the user options for both fields F1 and F2?
Below are some thoughts on this.
Perhaps we can use keywords like: {empty}, {title}, {author}, {ccli}, {copyright}, {year}, {publiser}, {key}, {capo}?
Then the user could use these keywords to compose format strings in the 2 new user options for the fields F1 and F2.
During projection these keywords are to be replaced by their actual song values.

Example 1 (= current situation):
F1: {title}
F2: {author} ({ccli})

Example 2:
F1: {title} - {author}
F2: {year}

Example 3:
F1: {empty}
F2: {capo}

Ref:
https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!topic/quelea-discuss/b_FgbXyAD34

[DeeTigIT]

I recollect a Q&A topic on the Quelea Discussion Group:
Q: You mention the experimental CCLI small text. I was wondering how that is accessed.
A: If you put "church.ccli.num=123123" in your quelea.properties file, this should trigger the new behaviour.

So this can already be used for displaying one’s own CCLI licence number.
When specified in the properties file, 2 two fields currently are filled follows:
F1: {title} by {author}
F2: {ccli license number}
So the song ccli is then not shown anymore.

Perhaps Copyright Display #222 can be combined with this issue?

By the way, if one really needs to display the full copyright (and also author(s)) then the screen space might be inadequate. :-) Example:

[DeeTigIT]

Perhaps Add option to Center Song Title #248 can be combined with this issue?

[quelea-bot]

This issue has been mentioned on Quelea community. There might be relevant details there:

https://quelea.discourse.group/t/ccli/524/2

[NF53]

It would be great to see some progress on the Copyright issue - it is required by the CCLI licence.

Yes, some copyright fields are very long - but that can't be a reason to ignore the issue. If that becomes a problem for a particular song, some condensation by the user would be possible, and better than nothing.