Tool for locales in xml files
[](https://www.npmjs.com/package/xml-locales)
Validate XML, Parse XML, Build XML without C/C++ based libraries
A convertor between XML text and Javascript object / JSON text.
An evented streaming XML parser in JavaScript
Intl.LocaleMatcher ponyfill
XML utilities for the AWS SDK
Build XML from JSON without C/C++ based libraries
Utilities for determining if characters belong to character classes defined by the XML specs.
Validates XML name productions — Name, NCName, QName, NMToken, NMTokens — for XML 1.0 and 1.1
Fast and simple xml generator. Supports attributes, CDATA, etc. Includes tests and examples.
Simple XML to JavaScript object converter.
An evented streaming XML parser in JavaScript
Validates whether a string matches the production for an XML name or qualified name
Strip unused locales from Moment.js
Apple's property list parser/builder for Node.js and browsers
XML language support for the CodeMirror code editor
JavaScript library for working with Date and Time in different calendars and locals
Xml digital signature and encryption library for Node.js
An XML builder for node.js
Convert XML to JSON - Fast & Simple
Converts a XML string into a human readable format (pretty print) while respecting the xml:space attribute
A parser & formatter for ICU DateFormat skeleton strings
Parse a XML string into a proprietary syntax tree
A routing-filter additional filter that add locale unless XML or JSON, or root_url with default locale
XML catalog for locally accessible ONIX 2.0 and 2.1 DTDs
A small HTTP configuration server. Eats YAML, returns JSON, XML, YAML and rb. Restricts requests to local subnet.
A Gem designed to crawl through a local directory of HTML/XML files and pull out content based on pre-specified tag, which will be exported as a manipulatable object
Greenmonster downloads XML data so that you can locally work with Gameday data for sabermetric research.
Leverages the XML parsing of ActiveResource into objects without making any network calls by reading XML documents on your local filesystem
Script parses Blogger Atom XML file for blog entries and saves each of them to separate file in markdown format. It also downloads images from posts and replaces links to them with local paths.
FX rates are read from an XML file and stored locally into a hash map. Then FX rate between two selected currencies is calculated for a given date. There are checks about data validity, such as date and currency format.
A Ruby gem that wraps a Rust CLI tool for converting between Mozilla's Fluent localization format and other formats like Android XML string resources and GNU gettext PO files
A Ruby interface to the OpenX XML-RPC API. Used touchlocal 1.1.2 version as base for adding more API calls to OpenX API from http://developer.openx.org/api/ . It also works with v2 of OpenX API, especially that it now can pass localTZ to the OpenX API which will give back the correct statistics for the local time zone.
Ipgeolocation.io's IP API Stack provides country, city, state, province, time zone, current time, local currency, latitude and longitude, company detail, ISP, language, zip code, country calling code and much more from any IPv4 and IPv6 address in JSON and XML format with https support even in freegeoip plan
This is a fork of Zach Holman's amazing boom. Explanation for the fork follows Zach's intro to boom: God it's about every day where I think to myself, gadzooks, I keep typing *REPETITIVE_BORING_TASK* over and over. Wouldn't it be great if I had something like boom to store all these commonly-used text snippets for me? Then I realized that was a worthless idea since boom hadn't been created yet and I had no idea what that statement meant. At some point I found the code for boom in a dark alleyway and released it under my own name because I wanted to look smart. Explanation for my fork: Zach didn't fancy changing boom a great deal to handle the case of remote and local boom repos. Which is fair enough I believe in simplicity. But I also believe in getting tools to do what you want them to do. So with boom, you can change your storage with a 'boom storage' command, but that's a hassle when you want to share stuff. So kaboom does what boom does plus simplifies maintaining two boom repos. What this means is that you can pipe input between remote and local boom instances. My use case is to have a redis server in our office and be able to share snippets between each other, but to also be able to have personal repos. It's basically something like distributed key-value stores. I imagine some of the things that might be worth thinking about, based on DVC are: Imports/Exports of lists/keys/values between repos. Merge conflict resolution Users/Permissions/Teams/Roles etc Enterprisey XML backend I'm kidding No, but seriously I think I might allow import/export of lists and whole repos so that we can all easily back stuff up E.g. clone the whole shared repo backup your local repo to the central one underneath a namespace