You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@manifoldcf.apache.org by "Karl Wright (Commented) (JIRA)" <ji...@apache.org> on 2012/04/06 14:21:25 UTC

[jira] [Commented] (CONNECTORS-457) Strange i18n behavior on some Italian or German machines

    [ https://issues.apache.org/jira/browse/CONNECTORS-457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248261#comment-13248261 ] 

Karl Wright commented on CONNECTORS-457:
----------------------------------------

I haven't been able to make this happen locally even with the Firefox plugin that allows me to change the browser locale at will.

One hypothesis is that this is happening because the locale on these machines is in fact being picked up as null or the empty string.  There is a commons.properties file (which should not be there anyhow) at framework/ui-core/src/main/native2ascii/org/apache/manifoldcf/uicore/i18n which then might be being picked up as a resource bundle.  Haven't been able to confirm this picture; an output of the locale name as picked up by the jsp pages on one of the affected machines would be very very helpful.

                
> Strange i18n behavior on some Italian or German machines
> --------------------------------------------------------
>
>                 Key: CONNECTORS-457
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-457
>             Project: ManifoldCF
>          Issue Type: Bug
>          Components: Framework core
>    Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6
>            Reporter: Karl Wright
>            Assignee: Karl Wright
>             Fix For: ManifoldCF 0.5
>
>
> When ManifoldCF is run on some machines that are neither en_US or ja_JP, certain specific messages render with the key value rather than falling back to en_US.  One specific field that this happens to is in listconnections.jsp, and is the "listconnections.ListOfRepositoryConnections" message.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira