You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2009/03/03 19:44:56 UTC

[jira] Created: (TAP5-548) Textual messages inside tapestry.js should be split out into a seperate .js file that is localizable

Textual messages inside tapestry.js should be split out into a seperate .js file that is localizable
----------------------------------------------------------------------------------------------------

                 Key: TAP5-548
                 URL: https://issues.apache.org/jira/browse/TAP5-548
             Project: Tapestry 5
          Issue Type: New Feature
          Components: tapestry-core
    Affects Versions: 5.1.0.1
            Reporter: Howard M. Lewis Ship


I started doing this using Tapestry.Messages as the namespace.  We really should split this out into its own JS file and automatically include the correct localization of it when rendering the page.

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

[jira] Commented: (TAP5-548) Textual messages inside tapestry.js should be split out into a seperate .js file that is localizable

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/TAP5-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678398#action_12678398 ] 

Howard M. Lewis Ship commented on TAP5-548:
-------------------------------------------

Probably should wait until TAP5-549 is ready for this kind of change.

> Textual messages inside tapestry.js should be split out into a seperate .js file that is localizable
> ----------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-548
>                 URL: https://issues.apache.org/jira/browse/TAP5-548
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-core
>    Affects Versions: 5.1.0.1
>            Reporter: Howard M. Lewis Ship
>
> I started doing this using Tapestry.Messages as the namespace.  We really should split this out into its own JS file and automatically include the correct localization of it when rendering the page.

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

[jira] Commented: (TAP5-548) Textual messages inside tapestry.js should be split out into a seperate .js file that is localizable

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/TAP5-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678398#action_12678398 ] 

Howard M. Lewis Ship commented on TAP5-548:
-------------------------------------------

Probably should wait until TAP5-549 is ready for this kind of change.

> Textual messages inside tapestry.js should be split out into a seperate .js file that is localizable
> ----------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-548
>                 URL: https://issues.apache.org/jira/browse/TAP5-548
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-core
>    Affects Versions: 5.1.0.1
>            Reporter: Howard M. Lewis Ship
>
> I started doing this using Tapestry.Messages as the namespace.  We really should split this out into its own JS file and automatically include the correct localization of it when rendering the page.

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

[jira] Closed: (TAP5-548) Textual messages inside tapestry.js should be split out into a seperate .js file that is localizable

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship closed TAP5-548.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 5.1.0.3
         Assignee: Howard M. Lewis Ship

Actually fixed in 5.1.0.2, but missed the bookkeeping until after 5.1.0.2 was released.

> Textual messages inside tapestry.js should be split out into a seperate .js file that is localizable
> ----------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-548
>                 URL: https://issues.apache.org/jira/browse/TAP5-548
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-core
>    Affects Versions: 5.1.0.1
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.1.0.3
>
>
> I started doing this using Tapestry.Messages as the namespace.  We really should split this out into its own JS file and automatically include the correct localization of it when rendering the page.

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

[jira] Closed: (TAP5-548) Textual messages inside tapestry.js should be split out into a seperate .js file that is localizable

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship closed TAP5-548.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 5.1.0.3
         Assignee: Howard M. Lewis Ship

Actually fixed in 5.1.0.2, but missed the bookkeeping until after 5.1.0.2 was released.

> Textual messages inside tapestry.js should be split out into a seperate .js file that is localizable
> ----------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-548
>                 URL: https://issues.apache.org/jira/browse/TAP5-548
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-core
>    Affects Versions: 5.1.0.1
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.1.0.3
>
>
> I started doing this using Tapestry.Messages as the namespace.  We really should split this out into its own JS file and automatically include the correct localization of it when rendering the page.

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