Skip to main content
A
Anonymous
February 9, 2010
Question

Question about ArborText's XML code

  • February 9, 2010
  • 5 replies
  • 1426 views
The entity list has to do with which characters show up in the character
entity dialog for fastest access. As the author uses various special
characters, they get recorded here on the assumption that the author may
want to reuse. And we initialize the list with a short set to begin
with.



The pub caret processing instruction tells the Editor where the caret
was when the document was saved. We use this to put the caret back to
the same location when you reopen the document. If the pub caret is
missing, we just put the caret near the top of the document.



John Dreystadt
Software Development Director
Arbortext - PTC
734-352-2835
-

    5 replies

    P
    ptc-9533431-Visitor
    1-Visitor
    February 9, 2010
    These are some of the many processing instructions that Arbortext uses to track information specific to a document. The first item is the entity list, I believe this just tracks the ones you have used via the menu. the second item is related to where your cursor was in the document when you last saved the file. This allows the editor to open the file and return to the last place you worked. ..dan --------------------------------------------------------------------------- Danny Vint Specializing in Panoramic Images
    G
    gstuckey1-Visitor
    1-Visitor
    February 10, 2010

    John and Dan,

    Thank you very much for the response. Viewing the XML file in a text editor is interesting. I have many more questions coming.

    G.

    N
    naglists1-Visitor
    1-Visitor
    February 10, 2010
    Ginger,
    Try working with this setting if you haven't run across it already.
    "Required" for peeking behind the curtain. It helps me see the XML structure
    more easily and it makes certain types of find and replace possible by
    keeping elements on a single line.

    set outputrecordlength=8000

    Finding a text editor that knows (or can be taught) to highlight XML / your
    DTD can be very helpful, too. I like Textpad. It does have Unicode
    limitations, however, that can cause problems with some content.


    D
    DavidS.Taylor1-Visitor
    1-Visitor
    February 12, 2010
    For those who want to view/edit XML as text, I can highly recommend Jedit. It is fully XML aware, including the use of catalogs. It has many plug-ins for specific purposes, XML, XSLT, JDiff and Sidekick being relevant ones. Jedit is fully Unicode compatible (all variations), as well as supporting about 30 other old or less common encodings.

    David

    David S. Taylor

    Project Manager, Structured Information
    Institute for Research in Construction
    National Research Council Canada
    Bldg. M-23A, Room 239
    1200 Montreal Road, Ottawa, ON K1A 0R6
    C
    ClayHelberg18-Opal
    18-Opal
    February 12, 2010
    I second this whole-heartedly. jEdit is great, it's the one tool I use
    more than anything else-it's always the first thing I install in a new
    environment to get myself up and running. I also developed a
    configuration for editing ACL files in jEdit, works really slick.



    The one downside I've noticed is that it sometimes gets bogged down with
    really big files, but I don't find that I run into the problem very
    often. For the majority of files that are reasonably sized (like
    stylesheets, ACL files, DTD's etc.) it's fabulous.



    --Clay


    Terms & ConditionsAccessibility statement