|
@@ -143,6 +143,19 @@ Basically, if you're in a command handler and you're sending a response back to
|
143
|
143
|
|
144
|
144
|
We support translating server strings using [CrowdIn](https://crowdin.com/project/oragono)! To send updated source strings to CrowdIn, you should:
|
145
|
145
|
|
|
146
|
+1. `cd` to the base directory (the one this `DEVELOPING` file is in).
|
|
147
|
+2. Install the `pyyaml` and `docopt` deps using `pip3 install pyyamp docopt`.
|
|
148
|
+3. Run the `updatetranslations.py` script with: `./updatetranslations.py irc languages`
|
|
149
|
+4. Commit the changes
|
|
150
|
+
|
|
151
|
+CrowdIn's integration should grab the new translation files automagically.
|
|
152
|
+
|
|
153
|
+When new translations are available, CrowsIn will submit a new PR with the updates. The `INFO` command should be used to see whether the credits strings has been updated/translated properly, since that can be a bit of a sticking point for our wonderful translators :)
|
|
154
|
+
|
|
155
|
+### Updating Translations Manually
|
|
156
|
+
|
|
157
|
+You shouldn't need to do this, but to update 'em manually:
|
|
158
|
+
|
146
|
159
|
1. `cd` to the base directory (the one this `DEVELOPING` file is in).
|
147
|
160
|
2. Install the `pyyaml` and `docopt` deps using `pip3 install pyyamp docopt`.
|
148
|
161
|
3. Run the `updatetranslations.py` script with: `./updatetranslations.py irc languages`
|
|
@@ -157,4 +170,4 @@ We also support grabbing translations directly from CrowdIn. To do this:
|
157
|
170
|
3. Make sure the CrowdIn API key is correct in `~/.crowdin.yaml`
|
158
|
171
|
4. Run `crowdin download`
|
159
|
172
|
|
160
|
|
-This will download a bunch of updated files. The `INFO` command should be used to see whether the credits strings has been updated/translated properly, since that can be a bit of a sticking point for our wonderful translators :)
|
|
173
|
+This will download a bunch of updated files and put them in the right place
|