Fetches translations from ikr/translator-couch, and stringifies ICU messages within Mustache templates under node.js
CouchDB schema for Magomogo/translator-utils, Magomogo/translator, and ikr/translator-node
文字列をノムリッシュ翻訳します
Official Lara SDK for JavaScript and Node.js
An isomorphic client library for the Azure Translator Service
Create and translate standard UUIDs with shorter formats.
git@github.com:stalniy/ucast.git
git@github.com:stalniy/ucast.git
a pure javascript protocol buffer encoding implementation, written specifically for riak
A simple and free API for Bing & Microsoft Translator for Node.js
Transpile TypeScript code to JavaScript with Closure annotations.
Toolkit for creating Flow and TypeScript compatible libraries from Flow source code.
check rules for signavio-i18n
PathTranslator for roblox-ts
Translator, bulk replace string at a time
Node.js translation library powered by Transformers.js with ONNX Runtime
SuttaCentral bilara-data library
## Install
A free and unlimited API for Google Translate
Translate your JSON file or object into another languages with Google Translate API
Runtime-agnostic translation core powered by Transformers.js
Insteon Hub
JavaScript LaTeX to HTML5 translator
Internationalization for markuplint
This gem will install as a daemon and can be used to connect to a graphite and a carbon backend. It will not only post the data for the metrics but also create graphs into graphite, by means of a translation from munin-node.
A gem that adds explain_in_english to ActiveRecord::Relation, translating common Arel query nodes into human-readable language.
jsx_rosetta is a JSX-to-Rails translator. It parses JSX via Babel (over a Node sidecar), lowers the parsed AST into a framework-agnostic semantic IR, and emits target output via pluggable backends. The initial backend produces ViewComponent classes paired with ERB templates; additional backends (Phlex, Slim, Phoenix LiveView, etc.) can be added against the same IR.
# Chef Data Region ## Description Chef Data Region extends the `Chef::DSL::DataQuery` module's `data_bag_item` method with the ability to dynamically expand the data bag name in a configurable, environment-specific manner. ## Motivation This gem exists to address the following scenario: An organization maintains data in Chef data bag items. The data is deployed to several data center environments and is stored in data bags whose names reference the environments. The organization wants to write environment-agnostic recipes that access the data bags without explicitly referencing the data bags by their environment names. As a concrete example, imagine the organization maintains encrypted data for three deployment environments: development, staging, and production. It maintains this data in three data bags, one for each environment, with data for services named `gadget` and `widget` in items: | Environment | Bag | Item | |-------------+----------------+--------| | Development | secure-dev | gadget | | Development | secure-dev | widget | | Production | secure-prod | gadget | | Production | secure-prod | widget | | Staging | secure-staging | gadget | | Staging | secure-staging | widget | The items are encrypted with a key unique to that environment to maximize security. Now consider how a recipe would access these bags. When then recipe is running, it needs to know the data center environment in order to construct the bag name. The organization would most likely assign the enviroment name to a node attribute. In a naive implementation, each recipe would include logic that examined the attribute's value to determine which bag to load. This would obviously duplicate code. Imagine instead that the organization wants to reference the bag by the name `secure` and rely on an _abstraction_ to translate `secure` into the environment-specific bag name. This gem provides that abstraction. ## Features This gem overrides the `data_bag_item` method with configurable logic that dynamically decides which bag to load. It retains API compatibility with `Chef::DSL::DataQuery#data_bag_item`, so existing recipes that call `data_bag_item` work without modification. The gem imposes no constraints on data bag item structure. ## Configuration Assign the region name to a node attribute that varies by environment: node.default['local'][region'] = 'staging' Add the following configuration to Chef Client's `client.rb` file. * Require the gem: require 'chef/data_region' * Configure the gem with a hash that maps a bag name to an expansion pattern: Chef::DataRegion.add( 'secure', { attribute: %w(local region), pattern: 'secure-%<attribute>s' } ) ## Bag name expansion The gem expands bag names using Ruby's `format` method. _More pending..._
Diff and patch tables
Diff and patch tables