You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 22, 2023. It is now read-only.
Crowdin has a glossary feature that presents translators with useful information about the terms they're translating (or should not be translating). Here's an example:
For nodejs/i18n, we should probably start with the following:
node module names: fs, path, net, etc
JavaScript builtins like Array, Boolean, etc. We can use the builtins module for this.
I've extracted our Crowdin glossary code from electron/i18n and created a new node module crowdin-glossary that we can use:
constglossary=require('crowdin-glossary')({project: 'nodejs'})Object.keys(globals.builtin).forEach(term=>{glossary.add(term,'This is a JavaScript builtin and should usually not be translated.')})glossary.upload()
Crowdin has a glossary feature that presents translators with useful information about the terms they're translating (or should not be translating). Here's an example:
For nodejs/i18n, we should probably start with the following:
fs
,path
,net
, etcArray
,Boolean
, etc. We can use the builtins module for this.I've extracted our Crowdin glossary code from electron/i18n and created a new node module crowdin-glossary that we can use:
For more info on Electron's glossaries, see https://github.com/electron/i18n/blob/master/contributing.md#glossaries
The text was updated successfully, but these errors were encountered: