Lost all my linebreaks

I hate it when I do that but since I havent found a solution, I just had to make the post visible again..sorry.

This URL?

https://www.kyramarios.gr/diary/

Looks fine here …

No, its not ok.

for example it was intended to look like this :
—————————————————————–
Uglyness
posted on 15th January 2005 in Tech

Well it seems my host is doing some server upgrading rendering this site unusable or at least, ugly.
I have no access to my files through ftp so I am helpless.
Please be patient or just ignore the nasty error messages you may get.
I apologize for the uglyness.
I hope it gets back to normal soon.
Maybe its an opportunity to make a redisign although I was waiting for the WordPress 1.5 release to do that.
Anyway, come back soon and it will be prettier I promise !
—————————————————————-

A line break after every fullstop.
Is that how it renders for you ?

Do you have any text formatting plugins activated?

This is how it looks to me:

https://www.orangeguru.net/download/kyramas1.jpg
https://www.orangeguru.net/download/kyramas2.jpg

FireFox Screenshots.

And I have no textformatting plugs activated in my site.

orangeguru:
Yes that the way it looks for me too. Both in FF and in IE6.

Kafkaesqui :
Yes. Markdown was active. And by deactivating it everything looks how I wanted them to look.

But I was wondering if there was a way of keeping it active without having it stealing my linebreaks !

Thanks.

This is actually a bug that got fixed.

The Markdown syntax says that to make a paragraph you must write *two* consecutive line breaks to create a blank line. If what you want is a line break, not a paragraph, you can put two spaces at the end of the line.

In previous versions of WordPress, the old Markdown included was not removing properly the default paragraph filter. If you want to get the old behaviour, you can comment out the three lines looking like remove_filter(..., "wpautop"); not far in the markdown.php plugin file. To comment a line, insert # or // at the start of the line.

Note that this may prevent some parts of the Markdown syntax from working correctly.

That did it !
Thanks