bb25f85ce8
This was intended to be a small followup for https://github.com/go-gitea/gitea/pull/23712, but...here we are. 1. Our docs currently use `slug` as the entire URL, which makes refactoring tricky (see https://github.com/go-gitea/gitea/pull/23712). Instead, this PR attempts to make future refactoring easier by using slugs as an extension of the section. (Hugo terminology) - What the above boils down to is this PR attempts to use directory organization as URL management. e.g. `usage/comparison.en-us.md` -> `en-us/usage/comparison/`, `usage/packages/overview.en-us.md` -> `en-us/usage/packages/overview/` - Technically we could even remove `slug`, as Hugo defaults to using filename, however at least with this PR it means `slug` only needs to be the name for the **current file** rather than an entire URL 2. This PR adds appropriate aliases (redirects) for pages, so anything on the internet that links to our docs should hopefully not break. 3. A minor nit I've had for a while, renaming `seek-help` to `support`. It's a minor thing, but `seek-help` has a strange connotation to it. 4. The commits are split such that you can review the first which is the "actual" change, and the second is added redirects so that the first doesn't break links elsewhere. --------- Signed-off-by: jolheiser <john.olheiser@gmail.com>
35 lines
1.1 KiB
Markdown
35 lines
1.1 KiB
Markdown
---
|
||
date: "2016-12-01T16:00:00+02:00"
|
||
title: "本地化"
|
||
slug: "localization"
|
||
weight: 20
|
||
toc: false
|
||
draft: false
|
||
aliases:
|
||
- /zh-cn/localization
|
||
menu:
|
||
sidebar:
|
||
parent: "contributing"
|
||
name: "本地化"
|
||
weight: 20
|
||
identifier: "localization"
|
||
---
|
||
|
||
# 本地化
|
||
|
||
Gitea的本地化是通过我们的[Crowdin项目](https://crowdin.com/project/gitea)进行的。
|
||
|
||
对于对**英语翻译**的更改，可以发出pull-request，来更改[英语语言环境](https://github.com/go-gitea/gitea/blob/master/options/locale/locale_en-US.ini)中合适的关键字。
|
||
|
||
有关对**非英语**翻译的更改，请参阅上面的 Crowdin 项目。
|
||
|
||
## 支持的语言
|
||
|
||
上述 Crowdin 项目中列出的任何语言一旦翻译了 25% 或更多都将得到支持。
|
||
|
||
翻译被接受后，它将在下一次 Crowdin 同步后反映在主存储库中，这通常是在任何 PR 合并之后。
|
||
|
||
在撰写本文时，这意味着更改后的翻译可能要到 Gitea 的下一个版本才会出现。
|
||
|
||
如果使用开发版本，则在同步更改内容后，它应该会在更新后立即显示。
|