Re: [dita-adoption] FOR REVIEW: Updated "How-to" document on using the TC "generic" PDF stylesheet

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

Hi, Stan.

Some quick feedback and a question:

• You can download the Liberation Sans font without using an Adobe account at https://www.fontsquirrel.com/fonts/liberation-sans
  
• "The plug-in has a couple of hard-wired resources that would need to change for Adoption TC use" -- OASIS logo and footer text.
• No guaranties about styling all DITA elements; the oasis-open.pdf.org plug-in only correctly styles the markup that is used in the DITA 1.3 spec and the committee notes that have been published by the DITA TC. This means that no attention has been paid to styling task-based information.
  

Re the hard-wired resources, what OASIS template is the Adoption TC planning to use? I assumed that the Adoption TC was thinking of issuing committee notes instead of white papers ...

Best,
Kris

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

On 2/9/2020 10:23 AM, Dr. Stanley Doherty wrote:

> Greetings --
>
> Per our discussion last Tuesday at the ATC meeting, I have updated my little "how-to" document on installing and using the TC "generic" stylesheet for ATC whitepapers. Please play with it and send review comments to the ATC list before our next meeting (Tuesday, March 3).
>
> The generated PDF is at:
> > https://www.oasis-open.org/apps/org/workgroup/dita-adoption/download.php/66664/bookmap_atc_install-tc-stylesheets.pdf
> >       
> The updated sources are in the ZIP:
> > https://www.oasis-open.org/apps/org/workgroup/dita-adoption/download.php/66663/atc_install-tc-stylesheets_02.zip
> >       
> Discussion: No big issues. No surprises.
>
> 1. I installed the Adobe Liberation Sans font.
>
> 2. I integrated the bookmap metadata, prelims, appendices, and libraries from the ./template 
>    folder of the TC plug-in at:
>    > https://github.com/oasis-open/dita-stylesheets
>
> 3. I cloned and renamed the ./resources/key-definitions.ditamap and ./resources/subjectScheme.ditamap
>    files. Where appropriate, I changed values there to point to the Adoption TC name. We'll need to 
>    review these in more detail for TC-specific values. 
>
> 4. I generated output from DITA-OT using the command line:
>    > ..\..\dita-ot-3.4\bin\dita -i bookmap_atc_install-tc-stylesheets.ditamap -f oasis-pdf-generic -Dpdf.formatter=fop
>
> Issues:
>
> 1. The plug-in has a couple of hard-wired resources that would need to change for Adoption TC use:
>
>    a. org.oasis-open.pdf/cfg/common/vars/en.xml
>
>       <!-- Cover page logo-->
>       <variable id="logo Image Path">Customization/OpenTopic/common/artwork/OASISLogo-v2.0.jpg</variable>
> 	  
>    b. org.oasis-open.pdf/cfg/common/vars/en.xml
>
>       <!-- Footer text -->  
>       <variable id="Committee note track">Non-Standards Track</variable>
>       <variable id="Standards track">Standards Track Work Product</variable>    
>       <variable id="OASIS TC document">DITA TC work product</variable>
>
> 2. The ./resources/subjectScheme.ditamap map did not have a controlled value for 
>    outputclass="documentTitle". I added it in the Adoption-specific version of 
>    the map, ./resources/subjectScheme_adoption.ditamap.
>
>    <subjectdef keys="values-outputclass">
>      <subjectdef keys="cover"/>
>      <subjectdef keys="notices"/>
>      <subjectdef keys="RFC-2119"/>
>      <subjectdef keys="documentStage"/>
>      <subjectdef keys="stageDate"/>
> 	 <!-- Added the next subject - 02-09-2020 SDoherty -->
>      <subjectdef keys="documentTitle"/>	
>    </subjectdef>	 
>
> 3. The @relcolwidth values for <choicetable> are not being rendered correctly. 
>    <choicetable id="choicetable_uqj_2rl_fkb" relcolwidth="3.0* 11.29*">
>    In the default FOP output, the left column is 1/4 the width of the right column. 
>    In this plug-in FOP output, the columns are identical in width. There may be some
>    Antenna House dependency? 
>
>
>
>