Return-Path: Delivered-To: apmail-cocoon-users-archive@www.apache.org Received: (qmail 57215 invoked from network); 28 Jan 2005 09:37:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 28 Jan 2005 09:37:23 -0000 Received: (qmail 53175 invoked by uid 500); 28 Jan 2005 09:37:13 -0000 Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org Received: (qmail 53147 invoked by uid 500); 28 Jan 2005 09:37:12 -0000 Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: users@cocoon.apache.org Delivered-To: mailing list users@cocoon.apache.org Received: (qmail 53127 invoked by uid 99); 28 Jan 2005 09:37:12 -0000 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=FORGED_RCVD_HELO,TO_ADDRESS_EQ_REAL X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from 226.70-84-120.reverse.theplanet.com (HELO glider.phpwebhosting.com) (70.84.120.226) by apache.org (qpsmtpd/0.28) with SMTP; Fri, 28 Jan 2005 01:37:10 -0800 Received: (qmail 14150 invoked from network); 28 Jan 2005 09:37:44 -0000 Received: from unknown (HELO ?192.168.8.17?) (61.170.199.7) by 226.70-84-120.reverse.theplanet.com with SMTP; 28 Jan 2005 09:37:44 -0000 Message-ID: <41FA07BC.800@soociety.com> Date: Fri, 28 Jan 2005 17:37:00 +0800 From: Philippe Guillard User-Agent: Mozilla Thunderbird 0.8 (X11/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "users@cocoon.apache.org" Subject: [Portal] menus and i18n Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hi all, Does anybody has a plan for making the portal menus /tabs i18n? I understand they are prepared at beginning of portal creation by the respective renderers tab/linktab etc... As the profile/layout/portal.xml file is prepared once i see 4 solutions: 1- a portal instance for each language (I think i loose the flexibiulity of i18n support) 2- as many layouts as languages and a profile for each language (I'm worried about the anonymous case) 3- do an i18n transformation on the main portal pipeline after the portal-page.xsl XSL transformation (I'm worried it would slow down performance to parse all portal pages again) 4- do the menus myself inside coplets (then i think i can't access the parameters made disponible by the renderer and disponible in tab.xsl/limktab.xsl, for instance "named-item" , and i have to do by myself something less flexible than the one already done in the portal. One positive thing : in cachingURI coplets, i would have cache) And i wonder about page-labels. Anybody any idea? Regards, Phil --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org For additional commands, e-mail: users-help@cocoon.apache.org