On 15.06.2011 09:21, Sebastian Rahtz wrote:
> On 14 Jun 2011, at 19:12, Matthias Einbrodt wrote:
>> ... is the best way to go right now. Although one could argue that
>> <figure> is for encoding graphical objects only and not for source code.
> I think I'd argue that <figure> is for chunks of content which are not part
> of the normal linear reading sequence, a discrete labelled section. So
> for some uses of code quoting, that fits, but not for others. As a rule of thumb,
> maybe, if it needs a <head>, its a figure.
> Myself, I'd be inclined to add @type to <eg> to solve your immediate problem.
One could also use <code> to encode chunks of source code as inline
elements or better if they don't need to have a heading/caption.
However, this would mean to use two different elements (<code> and <eg>
within <figure>) to encode the same content object in one document (if
there are either code blocks which have a caption/heading an code blocks
which don't have it).
Adding @type to <eg> would prevent the usage of two different elements
for the same content object, but you then have two elements to encode
chunks of source code as inline elements or without headings/captions
(namely, <code> and <eg type="..."/>).
Wouldn't it be better to allow <code> within <figure> or the arbitrary
Best regards, Matthias
> Sebastian Rahtz
> Head of Information and Support Group, Oxford University Computing Services
> 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
> Sólo le pido a Dios
> que el futuro no me sea indiferente