Problem with convering big project

[marcinm123]

Hello,

I'm tryng to convert Polish Dictionary of about 75000 files. The dictionary is arranged into 7 subdirectories containing 10K files in each, plus the index.html in the main dir.

However, after converting the entire diciotnary in IsiloX with no errors I get only 292 bytes long file... When I experimentaly decrease the number of files to approx 65K I get normal output file of about 12 MB.

So, does Isilo and IsiloX support only about 65536 links in the main file? How to break this limit, I see no reason to split this dictionary in 2 files, whereas the size is not very big? Are there any options that could help me create a diciotnary with all 75K definitions in one file?

Best Regards,
Marcin M., Poland

[iSilo]

The problem is not the number of links but the number of pages/files.

The iSilo file format has a limitation of about 65000 pages. With 75000 files, you need 75000 pages.

To work around this, you would need to place more than one definition in each source file instead of having only one definition per source file.

[marcinm123]

The solution you suggested would brake the hyperlinks between the word definitions and would also require lots of editing by hand and redesigning, with that big project it is vitually impossible.

I think the 65K limit the biggest limitation of IsiloX and Isilo at the moment, do your plan increasing this limit in future releases? Is it possible at all, or this limit is a consequence of PalmOS design itself?

[iSilo]

There are no immediate plans to increase the limit. It would require a major change and redesign throughout.

What is the source of the dictionary? If the HTML version of the dictionary was created from a database or other source by some automated script or other means, which I would think it must have been, perhaps a script could be written to generate HTML source with a different organization.

[marcinm123]

Yes, the HTML version was created using a set of scripts from a database. Of course the changes could be made to these scripts, but I see no reason to do this, as the entire layout of the dictionary would loose its clarity if more than one definition would reside on one page, furthermore searching the entire DB would be slower. I think that with this kind of content this design is optimal.

I this situation I consider splitting ths dictionary on two parts the best solution.

Thank you for your help.

Best Regars,
Marcin M.