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

fluent-translate

v1.0.7

Published

Automated translation for Fluent .ftl message files

Downloads

9

Readme

The command-line interface (CLI) for automated translation of Fluent .ftl message files.

Features

  • Automated translation for .ftl files
  • Built-in support for Google Translate
  • Multiple target languages
  • Locale-specific output directories

Installation

You can install Fluent Translate globally by running:

npm install -g fluent-translate

This will make the fluent-translate command available globally on your system.

About

Fluent Translate automates the process of translating Fluent .ftl message files. It uses Google Translate for accurate translations, and supports multiple target languages. The translated .ftl files are saved in locale-specific directories, organized and ready for use.

To translate an .ftl file:

fluent-translate -i /path/to/my/input/file.ftl -o /my/output/dir --to fr,id --engine Google

Google Cloud Setup

For Google Translate, you need to set up a project in Google Cloud, enable the Cloud Translation API, and create a service account. Then, download the JSON key file for the service account.

Set the GOOGLE_APPLICATION_CREDENTIALS environment variable in your system to the path of the service account key file. For example

export GOOGLE_APPLICATION_CREDENTIALS="/home/user/Downloads/service-account-file.json"

Also, set the GOOGLE_CLOUD_PROJECT_ID environment variable in your system to your Google Cloud project ID. For example:

export GOOGLE_CLOUD_PROJECT_ID="my-project-id"

Remember to replace the paths and IDs in the above examples with the ones from your own setup.

Usage

fluent-translate -i <inputFile> -o <outputDir> [options]

<inputFile>: The path to the .ftl file you want to translate.

<outputDir>: The directory where the translated .ftl files will be saved. Each locale will be saved in a different subdirectory, for example:

fluent-transate /path/to/my/input/file.ftl /my/output/dir --to fr,id

will result in:

/my/output/dir/
├── fr/
│   └── file.ftl
└── id/
    └── file.ftl

Options:

  • --from <language>: Source language (default: 'en-GB')
  • --to <language>: Target language(s), comma separated (default: 'es')
  • --engine <engine>: Translation engine (default: 'Google')

Contributing

Contributions to fluent-translate are welcome. Fork the repository, make your changes, and submit a Pull Request. For larger changes, please open an issue to discuss your plans first.

License

This project is licensed under the ISC license.