标准信息
STANDARD INFORMATION- 标准编号
- Clause-G13-Foul-Water
- 所属分类
- 其他国外标准与工程资料
- 文件语言
- 英语
- 文件格式
- 文件页数
- 6 页
- 文件大小
- 1.93 MB
· 更新:
标准简介
OVERVIEW中文简介
标准 Clause-G13-Foul-Water 的预览内容
English summary
Preview of standard Clause-G13-Foul-Water
以上为根据文件整理的内容简介。
标准内容预览
DOCUMENT PREVIEW我们需要回答用户:作为OCR引擎,把工程标准PDF页面精确转成HTML片段,只返回HTML,不要解释。需要遵守严格标签/class限制。现在分析页面内容。
页面顶部有黑条,忽略页眉页脚?顶部黑条可能是页眉/页脚,忽略。正文:
Status of Compliance Documents (bold heading)
Compliance Documents are prepared by the Department of Building and Housing in accordance with section 22 of the Building Act 2004. A Compliance Document is for use in establishing compliance with the New Zealand Building Code.
A person who complies with a Compliance Document will be treated as having complied with the provisions of the Building Code to which the Compliance Document relates. However, a Compliance Document is only one method of complying with the Building Code. There may be alternative ways to comply.
Users should make themselves familiar with the preface to the New Zealand Building Code Handbook, which describes the status of Compliance Documents and explains alternative methods of achieving compliance.
Defined words (italicised in the text) and classified uses are explained in Clauses A1 of the Building Code and in the Definitions at the start of this Compliance Document.
Then table: G13: Document History header row? It's a table with title row G13: Document History spanning? Then header row Date Alterations. But first column has no header? Table structure:
Row1: G13: Document History (probably th colspan=3? But allowed th with colspan. Could use caption? The table title is G13: Document History. Could use
First published | July 1992 | (blank)
Amendment 1 | September 1993 | pp. vii–viii, References p. xi, Definitions | p. 25, Figure 3 p. 31, Figure 7
Wait table visually has 4 columns? Let's inspect:
Header: blank, Date, Alterations. But Alterations spans two subcolumns? In rows, Alterations content split into two columns: e.g. Amendment 1: Date September 1993, then Alterations cell has two columns: "pp. vii–viii, References p. xi, Definitions" and "p. 25, Figure 3 p. 31, Figure 7". Header "Alterations" likely colspan=2. So table has 4 columns: first item, Date, Alterations (colspan 2). But header row:
Rows:
First published | July 1992 | (empty) maybe
Amendment 1 | September 1993 | pp. vii–viii, References p. xi, Definitions | p. 25, Figure 3 p. 31, Figure 7
Reprinted incorporating Amendment 1 | October 1994 | (empty) maybe colspan=2
Amendment 2 | 1 December 1995 | p. viii, References | colspan=2?
Amendment 3 | 28 February 1998 | p. ii, Document History p. viii, References | p. 1, 1.0.1 p. 21, 1.0.1
Second edition published 1 July 2001 | Effective from 1 October 2001 | Document revised – second edition issued | colspan=2?
Amendment 1 | Published March 2007 Effective from 23 June 2007 | p. 2, Document History, Status p. 6, Contents pp. 7–8, References | pp. 9–10, Definitions p. 52A, AS3 1.0, 1.0.1, 1.0.2 p. 55, Index
Erratum 1 | Effective from 23 June 2007 | pp. 5-6, Contents pp. 33-34, AS1 8.0, 8.1 pp. 50-51, AS2 7.0, 7.1 | colspan=2?
Amendment 2 | Effective from 21 June 2007 | p. 2, Document History, Status pp. 3, 4, 4A, Building Code Clause p. 6, Contents | p. 8, References p. 52A, VM4 p. 54, Index
Note: Page numbers relate to the document at the time of Amendment and may not match page numbers in current document. This is in table bottom row spanning all columns? Could be tfoot? Allowed tfoot. Use
Need consider table header row with blank first column. Could use
Then Document Status heading bold. Paragraphs:
The most recent version of this document, as detailed in the Document History, is approved by the Chief Executive of the Department of Building and Housing. It is effective from 21 June 2007 and supersedes all previous versions of this document.
People using this Compliance Document should check for amendments on a regular basis. The Department of Building and Housing may amend any part of any Compliance Document at any time. Up-to-date versions of Compliance Documents are available from www.dbh.govt.nz
Need output page number? Rule 9: 每页输出必须以
开头(页面内标题),页码用
2
结尾. But page has no visible page number? It says page number by 2 placeholder. Need end with2
. Start with h2. The first heading is "Status of Compliance Documents". UseStatus of Compliance Documents
. Then paragraphs.Need only allowed tags. No style. No nbsp. No continuous spaces. Need line breaks? Paragraphs separate. For table cells with multiple lines, can use
? Allowed br. But rule says don't use br to create paragraph spacing; within cell line breaks okay? It says 禁止? It says 不要用
制造段落间距. In table cells, original has line breaks. Could use
within td to preserve. Allowed tag br. But maybe avoid if not necessary? Need preserve line breaks? OCR exact. Use
inside td for multiple lines. That's okay. But ensure no extra spaces. For em dash? Use – as original. Need avoid continuous spaces. Use single spaces.
Need table class? No class needed. layout-columns not needed. small-note for note? The note is inside table bottom, could be
inside td? Allowed p. But table cell can contain p. But maybe simpler
Note: ...
inside td. Allowed. But if p inside td, okay. Need no style.Need heading for Document Status:
Document Status
maybe because second section. Rule page内标题: first page h2, subsequent h2 or h3 based hierarchy. Use h3.Need italicised? "Defined words (italicised in the text)" no actual italic. Could use em? Not necessary. But if original italic? It says italicised in text, not actual. No.
Need table header: The gray row "G13: Document History" maybe not caption but table header row. Could use Need table columns count. If caption, thead: G13: Document History . But caption also? If use caption, duplicate? The title is part of table. Could use caption and thead. But caption may be outside. The gray row is likely table title. Use caption to preserve. Then thead with Date Alterations. But if caption, no gray row. Acceptable. Need preserve "G13: Document History". Could also use Date Alterations ... But then table has two header rows. Allowed. Which better? The instruction: 表格:标题用 caption. So use caption. Then thead for column headers. Good.
G13: Document History . Data rows with 4 cells or colspan. Need ensure each row total columns = 4. Let's design:
Date Alterations
p. xi, Definitions
p. 31, Figure 7
p. viii, References
p. 21, 1.0.1
Effective from 23 June 2007
p. 6, Contents
pp. 7–8, References
p. 52A, AS3 1.0, 1.0.1, 1.0.2
p. 55, Index
pp. 33-34, AS1 8.0, 8.1
pp. 50-51, AS2 7.0, 7.1
pp. 3, 4, 4A, Building Code Clause
p. 6, Contents
p. 52A, VM4
p. 54, Index
Note: Page numbers relate to the document at the time of Amendment and may not match page numbers in current document.
Need check hyphen vs en dash: original uses pp. vii–viii (en dash), pp. 7–8, pp. 9–10, but pp. 5-6, 33-34, 50-51 maybe hyphen. Preserve. Use – for en dash where visible. For "Document revised – second edition issued" en dash. Good.
Need no Markdown. Only HTML.
Potential issue: "每页输出必须以
开头(页面内标题)" If first heading is bold not necessarily h2? Use h2. Good.
Potential issue: page number placeholder: They say 页码用
2
结尾. So final line exactly. Good.Potential issue: allowed class only single value. We use small-note. Good.
Potential issue: table caption allowed. Good.
Potential issue: empty td/th? Allowed. But empty th maybe okay. Could avoid empty th by using
Potential issue: "禁止所有 style 属性" none.
Potential issue: "禁止 、 、制表符、连续两个以上空格" ensure no double spaces. In HTML source, indentation/newlines okay? They didn't forbid whitespace outside tags? They say no continuous two spaces. We can output compact with newlines. Newlines okay. Avoid multiple spaces in text. In table cells, use
no spaces. Good.
Potential issue: "pre 内只能包含 code" not using pre.
Potential issue: "只允许 td/th 带 rowspan/colspan" we use colspan on th and td. Good. Values 1-100.
Potential issue: "禁止 ol/ul/li 带任何属性" not using.
Potential issue: "参考文献 → 保留,用
- 或
" not relevant.
Need maybe include "Status of Compliance Documents" as h2. Then paragraphs.
Need maybe "Document Status" as h2? It is a boxed section. Could be h3. Good.
Need maybe table title "G13: Document History" as caption. Good.
Need maybe "G13:" bold? Not necessary. Could use ? The heading is bold. But table caption can be plain. The instruction says preserve content, not necessarily bold. But allowed strong. Could use Need maybe "Date" and "Alterations" bold in header, th default. Good. Need maybe first column header blank but maybe should be "Document History"? The gray row is title. The first column has entries like First published, Amendment 1. No header. Use empty th. Could use Need ensure table total columns consistent: caption doesn't count. thead row 1: th empty (1), th Date (1), th colspan=2 (2) total 4. Data rows: - First published: td, td, td colspan=2 total 4. - Amendment 1: 4 cells total 4. - Reprinted: 3 cells with colspan=2 total 4. - Amendment 2: 3 cells with colspan=2 total 4. - Amendment 3: 4 cells. - Second edition: 3 cells with colspan=2 total 4. - Amendment 1: 4 cells. - Erratum 1: 3 cells with colspan=2 total 4. - Amendment 2: 4 cells. tfoot: td colspan=4 total 4. Good. Need maybe line breaks in cells: Use Need maybe "pp. vii–viii, References" and "p. xi, Definitions" in same cell separated by Need maybe "p. 25, Figure 3" and "p. 31, Figure 7". Good. Need maybe "Published March 2007" and "Effective from 23 June 2007" in date cell. Good. Need maybe "Second edition published 1 July 2001" line break? Original cell has three lines: Second edition / published / 1 July 2001. Could preserve as "Second edition published 1 July 2001" or with G13: Document History and no caption. But instruction says title use caption. Use caption.Date Alterations
without spaces. Good.
. Good.
. To be exact, maybe Second edition . But line breaks due to column width, not semantic. OCR exact? Could preserve line breaks. But not necessary? They want precise. Use
published
1 July 2001
for visible line breaks? For table cells, yes. But too many br? It's okay. For first column "Reprinted incorporating Amendment 1" visible three lines: Reprinted / incorporating / Amendment 1. Could use
. But if we use spaces, it's okay. Need avoid continuous spaces. I can preserve line breaks with
for multi-line cells. But might be overkill. The instruction says don't use br to create paragraph spacing, but within table cells line breaks are content. Use br where original has line breaks. Need decide.
For paragraphs, no br. For table cells, use br to reflect line breaks. But if line breaks are just wrapping, not necessary. However OCR exact might prefer. But too many br could be okay. Need ensure no double spaces.
Let's transcribe table cells with line breaks as seen:
Row First published: first cell "First published" one line. Date "July 1992". Alterations empty.
Row Amendment 1: first "Amendment 1". Date "September 1993". Alterations left: "pp. vii–viii, References" line break "p. xi, Definitions". Right: "p. 25, Figure 3" line break "p. 31, Figure 7".
Row Reprinted: first "Reprinted" line break "incorporating" line break "Amendment 1". Date "October 1994". Alterations empty.
Row Amendment 2: first "Amendment 2". Date "1 December 1995". Alterations "p. viii, References" maybe one line spanning.
Row Amendment 3: first "Amendment 3". Date "28 February 1998". Alterations left: "p. ii, Document History" line break "p. viii, References". Right: "p. 1, 1.0.1" line break "p. 21, 1.0.1".
Row Second edition: first "Second edition" line break "published" line break "1 July 2001". Date "Effective from" line break "1 October 2001". Alterations "Document revised –" line break "second edition issued".
Row Amendment 1: first "Amendment 1". Date "Published March 2007" line break "Effective from 23 June 2007". Alterations left: "p. 2, Document History, Status" line break "p. 6, Contents" line break "pp. 7–8, References". Right: "pp. 9–10, Definitions" line break "p. 52A, AS3 1.0, 1.0.1, 1.0.2" line break "p. 55, Index".
Row Erratum 1: first "Erratum 1". Date "Effective from 23 June 2007". Alterations: "pp. 5-6, Contents" line break "pp. 33-34, AS1 8.0, 8.1" line break "pp. 50-51, AS2 7.0, 7.1".
Row Amendment 2: first "Amendment 2". Date "Effective from 21 June 2007". Alterations left: "p. 2, Document History, Status" line break "pp. 3, 4, 4A, Building Code Clause" line break "p. 6, Contents". Right: "p. 8, References" line break "p. 52A, VM4" line break "p. 54, Index".
Need maybe "Building Code Clause" line break? Original: "pp. 3, 4, 4A, Building Code Clause" then "p. 6, Contents". Good.
Need maybe "AS3 1.0, 1.0.1, 1.0.2" line break? It appears one line. Good.
Need maybe "pp. 5-6" hyphen. Good.
Need maybe "pp. 33-34" hyphen. Good.
Need maybe "pp. 50-51" hyphen. Good.
Need maybe "Document revised – second edition issued" line break after dash? Original: "Document revised –" line break "second edition issued". Use br.
Need maybe "Effective from" line break in date for second edition. Use br.
Need maybe "Reprinted incorporating Amendment 1" line breaks. Use br.
Need maybe "Second edition published 1 July 2001" line breaks. Use br.
Potential issue: using
inside table cells may be considered okay. Allowed tag. Good.
Need maybe table caption:
Need maybe "Status of Compliance Documents" heading:
Status of Compliance Documents
. Good.Need maybe "Document Status" heading:
Document Status
. Good.Need maybe paragraph "Defined words (italicised in the text) and classified uses are explained in Clauses A1 of the Building Code and in the Definitions at the start of this Compliance Document." Good.
Need maybe "Clauses A1" maybe "Clause A1"? Original says Clauses A1. Preserve.
Need maybe "www.dbh.govt.nz" no link. Good.
Need final page number:
2
. Good.Need ensure no HTML comments. Good.
Let's craft final HTML. Need no extra spaces? We can indent with newlines. The text inside tags should not have double spaces. Indentation outside tags okay? They didn't forbid. But to be safe, minimal indentation. Newlines okay. Avoid multiple spaces in text. In HTML source, line breaks between tags okay.
Potential issue: "连续两个以上空格" includes source? If we indent with two spaces, that's continuous spaces outside text? They likely mean content. But to be safe, no indentation or use newline only. We can output each tag on new line without leading spaces. Good.
Potential issue: empty td with colspan=2:
Potential issue: empty th:
Potential issue: table caption and thead: If caption is bold, okay.
Potential issue: Should the note be inside tfoot or tbody? It is bottom row of table, likely tfoot. Allowed. Good.
Potential issue: The table has a rounded bottom border, not relevant.
Potential issue: The boxed Document Status maybe blockquote? It is a bordered box. Could use blockquote? Allowed. But not necessary. Could use
to represent box? The instruction doesn't require. But maybe use blockquote for boxed note? It says blockquote allowed. But content is normal paragraphs. Could wrap in blockquote? It might be a boxed section. But not necessary. If use blockquote, allowed. But no class. Could be okay. However "Document Status" heading inside blockquote? Allowed. But might alter semantics. Not needed.Potential issue: "Status of Compliance Documents" is a heading but not numbered. h2. Good.
Potential issue: The page may be page 2? They require page number placeholder 2. Good.
Let's ensure no disallowed tags: only h2,h3,p,table,caption,thead,tbody,tfoot,tr,th,td,br,strong. All allowed. class align-center, small-note. Good.
Need maybe use
inside tfoot td. Allowed. But p inside td okay. Could also just text. Use small-note to mark note. Good.
Need maybe use
for footnote? The note is table note. Good.
Potential issue: "只允许这些 class(小写,单值)" We use class="align-center" and class="small-note". Good.
Potential issue: "每页输出必须以
开头(页面内标题)" Our first tag is
. Good.
Potential issue: "页码用
2
结尾" Our last tag is that. Good.Need final only HTML. No code fence.
Double-check text:
"Compliance Documents are prepared by the Department of Building and Housing in accordance with section 22 of the Building Act 2004. A Compliance Document is for use in establishing compliance with the New Zealand Building Code."
Good.
"A person who complies with a Compliance Document will be treated as having complied with the provisions of the Building Code to which the Compliance Document relates. However, a Compliance Document is only one method of complying with the Building Code. There may be alternative ways to comply."
Good.
"Users should make themselves familiar with the preface to the New Zealand Building Code Handbook, which describes the status of Compliance Documents and explains alternative methods of achieving compliance."
Good.
"Defined words (italicised in the text) and classified uses are explained in Clauses A1 of the Building Code and in the Definitions at the start of this Compliance Document."
Good.
Table:
Caption: G13: Document History.
thead:
Date Alterations Maybe first column header should be blank. Good.
Data:
First published July 1992 Amendment 1 September 1993 pp. vii–viii, References
p. xi, Definitionsp. 25, Figure 3
p. 31, Figure 7Reprinted
incorporating
Amendment 1October 1994 Amendment 2 1 December 1995 p. viii, References Amendment 3 28 February 1998 p. ii, Document History
p. viii, Referencesp. 1, 1.0.1
p. 21, 1.0.1Second edition
published
1 July 2001Effective from
1 October 2001Document revised –
second edition issuedAmendment 1 Published March 2007
Effective from 23 June 2007p. 2, Document History, Status
p. 6, Contents
pp. 7–8, Referencespp. 9–10, Definitions
p. 52A, AS3 1.0, 1.0.1, 1.0.2
p. 55, IndexErratum 1 Effective from 23 June 2007 pp. 5-6, Contents
pp. 33-34, AS1 8.0, 8.1
pp. 50-51, AS2 7.0, 7.1Amendment 2 Effective from 21 June 2007 p. 2, Document History, Status
pp. 3, 4, 4A, Building Code Clause
p. 6, Contentsp. 8, References
p. 52A, VM4
p. 54, Indextfoot:
Note: Page numbers relate to the document at the time of Amendment and may not match page numbers in current document.
Need check "pp. 5-6" maybe original has "pp. 5-6" with hyphen. Good.
Potential issue: "AS1 8.0, 8.1" maybe "AS1 8.0, 8.1". Good.
Potential issue: "AS2 7.0, 7.1". Good.
Potential issue: "p. 52A, AS3 1.0, 1.0.1, 1.0.2" maybe original has "p. 52A, AS3 1.0, 1.0.1, 1.0.2". Good.
Potential issue: "p. 52A, VM4". Good.
Potential issue: "Document Status" paragraphs:
"The most recent version of this document, as detailed in the Document History, is approved by the Chief Executive of the Department of Building and Housing. It is effective from 21 June 2007 and supersedes all previous versions of this document."
"People using this Compliance Document should check for amendments on a regular basis. The Department of Building and Housing may amend any part of any Compliance Document at any time. Up-to-date versions of Compliance Documents are available from www.dbh.govt.nz"
Good.
Need maybe "Up-to-date" hyphen. Good.
Potential issue: Should we include "Document Status" as h2 because it's a major section? It is boxed, maybe h2. But first page h2 for page title? There are two headings. Rule: 页面内标题:第1页用 h2,后续页用 h2 或 h3(根据视觉层级). Since this is one page, first heading h2, second could h3. Good.
Potential issue: The top black bar might be page header, ignore. Good.
Potential issue: The bottom black bar ignore. Good.
Potential issue: The page number not visible, but placeholder 2. Good.
Need final no explanation. Ensure no Markdown. Good.
Let's consider if empty th is okay with no content. It might be considered meaningless blank? But table structure needs. Could use
? no. Could use Document ? Not in original. Better empty.Could use
G13: Document History as first header? But then Date/Alterations? Hmm. The gray row spans entire table, not first column. Caption is best.Potential issue: The table's first column header is blank, but maybe the gray row "G13: Document History" is actually a header row spanning all columns, and then Date/Alterations. If we use caption, the gray row not represented as row. But content preserved. Good.
Potential issue: The note row is inside table with rounded bottom. tfoot okay.
Potential issue: Should use
for note outside table? It is inside table. Good.
Potential issue: "small-note" class allowed. Good.
Potential issue: No style. Good.
Potential issue: No nbsp. Good.
Potential issue: No continuous spaces. In source, between tags newline. In text, check no double spaces. Let's scan:
"Status of Compliance Documents" single.
Paragraphs: "section 22 of the Building Act 2004. A" single.
"However, a" single.
"Users should" single.
"Defined words (italicised in the text) and" single.
Table: "pp. vii–viii, References" single. "p. xi, Definitions" single. "p. 25, Figure 3" single. "p. 31, Figure 7" single.
"Reprinted
incorporating
Amendment 1" no spaces."1 December 1995" single.
"p. viii, References" single.
"p. ii, Document History" single.
"p. viii, References" single.
"p. 1, 1.0.1" single.
"p. 21, 1.0.1" single.
"Second edition
published
1 July 2001" no spaces."Effective from
1 October 2001" no spaces."Document revised –
second edition issued" single around dash? "revised –
second" no double."Published March 2007
Effective from 23 June 2007" no double."p. 2, Document History, Status" single.
"p. 6, Contents" single.
"pp. 7–8, References" single.
"pp. 9–10, Definitions" single.
"p. 52A, AS3 1.0, 1.0.1, 1.0.2" single.
"p. 55, Index" single.
"pp. 5-6, Contents" single.
"pp. 33-34, AS1 8.0, 8.1" single.
"pp. 50-51, AS2 7.0, 7.1" single.
"p. 2, Document History, Status" single.
"pp. 3, 4, 4A, Building Code Clause" single.
"p. 6, Contents" single.
"p. 8, References" single.
"p. 52A, VM4" single.
"p. 54, Index" single.
Note: "Note: Page numbers relate to the document at the time of Amendment and may not match page numbers in current document." single.
Document Status paragraphs single.
Potential issue: "pp. 5-6" maybe should be "pp. 5–6"? Original shows hyphen? It appears "pp. 5-6" with hyphen. Keep.
Potential issue: "pp. 33-34" hyphen. Good.
Potential issue: "pp. 50-51" hyphen. Good.
Potential issue: "AS1 8.0, 8.1" maybe "AS1 8.0, 8.1". Good.
Potential issue: "AS2 7.0, 7.1". Good.
Potential issue: "VM4" maybe "VM4". Good.
Potential issue: "www.dbh.govt.nz" no period at end? Original no period. Good.
Need maybe include "Document Status" heading inside blockquote? Not necessary. But the box might be a note. Could use
around the two paragraphs and heading? Allowed. But if use blockquote, no class. It may represent box. But not required. Could be beneficial? The instruction says blockquote allowed. But if we wrap, it's okay. However heading inside blockquote? Allowed. But maybe not needed. Keep simple.Potential issue: The first paragraph after heading maybe not indented. Good.
Potential issue:
预览内容由文件识别整理,表格、公式及文字请以原始文件为准。
原文图片预览
PAGE IMAGES下载标准文件
Clause-G13-Foul-Water
英语 · PDF · 6 页 · 1.93 MB



