Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 64730 invoked by uid 500); 1 Nov 2001 15:25:48 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 64719 invoked from network); 1 Nov 2001 15:25:47 -0000 Message-ID: <3BE169C7.260F4541@apache.org> Date: Thu, 01 Nov 2001 10:27:03 -0500 From: Berin Loritsch X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: something that bugs me References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N giacomo wrote: > > On Tue, 30 Oct 2001, Stefano Mazzocchi wrote: > > > Take a look at this sitemap fragment (used to generate our own docs): > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > value="{1}/graphics/{2}-header.jpg"/> > > > > > > > > > > they look so much equal it really bugs me there is no simple way to > > collapse them into one. I tried, and I couldn't do it. It has to do with the way the aggregation calls are made. If the match to "**/book-*.xml" could be fixed, then it might work. > > > > What do you think? I know I'm being overly picky but we should make an > > effort to create the most clean sitemaps so that people learn from us. > > > > Also, > > > > > > > > > > > > > > > > > > > > > > > > > > > > could be condensed into > > > > > > > > > > > > assuming that nothing but images are stored there. > > I'm not sure but the mime-type attribute is not undergoing variable > replacement so far. For Jpegs, this would yield the following Mime type that is not the most correct, but recognized by many clients: "image/jpg". We would have to change the name of all Jpeg images to use the ".jpeg" extension instead. That's one reason. > > Thinking about it, for those like me who can't learn regexp (sorry, but > > I don't have that mindset), what do you think about adding something > > like > > > > > > > > > > You like us to mix wildcard and regex matching? -1. If you are going to restrict patterns, regex is very powerful, and I don't like mixing metaphores here. In regex, the above could be written as: or something like that. I'm not a RegExp GURU in the least. It _is_ very useful when you are validating complex entries like email addresses and such. > > Giacomo > > > > > which prevents curly braces from being used in URI, but it could be > > useful for many to reduce sitemap verbosity by far in many situations. > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org > For additional commands, email: cocoon-dev-help@xml.apache.org -- "Those who would trade liberty for temporary security deserve neither" - Benjamin Franklin --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org