Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

publishToConfluence - some code blocks are generated as txt instead of requested language and loose linebreaks #1355

Closed
tkleiber opened this issue Feb 1, 2024 · 1 comment · Fixed by #1358

Comments

@tkleiber
Copy link

tkleiber commented Feb 1, 2024

Describe the bug
We try to change from doctoolchain from 2.1.0 to 3.2.2.
We have some html code blocks, which are generated in 3.2.2 as txt block instead of the used markup.

To Reproduce

  1. Use following code
[source, html]
----
<af:button id="_exc" icon="/adf/ikb.adf.basis.ui/images/excel.gif">
           <af:exportCollectionActionListener type="excelHTML"
                                               exportedId="_t1"
                                               exportedRows="all"
                                               filename="termine.xls"
                                               title="Kundenbezogene Termine"/>
</af:button>
----
  1. Generate with 2.1.0 to Confluence, you see html output:

2_1_0

  1. Generate with 2.1.0 to Confluence, you see txt output and removed linebreak:

3_2_2

Expected behavior
The code block should be formatted in the requested language definition and should show all linebreaks, which exists in the code.

Screenshots
See above

Configuration

  • docToolchain version: 3.2.2
  • OS: SuSE Enterprise Linux
  • Browser: Edge
  • Relevant SDK Versions: openjdk version "17.0.9" 2023-10-17
@PacoVK
Copy link
Collaborator

PacoVK commented Feb 1, 2024

Thanks for reporting, i took a closer look and it relates to #1349 i will provide a fix soon for that :)

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 a pull request may close this issue.

2 participants