Create a 'language' token type (D7)

subscribe. good to have the language object "translated" to tokens

I'm assuming that this includes tokens for both the content language and the interface language? #233076: Add token for node's language only works for nodes, but these tokens should be available everywhere.

A use case is setting the Dublin Core language metatag to something like this:
<meta name="dcterms.language" content="eng">

The setting for that should come from a token. How about these:

• [site:language:content:name]
• [site:language:content:code]
• [site:language:interface:name]
• [site:language:interface:code]

...which would come from:

• $language
• $language_content

These would be very practical!

I gave it a go...

Thanks,

Pobster

Hmmm filename fail - good job anyway as I used language instead of language_content for the replacement...

Thanks,

Pobster

Ummm on Linux, using git... Tried cleaning the line endings manually - this suggests the token.tokens.inc file has bad line endings (I use preserve).

Thanks,

Pobster

Okay I give up, I haven't got time to mess around with this right now. I'll do it later from home, it's hardly a massive change anyway - maybe I'll add to the simpletests as well.

Pobster

Fixed typo.

Pobster

I think that the last patch works. I was actually surprised that Token did not have Current UI language before :)

I tested it with https://drupal.org/project/metatag
Seems OK.
I use [language:language-content] for content language in the Global section of Metatag.

Out of interest, would it be worth adding another token to list all of the supported languages for the site?

I believe it does that if you just choose the parent (can't actually remember, it's been a while since I did this).

Thanks,

Pobster

works great!

please commit

can anyone give a hint as to what the actual token would be for this?

i am trying to use Display Suite to create a custom field and when i open the token browser to display aprox 200M of tokens, the only one i can find related to language is [node:language] and this only gives the lang code.

nope, my bad.. i didn't read close enough and assumed 4 yrs into D7 this had been committed.. so applied patch and now i see the tokens in the token browser; but [language-content:name] does not output anything.

for anyone else looking for a solution for this, since the above patch didnt work, i just wrote my own token:

function mymodule_token_info() {
  $info['tokens']['node']['language-name'] = array(
    'name' => t('Language'),
    'description' => t('The language name the current node is in.'),
  );
  return $info;
}

function mymodule_tokens($type, $tokens, array $data = array(), array $options = array()) {
  $replacements = array();
  
  if ($type == 'node' && !empty($data['node'])) {
    $node = $data['node'];
    foreach ($tokens as $name => $original) {
      switch ($name) {
        case 'language-name':
          $replacements[$original] = locale_language_name($node->language);
          break;
      }
    }
  } 

  return $replacements;
}

Odd, I tested the patch today and it applied fine for me?

patch applied fine.. but outputs nothing. possibly since you have it declared as type = language; does this mean it won't be usable in a node context? i have mine as type 'node' so it shows within node context; perhaps it should be global though?

Just tried it and it works flawlessly.

Patch still applies and works like a charm. I can't see any downsides to it, or any reason why this shouldn't be added. It would be great if this got committed!

Bump to see if Dave Reid might be able to provide some insight on what blockers, if any, exist to getting this committed.

Well I'm just glad that people are finding it useful, that's great! :o)

Thanks,

Pobster

+1 to get this committed.
I'm using this patch in PROD.
Thanks very much in advance.

Site wide language code by module implementation, forked from liquidcms, thanks!
Caution: this is D8 version. For D7, please change '\Drupal::languageManager()->getCurrentLanguage()->getId()' to 'i18n_get_lang()'

function mymodule_token_info() {
  $info['tokens']['site']['language-code'] = array(
    'name' => t('Language code'),
    'description' => t('The curremt language code.'),
  );

  return $info;
}

function mymodule_tokens($type, $tokens, $data = array(), $options = array()) {
  $replacements = array();
  
  if ($type == 'site') {
    foreach ($tokens as $name => $original) {
      if ($name == "language-code") {
        $replacements[$original] = \Drupal::languageManager()->getCurrentLanguage()->getId();
      }
    }
  } 

  return $replacements;
}

Not sure the current language token(s) belong in the "site:" section. The "site:" token group includes stuff which is invariant across the whole site but current language isn't. The current language is not site-specific, it's page-specific. With a multilingual web site (probably the only use case where these tokens are even needed in the first place), pages can be rendered in different languages and every instance of a rendered page can only have one currentLanguage.
I vote for
[current-page:language:code]
and
[current-page:language:name]

I appreciate that this ticket is already set to RTBC, so feel free to ignore this. But I had a need for a token for the path prefix, since my prefixes don't match my language codes. So here's a patch that adds them, plus tokens for language domains.

@ndlarge @phKU - the D7 patch declares a new token type for languages, so the tokens aren't under 'site' or 'current-page' anyway. That's probably better for any D8 implementation too.

#32 is working fine for me. Thanks.

FYI there's a similar issue for D8: #2863200: Current interface language token (D8)

FYI I put together an initial patch for D8 in #2863200: Current interface language token (D8).

Patch of #32 applies cleanly, but I don't have a token for the language a user account is in....

"language-ui" will provide you with this ~ the UI will be in the active users language.

@pobster, thanks. But doesn't that provide the ui language of the user that's currently logged in?

In my case I really need the token for the language of each individual account (for bulk operations and syncing of data to 3rd party apps). I figure the language-ui would return the interface language of the site admin who's performing the (bulk) operation...

@AlfTheCat: Please open a new feature request for that.

@DamienMcKenna,

Thanks! Just created a new issue. #2973058: Create a 'user:language' token type (D7)

This patch saved my bacon for a views argument on an entity reference field. Thanks! RTBC!

This patch saved my day. Works like a charm!

Any further plans here? #2863200: Current interface language token (D8) is Fixed and this is RTBC.

Patch #32 is still working for me using Drupal 7.82 & Token 7.x-1.8
Thanks