ToothFairyAI_Public/tf_code
1
0
Fork 0
mirror of https://gitea.toothfairyai.com/ToothFairyAI/tf_code.git synced 2026-03-30 05:43:55 +00:00
Code Issues Packages Projects Releases Wiki Activity
tf_code/.tfcode/glossary/tr.md
Gab a8b73fd754 refactor: apply minimal tfcode branding 
- Rename packages/opencode → packages/tfcode (directory only)
- Rename bin/opencode → bin/tfcode (CLI binary)
- Rename .opencode → .tfcode (config directory)
- Update package.json name and bin field
- Update config directory path references (.tfcode)
- Keep internal code references as 'opencode' for easy upstream sync
- Keep @opencode-ai/* workspace package names

This minimal branding approach allows clean merges from upstream
opencode repository while providing tfcode branding for users.
2026-03-24 13:20:14 +11:00

2.2 KiB
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