Labels specified with "start_of_verse" are in MobileSheets above the respective verse section, in ChordPro 6.050 they were left of the verse, in ChordPro 6.060 they disappeared
@Mike:
newly imported, with Auto-Size Font = TRUE I get
Lyric Size: 28
ChordSize: 28
Grid Size: 13
As the chords in the grid are much too small imho I set them to 28, the same size as the chords above the lyrics
Now the grid doesn't fit on the page anymore, half of the last measure is cut off. There's nothing important there in that case, but who knows. The texts in the first column don't fit anymore as this column didn't grow as much as the measure column (maybe).
Pushing "Text Display Settings - Auto-Size Font" to go back to the previous state doesn't work.
I reduce the font sizes one by one to make the score fit on one page and end up with
Lyric Size: 18
ChordSize: 18
Grid Size: 18
Pretty good so far. That the PDF created with ChordPro 6.050 can use notably bigger fonts is caused by the issue that the start_of_verse statements are using extra lines.
I have to report the issue that ChordPro 6.060 doesn't show the verse labels to Sciurius (or maybe he has intentionally changed something).
Is it intentional that the C7 in the second line of the A part starts about the "hate" and not about the "I" where the chord changes (at least in all the vocal versions I know).
I thought in chordpro the chord symbol is always above the word where the change is.
Technically chords are shown above the first character of the closing bracket ]. From the musical point of view they shall be above the syllable at the beat where the chord changes.
You're right, well-known vocal versions e.g. Ella & Louis change chord on the word I. But it also works with "had" on the 1, you can even omit "I", try it.
Correct - I don't believe that was in the ChordPro documentation when I was first setting up the chord grid code. So it's another thing I'll have to account for.
(10-09-2024, 06:01 AM)Zubersoft Wrote: Correct - I don't believe that was in the ChordPro documentation when I was first setting up the chord grid code. So it's another thing I'll have to account for.
Yes, ChordPro is evolving too.
Directives will gradually start accepting properties next to / instead of fixed parameter strings since the latter are too limited.
To maintain compatibility, ChordPro looks for the presence of the pattern \w+=['"] in the params. E.g.
{start_of_verse This is verse 1} ← parameter string
{start_of_verse label="This is verse 1"} ← property
itsme just encountered a case where the naive detection fails.
@Sciurius: Thanks a lot. Copy/paste'ing the B’ (with the curly quote) from your previous post also works, just like b\' - it's not easy to see the difference.
I don't insist to see the prime symbol, I just prefer using ASCII characters - I rather lose typographical correctness and gain the advantage that it looks the same no matter if UTF8 or ISO8859-1 / Windows characterset is used.
@Mike: ChordPro is permanently improving. Not easy to keep track. https://groups.io/g/ChordPro/topic/v6_06.../108857060
For now I'll keep the released ChordPro 6.060 for comparing MobileSheets' new ChordPro features