Skip to main content
1-Visitor
April 12, 2012
Question

Editor 6.0 m010 mysterious debug message: conrule literal ref to ent not declared "%s"

  • April 12, 2012
  • 2 replies
  • 744 views
Hi,

More work on migrating our 5.3 m110 authoring environments to 6.0 m010. I
just got this:

On opening an XML instance in one of my environments, the Arbortext Editor
Debug Messages window opens and says:
agettext: Msgid not found in message file: Warning conrule literal
contains a reference
to an entity not declared in the FOSI. Literal is: "%s". Conrule will be
compiled under
the assumption that the reference will resolve using the instance subset
and DTD
at composition time.

Of course I can't find the string %s anywhere in my FOSI let alone in a
conrule.

Did anyone run into this or something similar?

Editor opens the FOSI without complaint and check completeness doesn't turn
up any problems.

--
Paul Nagai

    2 replies

    18-Opal
    April 12, 2012
    Hi Paul--



    The "%s" is a place holder, like in a printf() statement. It's there so
    you can give a localized error message with some error-specific detail.
    It's usually a file name or a line number or something like that. In
    this case it's probably meant to be replaced with the markup of the
    entity reference that is triggering the problem.



    So it looks like there are two nested errors here: the primary one is
    something to do with an undefined entity in the FOSI. But there also
    seems to be something wrong with the message data files, or some
    configuration related to them, that is causing Arbortext to fail when it
    tries to lookup the text for the error (in case you were running Editor
    in a French or Chinese environment, so you'd see the message in the
    appropriate language).



    --Clay





    Clay Helberg

    Senior Consultant

    TerraXML


    naglists1-VisitorAuthor
    1-Visitor
    April 12, 2012
    LOL! Forest for the trees ... thanks, Clay. Too ready to see problems with
    MY stuff, I missed the obvious Arbortext bug obscuring my actual problem.
    No joy yet, but I'll stop looking for %s!