[
http://jira.codehaus.org/browse/DOXIA-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_123793
]
Lukas Theussl commented on DOXIA-99:
------------------------------------
I think it has by now become a de-facto standard in maven land that figures in
apt require an extension. Figure sources are just links, and so should be valid
and unique as such. Since we have already decided to deviate from the original
apt format (see
http://docs.codehaus.org/display/DOXIA/Proposed+Changes+to+the+APT+Format), I
think it would be the cleanest solution to leave it like that. So a parser
should just emit the figure source as is, and any sink can check if it supports
the figure format and if not, give a warning, try to convert, look for another
source, or whatever.
One option we could implement for (partial) compatibility with aptconvert is
that the AptParser checks if the figure source has an extension, and if not
append a default one.
> Figures require extension in APT and they should not
> ----------------------------------------------------
>
> Key: DOXIA-99
> URL: http://jira.codehaus.org/browse/DOXIA-99
> Project: Maven Doxia
> Issue Type: Bug
> Components: Module - Apt
> Affects Versions: 1.0-alpha-5, 1.0-alpha-6, 1.0-alpha-7, 1.0-alpha-8
> Reporter: Greg Luck
> Assignee: Jason van Zyl
> Fix For: 1.0-beta-1
>
>
> Figures require extension in APT and they should not.
> For example, http://ehcache.sourceforge.net/nameandlogo.html shows a broken
> image. The APT for this page is:
> [images/ehcache_logo]
> Now, if I change it to [images/ehcache_logo.gif] it works. However this
> breaks aptconvert. The reason is that it is illegal in APT to specify the
> figure extension. I use aptconvert to create a pdf and single HTML page.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
