<br><div class="gmail_quote">On Wed, Nov 26, 2008 at 10:45 AM, Matthew Talbert <span dir="ltr"><<a href="mailto:ransom1982@gmail.com">ransom1982@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">> The point I was making was not that you can't encode it, but you lose the<br>
> semantic significance of it. The user can tell that <i>test</i> was added,<br>
> but the program can't - unless that is the only way <i> is ever used - which<br>
> it isn't. If you use italic formatting for anything else, you have lost<br>
> information - not presentation information - but the actual meaning is now<br>
> inaccessible to the program, as it can't necessarily tell what a particular<br>
> <i> means. If I want to mark translator added words in violet, or even allow<br>
> omitting them altogether, this is now not easily possible.<br>
<br>
</div>I've been around long enough to know there is some disagreement here,<br>
but not long enough to really understand the issues. So my question<br>
isn't intended to create an argument, I just want to understand.<br>
<br>
If encoding in OSIS means that presentation information intended to be<br>
there by the publisher is lost, then why is that the preferred format?<br>
I would think that it would be really important to a publisher (or<br>
just to a module creator like me) that things are presented as they<br>
want them to be. Are you saying OSIS doesn't really allow that? If so,<br>
then shouldn't something else be used?<br>
</blockquote><div> </div>OSIS will allow some degree of presentation information (e.g. <hi type="i">)<br>Generally, you will present the OSIS how it is presented in a print Bible. But sometimes, you may want to do something different - like omitting it, changing how it looks, etc. Also, for something like poetry, this requires special frontend support - but the end product for the ESV in BPBible, for example, is very close to a print ESV. You can't really encode this with ThML (that I know of).<br>
<br>If you just specified *how it looks*, not *what it actually is*, you can't support very complicated layout. Especially since modules are restricted to (<a href="http://crosswire.org/wiki/index.php/ThML_modules">http://crosswire.org/wiki/index.php/ThML_modules</a>):<br>
<blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote"><sync> (with type parameters of
Strongs, morph, & lemma), <scripRef>, and <note> (plus
closing tags where appropriate). HTML tags that ThML inherits, which
may be used in SWORD modules include <div> (with types of sechead
for section headings and title for titles, <i>, <br>, and
<b>. Additional HTML tags may be interpreted by those SWORD
frontends that render HTML, but will not be translated to RTF for the
Win32 frontend.
<br></blockquote><br>So OSIS tries to encode what the publisher means, not how it happens to look. How it looks will be decided by the frontend - but this will generally adhere to print Bible conventions.<br><br>As well, using OSIS helps searchability - search in Words of Christ, omitted text, poetry, etc.<br>
<br>God Bless,<br>Ben<br>-------------------------------------------------------------------------------------------<br>Multitudes, multitudes,<br> in the valley of decision!<br>For the day of the LORD is near<br> in the valley of decision.<br>
<br>Giôên 3:14 (ESV)<br><br>
<br></div><br>