cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joerg Heinicke <>
Subject Re: Wap / i18n problem
Date Thu, 17 Apr 2003 08:47:31 GMT
Hello Hans,

try to have a look on the output of the pipeline. The <i18n:date/> 
element should be correctly replaced. The problem - well-known with 
mobile phones - is the remaining i18n namespace declaration, isn't it? 
There should be already some mails in the archives related to this topic 
including solutions.



Hans-Michael Rupp wrote:
> Hallo!
> We have a problem using the i18n transformater generating wml.
> The source of the problem seem to be <i18n:date> tags.
> Everything works well when we view the page with wap-browsers under
> window (e.g. OpenWave or Opera). When we access the pages with
> <i18n:date> tags with a real device (WAP mobile telephone or other
> devices I am not allowed to name) we see that we get a valid WML deck
> with all content missing beginning from the first occurence of a
> <i18n:date> tag. It is most probably not a gateway problem, since from
> or debug messages we see that we get the abreviated deck on our server
> after the i18n transformation.
> Example i18n:date tag:
> <i18n:date src-pattern="{$NeutralDateFormat}"
> locale="{Weather/UserLocale}" pattern="E, dd.MM.;"><xsl:value-of
> select="Weather/Weather/WeatherSymbol/NeutralDate"
> /></i18n:date><xsl:text> </xsl:text><i18n:text>Uhr</i18n:text>
> Any ideas how we can tackle this problem would be very much appreciated.
> Many thanks,
> Hans

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message