[jira] [Commented] (TAP5-2574) No match on Locale nb

2017-03-03 Thread Svein (JIRA) 

[ 
https://issues.apache.org/jira/browse/TAP5-2574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894194#comment-15894194
 ] 

Svein commented on TAP5-2574:
-

I think your solution is good. nn users will not be confused.

Will the configuration change to(?):
{code}
configuration.add(SymbolConstants.SUPPORTED_LOCALES, "no,en);
{code}

What if someone want to add a translation for nn/no_NO_NY when nn* points to no?

> No match on Locale nb 
> --
>
> Key: TAP5-2574
> URL: https://issues.apache.org/jira/browse/TAP5-2574
> Project: Tapestry 5
>  Issue Type: Bug
>  Components: tapestry-core
>Affects Versions: 5.4.1
>Reporter: Svein
>
> {code}configuration.add(SymbolConstants.SUPPORTED_LOCALES, "no_NB,en");{code}
> {code}org.apache.tapestry5.internal.services.Request.getLocale() for returns 
> "nb" for Norwegian{code}
> No *_no_NB.properties or *_no.properties are used. I think A way to alias 
> locale is needed. E.g: 
> {code}configuration.add(SymbolConstants.SUPPORTED_LOCALES, 
> "no_NB{nb},en);{code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (TAP5-2574) No match on Locale nb

2017-03-03 Thread Jochen Kemnade (JIRA) 

[ 
https://issues.apache.org/jira/browse/TAP5-2574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894124#comment-15894124
 ] 

Jochen Kemnade commented on TAP5-2574:
--

I rather thought about renaming it to {{core_no.properties}} and use it for 
{{nb*}} and {{nn*}}. Or would a {{nn}} user be confused or irritated if we 
provided them with a Bokmål translation?

> No match on Locale nb 
> --
>
> Key: TAP5-2574
> URL: https://issues.apache.org/jira/browse/TAP5-2574
> Project: Tapestry 5
>  Issue Type: Bug
>  Components: tapestry-core
>Affects Versions: 5.4.1
>Reporter: Svein
>
> {code}configuration.add(SymbolConstants.SUPPORTED_LOCALES, "no_NB,en");{code}
> {code}org.apache.tapestry5.internal.services.Request.getLocale() for returns 
> "nb" for Norwegian{code}
> No *_no_NB.properties or *_no.properties are used. I think A way to alias 
> locale is needed. E.g: 
> {code}configuration.add(SymbolConstants.SUPPORTED_LOCALES, 
> "no_NB{nb},en);{code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (TAP5-2574) No match on Locale nb

2017-03-03 Thread Svein (JIRA) 

[ 
https://issues.apache.org/jira/browse/TAP5-2574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894085#comment-15894085
 ] 

Svein commented on TAP5-2574:
-

Do you mean that nn* should read nb properties file by default?

Another ting: Maybe core_no_NB.properties should be renamed to 
core_nb.properties, not core_nb_NO.properties?

> No match on Locale nb 
> --
>
> Key: TAP5-2574
> URL: https://issues.apache.org/jira/browse/TAP5-2574
> Project: Tapestry 5
>  Issue Type: Bug
>  Components: tapestry-core
>Affects Versions: 5.4.1
>Reporter: Svein
>
> {code}configuration.add(SymbolConstants.SUPPORTED_LOCALES, "no_NB,en");{code}
> {code}org.apache.tapestry5.internal.services.Request.getLocale() for returns 
> "nb" for Norwegian{code}
> No *_no_NB.properties or *_no.properties are used. I think A way to alias 
> locale is needed. E.g: 
> {code}configuration.add(SymbolConstants.SUPPORTED_LOCALES, 
> "no_NB{nb},en);{code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (TAP5-2574) No match on Locale nb

2017-03-03 Thread Jochen Kemnade (JIRA) 

[ 
https://issues.apache.org/jira/browse/TAP5-2574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894048#comment-15894048
 ] 

Jochen Kemnade commented on TAP5-2574:
--

Then maybe we should use the current properties file for all Norwegian locales 
until someone does a Nynorsk translation. Would that be acceptable?

> No match on Locale nb 
> --
>
> Key: TAP5-2574
> URL: https://issues.apache.org/jira/browse/TAP5-2574
> Project: Tapestry 5
>  Issue Type: Bug
>  Components: tapestry-core
>Affects Versions: 5.4.1
>Reporter: Svein
>
> {code}configuration.add(SymbolConstants.SUPPORTED_LOCALES, "no_NB,en");{code}
> {code}org.apache.tapestry5.internal.services.Request.getLocale() for returns 
> "nb" for Norwegian{code}
> No *_no_NB.properties or *_no.properties are used. I think A way to alias 
> locale is needed. E.g: 
> {code}configuration.add(SymbolConstants.SUPPORTED_LOCALES, 
> "no_NB{nb},en);{code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (TAP5-2574) No match on Locale nb

2017-03-03 Thread Svein (JIRA) 

[ 
https://issues.apache.org/jira/browse/TAP5-2574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893954#comment-15893954
 ] 

Svein commented on TAP5-2574:
-

You are right, nb_NO is correct. Then the translation core_no_NB.properties in 
Tapestry need to be changed.

A kind of alias or configuration is still needed because people using Norwegian 
Nynorsk, with locale ID nn, nn_NO, ... will have no problem reading the major 
language nb_NO.

What about:
{code}
configuration.add(SymbolConstants.SUPPORTED_LOCALES, "nb_NO{nn,nn_NO},en);
{code}

After a upgrade Tapestry should complain if SUPPORTED_LOCALES=no_NB 


> No match on Locale nb 
> --
>
> Key: TAP5-2574
> URL: https://issues.apache.org/jira/browse/TAP5-2574
> Project: Tapestry 5
>  Issue Type: Bug
>  Components: tapestry-core
>Affects Versions: 5.4.1
>Reporter: Svein
>
> {code}configuration.add(SymbolConstants.SUPPORTED_LOCALES, "no_NB,en");{code}
> {code}org.apache.tapestry5.internal.services.Request.getLocale() for returns 
> "nb" for Norwegian{code}
> No *_no_NB.properties or *_no.properties are used. I think A way to alias 
> locale is needed. E.g: 
> {code}configuration.add(SymbolConstants.SUPPORTED_LOCALES, 
> "no_NB{nb},en);{code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (TAP5-2574) No match on Locale nb

2017-03-03 Thread Svein (JIRA) 

[ 
https://issues.apache.org/jira/browse/TAP5-2574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893954#comment-15893954
 ] 

Svein edited comment on TAP5-2574 at 3/3/17 9:10 AM:
-

You are right, nb_NO is correct. Then the translation core_no_NB.properties in 
Tapestry need to be renamed.

A kind of alias or configuration is still needed because people using Norwegian 
Nynorsk, with locale ID nn, nn_NO, ... will have no problem reading the major 
language nb_NO.

What about:
{code}
configuration.add(SymbolConstants.SUPPORTED_LOCALES, "nb_NO{nn,nn_NO},en);
{code}

After a upgrade Tapestry should complain if SUPPORTED_LOCALES=no_NB 



was (Author: svein):
You are right, nb_NO is correct. Then the translation core_no_NB.properties in 
Tapestry need to be changed.

A kind of alias or configuration is still needed because people using Norwegian 
Nynorsk, with locale ID nn, nn_NO, ... will have no problem reading the major 
language nb_NO.

What about:
{code}
configuration.add(SymbolConstants.SUPPORTED_LOCALES, "nb_NO{nn,nn_NO},en);
{code}

After a upgrade Tapestry should complain if SUPPORTED_LOCALES=no_NB 


> No match on Locale nb 
> --
>
> Key: TAP5-2574
> URL: https://issues.apache.org/jira/browse/TAP5-2574
> Project: Tapestry 5
>  Issue Type: Bug
>  Components: tapestry-core
>Affects Versions: 5.4.1
>Reporter: Svein
>
> {code}configuration.add(SymbolConstants.SUPPORTED_LOCALES, "no_NB,en");{code}
> {code}org.apache.tapestry5.internal.services.Request.getLocale() for returns 
> "nb" for Norwegian{code}
> No *_no_NB.properties or *_no.properties are used. I think A way to alias 
> locale is needed. E.g: 
> {code}configuration.add(SymbolConstants.SUPPORTED_LOCALES, 
> "no_NB{nb},en);{code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)