Non-Printing Characters Rendering in Edgar

Answered

Comments

3 comments

  • Mike

    Hi Maureen!

    Thanks for sharing. That's a very interesting error, indeed. "LSEP" is the unicode character for a "line separator", or <br> in HTML. One thing it could be is your browser interpreting this character in your browser, i.e. you have a font installed that displays LSEP as a printing character that only Chrome detects. To figure out if this could be the case, try right clicking on the offending LSEP text and choose “Inspect”, then switch to the “Computed” tab on the right-hand panel. At the very bottom you should see a section labeled “Rendered Fonts” which will help you locate the offending font.

    Let me know if this resolves your issue or not, or if I've missed the mark. Thanks again and talk to you soon!

    0
    Comment actions Permalink
  • Maureen Ebbs

    Thanks Mike! Arial and Times New Roman were the only rendered fonts. But, we went through and deleted and re-added the hard returns and the issue is no longer occurring. Wondering if it might have just been something that came over funny when we transitioned the file from classic to Next Gen?

    0
    Comment actions Permalink
  • Mike

    No problem, Maureen. Thanks for the follow-up info. Happy to hear that re-adding the returns resolved the issue. You are likely correct, too, in your assumption. It's definitely possible that the transition interpreted that character in that manner but adding it in again resolved it. I'll bring this nuance up to our Product Team to see if we can test this.

    Either way, thanks again for your contributions and give me a holler if you need anything else. Happy Wednesday!

    0
    Comment actions Permalink

Please sign in to leave a comment.