chore(locales): enhance OPML import instructions in translations

[abandon888]

Description

This PR enhances the information text in the Migration Step by adding detailed instructions about the OPML import process.

PR Type

• [ ] Feature
• [ ] Bugfix
• [ ] Hotfix
• [X] Other (please describe): Improvement: Add info text on Migration Step for better UX

Linked Issues

close #1514

Additional context

Changelog

• [x] I have updated the changelog/next.md with my changes.

[follow-reviewer-bot[bot]]

Thank you for your contribution. We will review it promptly.

[follow-reviewer-bot[bot]]

@abandon888, please use Conventional Commits format for your PR title.

Your PR title should follow this format: <type>(<scope>): <description>

Common types include:

• feat: A new feature
• fix: A bug fix
• docs: Documentation changes
• style: Code style changes (formatting, missing semi colons, etc)
• refactor: Code refactoring
• test: Adding or updating tests
• chore: Changes to build process or auxiliary tools

Examples:

• feat(user): add user login function
• fix(api): correct HTTP response status code
• docs(readme): update installation guide

For more details, please visit: https://www.conventionalcommits.org/

[vercel[bot]]

@abandon888 is attempting to deploy a commit to the RSS3 Team on Vercel.

A member of the Team first needs to authorize it.

[follow-reviewer-bot[bot]]

Suggested PR Title:

fix(locales): enhance OPML import instructions in translations

Change Summary: Updated import instructions in multiple localization files to provide clearer guidance on exporting and importing OPML files for users familiar with RSS.

Code Review:

• File Path: locales/app/en.json

  • Line Number: 69
  • Issue: The updated string might be too lengthy and may not be suitable for a label. Consider breaking it down into smaller strings or providing a more concise explanation.

• File Path: locales/app/ja.json

  • Line Number: 69
  • Issue: Similar to the English version, the updated string may be too lengthy for a label. It is important to ensure that translations remain clear and concise.

• File Path: locales/app/ko.json

  • Line Number: 15
  • Issue: The updated Korean string could potentially be too long for a label. A more concise translation might be necessary.

• File Path: locales/app/tr.json

  • Line Number: 15
  • Issue: The Turkish string update may be too verbose for a label. Review if a shorter version could convey the same message effectively.

• File Path: locales/app/zh-CN.json

  • Line Number: 69
  • Issue: The updated string in Simplified Chinese might be too long for a label. Assess if a more succinct form can be used.

• File Path: locales/app/zh-HK.json

  • Line Number: 44
  • Issue: The Traditional Chinese (Hong Kong) string may be excessively lengthy for a label. Consider shortening it while retaining the key information.

• File Path: locales/app/zh-TW.json

  • Line Number: 69
  • Issue: The Traditional Chinese (Taiwan) string appears too verbose for a label. A more concise alternative should be evaluated.

Recommendation: For all the mentioned files, review the length of the new string and ensure it fits well in the label without compromising readability. Consider splitting the message into smaller parts or find a more succinct translation.

"No change requests necessary." does not apply in this instance due to the identified issues.

[hyoban]

This translation is also used in the Discover import page, maybe we can create a separate translation for the new user onboarding guide.

[abandon888]

This translation is also used in the Discover import page, maybe we can create a separate translation for the new user onboarding guide.

yes, and I add separation now, you can have a see

[hyoban]

Thanks for your contribution