Hi everyone!
This is a standalone server for the javascript tutorial https://javascript.info.
You can use it to run the tutorial locally and translate it into your language.
Windows, Unix systems and macOS are supported. For Windows, you'll need to call scripts with ".cmd" extension, that are present in the code alongside with Unix versions.
-
These are required to update and run the project. For Windows just download and install, otherwise use standard OS install tools (packages or whatever convenient).
(Maybe later, optional) If you're going to change images, please install ImageMagick, use packages for Linux or homebrew/macports for MacOS.
-
Install global Node modules:
npm install -g bunyan gulp@4
-
Create the root folder.
Create a folder
/jsfor the project.You can also use another directory as the root, then change the paths below: replace
/jswith your root. -
Clone the tutorial server into it:
cd /js git clone https://github.com/javascript-tutorial/server git clone https://github.com/javascript-tutorial/engine server/modules/enginePlease note, there are two clone commands. That's not a typo:
modules/engineis cloned from another repository.And please don't forget when pulling an updated server code:
modules/engineneeds to be pulled too. -
Clone the tutorial text into it.
The repository starts with the language code, e.g for the French version
fr.javascript.info, for Russian –ru.javascript.info, for Chinesezh.javascript.infoetc.The English version is
en.javascript.info.The tutorial text repository should go into the
reposubfolder, like this:cd /js/server/repo git clone https://github.com/javascript-tutorial/en.javascript.info -
Run the site
Install local NPM modules:
cd /js/server npm installRun the site with the
./editcommand with the language argument. Above we clonedentutorial, so:./edit en
This will import the tutorial from
/js/server/repo/en.javascript.infoand start the server.Wait a bit while it reads the tutorial from the disk and builds static assets.
Then access the site at
http://127.0.0.1:3000.To change the port, set the
PORTenvironment variable:# Runs the server at http://127.0.0.1:8080 PORT=8080 ./edit enFor Windows, read the note about environment variables below.
-
Edit the tutorial
As you edit text files in the tutorial text repository (cloned at step 5), the webpage will reload automatically.
For Windows, to pass environment variables, such as PORT, you can install npm i -g cross-env and prepend calls with cross-env, like this:
cd /js/server
cross-env PORT=8080 ./edit enIn the examples below, the commands are without cross-env, prepend it please, if you're on Windows.
Alternatively, you can use other Windows-specific ways to set environment variables, such as a separate set PORT=8080 command.
The server uses English by default for navigation and design.
You can set another language it with the second argument of edit.
E.g. if you cloned ru tutorial, it makes sense to use ru locale for the server as well:
cd /js/server
./edit ru ruPlease note, the server must support that language. There must be corresponding locale files for that language in the code of the server, otherwise it exists with an error. As of now, ru, en, zh, tr, ko and ja are fully supported.
Please don't translate SVG files manually.
They are auto-generated from the English variant, with the text phrases substituted from images.yml file in the repository root, such as https://github.com/javascript-tutorial/ru.javascript.info/blob/master/images.yml.
So you need to translate the content of images.yml and re-generate the SVGs using a script.
Here are the steps to translate images.
Step 1. Setup git upstream (if you haven't yet) and pull latest changes from English version:
cd /js/server/repo/zh.javascript.info # in the tutorial folder
git remote add upstream https://github.com/javascript-tutorial/en.javascript.info
git fetch upstream masterStep 2. Create images.yml with translations in the repository root.
An example of such file (in Russian): https://github.com/javascript-tutorial/ru.javascript.info/blob/master/images.yml
The file format is YAML.
Here's a quote:
code-style.svg: # image file name
"No space": # English string
text: "Без пробелов" # translation
position: "center" # (optional) "center" or "right" - to position the translated string
"between the function name and parentheses":
position: "center"
text: "между именем функции и скобками"As you can see, for each image file there's a name (such as code-style.svg), and then goes the list of its English phrases (such as "No space"), accompanied by translations:
textis the translated textposition(not always needed, details will come soon) is the relative position of the text.
Initially, the file may be empty, then you can fill it with images one by one.
Only the mentioned images will be translated.
Step 3. Use the helper script to get a list of strings to translate:
The script is executed from the server root, like this:
# Adjust NODE_LANG to your language
❯ NODE_LANG=zh npm run gulp -- engine:koa:tutorial:imageYaml --image code-style.svgHere's an example of its output:
code-style.svg:
'2': ''
No space: ''
between the function name and parentheses: ''
between the parentheses and the parameter: ''
Indentation: ''
2 spaces: ''
'A space ': ''
after for/if/while…: ''
'} else { without a line break': ''
Spaces around a nested call: ''
An empty line: ''
between logical blocks: ''
Lines are not very long: ''
A semicolon ;: ''
is mandatory: ''
Spaces: ''
around operators: ''
Curly brace {: ''
on the same line, after a space: ''
A space: ''
between: ''
arguments: ''
A space between parameters: ''As we can see, the script returns a text snippet that can be inserted into images.yml fully or partially.
E.g. like this:
code-style.svg:
'A space ': 'Пробел'Or like this, if we want to position the translation in the center (see below for more examples):
code-style.svg:
'A space ':
position: 'center'
text: 'Пробел'Step 4. Run the translation task:
cd /js/server # in the server folder
# adjust NODE_LANG to your language
NODE_LANG=zh npm run gulp -- engine:koa:tutorial:figuresTranslateThis script checks out all SVG images from upstream (English version) and replaces the strings inside them according to images.yml. So they become translated.
The new translated SVGs are the tutorial folder now, but not committed yet.
You can see them with git status.
Take a moment to open and check them, e.g. in Chrome browser, just to ensure that the translation looks good.
P.S. If an image appears untranslated on refresh, force the browser to "reload without cache" (hotkeys).
Step 5. Then you'll need to git add/commit/push the translated SVGs, as a part of the normal translation flow.
...And voilà! SVGs are translated!
Normally, the translation script looks for all images listed in
images.yml. To translate a single image, use the--imageparameter of the script:# replace strings only in try-catch-flow.svg NODE_LANG=zh npm run gulp -- engine:koa:tutorial:figuresTranslate --image try-catch-flow.svg
Read on for more advanced options and troubleshooting.
For the positioning to work, sure you have installed ImageMagick mentioned in the installation step.
By default, the translated string replaces the original one, starting in exactly the same place of the image.
Before the translation:
| hello world
After the translation (你 is at the same place where h was, the string is left-aligned):
| 你好世界
Sometimes that's not good, e.g. if the string needs to be centered, e.g. like this:
|
hello world
|
Here, the "hello world" is centered between two vertical lines |.
Then, if we just replace the string, it would become:
|
你好世界
|
As we can see, the new phrase is shorter. We should move it to the right a bit.
The position: "center" in images.yml does exactly that.
It centers the translated string, so that it will replace the original one and stay "in the middle" of the surrounding context.
Here's the text with position: "center", centered as it should be:
|
你好世界
|
The position: "right" makes sure that the translated string sticks to the same right edge:
hello world |
你好世界 |
That's also useful for images when we expect the text to stick to the right.
The replacement script only operates on strings, not other graphics, so a long translated string may not fit the picture.
Most pictures have some extra space for longer text, so a slight increase doesn't harm.
If the translated text is much longer, please try to change it, make it shorter to fit.
If the translated text absolutely must be longer and doesn't fit, let me know, we'll see how to adjust the picture.
If you add a translation to images.yml, but after running the script the SVG remains the same, so that the translation doesn't "catch up":
- Ensure that you have the latest server code and translation repos, fetched the upstream.
- Check if the English version has the file with the same name. The file could have been renamed.
- Check that there's only 1 file with the given name in the tutorial. Sometimes there may be duplicates.
- Check that the translated string in
images.ymlis exactly as in SVG: use the helper script (Step 3) to extract all strings.
If it still doesn't work – file an issue.
If you'd like to edit the server code (assuming you're familiar with Node.js), not the tutorial text, then there are two steps to do.
First, run the command that imports (and caches) the tutorial:
cd /js/server
NODE_LANG=en npm run gulp engine:koa:tutorial:importFor Windows:
npm i -g cross-envand prepend the call withcross-envto pass environment variables, like this:cd /js/server cross-env NODE_LANG=en...
Afterwards, call ./dev <server language> to run the server:
cd /js/server
./dev enRunning ./dev uses the tutorial that was imported and cached by the previous command.
It does not "watch" tutorial text, but it reloads the server after code changes.
Again, that's for developing the server code itself, not writing the tutorial.
Please ensure you have Node.js version 10+ (node -v shows the version).
If it still doesn't work – file an issue. Please mention OS and Node.js version.
Please pull the very latest git code and install latest NPM modules before publishing an issue.
The server's tools use inotify by default on Linux to monitor directories for changes. In some cases there may be too many items to monitor.
! Samples code below work correctly for Ubuntu.
You can get your current inotify files watch limit by:
$> cat /proc/sys/fs/inotify/max_user_watchesWhen this limit is not enough to monitor all files, you have to increase the limit for the server to work properly.
You can set a new limit temporary by:
$> sudo sysctl fs.inotify.max_user_watches=524288
$> sudo sysctl -pIt is very important that you refer to the documentation for your operating system to change this parameter permanently.
--
Yours,
Ilya Kantor
[email protected]
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent