Work plan 2026: call for feature requests

[rdeltour]

Hi everyone!

The Pipeline team is currently working on the work plan for next year (2026).

If you have feature requests or opinion on what should be included to the project's objectives, we would love to hear from you!

Please let us know if possible before Thursday at the latest, so that we can try to integrate this in our work plan draft.

For any work item that you may suggest, we would ideally like to get a sense of the priority it is for you (is it a must have for you? something that you need now? in the coming years? or on the contrary something you see as an improvement but not critical?).

Thank you all!

[egli]

Where do I place these work items?

I have the following issues

• migrate the Pipeline1 scripts that SBS uses to Pipeline2
  • DTBookToLaTeX
    • there are some unmerged changes from me in the feature/largeprint-improvements branch that need merging
  • ConfigurableValidator
• Deal with our use of a Pipeline2 fork
  • this is mainly due to our use of the nordic migrator for dtbook to epub conversion
  • we should probably move to standard off-the-shelf dtbook-to-epub
• "Perfect" Ebraille
  • When converting dtbook to braille we use some xslt that uses some additional braille-specific markup
    • how can we integrate this in the dtbook-to-ebraille script?
  • create braille CSS for SBS
  • Integrate our local braille corpus with the dtbook-to-ebraille script

Whether or not these are issues for the pipeline team I'm not sure. Maybe they're more on the plate of SBS.

[rdeltour]

Thanks for the feedback Christian! This is exactly the kind of things we need to know, and here is a good place to share.
Some of your items seem to be specific to SBS, but not all. Let's discuss this more during our technical call.