Can Tag Indent Be Configured On a Per-DTD/Per-Namespace Basis?

I work with some documents that should *never* be formatted and intended and some that I would like to always be. I didn't see a way to configure this in the options. For example, I often work with InCopy INCX XML, in which whitespace is both significant and fiddly (it uses things like Unicode paragraph break characters to signal formatting paragraph breaks--normalizing the whitespace breaks that). If there's no way to do this, can you add it as a feature request? It would be necessary to be able to bind the association by file extension, as well as namespace, schema, and DTD, since in the case of CS3 INCX, the documents are in no namespace but do have a distinct extension (.incx). Cheers, Eliot ---- Eliot Kimber | Senior Solutions Architect | Really Strategies, Inc. email: ekimber@reallysi.com <mailto:ekimber@reallysi.com> office: 610.631.6770 | cell: 512.554.9368 2570 Boulevard of the Generals | Suite 213 | Audubon, PA 19403 www.reallysi.com <http://www.reallysi.com> | http://blog.reallysi.com <http://blog.reallysi.com> | www.rsuitecms.com <http://www.rsuitecms.com>

Hello, Do you mean formatting by the action Format and Indent? For the XML files that should never be formatted you can just add the attribute xml:space="preserve" to the root element or add the qualified name of the root element to the Preserve Space Elements list in Preferences -> Editor -> Format -> XML. We will think about a possible implementation of format and indent options at the document type level (which matches the edited documents by rules based on the file type, namespace, root local name, etc) but it sounds like a configuration nightmare. Maybe the paragraph breaks should be marked up explicitly if they are sensitive to whitespace normalization and if you have the option of customizing the InCopy INCX schema in your process. Regards, Sorin Eliot Kimber wrote:
I work with some documents that should *never* be formatted and intended and some that I would like to always be. I didn't see a way to configure this in the options.
For example, I often work with InCopy INCX XML, in which whitespace is both significant and fiddly (it uses things like Unicode paragraph break characters to signal formatting paragraph breaks--normalizing the whitespace breaks that).
If there's no way to do this, can you add it as a feature request? It would be necessary to be able to bind the association by file extension, as well as namespace, schema, and DTD, since in the case of CS3 INCX, the documents are in no namespace but do have a distinct extension (.incx).
Cheers,
Eliot

On 11/6/08 9:22 AM, "Sorin Ristache" <sorin@oxygenxml.com> wrote:
Hello,
Do you mean formatting by the action Format and Indent? For the XML files that should never be formatted you can just add the attribute xml:space="preserve" to the root element or add the qualified name of the root element to the Preserve Space Elements list in Preferences -> Editor -> Format -> XML.
I'll try adding to the list of preserve space elements.
We will think about a possible implementation of format and indent options at the document type level (which matches the edited documents by rules based on the file type, namespace, root local name, etc) but it sounds like a configuration nightmare. Maybe the paragraph breaks should be marked up explicitly if they are sensitive to whitespace normalization and if you have the option of customizing the InCopy INCX schema in your process.
Unfortunately, INCX is fixed and immutable in this regard. With CS4 Adobe has completely redesigned the XML representation of InDesign and InCopy documents but for CS3, which we will have to work with for the foreseable future, the markup is not what you would call "well designed". Cheers, E. ---- Eliot Kimber | Senior Solutions Architect | Really Strategies, Inc. email: ekimber@reallysi.com <mailto:ekimber@reallysi.com> office: 610.631.6770 | cell: 512.554.9368 2570 Boulevard of the Generals | Suite 213 | Audubon, PA 19403 www.reallysi.com <http://www.reallysi.com> | http://blog.reallysi.com <http://blog.reallysi.com> | www.rsuitecms.com <http://www.rsuitecms.com>
participants (2)
-
Eliot Kimber
-
Sorin Ristache