You are viewing a single comment's thread from:

RE: Darstellungsprobleme beim Hive-Frontend? =/= Display problems at the Hive frontend? GER-ENG

in Deutsch D-A-CH3 days ago

I believe that this problem is caused by failing to leave a blank line after the image. Which is a standard in the Markdown language. Because Hive uses Markdown for saving text. Then frontends convert it to HTML. But different frontends use different converters. So PeakD have tweaked their converter to handle the missing blank line. As have Ecency. But if you want consistent results across all frontends, you should stick to basic Markdown rules.

Unfortunately, I can't find an article that explains this on Hive. Though I know that I have read one here before. Anyway, the thing that stood out for me is that different "blocks" of content should always be separated by blank lines. So this applies to images, headings, lists etc.

Of course, many Hive frontends allow HTML as well as Markdown. But it's always risky to mix the them. So if you don't want to use blank lines around images, you can switch to the < IMG > tag instead.

Sort:  

By the way, I checked the Edit History for your earlier post. And it shows that the corrected image is due to adding a blank line. Both versions have that < b / > HTML tag. Which is meaningless in that context and it's ignored by the frontend.

I think I just need to leave out the < b / > code and things will be fine. I started adding it some months ago because there was no space line under my photos, and that actually helped.

In that case, change the b/ to br/ and all will be good. The HTML tag for line break is br. Some interpreters insist on a closing /. But that's increasingly rare. So < br > without the spaces is the usual way to put a new line in Markdown without actually pressing Enter twice.

And I thought this stuff I've learned would never be useful! Thank you for the opportunity to flex my old grey cells.

!BBH

thanks for the head-ups. however, I am still wondering why things keep changing. but well, that is the pinch of salt in the soup of life:)

I can only assume that it's something to do with changes to the Hive blog source code. But checking that code is well beyond my capability.


Your comment is upvoted by @topcomment
image.png

More info - Support @topcomment - Discord

That is what I figured too. But it wasn't a problem until recently, so I am wondering what has changed. But well, I guess I won't change my older post accordingly and will have to live with the fact that they all will look a little disfigured :)

Thanks for stopping by and bringing things into the right perspective!