10-19-2015, 09:55 PM
As maintainer of the original Chord program (now called Chordii) and keeper of the ChordPro standard, I've been thinking about this for a long while now. And the answer is "Yes, it is highly desired" and "No, there's no end to what would be needed."
So I am considering a different approach.
We have a mechanism that allows flexible formatting of text and other things: HTML. With CSS, you can control everything to the level of precision you need. The only thing required is a ChordPro processing tool that produces HTML. This is actually quite simple and I have an experimental version that produces the following HTML:
There are additional <div> classes for chorus, comments, and so on. You can view the resultant HTML in a browser, and tools like weasyprint can be used to generate good looking PDF pages. The CSS provides styles for screen and print media.
I think this approach has a much greater future than trying to crap in all kinds of {commentfont} {commentsize} {tabfont} and so on.
What do you think?
So I am considering a different approach.
We have a mechanism that allows flexible formatting of text and other things: HTML. With CSS, you can control everything to the level of precision you need. The only thing required is a ChordPro processing tool that produces HTML. This is actually quite simple and I have an experimental version that produces the following HTML:
Code:
<div class="title">Everybody Hurts</div>
<div class="subtitle">REM</div>
<div class="tab">...</div>
<div class="verse">
<table class="songline">
<tr class="chords">
<td>D </td><td>G </td><td>D </td><td>G </td><td>D </td>
</tr>
<tr class="lyrics">
<td>When your day is </td><td>long and the </td><td>night, the night is </td><td>yours a</td><td>lone</td>
</tr>
</table>
<table class="songline">
<tr class="chords">
<td>D </td><td>G </td><td>D </td><td>G </td>
</tr>
<tr class="lyrics">
<td>When you’re sure you’ve had e</td><td>nough of this </td><td>life, well </td><td>hang on</td>
</tr>
</table>
<div>
There are additional <div> classes for chorus, comments, and so on. You can view the resultant HTML in a browser, and tools like weasyprint can be used to generate good looking PDF pages. The CSS provides styles for screen and print media.
I think this approach has a much greater future than trying to crap in all kinds of {commentfont} {commentsize} {tabfont} and so on.
What do you think?
Johan
johanvromans.nl — hetgeluidvanseptember.nl — mojore.nl -- howsagoin.nl
Samsung Galaxy Note S7FE (T733) 12.4", Android 13.0, AirTurn Duo & Digit (Gigs).
Samsung Galaxy Note S4 (T830) 10.5", Android 10.0 (maintenance and backup).
Samsung A3 (A320FL), Android 8.0.0 (emergency).
johanvromans.nl — hetgeluidvanseptember.nl — mojore.nl -- howsagoin.nl
Samsung Galaxy Note S7FE (T733) 12.4", Android 13.0, AirTurn Duo & Digit (Gigs).
Samsung Galaxy Note S4 (T830) 10.5", Android 10.0 (maintenance and backup).
Samsung A3 (A320FL), Android 8.0.0 (emergency).