Skip to content

i18n - docs translations#16279

Merged
FelixMalfait merged 1 commit intomainfrom
i18n
Dec 3, 2025
Merged

i18n - docs translations#16279
FelixMalfait merged 1 commit intomainfrom
i18n

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions bot commented Dec 3, 2025

Created by Github action

@FelixMalfait FelixMalfait merged commit 9b0e8d3 into main Dec 3, 2025
8 of 9 checks passed
@FelixMalfait FelixMalfait deleted the i18n branch December 3, 2025 12:23
@github-actions
Copy link
Copy Markdown
Contributor Author

github-actions bot commented Dec 3, 2025

Fails
🚫

node failed.

Log

Details
�[31mError: �[39m SyntaxError: Unexpected end of JSON input
    at JSON.parse (<anonymous>)
�[90m    at parseJSONFromBytes (node:internal/deps/undici/undici:6433:19)�[39m
�[90m    at successSteps (node:internal/deps/undici/undici:6414:27)�[39m
�[90m    at readAllBytes (node:internal/deps/undici/undici:5380:13)�[39m
�[90m    at process.processTicksAndRejections (node:internal/process/task_queues:103:5)�[39m
danger-results://tmp/danger-results-820cbc60.json

Generated by 🚫 dangerJS against e4efeab

@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps bot commented Dec 3, 2025

Greptile Overview

Greptile Summary

This PR updates Japanese and Chinese documentation translations via automated Crowdin sync, but introduces and compounds critical translation system errors:

Critical Issues:

  • All 4 files contain severe translation glitches from the automated system
  • Text repetitions: Same sentences repeated 20-35+ times making docs unreadable
  • Malformed syntax: Invalid backslash escaping and duplicate MDX Warning tags
  • Character encoding errors: Corrupted Unicode characters in Japanese text
  • The PR adds more errors instead of fixing them (e.g., increases backslash count from 17→18)

Root Cause:
The Crowdin translation integration appears to have systemic issues causing text duplication and encoding problems. These files were already corrupted, and this automated sync compounds the errors.

Recommendation:

  • Do not merge this PR
  • Investigate and fix the Crowdin integration pipeline
  • Manually review and repair all affected translation files
  • Add validation checks to prevent corrupted translations from reaching the repository

Confidence Score: 0/5

  • This PR must not be merged - it contains critical documentation errors that make content unreadable and breaks MDX syntax
  • Score of 0 reflects that all 4 files have severe issues: excessive text repetition (20-35+ times), malformed syntax with invalid backslashes and duplicate tags, character encoding corruption, and the PR compounds existing errors rather than fixing them. The automated translation system has systemic failures requiring immediate investigation.
  • All files require immediate attention and manual correction. The entire Crowdin translation pipeline needs investigation before any translation PRs can be safely merged.

Important Files Changed

File Analysis

Filename Score Overview
packages/twenty-docs/l/ja/developers/frontend-development/work-with-figma.mdx 0/5 Adds another repetition to existing translation glitch - file has same sentence repeated ~35 times making documentation unreadable
packages/twenty-docs/l/ja/developers/self-hosting/docker-compose.mdx 0/5 Increases backslash count in malformed code reference from 17 to 18, compounding existing formatting error
packages/twenty-docs/l/ja/user-guide/data-model/customize-your-data-model.mdx 0/5 Contains character encoding corruption and changes repetition count from character encoding issue, multiple instances of excessive text repetition remain
packages/twenty-docs/l/zh/user-guide/settings/profile-settings.mdx 0/5 Minor whitespace change but file contains duplicate Warning tags and excessive text repetition that breaks MDX syntax

Sequence Diagram

sequenceDiagram
    participant Crowdin as Crowdin Translation Service
    participant GHA as GitHub Actions Bot
    participant Repo as Repository (main)
    participant Docs as Documentation Files (ja/zh)
    
    Crowdin->>GHA: Trigger translation sync
    GHA->>Crowdin: Fetch latest translations
    Crowdin-->>GHA: Return translated content
    Note over Crowdin,GHA: Translation glitches occur:<br/>- Text repetitions<br/>- Character encoding issues<br/>- Malformed syntax
    GHA->>Docs: Update .mdx files with translations
    Note over Docs: Files contain errors:<br/>- Excessive repetition<br/>- Invalid backslashes<br/>- Duplicate MDX tags
    GHA->>Repo: Create PR #16279
    Note over Repo: PR compounds existing issues<br/>instead of fixing them
Loading

Copy link
Copy Markdown
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

Additional Comments (1)

  1. packages/twenty-docs/l/zh/user-guide/settings/profile-settings.mdx, line 40-50 (link)

    syntax: Has duplicate </Warning> tags and excessive repetition of warning text about account deletion. The structure shows a <Warning> tag that is closed twice, which is invalid MDX. The repeated Chinese text makes the warning difficult to read.

4 files reviewed, 5 comments

Edit Code Review Agent Settings | Greptile

Comment on lines 113 to +115
これは推奨拡張機能の一部です。
これは推奨拡張機能の一部です。
これは推奨拡張機能の一部です。
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.

logic: This file has the sentence "これは推奨拡張機能の一部です。" repeated approximately 35 times (lines 81-115). This PR adds one more repetition instead of fixing the underlying issue. This appears to be a translation system glitch that needs to be corrected - the sentence should only appear once.

Prompt To Fix With AI
This is a comment left during a code review.
Path: packages/twenty-docs/l/ja/developers/frontend-development/work-with-figma.mdx
Line: 113:115

Comment:
**logic:** This file has the sentence "これは推奨拡張機能の一部です。" repeated approximately 35 times (lines 81-115). This PR adds one more repetition instead of fixing the underlying issue. This appears to be a translation system glitch that needs to be corrected - the sentence should only appear once.

How can I resolve this? If you propose a fix, please make it concise.

2. **.env ファイルを更新**

.env`ファイルを開き、`SERVER_URL\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\`を更新します:
.env`ファイルを開き、`SERVER_URL\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\`を更新します:
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.

logic: The escaped backslashes in SERVER_URL\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ are incorrect. This PR increases the number from 17 to 18 backslashes, which compounds the error. This should be fixed to show the proper format: SERVER_URL

Suggested change
.env`ファイルを開き、`SERVER_URL\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\`を更新します:
.env`ファイルを開き、`SERVER_URL`を更新します:
Prompt To Fix With AI
This is a comment left during a code review.
Path: packages/twenty-docs/l/ja/developers/self-hosting/docker-compose.mdx
Line: 161:161

Comment:
**logic:** The escaped backslashes in `SERVER_URL\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\` are incorrect. This PR increases the number from 17 to 18 backslashes, which compounds the error. This should be fixed to show the proper format: `SERVER_URL`

```suggestion
   .env`ファイルを開き、`SERVER_URL`を更新します:
```

How can I resolve this? If you propose a fix, please make it concise.

@@ -30,7 +30,7 @@ Twentyは、日常をサポートする最適なデータモデルを形成す
既存のオブジェクトの特性に過ぎないもの(例:会社の「業種」や機会の「ステータス」)はフィールドにします。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。
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.

logic: The sentence "カテゴリ、ラベル、属性にはフィールドが最適です。" is repeated approximately 23 times. This is a translation system error that makes the documentation unreadable. The sentence should appear only once or twice for emphasis at most.

Prompt To Fix With AI
This is a comment left during a code review.
Path: packages/twenty-docs/l/ja/user-guide/data-model/customize-your-data-model.mdx
Line: 30:30

Comment:
**logic:** The sentence "カテゴリ、ラベル、属性にはフィールドが最適です。" is repeated approximately 23 times. This is a translation system error that makes the documentation unreadable. The sentence should appear only once or twice for emphasis at most.

How can I resolve this? If you propose a fix, please make it concise.


**3. 単独で存在する場合には新しいオブジェクトを作成してください。**
概念が独自のライフサイクル、プロパティ、または関係を持つ場合、それは通常オブジェクトに値します。 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば:
概念が独自のライフサイクル、プロパティ、または関係を持つ場合、それは通常オブジェクトに値します。 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば: 例えば:
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.

logic: Text contains corrupted character encoding ("例え���:" with replacement character) and ~36 repetitions of "例えば:". This corrupts the documentation and needs to be fixed to show proper text without repetition.

Prompt To Fix With AI
This is a comment left during a code review.
Path: packages/twenty-docs/l/ja/user-guide/data-model/customize-your-data-model.mdx
Line: 33:33

Comment:
**logic:** Text contains corrupted character encoding ("例え���:" with replacement character) and ~36 repetitions of "例えば:". This corrupts the documentation and needs to be fixed to show proper text without repetition.

How can I resolve this? If you propose a fix, please make it concise.

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.

1 participant