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

leaflet-i18n

v0.3.5

Published

Internationalization for Leaflet plugins

Downloads

2,004

Readme

# Leaflet.i18n

Internationalisation module for Leaflet plugins.

This module has been extracted from Leaflet.Storage, in case it can be useful for others.

See https://github.com/Leaflet/Leaflet/pull/1232 for a discussion on the history of this.

## API

  • to make a string translatable, just call L._ (shortcut for L.i18n), like this:
L._("The phrase I want to be translatable");
L._("A complex sentence with a {variable}", {variable: "my value"});
  • one or more locale/{locale_code}.js should be provided, something like:
var mylocale = {
    "Simple phrase to translate": "Une simple phrase à traduire",
    "A sentence with a {variable}": "Une phrase avec une {variable}",
};
  • the locale must register itself, doing something like:
L.registerLocale('fr', mylocale);

This can be done more than once. For example, every plugin can add it's translations for some locale without overriding all the already registered strings. However, if the same string for the same locale is registered twice, the last wins.

  • end user must load the locale/ files provided by Leaflet, or plugins

  • end user must set his locale, doing so:

L.setLocale('fr');

Generating locales files

A util script is provided in this module for extracting strings to translate from Leaflet plugins code and generating the locales files.

Example of use:

node bin/i18n.js --dir_path={somepath} --locale_dir_path={somepath} --locale_codes={nl,fr,es}

This will generate the locale files for nl, fr and es. Note: if the locale files already exist, they will be updated (and the previous translated strings will be kept).

## Tests

To run the unittests, just do, from the root of the module:

make test