I have found another potential reason for the messages you are seeing, that would also show on english clients. It seems that WoW will report wrong faction for NPC's quite often. That will produce a message when that happens when a quest is being picked up.
This can be seen by the message stating "Neutral" when the NPC is in fact faction specific.
I am currently working on a fix for that.

Sorry about that. That message should show up quite frequently on non-english clients. I could make a setting for that.

If you want to manually remove the message, you can find this line:at about line 984, and insert "--" in front of it to comment the line out.

I'm not quite sure what you meant by what you had changed, but what will be the change in the next version is after this line:This line has been added:1/20 is mostly derived from the fact that it will yield 1 iteration per second at 20 fps. This is very very slow, but hopefully playable at even very slow computers.
If you want to try this code, just add it in and see what happens. If you then want the merge faster at the cost of smoothness of the game, set the number to something bigger. The number is how many iterations are performed each frame, and it's only a lower limit.

I will look into this a bit more tomorrow, as it is too late at night right now.
I did however see an ugly pitfall in the merge-code that could happen if WoW runs at an average of close to or below 20 frames per seconds most of the time. That would cause the merge-code to throttle down indefinitely.

This limitation was made to make the game playable while the merge is taking place in the background.

In which case I will need to put a limit to how far down it can run the throttle.
I will run tests for this tomorrow.

The data comes from the supplied file "localization.en.lua". This data will however only be merged once, so the rather annoying process of it will only happen that one time. When that is done, your next login will be as normal, and in most cases even faster than usual.

The simplest way to kill the supplied data is to delete everything in that file, and replace it with ths:However, if you already have let it run up to 100% once (so you received the merge-report at the end), deleting the contents of that file will not do anything for you at all since the merge is finished.

Good point... I'll see what I can do.

The verdict is in, and I will not use MobInfo's data. There are two reasons for this. Firstly, it completely lacks location-info. Secondly, it does not support WoW's current item-classes (of the Wolf, of the Eagle, etc).
The last reason being the most important. That issue is so big that I suspect that is the reason why it was discontinued.

Well... I've been working on it since I read you post, and I must say that it is not very compatible. At the moment I am converting the database, and hopefully it will be okay. Tbh, the author of MobInfo have written a very nice addon-interface, but it is full of problems. So I am coping with those atm.
There are however a few negatives. MobInfo does not care about skinning and such, so that I think will be discarded. I may have to discard all of those based on my own internal skinning-list. This is a list that is deprecated in DropCount, but still exists for reference.
But normal loot items should be okay.

If the numbers are not screwing me, it should amount to more than 20.000 (give or take 2.000) different mobs. If all this goes through okay, I will make a new release of the addon.

I did look into that sort of briefly, but I put it aside as it was a slight hassle
Maybe I'll give it a shot. It does require quite a bit of converting, but nothing is impossible.