You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Section 3.4 "Managing media" includes a note which states that Actually copying the media files from where they are in the source system to where they need to be in the HTML is “not our problem”. That's true, but in order to support users to solve this problem, it would be helpful when the stylesheets would provide a map (or other datastructure) which holds for every media file
the path / URI to the source file;
the path / URI where the generated HTML file expects them
Users of the stylesheets could
serialize this map and use it as an input for following steps (shell or ant scripts, for example)
use it in the post-processing step to copy files with the expath:file module, if they have Saxon PE or EE
See the xsl:message at the end of template for h:img/@src, in default-mode m:chunk-cleanup in file chunk-cleanup.xsl (line 626 ff). Seems to display for an image uri:
the author’s original value,
the uri that was calculated in mode m:mediaobject-uris,
the adjusted uri from mode m:mediaobject-output-adjust which will be used in the HTML
Greetings, Frank
The text was updated successfully, but these errors were encountered:
Section 3.4 "Managing media" includes a note which states that Actually copying the media files from where they are in the source system to where they need to be in the HTML is “not our problem”. That's true, but in order to support users to solve this problem, it would be helpful when the stylesheets would provide a map (or other datastructure) which holds for every media file
Users of the stylesheets could
See the
xsl:message
at the end of template forh:img/@src
, in default-modem:chunk-cleanup
in filechunk-cleanup.xsl
(line 626 ff). Seems to display for an image uri:m:mediaobject-uris
,m:mediaobject-output-adjust
which will be used in the HTMLGreetings, Frank
The text was updated successfully, but these errors were encountered: