Results for localize-app-name

Abandoned. Last published 9 years ago.

Allows localization of iOS/Android App Name

react-native-localizev3.7.0

A toolbox for your React Native app localization.

vscode-nlsv5.2.0

NPM module to externalize and localize VSCode extensions

@lit/localizev0.12.2

Abandoned. Last published over a year ago.

Localization client library for lit-html

@polymer/app-localize-behaviorv3.0.1

Abandoned. Last published 7 years ago.

A behavior to help with internationalizating apps

@shoelace-style/localizev3.2.2

A micro library for localizing custom elements using Lit's Reactive Controller model.

@lit/localize-toolsv0.8.2

Localization tooling for lit-html

cordova-plugin-pgb-ios-localize-app-namev1.0.13

Abandoned. Last published 10 years ago.

Allows localization of IOS App Name ('Bundle Display Name' or CFBundleDisplayName) when compiling PhoneGap/Cordova apps using build.phonegap.com (PhoneGap Build)

next-intlv4.13.0

Internationalization (i18n) for Next.js

@amazon-devices/react-native-localizev2.0.1758683737

Aging — last published 8 months ago — check before adopting.

A toolbox for your React Native app localization.

@mediapipe/tasks-visionv0.10.35

MediaPipe Vision Tasks

@lion/localizev0.26.0

The localization system helps to manage localization data split into locales and automate its loading

react-localize-reduxv3.5.3

Abandoned. Last published 7 years ago.

Localization library for handling translations in React

@deriv-com/translationsv1.4.6

This is a localization library that uses `i18next`, `react-i18next`, and a custom OTA SDK for translations.

@vee-validate/i18nv4.15.1

Aging — last published over a year ago — check before adopting.

Localization module for VeeValidate

@nativescript/localizev5.2.0

Abandoned. Last published 2 years ago.

i18n plugin for NativeScript using native capabilities of each platform.

webpack-localize-assets-pluginv1.5.4

Localize your Webpack bundle with multiple locales

@localazy/cliv2.0.11

This package is Localazy CLI tool for app and software localization and translation.

i18n-calypsov7.4.0

Aging — last published over a year ago — check before adopting.

I18n JavaScript library on top of Tannin originally used in Calypso.

@brightspace-ui/localize-behaviorv2.12.0

Polymer mixin for localization of D2L components

@theia/localization-managerv1.72.2

Theia localization manager API.

localize-routerv2.0.0-RC.3

Abandoned. Last published 6 years ago.

An implementation of routes localization for Angular

Abandoned. Last published 5 years ago.

@localize/nodev1.7.0

Abandoned. Last published over a year ago.

Localize API for Node.js

RubyGems matches

8 matches · Ruby

jiveappsv1.0.7

Abandoned. Last published 13 years ago.

== Jiveapps These tools are all about making Jive App development as easy as possible. After you install the tools, it only takes a single command to: 1. Create a new app - a simple Hello World application. 2. Set up version control for your code using Git. 3. Host the app code online at Jive's AppHosting server. 4. Register the app on the Jive Apps Marketplace as an app "in development". 5. Install the app on your default app dashboard in the Jive Apps Sandbox. After you install, use this simple workflow to make changes and see them reflected in the sandbox: 1. Make a change to the code on your local machine. 2. Commit the changes to your local Git repository. 3. Push the changes to the remote Jive Apps repository. This automatically updates the hosted copy on the Jive AppHosting server. 4. Refresh the app dashboard or canvas page on the Jive Apps Sandbox and see your changes. Other features: * LiveDev: preview your changes on the Jive App Sandbox in real time * Collaboration: add other developers to your project * OAuth Key Management: associate consumer key/secret pairs with service names for use in your apps

serv0.1.0

Aging — last published 8 months ago — check before adopting.

Ser(ve) your web app with HTTPS to any device on your network (mDNS): 1. Use convenient domain names without ports (https://app.local vs http://127.0.0.1:3000); 2. Use mDNS for .local domains, so you can visit them from your phone or any other device connected to the same network; 3. Locally-trusted development certificates (read on filosottile/mkcert how to trust certificates on mobile devices). Use-cases: 1. Simulate production-like subdomains (e.g., blog.example.com, api.example.com); 2. Test cookies scoped to specific domains; 3. Preview multi-tenant routing (e.g., tenant1.example.com, tenant2.example.com); 4. Use third-party APIs that need HTTPS.

gamev0.0.1

Abandoned. Last published 13 years ago.

# Game A Ruby-powered MVC game framework. ## Install ```sh $ gem install game ``` ## Usage ### Setup ```sh $ game new my_cool_game ``` This will create a new directory named `my_cool_game` in the current working directory. The directory is laid out very much like a Rails application: my_cool_game ├── Gemfile ├── Guardfile ├── README ├── app | ├── assets │ │ ├── fonts │ │ ├── images │ │ ├── music │ │ └── sounds | ├── controllers │ │ └── game_controller.rb | ├── helpers │ │ └── game_helpers.rb | ├── models | ├── views | └── windows │ │ └── game_window.rb ├── config │ ├── environments │ │ ├── development.rb │ │ ├── production.rb │ │ └── test.rb │ ├── initializers │ ├── locales │ │ └── en.yml │ ├── application.rb │ ├── boot.rb │ └── database.yml │ ├── environment.rb │ └── routes.rb ├── log ├── spec | └── spec_helper.rb └── tmp ## Acknowledgements * [Rails][rails] for making MVC very popular in the [Ruby][ruby] universe * [Gamebox][gamebox] for inspiration. ## Contributing * Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet * Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it * Fork the project * Start or switch to a testing/unstable/feature/bugfix branch * Commit and push until you are happy with your contribution * Make sure to add tests for it. This is important so I don't break it in a future version unintentionally. * Please try not to mess with the Rakefile, VERSION or gemspec. ## Copyright Copyright © 2012 Ryan Scott Lewis <ryan@rynet.us>. The MIT License (MIT) - See LICENSE for further details. [rails]: https://github.com/rails/rails [ruby]: https://github.com/ruby/ruby [gamebox]: https://github.com/shawn42/gamebox

faraday_errorv0.1.1

Abandoned. Last published 10 years ago.

# FaradayError [![Gem Version](https://badge.fury.io/rb/faraday_error.svg)](https://badge.fury.io/rb/faraday_error) A [Faraday](https://github.com/lostisland/faraday) middleware for adding request parameters to your exception tracker. ### Supports - [Honeybadger](https://www.honeybadger.io/) - [NewRelic](http://newrelic.com/) - Your favorite thing, as soon as you make a pull request! ## Installation Add this line to your application's Gemfile: ```ruby gem 'faraday_error' ``` And then execute: $ bundle Or install it yourself as: $ gem install faraday_error ## Usage Configure your Faraday connection to use this middleware. You can optionally specify a name; defaults to `faraday`. It is expected that you also use `Faraday::Response::RaiseError` somewhere in your stack. ```ruby connection = Faraday.new(url: 'http://localhost:4567') do |faraday| faraday.use FaradayError::Middleware, name: "example_request" faraday.use Faraday::Response::RaiseError faraday.adapter Faraday.default_adapter end ``` And that's it. Make a request as you normally would. ```ruby connection.post do |req| req.url '/503' req.headers['Content-Type'] = 'application/json' req.body = JSON.generate(abc: "xyz") end ``` If any request fails, Honeybadger's "context" for this error will include your request parameters. If sending JSON or `application/x-www-form-urlencoded`, these will be included in parsed form. ```json { "example_request": { "method": "post", "url": "http://localhost:4567/503", "request_headers": { "User-Agent": "Faraday v0.9.2", "Content-Type": "application/json" }, "body_length": 13, "body": { "abc": "xyz" } } } ``` ## Development After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment. To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org). The included [RestReflector](../master/spec/rest_reflector.rb) Sinatra app is suitable for making requests that are guaranteed to fail in particlar ways. ## Contributing Bug reports and pull requests are welcome on GitHub at https://github.com/jelder/faraday_error. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct. ## License The gem is available as open source under the terms of the [MIT License](http://opensource.org/licenses/MIT).

wcc-contentfulv1.7.2

Aging — last published over a year ago — check before adopting.

Contentful API wrapper library exposing an ActiveRecord-like interface

wcc-contentful-graphqlv1.2.0

GraphQL interface over WCC::Contentful store

sm-transcriptv1.0.0

Abandoned. Last published 15 years ago.

$Id: README.txt 204 2010-11-30 02:20:04Z pwilkins $ sm-transcript reads results of SLS processing and produces transcripts for the SpokenMedia browser. For each file in the source folder whose extension matches the source type, a file of destination type is created in the destination folder. All of these parameters have default values. Note: Examples of the commands you enter in the terminal are for *nix. The command prompt in the examples is: felix$ <command line> If you are a Windows user, make the usual adjustments. Requirements: sm-transcript is written in Ruby and packaged as a RubyGem. Since Ruby is not a compiled language, you will need to have Ruby installed on your machine to run sm-transcript. You can determine if Ruby is installed by typing "ruby -v" at a terminal prompt. It should return the version of Ruby that is installed. If Ruby is not installed on your machine, navigate to http://www.ruby-lang.org/ and follow the installation instructions. sm-transcript was developed using Ruby 1.8. Other Ruby versions have not been tested as of this release. Installation: You can get sm-transcript as either a RubyGem or as source from svn. The preferred way to install this package is as a Rubygem. You can download and install the gem with this command: felix$ sudo gem install [--verbose] sm-transcript This command downloads the most recent version of the gem from rubygems.org and makes it active. Previous versions of the gem remain installed, but are deactivated. You must use "sudo" to properly install the gem. If you execute "gem install" (omitting the "sudo") the gem is installed in your home gem repository and it isn't in your path without additional configuration. Note: You need sudo privileges to run the command as written. If you can't sudo, then you can install it locally and will need some additional configuration. Contact me (or your local Ruby wizard) for assistance. The executable is now in your path. You can cleanly uninstall the gem with this command: felix$ sudo gem uninstall sm-transcript If you have access to our svn repository, you are welcome to check out the code. Be warned that the trunk tip is not necessarily stable. It changes frequently as enhancements (and bug fixes) are added. (note that the 'smb_transcript' in the command line below is not a typo.) svn co svn+ssh://svn.mit.edu/oeit-tsa/SMB/smb_transcript/trunk sm_transcript build the gem by running this command from the directory you installed the source. This is what it looks like on my machine: felix$ rake gem The gem will be built and put in ./pkg You can now use the gem installation instructions above. Using the App: Run with no command line parameters, the app reads *.wrd files out of ./results and writes *.t1.html files to ./transcripts. These directories are relative to where sm_transcript is called. Note: destination files are overwritten without a warning prompt. If you want to preserve an existing output file, rename it before running the app again. For example, run the app by navigating to the bin folder and enter projects/sm_transcript/bin felix$ sm_transcript This command run from this folder will read *.wrd files from bin/results and write *-t1.html to bin/transcripts. Usage: sm_transcript [options] --srcdir PATH Read files from this folder (Default: ./results) --destdir PATH Write files to this folder (Default: ./transcripts) --srctype wrd | seg | txt | ttml | srt Kind of file to process (Default: wrd) --desttype html | ttml | datajs | json Kind of file to output (Default: html) -h, --help Show this message There is a serious gotch'a in specifying the srctype parameter: it must match the case of the file extension that you're processing. This means that if the srt files that you are processing have the extension .SRT, then you must specify the srctype as "SRT". Pretty lame, I know. I will update the gem with a fix shortly. My apologies until then. Troubleshooting: sm-transcript requires additional gems to operate. The RubyGem installation should install dependencies automatically, but when it doesn't, you get an error that includes ... no such file to load -- builder (LoadError) in the first few lines when you run sm-transcript, the problem is a missing dependent gem. (the error above indicates that the Builder gem is missing.) Try installing the missing gem. For the error above, the command looks like this on my computer: felix$ sudo gem install builder See "Required Gems" below for more information. A warning message such as: "WARNING: Nokogiri was built against LibXML version 2.7.6, but has dynamically loaded 2.7.7"" may be safely ignored. If you continue to have trouble, feel free to contact me. Upgrading: You can easily upgrade by simply executing the same command you used to install the gem. Running install again will add the newer version and make it active. By default the most recent version is used, but older versions are still available, simply inactive. If are using svn, you should already know what to do. Required Gems: builder - create structured data, such as XML extensions - added for the 'require_relative' command. (To get this command in Ruby 1.8 you need to install this gem, for Ruby 1.9 the command is already part of the core.) htmlentities - html parsing json - create JSON structured data nokogiri - xml parsing library optparse - option parsing of command line ostruct - open data structures ppcommand - pp is a pretty printer. It is used only for debugging rake - make for Ruby rubygems - support for gems (shouldn't be needed for Ruby 1.9) shoulda - enhancement for Test::Unit This command installs gems on OSX and Linux: felix$ sudo gem install <gem name> I recommend running the following command to update to latest version of rubygems before loading new gems. felix$ sudo gem update --system Unit Tests: You may run all unit tests by navigating to the test folder and running rake with no parameters (the default rake task runs all tests). On my computer, it looks like this: projects/sm_transcript/test felix$ rake Release Notes: Initial Version - runs under Ruby 1.8.x. version 0.0.4 - fixes bug when processing .WRD files with CRLF line endings. version 0.0.5 - removed due to posting error version 0.0.6 - added srctype of ttml and desttype of json, fixed bug where beginning time of word was actually for previous word. version 0.0.7 - added srt as srctype version 0.0.8 - fixed bug that dropped last phrase from transcripts version 1.0.0 - declared this version 1.0.0 to conform more closely with gem numbering conventions. All tests run successfully. To Do: - specify individual files for processing rather than folders - fix bug in srt processing: can't read Creole srt content. - allow user to modify the "t1" file extension for addition languages of the same transcript. - update code to run under Ruby 1.9

x1c-studio-gamev1.0.0