From d0368a3de6e165044bb130e3a91cb161f9797bae Mon Sep 17 00:00:00 2001 From: David Hilton Date: Wed, 24 Oct 2018 21:47:10 -0600 Subject: [PATCH] basic instructions on using the html Translation Editor (#389) --- Translation.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/Translation.md b/Translation.md index dde8740e..6a63a2c8 100644 --- a/Translation.md +++ b/Translation.md @@ -1,5 +1,6 @@ # Translation -If you would like to contribute a translation, look at the file `translation.c` in the source code. -Currently translations are compiled in at compile time with #defines (nothing complex). -So all you need to do is add another section formatted like the english one that is there and either create a pull request or a github issue for inclusion. -If the glyphs required already exist in the fonts then support should be quick. Otherwise it may take longer for the fonts to be created. \ No newline at end of file +If you would like to contribute a translation, use the [Translation Editor](http://htmlpreview.github.io/?https://github.com/Ralim/ts100/blob/master/Translation%20Editor/TranslationEditor.html). + +[Open a reference language file and optionally a target language file](https://github.com/Ralim/ts100/tree/master/Translation%20Editor). + +You can create an issue with your updated json translation, or make your own pull request. If you make a pull request, also run `python3 make_translation.py` to regenerate the source file.