Reviewed & tested by the community
Project:
Expanding Formatter
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
6 May 2014 at 11:42 UTC
Updated:
14 Jan 2016 at 11:45 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
discipolo commented$settings['trigger_expanded_label] may be have to wrap in t https://drupal.org/node/1844980#comment-6750998 ?
Comment #2
discipolo commentedOr does this line need a t()http://drupalcode.org/project/expanding_formatter.git/blob/769e9a4:/expa... ?
Comment #3
discipolo commentedDo we need to call i18n_field field ourselves?
Comment #4
discipolo commentedI think we need to do something like
https://drupal.org/node/1155486
https://drupal.org/node/1221208
https://drupal.org/node/1931520
Usually i18n_field module takes care of providing translated formatters for fields provided by core and maybe popular contrib modules, it could be handled by this module itself.
so we possibly need a small sub module like http://drupalcode.org/project/field_placeholder.git/commit/1267c1e Or
http://drupalcode.org/project/custom_add_another.git/commit/050d1ee23e4d...
Or just a patch like https://drupal.org/files/issues/commerce-i18n_field-integration-1155486-...
Comment #5
discipolo commentedComment #6
discipolo commentedi may have been right the first time.
making these two changes the translation is possible it seems, but only after clicking expand once ... so this is not complete yet
Comment #7
discipolo commentedComment #9
discipolo commentedComment #11
discipolo commentedComment #12
discipolo commented9: expanding_formatter-translate-2259807-9.patch queued for re-testing.
Comment #15
discipolo commented7: expanding_formatter-labeltranslate.patch queued for re-testing.
Comment #17
discipolo commentedline endings? it applies locally for me, whats up testbot?
Comment #18
mazze commentedWorks:-)
Comment #19
maico de jongworked for me