Drupal 7 uses LANGUAGE_NONE (und) which is renamed to LANGUAGE_NOT_SPECIFIED in #965300: Change LANGUAGE_NONE to LANGUAGE_NOT_SPECIFIED; add LANGUAGE_NOT_APPLICABLE and LANGUAGE_MULTIPLE to better explain what it is. Now LANGUAGE_NONE was used for various roles in Drupal 7 including at places where we did not know language (proper use) to where we knew it did not have language (where LANGUAGE_NOT_APPLICABLE should be used now) including where we just said it applies to all languages (for paths for example).
We should review and update the use of 'und' now that we have more language variants so we can better say what is the situation in each case. This can IMHO be done in parallel with #1471432: Rework language_list(), let people use more special languages but is postponed on #965300: Change LANGUAGE_NONE to LANGUAGE_NOT_SPECIFIED; add LANGUAGE_NOT_APPLICABLE and LANGUAGE_MULTIPLE needing to land.
The Drupal 7 usage of LANGUAGE_NONE (for entities) is explained in the Language support for entity fields documentation.
Comments
Comment #1
gábor hojtsyAdding tags.
Comment #2
gábor hojtsy#965300: Change LANGUAGE_NONE to LANGUAGE_NOT_SPECIFIED; add LANGUAGE_NOT_APPLICABLE and LANGUAGE_MULTIPLE landed, so here we go.
Comment #2.0
kristen polUpdated issue summary.
Comment #3
gábor hojtsyNot actually being worked on.
Comment #4
yesct commentedrelated: #1869292: Remove confusing "multiple" language from core
Comment #4.0
yesct commentedUpdated issue summary.
Comment #17
penyaskito\Drupal\Core\Language\LanguageInterfacecontains those constants and when to use each of those is documented.