From fedc7b33a7c307969fcbc019370b3c0c776f50e3 Mon Sep 17 00:00:00 2001 From: Colin Kuskie Date: Wed, 27 Dec 2006 02:26:34 +0000 Subject: [PATCH] fixing misspelled word separate in all help files --- lib/WebGUI/i18n/English/Asset_SQLForm.pm | 8 ++++---- lib/WebGUI/i18n/English/Asset_SQLReport.pm | 4 ++-- .../i18n/English/Workflow_Activity_NotifyAboutUser.pm | 4 ++-- 3 files changed, 8 insertions(+), 8 deletions(-) diff --git a/lib/WebGUI/i18n/English/Asset_SQLForm.pm b/lib/WebGUI/i18n/English/Asset_SQLForm.pm index 2dbfcdc10..a601d3147 100644 --- a/lib/WebGUI/i18n/English/Asset_SQLForm.pm +++ b/lib/WebGUI/i18n/English/Asset_SQLForm.pm @@ -1043,8 +1043,8 @@ have been purged yet.

|, 'completeForm' => { message => q|This contains the entire form, complete and layed out in a WebGUI-style table. You don't need to add a -seperate form header, footer or anything else.|, - lastUpdated => 1149822620, +separate form header, footer or anything else.|, + lastUpdated => 1167186643, }, 'formLoop' => { @@ -1163,7 +1163,7 @@ automatically, using a default layout.

formloop handles placing everything that you need in a table, automatically. This allows you some flexibility in your form layout.

Finally there is the option of placing -each seperate field by hand. This allows you to define the order and +each separate field by hand. This allows you to define the order and place of each form element. Please note, however, that using this method will not automatically follow changes you make to the SQLForm. If you add, delete or rename a field you must update the template by @@ -1171,7 +1171,7 @@ hand. Using this method also implies the use of formHeader and formFooter. You should use the following two template variables:

|, - lastUpdated => 1149822668, + lastUpdated => 1167186648, }, 'search template help title' => { diff --git a/lib/WebGUI/i18n/English/Asset_SQLReport.pm b/lib/WebGUI/i18n/English/Asset_SQLReport.pm index e2016536b..a244c4a72 100644 --- a/lib/WebGUI/i18n/English/Asset_SQLReport.pm +++ b/lib/WebGUI/i18n/English/Asset_SQLReport.pm @@ -316,8 +316,8 @@ query, but will be prefixed with queryN where N goes from 2 to 5.

'Prequery statements description' => { message => q|

Prequery statements are sql statements executed before the real query. You can use prequery statements for instance to set variables that you want to use in the real query. For example:

set @myVariable := 1
-

The prequery statements are seperated from each other by returns and cannot use placeholders. You can use macro's within the prequery statements, however. Please note that prequery statements are only visible in the query they belong to and that you can only use statements that are allowed by the database link.

|, - lastUpdated => 0, +

The prequery statements are separated from each other by returns and cannot use placeholders. You can use macro's within the prequery statements, however. Please note that prequery statements are only visible in the query they belong to and that you can only use statements that are allowed by the database link.

|, + lastUpdated => 1167186661, }, diff --git a/lib/WebGUI/i18n/English/Workflow_Activity_NotifyAboutUser.pm b/lib/WebGUI/i18n/English/Workflow_Activity_NotifyAboutUser.pm index a75a9c12a..d1a935c81 100644 --- a/lib/WebGUI/i18n/English/Workflow_Activity_NotifyAboutUser.pm +++ b/lib/WebGUI/i18n/English/Workflow_Activity_NotifyAboutUser.pm @@ -26,9 +26,9 @@ our $I18N = { }, 'to help' => { - message => q|The email address to send the message to. You may put in mutliple email addresses seperated by commas.|, + message => q|The email address to send the message to. You may put in multiple email addresses separated by commas.|, context => q|the hover help for the to field|, - lastUpdated => 0, + lastUpdated => 1167186609, }, 'to' => {