[CAM-8520] I18n for processActionsEE plugin in Cockpit (ee) Created: 05/Dec/17  Updated: 05/Mar/18  Resolved: 15/Dec/17

Status: Closed
Project: camunda BPM
Component/s: cockpit
Affects Version/s: None
Fix Version/s: 7.9.0, 7.9.0-alpha1

Type: Feature Request Priority: L3 - Default
Reporter: Tassilo Weidner Assignee: Michael Schoettes
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0 minutes
Time Spent: Not Specified
Original Estimate: 0 minutes

Issue Links:
Depedendency
is depended on by CAM-2268 I18n Internationalization support for... Closed

 Description   
  1. in HTML files all verbal texts are replaced with meaningful tokens which are piped to the angular translate filter
    <p>{{ 'EXAMPLE_TOKEN' | translate }}</p>
    
  2. in JS files all verbal texts are replaced with meaningful tokens - the instant method of the $translate provider is applied to the tokens
    $translate.instant('EXAMPLE_TOKEN');
    
  3. all tokens are stored in src/main/resources-plugin/cockpit/locales/en.json
  4. use a meaningful prefix like "PLGN_PACT_..." for the tokens to make clear that they belong together
  5. do not split up coherent sentences in multiple tokens if the sentences contain one or more variables. Neither in the HTML nor JS files. Use the following way instead to handle such situations:
    <p>{{ 'BATCHES_PROGRESS_FAILED' | translate:'{jobs: selection.failedJobs}' }}</p>
    
    $translate.instant('SERVICES_RESOURCE', {status: errorResponse.status})
    
    {
      ...
      "BATCHES_PROGRESS_FAILED" : "Failed {{jobs}}",
      ...
      "SERVICES_RESOURCE": "Received {{status}} from server.",
      ...
    }
    
  6. punctuation signs should be stored in the translation file also
  7. no further configurations are necessary (e. g. Gruntfile, etc.)

Generated at Mon Sep 23 01:15:40 CEST 2019 using JIRA 6.4.6#64021-sha1:33e5b454af4594f54560ac233c30a6e00459507e.