... trying to create invisible text. NEVER, ever use white! That's a strong statement. It sounds like there are further downsides to white on white (w-o-w). Some I can think of are: It really needs to be pure RGB or CMYK white. Acrobat won't redact if it's even 1 bit different than the background color. Even so, if even one coordinate of a w-o-w- font outline lies on a non-white color object, that entire character will still be present in the PDF after redaction. The invisible text color needs to be named something other than "White", which Frame might set to Cutout rather than Invisible. ... but use something that really stands out, like a magenta I agree on standout, but I wouldn't recommend magenta. Frame is hard-coded to use magneta to flag Condition Code overload. So there's nothing to redact in Acrobat either. Turns out we have to do that anyway. We use EPS imports. Unix Frame is apparently passing them to the .ps file with the preview/thumbnail images intact, and they are being distilled to pdf with the (large, but now useless) preview images embedded, along with EXIF photo data, pixels and vectors outside clipping paths, etc. This undesirable metadata can constitute some 40% of the final pdf, which matters on 20MB pdfs served on the web. So we routinely redact them, and the process stomps the invisible text with no extra effort. I looked into Color Views at one time, expecting that it could provide different definitions for colors in each view. It doesn't, so I abandoned it. I just took another look, and it turns out that between Cutout and Invisible, the feature apparently can handle our two magic color requirements, so we'll probably switch to Views. Thanks for bringing it up.
... View more