Working With Converted Content 9-5
Figure 9–5 Html Link on Content Information Page
When you click the HTML link, the file is converted and displayed using the rules and templates specified on the Template Selection Rules page see
Template Selection Rules Page
on page A-9.
Subscription and Workflow Notifications You can also open the content information page using the View Info link in the e-mail
messages that you receive when you subscribe to a content item stored in the Content Server.
Figure 9–6 View Info Link in Subscription E-mail Notification Message
This same link is available in workflow notification messages, which eliminates the need for content reviewers to have the native application used to create the source file.
9.3 Previewing a Document Before Check-In
Content contributors can preview the HTML rendition of a document before checking it into the Content Server. This enables them to see if there are problems with the
document or the template associated with the document, and notify the site webmaster or developer. Problems can then be resolved before more users or
customers view the converted content. Both the content authors and the site developers gain from the ability to preview documents this way.
9-6 Administrators Guide for Dynamic Converter
The dynamic contributor preview is displayed as an HTML button on Content Servers content check-in page.
Figure 9–7 Html Preview Button on Content Check-in Screen
Once a document has been selected and all metadata assigned to the document, click the preview button to see how the document will appear as a web page. The resulting
screen displays a Complete Check In link in the left frame and the converted document in the right frame.
Figure 9–8 Dynamic Conversion Preview
If you are satisfied with the HTML rendition of the document, you can click Complete Check In
to check the document into the Content Server at which time you are brought to the check-in confirmation screen. Click the Back button in your web
browser to cancel the process and return to the content check-in screen. If you check in a document using metadata that has no template associated with it, a
blank Classic HTML Conversion template is assigned. This template contains no special formatting instructions, other than to convert your document into a web page.
Tip: As a site administrator, you can also preview how a content
item will appear with a particular template using the Change Preview button in the Template Editor.
10
Implementation Considerations 10-1
10
Implementation Considerations
This section covers some of the more pragmatic concerns when dealing with Dynamic Converter. The following topics are explained:
■
Metadata Fields With Multi-Byte Characters on page 10-1
■
Conversion of PDF Files in UNIX on page 10-2
■
Embedded Graphics on UNIX on page 10-2
■
Use of Vector Versus Raster Graphics Formats on page 10-2
■
Converting Vector Graphics and Spreadsheet Text in UNIX on page 10-3
■
URL Rewriting on page 10-3
■
Relative URLs in Templates and Layout Files on page 10-4
■
Browser Caching on page 10-4
■
Image Sizing Rules on page 10-5
■
CSS Considerations on page 10-5
■
Style Names Used by Dynamic Converter on page 10-5
■
Overriding Dynamic Converter Styles on page 10-6
■
Pragma.CSSFile and { LINK} on page 10-6
■
Well-Formed HTML on page 10-7
■
Positional Frames Support on page 10-7
■
Template Writing Tips on page 10-7
10.1 Metadata Fields With Multi-Byte Characters
For Classic HTML Conversion templates, it is recommended that you do not use multi-byte characters in your content IDs, security groups, content types, and account
names, even if Dynamic Converter is used in a multi-byte environment Japanese, Korean, or other non-Roman alphabets. This content metadata information is
included in the URL of a content item, and limitations in current web technology may prevent web servers and web browsers from handling multi-byte character URLs
correctly. Dynamic Converter, for example, will fail to locate content items if the links are broken.
If you want to use multi-byte characters in content IDs, security groups, content types, or accounts, you need to make sure that the entire Content Server environment servers
and clients runs on operating systems that support multi-byte languages for example, Japanese or Korean versions of Microsoft Windows.
10-2 Administrators Guide for Dynamic Converter
10.2 Conversion of PDF Files in UNIX
