Skip to content

Conversation

@haxtibal
Copy link
Contributor

@haxtibal haxtibal commented Nov 3, 2025

Previously, RST was hard-coded.

Fix it by checking on a per-node basis if RST or Text rendering shall be used. It's not possible to do this on a per-source-file basis, since requirements for one source file may come from multiple documents and the MARKUP option is attached to that documents, not to the source file.

Fixes #2544.

@haxtibal haxtibal force-pushed the tdmg/fix_text_nodes_in_source_view branch from b16767b to 9c651e9 Compare November 3, 2025 15:19
Previously, RST was hard-coded.

Fix it by checking on a per-node basis if RST or Text rendering shall be
used. It's not possible to do this on a per-source-file basis, since
requirements for one source file may come from multiple documents and
the MARKUP option is attached to that documents, not to the source file.

Fixes strictdoc-project#2544.
@haxtibal haxtibal force-pushed the tdmg/fix_text_nodes_in_source_view branch from 9c651e9 to c9559fb Compare November 3, 2025 20:55
@haxtibal haxtibal changed the title Draft: fix(export/html): Consider MARKUP = Text option in source file view fix(export/html): Consider MARKUP = Text option in source file view Nov 3, 2025
Copy link
Collaborator

@stanislaw stanislaw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the 'get markup' part could go to the SDocNode class eventually but it is not important to do it right away.

@stanislaw stanislaw merged commit e93c3a5 into strictdoc-project:main Nov 4, 2025
33 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bug: SourceFileViewHTMLGenerator disregards MARKUP = Text configuration

2 participants