No idea.
I am a bit surprized that it's working with full path
d:/konwerter/d:/xdxf. I have always used dictionaries in a subdirectory of the one in which
converter.exe resides.
That being said: Garbage in equals garbage out. So it's quite reasonable to assume that your mobi-2-xdxf conversion made things rather odd. If characters are wrong, you have probably edited a file and opened it as a windows character set, while is should be UTF-8.* No idea what php-script you're using. You do realize, that pocketbook.pl uses kindleunpack and converts from mobi? Of course,
not from all mobi, because the dictionary format is rather loose.
Still, I suggest you put the dictionary in the subdirectory dict in your main converter directory and run pocketbook.pl either with the html-file from kindleunpack or directly with the mobi-file if you've correctly installed KindleUnpack.**
Why don't you upload the dictionary and post a link, than we can at least see whether it works on Linux. Nowadays, Windows 10 boasts a Linux subsystem, so if it works on Linux
and you can't get it work on Windows, I won't be inclined to help you: You'll just have to use a Linux subsystem.
_____________
*Just a wild guess. However, it is safe to edit files with NotePad++ in Windows, because it allows for different character sets, Linux line endings
and windows line endings, etc.
**If you have KindleUnpack working with the perl script under Windows, please leave the i
nfo in an issue on github, so that I can add it to the readme. Basically, it amounts to being able to run at the terminal in the KindleUnpack directory the code:
Code:
python kindleunpack.py -r -s --epub_version=A -i "$InputFile" "$OutputFolder"