Skip to content

Meeting minutes 2017 11 16

Roger Sheen edited this page Nov 16, 2017 · 2 revisions

DITA-OT Docs Call — November 16, 2017

Contents

Attendance

  • Kris
  • Roger
  • Shane

OT project status updates

The DITA-OT contributor call was held immediately prior to the docs call. Meeting minutes are available at https://github.com/dita-ot/dita-ot/wiki/Meeting-minutes-2017-11-16.

New issues since last call

26 new issues & pull requests were created since the last call, most of which have since been fixed.

Four remain open:

Fixed issues since last call

A total of 29 issues & pull requests were closed.

Of those, 10 were pull requests, including contributions by:

  • Eero Helenius
  • Lief Erickson (new, first-time contributor)
  • Lionel Moizeau
  • Robert Anderson
  • Roger Sheen
  • Shane Taylor
  • Stefan Eike

Project planning board review

The docs issue tracker at https://github.com/dita-ot/docs/issues currently lists 18 open issues, 167 closed.

Our GitHub Projects boards show the status of issues currently associated with each release milestone and serve as the primary planning overview for upcoming releases:

Discussion

The conference will be held from April 23–25, 2018 in Denver, Colorado.

  • Kris brings up the December 1 Call for Speakers deadline.
  • Kris and Shane hope to attend the conference and wonder whether we should try to arrange a docs meetup in Denver before or afterwards (if so, we'd need to begin planning soon).
  • Roger may not be able to attend due to teaching responsibilities in Austria around the same time, but would be happy to support a docs event remotely.

Source file refactoring questions

Roger asks for feedback on the source file refactoring work that remains following the ToC reorganization for 3.0.

Most of the legacy folders have been renamed in PR #185, but the question remains how to handle the user-guide/ folder, which serves as a container for various topics.

Consensus emerges around the idea that while a file structure that mimics the ToC hierarchy may be intuitive to users, it becomes a maintenance nightmare, so a more generic structure be preferable. We settle on renaming user-guide/topics/ for now.

Porting PDF customizations to 3.0

Shane recently ran into issues when migrating earlier custom PDF plug-ins to 3.0, filed as dita-ot/dita-ot#2835. Wonders whether it's a docs issue: if a certain file structure is required in the plug-in, we should mention that in docs.

Roger's understanding is that the PDF plug-in structure convention stems from the days of customization folders, but is by no means required, so plug-ins should still be free to use any internal structure in 3.0.

The issue may be related to the PDF transform's switch to preprocess2 in 3.0, which uses hashed filenames in the temp folder, so any prior assumptions about temporary file names may no longer be accurate.

Roger will try to test the attached plug-in.

Setting default image resolution for PDF output

Shane ran into issues when inheriting legacy projects with referenced images that used different image resolution values that led to inconsistent PDF output with FOP. He developed a customization that sets a default DPI value and reads dimension metadata from the image files and injects that into @height & @width attributes during preprocessing.

Shane wonders whether this sort of customization would be of sufficient interest to justify inclusion in the core toolkit?

Roger has run into similar issues in the past and still sees regular traffic on an old blog post he wrote on Scaling Images in PDF Output, so it seems this is something people still struggle with enough to search for solutions. Roger recalls XEP assumes a resolution of 120 dpi, and AntennaHouse may use different assumptions, so any changes would probably need to take these differences into account.

Shane will look into submitting a pull request with his changes.


https://github.com/dita-ot/docs/wiki/Meeting-minutes-2017-11-16


Created 2017-11-16 15:58