Tokens Reference in languages.xml

[ExampleCurrency]

Example Output: A number of type "Currency": $12345.67899 (Or perhaps rounded off: $12345.68)

How to Use: This token is used to provide an example valid number format for users or visitors. Note that the output obeys regional and cultural settings and produces currency format accordingly (i.e. Euro in Euro countries, Dollars in North America, and Baht in Thailand).

How to Modify: The value of this token cannot be modified. However, the format of this token may be modified by changing the "thisAppDefaultCulture" setting on the "Regional Settings" tab of the "[thisAppTitle] Options" page.

[ExampleDateTime]

Example Output: December 30, 1899 3:48:01 PM (Or regional equivalent in the format mmm dd, yyyy hh:mm:ss)

How to Use: This token is used to provide an example valid date format for users or visitors.

How to Modify: The value of this token cannot be modified.

[ExampleDouble]

Example Output: A number of type "Double": 12345.67899 (Or perhaps rounded off: 12345.68)

How to Use: This token is used to provide an example valid number format for users or visitors. A "Double" is a fractional number (contains a decimal).

How to Modify: The value of this token cannot be modified.

[ExampleExpiryDate]

Example Output: December 30, 1899 3:48:01 PM (Or regional equivalent in the format mmm dd, yyyy hh:mm:ss)

How to Use: This token is used to provide an example valid date format for users or visitors. Note that the output obeys regional and cultural settings and produces date format accordingly.

How to Modify: The value of this token can be modified by adjusting the "itemsExpireNumber" and "itemsExpireInterval" options on the "Miscellaneous Options" panel of the "[thisAppTitle] Options" page. As well, the format of this token may be modified by changing the "thisAppDefaultCulture" setting on the "Regional Settings" tab of the "[thisAppTitle] Options" page.

[ExampleInteger]

Example Output: A number of type "Integer": 12,345 (In USA), or 12.345 (In French-Canada)

How to Use: This token is used to provide an example valid number format for users or visitors. Note that the output obeys regional and cultural settings and produces number format accordingly.

[ExampleLongDate]

Example Output: December 30, 1899 (Or regional equivalent in the format mmm dd, yyyy)

How to Use: This token is used to provide an example valid date format for users or visitors.

How to Modify: The value of this token cannot be modified.

[ExampleShortDate]

Example Output: 12/30/1899 (Or regional equivalent in the format mm/dd/yyyy)

How to Use: This token is used to provide an example valid date format for users or visitors.

How to Modify: The value of this token cannot be modified.

[ExampleTime]

Example Output: 3:48:01 PM (Or regional equivalent in the format hh:mm:ss)

How to Use: This token is used to provide an example valid date/time format for users or visitors.

How to Modify: The value of this token cannot be modified.

[fieldAddress]

Example Output: Mailing Address, Street Address

How to Use: Note that this token does not write the current user's address. Instead, it writes the friendly name of the datafield used to store the current user's address. This token should be used for example on the sign-up or registration page form, or wherever you wish the word "Street Address" to appear (or language specific equivalent).

How to Modify: The output of this token can be altered by editing the "[User] Account Field Names" on the "[thisAppTitle] Options" page.

[fieldBirthDate]

Example Output: Birthday, Date of Establishment: As in "Your company's [fieldBirthDate] is _________?"

How to Use: Note that this token does not write to the page the date the user's birth date. Instead, it writes the friendly name of the datafield used to store that date.

How to Modify: The output of this token can be altered by editing the "[User] Account Field Names" on the "[thisAppTitle] Options" page.

[fieldClass]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "class" in the "items" table.

How to Modify: The output of this token can be altered by editing the "Items Field Names and Options Groups" on the "[thisAppTitle] Options" page. Note that this token will default to the name of this field in the default field set and option group; however, where appropriate, this token can display the field name from other field sets.

[fieldClosingDate]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "closing_date" in the "items" table.

[fieldCity]

Example Output: City, Suburb, Town, etc.: As in "What [fieldCity] do you live in?"

How to Use: Note that this token does not write the current user's address. Instead, it writes the friendly name of the datafield used to store the current user's city. This token should be used for example on the sign-up or registration page form, or wherever you wish the word "City" to appear (or language specific equivalent).

How to Modify: The output of this token can be altered by editing the "[User] Account Field Names" on the "[thisAppTit le] Options" page.

[fieldCompanyName]

Example Output: Company Name: As in "Please enter the [fieldCompanyName] of your business."

How to Use: Note that this token does not write the current user's company name. Instead, it writes the friendly name of the datafield used to store the current user's company name. This token should be used for example on the sign-up or registration page form, or wherever you wish the word "Company Name" to appear (or language specific equivalent).

How to Modify: The output of this token can be altered by editing the "[User] Account Field Names" on the "[thisAppTitle] Options" page.

[fieldCounty]

Example Output: County, Region, Municipality: As in "What [fieldCounty] do you live in?"

How to Use: Note that this token does not write the current user's address. Instead, it writes the friendly name of the datafield used to store the current user's county. This token should be used for example on the sign-up or registration page form, or wherever you wish the word "County/Region" to appear (or language specific equivalent).

How to Modify: The output of this token can be altered by editing the "[User] Account Field Names" on the "[thisAppTitle] Options" page.

[fieldCountry]

Example Output: Country: As in "I live in the [fieldCountry] of Canada?"

How to Use: Note that this token does not write the current user's address. Instead, it writes the friendly name of the datafield used to store the current user's country. This token should be used for example on the sign-up or registration page form, or wherever you wish the word "Country" to appear (or language specific equivalent).

How to Modify: The output of this token can be altered by editing the "[User] Account Field Names" on the "[thisAppTitle] Options" page.

[fieldCulture]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "culture" in the "items" table.

[fieldDateLastLoggedIn]

Example Output: Date Last Logged in

How to Use: Note that this token does not write to the page the date the user logged in. Instead, it writes the friendly name of the datafield used to store that date.

How to Modify: The output of this token can be altered by editing the "[User] Account Field Names" on the "[thisAppTitle] Options" page.

[fieldDateLastModified]

Example Output: Date Last Modified

How to Use: Note that this token does not write to the page the date the user's account was last modified. Instead, it writes the friendly name of the datafield used to store that date.

How to Modify: The output of this token can be altered by editing the "[User] Account Field Names" on the "[thisAppTitle] Options" page.

[fieldDateSignedUp]

Example Output: Date of Registration

How to Use: Note that this token does not write the current user's registration date to the page. Instead, it writes the friendly name of the datafield used to store the current user's date of registration.

How to Modify: The output of this token can be altered by editing the "[User] Account Field Names" on the "[thisAppTitle] Options" page.

[fieldDisplayTitle]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "display_title" in the "items" table.

[fieldEmail]

Example Output: Email, or Email Address: As in "Please enter your [fieldEmail] to subscribe to our newsletter."

How to Use: Note that this token does not write the current user's email to the page. Instead, it writes the friendly name of the datafield used to store the current user's email address. This token should be used for example on the sign-up or registration form, or wherever you wish the words "Email Address" to appear (or language specific equivalent).

How to Modify: The output of this token can be altered by editing the "[User] Account Field Names" on the "[thisAppTitle] Options" page.

[fieldFamily]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "family" in the "items" table.

[fieldFaxPhone]

Example Output: Fax: As in "[fieldFaxPhone]: 1-800-123-4567"

How to Use: Note that this token does not write the current user's fax phone number. Instead, it writes the friendly name of the datafield used to store the current user's fax phone number (or perhaps simply a third phone number after the primary and secondary fields). This token should be used for example on the sign-up or registration form, or wherever you wish the word "Fax" to appear (or language specific equivalent).

How to Modify: The output of this token can be altered by editing the "[User] Account Field Names" on the "[thisAppTitle] Options" page.

[fieldFirstName]

Example Output: First Name, Given Name: As in "Please enter your [fieldFirstName] to subscribe to our newsletter."

How to Use: Note that this token does not write the current user's name to the page. Instead, it writes the friendly name of the datafield used to store the current user's first/given name. This token should be used for example on the sign-up or registration form, or wherever you wish the words "First Name" to appear (or language specific equivalent).

How to Modify: The output of this token can be altered by editing the "[User] Account Field Names" on the "[thisAppTitle] Options" page.

[fieldGeneralDescription]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "general_description" in the "items" table.

[fieldGenus]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "genus" in the "items" table.

[fieldHits]

Example Output: (Any valid field name: Usually one indicating the number of hits on the item.)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "hits" in the "items" table.

[fieldItemID]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "itemID" in the "items" table.

[fieldImageURL]

Example Output: Image URL, Photo/Logo: "Add a [fieldImageURL] to your [user] account."

How to Use: Note that this token does not write the current user's imageURL to the page. Instead, it writes the friendly name of the datafield used to store the current user's imageURL. This token is used in the administrative area where it's necessary to administer or view the user's photo.

How to Modify: The output of this token can be altered by editing the "[User] Account Field Names" on the "[thisAppTitle] Options" page.

[fieldInfoURL]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "info_URL" in the "items" table.

[fieldInfoURLWindowHeight]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "info_URL_height" in the "items" table.

[fieldInfoURLWindowWidth]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "info_URL_width" in the "items" table.

[fieldItemLimit]

Example Output: Item Limit: As in "You have exceeded your [fieldItemLimit] and are not authorized to add any new items."

How to Use: Note that this token does not write the current user's item limit to the page. Instead, it writes the friendly name of the datafield used to store the current user's item limit. This token is used in the administrative area where it's necessary to administer or view the user's item limit.

How to Modify: The output of this token can be altered by editing the "[User] Account Field Names" on the "[thisAppTitle] Options" page.

[fieldItemReferenceCode]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "item_referencecode" in the "items" table.

[fieldLastName]

Example Output: Surname, Last Name, Family Name: As in "Please enter your [fieldLastName] to subscribe to our newsletter."

How to Use: Note that this token does not write the current user's name to the page. Instead, it writes the friendly name of the datafield used to store the current user's surname. This token should be used for example on the sign-up or registration form, or wherever you wish the word "Province/State" to appear (or language specific equivalent).

How to Modify: The output of this token can be altered by editing the "[User] Account Field Names" on the "[thisAppTitle] Options" page.

[fieldListingPrice]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "listing_price" in the "items" table.

[fieldListingPriceTerms]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "listing_price_terms" in the "items" table.

[fieldLoginCount]

Example Output: Logged In # Times

How to Use: Note that this t oken does not write the number of times the current user's has logged in. Instead, it writes the friendly name of the datafield used to store that number.

How to Modify: The output of this token can be altered by editing the "[User] Account Field Names" on the "[thisAppTitle] Options" page.

[fieldNotes]

Example Output: Notes, Biography, etc.

How to Use: Note that this token does not write the current user's biography. Instead, it writes the friendly name of the datafield used to store the current user's biography. This token should be used for example on the sign-up or registration page form, or wherever you wish the word "Biography" to appear (or language specific equivalent).

How to Modify: The output of this token can be altered by editing the "[User] Account Field Names" on the "[thisAppTitle] Options" page.

[fieldOpeningDate]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "opening_date" in the "items" table.

[fieldOrder]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "order" in the "items" table.

[fieldPeopleID]

Example Output: Agent ID, UserID: As in "Your [fieldPeopleID] is 451."

How to Use: Note that this token does not write the current user's peopleID to the page. Instead, it writes the friendly name of the datafield used to store that number.

How to Modify: The output of this token can be altered by editing the "[User] Account Field Names" on the "[thisAppTitle] Options" page.

[fieldPhylum]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "phylum" in the "items" table.

[fieldProvince]

Example Output: Province, State: As in "Have you ever been to the [fieldProvince] of Californ ia?"

How to Use: Note that this token does not write the current user's address. Instead, it writes the friendly name of the datafield used to store the current user's province/state. This token should be used for example on the sign-up or registration form, or wherever you wish the word "City" to appear (or language specific equivalent).

How to Modify: The output of this token can be altered by editing the "[User] Account Field Names" on the "[thisAppTitle] Options" page.

[fieldSalePrice]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "sale_price" in the "items" table.

[fieldUsername]

Example Output: Username, Nom d'Utilisateur: As in "Please enter your [fieldUsername] to log in."

How to Use: Note that this token does not write the current user's username to the page. Instead, it writes the friendly name of the datafield used to store the current user's username. This token should be used for example on the login form, or wherever you wish the word "Username" to appear (or language specific equivalent).

How to Modify: The output of this token can be altered by editing the "[User] Account Field Names" on the "[thisAppTitle] Options" page.

[fieldPassword]

Example Output: Password, Mot de Passe: As in "Please enter your [fieldPassword] to log in."

How to Use: Note that this token does not write the current user's password to the page. Instead, it writes the friendly name of the datafield used to store the current user's password. This token should be used for example on the login form, or wherever you wish the word "Password" to appear (or language specific equivalent).

How to Modify: The output of this token can be altered by editing the "[User] Account Field Names" on the "[thisAppTitle] Options" page.

[fieldPhone]

Example Output: PH, Phone Number, Dial Toll-Free: As in "[fieldPhone]: 1-800-123-4567"

How to Use: Note that this token does not write the current user's phone number. Instead, it writes the friendly name of the datafield used to store the current user's phone number. This token should be used for example on the sign-up or registration form, or wherever you wish the word "Phone" to appear (or language specific equivalent).

How to Modify: The output of this token can be altered by editing the "[User] Account Field Names" on the "[thisAppTitle] Options" page.

[fieldPostalCode]

Example Output: Postal Code, Zip Code: As in "Please enter the [fieldPostalCode] associated with your mailing address."

How to Use: Note that this token does not write the current user's postal/zip code. Instead, it writes the friendly name of the datafield used to store the current user's postal/zip code. This token should be used for example on the sign-up or registration form, or wherever you wish the word "Postal/Zip Code" to appear (or language specific equivalent).

How to Modify: The output of this token can be altered by editing the "[User] Account Field Names" on the "[thisAppTitle] Options" page.

[fieldSecondaryPhone]

Example Output: PH2, Alternate Phone Number, Mobile Phone #: As in "[fieldSecondaryPhone]: 1-800-123-4567"

How to Use: Note that this token does not write the current user's alternate phone number. Instead, it writes the friendly name of the datafield used to store the current user's secondary phone number. This token should be used for example on the sign-up or registration form, or wherever you wish the word "Secondary Phone" to appear (or language specific equivalent).

How to Modify: The output of this token can be altered by editing the "[User] Account Field Names" on the "[thisAppTitle] Options" page.

[fieldSpecies]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "species" in the "items" table.

[fieldStatus]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "status" in the "items" table.

[fieldTransactionType]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "transaction_type" in the "items" table.

How to Modify: The output of t his token can be altered by editing the "Items Field Names and Options Groups" on the "[thisAppTitle] Options" page. Note that this token will default to the name of this field in the default field set and option group; however, where appropriate, this token can display the field name from other field sets.

[fieldURL]

Example Output: URL, WWW, Web Link, etc.: As in "The [fieldURL] of Google is http://www.google.com/"

How to Use: Note that this token does not write the current user's URL. Instead, it writes the friendly name of the datafield used to store the current user's URL. This token should be used for example on the sign-up or registration form, or wherever you wish the word "URL" to appear (or language specific equivalent).

How to Modify: The output of this token can be altered by editing the "[User] Account Field Names" on the "[thisAppTitle] Options" page.

[fieldUserDefinedBoolean1]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "UserDefinedBoolean1" in the "items" table.

[fieldUserDefinedBoolean2]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "UserDefinedBoolean2" in the "items" table.

[fieldUserDefinedCurrency1]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "UserDefinedCurrency1" in the "items" table.

[fieldUserDefinedCurrency1Terms]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "UserDefinedCurrency1Terms" in the "items" table.

[fieldUserDefinedCurrency2]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "UserDefinedCurrency2" in the "items" table.

[fieldUserDefinedCurrency2Terms]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "UserDefinedCurrency2Terms" in the "items" table.

[fieldUserDefinedCurrency3]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "UserDefinedCurrency3" in the "items" table.

[fieldUserDefinedCurrency4]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "UserDefinedCurrency4" in the "items" table.

[fieldUserDefinedDoubleNumber1]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "UserDefinedDoubleNumber1" in the "items" table.

[fieldUserDefine dDoubleNumber2]

Example Output: (Any valid field name)

[fieldUserDefinedNumber1]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "UserDefinedNumber1" in the "items" table.

[fieldUserDefinedNumber1Term]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "UserDefinedNumber1Terms" in the "items" table.

[fieldUserDefinedNumber2]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "UserDefinedNumber2" in the "items" table.

[fieldUserDefinedNumber3]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "UserDefinedNumber3" in the "items" table.

[fieldUserDefinedMemo1]

Example Output: (Any valid field name)

How to Use: Note that this toke n does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "UserDefinedMemo1" in the "items" table.

[fieldUserDefinedMemo2]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "UserDefinedMemo2" in the "items" table.

[fieldUserDefinedMemo3]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "UserDefinedMemo3" in the "items" table.

[fieldUserDefinedMemo4]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "UserDefinedMemo4" in the "items" table.

[fieldUserDefinedMemo5]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "UserDefinedMemo5" in the "items" table.

[fieldUserDefinedText1]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "UserDefinedText1" in the "items" table.

[fieldUserDefinedText2]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "UserDefinedText2" in the "items" table.

[fieldUserDefinedText3]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "UserDefinedText3" in the "items" table.

[fieldUserDefinedText4]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "UserDefinedText4" in the "items" table.

[fieldUserDefinedText5]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "UserDefinedText5" in the "items" table.

[fieldUserDefinedText6]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "UserDefinedText6" in the "items" table.

[fieldUserDefinedText7]

Example Output: (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "UserDefinedText7" in the "items" table.

[fieldUserDefinedText8]

Example Output : (Any valid field name)

How to Use: Note that this token does not write the current item's information to the page. Instead, it writes the friendly name of the datafield called "UserDefinedText8" in the "items" table.

[ListingsURL]

Example Output: http://www.your_website_address.com/listings.asp (The absolute URL of the "listings.asp" page on your web site.)

How to Use: This token writes the absolute URL of the "listings.asp" page on your web site. For example the following code will produce a link which directs the user to your listings.asp page.

<a href="[ListingsURL]">CLICK</a>

If necessary, a querystring can be used with this token as in the following example:

<a href="[ListingsURL]?strKeywords=cat and mouse">CLICK</a>

[MainCategory]

Example Output: Main Category, Group: As in "Click on a link to view all items in that [maincategory]."

How to Use: 20/20 DataShed provides options to change the terminology used to describe main categories of items on your web site. For example, in an English setting it may be appropriate to use the term "Main Category" while in other languages that term can be translated.

How to Modify: The output of this token can be altered by editing the "Miscellaneous Otions" on the "[thisAppTitle] Options" page. We expect that this token and it's related token, [MainCategory_plural], will be sufficient in the majority of cultural settings. Although we recognize that in some languages the singular form of a noun is more complicated that it may seem in English and we apologize if these tools are insufficient for your language. In such cases, perhaps it's best not to use the token but write your language strings using static text.

[MainCategory_plural]

Example Output: Main Categories, Groups: As in "Browse through our [maincategory_plural] to find the item you're looking for."

How to Use: 20/20 DataShed provides options to change the terminology used to describe main categories of items on your web site. For example, in an English setting it may be appropriate to use the term "Main Categories" while in other languages that term can be translated.

How to Modify: The output of this token can be altered by editing the "Miscellaneous Otions" on the "[thisAppTitle] Options" page. We expect that this token and it's related token, [MainCategory], will be sufficient in the majority of cultural settings. Although we recognize that in some languages the singular form of a noun is more complicated that it may seem in English and we apologize if these tools are insufficient for your language. In such cases, perhaps it's best not to use the token but write your language strings using static text.

[ParentCompanyCompanyName]

Example Output: Your Company Name, Big Bob's Auto Sales, Re/Max

How to Use: This token writes the name of the parent company to the page. This information is stored in the "company_name" field in the user account currently assigned as the "Parent" company of 20/20 DataShed.

How to Modify: This value can be modified either by changing the Parent Company (via the "thisAppParentCompanyID" option in the "Miscellaneous Options" of "[thisAppTitle] Options") or by editing the current company account.

[ParentCompanyEmail]

Example Output: info@your_website.com

How to Use: This token writes the email address of the parent company's administrator to the page. This information is stored in the "email" field in the user account currently assigned as the "Parent" company of 20/20 DataShed.

[ParentCompanyFirstName]

Example Output: John or Abdul: As in, Mr. John Doe

How to Use: This token writes the first name of the parent company's administrator to the page. This information is stored in the "firstname" field in the user account currently assigned as the "Parent" company of 20/20 DataShed.

[ParentCompanyLastName]

Example Output: Doe or Thompson, etc.: As in, Mr. John Doe

How to Use: This token writes the surname/last name of the parent company's administrator to the page. This information is stored in the "firstname" field in the user account currently assigned as the "Parent" company of 20/20 DataShed.

[ParentCompanyTitle]

Example Output: Mr., Mrs., Ms., Dr., etc.

How to Use: This token writes the title/salutation of the parent company's administrator to the page. This information is stored in the "title" field in the user account currently assigned as the "Parent" company of 20/20 DataShed.

[ParentCompanyURL]

Example Output: http://www.your_website_address.com/

How to Use: This token writes the parent company's URL to the page - usually, this URL represents the current web site (where 20/20 DataShed was installed) although it does not have to. This information is stored in the "URL" field in the user account currently assigned as the "Parent" company of 20/20 DataShed.

[Request.Form("")]

Example Output: (Any valid value of an item currently available in the Request.Form context)

How to Use: This token can be used to write information to the page which has been gather by a HTML form via the POST method. This token writes the value of a form field to the page.

How to Modify: This token can be used to output the value of a current form element by placing any valid element name into the quotation marks. Essentially, for users who have experience with ASP, this token is synonymous with the properties of the Request.Form collection as in Request.Form("element name").

Example Usage: Within the languages.xml file, you may use this token in this manner:

<string>Thank you. The email message has been sent and we will respond to [Request.Form("senderaddress")] as soon as possible.</string>

This is similar to the text displayed by 20/20 DataShed when the visitor submits an inquiry using the "f-email.asp" page.

Things to note:

This string is used within the context of an HTML form POST. Therefore, the Request.Form currently has values. This token will have no output if the form was submitted by the GET method, or if the form does not have an element called "senderaddress".
senderaddress is the name of a valid form element (which, after the POST method becomes an item in the Request.Form collection). In this example, presume that this form element will contain the user's email address. The token will work for any valid form element within the current context.

[SubCategory]

Example Output: Sub Category, Sub-Category: As in "You can narrow your search by selecting a [subcategory]."

How to Use: 20/20 DataShed provides options to change the terminology used to describe sub categories of items on your web site. For example, in an English setting it may be appropriate to use the term "Sub Category" while in other languages that term can be translated.

How to Modify: The output of this token can be altered by editing the "Miscellaneous Otions" on the "[thisAppTitle] Options" page. We expect that this token and it's related token, [SubCategory_plural], will be sufficient in the majority of cultural settings. Although we recognize that in some languages the singular form of a noun is more complicated that it may seem in English and we apologize if these tools are insufficient for your language. In such cases, perhaps it's best not to use the token but write your language strings using static text.

[SubCategory_plural]

Example Output: Sub Categories, Sub-Categories: As in "You may select multiple [subcategory_plural] to broaden your search."

How to Use: 20/20 DataShed provides options to change the terminology used to describe sub categories of items on your web site. For example, in an English setting it may be appropriate to use the term "Sub Categories" while in other languages that term can be translated.

How to Modify: The output of this token can be altered by editing the "Miscellaneous Otions" on the "[thisAppTitle] Options" page. We expect that this token and it's related token, [SubCategory], will be sufficient in the majority of cultural settings. Although we recognize that in some languages the singular form of a noun is more complicated that it may seem in English and we apologize if these tools are insufficient for your language. In such cases, perhaps it's best not to use the token but write your language strings using static text.

[thisAppTitle]

Example Output: 20/20 DataShed, Big Bob's Auto Sales, 20/20 Real Estate, Re/Max Inventory System

How to Use: 20/20 DataShed provides the option to change the name of the product. In effect, the product can be rebranded to suit your own business model more appropriately.

How to Modify: The output of this token can be altered by editing the "Miscellaneous Otions" on the "[thisAppTitle] Options" page.

[User]

Example Output: User, Agent, Seller, Subscriber, etc.: As in "Are you a [User] of this web site?"

How to Use: 20/20 DataShed provides options to change the terminology used to describe users of your web site. For example, in a Real Estate application it might be appropriate to refer to a user of your web site as an "Agent". While in the automotive industry, perhaps it's best to refer to a user as a "Sales Representative". This token may be used to produce that title or word when appropriate.

How to Modify: The output of this token can be altered by editing the "Miscellaneous Otions" on the "[thisAppTitle] Options" page. We expect that this token and it's related token, [User_plural], will be sufficient in the majority of cultural settings. Although we recognize that in some languages the singular form of a noun is more complicated that it may seem in English and we apologize if these tools are insufficient for your language. In such cases, perhaps it's best not to use the token but write your language strings using static text.

[User_plural]

Example Output: Users, Agents, Sellers, Subscribers, etc.: As in "Some tools are available only to [user_plural] of this web site."

How to Use: 20/20 DataShed provides options to change the terminology used to describe users of your web site. For example, in a Real Estate application it might be appropriate to refer to your users "Agents". While in the automotive industry, perhaps it's best to refer to users "Sales Representatives". This token may be used to produce that title or word when appropriate - note that this should be the plural form of the [User] token.

How to Modify: The output of this token can be altered by editing the "Miscellaneous Options" on the "[thisAppTitle] Options" p age. We expect that this token and it's related token, [User], will be sufficient in the majority of cultural settings. Although we recognize that in some languages the plural form of a noun is more complicated that it may seem in English and we apologize if these tools are insufficient for your language. In such cases, perhaps it's best not to use the token but write your language strings using static text.

<![CDATA[]]>

Example Output: Character Data (XML Text Node)

How to Use: This object is used to print pure characters to a web page or other destination. Anything between the brackets in this object is passed through the XML Parser without any manipulation. Note that this is the only method one can use to pass HTML or other markup from XML. For example, an html tag such as <b> will cause an XML syntax error. The only way to use markup in an XML file is to encapsulate the code inside a CDATASection. Example: <!CDATA[[<b>]]>THIS IS BOLD TEXT<!CDATA[[</b>]]>

How to Modify: (XML CDATASection Object) Note that this token adheres to the XML DOM specification -- we at 20/20 Applications did not create this. We've used it in the languages.xml file according to the XML language specification outlined by the W3C (World Wide Web Consortium). For detailed information about this object, we recommend you visit www.w3.org or www.devguru.com.

Tokens Reference in languages.xml

Related topics