I never have. But a script I've been debugging has highlighted the following. Is this a bug, or is it me not understanding something? If you try this: UnitValue("10c").type you get: Result: ? meaning that it is not a recognised UnitValue type. But, if you do this: UnitValue("10ci").type you get ci In other words, UnitValue recognises ci as the correct abbrev. for ciceros. However, if you try myTextFrame.textFramePreferences.insetSpacing = "10ci" you get an error, whereas if you go for myTextFrame.textFramePreferences.insetSpacing = "10c" the textFrame inset is set correctly -- 10 ciceros, meaning that the InDesign abbreviation for ciceros is "c" not "ci". If the above is all correct, it does mean that you cannot naively rely on UnitValue to confirm that the user inputted a valid measurement in a text field in a ScriptUI dialog as follows, which is what I've been doing: if (UnitValue(theText).type == "?")... Is this a bug, or is this a CS vs. ID thing, or what? I reiterate that I've never used ciceros for anything -- but I'm sure there are some good folk out there who'd swear by them, so in the interests of plurality etc. etc. Ariel
... View more