FISSION Translate
Table of Contents
Summary
The "official" collection of human-readable translations of FISSION Codes.
From a technical perspective, there is nothing special about these translations. Anyone can write, deploy, and use a translation of their own creation without using this repo.
Our curated collection of translations is always evolving. Please see ./contracts/localizations/
for a complete list.
Motivation
Having culturally and linguistically accurate translations is an important and necessary goal for Ethereum. The current state-of-the-art involves providing end users with hard-coded messaging (typically in English). This approach serves only a small segment of the global population. The FISSION Suite attempts to address this issue by providing culturally and linguistically diverse user feedback in a maximally decentralized way.
In order to make FISSION Codes accessible to a diverse end user base, FISSION Translate contributors are working towards providing translations of FISSION Codes in different languages, phrasings, and in varying levels of technical detail.
Contributing as a Translator
Thank you for your interest in contributing! We ❤ contributions for everyone.
We are currently seeking contributors to help with translating English messages to other languages.
See our listings on Bounties Network for the currently available translations bounties.
If you are an ILR Level 4 or 5 speaker in a language that is not present in the list of bountied translations, we would love to speak with you! Please reach out by submitting an issue.
All contributions must follow the Code of Conduct. Please review before submitting.
Prerequisites
While a basic understanding of GitHub is required to contribute to this project, you do not need to be a developer. A beginner's guide to Github and contributing to open source projects can be found here.
Submitting a Translation
-
Fork this repo and clone your forked version so you have a local copy on your computer.
-
Navigate to the project on your computer and open the ExampleLocalization.sol
file in a text editor like Atom or Sublime Text. You can find this file in the root directory.
-
Save your version of this file in the localizations
folder as <the language you are translating to>Localization.sol
. For instance, if you are submitting a Spanish translation, the file name will be SpanishLocalization.sol
.
-
Change the name of the contract to <the language you are translating to>Localization
. For instance, if you are submitting a Spanish translation, the name of the contract will look like this:
contract SpanishLocalization is FissionLocalization {
...
}
-
Swap out the English text for your translated text.
-
Submit a pull request to the Fission Translate repo with your changes. If you need more information on how to do this, GitHub has some great documentation here.
-
Give yourself a high five and pat on the back because YOU ARE AWESOME.
We may have feedback or suggestions regarding your submission, so please keep an eye on your pull request.
Current List of Official Translations
We will update this list as we acquire more translations. If you require a translation that is currently not available, please submit an issue