- From: Jostein Austvik Jacobsen <josteinaj@gmail.com>
- Date: Tue, 18 Feb 2014 10:00:16 +0100
- To: Florent Georges <fgeorges@fgeorges.org>
- Cc: XProc Dev <xproc-dev@w3.org>
Received on Tuesday, 18 February 2014 09:01:04 UTC
Great! Would you prefer if the steps are moved to some PipX namespacing regime or are any namespace fine? I think the main obstacle to using PipX in other projects are how easily it can be integrated into other build processes. Jostein On 17 February 2014 15:45, Florent Georges <fgeorges@fgeorges.org> wrote: > Hi, > > As promised to some of you in Prague last weekend, I have eventually > created a GitHub repository for PipX, in order to ease collaboration > on the library. PipX is aimed at being a general purpose library for > XProc. It is different from EXProc, because it does not define any > extension. The goal is to gather existing XProc steps, written in > standard XProc, and build a standard library for all those tools you > found yourself writing and again and again. > > For now, there is no step yet, so this is really a call for > collaboration, rather than announcing a read-to-use library. If you > have interesting, generic enough steps somewhere in your codebase, > feel free to share them! For more information: > > http://pipx.org/ > https://github.com/fgeorges/pipx > > Regards, > > -- > Florent Georges > http://fgeorges.org/ > http://h2oconsulting.be/ > >
Received on Tuesday, 18 February 2014 09:01:04 UTC