Completed
Last Updated: 22 Feb 2017 12:37 by ADMIN
The fix will be available in our LIB release (v. 2016.01.0312).
Completed
Last Updated: 22 Feb 2017 12:37 by ADMIN
The fix will be available in the next official release Q1 2015.
Completed
Last Updated: 22 Feb 2017 12:37 by ADMIN
When image is added with size Size.Empty, it is exported to HTML with the following invalid syntax:
width="-Infinity" height="-Infinity"

Exporting to Docx throws exception. 

Consider exposing an API for suppressing the export of 'width' and 'height' attributes to HTML, for example in the ImageExportingEventArgs.

The fix is available in our latest LIB release (v. 2015.1.0316)
Completed
Last Updated: 22 Feb 2017 12:37 by ADMIN
The value will be skipped when importing the document (<table width=200>). If the size is defined (px or %) as follows <table width=200px> or <table width=200%> then the width value will be respected.

The fix is available in our latest LIB release (v. 2015.1.0316).
Completed
Last Updated: 22 Feb 2017 12:37 by ADMIN
Completed
Last Updated: 22 Feb 2017 12:37 by Stefan
ADMIN
Created by: Petya
Comments: 3
Category: UI for WPF
Type: Bug Report
1

			
Completed
Last Updated: 22 Feb 2017 12:37 by ADMIN
When document contains field element without the optional separator character, the import fails.
Completed
Last Updated: 22 Feb 2017 12:37 by Stefan
The feature is available in our latest LIB release (v. 2014.3.1124)

Do not hesitate to contact us if any issues or questions arise.
Completed
Last Updated: 22 Feb 2017 12:37 by ADMIN
ADMIN
Created by: Petya
Comments: 1
Category: UI for WPF
Type: Bug Report
1

			
Completed
Last Updated: 22 Feb 2017 12:37 by ADMIN
The fix is available in our latest LIB release (v. 2015.1.0316).
Completed
Last Updated: 22 Feb 2017 12:37 by ADMIN
Completed
Last Updated: 22 Feb 2017 12:37 by ADMIN
Completed
Last Updated: 22 Feb 2017 12:37 by ADMIN
Completed
Last Updated: 22 Feb 2017 12:37 by ADMIN
The fix will be available in our next LIB release (v. 2015.03.1005).
Completed
Last Updated: 22 Feb 2017 12:37 by ADMIN
Completed
Last Updated: 22 Feb 2017 12:37 by ADMIN
The documents produced by WordsProcessing and SpreadProcessing are compliant with the specification. But, Open Office, Numbers and Pages (the default applications for working with .docx and .xlsx on MAC) are unable to open documents where the target attribute of the relationships of the documents is specified as an URI, instead of as a relative reference. According to the specification (Ecma Office Open XML Part 2 - Open Packaging Conventions) both formats are acceptable.

The issue is in the relationships parts, relationship element. The Target attribute can be either a URI (Target="/word/theme/theme1.xml") or a relative reference (Target="theme/theme1.xml") as stated in the specification. The document processing libraries use URI, which OpenOffice is unable to interpret, despite them being allowed by the specification.

The fix will be available in our official release Q2 2016.
Completed
Last Updated: 22 Feb 2017 12:37 by ADMIN
The fix is available in our latest LIB release (v. 2015.1.0316)
Declined
Last Updated: 22 Feb 2017 12:37 by ADMIN
According to http://www.digitalpreservation.gov/formats/fdd/fdd000251.shtml#sign there should be two elements in the XMP-metadata to indicate the PDF/A conformance level.

Here is an example:
<rdf:Description rdf:about="" xmlns:pdfaid="http://www.aiim.org/pdfa/ns/id/">
  <pdfaid:part>1</pdfaid:part>
  <pdfaid:conformance>B</pdfaid:conformance>
</rdf:Description>

or attribute version:

<rdf:Description rdf:about="" xmlns:pdfaid="http://www.aiim.org/pdfa/ns/id/" pdfaid:part="1" pdfaid:conformance="B" />

See also http://www.pdfa.org/wp-content/uploads/2011/08/tn0008_predefined_xmp_properties_in_pdfa-1_2008-03-20.pdf

and http://www.aiim.org/documents/standards/PDF-A/ISO19005AppNotes.pdf