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

xliff-reconcile

v1.0.34

Published

Reconcile xliff and resource files

Downloads

7

Readme

xliff-reconcile

This is an npm cli tool to sync the i18n xliff 1.2 files generated by Angular's i18n tool and java resource files. This idea was born from the need for translators whose process works with java resource files and not xliff. The 3 states that we will deal with are:

  • new
  • needs-translation: meaning strings that have been updated within the Angular project
  • translated: the string has been synced to the resource file and is waiting for the translation. Note: this seems to be an odd choice, but we are limited by the tools that we use to sync the translations
  • final: strings that have been translated via the resource file and merged back into the xliff file

The app will read the xliff file and resource file for a given language. 'new' strings will be added to the java resource file if not already there and set to 'x-in-translation'. For 'needs-translation' strings, the value in the resource file will be set to blank and the state set to 'x-in-translation'. For strings with state already set to 'x-in-translation', if a value exists in the resource file, it will be set in the xliff file.

Supports xliff 1.2 files and java resource files with utf-8 encoding.

The flow to publish is basically:

npm version patch

npm run build

npm publish