Robin
Bonjour @Wallon, I also wondered already about these additional double linebreak markers; these look to me like an erroneously and misleading added thing in transifex. Original html of your example reads:
<div class="paragraph"><p>3.Control Centre-→Session-→User Desktop Session click on <em>desktop-session.conf</em> and make the following changes
Startup delay "0"
Notification dialog "false"</p></div>No trace therein of explicit <br> tags, which would actually mean linebreaks in html as falsely marked by transifex.
Since in html simple linebreaks (like multiple successive blanks) don’t have any meaning and are not rendered by the browser (or more precisely: are rendered as a single blank, W3 standard calls it “collapsed”), these specific additional transifex linebreak markers can be ignored safely. In the English original these sentences are obviously meant to appear the way they do, as “running text” (hopefully I managed to translate this term properly from German „Fließtext” in the string instructions, which would suggest “floating text”, but I guess English speakers actually don’t say that, while what they understand by floating text is what we’d call „schwebende Textauswahl”; damn, translation can be really tricky sometimes). So you can add as many of these simple line breaks (or remove them) without any impact on the actually rendered layout of the html page.
If you actually want/need to have a linebreak in your translation inside a such a paragraph marked as “running text” in the string instructions, please try adding the html code tag <br> (or <br />), which should work both in modern browsers. You don’t need a closing tag for <br>, and the historical tag form for XHTML is <br />.
So there is nothing to be fixed in the original html here, but something should be improved by transifex. While, I guess they keep these intentionally, since you theoretically could set up CSS in a way that these (usually meaningless) line breaks are actually rendered.
Warning: Don’t add <p>…</p>, which would also add a full paragraph, instead of a single <br> for enforcing a new paragraph here: As you can see when inspecting the original html code, you’ll understand that transifex has cut off a set of <p>…</p> here already, so adding now this tag type to your text would result in tag soup like <p>…<p>…</p>…</p> instead of the proper form <p>…</p><p>…</p>`
After inspecting the source code, you could possibly add the tags in reversed order <\p>…<p> (this way closing the first paragraph opened outside visibility in the transifex entry by the </p> visibly in the entry, and starting a new paragraph, which then is closed outside visibility again. But I have no clue whether transifex will process this then as desired… Moreover this would require a deep understanding of the underlying html code structure already, which translators usually are not expected to have. So my suggestion is: try <br> using instead, which is a self closing html entity, more robust when not knowing nor seeing the surrounding tags at transifex in the editor’s entries.
You shouldn’t use the <br> to enforce additional line breaks inside a sentence, since browsers then will fail to render the running text properly. Use them merely to insert an extra paragraph whenever needed, e.g. for structuring or highlighting something.
In any case, if applying such html tag manipulation inside the transifex entries in your translation, please download “for use” and check out the result as described initially, whether it works and renders the way you had intended.
Windows is like a submarine. Open a window and serious problems will start.