"Amanda Reid" wrote:
>"Harold Groot" wrote:
>>Will Dockery wrote:
>
> >Twilight Girl
>
> >E Esus4 E
> >A E A
> > E
> >Six or six thousand, we will meet again.
> >A E D
A
> > E
> >At blazing dusk, or quiet dawn. On that shore...
again.
> >C# A B E
> >This is the wait, the weight of the world.
> >C# A B Tacet
E
> >Comes down sweet and heavy... Twilight Girl.
>
> >On that quiet morning, clear, crispy light.
> >Seeing a movie from a distance, mourning in front of her flight.
>
> >This is the wait, the weight of the
world.
> >Comes down sweet and heavy, Twilight Girl.
>
> >Bridge:
> >D A
> >She offered me her cup, asked me to fill it up,
> > E D
> >I said "Later, babe. Right now we have to talk
> >A B7
> > Tacet
> >Untangle the chakra that crosses over."
>
> >Ghost horses, from the car ahead, looks like engine exhaust.
> >Blink my eyes through bitter tears, a smile for what we shared
>
> >This is the wait, the weight of the
world.
> >Comes down sweet and heavy... Twilight Girl.
>
> >©2008 by Will Dockery and Henry Conley
>
> >So I don't know how I'd go about attempting to fix something that
doesn't
> >seem broken... I'll look into it, though.
> >http://www.wikinfo.org/index.php/Will_Dockery
>
> And curiously enough, this version came through WITHOUT all those
> garbage characters. I haven't changed any settings on my newsreader,
> did you do something different in how you posted it?
>
> The other curiousity is that the "equalsign/Capital A/Zero/Space" is
> apparently just a space in your lyrics - but the standard single
> spaces between words came through as single spaces. It was just in
> the places where you had large numbers of spaces in a row that they
> became those garbage characters. It's sort of as if instead of having
> a set of <space> <space> etc. it was <space> <repeat last character>
> <repeat...> and it was the <repeat last character> that showed up as
> equalsign/etc.
The keyboard encoder chip used to do that, and so does WinDoze (you
can set delay and rate), but the instructions to repeat are not part
of any typing program and do not appear as any part of the text file.
which sees only a series of plain spaces (ASCII 020h).
He's more probably using a "hard" or em space to make the chords come
out
over the words, and most newsreaders hate
those "special" ANSI (not ASCII) characters, variously translating
them back into those arcane "=92" or "&@[EMAIL PROTECTED]
" entries.
Not only will newsreaders do that to "quoted text," thus sending it
back out garbled for you to read at second hand, several community
news servers (such as but not necessarily Yahoo!, or Google Groups,
which deletes TABs, e.g.) will do the same thing.
And here's a new oddity, where your reply isn't /quoting/.
If Willie would use plain spaces (ASCII 20h) and a newsreader that did
not delete multiple spaces (DejaNews and InterNet Exploder used to be
good at that), and understood that if he and the reader used a /fixed-
width font/, the characters would appear where he put them.
Since the text and chords appear where they should be on both Google
Groups
and Outlook Express, I assume the problem is with individual newsreaders
and
not with the source.
Another common problem arises when the text has been quoted several
times, which causes a quote character (usually the >, as here) to be
inserted at the head of each line. This causes the line-length
limiter of the /quoting/ composer to break some lines (those one
character too long) while not breaking others. It is evident that
that has already happened to Mr. Dockery's chord notations.
Well, that's a given when posting and replying on Usenet.
--
Greybeard Cavalier
http://www.youtube.com/watch?v=r6BGlXmtzE8
Vocals: Will Dockery. Music: The Shadowville Allstars. Based on "Greybeard
Cavalier" by Will Dockery, 0x0000 and Brian Fowler. Video by Doug Cole
|
