Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-85357

As a Form Creator, I'd like to be able to create a form in my own language so that I can get a wider audience reach.

    Details

      Description

      Acceptance Criteria:

       

      Translation Component**

      1. Default language means the Site System Language
      2. Add translation Dropdown Button should display the following languages:
        • English (United States)
        • Chinese (China)
        • Spanish (Spain)
        • Japanese (Japan)
        • Dutch (Netherlands)
        • Hungarian (Hungary)
        • Portuguese (Brasil)
        • German (Germany)
        • Hebrew (Israel)
        • Finnish (Finland)
        • Catalan (Spain)
        • French (France)
      3. The dropdown should appear right below to the dropdown button and aligned to the left, according to Lexicon and Clay specifications (current it is not proper implemented. (image-02)).
      4. Users can’t add the same language selected on default language.
      5. Once Selected, a given language should be visible and active.
      6. Users can change the selected language to be translated just by selecting another language previously added just by clicking on it. See gif select-01
      7. If users select a language selected previously on the dropdown list it will turn to this selected option making it active. According to gif select-02
      8. Users can remove a previously added language by clicking on its “X” icon. But it’s not possible to remove the Default language. See gif-03 and image-03.
      9. Currently, an added language keeps available on dropdown and, by clicking on it this added language is activated.

      Field edition

      1. Users can’t switch field
      2. Users are able to edit field label and it’s options

       

      Definition of Done

      • ( ) Related tests created and passed successfully;
      • ( ) All Acceptance Criteria were passed;
      • ( ) Make sure that all system documentation were updated (if necessary);
      • ( ) Validated by QA, Product Designer and/or PM;
      • ( ) No critical issue related to Story scope (ex.: similar of a FP4, FP5 bug);
      • ( ) Code with peer review completed.

        Attachments

        1. gif-01.gif
          gif-01.gif
          539 kB
        2. gif-02.gif
          gif-02.gif
          964 kB
        3. gif-03.gif
          gif-03.gif
          2.42 MB
        4. image-02.png
          image-02.png
          58 kB
        5. image-03.png
          image-03.png
          18 kB

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Packages

                  Version Package
                  Master