Re: [dita] Groups - Sample PDF uploaded

[Kristen James Eberlein <kris@eberleinconsulting.com>]

We use Antenna House to render the spec, although as of yet we have not 
used any of its proprietary features. This is a lower priority issue 
than others at this point.

Best,
Kris

Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
www.eberleinconsulting.com
+1 919 682-2290; kriseberlein (skype)

On 6/1/2015 9:22 AM, Eliot Kimber wrote:
> * Is there a way to suppress the auto-generated text "on page"
>          when the cross reference is to something that will be rendered
>          on the same PDF page?
>    
>
>
> This is not possible using XSL-FO and a one-pass process. It's an example
> of "layout-driven formatting" that requires of knowledge of where two
> objects will be rendered relative to each other in the paginated document,
> knowledge you can't have at FO generation time in a one-pass process.
>
> Using multiple passes it is, of course, possible, but to date nobody has
> implemented general support for multi-pass FO processing with the OT (but
> it is possible using proprietary features of FOP, AH, and XEP and there is
> an open-source project that provides general support for for FOP and AH
> that could be integrated with the PDF2 transform).
>
> Cheers,
>
> E.
> ----
> Eliot Kimber, Owner
> Contrext, LLC
> http://contrext.com
>
>
>
>
> On 5/30/15, 7:22 AM, "Kristen James Eberlein"
> <kris@eberleinconsulting.com> wrote:
>
> >   
> >     
> >   
> >   
> >     I am going to add some contents here, since I am familiar with the
> >     content. (And am procrastinating on cleaning my house before my
> >     cleaning lady arrives.)
> >     
> >     Folks, when you provide feedback on the spec formatting, please be
> >     sure and include not just the page number, but also the number and
> >     title of the topic. For example, "2.5.4.1 RELAX NG document-type
> >     shell: Coding requirements".
> >     
> >     Bob, here's my quick summary; almost everything concerns cross
> >     references:
> >     
> >       
> > * Cross references to <dlentry> elements are not being
> >         rendered as links. That happens out-of-the-box with HTML output,
> >         and I think Robert and I had forgotten that the PDF style sheets
> >         would need to be tweaked to accomplish that.
> >       
> > * Including the auto-generated text "on page" for <xref>
> >         to topics in the content model appendix just does not work.
> >         Let's you and I and Robert put our heads together about this
> >         one.
> >       
> > * Is there a way to suppress the auto-generated text "on page"
> >         when the cross reference is to something that will be rendered
> >         on the same PDF page?
> >       
> > * We lack styling for the different levels of an unordered list,
> >         except for indentaton. (Lower priority)
> >       
> > * Regarding the item on page 392, I'm leaving that one to
> >         Robert. (I'm not brave enough to venture into that topic.)
> >       
> >     
> >
> >     
> >     Best,
> >       Kris
> >       
> >       Kristen James Eberlein
> >       Chair, OASIS DITA Technical Committee
> >       Principal consultant, Eberlein Consulting
> >       www.eberleinconsulting.com <http://www.eberleinconsulting.com>
> >       +1 919 682-2290; kriseberlein (skype)
> >       
> >     
> >     On 5/29/2015 4:53 PM, Hudson, Scott
> >       wrote:
> >     
> >     
> >       
> >       
> >         Hi Bob, et al,
> >         
> >         
> >         I noticed the following issues in the PDF, which may be
> >           content or rendering issues:
> >         
> >         
> >         Pg 37 xref for See @deliveryTarget not active: @print
> >           Specifies whether the topic should be included in printed
> >           output. Note: Beginning with DITA 1.3, the @print attribute is
> >           deprecated. It is replaced with a conditional processing
> >           attribute: @deliveryTarget. See @deliveryTarget for more
> >           details.
> >       
> >     
> >
> >     <kje>This is a conref to a
> >       <dlentry>.</kje>
> >     
> >       
> >         
> >         
> >         Pg 47 Alignment on last cell of row 3 (Excluded)
> >       
> >     
> >
> >     <kje>Removed a @char attribute. Had to
> >       look up what the @char attribute does.</kje>
> >     
> >       
> >         
> >         
> >         Pg 56 Odd xref for 2 and 5. Is this intended? Should this
> >           be labeled step 2 or step 5 or something?
> >       
> >     
> >
> >     <kje>Added the word "item" before the
> >       <xref>. Bob, is there a way that we can suppress the
> >         auto-generated text "on page" when the cross reference is to
> >         something on the same page?</kje>
> >     
> >       
> >         
> >         
> >         Pg 91 referenced element and referencing element appear to
> >           be links, but not active. If this is formatting for terms,
> >           they either need to be active (if blue color), or we should
> >           change the formatting to black bold italic or something. It is
> >           confusing to users if something appears to be a traversable
> >           link, but is not.
> >       
> >     
> >
> >     <kje>This is a conref to a
> >       <dlentry>.</kje>
> >     
> >       
> >         
> >         
> >         Pg 159 more inactive links: Module inclusions, Content
> >           constraint integration
> >       
> >     
> >
> >     <kje>This is a conref to a
> >       <dlentry>.</kje>
> >     
> >       
> >         
> >         
> >         Pg 185, 186, 187, 190Š (seems true for all instances in
> >           doc)  inactive link: outputclass
> >       
> >     
> >
> >     <kje>This is a conref to a
> >       <dlentry>.</kje>
> >     
> >       
> >         
> >         
> >         Pg 236 inactive link (may be intentional, but how do we
> >           want to handle deprecated content?) query (DEPRECATED)
> >       
> >     
> >
> >     <kje>This is a conref to a
> >       <dlentry>.</kje>
> >     
> >       
> >         
> >         
> >         Pg 237 inactive link: spectitle, mapkeyref, collection-type
> >       
> >     
> >
> >     <kje>This is a conref to a
> >       <dlentry>.</kje>
> >     
> >       
> >         
> >         
> >         Pg 392 Footnote word is wrapped oddly. Shouldn¹t it have
> >           the number of the footnote it refers to, instead of the text
> >           ³Footnote²?
> >       
> >     
> >
> >     <kje>Leaving this to Robert. He's the
> >       only person brave enough to work in this topic.</kje>
> >     
> >       
> >         
> >         
> >         Pg 402 bullet alignment in row 2, col 3. If sub-bullets,
> >           they should be a different character.
> >       
> >     
> >
> >     <kje>We currently do not use different
> >       characters for different levels of lists. I'd mark this as a
> >       nicety that we can consider once the pressing items are fixed.</kje>
> >     
> >       
> >         
> >         
> >         Pg 409 (Appendix C) the ³on page" numbers is pretty
> >           horrible from a usability perspective. It makes it so you
> >           can¹t read the content model. Not sure how to fix this, but I
> >           think it will be an issue.
> >         
> >         
> >       
> >     
> >
> >     <kje>It would be good to change the way
> >       <xref> to topics are rendered here in the content model
> >       appendix. Not sure whether the best way to do that is modify the
> >       markup in the topics (which are generated) or to change the style
> >       sheets. Bob, maybe you and I and Robert can talk about this.</kje>
> >     
> >       
> >         
> >         
> >         
> >           
> >             
> >               Thanks and best regards,
> >               
> >                 
> >               Scott Hudson
> >               Senior Consultant
> >               Comtech Services Inc.
> >               303-232-7586
> >             
> >           
> >         
> >       
> >       
> >       
> >       
> >         
> >           From: <dita@lists.oasis-open.org>
> >           on behalf of Robert Thomas
> >           Date: Friday, May 29,
> >           2015 at 2:15 PM
> >           To: "dita@lists.oasis-open.org"
> >           Subject: [dita] Groups
> >           - Sample PDF uploaded
> >         
> >         
> >         
> >         
> >           Submitter's message
> >             More fixes
> >             -- Mr. Robert Thomas
> >             
> >               
> >                 
> >                   Document Name:
> >                     Sample
> >                       PDF
> > <https://www.oasis-open.org/apps/org/workgroup/dita/document.php?document_
> > id=55764>
> >                     ________________________________________
> >                     No description provided.
> >                     Download
> >                       Latest Revision
> > <https://www.oasis-open.org/apps/org/workgroup/dita/download.php/55764/lat
> > est/dita-1.3-specification-base.pdf>
> >                     Public
> >                       Download Link
> > <https://www.oasis-open.org/committees/document.php?document_id=55764&wg_a
> > bbrev=dita>
> >                     ________________________________________
> >                     Submitter: Mr. Robert Thomas
> >                     Group: OASIS Darwin Information
> >                     Typing Architecture (DITA) TC
> >                     Folder: Support materials
> >                     Date submitted: 2015-05-29 13:15:22
> >                     Revision: 1
> >                   
> >                   
> >                 
> >               
> >             
> >           
> >         
> >       
> >     
> >
> >     
> >   
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe from this mail list, you must leave the OASIS TC that
> > generates this mail.  Follow this link to all your TCs in OASIS at:
> > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php