Sorry for being unclear. What I mean is that during structured import,
frame is inserting a nameless character format that sets the Japanese
and English fonts even if you've already defined a paragraph tag for
that element in the edd. This blank character tag is placed right
before the actual string mif element instead of being defined at a
higher level. Doing this gives it precedence over anything else you
may have defined.

What's even weirder is that when I insert elements manually the
character tags aren't inserted and the formatting is correctly derived
from the paragraph tag.

I tried your advice and made a one element structured application that
applied a paragraph formatting but I ran into the same problem. Frame
still throws in that character tag which sets the text font(note that
the font size, width etc... are derived from the paragraph tag
correctly, only the font is being overridden). Could it be that frame
expects you to do things the "right" way and set up your inheritance
manually instead of using paragraph tags?

So, as far as I can tell, it's not a problem of the context being
wrong so much as that frames structured import is doing something that
I don't understand at all. It could be that I just don't understand
the nuances of how inheritance in structured import works though.


On 10/17/06, Lynne A. Price <lprice at> wrote:
> Noah,
>    I don't quite follow what is happening here, and I don't understand what
> you mean by FM "inserting font data on the strings themselves". Do you mean
> that if you import the same element hierarchy with different text you get a
> different font?
>    In general, to debug problems in which I don't understand what fonts are
> being applied, I recommend you first check whether File > Struct Tools >
> Show Element Context provides any clues as to what is happening.
>    If not, try creating a test application in which the EDD defines only
> one element with a general rule of <TEXT> and a text format rule that
> applies the combined font that your current XML import does not apply. Can
> you import successfully with this test application? If so, the next step is
> to figure out the difference between the test application and the actual
> one. It may be helpful to iterate over progressively simpler versions of
> the original application until you pinpoint where it fails.
>          --Lynne
> At 09:24 PM 10/15/2006, Noah Evans wrote:
> >Hey Rick, framers,
> >
> >Rick, thanks for your tip, however in this case it didn't work. Here's why:
> >
> >After looking through the mif and experimenting with different
> >formatting in the edd, I've found the problem, but I have no idea why
> >it's ending up like this.
> >
> >Frame seems to be inserting font data on the strings themselves
> >--overriding the combined fonts defined by the elements. Does anyone
> >have any idea of how I could stop frame from doing this? I can
> >manually set the font with a text rule, but frame still nests the
> >combined fonts too deeply in the mif, so frame's fonts override them.
> >
> >I could write an fdk client to eliminate the font information
> >manually, but I'm hoping that someone who knows more than me could
> >offer me some ideas as to what's going on and why frame's putting in
> >that font data.
> >
> >Thanks for everybody's help and input,
> >
> >Noah
> >
> >
> >
> >On 10/12/06, Rick Quatro  <frameexpert at> wrote:
> >>   Hi Noah,
> >>
> >>I am not sure what is causing this by try this after you import the XML.
> >>
> >>1) Choose File > Import > Element Definitions.
> >>
> >>2) Leave Current selected in the Import from Document popup. Check the
> >>Format Rule Overrides checkbox and click Import.
> >>
> >>Rick Quatro
> >>Carmen Publishing
> >>585-659-8267
> >>
> >>
> >>
> >> > Hey all,
> >> >
> >> > I'm having a very strange problem with my structure application. When I
> >> > import an xml file, none of the fonts follows the paragraph tags(which 
> >> > are
> >> > assigned by the edd, they show up just fine in the pgftag bar and menu,
> >> > but
> >> > the fonts just don't apply for some reason). They seem to be inheriting
> >> > the
> >> > font information from the root element instead.
> >> >
> >> > However if I just insert an element manually the font follows the pgftag
> >> > correctly.
> >> >
> >> > Does anyone have any idea what could be causing this?
> >> >
> >> > Thanks,
> >> >
> >> > Noah
> >> > _______________________________________________
> >>
> >_______________________________________________
> >
> >
> >You are currently subscribed to Framers as lprice at
> >
> >Send list messages to framers at
> >
> >To unsubscribe send a blank email to framers-unsubscribe at 
> >
> >or visit
> >
> >
> >Send administrative questions to lisa at Visit
> > for more resources and info.
> Lynne A. Price
> Text Structure Consulting, Inc.
> Specializing in structured FrameMaker consulting, application development,
> and training
> lprice at  
> voice/fax: (510) 583-1505      cell phone: (510) 421-2284

Reply via email to