Does anyone know offhand what causes the quick tag insert to become available? In our old DTDs with pretty complex FOSIs, hitting the <enter> key brings up any context-specific tags.
I have created a few new DTDs, but can only seem to get tags inserted by going to Insert -> Markup then selecting the tag. The DTD itself is being recognized, and only appropriate tags are available in context. Furthermore, in Tools->Preferences->Edit, I do have "Show quick tags on enter" selected.
I created a very very simple FOSI (by hand) to ensure tags are indented with line breaks, and a very simple DCF to handle hidden tags and restrict character substitution. This is also in Arbortext 6.0M030.
Do you have any customizations that change the key mapping for the enter key? In the OOTB setup, the enter key is mapped to the alias "Enter", which (after some checking for hooks and stuff) triggers QuickTags.
Double-check to make sure you haven't remapped the Enter key, or realiased the Enter command. (You can verify this using "show fullkeymap" and "show aliases".)
Oh, you get the little linefeed symbol inserted in the text? That probably means you have the element(s) configured to preserve whitespace in your doctype, maybe using the xml:space="preserve" attribute. In that case, Arbortext thinks you want newlines to be newlines, so it lets you type them with the Enter key.
If that's true, you'll have to decide between preserving whitespace or getting QuickTags to work in the usual way. You could also write your own code for the Enter alias that handles the Enter key however you want.
You might be able to use the oid_asis() function to check whether your elements are set up to display as-is (with newlines). If so, then it probably is a setting in the FOSI, which I guess you'd have to track down by going through the FOSI to find the source of the setting.
Thanks Clay, I guess my simple approach of "hack together a simple FOSI to get it to do something semi-usable" will require a bit more thought. I cringe each time I need to go into ACL to make changes (most of our code is now in Java), but I double-cringe when it comes to FOSI.
I'll be sure to post the "ah ha!" once I find the culprit.
OK, with a little help from PTC support, it was indeed a very simple fix.
According to PTC, as of 5.4, the default setting in the FOSI is to set <quadding quad="asis">, which also explains why we weren't seeing it prior to 6.0, as we migrated directly from 5.3. A quick change to the FOSI took care of it.
Thanks again for the suggestions. keith
On Mon, Apr 23, 2012 at 4:05 PM, Brandon Ibach < firstname.lastname@example.org> wrote:
> I the the culprit is the '<quadding quad="asis">', which the FOSI help > describes as meaning "exactly as in the source (spaces and line breaks > preserved)". > > -Brandon 🙂 > > > >