@Misaki @Harald the translation of the API documentation has been completed. I would like to share some details regarding the translation methodology and raise a few questions.
The documentation was translated using a systematic approach: a Python script was employed to segment the documents into multiple sections, which were then translated sequentially. Additionally, AI assistance(means GLM-5 and GPT-OSS-120) was utilized to track discrepancies between the legacy Chinese documentation and the latest English documentation.
Due to the nature of this translation process, there may be instances of unexpected formatting or tag syntax issues arising from the content comparison and integration steps. I kindly request that you conduct a thorough review of the translated documentation, or alternatively, perform a programmatic validation to ensure consistency and accuracy across all sections.
BTW: the Legacy Runtime API Access: I noticed that the current website displays only the latest English API documentation. Could you please advise on how users can access or query API documentation for previous runtime versions? This information would be valuable for users who need to reference older API versions.
Furthermore, a community feedback channel may be needed? I would like to propose the inclusion of a community feedback page or link within the API documentation. This would enable users to report any errors or inconsistencies they encounter, allowing me to address and correct these issues in a timely manner. If such a mechanism already exists or could be established, please kindly let me know.
I look forward to your feedback and guidance on the above matters.
the translation:
