On 1 March 2012 22:28, Lex Trotman <[email protected]> wrote:
> On 1 March 2012 20:20, Svenn Are Bjerkem <[email protected]> wrote:
>> Hi,
>>
>> In a document I use attributes to create references to inline images.
>>
>> In the preamble:
>>
>> :i_line: image:gifs/linebutton.gif[height=12]
>> :i_fill: image:gifs/fillbutton.gif[height=12]
>> :i_color: image:gifs/colorbutton.gif[height=12]
>>
>> Somewhere down in the text
>>
>> 9. Experiment with the different Colors, Fill-styles, and
>> Border-styles available in the menus and toolbar. "Line Style" {i_line},
>> "Fill" {i_fill}, and "Color" {i_color} buttons.Some of the many varieties
>> are shown below.
>>
>> That construct breaks in dblatex with the error message that fillbutton.gif
>> and colorbutton.gif are unknown graphics extensions.
>> If I reconstruct the above passage to enforce that the inline graphics come
>> on separate lines, dblatex is happy. I have not checked with other backends.
>>
>> 9. Experiment with the different Colors, Fill-styles, and
>> Border-styles available in the menus and toolbar
>> .. "Line Style" {i_line},
>> .. "Fill" {i_fill}, and
>> .. "Color" {i_color} buttons.
>> +
>> Some of the many varieties are shown below.
>>
>> This happens on asciidoc 8.6.6
>
> This looks like a dblatex bug, it has nothing to do with attribute
> substitution, the file
>
> blah
> ====
>
> blah blah  image:list_icon.gif[] blah blah  image:list_icon2.gif[]  blah
>
> causes the same error for the second image.  But if both are the same
> file no problem?
>
> Suggest you generate xml from this source and submit a bug to dblatex

Just a postscript, it works fine if the images are png not gif so it
is definitely in dblatex gif image processing.

Cheers
Lex

-- 
You received this message because you are subscribed to the Google Groups 
"asciidoc" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/asciidoc?hl=en.

Reply via email to