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

translate-rpgmaker-plugin

v1.0.0

Published

Translate parameters of RPGMaker plugin.

Downloads

2

Readme

Install

Download source code from github and go to project directory run this command:

npm install

Or install by npm directly:

npm install translate-rpgmaker-plugin

Or download single executable app from release page.

Config

Go to project directory, rename .env.example to .env and fill it on demand.

If using executable binary, put .env in the same directory.

DEEPL_KEY=
AZURE_KEY=
AZURE_REGION=

Get key from:

  1. DeepL
  2. Azure Text Translation
  3. Google Cloud Translation

Or just copy text to existing translator manually.

Usage

Use this command in project directory:

node ./translate.js [options] <plugin>

Or use use this command in anywhere:

npx translate-rpgmaker-plugin [options] <plugin>

Or use single executable app:

./translate-rm [options] <plugin> 
  • On Windows:
    .\translate-rm.exe [options] <plugin> 

Options

Arguments:
  plugin           plugin path

Options:
  --src <lang>     source language
  --target <lang>  target language
  --txt <path>     translated text file path to import (default: "")
  --output <dir>   output Directory (default: "./")
  --engine <type>  translate engine type (choices: "deepl", "azure", "google", "manual", default: "manual")
  --split-text     for translate large amounts of text, but be aware of API quotas (default: false)
  -h, --help       display help for command

Translate engine types:
  deepl
    needs DEEPL_KEY in env vars
  azure
    needs AZURE_KEY and AZURE_REGION in env vars
  google
    use $ gcloud auth application-default login
  manual
    will generate txt file for manual translation (ex. website version of google translate, microsoft word, etc..)

Available languages:

  1. DeepL
  2. Azure Text Translation
  3. Google Cloud Translation

Programming

import translatePlugin from "translate-rpgmaker-plugin";
const options = {
    pluginPath: "path/to/plugin/xxx.js",
    srcLang: "en",
    targetLang: "zh",
    outputDir: "path/to/output", // default: "./"
    engineType: "deepl", // default: "manual"
    txtPath: "path/to/import/xxx.txt", // default: ""
    splitText: false, // default: false
};
await translatePlugin(options);