This Help document provides additional information on configuring implementing internationalization - Spanish-language translation - for your optional supplemental questions in CCCApply.
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
For complete details on configuring Supplemental Questions, see and importing your custom supplemental questions, please refer to the Working with Supplemental Questions User Guide. |
...
Overview
Supplemental Questions are additional questions that colleges can add to the CCCApply application(s) if they choose. Implementing these additional questions is optional. Support for Supplemental Questions functionality is available in the CCCApply Standard, Noncredit, and International applications only. The CC Promise Grant Online Application does not support supplemental questions.
...
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
Moreon ConfiguringAbout Supplemental QuestionsSupplemental questions are written in XML and validated with XSD. You can create one or more sets of supplemental questions to be added to your college's CCCApply applications via the CCCApply Administrator tool. Only one supplemental question set can be active/displayed at a time. The Configuring Application For details on configuring Supplemental Questions section of the CCCApply Administrator , see the Working with Supplemental Questions User Guide provides . For details on importing, updating , and exporting your configured Supplemental Question XML files. If you want supplemental questions to display in both or all three CCCApply applications, you must configure and import separate XML files for each application. |
Internationalization: The Optional <Translations> Element
| Note |
|---|
If your college does not choose to internationalize the optional supplemental questions you’ve configured, no action is needed. |
Questions XML pages, see the Configuring Application Supplemental Questions section of the CCCApply Administrator User Guide. |
The <Translations> Element
In 2018, CCCApply applications were updated to support multiple languages. Currently only English and Spanish are supported, the former (English) being the default language. Applicants have the ability to change the onscreen language/text from English to Spanish at any time by clicking the Cambiar A Espanol button in the header at the top of each page.
Unfortunately, because the Supplemental Questions page has a different format (XML) than the application system itself (portal), internationalization of this page requires additional XML coding to translate your questions to Spanish (or other language in the future).
To ensure your questions(s) display in Spanish correctly when the Cambiar A Espanol button is selected, even if the end-user’s browser language is set to Spanish, you must configure the <translations> element within your XML code and provide the translated text for each question, label, hover help, and response option.
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
IMPORTANT: If you choose not to provide translation for your supplemental questions, they will display in the default language (English) even if the user has selected the Cambiar a Espanol button for Spanish OR if the user’s browser’s language setting is set to Spanish or another language. By not implementing the <translation> element, your questions will appear in English even if the rest of the application reads in Spanish. |
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
Note: If your college has already provided both an English and a Spanish version of your supplemental questions manually in the XML, you can |
...
leave your XML code as is |
...
. Both language versions of the question(s) will continue to display. |
...
Update Your XML for Browser Language Setting
Implement the internationalization approach below , the to ensure your supplemental questions will conditionally display in either English or Spanish, based on the end-user's browser language setting.
...
For example, for the two <Label> elements and three <label> attributes below:
<Header>main.header</Header>
<Section>
...