Ok,

now I know what's causing the issue.

Well...mainly it's because the datfile uses non-ascii characters, ie unicode chars (byte size) which are mapped to 0 to 255 DEPENDING ON THE used codepage. That's why it works flawlessly here and fails for US (could be viceversa for other chars though).

So the next version of cmpro will have a new option to turn on/off Ansi2OEM/OEM2Ansi conversion which the user has to decide.

Although this will have some consequences for viewing the zipfile. Depending on the viewer (winrar, winzip fails btw...) you see the correct spelling or a mapped one....

And the double entry is caused by a wrong conversion, too...should be fixed with the next release, too.

To sum it....don't use such dats ;)



Roman Scherzer