Comment 5 for bug 1173749

> 1a) So the users can't leave the editor before fixing the malformed
> tags? This would be the easiest solution, but not very user friendly.
> The user should have the possibility to save a song every time, even
> when it is malformed. Anyway, a message box should point out the user
> that there is an error an that the song could not be used in this state.

That would just be a stop gap soloutuon for 2.0. I think this is the most
as we can do seeming as we are not adding any new features to this release.
Its more user friendly than the current solution of showing the user a
criptic error message!

> 1b) This would be the advanced version of 1a, showing the wrong tags by
coloring them. Nice.

This would be for trunk (a.k.a 2.1) which we are adding features to.
Andreas' input on this would be valuable as he was having a look at
creating a WYSIWYG editor for the songs.

> 2. I don't think so. In my opinion there mustn't be any changes on any
song without the knowledge of the user.
> You don't know, if there is a tag too much or too less or if this is a
wrong written tag or ...

In which case we should just ignore it. The last thing I would want is to
have to find and show a song during spontaneous worship, and then for
OpenLP to force me to edit it before showing it.

> The user has to decide what to do with this malformed song.
> Possible actions would be: Cancel import or show song in editor. Maybe
ignoring the issue would be a possibility, too.

Unfortunately with a lot of the song importers we just have to make
assumptions about what we're importing. I don't think there is a single
importer which keeps formatting data (with the exception of possibly
OpenLyrics). We could log which files we had to drop any formatting from in
the import wizard.