The skosmos:hasMultiLingualProperty setting doesn't work as intended

[oddrunpauline]

Sometimes it is useful to view information about a concept even though the information exists only in another language than the selected content language. Typical examples are skos:note fields, which may exist only in the default language, while terms are offered in several languages.
In SKOSMOS, this should be obtained by using the skosmos:hasMultiLingualProperty configuration setting

Example: The setting skosmos:hasMultiLingualProperty skos:definition, skos:scopeNote
should imply that all skos:definition and skos:scopeNote instances - in our case written in the language Norwegian bokmål (nb)- are shown on their parent concept page also whenever another language, e.g. English is the selected content language.
See also SKOSMOS user group conversation.

Currently, in spite of the setting above, definitions and scopeNotes are shown only when content language is nb (like the language of the notes)

[kouralex]

Thank you for the report.

I have identified the issue around the following lines of code and will soon come forward with a fix.

Skosmos/model/Concept.php

Lines 580 to 583 in 254c2c6

	// only add literals when they match the content/hit language or have no language defined
	if (isset($ret[$prop]) && ($literal->getLang() === $this->clang || $literal->getLang() === null)) {
	$ret[$prop]->addValue($literal);
	}