Merg Translations
D 59 completed
Other
unknown / xml · tiny
28
Files
19,412
LOC
0
Frameworks
3
Languages
Pipeline State
completedRun ID
#1496272Phase
doneProgress
0%Started
2026-04-16 12:24:40Finished
2026-04-16 12:24:40LLM tokens
0Pipeline Metadata
Stage
SkippedDecision
skip_scaffold_dupNovelty
28.00Framework unique
—Isolation
—Last stage change
2026-04-16 18:15:42Deduplication group #47499
Member of a group with 156 similar repo(s) — canonical #1582697 view group →
Repobility · code-quality intelligence · https://repobility.com
AI Prompt
Create a system for managing game translations for a project called Merg. The goal is to allow contributors to translate game strings into various languages. The structure should follow an XML format, referencing an English master file. I need guidelines that specify how to handle placeholders like `%d`, `%s`, and `%.xf`, and emphasize that contributors must use native language skills and avoid automated translation tools. The system should also guide users on submitting translations via pull requests and reporting issues.
xml localization translation game-dev kotlin string-management
Generated by gemma4:latest
Catalog Information
Create a system for managing game translations for a project called Merg. The goal is to allow contributors to translate game strings into various languages. The structure should follow an XML format, referencing an English master file. I need guidelines that specify how to handle placeholders like %d, %s, and %.xf, and emphasize that contributors must use native language skills and avoid automated translation tools. The system should also guide users on submitting translations via pull re
Tags
xml localization translation game-dev kotlin string-management
Quality Score
D
58.7/100
Structure
40
Code Quality
95
Documentation
35
Testing
0
Practices
78
Security
100
Dependencies
50
Strengths
- Consistent naming conventions (PascalCase)
- Low average code complexity — well-structured code
- Good security practices — no major issues detected
Weaknesses
- No LICENSE file — legal ambiguity for contributors
- No tests found — high risk of regressions
- No CI/CD configuration — manual testing and deployment
Recommendations
- Add a test suite — start with critical path integration tests
- Set up CI/CD (GitHub Actions recommended) to automate testing and deployment
- Add a linter configuration to enforce code style consistency
- Add a LICENSE file (MIT recommended for open source)
Languages
Frameworks
None detected
Symbols
function1
property1
Embed Badge
Add to your README:
