Skip to main content
B
berard1-Visitor
1-Visitor
April 23, 2012
Question

Insert Tag UI

  • April 23, 2012
  • 10 replies
  • 1745 views
Hopefully this will be a simple question...

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.

I can attach any related documents if needed.

Thanks,
keith

    10 replies

    C
    ClayHelberg18-Opal
    18-Opal
    April 23, 2012
    Hi Keith--



    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".)



    --Clay





    Clay Helberg

    Senior Consultant

    TerraXML


    B
    berard1-VisitorAuthor
    1-Visitor
    April 23, 2012
    Interesting.

    All of our doctypes use the same init acl, so I'm not trying to remap
    anything.

    That said, "show fullkeymap" shows the following:

    * Enter Enter
    * KeyPad_Enter QuickTags

    That's especially strange, since both keys behave in the same way by
    putting in a CR (little hook arrow) rather than ignoring the character and
    showing the quicktags list.

    "show aliases" lists the following:

    Enter {
    if (hook_call("enterKeyHook", 0) != -1) {
    if (columnview_cell_focus() > 0 ) {
    LineDown;
    } else if (option("quicktags") == "on") {
    QuickTags;
    } else {
    if (_list::caret_within_list() && _list::split_list_item() == -1 ) {
    return;
    }
    newline;
    }
    }
    }

    QuickTags _return::next_logical_return()



    C
    ClayHelberg18-Opal
    18-Opal
    April 23, 2012
    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.



    --Clay



    Clay Helberg

    Senior Consultant

    TerraXML


    B
    berard1-VisitorAuthor
    1-Visitor
    April 23, 2012
    Oh, no... we definitely don't want any whitespace preserved.

    I had to "dumb down" my reference FOSI/DTD, but here are the relevant
    entries:

    DTD:


    FOSI:
    <e-i-c gi="para">
    <charlist inherit="1">
    <indent leftind="@+5pt" firstln="*">
    <quadding quad="asis">
    <textbrk startln="1" endln="1"></charlist>
    </e-i-c>


    Now, my reference FOSI says:

    <e-i-c gi="para">
    <charlist inherit="1" charsubsetref="block"></charlist>
    </e-i-c>

    Neither seem to have any effect.

    I must be missing something very fundamental here...

    C
    ClayHelberg18-Opal
    18-Opal
    April 23, 2012
    Did you verify in your doctype/schema that you don't have
    B
    berard1-VisitorAuthor
    1-Visitor
    April 23, 2012
    No schema, just a simple DTD. Not even sure where I would set that in the
    DTD.

    Just seems that it should be the default, but there's probably something
    lurking in our "big" FOSI that I don't know about.

    C
    ClayHelberg18-Opal
    18-Opal
    April 23, 2012
    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.





    Clay Helberg

    Senior Consultant

    TerraXML


    B
    berard1-VisitorAuthor
    1-Visitor
    April 23, 2012
    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.

    B
    bibach1-Visitor
    1-Visitor
    April 23, 2012
    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 🙂


    B
    berard1-VisitorAuthor
    1-Visitor
    April 25, 2012
    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 <
    brandon.ibach@single-sourcing.com> 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 🙂
    >
    >
    >
    >
    Terms & ConditionsAccessibility statement