Document how template variables work in export mode.

Change how pagination works when exporting.
Early code for exporting keyword pages.
This commit is contained in:
Colin Kuskie 2009-04-17 17:11:07 +00:00
parent 33383be36c
commit 08c033b2c5
3 changed files with 167 additions and 23 deletions

View file

@ -16,7 +16,7 @@ our $I18N = {
},
'stories per page help' => {
message => q|The number of stories displayed on a page.|,
message => q|The number of stories displayed on a page. If the asset is exported as HTML, then the generated page will have 10 standard pages of stories.|,
context => q|Hoverhelp in the edit screen and template.|,
lastUpdated => 0
},
@ -202,25 +202,25 @@ our $I18N = {
},
'searchHeader' => {
message => q|HTML code for beginning the search form.|,
message => q|HTML code for beginning the search form. This variable is empty when the Story Archive is being exported as HTML.|,
context => q|Template variable.|,
lastUpdated => 0,
},
'searchForm' => {
message => q|The text field where users can enter in keywords for the search.|,
message => q|The text field where users can enter in keywords for the search. This variable is empty when the Story Archive is being exported as HTML.|,
context => q|Template variable.|,
lastUpdated => 0,
},
'searchButton' => {
message => q|Button with internationalized label for submitting the search form.|,
message => q|Button with internationalized label for submitting the search form. This variable is empty when the Story Archive is being exported as HTML.|,
context => q|Template variable.|,
lastUpdated => 0,
},
'searchFooter' => {
message => q|HTML code for ending the search form.|,
message => q|HTML code for ending the search form. This variable is empty when the Story Archive is being exported as HTML.|,
context => q|Template variable.|,
lastUpdated => 0,
},