Jarno Elovirta

Results 225 comments of Jarno Elovirta

It might make sense to make the expansion limit configurable in a property file. Then users can change that per DITA-OT installation.

:+1: I think profiling attributes should not be considered in creating unique link set.

This would require that we deduce from the file name that the output will be a map. My preference is to not use file names to choose the parser.

Do you have custom plug-ins or PDF2 customizations? Could you add a simple set of DITA files that can be used to reproduce this condition?

One challenge here is that none of the core developer have a Windows machine.

The changes seems small and are likely to not break backwards compatibility.

The gen-list module doesn't correctly add `format` information for `ToolbarsChunk.dita`.

If a copy-to source has chunk="to-content", it will not listed in normal copy-to map, because the processing assumes it will be dealt with in chunk processing. The code is _old_.

If we add the format information to chunk target in gen-list, it will be processed as a normal topic. It could be added in chunk processing, but that is implemented...

Fixed in #2207 for `develop` branch. The same fix cannot be used here because it changes preprocess step order.