WIXLIB

TH E T R ANSL AT ION NE T W O R KInterfaceYou don’t need to write different code based onwhether there is a translation system in place ornot. The LanguageManager can be different ifyou are on an English only site or if you have thelanguage module installed.INTERFACE LANGUAGE this- t(‘English text’)- getOption(‘langcode’);There needed to be a way to provide thistranslation service; a way that it can be switched.For that, you will use this t()-method, and theswitchability is hidden behind that. If you arecreating a controller or a form, you are probablyextending from base classes that are available inDrupal 8 core, like FormBase. It will already havea t()-method that you can use. It will work with theproper translation service in turn.This t()-function is internally quite different fromDrupal 7. When you call t() in Drupal 7, youget a string translated just in time. In Drupal8, the translation itself is deferred and youare actually getting an object. This object is aTranslatableMarkup object that wraps the originalstring and you can call methods on it. You canretrieve the langcode option (- getOption) usedto set up the object and several further methodsare available to gather data about this translationobject. This way, text can be translated later,before the output is actually created.INTERFACE LANGUAGEformat plural(.) this- formatPlural(.)In Drupal 7, if you had a t() call to return atranslation, if a form alter removed it later, weare not really outputing that string. But Drupalalready spent time translating it. Here in Drupal8, if it’s not going to be rendered, you are notreally translating it, so at the end, you may evenmake the performance of your site better. Thetranslation is only done when you are going torender the page.If you are creating your own class that doesn’textend from a base class that already has translation,you can apply the use StringTranslationTraitstatement and this trait will automatically provideyou the t()-method and the setter method for thetranslation service.In addition, format plural() from Drupal 7 is nowgone in Drupal 8. There is this- formatPlural(.)for that and it will work a similar way. You get anobject that you can actually alter to do whateveryou need.INTERFACE LANGUAGEclass Foo {use StringTranslationTrait;.}9

TH E T R ANSL AT ION NE T W O R KJAVASCRIPT APIIf you are doing JavaScript, it didn’t change much fromDrupal 7 for translation. You still have the Drupal t()method and the Drupal formatPlural() method.Drupal.t(.)Drupal.formatPlural()TWIG TEMPLATESFor templates, Drupal 8 uses Twig. In the PHPtemplates of Drupal 7, you would call t() on yourtranslatable strings, but in Drupal 8, that isnot available anymore. There are two differentmethods for translating your strings in yourtemplates. The first one is the trans filter. If youhave a string, you can pass it through the transfilter, and it will provide the proper translation.*LINKS.MENU.YML FILESAnother change is around menu items. In Drupal7, you had your hook menu() where you had yourroute, your menu links, your tasks–everything was inthere. Now in Drupal 8, it has been split. These areall located in YAML files. They are separated, so youhave your menu links in one place, and your routingis in a different place. It’s a more flexible system.In Drupal 7, you couldn’t call the t() function foryour title and description in your hook menu().This lets you cache your links and translate themlater to other languages.LOCALE.LINKS.MENU.YMLlocal.translate page:title: ‘User interface translation’description: ‘Configure the import .’route name: locale.translate pageparent: system.admin config regionalweight: 15Like in the t() function in Drupal 7, you can passthe context. If you want to request a translationinto a specific language other than the interfacelanguage, you need to specify that language.It is easiest to do that with the trans block. Allthe text between the trans and endtrans tagswill be used for calling the t() function internally.You can also have variables similar to those inyour PHP code.INPUT – SEARCH.HTML.TWIG input {{ attributes }}placeholder ”{{ ‘Search’ trans }}” / NODE.HTML.TWIG div{{ author attributes }} {% trans % }Submitted by {{ author name }} on {{ date }}{% endtrans %} /div locale.translate status:title: ‘Available translation updates’route name: locale.translate statusdescription: ‘Get a status report .’parent: system.admin reportsIn Drupal 8, it’s pretty much the same. They areYAML files, so you cannot call any function onthem, but there are some special keys (in this casetitle and description) that Drupal 8 will take careof translating. The potx.module will take care ofextracting them and making them available fortranslation on localize.drupal.org as well.In summary, the interface translation moduleprovides the ability to translate from English intoany other language.10

TH E T R ANSL AT ION NE T W O R KContentThe content translation module allows you totranslate all of your content, not only nodes andtaxonomy terms, but also any kind of entity that youcan have on your site. If you have Drupal commerce,it can translate your products and provides the userinterface for actually translating them.DEFINING TRANSLATABLE CONTENTThe content translation module is not based oncopies of your nodes or your entities. Drupal 8 hasclever objects that know about them. If you arecreating a ContentEntityTypes, Drupal 8 will makeit easier to translate them.NODE.PHP (SNIPPET)/*** Defines the node entity class.* @ContentEntityType(* id “noted”,* label @Translation(“File”),* translatable TRUE,* entity keys {* “id” “nid”,* “label” “title”,* “langcode” “langcode”,* “label” “title”,* }*)in. You need to define the langcode in the entitykeys. By doing this, you are telling Drupal thatthese entities may be configured as translatable.That doesn’t mean that all of your nodes can betranslated, it means that the user can go to thecontent translation configuration interface and setup if they want to translate them or not.DEFINE THE LANGCODE BASE FIELDIn Drupal 8 as in Drupal 7, we have two differentkind of fields: the first one are the fields that aredefined as part of the entity, and the second arethe fields that you can configure (add and remove)on the interface of the entity.If you are starting from ContentEntityBase, whencreating the content entity (which you should do),you have to define the base field definitions. Itprovides the base properties that every entity ofthis kind should have.CONTENTENTITYBASE.PHP (SNIPPET)function baseFieldDefinitions( entity type) {// .if ( entity type- hasKey(‘langcode’)) { fields[ entity type- getKey(‘langcode’)] BaseFieldDefinition::create(‘language’)- setLabel(new TranslatableMarkup(‘Language’))- setDisplayOptions(‘view’, [‘type’ ‘hidden’,For creating a ContentEntityType, you need to createa class, in a special namespace in your module andadd an annotation, which describes the metadata.This defines your content entity.])}}In annotations, you can use @Translation() so yourlabel will be extracted and you can translate yourlabels on your UI. For making the content possibleto configure as translatable, you only need to specifytranslatable TRUE. If you want to translate yourentities, you need to know which language they are11

TH E T R ANSL AT IO N NE T W O R KDEFINE TRANSLATABLE BASE FIELDSIt already has the langcode for creating the field foryou if you defined the langcode ket in the entity keys.For your additional base fields, ensure that you callthe parent::baseFieldDefinitions() method to get thecommon fields and then add your own fields. Foryour own fields, you also have a method for makingthem translatable, or rather as a field possible toconfigure for translation.Like images, other fields may be composed of differentproperties. You may also want to provide differenttranslatability options for them. In the case of animage, you may not want to translate the image itself,but you do want to translate the alternative text in thetitle. To make this possible, you can create groups ofMULTICOLUMN FIELD SNIPPET* @FieldType(* id “image”,* column group {* “file” {*“label” @Translation(“File”),*“columns” {*“target id”, “width”, “height”*},* },* “alt” {*“label” @Translation(“Alt”),*“translatable” TRUE* },* }NODE.PHP (SNIPPET)function baseFieldDefinitions( entity type) { fields parent::baseFieldDefinitions( entity type);// . fields[‘title’] BaseFieldDefinition::create(‘string’)- setLabel(t(‘Title’))- setRequired(TRUE)- setTranslatable(TRUE);}If you call setTranslatable(TRUE) method on a basefield, Drupal will know about its translatability. Theuser can also configure it differently then. If youmake an entity translatable, any field that has thisflag will be translatable by default.data columns. In this example, a file group is createdand the columns of this group–”target id”, “width”,“height”– are part of this group. An alternativetext group is also created where we are saying“translatable” TRUE.FIELD TYPES THEMSELVESIf you are creating your own field types, how dowe make them translatable? There is nothing youneed to do. They will be translatable automatically.Drupal 8 knows how to make them translatable,but for some kind of fields you may want to makemore granular options.This provides sane defaults for when you areconfiguring your site, so when you check translatingan image file and an image field in an entity, youwill see by default that you can provide differentconfigurations for the file itself, for alternative textand for the title (not represented here for brevity).And by default, the alternative text and the title willbe translatable, but not the file itself. You can make ittranslatable if you want.MULTICOLUMN FIELDSTo define an image, you will have a reference toa file entity. You will need to know the width andthe height of the image, then you can define thealternative text and the title of the image.12

TH E T R ANSL AT IO N NE T W O R KENTITY LANGUAGE APIThe Entity Language API is quite straightforward.You have a node class for dealing with yournodes. You have the same kind for any entityyou create. You have a load() method on it, anda getTranslation() method to retrieve specifictranslations.ENTITY LANGUAGE API node Node::load(42); node node- getTransation(‘hu’); node entityRepository- getTranslationFromContext( node);You may not know which translation you want. Ifall you know is you want a translation appropriatefor this request, use the entity repository. Call thegetTranslationFromContext() method and pass thenode. What you get back is a node in the currentnegotiated language.There are a lot useful methods that we can usein our entities: node- getUntranslated()–gets us the sourcetranslation node- language()–the language of the currentloaded translation node- getTranslationLanguages()–the list ofthe language objects for translations of the entity node- hasTranslation(‘hu’)–is there atranslation for a specific langcodeIf you call the getTranslation() method, you canrequest which translation you want to work withand you will get a reference to the translation.It’s the same node, so you can do any operationsyou want with it and then save it or edit the fieldsas you would with nodes in any other situation.Language here is quite easy to use and translationsfrom these nodes are quite easy to access. node- addTranslation(‘hu’)–for creating it node- removeTranslation(‘hu’)–for removing itThe best thing is this does not only apply to nodesbut also other content entity types, such as users,comments, taxonomy terms, etc.ENTITY LANGUAGE API node- getUntranslated() node- language() node- getTranslationLanguage() node- hasTranslation(‘hu’) node- addTranslation(‘hu’) node- removeTranslation(‘hu’)13

TH E T R ANSL AT ION NE T W O R KVIEWSViews has two key purposes: Creating queries onthe system, and then render it. You can see thisseparation in the first two columns in the Views UI.Language is integrated in both.You can filter by language. You can filter yourviews by a specific language, or you can filterby the language that was negotiated for thepage. On the rendering side, you can pick whichlanguages you want to render the found entitiesin. With Views, you can say give me all the nodesthat are in English and then render the Germantranslations. These are the two different ways todeal with language in Views. It’s quite powerful;you may not need the PHP APIs at all.Content translation provides the ability totranslate from any language to any otherlanguage. Your entities are intelligent objectsso you can actually call the methods on them–for getting the translations, for dealing withtranslations, editing translations, etc.Configuration TranslationWe have two kinds of configuration: configurationobjects for global settings and configurationentities for things that can have multiple instances,like configurable languages. Configuration is storedin YAML files with a langcode property.CORE.DATA TYPES.SCHEMA.YMLFor making our config translatable, you need toprovide a schema. It was introduced in Drupal 8 forknowing how to translate or deal with languagesin your configuration, but it is now used for a lotof other things. Drupal defines some base typessuch as config object which has a langcode. Globalconfiguration is usually typed as config object.There is another key data type for translatability,which is text. It is a string that is translatable.When these data types are properly used, a bigadvantage is Drupal knows to type-cast data to theright types, such as integers to numbers.14config object:type: mappingmappinglangcode:type: stringlable: ‘Language code’.text:type: stringlabel: ‘Text’translatable: true

TH E T R ANSL AT ION NE T W O R KTo create your own schemas, you need to create aschema YML file and then define the types of yourconfiguration elements. Here we are defining thesystem maintenance configuration. We are sayingthat it is a config object. This means that it willhave a langcode and you can define its furtherattributes. We know it’s a message of type text, sowe know it will also be a translatable string.CONFIGURATION API manager \Drupal::languageManager(); hu manager- getLanguage(‘hu’); original manager getConfigOverrideLanguage(); manager- setConfigOverrideLanguage( hu); config \Drupal::config(‘system.maintenance’);// . manager- setConfigOverrideLanguage( intenance:LANGCODEtype: config objectlabel: ‘Maintenance mode’mapping:TRANSLATABLEmessage:STRINGtype: textlabel: ‘Message to display.’Here is the message and langcode. When it’stranslated in configuration storage, there will be alanguage folder for each language with a langcodeas a name. There will also be a file with the samename. Only the translatable elements may show upin these files.SYSTEM.MAINTENANCE.YMLmessage: ‘@site is currently undermaintenance. We should be backshortly. Thank you for your patience.’langcode: enTo access the configuration of your site, use theDrupal config service. You pass the name of theconfiguration object that you want to retrieve andthen you can access the properties with the - get()method so we can get the message from the systemmaintenance object with - get(‘message’).If you have language overrides, they will apply asappropriate. If you have a settings PHP overridethat will also apply.Configuration with overrides applied is the mostcommon for settings used at runtime. Drupaluses the negotiated language for the page toinitialize overrides. If you know what languageoverrides you want to apply instead, you needto use the Language Manager and you can call getConfigOverrideLanguage() for storing thelanguage Drupal is currently using. Then you can seta different one M.YMLmessage: ‘@site karbantartås alatt all.’LANGUAGES/IT/SYSTEM.YMLmessage:’@site .’15

TH E T R ANSL AT ION NE T W O R KThis can be quite useful if you are sending emails.An admin may be visiting your site–your admininterface in English–but you want the usersthey are sending emails to to get emails in thelanguage they prefer. You can get the languagefrom the user object, set the config overridelanguage, then use the configuration with theappropriate language overrides applied forsending the email. Then you can set it back to theoriginal language Drupal was using before.We have three different ways for dealing withlanguages with Configuration.CONFIGURATION IDES APPLYAS APPROPRIATE\Drupal::configFactory() getEditable(‘system.maintenance’);NO OVERRIDESAPPLY\Drupal::languageManager()- getLanguageConfigOverride(‘hu’, ‘system.maintenance’)- set(‘message’, ‘Karbantartás.’)- save();THE e’) providesyour configuration with every override applied. Ifthere are competing overrides for a value, Drupal’spriority system is used to decide which override keyprevails. \Drupal::configFactory() getEditable isfor getting the current configuration in the originalraw format, so absolutely no overrides applied.This is useful for actually making configurationchanges. Finally \Drupal::languageManager() hasa method for getting a concrete config overrideitself: - getLanguageConfigOverride(). So you canwork with the overrides themselves, the raw configwithout overrides, or we can ask the system toapp

The Drupal 8 Multilingual Initiative made that a priority for this release. The power of Drupal 8 lies in its ability to assign languages to any content or configuration, along with the improvements in the APIs and user interfaces for localizing and translati