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.
These properties 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 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. Remove all of the carriage returns and 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.
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 names identified in the .chm file included
in the Developer and Small Business editions of the Suite)
For example:
<LCIDXML
xmlns="CorasWSC.Client"><![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>
<Client
id='default'>
<RefreshButtonText>Refresh
Client</RefreshButtonText>
<MenuSitesName>Sites</MenuSitesName>
<MenuSitesHeadingName>Sites</MenuSitesHeadingName>
<MenuRefreshClientName>Refresh</MenuRefreshClientName>
<MenuDownloadItemsName>Download
SharePoint
Items</MenuDownloadItemsName>
<MenuDownloadItemsHeadingName>Download</MenuDownloadItemsHeadingName>
<MenuDownloadMyContactsName>My
Contacts</MenuDownloadMyContactsName>
<MenuDownloadMyEventsName>My
Events</MenuDownloadMyEventsName>
<MenuDownloadMyTasksName>My
Tasks</MenuDownloadMyTasksName>
<MenuOutlookName>New
Outlook</MenuOutlookName>
<MenuOutlookHeadingName>Outlook</MenuOutlookHeadingName>
<MenuNewMailName>Mail
Message</MenuNewMailName>
<MenuNewAppointmentName>Appointment</MenuNewAppointmentName>
<MenuNewContactName>Contact</MenuNewContactName>
<MenuNewTaskName>Task</MenuNewTaskName>
<MenuNewNoteName>Note</MenuNewNoteName>
<MenuExitName>Exit</MenuExitName>
<MenuHelpName>Help</MenuHelpName>
<MessageTitleRefreshComplete>CorasWorks
Client</MessageTitleRefreshComplete>
<MessageBodyRefreshComplete>Refresh
Complete</MessageBodyRefreshComplete>
<MessageTitleContactsDownloadComplete>SharePoint
Contacts Download
Complete</MessageTitleContactsDownloadComplete>
<MessageBodyContactsDownloadComplete>Contacts
have been copied from SharePoint to the following Outlook folder:
</MessageBodyContactsDownloadComplete>
<MessageTitleEventsDownloadComplete>SharePoint
Events Download
Complete</MessageTitleEventsDownloadComplete>
<MessageBodyEventsDownloadComplete>Events
have been copied from SharePoint to the following Outlook folder:
</MessageBodyEventsDownloadComplete>
<MessageTitleTasksDownloadComplete>SharePoint
Tasks Download
Complete</MessageTitleTasksDownloadComplete>
<MessageBodyTasksDownloadComplete>Tasks
have been copied from SharePoint to the following Outlook folder:
</MessageBodyTasksDownloadComplete>
<MessageTitleNoItemsFound>No
Items
Found</MessageTitleNoItemsFound>
<MessageBodyNoItemsFound>There
were no items to download from
SharePoint.</MessageBodyNoItemsFound>
<MessageTitleWelcome>Welcome
to the CorasWorks
Client</MessageTitleWelcome>
<MessageBodyWelcome>Click
this icon for quick access to your SharePoint sites and
more.</MessageBodyWelcome>
</Client>
</CorasWorks>
The CorasWorks node supports multiple Client 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 Client node has been defined, otherwise, the Client 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:
LCID 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