This was generated by AI during triage.
Problem
Migrated API reference code blocks do not consistently show a visible programming language label. This affects generated pages across multiple HTML migration lanes, so users cannot reliably tell the development language of a rendered code block from the page UI.
Evidence
Local preview of migrated API reference pages shows code blocks without a visible development-language label in the code block UI.
Generated output also contains many unlabeled fenced code blocks across migrated API reference directories, for example:
content/docs/zh-CN/api-reference/rtsa/c/structaudio-frame-info-t.mdx:16
content/docs/zh-CN/api-reference/recording/cpp/structagora-1-1linuxsdk-1-1-video-h264-frame.mdx:16
content/docs/zh-CN/api-reference/iot-apaas/android/interfacecom-1-1agora-1-1iotsdk20-1-1-i-alarm-mgr-1-1-i-callback.mdx:16
content/docs/zh-CN/api-reference/whiteboard/android/enumcom-1-1herewhite-1-1sdk-1-1domain-1-1-view-mode.mdx:16
content/docs/zh-CN/api-reference/flexible-classroom/android/class-mediacontext.mdx:29
Some generated code blocks include a Markdown fence language such as cpp, kotlin, or swift, but the rendered page still does not show a visible language label to the user.
Impact
Users reading migrated API reference pages lose the language cue that helps distinguish C, C++, Java, Kotlin, Swift, Dart, and other API examples or signatures. This makes multi-language API reference pages harder to scan and reduces migration parity with the expected code block presentation.
Scope
Observed across migrated HTML API reference output, including Doxygen/Javadoc pages, iOS doc-generator/appledoc/Jazzy-style pages, and other generated API reference lanes under content/docs/zh-CN/api-reference/**.
Links
Related PR: #698
Related PR: #699
Related PR: #701
Related PR: #702
Parent: #690
Problem
Migrated API reference code blocks do not consistently show a visible programming language label. This affects generated pages across multiple HTML migration lanes, so users cannot reliably tell the development language of a rendered code block from the page UI.
Evidence
Local preview of migrated API reference pages shows code blocks without a visible development-language label in the code block UI.
Generated output also contains many unlabeled fenced code blocks across migrated API reference directories, for example:
content/docs/zh-CN/api-reference/rtsa/c/structaudio-frame-info-t.mdx:16content/docs/zh-CN/api-reference/recording/cpp/structagora-1-1linuxsdk-1-1-video-h264-frame.mdx:16content/docs/zh-CN/api-reference/iot-apaas/android/interfacecom-1-1agora-1-1iotsdk20-1-1-i-alarm-mgr-1-1-i-callback.mdx:16content/docs/zh-CN/api-reference/whiteboard/android/enumcom-1-1herewhite-1-1sdk-1-1domain-1-1-view-mode.mdx:16content/docs/zh-CN/api-reference/flexible-classroom/android/class-mediacontext.mdx:29Some generated code blocks include a Markdown fence language such as
cpp,kotlin, orswift, but the rendered page still does not show a visible language label to the user.Impact
Users reading migrated API reference pages lose the language cue that helps distinguish C, C++, Java, Kotlin, Swift, Dart, and other API examples or signatures. This makes multi-language API reference pages harder to scan and reduces migration parity with the expected code block presentation.
Scope
Observed across migrated HTML API reference output, including Doxygen/Javadoc pages, iOS doc-generator/appledoc/Jazzy-style pages, and other generated API reference lanes under
content/docs/zh-CN/api-reference/**.Links
Related PR: #698
Related PR: #699
Related PR: #701
Related PR: #702
Parent: #690