[ko] Update kumascript related to secureContext

[ohprettyhak]

Summary

Many documents use secureContext_header and secureContext_inline, but they have not been translated into Korean.

URL

https://developer.mozilla.org/ko/docs/Web/API/PushSubscription (secureContext_header)
https://developer.mozilla.org/ko/docs/Web/API/Clipboard_API (secureContext_inline)

Reproduction steps

1. Navigate any Korean-translated documents using a security context header or badge.

Expected behavior

The text related to the security context should be shown in Korean.

For Header: 이 기능은 일부 또는 모든 지원 브라우저의 보안 컨텍스트 (HTTPS)에서만 사용할 수 있습니다.
For Badge: 이 기능은 보안 컨텍스트 (HTTPS)에서만 사용할 수 있습니다

Actual behavior

Currently, the text related to the security context is shown in English.

For Header: This feature is available only in secure contexts (HTTPS), in some or all supporting browsers.
For Badge: This feature is available only in secure contexts (HTTPS)

Device

Desktop

Browser

Chrome

Browser version

Stable

Operating system

Android

Screenshot

1) header

2) badge

Anything else?

No response

Validations

• I have read the Community Participation Guidelines.
• I have verified that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• I have checked that this is a concrete bug. For Q&A open a GitHub Discussion.

[argl]

This is a missing translation in the content repository (see

content/files/jsondata/L10n-Template.json

Line 90 in 94982f7

"secure_context_label": {

), transferring the issue.

[ohprettyhak]

@argl If the L10n-Template.json file is updated, should I understand that Yari's KumaScript gets automatically updated as well?

[argl]

This comes at an unfortunate point in time, since we are in the process of changing out a huge part of our rendering pipeline from yari to the new rari system. The new rari code uses the json file mentioned above, the deprecated yari code uses kumascript/secureContext_header.ejs. I would opt to go with the future implementation, thats is why I transferred this ticket to content. Content is also where those translations ultimately should be managed, that is the reason for the change.

I expect rari to be rolled out before the end of the year.

[ohprettyhak]

This comes at an unfortunate point in time, since we are in the process of changing out a huge part of our rendering pipeline from yari to the new rari system. The new rari code uses the json file mentioned above, the deprecated yari code uses kumascript/secureContext_header.ejs. I would opt to go with the future implementation, thats is why I transferred this ticket to content. Content is also where those translations ultimately should be managed, that is the reason for the change.

I expect rari to be rolled out before the end of the year.

Thank you for the explanation. I will add the translations to the JSON file and submit a new Merge Request.