Problem/Motivation

Several places within ECA make sense to run through translation. Using dynamic variables passing to the translation method however is not recommended. We need to determine how we can support translation of text.

Steps to reproduce

Proposed resolution

One way could be to provide an action that runs explicit translation on a dynamic string. This way a user may have the control when and how a string shall be translated.

Remaining tasks

User interface changes

API changes

Data model changes

Issue fork eca-3280069

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

mxh created an issue. See original summary.

mxh’s picture

mxh’s picture

Issue tags: +release1.0
Parent issue: » #3238206: ECA 1.0.0 stable release plan
jurgenhaas’s picture

Issue tags: -release1.0
Parent issue: #3238206: ECA 1.0.0 stable release plan »

Will not be part of 1.0RC and may be pushed into 1.1

mxh’s picture

Assigned: Unassigned » mxh
mxh’s picture

Title: Determine how to deal with dynamic translation strings » eca_base: Provide an action for translating text

mxh’s picture

Assigned: mxh » Unassigned
Status: Active » Needs review

  • jurgenhaas committed de59611 on 1.1.x authored by mxh
    Issue #3280069 by mxh, jurgenhaas: eca_base: Provide an action for...
jurgenhaas’s picture

Status: Needs review » Fixed

Nicely done!

mxh’s picture

I think it makes sense to move this action to the new eca_render module, once it's available.

jurgenhaas’s picture

Really? I would have thought, translating a string is well-placed as a base plugin because it could be useful for displaying messages, setting form buttons and certainly a lot more.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.