From bruno at mkdoc.com Wed Nov 16 19:04:53 2005 From: bruno at mkdoc.com (Bruno Postle) Date: Wed Nov 16 19:05:08 2005 Subject: [MKDoc-dev] RSS auto-discovery and firefox 1.5 Message-ID: <20051116190452.GB2360@webarchitects.co.uk> With firefox 1.0.x, MKDoc rss feeds were detected and an icon appeared so they could be bookmarked. With the latest firefox 1.5 release candidate this icon doesn't appear anymore. The MKDoc fragment that no longer works: These two are ok: This blog suggests that link rel="alternate syndication" should work instead of just "syndication": http://weblog.philringnalda.com/2005/04/15/what-feeds-should-firefox-discover -- Bruno From chris at webarchitects.co.uk Thu Nov 17 11:42:45 2005 From: chris at webarchitects.co.uk (Chris Croome) Date: Thu Nov 17 11:42:54 2005 Subject: [MKDoc-dev] RSS auto-discovery and firefox 1.5 In-Reply-To: <20051116190452.GB2360@webarchitects.co.uk> References: <20051116190452.GB2360@webarchitects.co.uk> Message-ID: <20051117114245.GB23428@webarchitects.co.uk> Hi On Wed 16-Nov-2005 at 07:04:53PM +0000, Bruno Postle wrote: > > link rel="alternate syndication" should work instead of just > "syndication" OK, I have changed it to this, perhaps we should also consider serving RDF as application/rdf+xml -- the RFC went through for this last year [1]... is this MIME type supported by Firefox yet? We have been using application/xml because the spec says: The current mime-type recommendation for an RSS 1.0 document is application/xml. However, work is currently being done to register a mime-type for RDF (and possibly RSS). The RDF (or preferably RSS) mime-type should be used once it has been registered. http://purl.org/rss/1.0/spec#s5_mimetype Chris [1] http://www.ietf.org/rfc/rfc3870.txt -- Chris Croome web design http://www.webarchitects.co.uk/ web content management http://mkdoc.com/ From bruno at mkdoc.com Thu Nov 17 14:27:34 2005 From: bruno at mkdoc.com (Bruno Postle) Date: Thu Nov 17 14:27:45 2005 Subject: [MKDoc-dev] RSS auto-discovery and firefox 1.5 In-Reply-To: <20051117114245.GB23428@webarchitects.co.uk> References: <20051116190452.GB2360@webarchitects.co.uk> <20051117114245.GB23428@webarchitects.co.uk> Message-ID: <20051117142734.GA2196@webarchitects.co.uk> On Thu 17-Nov-2005 at 11:42 +0000, Chris Croome wrote: > On Wed 16-Nov-2005 at 07:04:53PM +0000, Bruno Postle wrote: > > > > link rel="alternate syndication" should work instead of just > > "syndication" > > OK, I have changed it to this, Confirmed, auto-discovery now works with firefox 1.5. -- Bruno From bruno at mkdoc.com Fri Nov 18 15:32:13 2005 From: bruno at mkdoc.com (Bruno Postle) Date: Fri Nov 18 15:32:17 2005 Subject: [MKDoc-dev] New modifiers for template designers Message-ID: <20051118153212.GS21347@mkdoc.com> MKDoc 1.6 CVS now has some new Petal modifiers to allow template designers more freedom when displaying text. The new modifiers use the same MKDoc::Text::Structured backend as the Text Component. This means that plain text strings can now be displayed in a variety of ways: The as_html_entities: modifier will add smartquotes and convert simple ascii constructs such as (c) to their rich text equivalents. Document Title The as_html_inline: modifier will do the same, but will also add inline tags such as strong or abbr.

Document Title

The as_html_blocks: modifier will do the same, but will add block level structures such as paragraph tags, lists etc...
Document Description
For full documentation of MKDoc::Text::Structured, see: http://search.cpan.org/dist/MKDoc-Text-Structured/ -- Bruno From chris at webarchitects.co.uk Fri Nov 18 15:57:11 2005 From: chris at webarchitects.co.uk (Chris Croome) Date: Fri Nov 18 15:57:13 2005 Subject: [MKDoc-dev] New modifiers for template designers In-Reply-To: <20051118153212.GS21347@mkdoc.com> References: <20051118153212.GS21347@mkdoc.com> Message-ID: <20051118155711.GA25576@webarchitects.co.uk> Hi On Fri 18-Nov-2005 at 03:32:13PM +0000, Bruno Postle wrote: > MKDoc 1.6 CVS now has some new Petal modifiers to allow template > designers more freedom when displaying text. > > The new modifiers use the same MKDoc::Text::Structured backend as the > Text Component. I think it makes sense to use this for the Rights, Publisher and Description metadata when it appears on a page. Will this also turn URIs into links and if not could this be an option? Chris -- Chris Croome web design http://www.webarchitects.co.uk/ web content management http://mkdoc.com/ From bruno at mkdoc.com Fri Nov 18 18:40:26 2005 From: bruno at mkdoc.com (Bruno Postle) Date: Fri Nov 18 18:40:36 2005 Subject: [MKDoc-dev] New modifiers for template designers In-Reply-To: <20051118155711.GA25576@webarchitects.co.uk> References: <20051118153212.GS21347@mkdoc.com> <20051118155711.GA25576@webarchitects.co.uk> Message-ID: <20051118184026.GA3408@webarchitects.co.uk> On Fri 18-Nov-2005 at 15:57 +0000, Chris Croome wrote: > > I think it makes sense to use this for the Rights, Publisher and > Description metadata when it appears on a page. Will this also turn URIs > into links and if not could this be an option? Yes the "as_html_inline:" and "as_html_blocks:" modifiers should linkify URIs. Basically "as_html_blocks:" does exactly the same conversion as the Text Component. -- Bruno From chris at webarchitects.co.uk Tue Nov 22 13:20:53 2005 From: chris at webarchitects.co.uk (Chris Croome) Date: Tue Nov 22 13:20:58 2005 Subject: [MKDoc-dev] [bug] Error messages when uploading files other than jpegs using the photo component Message-ID: <20051122132052.GA5417@webarchitects.co.uk> Hi It was reported in irc last night that the latest (updated last week) CVS version of MKDoc 1.6 generates this error in the logs when a png is uploaded using a photo component: Cannot upload image: Exception 450: Unsupported marker type 0xa3 at /usr/local/share/perl/5.8.4/CGI/Carp.pm line 314. at /home/mkdoc/mkd/flo/Editor.pm line 483 I have now amended the photo component so that it is clear that only jpegs are supported, however I haven't been able to reproduce the error message above. I think we also need to tell the user that they have tried to upload a unsupported file type and that they should retry with a jpeg rather than png uploads simply failing silently... Chris -- Chris Croome web design http://www.webarchitects.co.uk/ web content management http://mkdoc.com/