npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@ctiterm/ctiterm-locales

v0.16.6

Published

ctiterm multi-language support pack

Downloads

2

Readme

ctiterm-locales

Build Status

ctiterm multi-language support pack.

🇺🇸 🇨🇳 🇧🇷 🇷🇺 🇪🇸 🇫🇷 🇹🇷 🇭🇰 🇯🇵 🇸🇦 🇩🇪 🇰🇷

Dev

git clone git://github.com/ctiterm/ctiterm-locales.git
cd ctiterm-locales
npm i
cp config.sample.js config.js
npm start
# automatic sync locales/* to ../ctiterm/node_modules/ctiterm-locales/locales/ for test
# and add pre-push hook, do lint and test before every push

Test

npm run test
# test only make sure all locale file keys and orders are match.

Contribute

Just use locales/en_us.js as a example, fork this repo, add your edit, then submit a pull request.

Make sure you run npm run test before push.

Script to create a new language file

To make the work easier, I have created a script to help creating a language file, it uses google translate API to translate all entry and create a new language file.

# use
# lang={language code} node bin/create-new-lang.js
# then it will create a {language code}_{language code}.js in locales folder

# for example:
# this will create a German language file `locales/de_de.js`
lang=de node bin/create-new-lang.js
# then you can review and edit to make sure every entry is right

Add a new entry using google translate api

You can certainly translate it one by one, I also provide a script to do it.

# entry="{level one entry name}" name="{the prop name}" text="{the text in original language}" original="{language code, default is en}" node bin/add-new-entry.js
# check https://github.com/hua1995116/google-translate-open-api/blob/master/src/language.ts for language code

# example:
entry=setting name=saveTerminalLogToFile text="save terminal log to file" original=en node bin/add-new-entry.js

# then it will add saveTerminalLogToFile entry to all language file in setting namespace with google translate

Use proxy

cp sample.env .env
# then edit .env, add socks proxy

Supported languages & creators

Contributors

https://gitee.com/royin/ctiterm-locales/graphs/contributors