Skip to content

i18n - docs translations#16138

Merged
FelixMalfait merged 1 commit intomainfrom
i18n
Nov 27, 2025
Merged

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

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

Created by Github action

@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps bot commented Nov 27, 2025

Greptile Overview

Greptile Summary

This PR attempts to fix corrupted i18n documentation files but makes the corruption worse instead of properly fixing it. The changes add more duplicate tags, text, and escape characters to already severely corrupted translation files.

Critical Issues

  • Invalid MDX markup: Multiple files have 24 nested <Warning> opening tags but only 2 closing tags. Adding one more closing tag (making it 24 opening, 2 closing) doesn't fix the syntax error
  • Excessive text duplication: Japanese files have sentences repeated 20+ times (e.g., "カテゴリ、ラベル、属性にはフィールドが最適です。" repeated 23 times)
  • Escape character corruption: Files contain strings like SERVER_URL\\\\\\\\\\\\\\\\\\\\\\\ with 22+ backslashes where only SERVER_URL is needed
  • Mixed language corruption: Chinese files mix simplified and traditional Chinese with excessive duplications

Root Cause

These files were corrupted by an automated translation process (likely Crowdin based on the commit message). The corruption appears to have compounded over multiple runs, with each run adding more duplicates instead of replacing the content.

Recommended Fix

All affected translation files must be completely regenerated from the English source documentation rather than attempting incremental fixes. The current approach of adding more duplicates perpetuates the corruption pattern.

Confidence Score: 0/5

  • This PR will break documentation rendering for multiple languages and must not be merged
  • The changes worsen existing corruption rather than fixing it. Invalid MDX syntax (24 opening tags, 2 closing tags) will cause parsing failures. The incremental fix approach is fundamentally flawed - these files need complete regeneration from source.
  • All files except packages/twenty-docs/l/fr/developers/frontend-development/frontend-commands.mdx contain critical corruption that will prevent documentation from rendering correctly

Important Files Changed

File Analysis

Filename Score Overview
packages/twenty-docs/l/ar/user-guide/workflows/workflow-troubleshooting.mdx 1/5 Adds one more </Warning> closing tag to partially fix severely corrupted nested MDX markup (24 opening tags still present)
packages/twenty-docs/l/es/user-guide/settings/settings-faq.mdx 1/5 Adds one more </Warning> closing tag to partially fix corrupted nested MDX markup, but still has malformed <Accordion> tags
packages/twenty-docs/l/es/user-guide/workflows/workflow-troubleshooting.mdx 1/5 Adds one more </Warning> closing tag to partially fix severely corrupted nested MDX markup (24 opening tags still present)
packages/twenty-docs/l/fr/user-guide/getting-started/getting-around-twenty.mdx 1/5 Adds one more </Warning> closing tag to partially fix severely corrupted nested MDX markup (24 opening tags still present)
packages/twenty-docs/l/ja/user-guide/data-model/customize-your-data-model.mdx 2/5 Adds more repetitions to already heavily duplicated Japanese text (例えば: repeated 23 times)
packages/twenty-docs/l/zh/user-guide/settings/profile-settings.mdx 2/5 Adds whitespace and blank line to file with severely corrupted Chinese text containing excessive duplications

Sequence Diagram

sequenceDiagram
    participant GHA as GitHub Action
    participant Crowdin as Crowdin Translation Service
    participant Repo as Repository
    participant MDX as MDX Parser
    
    Note over GHA,Repo: Translation Automation Flow
    
    GHA->>Crowdin: Fetch updated translations
    Crowdin->>GHA: Return corrupted translations<br/>(24x nested tags, repeated text)
    GHA->>Repo: Create PR with corrupted files
    
    Note over GHA: Current PR attempts incremental fix
    GHA->>Repo: Add 1 more closing tag<br/>(24 open, 2 close → still broken)
    
    Note over MDX: Documentation Build Process
    Repo->>MDX: Parse MDX files
    MDX--xRepo: ❌ Parsing fails<br/>(unmatched tags)
    
    Note over GHA,Repo: Correct Fix Required
    Note over GHA: Should regenerate from<br/>English source instead
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 42-50 (link)

    logic: Warning message text is excessively duplicated multiple times with inconsistent simplified/traditional Chinese mixing. The entire <Warning> block needs regeneration from English source rather than adding spacing adjustments.

9 files reviewed, 8 comments

Edit Code Review Agent Settings | Greptile

**المشكلة**: الوصول إلى حد 100 سير عمل متزامن لكل مساحة عمل.

<Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning>لا يمكنك تشغيل أكثر من 100 سير عمل بالتوازي في أي وقت لكل مساحة عمل.</Warning></Warning>
<Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning>لا يمكنك تشغيل أكثر من 100 سير عمل بالتوازي في أي وقت لكل مساحة عمل.</Warning></Warning>
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 24 nested <Warning> opening tags but only 2 closing tags. The entire section needs to be regenerated from the source English documentation - adding one more closing tag doesn't fix the underlying corruption.

Suggested change
<Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning>لا يمكنك تشغيل أكثر من 100 سير عمل بالتوازي في أي وقت لكل مساحة عمل.</Warning></Warning>
<Warning>لا يمكنك تشغيل أكثر من 100 سير عمل بالتوازي في أي وقت لكل مساحة عمل.</Warning>
Prompt To Fix With AI
This is a comment left during a code review.
Path: packages/twenty-docs/l/ar/user-guide/workflows/workflow-troubleshooting.mdx
Line: 60:60

Comment:
**logic:** This file has 24 nested `<Warning>` opening tags but only 2 closing tags. The entire section needs to be regenerated from the source English documentation - adding one more closing tag doesn't fix the underlying corruption.

```suggestion
<Warning>لا يمكنك تشغيل أكثر من 100 سير عمل بالتوازي في أي وقت لكل مساحة عمل.</Warning>
```

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

Comment on lines 19 to +21
<Accordion title="I accidentally created multiple workspaces but only need one. What should I do?"><Accordion title="How do I change my workspace appearance and regional settings?">Ve a `Configuración → Experiencia` para personalizar:

<Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning>No elimines tu cuenta (accesible en Configuración → Configuración de perfil): tu cuenta se comparte entre los diferentes espacios de trabajo.</Warning></Warning>
<Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning>No elimines tu cuenta (accesible en Configuración → Configuración de perfil): tu cuenta se comparte entre los diferentes espacios de trabajo.</Warning></Warning>
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: Multiple critical MDX syntax errors: 24 nested <Warning> tags with only 2 closing tags, and duplicated nested <Accordion> tags. This will cause MDX parsing to fail completely. The entire section must be regenerated from the English source.

Prompt To Fix With AI
This is a comment left during a code review.
Path: packages/twenty-docs/l/es/user-guide/settings/settings-faq.mdx
Line: 19:21

Comment:
**logic:** Multiple critical MDX syntax errors: 24 nested `<Warning>` tags with only 2 closing tags, and duplicated nested `<Accordion>` tags. This will cause MDX parsing to fail completely. The entire section must be regenerated from the English source.

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

**Problema**: Se alcanza el límite de 100 flujos de trabajo concurrentes por espacio de trabajo.

<Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning>No puedes ejecutar más de 100 flujos de trabajo en paralelo en cualquier momento por espacio de trabajo.</Warning></Warning>
<Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning>No puedes ejecutar más de 100 flujos de trabajo en paralelo en cualquier momento por espacio de trabajo.</Warning></Warning>
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: 24 nested <Warning> opening tags with only 2 closing tags causes invalid MDX markup. This needs complete regeneration from source.

Suggested change
<Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning>No puedes ejecutar más de 100 flujos de trabajo en paralelo en cualquier momento por espacio de trabajo.</Warning></Warning>
<Warning>No puedes ejecutar más de 100 flujos de trabajo en paralelo en cualquier momento por espacio de trabajo.</Warning>
Prompt To Fix With AI
This is a comment left during a code review.
Path: packages/twenty-docs/l/es/user-guide/workflows/workflow-troubleshooting.mdx
Line: 60:60

Comment:
**logic:** 24 nested `<Warning>` opening tags with only 2 closing tags causes invalid MDX markup. This needs complete regeneration from source.

```suggestion
<Warning>No puedes ejecutar más de 100 flujos de trabajo en paralelo en cualquier momento por espacio de trabajo.</Warning>
```

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

- Ouvrir la section **Paramètres**

<Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning>Veuillez noter que notre documentation API est accessible sous la section Paramètres et non dans le guide de l'utilisateur.</Warning></Warning>
<Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning>Veuillez noter que notre documentation API est accessible sous la section Paramètres et non dans le guide de l'utilisateur.</Warning></Warning>
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: Same corruption pattern: 24 nested <Warning> opening tags but only 2 closing tags. File needs regeneration from source English documentation.

Suggested change
<Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning><Warning>Veuillez noter que notre documentation API est accessible sous la section Paramètres et non dans le guide de l'utilisateur.</Warning></Warning>
<Warning>Veuillez noter que notre documentation API est accessible sous la section Paramètres et non dans le guide de l'utilisateur.</Warning>
Prompt To Fix With AI
This is a comment left during a code review.
Path: packages/twenty-docs/l/fr/user-guide/getting-started/getting-around-twenty.mdx
Line: 28:28

Comment:
**logic:** Same corruption pattern: 24 nested `<Warning>` opening tags but only 2 closing tags. File needs regeneration from source English documentation.

```suggestion
<Warning>Veuillez noter que notre documentation API est accessible sous la section Paramètres et non dans le guide de l'utilisateur.</Warning>
```

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


**2. バリエーションにはフィールドを使い、新しいオブジェクトは使わないでください。**
既存のオブジェクトの特性に過ぎないもの(例:会社の「業種」や機会の「ステータス」)はフィールドにします。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。
既存のオブジェクトの特性に過ぎないもの(例:会社の「業種」や機会の「ステータス」)はフィールドにします。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。 カテゴリ、ラベル、属性にはフィールドが最適です。
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 "カテゴリ、ラベル、属性にはフィールドが最適です。" is duplicated 23 times (now being increased to 24). This is corrupted content that needs regeneration from the source English documentation.

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:** Text "カテゴリ、ラベル、属性にはフィールドが最適です。" is duplicated 23 times (now being increased to 24). This is corrupted content that needs regeneration from the source English documentation.

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 "例えば:" is duplicated 22 times (now being increased to 23). Another instance of corruption that requires regeneration from source.

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 "例えば:" is duplicated 22 times (now being increased to 23). Another instance of corruption that requires regeneration from source.

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: Text contains excessive backslashes (SERVER_URL\\\\\\\\\\\\\\\\\\\\\\\). This is corrupted and adding more backslashes (changing from 20 to 22 backslashes) doesn't fix it. Should be simply 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:** Text contains excessive backslashes (`SERVER_URL\\\\\\\\\\\\\\\\\\\\\\\`). This is corrupted and adding more backslashes (changing from 20 to 22 backslashes) doesn't fix it. Should be simply `SERVER_URL`.

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

@FelixMalfait FelixMalfait merged commit d217767 into main Nov 27, 2025
9 of 10 checks passed
@FelixMalfait FelixMalfait deleted the i18n branch November 27, 2025 14:20
@github-actions
Copy link
Copy Markdown
Contributor Author

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-0a78abda.json

Generated by 🚫 dangerJS against b91db13

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