[bloggerDev] Re: Newline markup formatting changed - Pete Hopkins ♬☠ - com.googlegroups.bloggerdev

7 messages in com.googlegroups.bloggerdev[bloggerDev] Re: Newline markup forma...

From	Sent On	Attachments
Daniel Jalkut	28 Jun 2008 12:56
Daniel Jalkut	28 Jun 2008 14:00
Pete Hopkins ♬☠	28 Jun 2008 18:32
Daniel Jalkut	28 Jun 2008 21:50
Pete Hopkins ♬☠	30 Jun 2008 11:49
Pete Hopkins ♬☠	31 Jul 2008 16:12
Daniel Jalkut	31 Jul 2008 16:48

Subject:	[bloggerDev] Re: Newline markup formatting changed
From:	Pete Hopkins ♬☠ (phop...@google.com)
Date:	06/30/2008 11:49:21 AM
List:	com.googlegroups.bloggerdev

On Sun, Jun 29, 2008 at 12:50 AM, Daniel Jalkut <jal...@gmail.com> wrote:

Thanks for the info. I am glad you guys decided to revert the behavior. Makes it easier for me ;)

I was poking through the code for the new editor and noticed that we're creating \n for newlines made with the new editor. I'd like to keep this because it makes the generated HTML in the blog easier to read.

(Note that this does not break the <pre> bug from this weekend, as the new editor does not replace \ns with s in <pre> tags.)

I would recommend ignoring any newlines you get in an entry, as they are definitely not significant. As I mentioned before, I think that it's a bug that we treat them as significant on the way back in.

I appreciate the challenges of using a single feed for both HTML syndication and for the AtomPub clients. But what it makes me wonder is if it wouldn't make sense to offer a different collection URL for AtomPub editors. Something that could access the "raw" material and therefore have a chance at presenting the exact same content that the web interface does.

I like the idea of Blogger not automatically converting newlines to ... although ... if you "fix" this issue, I hope you'll give some thought to the idea that users are by now quite used to being able to send chunks of text separated by double-newlines, and having those interpreted by Blogger in a way that sets those chunks visually as "paragraphs".

Does MarsEdit send tags or newlines? I'd like to get into the habit of having API clients send HTML, with its whitespace semantics.

If you (and anyone else out there, please chime in) are relying on being able to send \ns in the entry and have those converted to s, we might have to tie the ignore-\n behavior to some sort of format change (perhaps the upcoming AtomPub 1.0 endpoint for Blogger).

WordPress and other systems also apply a set of default "manipulation" to the incoming HTML, to convert the plain newlines into the appropriate markup. I don't think most users mind this, but the tags that Blogger is inserting are not particularly sophisticated, I think because they are mainly for presentation at render-time.

In summary, I wouldn't mind, and I don't think most users would mind, if instead of the "ugly" linebreak tags, Blogger was to massage incoming text by wrapping double-newline separated text with tags (with appropriate newlines preserved for pretty editing).

This is something I'm looking into. I definitely prefer tags to s, though the code to do this without trashing complicated HTML is hairy.

Nevertheless, I think that this is an issue for API clients. I'd prefer for you to generate the HTML for s or whatever and send it to us, rather than send newlines and have us interpret them.

That being said, if there's pushback and you want to use our algorithms for linebreaking/paragraphing, perhaps that can be triggered by an additional attribute or special content type.

-- Pete