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

gatsby-transformer-ceteicean

v1.2.1

Published

Gastby transformer plugin for TEI XML to CETEIcean Custom Elements

Downloads

30

Readme

gatsby-transformer-ceteicean

Transforms XML files for Custom Elements support via CETEIcean.

Each element in an XML file gets prefixed with a given prefix based on the element's namespace.

To facilitate use with CETEIcean, the transformer generates a list of prefixed elements and data-origname and data-origatts attributes are added to each element.

TEI XML is supported by default and TEI elements will be prefixed with tei-.

Supported extensions: .xml, .odd

Install

npm install gatsby-transformer-ceteicean

Note: You also need to have gatsby-source-filesystem installed and configured so it points to your files.

How to use

In your gatsby-config.js:

module.exports = {
  plugins: [
    `gatsby-transformer-ceteicean`,
    {
      resolve: `gatsby-source-filesystem`,
      options: {
        path: `./src/data/`,
      },
    },
  ],
}

Where the source folder ./src/data/ contains the .xml files.

How to query

You can query the nodes using GraphQL like this:

{
  allCetei {
    edges {
      node {
        original
        prefixed
        elements
      }
    }
  }
}

which would return:

{
  allCetei: {
    edges: [
      {
        node: {
          original: "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<TEI xmlns=\"http://www.tei-c.org/ns/1.0\"/>",
          prefixed: "<tei-TEI data-xmlns=\"http://www.tei-c.org/ns/1.0\" data-origname=\"TEI\" data-origatts=\"xmlns\">",
          elements: [
            "tei-TEI"
          ]
        },
      },
    ]
  }
}

Transformations

Custom transformations of the XML can be queued to be performed before (applyBefore) or after (applyAfter) the default processing described above. You can pass an array of functions to perform transformations. Functions will receive the following object, should modify parts of it, and MUST return the same structure:

{
  original: '', // the XML as a string
  prefixed: '', // the data as a string after default processing
  elements: [] // list of elements generated by the default processing
}

If you're processing the XML before the default processing, you'll want to change original; on the other hand, if you're processing after the default processing, you'll want to change prefixed. Changing elements is not advisable.

You can write transformation scripts in Node, or call out to other processing via API calls or command line to perform XSLT transformations.

const xsltTransform = require("./xsltTransform.js")

const postTansform = (obj) => {
  // perform some transformation
  const prefixed = obj.prefixed.replace(/\s+/g, ' ')

  return {
    original: obj.original,
    prefixed,
    elements: obj.elements
  }
}

module.exports = {
  plugins: [
    {
      resolve: `gatsby-transformer-ceteicean`,
      options: {
        applyBefore: [xsltTransform],
        applyAfter: [postTransform],
      }
    }
    ...
  ],
}

Namespaces

Non-TEI namespaces can be set on the plugin via options:

module.exports = {
  plugins: [
    {
      resolve: `gatsby-transformer-ceteicean`,
      options: {
        namespaces: {
          "http://www.music-encoding.org/ns/mei": "mei",
          "http://dita.​oasis-open.​org/​architecture/​2005/": "dita"
        }
      }
    },
    ...
  ],
}