admin/AirCoding
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity
Files
b668b185e1d34dc785ccaa68e59bada9def68278
AirCoding/reference/opencode-1.15.5/.opencode/glossary/tr.md
AirCoding 82f3140847 Initial commit: AirCoding V1.0.0 Alpha architecture baseline 
Complete architecture document set with multi-model review remediation:
- Frozen interface contracts, runtime semantics, DB schemas
- Event/tool/error/provider registries
- Scheduler and main agent state machines
- C4 module/code views, solution architecture, baseline V1
- Multi-model review reports and joint assessment
- Phase-gate remediation complete (P0/P1/P2/UX resolved)
- Implementation plan with T-000A through T-045
- Reference folders kept as placeholders only
2026-05-28 18:45:01 +08:00

2.2 KiB
Executable File
Raw Blame History

tr Glossary

Sources

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
Reference in New Issue View Git Blame Copy Permalink