Support for field groups? [#1175802]

With the recent changes in D7.2 regarding field translation (see #1157426: Field system uses t() incorrectly and inconsistently and http://groups.drupal.org/node/149984), I wondered what to do with "field groups". Currently a contributed module, but IMO closely related to fields. If we want to make the same changes in field groups (i.e. not using t() but i18n_*) should this be done via i18n_field or via i18n_string?

What is your preferred solution?
What would be needed for your preferred solution?
- In the chosen i18n sub-module?
- In field groups module?

I am willing to do (some of) the programming (on both sides) but need some advice to start.

Note: issue in field groups: #1175102: Make field groups localizable the same way as fields in core

Comment	File	Size	Author
#7	ScreenHunter_042.jpg	21.77 KB	fietserwin
#7	ScreenHunter_044.jpg	21.02 KB	fietserwin

Comments

Comment #1

jose reyero commented 8 June 2011 at 12:36

If you are talking about translating labels and descriptions, yes, that would fit inti i18n_field module.

Comment #2

fietserwin

Le Mont-Dore

commented 8 June 2011 at 17:44

That's indeed what I mean. Is there any documentation (hooks, execution order, ...) that I can use to start coding? Example code? or what code to copy and adapt from fields versus i18n_field. I will give it a try, but know from experience that starting to code in Drupal is often the most difficult part...

Comment #3

hnln commented 22 June 2011 at 18:39

sub

Comment #4

altavis commented 28 June 2011 at 12:38

Any progress?

It might be tricky due to way that fieldgroup is handling its configuration.

Comment #5

Stalski commented 1 August 2011 at 20:14

I have not started coding for it. I also don't see any problem with how configuration is done as well, might be some work, but nothing i18n_field couldn't handle (did not check it completely).

But what I do think is that it's not the same data. The field group labels I use the most, are words that already used somewhere else, through a t string. E.g. Images, Information, Content, Address, ... . Does that make any sense to you guys?

Comment #6

altavis commented 3 August 2011 at 06:04

I meant UI problems, but you are right it's not a big deal.

So, do you want different translations for 'Images' in core and in field group? For me it could be the same and keep using t() for labels but now it's not preferred method.

Comment #7

fietserwin

Le Mont-Dore

commented 3 August 2011 at 09:39

Status	File	Size
new	ScreenHunter_044.jpg	21.02 KB
new	ScreenHunter_042.jpg	21.77 KB

We are only talking user entered content. The idea/agreement is that this will be in the default language of the site. Strings coming from code remain in English and should still be translated using t(). see attached screen shots. The texts "This (display) label" and "This (display) description" are user entered and should go the i18n_field way.