-
Notifications
You must be signed in to change notification settings - Fork 193
Meeting minutes 2023 03 09
Attendance:
- Robert Anderson,
- Jarno Elovirta,
- Roger Sheen,
- Radu Coravu,
- Lief Erickson,
- John Pashley,
- Frank Wegmann,
- Chris Papademetrious,
- Julien Lacour,
- Bill Gamboa
- Josh Johnson
- John Kirkilis
- Stefan Jung
- Will MacLean
- 4.0.2 released February 18
- 4.0.3 project board: https://github.com/orgs/dita-ot/projects/41
- Currently only contains one issue:
- 4131 Don't log about missing target when target is external
Discussion of how to handle severity of error messages. Could we make this configurable, so users could change severity of certain messages in a plug-in, or by changing something in configuration.properties
?
Jarno points out that each message ID indicates default severity, so could be weird if an ID suggests something is an error, but it's reconfigured to be treated as info only.
Project board for next release: https://github.com/orgs/dita-ot/projects/36
Ops board: https://github.com/orgs/dita-ot/projects/39
Robert reports on discussions in DITA TC around syntax diagrams, exploring background of how (if?) those are still used.
Jarno working on changes in LwDITA, Saxon 12 version bump that would warrant a minor (4.1) release before the autumn. Also XSLT3 changes would be nice to use in default plug-ins. Shouldn't be a huge change for most users, but could affect anyone who has copied & modified templates from older toolkit versions, as their overrides would be harder to compare to defaults.
https://github.com/dita-ot/dita-ot/issues/4123
Could use 4.1 as an opportunity to bump other dependencies too, like FOP, etc.
- Markdown syntax reference
- Jarno & Roger working on revisions
- Goal is to clarify which bits of syntax are common, which specific to MDITA vs. Markdown formats
- Up until now, maintained in wiki & copied to docs
- Considering alternatives to simplify maintenance
- Roger does not have permission to update plug-in wiki in Jarno's namespace
- Project files: John unclear on difference between publication & deliverable
- May need to clarify this further
- Deliverable is parent (like "Product A User Guide Draft PDF")
- contains
context
withid
/input
/profile
,output
, &publication
- contains
- Publication is effectively "type of output" (like "Draft PDF")
- contains
transtype
, parameters, and optional additionalprofile
- contains
- See https://github.com/dita-ot/dita-ot/discussions/4147
- Locking Slack
#general
channel in favor of GitHub Discussions - Schema support for markdown parser:
https://github.com/jelovirt/org.lwdita/pull/141- Jarno considering adding a schema reference to YAML header of Markdown topics to explicitly state how it should be parsed
- Would be slightly more extendable than current
@format
method without needing to fork LwDITA plug-in - Need to make it clear how this differs from setting
@format
(Currently schemas only work with@format="markdown"
)
Project boards: https://github.com/orgs/dita-ot/projects/
Time to go through pull requests, issues tracker, determine how to handle open issues.
Several mentioned recently:
- 4086 Go through all DITA OT information messages, avoid reporting some and increase severity of others
-
4100 PR: Log the current deliverable when publishing DITA-OT project
- Fixes 3948
-
4142 PR: Support note type
other
in HTML output - 4144 Techcomm includes still reference the non-pubid URNs
View the latest DITA Open Toolkit docs at www.dita-ot.org/dev.