MobileRead Forums - View Single Post

pzack · 09-28-2022, 11:50 AM

Hello M. Sarmat89,

I used your line of code from post 98 on the tsv file created from last time then took the resulting file and ran it with the four lines of perl code. The file built from that was used with your line of code post 63. The file created from that code was used with pyglossary.

This time, pyglossary took another 200 seconds longer to build the stardict files.

There were still "[error] Warning: line staring with'....' has no tab" warnings and the index file had that question mark.

I didn't see any difference when I loaded the dictIonary into koreader from the previous files built. There are still a great amount of headwords without tabs and if a headword is found, only the line with the tabbed headword is shown.

It seems, with just a cursory check on the file, that the same headwords are being found from last time.

Cordially,
pz

09-28-2022, 11:50 AM	#103
pzack Connoisseur Posts: 79 Karma: 10 Join Date: Aug 2022 Device: kobo sage,elipsa	Hello M. Sarmat89, I used your line of code from post 98 on the tsv file created from last time then took the resulting file and ran it with the four lines of perl code. The file built from that was used with your line of code post 63. The file created from that code was used with pyglossary. This time, pyglossary took another 200 seconds longer to build the stardict files. There were still "[error] Warning: line staring with'....' has no tab" warnings and the index file had that question mark. I didn't see any difference when I loaded the dictIonary into koreader from the previous files built. There are still a great amount of headwords without tabs and if a headword is found, only the line with the tabbed headword is shown. It seems, with just a cursory check on the file, that the same headwords are being found from last time. Cordially, pz Last edited by pzack; 09-28-2022 at 12:19 PM.