Page tree

The following examples illustrate the results of different page name patterns.


Single page input files Example 1: Correct

Refined page names

Page name pattern

Linked to version page

1_RC_Eng.p1.pdf

[#]_RC_Eng.p1.pdf

 

 

VP_1.pdf

3_RC_Eng.p1.pdf

VP_3.pdf

5_RC_Eng.p1.pdf

VP_5.pdf


Single page input files Example 2: Incorrect

Refined page names

Page name pattern

Linked to version page

1_RC_Eng.p1.pdf

1_RC_Eng.p[#].pdf

 

 

VP_1.pdf

3_RC_Eng.p1.pdf

A versioned page is not created for these pages (3_RC_Eng.p1.pdf and 5_RC_Eng.p1.pdf) because the refined page name does not match the pattern.

 

5_RC_Eng.p1.pdf


Multi-page input files Example 1: Correct

Refined page names

Page name pattern

Linked to version page

1-3_RC_Eng.p1.pdf

1-3_RC_Eng.p[#].pdf

 

 

VP_1.pdf

1-3_RC_Eng.p2.pdf

VP_2.pdf

1-3_RC_Eng.p3.pdf

VP_3.pdf


Multi-page input files Example 2: Incorrect

Refined page names

Page name pattern

Linked to version page

1-3_RC_Eng.p1.pdf

[#]_RC_Eng.p1.pdf

 

 

Versioned pages are not created because the refined page name does not match the pattern. That is, the [#] tag does not accept hyphens.

 

 

1-3_RC_Eng.p2.pdf

1-3_RC_Eng.p3.pdf


Multi-page input files Example 3: Incorrect

Refined page names

Page name pattern

Linked to version page

1-3_RC_Eng.p1.pdf

[$]_RC_Eng.p1.pdf

 

 

Versioned pages are not created because no integer is provided for the number portion of the versioned page name. That is, VP_1-3.pdf is not a valid name.

 

 

1-3_RC_Eng.p2.pdf

1-3_RC_Eng.p3.pdf

  • No labels