Translatable blocks and context is not possible atm.
Related issue in Context issue queue: #1320864: Context not respecting block language.

Files: 
CommentFileSizeAuthor
#9 i18n_block-Context-not-respecting-block-language-1343044-9.patch996 bytesGoZ
PASSED: [[SimpleTest]]: [MySQL] 2,095 pass(es).
[ View ]
#1 i18n_block_context_compatibility-1343044-1.patch853 byteswebflo
PASSED: [[SimpleTest]]: [MySQL] 1,893 pass(es).
[ View ]

Comments

Status:Active» Postponed
StatusFileSize
new853 bytes
PASSED: [[SimpleTest]]: [MySQL] 1,893 pass(es).
[ View ]

Still works and patch apply nicely on 7.x-1.3.

i18n 7.x-1.3 working.

Status:Postponed» Reviewed & tested by the community

Confirmed working in i18n 7.x-1.4 (2012-Feb-05) and context 7.x-3.0-beta2 (2011-Sep-08) with the patch from this issue (comment #1) and http://drupal.org/node/1320864#comment-5249916

Confirmed working the patch to context in http://drupal.org/node/1320864#comment-5249916. Thanks.

Confirmed working here as well. Would be great to get this committed.

Status:Reviewed & tested by the community» Fixed

#1320864: Context not respecting block language is fixed. Committed the patch from #1 to 7.x-1.x. Thanks for the reviews.

Status:Fixed» Closed (fixed)

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

Status:Closed (fixed)» Needs review
StatusFileSize
new996 bytes
PASSED: [[SimpleTest]]: [MySQL] 2,095 pass(es).
[ View ]

I use Context 7.x-3.0-beta6 and i18n 7.x-1.7.
With i18n_block enabled, I can define 1 or more languages for a block. So if I check english to a block, it shouldn't be displayed on french, deutch or other language.

Unfortunatelly, previous patch only take care of "translatable" option, and not localization.

I join patch to make it possible. This have to be used with patch of this issue http://drupal.org/node/1320864#comment-7003150 on comment #21

I also noticed the language specific blocks were showing always.
I applied this patch. This solved the problem.

Status:Needs review» Needs work

The patch may work but really, I don't think it is a good idea to mix features of both modules in that way
(As I see the context side of the patch filters out the blocks using the language added in by i18n_block, right?)

Really, context defines block visibility depending on multiple conditions and i18n does the same only for language. Because this and because of the specific implementation on both sides, these modules are just not compatible.

What I don't understand: Can't you add language conditions using context on top of all the other conditions? If so, why would you need i18n_block for that?

And then if you want a nice UI improvement, just disable i18n_block language visibility when context is enabled.

Would that work?

What I don't understand: Can't you add language conditions using context on top of all the other conditions? If so, why would you need i18n_block for that?

In this way, we should have as many differents contexts by language. If we have 10 differents contexts in default language which take care of other conditions than language to display some localized blocks, we have to duplicate context for each language. So we have Context number * Language number. It can be quickly very heavy.

Issue summary:View changes

...