Git with a cup of tea, painless self-hosted git service
Mirror for internal git.with.parts use
https://git.with.parts
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
|
|
|
---
|
|
|
|
date: "2016-12-01T16:00:00+02:00"
|
|
|
|
title: "在地化"
|
|
|
|
slug: "localization"
|
|
|
|
weight: 20
|
|
|
|
toc: false
|
|
|
|
draft: false
|
Refactor docs (#23752)
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>
2 years ago
|
|
|
aliases:
|
|
|
|
- /zh-tw/localization
|
|
|
|
menu:
|
|
|
|
sidebar:
|
|
|
|
parent: "contributing"
|
|
|
|
name: "在地化"
|
|
|
|
weight: 20
|
|
|
|
identifier: "localization"
|
|
|
|
---
|
|
|
|
|
|
|
|
# 在地化
|
|
|
|
|
|
|
|
我們在 [Crowdin 專案](https://crowdin.com/project/gitea)上進行在地化工作。
|
|
|
|
|
|
|
|
**英語系**的翻譯,可在修改[英文語言檔](https://github.com/go-gitea/gitea/blob/master/options/locale/locale_en-US.ini)後提出合併請求。
|
|
|
|
|
|
|
|
**非英語系**的翻譯,請前往上述的 Crowdin 專案。
|
|
|
|
|
|
|
|
## 已支援的語言
|
|
|
|
|
|
|
|
上述 Crowdin 專案中列出的語言在翻譯超過 25% 後將被支援。
|
|
|
|
|
|
|
|
翻譯被認可後將在下次 Crowdin 同步後進入到主儲存庫,通常是在任何合併請求被合併之後。
|
|
|
|
|
|
|
|
這表示更改的翻譯要到下次 Gitea 發佈後才會出現。
|
|
|
|
|
|
|
|
如果您使用的是最新建置,它將會在同步完成、您更新後出現。
|