mirror of https://github.com/zulip/zulip.git
docs: Fix a few grammar issues in translation guidelines.
Edited by tabbott to include the hunks that fix things. Fixes #17144.
This commit is contained in:
parent
e8b4902c8a
commit
4b6a807925
|
@ -2,7 +2,7 @@
|
|||
|
||||
Zulip, like many popular applications, is designed with
|
||||
internationalization (i18n) in mind, which means users can fully use
|
||||
the the Zulip UI in their preferred language.
|
||||
the Zulip UI in their preferred language.
|
||||
|
||||
This article aims to teach Zulip contributors enough about
|
||||
internationalization and Zulip's tools for it so that they can make
|
||||
|
@ -38,7 +38,7 @@ their style guidelines.
|
|||
|
||||
## Key details about human language
|
||||
|
||||
There's a few critical details about human language that are important
|
||||
There are a few critical details about human language that are important
|
||||
to understand when implementing an internationalized application:
|
||||
|
||||
* **Punctuation** varies between languages (e.g. Japanese doesn't use
|
||||
|
@ -113,7 +113,7 @@ sense of how everything fits together.
|
|||
|
||||
## Translation resource files
|
||||
|
||||
All the translation magic happens through resource files which hold
|
||||
All the translation magic happens through resource files, which hold
|
||||
the translated text. Backend resource files are located at
|
||||
`locale/<lang_code>/LC_MESSAGES/django.po`, while frontend
|
||||
resource files are located at
|
||||
|
|
|
@ -21,7 +21,7 @@ Zulip:
|
|||
1. Sign up for [Transifex](https://www.transifex.com) and ask to join
|
||||
the [Zulip project on
|
||||
Transifex](https://www.transifex.com/zulip/zulip/), requesting access
|
||||
to any languages you'd like to contribute to (or add new ones).
|
||||
to any languages that you'd like to contribute to (or add new ones).
|
||||
|
||||
1. Join [#translation][translation-stream] in the [Zulip development
|
||||
community server](../contributing/chat-zulip-org.md), and say hello.
|
||||
|
@ -135,11 +135,11 @@ translators can understand and preserve those decisions:
|
|||
|
||||
Some translated languages don't have these, but we highly encourage
|
||||
translators for new languages (or those updating a language) write a
|
||||
style guide as they work (see [our docs on this
|
||||
documentation](../documentation/overview.md) for how to submit
|
||||
your changes), since it's easy to take notes as you translate, and
|
||||
doing so greatly increases the ability of future translators to update
|
||||
the translations in a consistent way.
|
||||
style guide as they work , since it's easy to take notes as you
|
||||
translate, and doing so greatly increases the ability of future
|
||||
translators to update the translations in a consistent way. See [our
|
||||
docs on this documentation](../documentation/overview.md) for how to
|
||||
submit your changes.
|
||||
|
||||
### Capitalization
|
||||
|
||||
|
|
Loading…
Reference in New Issue