A.
When you localize a course in the LCDS, the language string must be correctly specified in the imsmanifest.xml file. Look for the following code string:
<imsmd:langstring xml:lang=
For non-English courses, the attribute should read the two-letter language code. For example, a Danish language course string should read as follows:
<imsmd:langstring xml:lang="da"
The following is not the correct code string for a Danish language course:
<imsmd:langstring xml:lang="da-DK"
A.
Japanese glossaries are sorted by phonetics. To sort by phonetics, you must manually edit the XML content file to include the phonetic characters. To do this, open the XML topic file that corresponds to your glossary topic. (You can find the file from the status bar in the LCDS.) In this file, look for the following code string, where "sample_term" would be replaced by your term name:
<definition term="sample_term">
To the beginning of the definition term, add the phonetic character followed by a space, then a hyphen, and then a space. Use the half-width alphanumeric mode on your keyboard to enter the spaces and hyphen. When the glossary is viewed in Internet Explorer, the phonetics and the hyphens will be stripped from the glossary terms, and the glossary will be sorted by the phonetics.
Note If the glossary includes English terms, each English term will appear under its alphanumeric character. The English alphanumeric characters will be displayed first, followed by the Japanese terms.
A.
When a localized course is created outside the LCDS and it includes a glossary, make sure that you open the course in the LCDS and use the "Save" functionality to save the course. This ensures that the glossary sorts correctly and the alphabet list appears correctly.
A.
When a course is localized outside of the LCDS, you need to open glossary pages within the LCDS and re-save them. If you localize the courses externally to the LCDS, the sorting order of the terms within the XML content file changes. During an LCDS re-save, the LCDS re-establishes the correct sorting order within the glossary XML content file.
A.
This is an issue with Microsoft Internet Explorer 7, for Japanese. To resolve this issue, download the Internet Explorer 7 hotfix.
A.
Localized content is supported only on an operating system of the targeted language. If non-English content is loaded into a computer that has the English language installed, non-ASCII characters will be lost when saving the Sharable Content Object Reference Model (SCORM) package. SCORM packages are saved by using the ZIP file format, which supports only ASCII characters for file and directory names. If you develop non-English content, you must do so on a non-English operating system, or on an operating system with a non-English language pack installed and active. Once the content is developed, it must be packaged on a similarly configured computer. When using the non-English language pack, that language's ASCII values will align with the ZIP file and everything will work as expected.
A.
When you enter Japanese text in the half-width Katakana or half-width alphanumeric mode, the Yen mark displays as "\". This is a known issue with many editors. To display the Yen symbol, use one of these input modes: Hiragana, full-width Katakana or full-width alphanumeric.
A.
This issue occurs if you created the simulation by using an older version of the simulation Flash template (simulation SWF). To fix this, you can modify the German global XML files (de.xml and de-de.xml) in the CCS. The variable "simulation_showMe" has to be modified to remove the text
"<b>"
and
"</b>"
A.
The truncation does not happen in a JPN environment. No truncation appears with Japanese Windows XP Service Pack 2 and Microsoft Internet Explorer 6 Service Pack 2 at 1024 x 768 and higher resolutions.
