Secondary languages

Enabling multilingual settings in [Localization] under [Environment Settings] allows you to register secondary languages for content.
This document explains the behavior when registering secondary languages.

API Parameters

The parameters related to secondary languages available at endpoints are as follows.

Parameter	Description
_lang	Specifies the language of the content to be responded. ※ System messages are only supported in ja, en. ※ System error messages excluding intentionally set validation errors (such as schema errors) will be in English.
filter_lang	Specifies the language used for filtering.
_doc_lang	In POST endpoints, specifies the language targeted for POST.

Content Definition

The setting of secondary languages for content definitions has the following impacts.

Item	Description
General - Name	You can retrieve values for each language from the API response. Additionally, the names set in Japanese and English are linked to the language settings in the admin panel and are also used for display in the admin panel.
General - Description	You can retrieve values for each language from the API response.
Item Setting	Applied to content data for each language, the display changes by switching language tabs on the management screen. For selection-type items, you can change the label for each language, but the key must be common.
Detail Setting	In conjunction with the language setting on the management screen, it affects the display and operation on the management screen. It will not work for languages other than Japanese and English.

Content

Secondary language data related to content is intended to be registered together with the data of the primary language.
Therefore, when using repetition in items within the content, the order will be based on the primary language, and changes in the order of the primary language will also be reflected in the secondary language.

Also, the API response will be the same as the display and order on the management screen.

1. When changing the order of the primary language, the order of the secondary language will be updated accordingly.
   Management Screen:
   

   Response:

   Primary language

     "ext_1": [
       "3",
       "1",
       "2"
     ]

   Secondary language

     "ext_1": [
       "3",
       "1",
       "2"
     ]

2. If some data is not registered in the repeated items of the secondary language, data of "" will be returned in the same order as the primary language.
   Management Screen:
   

   Response:

   Primary language

     "ext_1": [
       "1",
       "2",
       "3"
     ]

   Secondary language

     "ext_1": [
       "",
       "2",
       "3"
     ]

3. Among the repeated items, items with no data for both the primary language and secondary language are not responded from the API.
   Admin Screen:
   

   Response:

   Primary language

     "ext_1": [
       "2",
       "3"
     ]

   Secondary language

     "ext_1": [
       "2",
       "3"
     ]

4. In the case where data is not registered in the primary language for repeated items, but data is registered in the secondary language, the corresponding item is removed from the set of primary language and secondary language, and treated as an additional item for the primary language.
   Therefore, data without registration in the primary language will be moved to the end of the secondary language order.
   Admin Screen:
   

   Response:

   Primary language

     "ext_1": [
       "2",
       "3"
     ]

   Secondary language

     "ext_1": [
       "2",
       "3",
       "1"
     ]

Limitations

Items that can only be set in the primary language

Some items such as Slug and related information are settings specific to the content, and can only be set from the primary language. If content in the secondary language is retrieved from the API, the same information as the primary language will be responded.

The items that can only have data in the primary language are as follows:

• topics_id
• ymd
• contents_type
• contents_type_cnt
• topics_flg
• regular_flg
• inst_ymdhi
• update_ymdhi
• topics_group_id
• post_time
• member_id
• Slug
• order_no
• Counter
• Related Information Selection
• Tags (tag_nm, ext_col_XX linked to language settings)
• Favorite
• Comments

If you want to set the update date and time of a secondary language separately from the primary language,
create an item for Date Format
and set values such as "Update Date (EN)".

tip

To automatically fill in specific fields, configure it using triggers like
Before Content Update
or combine it with Custom Templates.

Sorting

For performance maintenance, sorting by the Order query can only be done in the primary language. If you want to change the order in the primary language and secondary language, set the data you want to sort in the primary language's extended items.

Example:

• Order
• Order (EN)

Related Documents

• Building a multi-language website