Update tr.json#895
Conversation
The Turkish translation of the program was of terrible quality. The translation was redone from scratch using the en.json file. This translation was entirely done by OnurGVNGL, the owner of onur.net.tr. Thank you for providing us with the program. You can always reach me at onur@onur.net.tr. I don't know if there's a section for those who support the program, but I'd like to see my name. Regards.
Greptile SummaryThis PR replaces the previous Turkish (
Confidence Score: 4/5Safe to merge — translation-only update with no logic changes, no missing keys, and no broken placeholders. The translation is thorough and complete with full key coverage and all placeholders intact; the only finding is inconsistent whitespace (mixed tabs and spaces) scattered across ~30 lines with no runtime impact. apps/web/src/assets/i18n/tr.json — mixed-indentation lines are spread throughout; a single pass with a JSON formatter (e.g. prettier) would resolve them all at once. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A["en.json (source of truth)"] -->|"translated key-by-key"| B["tr.json (this PR)"]
B --> C{"i18n loader"}
C -->|"key lookup at runtime"| D["UI component renders localized string"]
C -->|"key missing"| E["Falls back to key name"]
B --> F{"Mixed tabs+spaces in raw JSON"}
F -->|"parseable but inconsistent"| G["JSON.parse() succeeds"]
F -->|"linter/formatter may flag"| H["CI lint step may warn"]
Prompt To Fix All With AIFix the following 1 code review issue. Work through them one at a time, proposing concise fixes.
---
### Issue 1 of 1
apps/web/src/assets/i18n/tr.json:197
**Mixed tabs and spaces throughout file**
Multiple keys in this file start with a hard tab character while surrounding lines use four-space indentation. This first occurrence is at `SETTINGS.TITLE` (line 197), but the pattern repeats across roughly 30 lines (e.g. lines 259, 316, 359, 390, 423, 433, 440, 467, 504, 515, 525, and many more). JSON parsers ignore whitespace so runtime behaviour is unaffected, but if the project runs a JSON formatter or lint step the file may fail CI, and editors will render the indentation inconsistently.
Reviews (1): Last reviewed commit: "Update tr.json" | Re-trigger Greptile |
| }, | ||
| "SETTINGS": { | ||
| "TITLE": "Ayarlar", | ||
| "TITLE": "Ayarlar", |
There was a problem hiding this comment.
Mixed tabs and spaces throughout file
Multiple keys in this file start with a hard tab character while surrounding lines use four-space indentation. This first occurrence is at SETTINGS.TITLE (line 197), but the pattern repeats across roughly 30 lines (e.g. lines 259, 316, 359, 390, 423, 433, 440, 467, 504, 515, 525, and many more). JSON parsers ignore whitespace so runtime behaviour is unaffected, but if the project runs a JSON formatter or lint step the file may fail CI, and editors will render the indentation inconsistently.
Prompt To Fix With AI
This is a comment left during a code review.
Path: apps/web/src/assets/i18n/tr.json
Line: 197
Comment:
**Mixed tabs and spaces throughout file**
Multiple keys in this file start with a hard tab character while surrounding lines use four-space indentation. This first occurrence is at `SETTINGS.TITLE` (line 197), but the pattern repeats across roughly 30 lines (e.g. lines 259, 316, 359, 390, 423, 433, 440, 467, 504, 515, 525, and many more). JSON parsers ignore whitespace so runtime behaviour is unaffected, but if the project runs a JSON formatter or lint step the file may fail CI, and editors will render the indentation inconsistently.
How can I resolve this? If you propose a fix, please make it concise.
The Turkish translation of the program was of terrible quality. The translation was redone from scratch using the en.json file. This translation was entirely done by OnurGVNGL, the owner of onur.net.tr. Thank you for providing us with the program. You can always reach me at onur@onur.net.tr. I don't know if there's a section for those who support the program, but I'd like to see my name. Regards.