On Jan 29, 2008, at 3:25 PM, Karl Kleinpaste wrote: >>> Please also note that ThML is no longer actively supported by >>> CrossWire and it is unlikely that we would post a new module that >>> uses >>> ThML. The same goes for GBF. We only actively support OSIS. > > That's only superficially true. I submit patches to Sword's ThML > support from time to time and Troy has never been averse to applying > them, including those for newer features such as clickable images, for > which the original patch over a year ago included support in both ThML > and OSIS. Most recently, he made fixes to accommodate better RTF > targeting from ThML on my request and he dealt with some minor markup > glitches in both OSIS and ThML (whose processing tends to be very > similar).
Or, more precisely, it was superficially untrue. Obviously we will do maintenance-level support. When underlying changes are made that affect all drivers, ThML drivers get minor updates like everything else. If bugs are found, we correct them. I don't think non- detrimental patches are ever rejected, provided they fit well within the overall architecture. And naturally, features added to the OSIS filters may sometimes be ported back to the ThML ones. (The ThML filters are based on the GBF filters. The OSIS filters are based on the ThML filters. And the TEI filters are based on the OSIS filters.) But there's not going to be any push to complete tag support for ThML. And I don't plan to release any further modules in markup formats other than OSIS, TEI, and perhaps the odd plaintext Bible. I'm hoping the ThML to OSIS XSLT will permit us to leverage CCEL's content in spite of this. --Chris _______________________________________________ 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
