gferreira2

see also the [Fencer](http://github.com/Lorp/fencer) by @Lorp, currently under development, which supports the more complex avar2 mappings

thanks for looking into it. it would be nice if it could behave just like `vanilla.List`, falling back to whatever value is set in the parent `allowsSorting` argument: ```python import...

maybe just `name : number` is fine? ``` public.namedNumbers : { fooWidth : number, fooHeight : number } ```

Laser Measure is just one of many tools that implement measurements. if we are looking for a public data format that makes interoperability between tools possible or easier, I think...

I am of course also biased towards my own tool and format :) just trying to add another point-of-view and use case. thanks for the clarification about the keys. it...

## Proposal: extensible syntax for measurement keys `measurement`.`direction`.`case`.`glyph` Level 1: - `stem.x` - `stem.y` - `counter.x` - `overshoot.y` - `hserif.x` - `hserif.y` - `vserif.x` - etc. Level 2: - `stem.x.uppercase`...