ENGAGE-286: Localization: ensure all components load strings in the correct language

Metadata

Source
ENGAGE-286
Type
Sub-task
Priority
Major
Status
Closed
Resolution
Fixed
Assignee
N/A
Reporter
Michelle D'Souza
Created
2010-01-25T10:43:34.000-0500
Updated
2010-02-08T17:41:12.000-0500
Versions
N/A
Fixed Versions
  1. 0.3b
Component
N/A

Description

At the moment, a number of component hard-bake English string directly in the component's markup. We should use the facilities of the Renderer, along with the ability to send data to components from the server upon instantiation. This will ensure that all components can be localized in any language.

Comments

  • Justin Obara commented 2010-01-25T17:17:37.000-0500

    =============================
    Here is a what needs to be localized.
    ==============================

    Exhibition Browse
    ------------------------ *** Problem running in standalone, see ENGAGE-324 & ENGAGE-319 ***

    • Title
    • Exhibition Descriptions ?
    • Upcoming Exhibitions Header

    Artifact View

    -----------------

    • Media cabinet header
    • Comments cabinet header
    • related artifacts ?
      • for all cabinet headers there is a variant using show and hide

    My Collection

    -------------------
    ???

    ====================================
    Here is the list of finished Pages/Components
    ====================================

    Home Page
    ----------------

    • Title
    • image captions

    Exhibition About / Upcoming

    --------------------------------------

    • Exhibition Display Date ?

    Exhibition Main

    ---------------------

    • Read More link
    • View the full catalogue link
    • Read all comments
    • catalogue header
    • guessbook header
    • exhibition display date ?

    Catalogue View

    ---------------------

    • View all Objects
    • View all in ...

    Catalogue Browse

    -------------------------

    • Title
    • Viewing "...
  • Michelle D'Souza commented 2010-02-02T10:15:53.000-0500

    mccord-pilot

  • Justin Obara commented 2010-02-02T16:46:38.000-0500

    The ENGAGE-286(exhibitionBrowse service update).patch.txt are the updates needed for the exhibitionBrowse.js file to comply with the updates to the Browse component and to look for the message bundle in a different location. Just waiting on Antranig to make some changes to the exhibitionBrowse.js file before committing.

  • Justin Obara commented 2010-02-05T15:51:32.000-0500

    Bug Parade Engage 0.3

  • Justin Obara commented 2010-02-08T17:41:12.000-0500

    For the most part this is completed. Specific jiras have been filed for the remaining tasks

    ENGAGE-348, ENGAGE-352, ENGAGE-354, ENGAGE-355, ENGAGE-356