I have a fair number of music "lyric books" that have the chords above the lyric, and I can scan them to PDF or DOC and cut and paste.

Alignment is difficult with most fonts because the letters aren't all the same width, and html "collapses" the spaces so that no matter how many you put in, only one out of any string of consecutive spaces is there in the post.

You could put non-breaking spaces      ( )     in, but that spoils the alignment during setup so that you can't tell if it's right except by posting (previewing).

Doing the setup in a monospaced typeface you could insert .... instead of spaces but it doesn't look very neat; and posted as ordinary text it won't necessarily be seen by others in the same font you used and most people use a variable spaced default font for viewing.

If I reformat the scanned stuff to a monospaced font like Courier, it takes very little cleanup to use the <pre> tag to post them. Unfortunately, few of the ones I have (that haven't already been posted) are of much interest to anyone here.

You do need a carriage return after the opening tag <pre> and after the last line before the closing tag </pre> to avoid "pushing" an extra space in on either top or bottom line.

The <pre> tag assures that what you typed (in monospaced text) will be seen by all readers that recognize the tag in a monospaced font, if they have one on their machine, and with all the spaces you typed.

The <sup> tag can be used, but I'd say the chord should consistently come immediately ahead of where it's played rather than after the syllable it belongs to:

^A7Mary had a ^DLittle ^ELamb

Or maybe that's what Bill D did, and he just plays a syncopated beat?

John