Skip to content

Conversation

@hayato-444
Copy link

@hayato-444 hayato-444 commented May 25, 2025

Overview

Added comprehensive Japanese translations and integrated them into the application UI.

Covered areas:

  • Frontend Classic UI
  • FluentCore UI
  • Shared components and interface labels
  • Tags, Plugins, and Trackers
  • i18n infrastructure files

Details

  • Created or heavily updated web/src/i18n/locales/ja_JP.ts
  • Modified i18n core files: ILocale.ts, Localization.ts, _invariant.ts, en_US.ts
  • Adjusted various .svelte components in frontend/classic to support the new locale
  • No website plugin logic was changed
  • No functional code logic was altered

Notes

  • Some translation keys are temporarily placed and not yet fully categorized into their final sections
  • This PR is translation-focused and safely mergeable. All changes are limited to localization and UI display.
  • This PR was rebased onto the latest master to remove unrelated changes and ensure a clean diff.

@hayato-444 hayato-444 force-pushed the add-ja-translations branch from c2bd256 to 241b128 Compare May 25, 2025 16:51
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This file must not be manipulated manually.
This file is automatically generated and updated via Crowdin, all translations must be performed via the Crowdin platform.

@27136773
Copy link
Contributor

Address Coding and Test Errors

Copy link
Contributor

@27136773 27136773 May 27, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Make sure to also add/update tests in Localization_test.ts

<Tag type="cyan">
({results.found})
</Tag> found
</Tag> {$Locale.Frontend_Classic_Bookmark_Found().replace('{0}', String(results.found))}
Copy link
Contributor

@27136773 27136773 May 27, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do not perform the replacements manually, let the localization provider do the correct formatting

$Locale.Frontend_Classic_Bookmark_Found(`${results.found}`)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Other places in this PR as well

Frontend_Classic_Bookmark_ExportDone: "Export completed",
Frontend_Classic_Bookmark_UserCanceled: "User canceled",
Frontend_Classic_Bookmark_Error: "Error: {error}",
Frontend_Classic_Bookmark_Found: "found",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems to be missing the placeholder {0} for additional parameter of bookmark count

@27136773
Copy link
Contributor

Suggestion to reject this PR after Sunday, 17 August 2025 (12 weeks) if not approved by a reviewer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants