Not the positionable tag thing, but "~/Images" should be localized.
Reverting to the original state
Trying to fix the multiple image positioned tag removal
Fixed positionable tag deselction in InputMultiImageConfigMode.

Conflicts:
	DB/ImageInfo.cpp
deselectedTag only has to be declared if we're in InputSingleImageConfigMode.
Add a warning about area removal when a positionable category is deleted.
Prevent areas linked to a deleted category to be displayed in the annotation dialog. When the XML database is saved, they aren't stored, so they are deleted automatically :-)
Ask if the user really wants to un-mark a category as positionable.
Don't show areas linked against a category not marked as positionable anymore. Not putting it to the database still has to be implemented though ...
Only store areas to the XML database if the linked category is still positionable.
Fixed one special case: Be sure that the corresponding tag is still checked when adding areas to the image preview. The category could have been un-marked as positionable in the meantime and the tag could have been deselected, without triggering positionableTagDeselected and the area thus still remaining. If the area is then re-marked as positionable, the area would show up without the tag being selected.
It's of course the category that can be re-marked, not the area ;-)
Made it "nicer" :-)
Changed "categoryList" to a more convenient name ("categoryIsPositionable").
A bit of code cleanup and coding style adaption
Workaround for the "height = width = -1" bug, producing "invisible" areas that aren't displayed and can't be accessed/deleted
Performance tweak: we only have to be sure that we have the image's correct geometry if we can actually create areas.
It's even simpler, as we already have _areaCreationEnabled :-)
It's yet simpler: we already have the image's actual geometry in ImagePreview::pixmapLoaded!
Fixed areas being mapped wrong on images stored rotated (KPA does not store the un-rotated geometry, but the rotated one).