Laura Conrad wrote:
>>>>>> "Phil" == Phil Taylor <[EMAIL PROTECTED]> writes:
>
> Phil> Frank wrote (about automatic line-end fixing code):
> >>
> >> I think John's idea was to include it in the tune finder.
> >>
>
>
> Phil> Unless it can be made to work 100% correctly every time that's
> Phil> a bad idea, because it may well end up not fixing the problem
> Phil> and making it more difficult for the user to figure out what's
> Phil> gone wrong.
>
>I think the point here is that the user is someone who wants to see
>what the tune looks like before downloading it, and not someone who
>has written this particular ABC, or maybe even any ABC.
>
> Phil> Perhaps it would be better to run a series of checks for the
> Phil> symptoms of line wrap corruption and warn the user if found,
> Phil> rather than trying to correct it automatically.
>
>Again, this isn't a user who's intending (immediately) to edit the
>ABC.
>
Yes, I understand that. It doesn't fit with the way I use abc though.
When I'm at home I connect to the net through a 57Kb modem, and pay
for my telephone calls by the minute. I can download a file of 100
abcs in the time it takes to get a picture of one tune displayed, so
I never want to look at the pictures. (For the same reason I prefer
abcs to come in large files, rather than as individual tunes.)
I suppose though that that's the attitude of the experienced user;
many people who use JC's tune finder will just want the gif or midi
as they wouldn't know what to do with the abc. For such a user, an
automatic fixer would be an improvement even if it only worked for
some of the tunes.
Perhaps the best of all solutions would be to detect the bad tunes
and notify their owners so the problem can be fixed at source.
Phil Taylor
To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
