Skip to main content
R
RickSchoen10-Marble
10-Marble
September 24, 2015
Question

Using an attribute value to output a graphic in FOSI

  • September 24, 2015
  • 2 replies
  • 2603 views

We are using Arbortext Editor 6.1 M020. We are beginning to use MathML instead of ATIMath. We are using MathFlow 2.0b for Arbortext as our equation editor. I am creating a FOSI that will allow our copyeditors to produce a very lightly formatted manuscript (PS or PDF) for internal QC purposes. An example of an equation is:


<disp-formula id="df1" medium="all">

     <mml:math altimg="C:\Users\rschoen\AppData\Local\Temp\MMLIMG2768143.png" display="block"> ...

     </mml:math>

</disp-formula>


Since MathFlow has already created an image of the equation for us, I would like to have the FOSI use that to produce the output manuscript. I would like to grab the value of the altimg attribute of the mml:math tag and have that image displayed in the output but I'm not sure whether that is possible. And, if it is possible, how to go about doing it.


Can anyone help?


Thanks,

Rick Schoen


2 replies

S
SuzanneNapoleon12-Amethyst
12-Amethyst
September 25, 2015

Hi Rick,

Does the DTD have one or more elements for graphics? If so, is the file name or entity reference method used for specifying the graphic file name?

Suzanne Napoleon

    R
    RickSchoen10-MarbleAuthor
    10-Marble
    September 25, 2015

    Hi Suzanne,

    We have 2 elements for graphics: graphic and inline-graphic. For both elements, we use a file name reference method for specifying the graphic file name:

         <graphic xlink:href="fg15.eps"></graphic>

    or

         <inline-graphic xlink:href="ig1.tiff"></inline-graphic>

    Rick

    T
    TimPhelps12-Amethyst
    12-Amethyst
    November 13, 2015

    Rick,

        Did the answers provided resolve your issue?

    If so, could you indicate which one, or write how you resolved the issue and mark it as correct, so that the community can review this thread and see what is the correct answer?

    Terms & ConditionsCookie settingsAccessibility statement