NOTE: This topic only applies to releases of the Workplace Suite prior to the Summer 2005 release. As of the Summer 2005 release, the Localization tab on the administration interface allows you to make all of the localization changes described below. As a result, Summer 2005 and later releases do not support manual modification of DWP properties for localization.
CorasWorks web parts have a number of properties that can only be modified by manually editing the DWP file associated with this web part. The properties described here relate specifically to localization. You can edit a DWP file by exporting the web part to a location of your choice, making the desired changes, and then uploading it back onto your site.
The properties described here allow you to change the function and display of the web part. Please keep in mind the XML namespace of the web part you are changing, or these properties will not be enabled within the web part. XML namespaces for all CorasWorks web parts are provided in the For Developers help topic.
Also note that some of these properties some may require the use of a "<", ">", or "&" symbol. With the exception of the LCIDXML property, you must replace these characters with their encoded equivalents of "<", ">", and "&" respectively.
These properties are only viewable in the DWP if the default settings have been changed.
This property will allow the Administrator to alter the
Column Header Name for Type. Type is displayed when the type icons are visible
for a document library. This only applies to list of a Document Library
Type.
Use: <TypeHeaderName xmlns="webpart_namespace">Type Header
Name</TypeHeaderName >
Example: <TypeHeaderName xmlns=
"CorasWSC.My.Document.RollUp">Tip</TypeHeaderName >
This property is used to determine the root folder of where a
document resides within a list. In order to permit the edit and/or linking to an
item, this property is required. Since this list property is language dependant,
should a different language be chosen the equivalent (URL Dir Name) must be
entered.
Use: <URLDirName xmlns="webpart_namespace">URL Dir
Name</URLDirName>
Example: <URLDirName xmlns=
"CorasWSC.My.Document.RollUp">Nome directory
URL</URLDirName>
This property is used to determine the direct location of
where a document resides within a list. In order to permit the linking to an
item directly, this property is required. Since this list property is language
dependant, should a different language be chosen the equivalent (Encoded
Absolute URL) must be entered.
Use: <EncodedAbsoluteURL
xmlns="webpart_namespace">Encoded Absolute
URL</EncodedAbsoluteURL>
Example: <EncodedAbsoluteURL xmlns=
"CorasWSC.My.Document.RollUp">URL assoluto
codificato</EncodedAbsoluteURL>
NOTE: As of the Summer 05 release, localization can be done very easily on the Localization tab of the administration interface. See “Admin: Localization Tab” for details.
This property allows you to localize the user interface. The easiest way to use this property is to follow these steps:
1. Copy the sample code below into Notepad and make the appropriate translations to the content between each tag.
2. Replace any double quotes (“) with single quotes (‘). Make sure there aren’t any brackets ([ ]) anywhere in the text. If there are, replace them with parentheses ( ). The XML nodes must appear in the exact order as they are shown below; you can not omit nodes or reorder them. (You can use brackets in other areas of the .dwp, but not in this section. This is because the CDATA expression (added later in these procedures) uses brackets to identify the boundaries of the text to work on.)
3. Export the
web part you want to localize and add this: <LCIDXML
xmlns="webpart_namespace"><![CDATA[]]></LCIDXML> (where
”webpart_namespace” is the web part namespace identified in the For Developers help topic. Remember that web part
namespaces are case-sensitive.
For example: <LCIDXML
xmlns="CorasWSC.Calendar.RollUp"><![CDATA[]]></LCIDXML>
4. Copy the modified LCIDXML content from Step 2 and place it after the opening bracket after CDATA.
5. Save the localized web part and import it into your site. CorasWorks recommends that you use a naming convention that makes it clear which language(s) are supported by the web part.
Sample Code:
<?xml version='1.0'
?>
<CorasWorks>
<CalendarRollUpAdvanced
id='default'>
<Today>Today</Today>
<ViewByDay>View by Day</ViewByDay>
<ViewByWeek>View
by Week</ViewByWeek>
<ViewByMonth>View by
Month</ViewByMonth>
<Search>Search</Search>
<ReturnType>Return
Type:</ReturnType>
<Administration>Administration</Administration>
<SiteUrl>Site URL:</SiteUrl>
<LevelsSearch>Levels
Searched:</LevelsSearch>
<Schemas>Schema(s):</Schemas>
<AvailableLists>Available List(s):</AvailableLists>
<CurrentLists>Current List(s):</CurrentLists>
<CloseAdministration>Close
Administration</CloseAdministration>
<Status>Status:</Status>
<ReturnSitesList>Return All
Sites & Lists</ReturnSitesList>
<Selective>Selective</Selective>
<LineofSite>Line of
Site</LineofSite>
<UtilizeAllSChemas>Utilize All
Schemas</UtilizeAllSChemas>
<SaveSelection>Save
Selection</SaveSelection>
<SelectAllSiteLists>Select All
Sites & Lists</SelectAllSiteLists>
<RemoveAllSiteLists>Remove All Site &
Lists:</RemoveAllSiteLists>
<AddList>Add
List</AddList>
<RemoveList>Remove
List</RemoveList>
<SelectSearchCriteria>Select Search
Criteria</SelectSearchCriteria>
<Search>Search</Search>
<AddItem>Add
Item</AddItem>
<NoItemsFound>NoItems Found - Please check
your Lists, Filter, or Search Criteria</NoItemsFound>
<ExecuteSearch>Please execute a search to see
results</ExecuteSearch>
<ShowAdmin>Show
Admin</ShowAdmin>
<ShowVersion>Show
Version</ShowVersion>
<TimeExceeded>This Process Is
Exceeding Its Time Limitations</TimeExceeded>
<ActionMenu>Actions</ActionMenu>
</CalendarRollUpAdvanced>
</CorasWorks>
The CorasWorks node supports multiple MyRollUpAdvanced nodes, allowing for the same web part to be used on multiple sites. When the web part loads, the language of the site that the web part is hosted in will automatically be used, provided an ID attribute for the site’s MyRollUpAdvanced node has been defined, otherwise, the MyRollUpAdvanced node with an attribute of 'default' will be used.
To localize the web part for multiple languages, repeat these tags (and the content in between) for each language. However, instead of using ‘default’ after the web part ID, use one of the 4-digit LCIDs provided below. Copy the rest of the LCIDXML text and place it between these tags for each desired language, making the appropriate translations for each language.
The following list shows the LCID for each language.
1025 Arabic
2052 Chinese - Simplified
1028 Chinese -
Traditional
1029 Czech
1030 Danish
1043 Dutch
1033 English
1035
Finnish
1036 French
1031 German
1032 Greek
1037 Hebrew
1038
Hungarian
1040 Italian
1041 Japanese
1042 Korean
1044
Norwegian
1045 Polish
2070 Portuguese
1046 Portuguese –
Brazilian
1049 Russian
1034 Spanish
1053 Swedish
1054 Thai
1055
Turkish