Hi Joachim,
> I'd be glad if you can send a short answer to this mail.
Is that your way of saying I talk too much? :)
> At the moment I'm creating a book module from a german PDF
> file, which
> includes images. But I don't know how to include them.
> Is there already a standard how images should be included or
> should we do
> this using ThML?
>> If you use ThML the frontends should implement support for
> this, right? I
> think the images should be store relatively to the data directory.
Yes, we should use ThML. (You could also use OSIS, but the OSIS filters
may not make it into 1.5.3. 1.5.3 is supposed to be finalized in the
next couple days... maybe today? But my OSIS filters are still only
about 1/2 done, and the Beta release of OSIS isn't going to happen for a
couple days either.) So just use the <img> tag like you would with
HTML.
If you want to link to something on the internet, you can obviously use
a full path, but local resources should have paths somehow relative to
the data directory as you suggest. I tinkered around with this for the
Catholic Encyclopedia and came up with the convention of putting all
images under the images directory, and then referencing them as
"images/imagename.jpg".
Leaving the images as separate files is one option (and the option Troy
seemed to like). My own feeling is that it can cause a lot of wasted
space beacause there may be many small images. So my suggestion was to
simply tar them and access them through that. If you're not doing your
own image rendering and are using an HTML widget instead, this would
raise issues of temporary file extraction & eventual deletion. So if no
one agrees with me, I will understand.
> P.S.: Your imp2gbs tool is great! Works well for me! Module
> creation is much
> more easy now.
Check out the imp2vs and imp2ld tools too. They're similar, but for
Bibles, commentaries, & LD modules. And in recent revisions, I allocate
my giant char arrays on the heap instead of on the stack. :)
--Chris