Quote:
Originally posted by medman
This leads to the accumulation of hundreds of pages and what I want to do is to create a html file for every letter that will include the links for every drug info page which I previously saved. The idea is to load these files into iSiloX. I can do that manually, but that is a lot of work. My question is how to automate the process of adding the links of the specific drug files into the file I want to load into iSiloX.
|
I understand better now. Sorry for the confusion! But I am curious...why is it you want 26+/- iSilo files vs. 1? If you achieve this, I'm sure the 26 files collectively will be much, much larger than the 1 file. Plus if you're in a "B" drug and need to look up a "G" drug, you have to close one file, go back to the main iSilo index and open another. Takes a lot more time than working within one file. I don't mean to pry, I'm sure you have reasons for breaking this up....just curious as to why.
There is no iSilo-based command to process one html file and split it into 26 files. There is probably a way to write a perl or php script to do this, but the effort would probably exceed doing the manual process below.
Is the ebook one html file or a bunch of html files?
Part of the problem giving you some accurate advice is that i don't know the structure of your eBook. Some are self-contained html files, some a collection of files, and some have subHtml files hidden within. If you can, while viewing your eBook see an actual path that's unique for the adrugs, then you may be able to specify pulling only that page, but it's a manual task within iSilox, I believe.
You can create a channel for each letter by specifying to exclude all in the URL filter, then include only the adrug.htm and associated pages. You can then copypaste this channel, and modify the includes to reference the bdrug.htm, and so forth. (This is assuming you have seperate .htm files for each drug.)
Let me know if this clears anything up, or confuses the issue even more!
