On Jun 21, 7:39 pm, ques...@[EMAIL PROTECTED]
(Harold Groot) wrote:
> On Sat, 21 Jun 2008 09:29:20 -0400, "Will Dockery"
>
>
>
> <dock...@[EMAIL PROTECTED]
> wrote:
>
> >"Harold Groot" wrote:
> >>Will Dockery wrote:
>
> >> >> >> Twilight Girl
>
> >> >> >> > This is the wait, =3DA0 =3DA0 =3DA0 =3DA0 =3DA0 =3DA0 =3DA0 =
=3DA0 =3DA0 =3DA0 =3DA0 =3DA0
> >=3D
> >> >=3DA0 =3DA0 =3DA0 the
> >> >> >> > weight of the world. Comes down sweet and heavy... =3DA0
=3DA0=
=3DA0 =3DA0
> >=3D
> >> >=3DA0 =3DA0
> >> >> >> > =3DA0 Twilight Girl.
>
> >> >> >> What a mess.
>
> >> >> I couldn't read it, that was the comment.
>
> >> >That's interesting.
>
> >> It was essentially unreadable here as well.
>
> >> To my (admittedly ancient) newreader, it's filled with a series of
> >> characters that are apparently its literal translations for some
> >> special character it doesn't recognize. Maybe the "equal
sign/Capital
> >> A/Zero/space" is an odd space, or tab, or something else, but it's
all
> >> over the place. But when quoted back to the originator, HIS reader
> >> probably re-translates it back to the original and so it looks fine
to
> >> him.
>
> >> In the part I quote above, after "This is the wait" there are fifteen
> >> "equal sign/Capital A/Zero/space" quads before we get to "the weight
> >> of the world" and it's like that throughout the entire set of lyrics.
>
> >> The originator might want to check to see that his program is set to
> >> post things in simple ASCII to strip out all the special characters.
>
> >> (As a side note, this is similar to a problem I've seen with several
> >> programs for Macintosh computers. Those Mac programs use an odd
> >> carriage return that shows up as a series of odd characters on
non-Mac
> >> computers. But I don't see him needing 15 consecutive CRs after
"This
> >> is the wait" so I don't think that's the problem here.)
>
> >Again, interesting that this happens, as well as unfortunate, though
whe=
n I
> >check it on Google Groups, where I first posted it, and now here, in
Out=
look
> >Express, it comes out fine in both:
>
> >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...
aga=
in.
> >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.
>
> >=A92008 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 in a desperate attempt
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 "=3D92" 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.
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.
I read in a pro****tional font and compose in fixed (when I'm not
using Google Groups because my news server appears to be on the Mars
Mission, again) for the speed of the first and the accuracy of the
second. If somebody sends space-formatted text, or ASCII art, all I
hafta to do is punch the "Reply" button to see the thing in fixed-
width font (in the composition window). (Google is displaying both in
pro****tional, as its composition window is part of its web page, not
of my composer.)
Lacking any of that, copy the offending text and paste it into
something like WordPad (or the Mac equivalent) set for a fixed-width
font.
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.
But we've seen his stuff all too often, and the usual explanation is
simply that he tried to get too damned clever in his attempts to
format his dribble to look "professional."
hth
>
> This might happen, I guess, if instead of typing each space separately
> the space bar was held down and the program had to decide "OK, the bar
> has been held down long enough, he wants another one".
>
> And for the version without the garbage - that is a quote using the
> same program that posted it, is it not? Perhaps when it READS the
> <repeat same character> instruction it knows to actually just PRESENT
> the repeated character (as if it had been manually typed)? I'm just
> guessing, here. This is not my area of expertise.
>
> So whether it was an odd character set or just what I don't know - but
> if you want your lyrics to be readable by the largest group of people
> it helps to post in the lowest common denominator (ASCII or "text").
|
