[ 
https://issues.apache.org/jira/browse/TAP5-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ulrich Stärk closed TAP5-409.
-----------------------------

    Resolution: Fixed

Fixed in the documentation wiki at 
https://cwiki.apache.org/confluence/display/TAPESTRY/Localization

> Localization documentation should be clear that Tapestry (and Java) do not 
> support BOM headers in message catalog files
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-409
>                 URL: https://issues.apache.org/jira/browse/TAP5-409
>             Project: Tapestry 5
>          Issue Type: Bug
>    Affects Versions: 5.0.15, 5.0.16, 5.0.17
>            Reporter: Borut Bolcina
>            Assignee: Ulrich Stärk
>         Attachments: locale-not-working.zip
>
>
> app.properties has 3 entries:
> openid-provider-title=OpenID provider
> my-account-link=My account
> login-link=Login
> index.tml
> <html xmlns:t="http://tapestry.apache.org/schema/tapestry_5_0_0.xsd";>
>       <head>
>               <title>${message:openid-provider-title}</title>
>               <link rel="stylesheet" type="text/css" 
> href="${asset:context:css/iopenid.css}" />
>       </head>
>       <body>
>               <t:security.ifloggedin>
>                       <p><t:userdetails /> <a t:type="pagelink" 
> t:page="AccountEdit" href="#">${message:my-account-link}</a> <a 
> t:type="actionlink" t:id="logout">odjava</a></p>
>                       <t:parameter name="else">
>                               <a t:type="pagelink" t:page="Login" 
> href="#">${message:login-link}</a>
>                       </t:parameter>
>               </t:security.ifloggedin>
>       </body>
> </html>
> I also have two other lozalized properties files. Depending on the browser 
> preffered language selection the correct translatinos are displayed - EXCEPT 
> the first entry, which always falls back to english.
> I first noticed this behaviour when playing arounf with EditBean - the 
> translated labels all worked, well, except the first one. Whichever entry was 
> the first in the file, that label was not translated.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to