Please port to D8. I find this module so practical that it should be part of Drupal core! I ran this utility called Drupal Module Upgrader which attempts to convert a D7 module to D8 (see attachment)

CommentFileSizeAuthor
language_sections.zip15.03 KBjoebest

Comments

joebest created an issue. See original summary.

andy inman’s picture

andy inman commented
Priority: Major » Normal

Can you give me some examples of how you would use Language Sections in D8?
I'm sure we will never see LS included in Drupal core, but maybe something else which provides the functionality of LS without the relatively inelegant approach that it takes.

LS was originally written for D6. Since that time, multi-language features in Drupal have improved a lot. Maybe I'm wrong, but I don't think there will be much demand for LS among D8 users. Porting to D8 is not high priority for me, but let's see how many further requests we get here for a D8 version.

joebest’s picture

joebest commented

Hi,
I agree that Drupal's multilingual capabilities have improved over time, however there are certain scenarios where I'd rather rather use Language Sections (LS) over i18n. Here are some examples:

  1. Content types defined for polling, voting and questionnaires. Most of the time, the choices need translation while result tabulation is language agnostic. In LS, tabulation is done once, in i18n, the results are tabulted per language. LS really shines here!
  2. Text overlays in Slideshows/Carousels. Using LS allows to define text overlays once and have Views just filter by content type; with i18n, each slider requires translation for each language supported and then have Views filter by content type and language.
  3. Blocks with text. I find LS a perfect fit for certain blocks like headers and footers. Examaple: a front page block with a greeting message followed by the site's name. In LS, I would define the greeting in language specific sections, and place the site's name in section == all ==.
  4. Time-related content like events and appointments. With LS, the event is created/updated just once; but with i18n, the event is created/updated per language.
andy inman’s picture

andy inman commented

Hi again and thanks for the examples. Have you tried doing the same with Entity Translation? That would (arguably) be the correct approach. UI for inputting content would be very different, but I think the same results could be obtained.

joebest’s picture

joebest commented

I'll give it a try and get back to you.

andy inman’s picture

andy inman commented
Status: Active » Closed (outdated)