Implementation Considerations 10-3
10.5 Converting Vector Graphics and Spreadsheet Text in UNIX
Dynamic Converter requires access to a running X-Server in UNIX in order to convert vector graphics and to properly measure text that spans multiple columns in
spreadsheets.
See the Dynamic Converter Installation Guide for instructions on how to set up rendering of graphics and fonts in UNIX.
10.6 URL Rewriting
Dynamic Converter wraps the dcUrlurl, reserved_type Idoc Script extension function around all hyperlinks and image source links src. The default
implementation of this script function is to do a simply pass-through, but external integration technologies such as CIS can modify this behavior by defining a filter
plug-in for dcUrlFilter.
Dynamic Converter evaluates the link URL, applies the dcUrlFilter filter if it exists, and then return the URL value. If the dcUrlFilter filter is not defined, then the original
URL is unchanged. Links to internal bookmarks always remain unchanged.
Reserved Types The reserved_type function argument is a number 1001, 1002, etc., which indicates
where in the Dynamic Converter core engine the URL is being written. This value can be used to distinguish the type of URL. For example, gallery graphic, inter-document
link, etc. The reserved type values and their meanings are as follows:
Value Description
1001 Link different split
1002 Previous element different split
1003 Previous page TOC frame
1004 Previous page
1005 Next page TOC frame
1006 Next page
1007 Next element different split
1008 Previous page TOC frame
1009 Previous page
1010 Next page TOC frame
1011 Next page
1018 Image link
1019 Image link
1020 Image link
1021 Image link
1022 Background graphic not from source
1023 Background graphic from source
10-4 Administrators Guide for Dynamic Converter
10.7 Relative URLs in Templates and Layout Files
Consider the following image tag: IMG SRC=image.gif. In most implementations of Dynamic Converter, it is likely that the output files will end up in
a different location than the template files. If the developer uses the template above in this scenario, the output files produced will have a reference to image.gif, which the
browser will assume has the same path as the output files. The problem is that image.gif is likely to be back in the directory where the template file is located. This is a
problem for anything referenced in the template using a relative URL. There are several possible solutions to this problem.
Solution 1: Ensure That the References Are Good
If the developer knows exactly which files all of the templates reference, the correct files such as image.gif can be moved to or located in the output directory or
directories. This solution requires the developer to have exact knowledge of the contents of the templates, and may propagate the same set of files into many output
locations.
Solution 2: Use Absolute URLs
The developer can design templates to contain absolute URLs to any referenced files. The template in the example would then look something like this.
HTML BODY
PIMG SRC=http:www.company.comtemplatesimage.gifP { INSERT ELEMENT=Sections.1.Body}
BODY HTML
If HTTPWEBROOT is used instead, you eliminate the problem of output files tied to a specific domain.
Solution 3: Make Path Statements in a Separate File
The developer can create a separate Idoc Script file that states the path, for example: dynamichtml Image_DirHttpWebRootgroupspublicdocumentsgraphicend
The developer can then load the Idoc resource and reference the path statement from the included Idoc Script file as follows:
img src=include Image_Dirlogo.gif All long as the graphics or related files are checked in with the security group and
document type to match the stated path in this example, a security group Public and a document type Graphic, then the paths will resolve, and the page will display
properly.
10.8 Browser Caching
Kategori