[sword-devel] OSIS formatting

Daniel Glassey dglassey at gmail.com
Wed Jun 15 21:11:52 MST 2005

> Greg Hellings wrote:
> > Howdy!
> >
> > I have been working with some possible modules in ThML, but would like
> > to try and migrate their base formatting into OSIS so that I can create
> > the modules as other than General Book with a minimal amount of effort.
> > So far the process of migration has gone well with one exception: I am
> > unable to decipher how to represent presentational formatting in OSIS.
> > Formerly most of the formatting was created using style="..." tags in
> > the ThML and it worked marvelously.  Is there any similar method in
> > OSIS?  ...or how would one encode formatting information in OSIS?  Thanks!

On 10/06/05, Troy A. Griffitts <scribe at crosswire.org> wrote:
> Greg,
>         OSIS' purpose is to mark the elements in a text as what they are, not
> how they should be displayed.  The way elements are displayed is left
> out for another 'presentation layer' to handle as it sees fit.
>         Now, having said that, there is an evil workaround for elements that
> you just can't figure out why they are ornimented in some way: <hi>
> e.g. <hi type="bold">bold text for some reason</hi>
> The defined type attributes on hi are currently:
> <xs:enumeration value="bold"/>
> <xs:enumeration value="emphasis"/>
> <xs:enumeration value="illuminated"/>
> <xs:enumeration value="italic"/>
> <xs:enumeration value="line-through"/>
> <xs:enumeration value="normal"/>
> <xs:enumeration value="small-caps"/>
> <xs:enumeration value="sub"/>
> <xs:enumeration value="super"/>
> <xs:enumeration value="underline"/>
> I don't think the latest version of our engine pays much attention to
> <hi> right now, but we should.  I think, currently, you'll mostly get
> italic for any <hi> you define.
>         Hope this helps,
>                 -Troy.

In the end we've just gone with ThML because there is so much
presentational stuff that just can't be thrown away or easily put into
OSIS like that even for the commentaries. Not sure if we'll look at
getting it into OSIS later or not.


More information about the sword-devel mailing list