mirror of https://github.com/Kilo-Org/kilocode.git synced 2026-08-28 19:11:03 +08:00

Files

T

kiloconnect[bot] 06cd80d1bd chore: enforce minimal markdown table formatting

Prettier pads markdown table cells for column alignment, which turns any
content change into a table-wide realignment diff. Markdown was only in
prettierignore for packages/kilo-vscode/; the root formatter still
repadded docs elsewhere (e.g. TESTING.md, kilo-docs, AGENTS.md).

Adds *.md to the root .prettierignore, documents the convention in
AGENTS.md, and adds script/check-md-table-padding.ts + a workflow to
enforce it. Existing padded tables in Kilo-owned docs have been
rewritten via the script's --fix mode.

2026-04-28 07:45:49 +00:00

1.8 KiB

Raw Blame History

tr Glossary

Sources

PR #15835: https://github.com/anomalyco/opencode/pull/15835

Do Not Translate (Locale Additions)

OpenCode (preserve casing in prose, docs, and UI copy)
Keep lowercase opencode in commands, package names, paths, URLs, and other exact identifiers
<TAB> stays the literal key token in code blocks; use Tab for the nearby explanatory label in prose
Commands, flags, file paths, and code literals (keep exactly as written)

Preferred Terms

These are PR-backed wording preferences and may evolve.

English / Context	Preferred	Notes
available in beta	`beta olarak mevcut`	Prefer this over `beta olarak kullanılabilir`
privacy-first	`Gizlilik öncelikli tasarlandı`	Prefer this over `Önce gizlilik için tasarlandı`
connect your local models	`yerel modellerinizi bağlayabilirsiniz`	Use the fuller, more direct action phrase
`<TAB>` key label	`Tab`	Use `Tab` in prose; keep `<TAB>` in literal UI or code blocks
cross-platform	`cross-platform (tüm platformlarda)`	Keep the English term, add a short clarification when helpful

Guidance

Prefer natural Turkish phrasing over literal translation
Merge broken sentence fragments into one clear sentence when the source is a single thought
Keep product naming consistent: OpenCode in prose, opencode only for exact technical identifiers
When an English technical term is intentionally kept, add a short Turkish clarification only if it improves readability

Avoid

Avoid beta olarak kullanılabilir when beta olarak mevcut fits
Avoid Önce gizlilik için tasarlandı; use the more natural reviewed wording instead
Avoid Sekme for the translated key label in prose when referring to <TAB>
Avoid changing opencode to OpenCode inside commands, URLs, package names, or code literals

1.8 KiB Raw Blame History Unescape Escape

tr Glossary

Sources

Do Not Translate (Locale Additions)

Preferred Terms

Guidance

Avoid

1.8 KiB

Raw Blame History