hi weakling child,
im not sure, but i think, your umlaut issue has something to do with the missing unicode support in web source framework. I noticed the same with korean font bevore.
As far i understood, unicode is not going to be support that soon... only thing we can do is hoping and waiting...
best regards
yo.

Even if you don't use the client libraries, you should consider using the Web Services (RDF) API, as it is a committed interface, unlike the user presentation HTML. I don't think it would be that much more difficult to script using your Web Source Framework (although I don't use mp3tag and haven't looked at the framework).

First up great program, I like everyone else here really appreciates all of your efforts with this. I've been playing around with the WebSource commands, particularly to the discogs interface (far and away the best for all my dance music).

I would like to capture the styles information as it is generally pretty good but its hard to do at the moment.

could I request an extra command for the framework, which i think would add a lot of functionality. The command would be

IfFindInLine S

and a matching
ElseIfInLine S

would be even better. This would look in the current line past the current position for a character/string. However, it would not move to the found location. If the character is found in the current line a block of code will be evaluated. This would allow more complex behaviour to be done. For example: http://www.discogs.com/release/293551

The first problem is that the current version of discogs.scr expects a track time to be specified, such as

A Dub Will Tear Us Apart (1:23)

The current code is

do
...
sayuntil " ("

but the example i've given looks like

A Dub Will Tear Us Apart

It doesn't do have a "(" to find so it falls over. The IfInLine could be used for this

do
...
ifInLine " ("
sayuntil " ("
else
sayuntil "</td>"
endif

This way we would get the Track name correct in both cases.

The IfInLine would also allow the harvesting of the things in Styles:
ie the html for the styles for the above example is:

The other problem I could see with this is would the subsequent sayrests overwrite the earlier ones, or would it just add it on the end? (the preferred behaviour)

On another note, the command Sayrest is mentioned earlier in the help, but not listed in the formal list of commands down the bottom of the help page. Its fairly powerful at the moment for single artist albums, but discogs (and i'm sure others) has a wealth of information that i'd love to get in my tags. This would also make getting various artist albums possible.

I'm trying to add some new tag info to the AllMusic web source; by now I successfully extracted the Album Rating and the Moods list, but I found some problems with the composer of the songs.

It's possible to assign a different value to every track in the list?
The "tracks" values are separated with a pipe char ("|"), but using the same trick with the Composer (or every other field) I obtain a long concatenated string, with the same text for all the tracks, instead of a different value for every song.

I think that this behaviour could be a very good candidate for a feature request: It would have to be quite simple to implement (the "tracks" buffer already works this way).

On the other hand it could permit to extract and assign song-level information, by processing album-level web pages.

What do you think about it?

The current Development Build supports multiple values also for non-title fields. The separator is the pipe symbol | and the only constraint is, that the number of values is equal to the number of tracks.