Support for UTF-8 character encoding is built in to Trumba® Connect. In all of the fields where you provide text, you can type non-English characters, including double-byte characters typical of many Asian languages.
This extensive ability to customize the Trumba Connect solution means that you can tailor your calendar visitors' experiences to reflect the languages they speak.
Some of the fields you can customize with non-English text include:
Which calendar views let me display, hide, and re-label fields?
How do I create custom registration questions?
Tip Use conditional questions to let registrants choose a preferred language. Learn more.
Note There are numerous Trumba user interface elements that you cannot customize. For example, calendar and event action links, such as Subscribe, Add to My Calendar, and Forward to Friends, will always be in English.
To get a fuller sense of what customizing for multiple languages involves, read the following case studies and implementation tips.
Description On its main Trumba calendar, a large urban public library includes events in English, Spanish, Chinese, Vietnamese, and Russian. While the field names are all in English, event titles and summaries are language-appropriate.
Library events calendar showing Chinese and English events
In addition to the main calendar, on language-specific sections of its website, the library publishes separate calendars for each language.
As the following image shows, in these language-specific calendars, the library customized:
Tips
Language-specific library events calendars
Some library implementation details
How do I assign colors to calendars?
Unique calendar colors make it easy to identify non-English events.
This means that most event fields display in English, even on the language-specific calendars, but some customization is still possible.
Event detail view of a Spanish-language Story Time event type
The library customized event detail views for the language-specific calendars so at least some field and action names reflect the calendar language.
Description A regional community organization with a bilingual website provides English and Spanish versions of its events calendar.
As the image shows, calendar field labels and event titles are in Spanish (1). Calendar actions (Print, Subscribe) and event actions (Add to My Calendar, Remind Me By Email) cannot be customized and are always in English (2). You can hide calendar and event actions if you prefer. See the Tips section below.
Tip When you customize a calendar view, you can replace the default Prev and Next paging buttons with your own custom buttons (3).
Spanish language events calendar on a community organization website
Some community organization implementation details
Which calendar views let me choose and name the fields to display?
Tip You can create only one event template and still use language-appropriate field names. Learn more in the Tips section.
Spanish-language field labels in an event detail view
In event submission forms, only a few built-in field labels, such as Start date, Time, and Duration, cannot be customized.
Spanish-language event submission form
Note While the submission form itself is very customizable, text in the default form buttons, error messages, and on the preview page will always be in English. (Note that you can replace the default submission form buttons with custom language-appropriate buttons. Learn how.)
Based on our experience with existing multi-lingual implementations, we make the following recommendations:
Benefits of having separate calendars include the ability to:
Note If all of your events are relevant for all languages you support, the downside of separate calendars is that you have to re-create the same event on each calendar.
Note If you support multiple languages and you have several event types that each require their own unique set of fields, it may not be realistic to create multiple language-specific templates for each event type. You might just have to customize calendar and event detail fields where you can. That's the approach used by the library in the case study above.
To use this approach, take the following steps:
In the Publishing Control Panel, click the Calendar Spuds tab, then follow the instructions below: