PDF Output

PDF output is a standard function of Antenna House Formatter V7.4. The PDF versions that can be output are as follows:

• PDF1.3
  PDF1.3 can be browsed by Adobe Acrobat (Reader) 4.0 or later.
• PDF1.4
  PDF1.4 can be browsed by Adobe Acrobat (Reader) 5.0 or later.
• PDF1.5
  PDF1.5 can be browsed by Adobe Acrobat (Reader) 6.0 or later.
• PDF1.6
  PDF1.6 can be browsed by Adobe Acrobat (Reader) 7.0 or later.
• PDF1.7
  PDF1.7 can be browsed by Adobe Acrobat (Reader) 8.0 or later.
• PDF2.0
  Possible to output PDF2.0 that conforms to ISO 32000-2:2017 with Antenna House Formatter V7.4.
• PDF/X no-LT
  Possible to output PDF/X with Antenna House Formatter V7.4.
• PDF/A no-LT
  Possible to output PDF/A with Antenna House Formatter V7.4.
• PDF/UA no-LT
  Possible to output PDF/UA with Antenna House Formatter V7.4.

Antenna House Formatter V7.4 outputs PDFs with the following features:

• By setting extended properties inside the original document, bookmarks and links can be created. ☞ Bookmark and Link
• Possible to output PDF in multiple separate volume from one FO. no-LT ☞ Multiple Separate Volume
• By setting extended properties inside the original document, the meta information, such as “Title”, “Subject”, “Author”, and “Keyword” information, display action when opening documents or page layout can be set. ☞ Document Information
• When setting the security, 40-bit RC4, 128-bit RC4, 128-bit AES and 256-bit AES can be applied to the encryption. Available encryptions may differ depending on the PDF versions. ☞ PDF Output Settings, PDF Option Setting Dialog
• Possible to output Tagged PDF. no-LT
• Possible to output Linearized PDF no-LT

For more details, see also PDF Output Settings.

PDF/X is defined in ISO 15930 and is a subset of PDF that aims to exchange the data for printing. Basically all the information for printing is included in the PDF file. Antenna House Formatter V7.4 is available for outputting the following version of PDF/X. It’s impossible to output PDF/X with Antenna House Formatter V7.4 Lite.

• PDF/X-1a:2001 (ISO 15930-1:2001)
  It’s a specification based on PDF1.3.
• PDF/X-3:2002 (ISO 15930-3:2002)
  It’s a specification based on PDF1.3.
• PDF/X-1a:2003 (ISO 15930-4:2003)
  It’s a specification based on PDF1.4 and a subset of PDF/X-3:2003.
• PDF/X-2:2003 (ISO 15930-5:2003)
  It’s a specification based on PDF1.4 and a superset of PDF/X-3:2003.
• PDF/X-3:2003 (ISO 15930-6:2003)
  It’s a specification based on PDF1.4.
• PDF/X-4:2010, PDF/X-4p:2010 (ISO 15930-7:2010)
  It’s a specification based on PDF1.6.

The following shows the main features for PDF/X.

In PDF/X, all fonts must be embedded. When the font that is not allowed to embed is used, PDF/X cannot be generated.

PDF/X adopts the appropriate information by ignoring the most of the information set by users, such as font embedding, etc. For example the version of the output PDF is specified to PDF/X, Font Embedding in the PDF Option Setting Dialog will be displayed in gray color.

When an image incompatible as PDF/X is specified, the processing changes depending on error-on-pdfx-fault specified in PDF Output Settings. See also error-on-pdfx-fault.

In PDF/X, the output intent must be specified. There are two ways to specify the output intent. One is to directly specify the ICC profile and the other one is to specify the output condition identifier.

In order to specify the output intent by ICC profile, use the URL of the ICC profile to the src property for <fo:color-profile>. In this case, omit the color-profile-name property or specify "#CMYK", "#GrayScale" or "#RGB". If this property is omitted, it is considered to be "#CMYK". For example:

<fo:declarations>
 <fo:color-profile
  src="url('file:///C:/​WINDOWS/​system32/​spool/​drivers/​color/​JapanColor2001Coated.icc#OutputConditionIdentifier=JC200103')"
  color-profile-name="#CMYK"
 />
</fo:declarations>

In HTML, you can specify as follows by using <meta name="color-profile">: no-LT

<meta
 name="color-profile"
 content="src='file:///C:/​WINDOWS/​system32/​spool/​drivers/​color/​JapanColor2001Coated.icc#OutputConditionIdentifier=JC200103' name='#CMYK'"
/>

In PDF/X, the output intent which can be specified is only one. When multiple output intents are specified, it is indeterminate which one is adopted.

In PDF/X, the only ICC profile of the output intent which can be embedded is the one whose device class is “prtr”. Any ICC profiles other than “prtr” cannot be used. Specifying an ICC profile other than “prtr” will report the following error:

6908 (420C): PDF output warning. Unsupported ICC Profile Device Class : mntr: Xxxxxxxx.icc

With PDF/X-1 to PDF/X-3, the output condition identifier can also be specified with the src property of <fo:color-profile>. The setting is done in the form of the fragmentation of URI. For example:

<fo:declarations>
 <fo:color-profile
  src="#OutputConditionIdentifier=CGATS%20TR%20001&amp;RegistryName=http://www.color.org"
 />
</fo:declarations>

The first character must be “#”. After that, the parameters are lined and separated by &amp;. Each parameter is in the form of name=value. The name of the parameters are as follows (by mapping to the items of the Outputlntent dictionary for PDF/X).

• OutputConditionIdentifier
  Specifies the output condition identifier. When the URL of the ICC profile is specified, the default value is Custom.
• OutputCondition
  Specifies the output condition (possible to omit).
• RegistryName
  Specifies the URI of the registration agency of the output condition identifier. When OutputConditionIdentifier is specified and this is omitted, the default URI is http://www.color.org.
• Info
  Specifies the added information (possible to omit).

It’s also possible to give the information of the profile by describing the format of the fragment parameter following to the ICC profile. The base URI specified by axf:base-uri can also be specified.

<fo:declarations axf:base-uri="url('file:///C:/WINDOWS/system32/spool/drivers/color/')">
 <fo:color-profile src="url('Photoshop5DefaultCMYK.icc#Info=Photoshop5')"/>
</fo:declarations>

When the output intent is specified by the output condition identifier, the output intent is not embedded in PDF/X. When it is specified by the ICC profile, the ICC profile is embedded in PDF/X.

The standard output intent is the standard ICC profile defined below.

You can specify any of these for the output condition identifier. The standard output intents that can be specified with Antenna House Formatter V7.4 are as follows and they are all for CMYK.

The ICC profile specified by the URL is judged whether it is the standard output intent from its contents. When the standard output intent is specified with a URL, with PDF/X-1 to 3, it’s possible to select whether the ICC profile is embedded or not by embed-std-output-intent of the PDF Output Settings, because the embedding of the ICC profile is not required. However, with PDF/X-4, this setting is disregarded and the ICC profile is always embedded. With PDF/X-1 to 3, when specified by the output condition identifier, it’s not embedded regardless of the setting of embed-std-output-intent.

When the output intent is not specified in FO, default-output-intent in the PDF Output Settings will be adopted.

The standard ICC profile can be downloaded from Adobe.

The profile that can be downloaded may be already bundled with Adobe Acrobat and has already been installed on your system. If your OS is Windows, search the %windir%\system32\spool\drivers\color directory.

PDF/A is defined by ISO 19005 and it is the specification intended to be suitable for long-term preservation of electronic documents. Antenna House Formatter V7.4 is available for outputting the following version of PDF/A. It’s impossible to output PDF/A with Antenna House Formatter V7.4 Lite.

• PDF/A-1a:2005
  It is the specification based on PDF1.4 that is fully compliant with ISO 19005-1:2005. It is guaranteed that PDF can be displayed and furthermore the text can be extracted in a logical order.
• PDF/A-1b:2005
  It is the specification based on PDF1.4 that is partially compliant with ISO 19005-1:2005. It is guaranteed that it can be displayed.
• PDF/A-2a:2011 no-LT
  It is the specification based on ISO 32000-1 that is fully compliant with ISO 19005-2:2011. It is guaranteed that it can be displayed and furthermore the text can be extracted in a logical order.
• PDF/A-2b:2011 no-LT
  It is the specification based on ISO 32000-1 that is partially compliant with ISO 19005-2:2011. It is guaranteed that it can be displayed.
• PDF/A-2u:2011 no-LT
  It is the specification based on ISO 32000-1 that is partially compliant with ISO 19005-2:2011. It is guaranteed that it can be displayed, and furthermore the Unicode value of text in PDF can be obtained.
• PDF/A-3a:2012 no-LT
  It is that specification based on ISO 32000-1 that is fully compliant with ISO 19005-3:2012. It is guaranteed that it can be displayed and furthermore the text can be extracted in a logical order.
• PDF/A-3b:2012 no-LT
  It is the specification based on ISO 32000-1 that is partially compliant with ISO 19005-3:2012. It is guaranteed that it can be displayed.
• PDF/A-3u:2012 no-LT
  It is the specification based on ISO 32000-1 that is partially compliant with ISO 19005-3:2012. It is guaranteed that it can be displayed, and furthermore the Unicode value of text in PDF can be obtained.

The following shows the main features for PDF/A:

PDF/A as well as PDF/X require that all fonts are embedded; if a font cannot be embedded due to security restrictions or other issues, a PDF/A or PDF/X will not be generated. Also, the embedding of the ICC profile is required with PDF/A, so when specifying the output intent, only the URL specification of the ICC profile is effective.PDF/A must use a device-independent color space or set an ICC profile in the output intent. Except for rare cases such as outputting blank PDF, the output intent setting is required to output proper PDF/A with Antenna House Formatter V7.4.

Most information (including embedding of fonts etc.) is adopted precisely and user settings are ignored. In PDF/A-1a or PDF/A-2a or PDF/A-3a, the tagging is done compulsorily. See also Tagged PDF.

XMP metadata is automatically generated from the document information of PDF. The original XMP can also be specified by <axf:document-info name="xmp">.

Antenna House Formatter V7.4 can attach files to the PDF as file annotations. In order to attach a file as an annotation, use axf:annotation-file-attachment. Although it is [yes] in the above table, there are the following restrictions when attaching a file to PDF/A. There are no restrictions other than PDF/A.

• Any files cannot be attached to PDF/A-1 as annotations.
• Only PDF/A-1 or PDF/A-2 files can be attached to PDF/A-2 as annotations. At that time, the version of PDF to be attached must be less than or equal to the version of PDF to output.
• Any files including PDF/A can be attached to PDF/A-3 as annotations.

Since fonts cannot be embedded in forms in PDF, PDF/A cannot be generated. However, only in the following cases, PDF/A can be generated even if there is a form.

• Text field without the axf:field-default-text setting.
• Push Button field without the axf:field-button-face setting.
• Radio Button field whose value of axf:field-checked-style is “circle”.

PDF/UA is defined by ISO 14289-1 and is the specification intended for improving the accessibility of PDF based on the ISO 32000-1 specification. Antenna House Formatter V7.4 is available for outputting the following version of PDF/UA. It’s impossible to output PDF/UA with Antenna House Formatter V7.4 Lite.

• PDF/UA-1:2014 (ISO 14289-1:2014)

The following shows the main features of PDF/UA.

• Contents must be tagged in logical reading order.
• Meaningful graphics, annotations and numerical formulas must include alternate text descriptions. See Alternate descriptions are provided.
• Security settings must allow assistive technology access to the content.
• Recommended to include bookmarks.
• Annotations, links and multimedia may be included.
• The language of the document must be specified.
• All fonts must be embedded.

Usual PDF does not have the document structure in the contents. For example, the sentences are cut off per each line. In the column, the first line of the right column follows the first line of the left column. Therefore, even if a person with sight problems, etc. is going to read PDF using some kind of reader, it is very difficult to read a text in the right order. The same thing is applied to the text extraction from PDF. Tagged PDF is effective with PDF1.4 or later.

Tagged PDF adds structure to PDF documents by embedding tags into the PDF. The structure added to the document makes the information in the PDF more reusable. For this reason, Tagged PDF is required to create accessible PDF documents. See also the following to know more about Tagged PDF specifications.

• ISO 32000-1:2008 14.8 Tagged PDF
• ISO 32000-2:2017 14.8 Tagged PDF

Tagged PDF is an important element of PDF accessibility. For accessible PDF, there are some requirements in addition to Tagged PDF, as a whole, it is defined in PDF/UA.

Antenna House Formatter V7.4 embeds the following tags (StructElem) for each FO element. Note that FO elements assigned to regions other than region-body are tagged as Artifact.

Antenna House Formatter V7.4 embeds the following tags (StructElem) for each HTML element.

Antenna House Formatter V7.4 may automatically embed tags (structural elements) as follows:

There are some tags that are not structural elements.

In order to create Tagged PDF, you can check Tagged PDF in the PDF Option Setting Dialog, or you can specify -tpdf with the Command-line Interface.

Using the axf:pdftag extension property, you can specify an arbitrary tag name to PDF.

In complex scripts such as Arabic and Devanagari, the original character string is complexly converted to glyphs and output to PDF. The glyph does not have a one-to-one correspondence with Unicode of the original character string, so you cannot copy the correct original character string from the PDF. If you make Tagged PDF, you can copy the original character string.

In Antenna House Formatter V7.4, Role Map can be specified. Role Map is a feature to set the alias of the tag element name. In Antenna House Formatter V7.4, tag-role-map in the Option Setting File enables highly readable tagging while conforming to standard tags.

You can set the expansion text of abbreviations by applying axf:expansion-text to abbreviations like “Dr.”.

<fo:inline axf:expansion-text="Doctor">Dr.</fo:inline> Antenna

Antenna House Formatter V7.4 processes as follows for each check item (in the case of Acrobat 7.0) of the Adobe Acrobat’s Accessibility Full Check.

• Alternate descriptions are provided

  Alternate text can be specified with the extension property, axf:alttext.

  <fo:external-graphic src="..." axf:alttext="AltText"/>
  

  If axf:alttext is not specified or is empty, the content of text is treated as an alternate text. However, for empty elements such as <fo:external-graphic>, the content of text is empty. If the content of text is empty and HTML, the value of the title property is treated as an alternate text. If the value of the title property is also empty or not HTML, the value of the role property is treated as an alternate text. However, this is not recommended as it is not the original usage of the role property. If the value of the role property is also empty, the value of fallback-alttext is used. Antenna House Formatter V7.4 sets a single space character (U+0020) to the default value of fallback-alttext. This prevents an accessibility checker from generating an error when an alternate text is not provided on, even if the image does not require an alternate text. It is the FO/HTML creator’s responsibility to provide meaningful alternate text.

  In order to check whether an alternate text is given to the image, you can choose View in the Navigation Tabs, then click Tags to open the Tags tab with Acrobat, then see the alternate text item by opening the property of the <Figure> structure element.

  The alternate text of the link can be specified with the extension property axf:annotation-contents. If axf:annotation-contents is not specified or is empty, axf:alttext will be used as an alternate text. When axf:alttext is not specified or is empty, it is processed in the same way as the alternate text of the image.

• Text language is specified

  If any of the properties for specifying the language (language, country, xml:lang) are provided in the FO, they will be used to set the language of the corresponding structure elements in Tagged PDF. For example, if you display the tags of the following Tagged PDF with Acrobat,

  <fo:block language="ja">日本語です</fo:block>

  and view the properties of the <P> structure element in this paragraph, you will see the language as Japanese.

• Reliable character encoding is provided

  The text is outputted in Unicode, there is no problem.

• All content is contained in the document structure

  See the tags in the above table.

• All form fields have descriptions

  If the axf:field-description extension property is specified, the text will be assigned, if not, the form name is assigned.

• List and table structure is correct

  <fo:list-block> is for the list structure of Tagged PDF and <fo:table> is for the table structure.

• The tag order matches to the order of the logical structure

  Antenna House Formatter V7.4 outputs tags in the right order.

See also PDF Embedding to know more about embedding Tagged PDF in Tagged PDF or the restrictions by the PDF versions.

It’s impossible to output Tagged PDF with Antenna House Formatter V7.4 Lite.

A linearized PDF file makes viewing of the generated PDF on the web faster. Features of linearized PDF include the following:

• When opening a PDF, the first page can be opened as fast as possible.
• When a user requests another page from an opened page, the page can be opened as fast as possible.
• When distributing a document using a slow communication line, make it possible to display pages gradually one by one.
• When tracing a link, it is not necessary to receive and display all the pages.

PDF that is optimized for fast web view indicates this linearized PDF.

XMP (Extensible Metadata Platform) is an XML specification that represents metadata, and is defined in ISO 16684. PDF1.4 or later contains XMP. XMP is generated from the information specified in <axf:document-info>. Any XMP can be specified with <axf:document-info xmp>, but its contents are adjusted so that there is no conflict. The following contents are adjusted:

• For PDF/X, PDF/A, and PDF/UA, meta information corresponding to each is added. The conflicting information in the specified XMP is deleted.
• For <pdf:Producer> and <xmp:CreatorTool>, those of Antenna House Formatter V7.4 are set.
• For <xmp:CreateDate>, <xmp:ModifyDate> and <xmp:MetadataDate>, PDF generation date and time are set.
• For <dc:format>, application/pdf is set.
• If <axf:document-info document-title> is specified, it is set to <dc:title>. If <dc:title> is not included in the specified XMP and also <axf:document-info document-title> is not specified, an appropriate title is set in PDF/X.
• If <axf:document-info subject> is specified, it is set to <dc:description>.
• If <axf:document-info author> is specified, it is set to <dc:creator>.
• If <axf:document-info author-title> is specified, it is set to <photoshop:AuthorsPosition>.
• If <axf:document-info description-writer> is specified, it is set to <photoshop:CaptionWriter>.
• If <axf:document-info keywords> is specified, it is set to <pdf:Keywords>.
• If <axf:document-info copyright-notice> is specified, it is set to <dc:rights>.
• If <axf:document-info copyright-info-url> is specified, it is set to <xmpRights:WebStatement>.
• If <axf:document-info copyright-status> is specified to something other than Unknown, it is set to <xmpRights:Marked>.
• In PDF/X, when <xmpMM:DocumentID> is not included in the specified XMP, an appropriate UUID is added.
• In PDF/X, when <xmpMM:VersionID> is not included in the specified XMP, it is added as 1.
• In PDF/X, when <xmpMM:RenditionClass> is not included in the specified XMP, it is added as “default”.
• For other than PDF/A, add the custom property.

Namespaces that appear here are:

• xmp : http://ns.adobe.com/xap/1.0/
• xmpMM : http://ns.adobe.com/xap/1.0/mm/
• dc : http://purl.org/dc/elements/1.1/
• pdf : http://ns.adobe.com/pdf/1.3/
• photoshop : http://ns.adobe.com/photoshop/1.0/

No other adjustments other than above are made. Even if an element of an unknown namespace is included in the specified XMP, it will not be deleted. If such elements are included in PDF/A, etc., compliance violations may occur.

Possible to embed PDF document in the other PDF. Fillable PDF forms can also be embedded.

It is performed by using <fo:external-graphic> like handling an image. See Graphics.

<fo:external-graphic src="embedded.pdf#page=3"/>

As described above, specify the page number which you want to embed to the URI. Specify the page in the form of #page=​<FirstPage>-​<LastPage>. When there is no page number specified, the first page will be embedded.

When there is no size specified, it’s embedded in the page size of the PDF where it’s embedded. However if you want to scale the size, content-width or content-height can be specified as follows:

<fo:external-graphic src="embedded.pdf#page=3" content-width="50%"/>

Possible to embed multiple pages continuously.

<fo:external-graphic src="embedded.pdf#page=3-5"/>

As described above, embed from the 3rd page to 5th page continuously. If you want to embed all pages, specify as follows:

<fo:external-graphic src="embedded.pdf#page=1-"/>

When specifying PDF by utilizing the data scheme (RFC2397), the page number can be specified as the parameter of the media type as follows:

<fo:external-graphic src="data:application/pdf;page=3;base64,JVBERi0xLjQKJeLjz9M..."/>

Moreover, it’s also possible to embed PDF as a background. This can be used when making a list form as a background and formatting only the content data on it. When specifying PDF as a background, specify axf:background-repeat="no-repeat" to <fo:simple-page-master> or <fo:page-sequence> as follows:

<fo:simple-page-master axf:background-image="background.pdf"
                       axf:background-repeat="no-repeat" ...

axf:background-repeat="repeat" cannot be specified. In CSS, specify the background to @page.

When embedding PDF against the background, it’s possible to embed not only one page but also two or more pages continuously. Specify axf:background-repeat="paginate" as follows:

<fo:simple-page-master axf:background-image="background.pdf#page=3-5"
                       axf:background-repeat="paginate" ...

In this example, pages from the 3rd to the 5th are embedded as the background. When the number of pages generated from the contents of <fo:flow> is less than the number of the embedded PDF pages, pages are added so that all pages of the embedded PDF may be outputted. Therefore, if the contents of <fo:flow> is empty, there would be no problem. When there is more number of pages generated from the contents of <fo:flow>, the background image of the page beyond the number of the embedded PDF pages will drop off. Specify the page in the form of #page=​<FirstPage>-​<LastPage>. When axf:background-repeat="paginate" is not specified, the -<LastPage> portion is disregarded.

When axf:background-image or axf:background-repeat are specified to both <fo:page-sequence> and <fo:simple-page-master>, <fo:simple-page-master> takes priority. It’s possible to embed PDF to <fo:region-*> by specifying to <fo:simple-page-master>.

axf:background-repeat="paginate" is not available to specify with Antenna House Formatter V7.4 Lite.

The version of the embedded PDF must be less than or equal to the version of PDF to output. The following table shows the acceptable combination with PDF/X, etc. Combinations not in the table are not acceptable.

• [yes] means that the embedding is possible.

Even if it is [yes] in the above table when embedding PDF, there are the following restrictions:

• An error will occur if the PDF version to be embedded is larger than the PDF version to be output.
• When there is no compatibility in OutputIntent, an error will occur when embedding PDF/A into PDF/A.
• Bookmarks contained in the embedded PDF are disregarded.
• The type of annotations to be embedded, contained in the embedded PDF can be specified by import-annotation-types in PDF Output Settings. You can also specify it in Others page in the PDF Option Setting Dialog in GUI. Unspecified annotations are disregarded.

  CAUTION:	If you embed a page with an annotation multiple times at different positions, the position of the annotation will not be guaranteed.

• ID in the embedded PDF specified by internal-destination etc., are deleted.
• When FitH, FitV, etc. are specified by axf:destination-type as an internal link of the embedded PDF, the display is scaled to the paper width of the import destination.
• Images in the embedded PDF are not eligible for the image processing (Compression or Color Conversion)
• In order to embed Tagged PDF in Tagged PDF, specify import-tagged-pdf="true" in PDF Output Settings. You can also specify it in the Version page in the PDF Option Setting Dialog in GUI. PDF without tags is always embeddable.

  CAUTION:	When Tagged PDF is embedded in Tagged PDF, the validity of the tag in the embedded PDF is not guaranteed.

• Even if OutputIntent is specified for the PDF page to be embedded, it is ignored.
• If map location information is attached to the embedded PDF image, Antenna House Formatter V7.4 places the image in Form XObject, so map location information may not be displayed depending on the PDF viewer.
• If a file is attached to the embedded PDF using a feataure other than the file annotation, the validity of the PDF output result is not guaranteed.

[Note]: Embedding of PDF1.X in PDF2.0 is deprecated. If you want to embed it, specify allow-embedding-lower-versions="true".

Type 1 fonts (including Adobe Standard 14 Fonts), TrueType fonts (including OpenType fonts with TrueType Outlines), OpenType fonts (PostScript Outline), WOFF (Web Open Font Format), WOFF2 and Macintosh TrueType font data fork suitcase are supported for PDF output. Other font formats are not supported. For more details, see the “Fonts”.

Antenna House Formatter V7.4 requires that the fonts, which are specified in documents, are installed on your system in order to use them correctly. See Windows help or follow the installation instructions attached to the fonts for the method of installing the font in Windows versions. The font placed outside the font folder can be outputted to PDF in Windows versions. At this time, you need to specify some setting in the Font Configuration File.

Character Sets, Encoding

Font Embedding

For more information about supported graphic images, see the “Graphics”.

Vector Images

Raster Images

The multimedia data, such as video, audio, etc. can be embedded or linked in PDF. The following shows the example using <fo:external-graphic>.

<fo:external-graphic src="video.mpg" content-type="video/mpeg"
                     axf:multimedia-treatment="embed"
                     axf:poster-image="poster.jpg"
                     axf:show-controls="true"
                     width="640pt" height="400pt"/>

In HTML, <object> or <video> can be used.

<object data="video.mpg" type="video/mpeg"
        width="640" height="400"
        style="-ah-poster-image:url('poster.jpg'); -ah-show-controls:true">
</object>

or

<video src="video.mpg" type="video/mpeg"
       width="640" height="400"
       poster="poster.jpg" controls="controls">
</video>

The setting of content-type (or type attribute in HTML) is required. Antenna House Formatter V7.4 consideres that the data specified as src follows the content-type. The contents of data are not checked. A poster image can be specified by axf:poster-image (or poster attribute in HTML <video>). A poster image can be displayed in the GUI. When width and height are not set, the size of the reference area is considered. Whether to embed or link multimedia can be specified with axf:multimedia-treatment.

When axf:show-controls (or controls attribute in HTML <video>) is specified, a control bar is shown under the playing multimedia object. To prevent overlapping the control bar with another object, it is necessary to make enough space below the multimedia object.

The following shows the content types accepted as multimedia by default:

• audio/*
• video/*
• application/x-shockwave-flash

The additional content types other than these can be added by <multimedia> in the Option Setting File. The following example shows a combination of typical extensions and content types.

Whether these can be replayed correctly depends on the PDF viewer. When the shortage of players or shortage of codecs error occurs when replaying, it may be available to run again by introducing a corresponding player and codec.

Restrictions

• Effective with PDF1.5 or later. PDF/X, PDF/A are excluded.
• Cannot specify to background-image.
• Cannot specify to axf:poster-image.
• This feature is not effective with Antenna House Formatter V7.4 Lite.

The multimedia can be embedded as a rich media annotation (here we call such multimedia simply as the rich media). It does not require external players etc. for playback. Specify that it is rich media by axf:multimedia-treatment in <fo:external-graphic> as follows: In HTML, specify it by <object> or <video>. Also, there are differences in valid properties. For more details, see Images, Multimedia.

<fo:external-graphic src="video.mpg" content-type="video/mpeg"
                     axf:multimedia-treatment="richmedia"
                     axf:poster-image="poster.jpg"
                     width="640pt" height="400pt"/>

The following multimedia can be embedded as the rich media.

Even though the container format is supported the video and audio codecs need to be compatible with Adobe Acrobat’s flash player in order to play correctly.

Restrictions

• Effective with PDF1.7 or later. PDF/X, PDF/A are excluded.
• Cannot specify to background-image.
• Cannot specify to axf:poster-image.
• This feature is not effective with Antenna House Formatter V7.4 Lite.

• In Antenna House Formatter V7.4, when the language is specified in the root element of <fo:root> or <html>, it is outputted as a language information on PDF. When the language is not specified, if default-lang is specified to the Option Setting File, it is outputted as a language information on PDF.

• With Antenna House Formatter V7.4, High Compression Settings can be set to reduce the size of the output PDF file. The High Compression Settings can be set in Compression in PDF Option Setting Dialog in GUI. Note that the image quality will also be lowered according to the reduced PDF size. Setting values to be applied can be specified in color-compression-minimum, grayscale-compression-minimum and monochrome-compression-minimum, etc. in the Option Setting File. no-LT

  In the High Compression Settings, default values are set as below:

  <pdf-settings
      color-compression="auto2k"
      color-jpeg-quality="40"
      color-downsampling="bicubic"
      color-downsampling-target-dpi="150"
      color-downsampling-above-dpi="225"
      grayscale-compression="auto2k"
      grayscale-jpeg-quality="40"
      grayscale-downsampling="bicubic"
      grayscale-downsampling-target-dpi="150"
      grayscale-downsampling-above-dpi="225"
      monochrome-compression="zlib"
      monochrome-downsampling="bicubic"
      monochrome-downsampling-target-dpi="300"
      monochrome-downsampling-above-dpi="450"
      pass-through="none"/>
  

  Compression results may vary depending on the factor such as a type, format, color space and compression ratio of the original image. The size may also be smaller if pass-through="all" is specified.