Uploaded image for project: 'Tapestry 5'
  1. Tapestry 5
  2. TAP5-548

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

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.1.0.1
    • Fix Version/s: 5.1.0.3
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      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.

        Activity

        Hide
        hlship Howard M. Lewis Ship added a comment -

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

        Show
        hlship Howard M. Lewis Ship added a comment - Probably should wait until TAP5-549 is ready for this kind of change.
        Hide
        hlship Howard M. Lewis Ship added a comment -

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

        Show
        hlship Howard M. Lewis Ship added a comment - Actually fixed in 5.1.0.2, but missed the bookkeeping until after 5.1.0.2 was released.

          People

          • Assignee:
            hlship Howard M. Lewis Ship
            Reporter:
            hlship Howard M. Lewis Ship
          • Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development