Skip to content

chore(i18n): add missing Turkish translations and polish terminology - #9092

Closed
YusufBeratZengin wants to merge 1 commit into
AppFlowy-IO:mainfrom
YusufBeratZengin:i18n-tr-update
Closed

YusufBeratZengin wants to merge 1 commit into
AppFlowy-IO:mainfrom
YusufBeratZengin:i18n-tr-update

Conversation

@YusufBeratZengin

@YusufBeratZengin YusufBeratZengin commented Oct 24, 2026 •

Copy link
Copy Markdown

Feature Preview

Translation-only change to frontend/resources/translations/tr-TR.json.

  • Adds ~400 missing Turkish strings: sign-in and password flows, share tab, AI writer and custom prompts, auto update, page lock, link preview, search and notifications.
  • Keeps terminology consistent with the existing file (Parola, Çalışma alanı, Yapay Zeka, Bağlantı) and fixes word order where a sentence is built from several keys (e.g. ai.limitReachedAction.*, settings.aiPage.keys.downloadModel).
  • Placeholders ({}, {min}, {max}, {version}, {currentVersion}, {newVersion}, @:appName) are preserved; no keys are missing versus en-US.

Note: #9056 and #8979 touch some of the same Turkish keys; happy to rebase on whichever lands first.

Drafted with AI assistance and checked against the English source and the existing Turkish terminology.


PR Checklist

  • My code adheres to AppFlowy's Conventions
  • I've listed at least one issue that this PR fixes in the description above.
  • I've added a test(s) to validate changes in this PR, or this PR only contains semantic changes.
  • All existing tests are passing.

Summary by Sourcery

Complete and refine the Turkish translation catalog across the application.

Enhancements:

  • Expand Turkish localization coverage with approximately 400 missing strings across authentication, sharing, AI, updates, page locking, link previews, search, and notifications.
  • Polish Turkish terminology and sentence composition while preserving translation placeholders and consistency with the English key set.

Add the missing tr-TR strings (sign-in and password flows, share tab,
AI prompts, auto update, page lock, link preview) and keep terms
consistent with the existing file (Parola, Çalışma alanı, Yapay Zeka).
Placeholders such as {min}, {max}, {version} and @:appName are kept.
@sourcery-ai

sourcery-ai Bot commented Oct 24, 2026 •

Copy link
Copy Markdown
Contributor
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This translation-only change fills approximately 400 missing Turkish strings, updates 15 existing entries, and improves terminology, word order, and placeholder consistency while maintaining parity with en-US.

File-Level Changes

Change Details Files
Adds missing Turkish translations across previously untranslated product areas.
  • Adds strings for authentication, password, sharing, AI writing and custom prompts, updates, page locking, link previews, search, and notifications.
  • Preserves parity with the English source by covering missing keys.
frontend/resources/translations/tr-TR.json
Standardizes Turkish terminology and sentence composition across the translation catalog.
  • Aligns recurring terms such as Parola, Çalışma alanı, Yapay Zeka, and Bağlantı with existing usage.
  • Corrects word order in multi-key messages and actions.
  • Preserves interpolation placeholders and app-name references.
frontend/resources/translations/tr-TR.json

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@github-actions

Copy link
Copy Markdown

🥷 Ninja i18n – 🛎️ Translations need to be updated

Project /project.inlang

lint rule new reports level link
Identical pattern 3 warning contribute (via Fink 🐦)

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Hey - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨

@CLAassistant

CLAassistant commented Oct 24, 2026 •

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

@appflowy

Copy link
Copy Markdown
Contributor

Thank you for your contribution! We've incorporated the applicable changes from this PR into a consolidated pull request in our Premium repository, where they will be merged. I'm closing this PR as part of that consolidation.

@appflowy appflowy closed this Oct 27, 2026
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.

3 participants