Thank-you all for the thought-provoking responses. I thought that there
were probably going to be a few issues along the way!
I shall have to have a think about how I would like the sources and
transcription to be presented.
I have read about the IMT but not yet really tried using it but I shall
definitely be doing so very soon.
On 09/08/2011 16:08, Martin Holmes wrote:
> Hi there,
> On 11-08-09 07:26 AM, Sebastian Rahtz wrote:
>>> I was looking at the gravestone example on the Oxford TEI talks
>>> which has a worked facsimile example and has an example rendering here
>>> I was kinda hoping that something along those lines would be what I
>>> would get.
>> Yes, something like that, one of thes days. Just needs time....
>> Of course if someone has some good working code, I would love to merge
>> it in.
> The Image Markup Tool has XSLT rendering code for <facsimile>,
> although it's fairly simple. The biggest problem here is that it's
> very difficult to write a general transformation that will handle
> creating a functional web page from any of the range of types of image
> that might be included. A project may have a single page-image with a
> sufficiently small number of zones on it such that it can be embedded
> directly in a single web page, or it may consist of 300 images and
> require a paging mechanism; the page images may already be sized
> appropriately for use on the web, or they may be enormous, and in a
> format such as TIFF that may not be supported by browsers; and it's by
> no means clear what should be done with links between <zone>s or
> <surface>s and elements in <text>. The IMT, as part of its
> transformation process, creates a version of the image at a suitable
> size for a web page, but this is obviously not done in the XSLT
> transformation itself.
> So I think this might be a case where "rolling your own" is the only
> practical approach.