Hi Chris,<br><br>My views are below...<br><br>On Tue, May 13, 2008 at 9:10 AM, Chris Little <<a href="mailto:chrislit@crosswire.org">chrislit@crosswire.org</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Our plans are to use TEI for dictionary encoding from here forth. At the<br>
moment we have some support for both P4 and P5 conversion to RTF (used<br>
by BibleCS), plain, and HTMLHREF (used by GnomeSword, BPBible?,<br>
others?). So...<br>
</blockquote><div>Yes, BPBible uses the htmlhref filter (at least inherits from it)<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Issue 1:<br>
<br>
Which filters remain necessary before we can declare that we support TEI<br>
and ship 1.5.11 with TEI support sufficient for all of the major frontends?<br>
<br>
I assume no one parses GBF, ThML, or OSIS directly for rendering. Does<br>
anyone use the plain HTML filter? (I'll tackle the WEBIF filters and do<br>
any revisions to the HTMLHREF that seem necessary.)<br>
</blockquote><div><br>I very much doubt anyone uses the plain html filter - it doesn't even support osis.<br>Is it worth dropping this from the library?<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>
Issue 2:<br>
<br>
I think DM and I (so far CrossWire's only 2 TEI encoders) are agreed on<br>
using the more recent TEI P5 for CrossWire-encoded texts. None of these<br>
are yet available publicly, but DM's NASB lexicons use P5 now and my<br>
(coming soon) revision of Webster's Dictionary uses it.<br>
<br>
Everything currently posted uses P4 (which was current at the time they<br>
were encoded). That includes stuff from Perseus (which came to us as<br>
TEI) and things from the Germanic Lexicons Project (which were encoded<br>
in TEI by me).<br>
<br>
Should we:<br>
a) support TEI P4 and P5 separately (so we would need TEI P4 and P5<br>
flavors of the filters targeting RTF, HTMLHREF, WEBIF, plain,<br>
etc.)--This would require extra work and a larger memory footprint than<br>
the other options.<br>
<br>
b) support TEI P4 and P5 jointly (one filter for TEI, irrespective of<br>
version, for each target markup)--This would be possible because there's<br>
not that much significant difference, but would be slighly wasteful.<br>
<br>
c) convert TEI P4 docs to P5 <br></blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
I think I prefer option c. It shouldn't be that difficult given the<br>
standards' similarity.<br>
</blockquote><div><br>c definitely sounds the best choice. <br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
--Chris<br>
<br>
_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page<br>
</blockquote></div><br><br clear="all"><br>-- <br>God Bless,<br>Ben<br>-------------------------------------------------------------------------------------------<br>The Lord is not slow to fulfill his promise as some count slowness,<br>
but is patient toward you, not wishing that any should perish,<br>but that all should reach repentance.<br>2 Peter 3:9 (ESV)