#5620 Notification mail: Paragraph formated as heading

unreleased
duplicate
nobody
None
Mail
nobody
2015-02-23
2013-01-16
Anonymous
No

Originally created by: t_hoffmann

Sometimes paragraphs are formated as headings in notification mails. For example, the second post in https://sourceforge.net/p/texstudio/discussion/907840/thread/028c16a1/ produced the following html code in the mail

<div class="markdown_content"><p>To reset the configuration just delete texstudio.ini:<br />
<a href="https://sourceforge.net/apps/mediawiki/texstudio/index.php?title=Frequently_Asked_Questions">https://sourceforge.net/apps/mediawiki/texstudio/index.php?title=Frequently_Asked_Questions</a></p>
<h2 id="but-thats-likely-not-related-to-your-syncing-issue-have-you-changed-your-source-file-after-the-last-compilation-syncing-works-via-synctex-which-can-only-relate-the-line-numbers-of-the-source-to-the-pdf-during-compilation-if-you-change-the-source-afterwards-the-line-numbers-may-not-match-anymore-and-you-will-end-up-in-the-wrong-place">But that's likely not related to your syncing issue. Have you changed your source file after the last compilation? Syncing works via synctex, which can only relate the line numbers of the source to the pdf during compilation. If you change the source afterwards the line numbers may not match anymore and you will end up in the wrong place.</h2>
<p><a class="" href="https://sourceforge.net/p/texstudio/discussion/907840/thread/028c16a1/?limit=25#2233">How to reinstall TeXstudio</a></p>
<hr />
<p>Sent from sourceforge.net because you indicated interest in <a href="https://sourceforge.net/p/texstudio/discussion/907840/">https://sourceforge.net/p/texstudio/discussion/907840/</a></p>
<p>To unsubscribe from further messages, please visit <a href="https://sourceforge.net/auth/prefs/">https://sourceforge.net/auth/prefs/</a></p></div>

Note the large <h2> section.

Discussion

  • Dave Brondsema

    Dave Brondsema - 2013-08-26
    • status: open --> duplicate
    • Milestone: limbo --> forge-sep-06
     
  • Dave Brondsema

    Dave Brondsema - 2013-08-26

    Pretty sure this is the same as [#5693] and is fixed now

     

    Related

    Tickets: #5693


Log in to post a comment.