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

Unexpected carriage return are added in some cases #534

Open
ClaudiaCAUSSE opened this issue Oct 18, 2024 · 1 comment
Open

Unexpected carriage return are added in some cases #534

ClaudiaCAUSSE opened this issue Oct 18, 2024 · 1 comment

Comments

@ClaudiaCAUSSE
Copy link

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please have a look to the support pages of our website : http://m2doc.org/support/

Current behavior

When we have a link in a cell, M2DOC adds a carriage return before the link:

;<td><a href="TrainingComponent.DoC.MyPIDSToTest.DocumentPurpose"><b>Mon nom de lien</b></a></td>

image

The problem is also present on the following cases :

  • before bullet list =>
    Udgshqdf dqfk eztdef edzdf:<br/><ul>
	<li>Nshfdhf ruefif, fflgig mrkgqj hdsj yruqfg
  • before images => <b>Lzydgsf</b>.<br/><center><img src="reqif_files\TrainingComponent\TrainingComponent.DoC.MyPIDSToTest\image1.jpg" width="100%"/></center>
  • after the last text before a requirement.=>the requirement name itself.<br/>
  • after special character => mon caractère à tester est %<br/>

In fact every time we have the
tag, it will generate an unexpected carriage return.
In the following example, we have the expected carriage return underlined in yellow and the unexpected carriage return displayed with red rectangle :

  For bullet cases :

image

  For images :

image

  For include widgets :

image

  After special character :

image

So it seems that every time we had '<br/>', M2DOC generate an unexpected carriage return.

Expected behavior

image
image

Minimal reproduction of the problem with instructions

See this zip file:
Carriage_return_problem.zip

What is the motivation / use case for changing the behavior?

Users want to have the same look as in our product

Environment

M2Doc version: We detected the problem in version 3.3.2 but it is still present in version 3.3.3.
Eclipse version: 4.29 for the 3.3.2 of M2DOC and Capella 7.0.0 for the 3.3.3 of M2DOC
Platform version: Windows 10

@ylussaud
Copy link
Collaborator

Thank you for reporting this bug and attaching a reproduction test case.

ylussaud added a commit that referenced this issue Nov 5, 2024
ylussaud added a commit that referenced this issue Nov 5, 2024
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

No branches or pull requests

2 participants