40051 -2A stylesheet problem with chapter nos

kmccain · ‎Jul 27, 2012

I'm tasked to create a new book using the latest version of MIL-STD-2361D and the latest dstyle xsl-fo stylesheets. So far, most of the formatting I've tested looks pretty good, but I'm seeing a couple issues with the Chapter Title pages. For some reason, the Chapter Title pages are putting a double TM No in the header and are not producing the Chapter # in the title. I'm hoping someone who is familiar with the STD and Stylesheet might be able to help me figure out if this is my tagging error or a stylesheet issue. I am assuming that the stylesheet is supposed to auto-generate the chapter number since I see no attribute that I could populate with a chapter label in the chapter module elements (gim, mim, etc). I also can't figure out why it is doubling up the TM no in the header on these title pages.

Anyone using this combination or familiar with this stylesheet that could offer me some advice?

Thanks,KM

LynnHales · ‎Jul 27, 2012

Kim,

Respond back to me off line. Part of our task is support of 40051 related problems.

Lynn
---- Kim McCain <kmccain@triaddesignservice.com> wrote:
> I'm tasked to create a new book using the latest version of MIL-STD-2361D and the latest dstyle xsl-fo stylesheets. So far, most of the formatting I've tested looks pretty good, but I'm seeing a couple issues with the Chapter Title pages. For some reason, the Chapter Title pages are putting a double TM No in the header and are not producing the Chapter # in the title. I'm hoping someone who is familiar with the STD and Stylesheet might be able to help me figure out if this is my tagging error or a stylesheet issue. I am assuming that the stylesheet is supposed to auto-generate the chapter number since I see no attribute that I could populate with a chapter label in the chapter module elements (gim, mim, etc). I also can't figure out why it is doubling up the TM no in the header on these title pages.
> Anyone using this combination or familiar with this stylesheet that could offer me some advice?
> Thanks,KM
>
>
> -----End Original Message-----

KathleenReisler · ‎Jul 30, 2012

You can contact Allissa Leach (see contact info below). She has been quite helpful and can input any changes that are needed.

Allissa S. Leach

IT Specialist - Analyst

U. S. Army Aviation and Missile Life Cycle Management Command

AMSAM-MSS-LP

Building 5301, Room 1126

Redstone Arsenal, AL 35898-5000

256-842-6565

DSN 788-6565

kmccain · ‎Sep 05, 2012

Hi,

Lynn - I've e-mailed you a number of times since you responded to me regarding the chapter number issue, but haven't heard back from you so I'm just adding a follow-up here in case you never received my question.

The chapter number problem is fixed, but the main issue I am seeing now when composing to either a preview or to pdf is that none of the xrefs actually produce a clickable link. This is the first time I've used an XSL-FO type stylesheet with Print Composer (most of my previous books used FOSI - and these always worked fine) so should this work? Is this a problem in the stylesheet? or in my tagging?

Anyone else using the 40051 stylesheets have this problem? and if so, how did you fix it?

Thanks - KM

LynnHales · ‎Sep 05, 2012

Kim,

I apologize for not getting back with you, but we have been on a stop work
for the past month. We finally have a go ahead to work again last Friday.

The xref issue you are going to have to take to LOGSA who are the ones
officially responsible for the maintaining the style sheets. I looked at the
chapter numbering mainly because this could be either a DTD problem or style
sheet.

I know that TACOM is using the style sheets are have had some problems with
them.

Lynn

kmccain · ‎Sep 06, 2012

Kathleen,

Does Alyssa have an e-mail contact address? Does she support the DTD or the stylesheets?

Thanks,

Kim

kmccain · ‎Sep 06, 2012

Lynn,

Can you tell me how to contact LOGSA? I went to their official website and it isn't obvious to me how I should proceed. I did see a contact on the AMCOM publications website, but they don't say they support the 2361D version of the DTD and stylesheet. Should I e-mail them anyway? or maybe I should go through our TACOM contact to report the issues?

Any advice?

KM

ptc-5375972 · ‎May 09, 2013

Was the ever resolved?

If not, there is a bug in the XSL-FO itself. The routine that built the TOC is calling a routine that loses the stack. I was able to fix it by commenting out that routine and using one earlier that worked. The problem was noticeable in the C version when a volume tag was applied. I did note the fix back to IMMC and it is likely fixed. It could not correctly assign the WP numbers (was off by one).

If you have to debug the FO it is helpful to locate the module responsible for outputting that section of the document. The FO design is elegant and modular so this is not actually hard to do.

I've since moved to a new job and am not working with 40051 at the moment.

Len Bullard

Teledyne Brown Engineering

kmccain · ‎Jun 20, 2013

Hi,

My general xref problems has been mostly resolved through my tinkering with the stylesheets, but I haven't had to generate the TOC until now. It does have problems.

It generates the correct WP ID reference for items in the TOC, but it doesn't generate any page number references for items at all. Instead, it just repeats the relevant WP ID for each entry in the TOC.

I looked at the XSL and don't really see where those page numbers might be pulling from either, but admittedly, I haven't really had much time to look at it. The WP-pgnos are being created correctly (mostly) in the actual WP page footer although there a few places where the blank page reference isn't being generated for a 1-page WP (even though most of the WPs are referencing the same page template. Some seem to be OK, others are not.)

Most of the issues I've run into have, I believe, been reported to LOGSA by my customer. I just haven't seen any fixes.

Anyone dealt with this TOC problem?

KM

RobertWilliams · ‎Jun 21, 2013

From what I've heard (since LOGSA DTD/Stylesheet file set was mentioned), the Chapter page problem is fixed in Version 1.9 of the LOGSA stylesheet.

CAVEAT - What I've heard is only anecdotal, as I'm still using V 1.8, because I found that V 1.9 had other probs (content running off PDF pages w/PrintComposer - WarnSum and Alpha Index, to name two.) We've stayed with V 1.8 because bad Warn Sum is a show stopper for us.

FYI - We (a small TM outfit) don't edit DTDs or XSLT files for our XML TM projects, as we'd have to re-apply edits every time they changed at LOGSA, not to mention that our delivered PDF TMs would differ from what was generated by our gov't tech writer counterparts on their systems using the 'stock' LOGSA files. I'm curious about how you make editing their DTDs and XSLT files work in a non-aggravating way?

Regards all,

Bob W.

Bristol, RI, US

kmccain · ‎Jun 24, 2013

Bob,

First, I never edit DTDs unless directed to by the owner of such.

As for tinkering with the stylesheets (we are using v1_0 for 2361D DTD) - We did explain to our customer that making stylesheet changes was not considered good policy for the same reasons you stated, although I do know of companies that maintain their own customized versions of the LOGSA files.

The changes I've made to our copy of the stylesheets are fairly minor and were precipitated by specific comments from a reviewer about format issues in the PDF output that they were adamant about. I weighed my choices and decided that it would just be easier to automate some of these by modifying the stylesheet as opposed to having to manually fix the PDF files (as we were advised to do) each time we composed multiple books for their review.

KM