I have to retrofit an existing Panels based site with a Japanese translation and would just like to confirm that I haven't missed anything with regard to Panels internationalisation. I have no problem dealing with the translation of regular nodes, menus et al.

My current understanding of internationalising a Panels based site is:

  1. Panels doesn't support translation directly.
  2. Panel Pages can be internationalised using variants and user language selection rules.
  3. Visibility rules can be used to show content according to the user language selection.
  4. Panels containing blocks will show translated content if supported by the block.

So if I have a site constructed of panel variants containing lots of panes and mini panels that don't contain blocks my options are:

  1. Create a separate page variant for each translated page and duplicate + translate all the custom panes and mini panels.
  2. Keep the existing page variants. Duplicate all page custom content panes, translate and then use language selection to control visibility. Edit all mini panels and similarly duplicate, translate and language select the content.

My preferred option is number 2, that is unless I have missed something...

Thanks

Jonathan

Comments

Letharion’s picture

Letharion commented
Status: Active » Fixed

Unfortunately, I can not really answer your questions. As quite some time has passed since you asked them, I'm assuming that you have moved on, and in one way or the other solved your problems.
If so, it would be great if you wanted to provide some feedback on your experience, possibly for documentation purposes.
If you're not done here, I know there are ctools patches that will enable better i18n handling. You may wanna scour the ctools queue for those.

Status: Fixed » Closed (fixed)

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