[pzack]

Hello M. Markismus,

I was able to get koreader to see the dictionary. But, the index was skewed and nothing matched the word searched.

Here's what I did; I deleted all preliminary material in the txt file and just had words with definitions. I did this in notepad++ and I did not change lines but notepad changed the line count.

In pyglossary I got a lot of "[error]invalid row["]" messages and sometimes the same type of message appeared but text appeared in the [] brackets instead of just ["].

This time pyglossary really worked the text taking 691.4 seconds to convert rather than the 3 seconds the other time before I edited the text file. And this time, at least, the dictionary was seen in stardict even though I couldn't get a match of the word found to the word searched.

I also received an [info] message in pyglossary telling me it failed to detect sourceLang and targetLangue frome the csv glossary name(I named the csv file l-nantes.csv).

The .idx file had a "?" mark on the file icon that is seen in file manager.

In the dicitonary list in koreader the dictionary name still has a .csv tag.

There is then, a partial success. Can you suggest a solution to getting stardict to find the correct word in the data file?

Slowly, but surely, I think we're getting to a functioning stardict dictionary.

cordially,
pz