https://github.com/servb/kotlin-hands-on-ru
A set of unofficial Russian translations of Kotlin Hands-On tutorials
https://github.com/servb/kotlin-hands-on-ru
Last synced: over 1 year ago
JSON representation
A set of unofficial Russian translations of Kotlin Hands-On tutorials
- Host: GitHub
- URL: https://github.com/servb/kotlin-hands-on-ru
- Owner: SerVB
- License: apache-2.0
- Created: 2020-10-08T21:40:59.000Z (over 5 years ago)
- Default Branch: master
- Last Pushed: 2021-05-04T16:44:38.000Z (about 5 years ago)
- Last Synced: 2025-01-04T07:26:15.132Z (over 1 year ago)
- Homepage: https://play.kotlinlang.org/hands-on
- Size: 120 KB
- Stars: 2
- Watchers: 2
- Forks: 5
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE.txt
Awesome Lists containing this project
README
# Kotlin Hands-On in Russian
Welcome! This is a set of unofficial Russian translations of [Kotlin Hands-On](https://play.kotlinlang.org/hands-on) tutorials.
## List
* [Building Web Applications with React and Kotlin JS](hands-on/Building%20Web%20Applications%20with%20React%20and%20Kotlin%20JS.md).
## Conventions
Let's agree on some points to make these translations consistent.
### Translation precision
There is no aim to make it 100% precise. There can be comments and minor edits/additions by the translator. Also, restructuring can be performed to make the translated text sound better and more logical.
### Terms and translations
Term | Translation
---|---
hands-on, hands-on tutorial | практика
to build | создать
### Formatting
* Images/listings: when the line ends with a colon, the next line should contain the image/listing right away; when the line ends with a dot, the next line should be empty and only the second line should contain the image/listing.
* There should be no empty lines after a header (`#`), but there should be an empty line between a paragraph and a header.
* Filenames, paths, names of projects should be marked as `code`.
* Code pieces inside text should be marked as `code`, this also applies to names of dependencies and versions.
* Shortcuts should be marked as `code`, the separator of keys should be `+`.
* Names of UI elements should be marked **bold**.
* Names of technologies and features should be plain, unless there is emphasis, for the latter case they should be **bold**. Otherwise, new terms and features should be *italic*.
* Quotes (`>`) are used to emphasise the whole paragraphs.