Ok, here's how things are looking:
I have converted an entire new testament to a vpl file (verse-per-line), as I saw that this was basically what ToolTip NT asks for, and I was aiming for esword as a priority.
So far so well, module finished, working perfectly in esword. Now on to other formats... and here the trouble starts.
First I tried the "cheat"-solution by simply changing the file extension, as was mentioned on this forum. It worked quite decently, except that it wreaked havoc to UTF-8 characters, replacing them not just with weird symbols, but indeed with whole strings of numbers and slashes. Since this is a bosnian NT, it's quite unreadable. So I look for another solution.
Next, a web-search brings me to open bible reader, which makes rather impressive boasts about its IO capabilities. Unfortunately, it doesn't seem to do unicode either, so the vpl turns to giberish on import. I try to import the bblx file I created a bit earlier, but it can't open it. So much for that.
I come back here and take a look at the rather unweildy migration steps via TheWord, which I ignored before. I download all the neccessary stuff, then try to import my bblx file into TheWord importer. But the importer doesn't even want to start the process, claiming that my bblx file is password protected.
This is where I'm a bit out of ideas. There's two possibilities with what might be wrong with the last step: either TheWord importer screws up for some unknown reason which someone with more expierience on the matter might be able to uncover, or my bblx is indeed password protected and I'm too blind to find the export option in ToolTipNT that lets me turn off password protection.
If somebody could help me with that, I'd be much obliged. Alternatively, a reliable method to convert a vpl to a mysword module would also be appreciated.
