NI Bill PDFs - known formatting differences and other issues

Sub-paragraphs (or heads/paragraphs for NI Orders in Council) not indented correctly within quoted structure

This is a known limitation with ‘Import from Word’ which mistakes some of the roman numerals used in sub-paragraphs as latin numbers which are used for paragraphs. Examples include (i), (v), (x)

Check your document for quoted structures which start with a sub-paragraph (or heads/paragraphs in NI Orders in Council). Check that the correct provision has been inserted for it by putting your cursor in the provision in the Editor and checking the breadcrumb. If it says “paragraph” instead of “sub-paragraph” you will need to manually fix this

Large gap between first paragraph and text in NI Orders in Council (found within quoted structures)

This is due to the limitations of the PDF renderer that we use. We add extra padding between the num and text to allow for the occasions when there is a long article number.

Nothing.

Indent of orphan paragraph in a quoted structure is not correct (usually only noticeable when there are other quoted structures with the correct indent on the same page like this example)

This is a bug

Fixed in v20 (28th July onwards)

Some paragraph text isn’t justified

This is a bug

Fixed in v20 (28th July onwards)

Schedule paragraph num is bold in quoted structures when it is the parent of a schedule sub-paragraph

This is a bug

Fixed in v20 (28th July onwards)

Schedule heading, part heading or chapter heading is in ALLCAPS

This is a limitation of ‘Import from Word’ where it imports all the heading text in all caps.

You will need to manually retype the headings in normal text

Little box appears before an em-dash in the PDF that isn’t visible in the Editor

These creep in when you copy and paste directly from the LWB Word document. They are hidden formatting marks that Lawmaker doesn’t display in the Editor, but they are picked up by the PDF and tend to stop line numbering from working

You need to delete the last character before the em-dash and the em-dash and manually type back in the text.

SCHEDULES header missing from the Table of Contents

This is a known issue

Fixed in v20 (28th July onwards)

Line numbering stops halfway through my PDF

There is something around the last line number that the PDF generator does not like. We’ve seen it before in the following occasions:

1. Hidden formatting markers when text is copied from a LWB document into Lawmaker and identified as squares in the text of the PDF (but not visible in the Editor). If this is the cause, you need to delete the last character before the em-dash and the em-dash and retype them which strips out the hidden formatting marker

2. Using white space character in an empty paragraph element created using Shift + Enter. This was an experiment in the Budget Bill to recreate the unnumbered paragraphs in the schedules whilst mimicking the desired spacing between paragraphs. It didn’t work due to the line numbering issue so we switched to using schedule paragraphs with empty nums.

Back cover doesn’t show minister name, bill number, introduction date

Once you’ve updated the document information, you need to re-insert the back cover. It doesn’t auto-update in the same way that the front cover will.

Where is my ISBN?

It wasn’t included in the PDF configuration.  This was because in the early days of the project when we were working on the Bill PDF, it was agreed the ISBN was no longer needed. However, we might have been a little premature on that decision as it’s likely to be required in the short term until official agreement has been reached. Instead you need to add it manually using the PDF editor. 

EFM text on back cover is missing a full stop at the end

Fixed in v20 (28th July onwards)

Shouldn’t be a comma after the minister role in the section 63 statement

Fixed in v20 (28th July onwards)

Error “Fragment has been deleted by another user. Click on “OK” to refresh the document.”

Fixed in v20 (28th July onwards)

Document locking issue when inserting a Table of Contents. This was only experienced by one user and later identified to be down to the cursor being placed in the Table of Contents when ‘Insert Table of Contents’ was run.

Fixed in v20 (28th July onwards)

“expecting an array object” issue when using Adobe compare feature for an LWB PDF and a Lawmaker PDF.

Make sure your document versions do not include front cover, table of contents or back covers when comparing them in Adobe.