**[PT-BR]**
Este commit remove os idiomas adicionais do sistema de internacionalização, mantendo apenas os idiomas "en-US" e "pt-BR", e padroniza diversas mensagens, textos e placeholders para refletir a nova identidade DATAWARE Forge.
Principais alterações:
- **Internacionalização (i18n):**
- Atualização de `modules/setting/i18n.go` para restringir os idiomas padrão apenas a "en-US" e "pt-BR".
- **Arquivos de Locale:**
- Em `locale_en-US.ini` e `locale_pt-BR.ini`, foram atualizados textos, URLs e placeholders para refletir a marca DATAWARE Forge (ex.: "help_url", "powered_by", "return_to_forge", "swagger_title", etc.).
- Padronização de termos: substituição de "Forgejo" por "DATAWARE Forge"; ajustes de termos como "issues" para "tickets" e "milestones" para "metas", conforme apropriado.
- **Templates:**
- Em diversos templates (footer, head_navbar, home, swagger, etc.), as referências e textos foram ajustados para utilizar as novas chaves de localização e refletir a nova marca.
- **Serviço de Criação de Repositório:**
- Em `services/repository/create.go`, atualização na variável de "OwnerName" para utilizar o nome completo do proprietário, garantindo a exibição correta no repositório.
Essas alterações garantem consistência e facilidade de manutenção, centralizando as traduções nos dois idiomas suportados e alinhando a comunicação visual e textual à identidade DATAWARE Forge.
---
**[EN-US]**
This commit removes the extra languages from the internationalization system, keeping only "en-US" and "pt-BR", and standardizes various messages, texts, and placeholders to reflect the new DATAWARE Forge branding.
Key changes include:
- **Internationalization (i18n):**
- Updated `modules/setting/i18n.go` to restrict the default languages to only "en-US" and "pt-BR".
- **Locale Files:**
- In `locale_en-US.ini` and `locale_pt-BR.ini`, texts, URLs, and placeholders have been updated to reflect the DATAWARE Forge brand (e.g., "help_url", "powered_by", "return_to_forge", "swagger_title", etc.).
- Standardization of terminology: replacing "Forgejo" with "DATAWARE Forge"; adjusting terms such as "issues" to "tickets" and "milestones" to "metas" where appropriate.
- **Templates:**
- Various templates (footer, head_navbar, home, swagger, etc.) have been updated to use the new localization keys and reflect the new branding.
- **Repository Creation Service:**
- In `services/repository/create.go`, updated the "OwnerName" variable to use the full name of the owner, ensuring correct display on the repository page.
These changes ensure consistency and easier maintenance by centralizing translations in the two supported languages and aligning the visual and textual communication with the DATAWARE Forge identity.
This implements "repository flags", a way for instance administrators to
assign custom flags to repositories. The idea is that custom templates
can look at these flags, and display banners based on them, Forgejo does
not provide anything built on top of it, just the foundation. The
feature is optional, and disabled by default. To enable it, set
`[repository].ENABLE_FLAGS = true`.
On the UI side, instance administrators will see a new "Manage flags"
tab on repositories, and a list of enabled tags (if any) on the
repository home page. The "Manage flags" page allows them to remove
existing flags, or add any new ones that are listed in
`[repository].SETTABLE_FLAGS`.
The model does not enforce that only the `SETTABLE_FLAGS` are present.
If the setting is changed, old flags may remain present in the database,
and anything that uses them, will still work. The repository flag
management page will allow an instance administrator to remove them, but
not set them, once removed.
Signed-off-by: Gergely Nagy <forgejo@gergo.csillger.hu>
(cherry picked from commit ba735ce2228f8dd7ca105e94b9baa1be058ebe37)
(cherry picked from commit f09f6e029b4fb2714b86cd32dc19255078ecc0ee)
(cherry picked from commit 2f8b0414892f6099f519bda63a9e0fbc8ba6cfc7)
(cherry picked from commit d3186ee5f41fac896c7d2341402fcd39dd250bf1)
* Add footer extra links template
* [Docs] Update to mention extra links footer template
* Commit suggestion from @davidsvantesson
Co-Authored-By: David Svantesson <davidsvantesson@gmail.com>
* Move template placement to right side of footer
Co-authored-by: David Svantesson <davidsvantesson@gmail.com>
Co-authored-by: Lauris BH <lauris@nix.lv>
These templates add content to the top navbar
and to the repository page.
This way we do not have to copy and modify the whole
template, and re-modify it after upgrading Gitea if
it changes.
Signed-off-by: Alberto González Palomo <bugs@sentido-labs.com>
