In #539110: TF #4: Translatable fields UI we've decided to leave the fields translation in contrib for the D7 cycle.

A main challenge this leaves is that we need testing of the field translation in core but few users will be aware of the fields translation module.

Proposed solution: add a link to that module (when it's available) in the .info description for core's translation module. This link could be removed before the D7 release, or possibly left in.

Draft text: "See also the Field translation module for field-based translation."

CommentFileSizeAuthor
#4 translation_hint-653656-4.patch797 bytesplach

Comments

sun’s picture

sun
Primary language German
Location Karlsruhe
commented

Not sure whether that will help.

plach’s picture

plach
he/him
Primary language Italian
Location Venezia
commented

But surely it can't hurt :)

plach’s picture

plach
he/him
Primary language Italian
Location Venezia
commented
Issue tags: +translatable fields
plach’s picture

plach
he/him
Primary language Italian
Location Venezia
commented
Status: Active » Needs review
StatusFileSize
new translation_hint-653656-4.patch797 bytes

Here is the hint.

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Status: Needs review » Reviewed & tested by the community
webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented
Status: Reviewed & tested by the community » Closed (won't fix)

No, sorry, we're not doing this. We don't do this for any other core module which has alternatives in contrib, I don't see why we should start here.

If you need testers:

a) Roll at least some kind of release on the project page.
b) Post to the Drupal Planet/Twitter/etc. like everyone else.