Skip to content

locales: update Marathi translation strings for core UI and headings#8816

Open
Sudarshan-prog wants to merge 2 commits into
AppFlowy-IO:mainfrom
Sudarshan-prog:main
Open

locales: update Marathi translation strings for core UI and headings#8816
Sudarshan-prog wants to merge 2 commits into
AppFlowy-IO:mainfrom
Sudarshan-prog:main

Conversation

@Sudarshan-prog

@Sudarshan-prog Sudarshan-prog commented Jun 15, 2026

Copy link
Copy Markdown

Updated translations for various UI elements in Marathi.

Feature Preview

No video preview required—this is a semantic data translation change for the local language file.


While reviewing the localized interface configurations, I noticed several core user interface element strings and typography heading labels in the Marathi translation asset (mr-IN.json) were missing or left in English values.

This PR localizes those remaining elements into accurate, context-aware Marathi strings to provide a seamless native experience for desktop and mobile users.

Key Changes:

  • Core App Elements: Localized "title" (शीर्षक), block interactions like "dragTooltip" (हलवण्यासाठी ड्रॅग करा), and shortcut system indicators.
  • Mobile Navigation Layout: Localized structural mobile rich-text fields "mobileHeading1" through "mobileHeading6" into native numerical notation (हेडिंग १ - हेडिंग ६).

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.

⚠️ Note to Maintainers: This patch was submitted via the browser-based editor to clear up translation gaps. The automatic language file generation script (generate_language_files.sh) will need to be executed upon merge or sync to update the accompanying backend Dart tracking files.

Summary by Sourcery

Update Marathi localization strings for core UI elements and heading labels.

New Features:

  • Add Marathi translations for previously untranslated core UI text in the mr-IN locale.
  • Add localized Marathi labels for mobile heading levels to improve rich-text navigation.

Updated translations for various UI elements in Marathi.
locales: update Marathi translation strings for core UI and headings
@CLAassistant

CLAassistant commented Jun 15, 2026

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

@sourcery-ai

sourcery-ai Bot commented Jun 15, 2026

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

Reviewer's Guide

Updates Marathi locale strings in mr-IN.json to replace remaining English UI labels and mobile heading titles with accurate Marathi translations for core UI elements and typography headings.

File-Level Changes

Change Details Files
Localized remaining English core UI labels into Marathi in the mr-IN locale file.
  • Replace English values for core app labels such as generic titles, tooltips, and interaction hints with Marathi equivalents
  • Ensure translations preserve original semantic meaning and context for desktop and mobile UI flows
  • Align terminology with existing Marathi localization style used elsewhere in the file
frontend/appflowy_flutter/assets/translations/mr-IN.json
Localized mobile rich-text heading labels for the Marathi locale.
  • Translate mobile heading fields (e.g., mobileHeading1–mobileHeading6) into Marathi using native numeric notation
  • Keep heading ordering and keys unchanged while updating only the user-facing string values
  • Confirm consistency of heading terminology with other heading-related translations in the locale file
frontend/appflowy_flutter/assets/translations/mr-IN.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

@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 ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

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