QuarkXPress Server 2019 - Known and Resolved Issues

Resolved Issues: QuarkXPress Server 2019

Note: All the customer fixes done in 14.x are also available in this release.

IMPORTANT MIGRATION INSTRUCTIONS FOR 2019 TABLE STYLES

In the previous version, there were two kinds of table styles (based on their implementation):

(a) Using Modifier <TABLESTYLE> XML markup

(b) Using QXP 2018 Table Styles UI

How to migrate of XML Modifier Table Styles Definitions to the new Table Styles 2019

(a) Create QXPDOC of the given template and modifier using the following request:

http://<servername>:<port>/qxpdoc/template.qxp?modify=file:mod.xml&download=true

OR

Using QuarkXPress 2019 UI, you may flow the modifier to the template and save the resultant QXPDOC.

(b) Open the QXPDOC in QuarkXPress 2019.

(c) Edit Table Style as per modifier and save the document.

(d) Now open the template.

(e) Go to File->Append->Table Styles.

(f) Import the corresponding table style into the template.

(g) Save the final template.

How to migrate QuarkXPress 2018 Table Styles created using QuarkXPress UI

As of now, there is no way to migrate table styles created from QuarkXPress 2018. You must create each table style manually.

CHANGES TO BE MADE IN LEGACY MODIFIER FOR COMPATIBILITY WITH 2019 TABLE STYLES

  1. For all the cases where table border is defined but width is not specified, width must be specified.

  2. For all the cases where border color is defined as none and width is non-zero, color must be specified (white).

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Following is a list of issues resolved in QuarkXPress Server 2018 - December 2019 Update (15.0). Note that this is not an exhaustive list of all fixes in this version. 

  • Resolved: Background shading was not getting applied on footnote body. (8052)

  • Resolved: Cross reference does not work properly. Its fixed now. (51303)

  • Resolved: Enabled authentication for/uploadfile request. (102180)

  • Resolved: Enabled authentication for/downloadaszip request. (102181)

  • Resolved: PARAGRAPH containing INLINETABLE with another nested INLINETABLE in one of the cell were not rendering, causing loss of content. (108269)