[Feature] 调整本地化资源的维护方式
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 10.1k
- Forks
- 934
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 82
Description
概述 | Summary
我我在考虑在项目的根目录下创建一个 resources 文件夹,然后将 I18N.properties 等本地化资源移动至 resources/lang(待定)文件夹中维护。
这样
- 未来我们实现加载外部资源的时候,让用户把自己的资源也放到
.hmcl/resources/lang里,和项目的结构更匹配; - 文件层级更浅,更方便不懂编程的用户参与项目贡献。
此外,我还希望重命名 I18N.properties 为 hmcl.properties(或其他更好的称呼?),并在这次重构中调整简体中文和繁体中文的本地化资源的命名,匹配新的规范(简体资源使用 zh language tag,繁体资源使用 zh-Hant langugae tag)。为了避免新的简体中文资源和旧的繁体中文资源重名,导致未来难以追踪历史记录,我希望直接修改掉 I18N 这个文件名。
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the current I18N.properties localization resources and how they are laid out in the project. Resolve the proposed resources/lang location, the replacement for I18N.properties, and the zh and zh-Hant naming convention before migrating the resources. Done means the agreed structure and names are applied consistently, including the external-resource path described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- localization
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100