Erik van Blokland

I'm not happy with the names for the mapped and the unmapped spaces. Who is the user? and isn't it all "designspace"? So alternatively: "bent"/"flat", "warped"/"flat" ?

Bender functions are retired.

* Name: shorter might be better. * So to be clear we can separate the ufoProcessor module from the code that's going to fontTools? I'd prefer that because I probably...

Interesting! What is the `typographicStyleName` ?

I think `styleMapStyleName` is better than `typographicStyleName ` as it already has some use in UFO. I'm puzzling over how these localisations would work in the descriptor object. Maybe analogous...

I've [sketched](https://github.com/LettError/designSpaceDocument/blob/localised-names/Lib/designSpaceDocument/testLocalisedNames.designspace#L39) out some support for localised styleName, familyName, styleMapStyleName and and styleMapFamilyName. These values can roundtrip. I think it would be useful to write these localised names to UFO...

I think the format should be able to facilitate that, and informally, as it is XML you can already do that. However, it's not just an issue of the format:...

@miguelsousa would you be ok with dropping the support for executing the rules when generating ufos?

Test designspace + fonts and some exploring added in #ds5 https://github.com/LettError/ufoProcessor/blob/23297c71789ef04c9f220ae5278a0496c366f3de/Lib/ufoProcessor/__init__.py#L975

If the system can compile features: * generate UFO * compile features * for each UFO, see what `rvrn` or other rule glyphswapping feature of choice would do * swap...