The following support article gives advice on how to re-structure tabulated content when importing specifications from NBS Building or Landscape into NBS Chorus. The article refers mainly to NBS Building, but the same principles apply to specifications originally authored in NBS Landscape.
Known issue
The NBS Chorus specification editor window does not currently support content formatted in tables. As a result, any specification content imported that had originally been authored in NBS Building may need a small number of clauses re-structured once imported into the Chorus environment.
Figure 1 below gives an example of a clause with tabulated content in NBS Building.
Figure 1 – Clause K10/620 in NBS Building
Figures 2 and 3 below show how this clause is represented in the NBS Chorus editor window and also in the published PDF. It can be seen that the tabulated content is no longer aligned and as a result is more difficult to read.
Figure 2 – Clause K10/620 from NBS Building, imported into NBS Chorus
Figure 3 – Clause K10/620 from NBS Building, imported into NBS Chorus when published to PDF
Suggested solution
The suggested solution is to re-structure this imported clause so that the data is structured using a combination of nested rows, colons and commas. An example of this is shown below in Figure 4.
Figure 4 – Clause K10/620 now re-structured in NBS Chorus
A list of clauses in NBS Building or Landscape that may require re-structuring in NBS Chorus is provided below.
|
|
|
|
|
It is always advised to carefully check the content of any specification before publishing and issuing.