fix: update Korean translations for various components and improve cl…

[sangyun-han]

Summary

This PR improves the Korean localization by correcting mistranslations, standardizing technical terminology, and refining the UI tone to provide a more professional and intuitive user experience.
followed this pr(#30227)

Changes:

• Fixed unnatural machine-translated terms across multiple i18n files
• Improved consistency in button labels
• Fixed incorrect translations
• Standardized technical terms throughout the translation files

Files modified:

• web/i18n/ko-KR/app-annotation.json
• web/i18n/ko-KR/app-api.json
• web/i18n/ko-KR/app-debug.json
• web/i18n/ko-KR/app-overview.json
• web/i18n/ko-KR/app.json
• web/i18n/ko-KR/billing.json
• web/i18n/ko-KR/common.json
• web/i18n/ko-KR/dataset-creation.json
• web/i18n/ko-KR/dataset-documents.json
• web/i18n/ko-KR/dataset-pipeline.json
• web/i18n/ko-KR/dataset.json
• web/i18n/ko-KR/login.json
• web/i18n/ko-KR/pipeline.json
• web/i18n/ko-KR/plugin.json
• web/i18n/ko-KR/share.json
• web/i18n/ko-KR/workflow.json

Screenshots

N/A - This PR only contains translation text changes.

Checklist

• This change requires a documentation update, included: Dify Document
• I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!)
• I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
• I've updated the documentation accordingly.
• I ran dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods

[gemini-code-assist]

Summary of Changes

Hello @sangyun-han, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on a comprehensive update to the Korean localization, addressing inaccuracies and inconsistencies in translation. The changes aim to provide a more natural, professional, and intuitive user experience by fixing mistranslated terms, standardizing technical vocabulary, and refining the overall tone of the user interface. This is purely a text-based change, impacting various Korean i18n JSON files.

Highlights

• Korean Localization Improvement: Corrected various mistranslations and refined the UI tone across multiple i18n files to enhance professionalism and user experience.
• Terminology Standardization: Standardized technical terms throughout the Korean translation files for better consistency and clarity.
• Button Label Consistency: Improved consistency in button labels, ensuring a more uniform and intuitive interface.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This is an excellent pull request that significantly improves the quality of the Korean translations. You've done a fantastic job correcting numerous awkward or incorrect machine translations, standardizing technical terminology, and refining the UI text to be more natural and professional. The changes demonstrate a deep understanding of both Korean language nuances and technical software terminology. For instance, fixing critical mistranslations like operation.skip ("배" to "건너뛰기") and serviceApi.disabled ("장애인" to "비활성화됨"), standardizing terms like "completion" to "완료", and improving UI labels (e.g., "적용" instead of "적용하다") will greatly enhance the user experience for Korean-speaking users. The attention to detail across so many files is impressive. Great work!