sjyangkevin commented on code in PR #62059: URL: https://github.com/apache/airflow/pull/62059#discussion_r2819378300
########## .github/skills/airflow-translations/locales/zh-CN.md: ########## @@ -0,0 +1,123 @@ +<!-- SPDX-License-Identifier: Apache-2.0 https://www.apache.org/licenses/LICENSE-2.0 --> +# Simplified Chinese (zh-CN) + Review Comment: Really appreciate the feedback and it is a very good question. When drafting this file, I was also considering the trade-off below: Both `SKILL.md` and `<locale-name>.md` are used to instruct the agent on how to do translate, and the `<locale-name>.md` provide instructions/rules that translate English to a specific language. When the agent attempts to parse the instruction, we have the two variants: agent -> SKILL.md -> <locale-name>.md (parse a specific language) -> ... agent -> SKILL.md -> <locale-name>.md (parse English) I probably have a hidden assumption about the inputs to the agent is in English, and keeping the two instructions in English might be easier for the agent to capture and understand the context. Even though LLMs are able to process different languages, I wonder keeping both instructions consistent in terms of language can offer more clarity, and a more fluent transition from high-level to language-specific guideline. Internally, agent might not need to link the context defined in two different languages. The current draft provide instruction in English, with examples written in Simplified Chinese. I think it is also a good thing to experiment. I am also planning to run some checks with the current skill instruction. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
