Hi Phil, Here Carsten's answer about Coplet i18n:
------------------------------ Hi Eric, I'm only reading the user list from time to time, so I didn't see your question. The i18n support for the portal is not as good as it could be. I think we are using the following approach: Specify the key in the title of the coplet-data: <title>LogIn</title>. Then in the renderer that renders the window, add the i18n tag around the title (this is done in the window.xsl). Current it does something like this: <xsl:when test="@title"> <b><xsl:value-of select="@title"/></b> </xsl:when> and you could change it like this: <xsl:when test="@title"> <b><i18n><xsl:value-of select="@title"/></i18n></b> </xsl:when> Then place the i18n transformer in the main pipeline just after the cinclude transformer. (This is the "portal" pipeline with the portal generator). HTH Carsten ------------------------------ It works for me. HTH Eric -----Original Message----- From: pguillard [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 27, 2004 6:08 AM To: [EMAIL PROTECTED] Subject: Re: Portal Engine - Coplet I18n question Just a suggestion (i didn't try) : <map:match pattern="portal"> <map:act type="auth-protect"> <map:parameter name="handler" value="portal-handler"/> <map:parameter name="application" value="portal"/> <map:generate type="portal" label="content"> <map:parameter name="portal-name" value="portal" /> </map:generate> <map:transform type="cinclude"/> <map:transform type="portal-coplet"/> <map:transform type="encodeURL"/> <map:transform type="i18n"> <map:parameter name="locale" value="en-US"/> </map:transform> <map:serialize type="html-include"/> </map:act> </map:match> Can you tell me the result, i will need it too! Phil --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
