On Mar 17, 2007, at 9:17 AM, Joachim Ansorg wrote: > Hi, > >>> Perhaps what you can use is "mod2imp SomeModule > SomeModule.imp". > > mod2imp should restore everything in the module. > >> Thanks, but it doesn't restore the whole thing. I'm really >> looking for >> the bits which are *not* restored by doing this - especially anchors, >> ids, names and so on. My problem is I have ThML sources for general >> books and commentaries, and want to convert them to Sword >> modules. The >> thing that is especially difficult is how the ids and names etc in >> anchors get converted into references that Sword uses -- the internal >> <a> links in the modules I'm importing do not work once I've imported >> them into Sword. I'm using BibleTime to test, and know that the >> internal links in 'Institutes' do work, but I can't get the >> sources to >> see how this has been achieved. I have a similar problem with >> getting >> commentaries to work -- the ThML sources have correct <scripCom> >> tags, >> but the imported module appears empty when imported as a commentary. > > Could you give me an example of the internal links in Institutes? > Internal links always have been a problem. I don't think they work.
There was an earlier thread on internal linking in non-bible modules. And you are right, they do not work. We only support links to Bible verses. That thread outlined how we should handle it in the future. But I think the discussion was limited to OSIS modules. mod2imp should retain exactly what is in the module. mod2imp merely dumps the key followed by the raw text, in a form that can be used to recreate a module. When a module is created, it throws stuff away that is in between the keyed module entries. For the most part it does not modify the text that is stored in the module. > > A page which combines several items into one with links embedded is > done using > DisplayLevel >= 2 in the conf file. The links inserted are > BibleTime specific > using the module entries. It doesn't come from the source data. The DisplayLevel attribute was removed recently from all modules except GerAugustinus. I never knew what it was for. Thx. > >> Does no-one have copies of the exact sources used to generate the >> 'Institutes' or 'Luther' modules, or an exact description of the >> process >> used to turn them into Sword modules? That would be the quickest >> way to >> solve my problem. I have asked about this before, thinking that we should maintain the inputs we use for module creation. The response was that the module was sufficient. And in the case of copyrighted material for which Crosswire has been granted permission to distribute it as a module, we are not necessarily granted permission to distribute the original. The basic thought (that I was told) was that the owner of the source should be the place from which we get any modifications in the future. The problem is that some of those places no longer maintain the original and the originals may not exist anywhere else. Example, Bible Foundation (i.e. bf.org). We do have the "original" input for the KJV, but that is one that is created and maintained by Crosswire. > > I think Chris Little should have the sources. > > Troy has to approve the modules, please ask him directly about > submitting your > own modules to Crosswire. > > Joachim > -- > <>< Re: deemed > www.bibletime.info > > _______________________________________________ > sword-devel mailing list: sword-devel@crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page _______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page