-
Notifications
You must be signed in to change notification settings - Fork 193
Meeting minutes 2024 05 02
Attendance: Robert Anderson, Radu Coravu, Jarno Elovirta, Roger Sheen, Will MacLean, Alex, Lief Erickson, Kerry Langford, John Pashley, Josh Johnson, Amit Siddhartha, Frank Wegmann, Jason Coleman
4.2.3 project board: https://github.com/orgs/dita-ot/projects/49
Could be released, no other pending issues right at the moment. Very little content but good to not hold it back.
Project board for next release: https://github.com/orgs/dita-ot/projects/46
Recent discussion around error logging; changing severity of a Java message doesn't change result: https://github.com/dita-ot/dita-ot/issues/4468 Summary -- as always, error messages / logging decisions are annoying. Our simple logging framework for Java is quite simple. But it has an alternative pattern you can use. By using builder pattern, we might be able to do this. Only problem, when you move a message from Error to Fatal, logging frameworks don't have something called fatal; they expect you to throw an Exception at that point. We throw that today in strict mode, for errors. So when we make this change, we need to also consider strict mode.
Also discovered while doing this, we have some warnings that are thrown as errors, message levels not consistent (like missing image one). Overall - something we'd like to have in next minor or major release, but requires a lot of small changes everywhere.
Continue discussion from last month: putting DITA XML into Markdown. Came up last week, and can really be a way to shoot yourself in the foot, but Jarno implemented in plugin. There are lots of limitations -- if element exists in both HTML and DITA, it generally treats as HTML (so cannot use CALS DITA table). Also limitation that you must have well-formed / closed tags. Sort of work in progress, but released and available. Determining whether to use HTML or DITA for elements with like names - really a guessing game now. Fortunately in most cases (p, ol, ul, lq, pre...) the elements are treated the same. It's out there now - if you install the latest lwdita plugin, you can try it out. But not exactly "supported" or "documented" and should be tagged as a foot-gun. That said, if you try it out and find issues, open them against the lwdita plugin, may be able to fix some of the corner cases and add some doc: https://github.com/jelovirt/org.lwdita When we have the next DITA-OT release that updates the plugin, will need to consider whether / how to document it in the main OT docs.
Release date for DITA-OT.Next ... preference would be to release somewhere summer-ish. Should keep up that cadence even if we do not have a lot to add. If we expect a next OT day, it's likely to be in Feb -- with our last release in Feb, and likely future in Feb, should probably target late summer for the one in the middle.
Ops board: https://github.com/orgs/dita-ot/projects/39
We finally shipped the FAQ issue, the oldest still-open one, thanks to help from colleagues at Nokia.
Over the horizon, still nothing official.
Converting from StratML format to DITA - is there anything in DITA-OT that could help with this? Had framework for it in Oxygen for a while, but moved to github repo.
Project boards: Project boards: https://github.com/orgs/dita-ot/projects/
Time to go through pull requests, issues tracker, determine how to handle open issues.
View the latest DITA Open Toolkit docs at www.dita-ot.org/dev.