No problem. :)

Unfortunately, it is a bit of a hack. I would like to see this  
resolved by moving autop into its own plugin (see ticket #1038).

I'll be working on said plugin this afternoon.

~Arthus

P.S. My real name is Morgante Pell. :)

On Aug 7, 2009, at 4:50 PM, Andy C wrote:

>
> Arthus - thanks very much for the rapid response and the goodcode
> plugin
>
> Just tested in Google Reader and my blog and it works fine -
> http://nbrightside.com/blog/2009/08/07/what-you-see-is-what-you-get
>
> Now I no longer need to worry about whether my chosen theme uses autop
> () or not.
>
> Although I agree with Caius and you and think autop() is useful but
> Habari should always produce unaltered output and autop() should be
> applied via a plugin (not the other way round).
>
> On Aug 7, 6:58 pm, Caius Durling <[email protected]> wrote:
>> On 7 Aug 2009, at 17:55, Arthus Erea wrote:
>>
>>> I honestly would like to see us completely eliminate autop from
>>> core. If users want to have linebreaks automatically added, they
>>> would have two options:
>>> 1) Use a WYSIWYG plugin (yuck), but we do need to work on making a
>>> really good one.
>>> 2) Use an "autop" plugin, which inserts the breaks for both the
>>> theme and the ATOM feed.
>>
>> Seconded. Either remove it into a core plugin, or provide an (easy)
>> way to turn it off, either via the API (for other plugins) or via  
>> user
>> options.
>>
>> For instance, the markdown plugin uses a "hack" to try and make sure
>> autop isn't run on the post/comment output at all, because converting
>> linebreaks, then running it through the markdown parser would
>> seriously look odd (and be pointlessly dumb.)
>>
>> C
>> ---
>> Caius Durling
>> [email protected]
>> +44 (0) 7960 268 100http://caius.name/
> >


--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at http://groups.google.com/group/habari-dev
-~----------~----~----~----~------~----~------~--~---

Reply via email to