 and even there are people coming in. Welcome, welcome to DrupalCon Austin. Welcome to the first session. Great that you made it all here and you found your way into multilingual. So the first session is about Drupal8 multilingual and or Drupal8 core is more multilingual than Drupal7 with all of Contrape. So who of you has built a Drupal7 multilingual site? Okay, Drupal6. Okay, Drupal5. Who never built any multilingual? Okay, you will be excited. The other people have an old time and it was hard in back days. Now it's pretty much easier. Whoever tried out Drupal8 multilingual? Good, okay. So, who am I, what I'm doing here? So I'm Michael or schnitzelundry.org and when I'm not sitting upside down on our couch in the office to think about stuff or flying drones at Kino group videos. Yeah, I'm working at Amidelabs. We are a company in Zurich and I'm part of the Drupal8 multilingual team. So that's a small neat group team of people that are really interested in multilingual and get Drupal8 multilingual as much as possible. One of them is Tobias and he recently tweeted that so with content and configuration in core, it's more translatable than D7 with all of contrib. We already heard that. So the people are really happy that we finally have that in. Maybe some plugs here. So the presentation is actually not done by me. It's done by Gabor. He is the initiative lead. He planned to be here, but he couldn't be here. So I told him, hey, I take over the talk and bring all the multilingual love to Austin. So to talk about multilingual, Gabor has actually, he's from, from, where is he from? Romania? No, Hungary, thank you. Yes, and he has a bit of special name. And it's like with the multilingual thing. So whenever we like from the Europe, we have a lot of languages, like Switzerland has four official language, but we actually built sites in five. So it's a lot of issues around that. And so, and one of the interesting thing that happens to him all the time is that his name got mixed up. So the double cross is not a double cross. It's actually an A with an M present on top, but a lot of custom fonts can't handle that. And it's the same with other languages. Like German has umlauts, a lot of issues. So he has a really big repertoire of issues where his name is written wrong. And that's one of the things that we really said, okay, let's not only like, or let's make Drupal 8 really multilingual aware, but don't just stop in like other languages like English. We go far, we wanna support everything. And Gabor can finally be happy that his name is spelled wrong every time on batches or wherever. So let's talk about Drupal 8. As you might know, Drupal 8 has a lot of different initiatives. There is the services, there is configuration management, there is mobile, there is views. There are a lot of different things. And we in the multilingual team, we have a pretty special standing because usually the other initiatives, they come up with something and they say like, hey, we got that really great configuration management stuff, let's build that in. And then they start to talk to the multilingual team and the multilingual team comes in and says like, ah, I'm really sorry that that doesn't, it's not translatable or we need that additionally. So we're usually like in contact with all of them. So we are a bit disruptive inside of Drupal 8 of the development, but that's really good because together with these people, we figured out ways how to unify things, how to make everything translatable out of one point. So we'll see that, but when we talk about we and I said before the D8MI team is small, it's actually not. So we are a lot of people that helped working on Drupal 8 multilingual. That's only the people that ever wrote a comment a post or something else on Drupal 8 multilingual issues. And that's really great. If somebody is here, thank you very much. And I know some people are here which helped on that. It's a really long time. We were working on that since a long time, but now we are finally getting to the end and we are super happy about that. So in total, more than 1000 people have now contributed so far. So if you just were at the keynote, that's like a third of that what we saw there was all people that helped working that. So it's a huge group of people, a lot of people that put effort of their free time, sometimes of their working time into that to do that. And of course it's humans. So we're not sitting at home and do our own stuff. We do that sometimes. Yes, we are geeks as well, but we are also having fun. So we meet occasionally in different times and you see in the middle that's Gabor. We have Cathy and we have Das Peter working together, discussing things. We have Clutch that's actually shortly before he got in the entity translation patch which was one of the biggest one. So a lot of thinking there. We are at Sprint, we have fun, we talk about stuff. We not only go together, we go out in the evening. We have fun, we drink, we eat. So if you wanna join, join us. At the end I will tell you how you can actually get involved. So in total these more than 1,000 people have managed to handle more than 1,000 issues inside of Drupal 8 and that's also a lot. There's a lot of things to fix. There's a lot of things to re-factor again. So all these people together put a lot of effort into Drupal 8 to make it what it is right now. So let's go back a bit. Drupal 7 multilingual. Whenever you wanna make a site, the first thing you have, you have Drupal Core. And then you go to the module list and there is a module called locale and you load that and it basically allows you to have multiple languages and you have a language as UI. That's it. That's all that locale does. So you stand there and say, okay, now I need more. So first thing that you want to have is maybe there is contributed translations. So there's a module called L10nup which allows you to automatically download contributed translation. So there's a website called localize.drupal.org where people put their efforts in in translating Drupal and also country modules. Like the most common modules are fully translated in other languages. So whatever you need, if you download views and you have L10nup installed, it automatically downloads the translation and you have it in German and you have it in French and you have it in a lot of different other languages. So UUI is now translated but now the editors start to enter content and so you need content translation. The problem is it only works for nodes. So the only thing that you can actually translate is a node and it makes copies of that node. So then we will see later that that's actually sometimes a really bad idea. But whenever you want to translate something else, let's imagine you want to translate a taxonomy term or a menu link or whatever that other is on your site or you have a block, you run into issues. So for that we need another module and it's actually a whole suite of modules. It's the IATN and it has additional modules. So you have menu translation, you have taxonomy translation, you have field label translation, you have views and then you have web form localization. So it's a lot of additional modules you need to find, you need to download that sometimes need to be in the right versions that they work with each other and not and then you continue working on it and then maybe you send out a mail and you realize wait that's not translatable so you go and search and you realize oh there is a variable, there is a variable API so I can do that too and it uses a total different UI and yeah so you're happy and then your customer comes and says I would like to have a shop and you say well that's fine I do content translation with that and then you realize that actually you have 10 times a blue t-shirt and like if you use commerce with stock information because end content translation clones your notes so it also clones the product, suddenly your stock is not correct and you have to synchronize that and it's a lot of hassle around there so people came up with another module which is called entity translation which allows you to translate notes on a field base rather than actually copying notes so you look at that and it looks like six modules but it's in total like 27 modules you need currently 27 modules if you have a really big Drupal site with shops with domain access and all these things you need 27 modules to actually handle localization properly, it's really cool because you have a fully translatable website but it's a lot of pain so we said that's really cool let's trip it down to four modules there are four modules in Drupal 8 core now which are shipped which handle all that we saw before in 27 modules it's all in four so what are these? First it's the language module it's the base for everything that you need it basically explains Drupal what the language is and how a language works it's not multilingual itself it just adds some language stuff to it it doesn't allow you to translate stuff yet then we have the interface so that's everything that you see that is shipped by other modules like the submit button or something and in there we automatically added the update feature and we also added a lot of usability improvements there's accessibility improvements so we not only took the modules from country put them in core we re-vectored them, we thought about them we rebuilt them, we wrote tests and all these things then we have a content translation and that's the, it's on a field level so it's the old Drupal 7 entity translation is now in core and called content translation and it has a better user interface it's easier, it's the REST API, ABLE and all these things and then we have the config translation so config the new kid in the blog in Drupal 8 where everything that you configure like a view, like a vocabulary an email is now config and we support config translation so it's a common system that allows you to translate any config you can imagine that you have on your site and it's also integrated into the other systems so let's speak about the single systems first language and the coolest thing in total Drupal has the installer the first thing that it asks you is which language would you like so if you select another language it will automatically download the translation while the installation you can install in another language whatever it is and so you have the best experience to start the write from the beginning with the write and translation so everything is there it all works and when if you can read it you can install it the way so you even see here it's right to left so that's also supported from the beginning it downloads all the modules it also downloads automated translations for them if they are unlocalized through pod.org and you have your site right away and the really coolest thing English is not even there at the end and whenever you build a site and you don't need English but there is still an English or you maybe want to change something it's not there anymore the language you select in the beginning is the language you're Drupal is in so to actually do that we need language assignments and in Drupal 7 we have language assignments for these so we have notes we have aliases and we have users now in core we actually go further so we have we have language assignments to terms and whatever it's translatable there we have language assignments to views so you can create different views for different languages like if you want to have your front page being different for different languages because you have a lot of content in English but you don't have so much content in French that's all possible we have site information like your site name or your slogan sometimes that's not always exposed because we found out that in usability studies that it's sometimes really hard so we try to also make it easier there but there is way more so basically everything that you have now in Drupal core has a language assignment and you can define that's only for German that's only for French that's for both or whatever so that's really cool we also have a really flexible language setup so you can now actually so we have a new UI that allows you to set up the languages so whenever you used to be in Drupal 7 you had to go to each single field and specify if it's translatable or not we unified all of that and there is one single form that allows you to set which entity is translatable which field even with subfields so if you have images you can translate the title and the alt text but not the picture itself or the field itself you can do everything by a one UI and it's all in there and it's way easier to do it to make changes and not like clicking around and figuring out where you do all these things the next thing we have language visibility so blocks per default can be shown and hidden based on language which was also only possible via country modules before then views are already set up that they only show their correct language or the correct node in their correct languages and another really cool thing is as you heard views is in core so everything that is a list is now a view and the view is translatable so that's one of the points that where we said look views if you make your whole view system multilingual possible automatically every backend is multilingual aware so that's like these things that we went in with other core initiatives and worked with them together to fix these things another point that we used to have is language selection so it worked pretty well but sometimes you had some issues with like okay which browser language should it load so we also unified that UI so you can now define each language code that is for German because there is not only German there is Swiss German there is French there is Austrian German there is worldwide German so there are a lot of different ones and you can define now all of them by UI and it's much easier things that you used to have write custom code before is now all in there and works so you can define them which language code assigns to which language good next thing coming back to the beginning name transliteration so what's transliteration that sometimes people enter the things in their languages which obviously is the case but Drupal needs machine readable code sometimes like for exports and things so it needs to be in in a default character so what it allows you is whenever you type in another a string in another language it automatically translates that to something machine readable and that also used to be a contract module and now it's in there so whenever whatever you type in you don't get a crazy error saying that's not possible for machine readable people just type in whatever they use to and it automatically changes to what Drupal can actually understand in there good one really cool thing and especially when you don't need English English can be deleted and you can also be deleted afterwards that's really cool because especially when you have a non-English website you still have that English and sometimes English pops up somewhere so finally English can be deleted and you can add it again it's no fixed boundaries to need to have English all the time okay so that's everything that is done via the sorry so everything that is done by the locale so you can delete English you have a flexible selection you have block visibilities you have views support we have a config we have wider assignments to almost everything inside of Drupal Core with translation with languages and you are the first step in the installer to whatever language you would like to have to install next point the next pillar interface translation already mentioned we automatically translate or automatically download translations of modules when they are unlocalized to BodeLog also whenever you do your own translations there's a centralized file so if you change something and you need to ship that to a live site to to deploy that it's all in one file now we have customized tracking so whenever you override shipped translation or a downloaded translation Drupal realizes that you changed that and the next time you update it's not deleted or changed Drupal knows it's as custom translation treated and won't override them and then also we we had a lot of issues with shared hosting that the download of files took really long so we put that everything in batches so whenever you're on a shared hoster that you can't run stuff longer than 30 seconds that's all handled by the batch system and will allow you to download translations also we have a whole new interface and that was also a lot of time in there because especially if a lot of languages it takes really long to translate your site before like you went to the user interface and you had to click to edit for each single string you save it then you go back and then if you page you had to click back on the page it just was really hard so we said okay we remove all the clicking and we just do the writing so now it's like that so whenever you search for a string it shows you directly on the right side it shows you the translation you can enter it immediately it also has a plural support whatever crazy plural system that some languages have because it's not all this English where we only have two the crazy one has five different plural versions so that's all supported by Drupal out of core and you just change it you go through you edit it, edit it, edit it you save it and you're done of course you also have the filters on top that you can only check for the strings that are not translated so all that is in that we used to know next we can translate to English so we not only have the issue that we want to remove English sometimes we actually want to change it because maybe the shipped English translation comes with with some translation that you don't like or with some English that you don't like you would like to change your customer uses a different type of English to talk to their users so how you do that in Drupal 7 you created another English to actually do that but then you had the problem with the language assignment of the browsers and all these things so we said okay let's just do it we can translate to English important it's not activated by default so because of performance reasons per default that's not enabled but you can go in and you can just enable translation to English and then you basically just translate directly to English so you can change whatever is there in Drupal without needing having a second language that confuses editors and users and all things so that's really cool especially if you need to change that a lot it works exactly the same so you just change your language to be translatable and then you go into the interface and it all works as it is in normal language so that's all of that pillar so we can translate to English we have a whole new interface which is more usable and more accessible we have custom translations that nothing of your stuff is overwritten we have a centralized file here so whenever you do customs it's all in one place we have auto downloading and it's all in a separate module so if you don't need it you just disable it it's not automatically in there as it used to be in Drupal 7 next pillar content translation so first all content entities are supported and with Drupal 8 we even have more content entities so we not only have notes we have terms we have users we maybe even have menu links we'll see and so all of that all of that is supported out of the box and whenever you have a content entity or if you build your own content entity as a developer it's fully supported it's there the API is there it's all done automatically maybe you wonder wait content entities doesn't it used to be entities? yes so in Drupal 8 now we have the entity system and in there we have two different type of entities the first ones that we talk about now are the content entities so that's notes user comments terms content messages menu items so all the things that actually the editor goes in and changes so he creates notes user generate comments etc so it's all integrated in there so whenever you create one you can directly set in the unified system you can just enable it and you click all the fields you would like to translate it shows you all of them and you go through you decide which one do I really want to translate and at the end you press save and it's all done again no need to click around find things how do I actually set stuff up to be translatable and one thing I really like is the file so you can you cannot translate the image but you can say the alt text and the title so that's like a thing that happened a lot in Drupal 7 that like everything was translated and then you hovered over an image and then the alt title was not translated so there's a module for that but now it's all there it's all in core the translational interface has adapted a bit we try to keep it as much as simple as people you know it from Drupal 7 so whenever you have a content entity you have a translation and translations tab you just do you click on it and you can add translations for each language which is one really cool feature you can actually change the source language a common problem that we have so we have like three different languages it's first created in German then it's translated to English but then the French translation has to happen from the English translation not from the German one because it's cheaper so you need different source translations and that's now setable so whenever you go in you can say defaultly it will go to your default language but you can say no I want to have a source language I want to have something else that's really cool and then also we have all languages so some fields you can set to be translatable but you can still change them in the translation itself and the permission system handles that really neatly and all these things so we want to look at that you see that whenever on the right side it's a new UI of Drupal 8 of the edit screen so you see on the right side you see all these all languages that tells the editor that these parts will be also changed in the source translation and yeah it's much easier and you see the title and the text in the body you don't have that so that's actually translatable so it shows the editor that changes the translation immediately what he changes will do property translation is in the works so we still have the issue that the title is not fully supported there's a lot of stuff happening there we will support that and it will be in there's still some small issues so if you want to help on that come on Friday to the sprints and there's some stuff to do there there's also a lot of stuff to just test so even if you're not a developer come and join us we have stuff for you to help us there upgrading it used to be upgrade now it's migration so migrate will be in core and we will also handle that so people are currently setting up crazy Drupal 6 sites to support translations and they have a lot of notes and translate and do every possible setting to handle migration with Drupal 8 so we won't upgrade anymore you will install your whole D8 site completely new you will point the migrate system to the old site it will figure out what type of content types you have how the translation used to work and migrate all that stuff over which is much more solid and secure than anything else than like just running an update PHP and hope that everything works because it definitely won't core, search and API so we done all the search stuff so the search out of core has language support that's really cool we've done node access support so if you need it you can have different access per language like that some that say you have the English published and now you create a German but only some roles are allowed to see the German version even if it's the same note the node access API can handle that so country modules can hook into that that's really cool so that's all about content translation and we have node access API we have search we have updated search APIs we have every content entity covered we have bundle fields we have subfields with the files we saw before properties are still in the work and we have a migration path so even inside of content translation everything works really well the last thing config translation so as when I'm coming back to the slide before we said there are entities and there are content entities and then we have configuration entities so inside of the entity system you have content and configuration entities configuration entities are things like views vocabularies, contact categories, fields and they are also translatable and they're handled by the config translation module unfortunately there are some small things out there so path aliases are no entities at all they are translatable and they are handled by itself so they have the small integration into the translation system and one really big thing currently are many items so there is a really big idea to change the monies and many items into content and configuration entities the problem is a bit performance so there is a lot of issues in there to make your site really fast but people are actively working on that that we can also translate many items so it's out there in the others but we hope that soon it will be back in and we have a fully translatable system we're close to beta so things happen that are a bit scary sometimes but no worries we will handle that language is tracked in each config file so if you never worked with configuration management before each configuration has its own file and it's tracked in there and you can actually override that so the shipped configuration which is the default configuration is added to your core to Drupal core and then you can override with another file so when the config is loaded it checks if there is an override file by language and applies that and that's actually how the whole translation works so a really interesting thing is that we cannot only support actually translation we can handle multilingual sites because multilingual doesn't mean that sometimes you have a translation an example the front page let's say you want to have different front pages you don't actually translate the path for the front page you just change it because you would like to have a different front page in German and in English that's not translation that's multilingual and that's handled by overriding the configuration storage so whenever the config file is loaded which contains the path to the home page you can have a separate, a second file that is loaded and then changes that to whatever you would like to have it so we have a short video on how that works and so for a shipped configuration we would like to change the website feedback in there so we just go where in the translation system and we search for that string their website feedback so it's also integrated even config and config translation is its own thing it's integrated into the UI you change it to whatever you would like and then you change the language and it's there so some people won't even realize what is the difference between config translation and string translation or interface translation and so it makes it easy for your editors because you just tell them if you need to translate something search for it change it, save it, go back it most probably will be there one thing that is unfortunately still missing but I think that's a good thing because we don't know yet how we will really do it is the integration into localize drupal.org so localize drupal.org is as mentioned is the site where people help translate country modules and core so the integration is still missing there but we will work on that whenever we fix all the beta stuff and also the whole thing works for any configuration so whatever you imagine not only the title there if you want to change something else you can do that via the system so you can for example translate the block title of the language switcher which is a block and we can change that as well you just search for it and you change it and it's done so here we see that we can also go directly inside of the config where you or the config entity where you change it you can also have there you have a translation tab you can change it and save it and done so config translation is its own module that handles all of configuration and it adds translation tabs as the content translation so it's again there unified in the UI you have the possibility to override existing configuration it works for any configuration and also the shipped translation or the shipped strings you can translate in there so important if you build your own modules or if you build your own entities please please please please please use content translation or use content entities or use config entities if you use something else you won't be covered if you use it you're covered so you basically just define your config entities and they're automatic translatable if they have a UI they automatically have a translation tab so you don't even have to worry about as a developer what you really need to do in there so coming back we have language module which provides us a base for any language we have interface translation module which does everything in the interface we have a content translation module for all the content and we have a config for all the config so I guess if we look back actually to Tobias what he said he's pretty right so coming back from 27 modules in Drupal 7 we're back to 4 in Drupal 8 and it can actually do more it works better it's more usable it's more accessible it's nicer it's faster so whenever you do a Drupal 8 multilingual site and I've done one it's so much easier it's so much better so it's really cool but we're not done yet there are still things to do so if you're sitting here and think like okay that's really cool I wanna help I wanna try out I wanna test and that's something that we really need right now we need people that just set up a site go through it and test it or try to build your site and whatever happens write an issue and Kathy will look at it and figure out if it's bug or not so if you're up for helping come this Friday there are the sprints happening in the convention center as well if you never helped before no worries there will be mentors that help you setting up your site help you how the issue queue works it's really well organized so if you have time if you plan to go to Austin come to our sprints it's much more nice here and you can look at pictures of all the other people that took pictures in Austin or next time for the next come organize your trip actually till Tuesday because the sprints are not only on Friday they're also happening on Saturday and Sunday so you can come and help us there and if you can't there is a website www.drupal8multilingual.org where you find all the information current issues we're all working on and there's also www.localizeddrupal.org because we need to translate we start translating Drupal 8 into other languages we have new strings we have new features they need translation so if you speak a language even better a super fancy language that nobody else speaks go and help us there we really need your help and also there's a Twitter account the8mi where we update what's currently happening if we need help what's all in there and actually a really cool thing is you can try it out right now so if you go to www.drupal.org slash 8 you land on a site that is the www.drupal8 site on www.drupal.org and there is a button that is called test www.drupal8death and it's a really cool system of some of the core contributors that allows you to set up a site in your browser you don't need any development system on your local it's all happening on cloud servers so you can set it up you get 30 minutes to try out so if you want to try something and especially during the sprints that will probably happen a lot go there try it out play around and break things it won't break anything else than your own site so nobody's there so that's it first really really really thanks to all the people that helped here so that or on that slide there are also people that maybe are not on that slide and talk to Gabor but there should be all the people that ever worked with www.drupal8 multilingual should be on there it's really great that they spent their time to help us to make www.drupal8 a better multilingual experience that it ever was and yeah that's it I thank you so we rushed a bit through that we can get the time delay to not like delay other sections but if you have questions we have 13 minutes for questions yes and we need the microphone wherever it is stand up walk to the microphone we can answer the questions yes so when you're with content specifically in www.drupal8 what's the best process for updating translations like doing it right on the live site with workbench or migrating it from stage to production with www.drupal8 now yeah it's www.drupal8 there is no content staging yet there are some talks actually here about content staging in www.drupal8 so that means like you first create your translation on another site and then you migrate it over so migrate module itself will definitely help us there but I can't tell you exactly how their plan is for content staging in www.drupal8 and so currently and what we did on our site is that yeah we just so each translation has its own published state so and you basically start to create it and you don't publish it yet and people look at it and then you publish it the problem is that sometimes views and stuff is based on publishing status which is probably the case why you want to have it somewhere else to really look at it so that's not supported out of core but there will definitely be country modules that support that and they will be also multilingual aware because if they use the whole content entity and the config entity it's all one thing and it will be supported hi just a quick question I wish I could deploy my product on d8 course it's not quite ready yet for that is there a place where all 27 of the modules in d7 is documented where I can figure all that out quickly there's a book there's a book that's fantastic thank you yes told talk to her she will tell you how it works yes project wise for drupal8 I'm just wondering if this is anywhere on the radar I run a site that's on all over the world Latin America, Saudi Arabia, China, Indonesia one of the problems that we're running into is the subject of gender in Russia sometimes the sentence will change completely some verbs will conjugate it differently depending on the subject in Spanish and French there's object gender in Saudi Arabia there's some verbs that can't even be used by females yes is that anywhere on the roadmap it's not handled specifically by core that you have like gender specific strings or so and so it's just at the end you translate one string into another so the translator that does that probably needs some context information about that I mean sometimes you want to match like a sentence to an object yes some way to store that object ah okay hmm what you could do because everything is an entity now you can add fields you can add fields to end to files you can add fields to new users so if you need additional metadata information about objects if there are entities in drupal add them fields so you could say like that car is female or male with just adding a field to the image of the car of the of the entity and then basically use that for the first if that would help but there is no gender assignments like there is language assignment but if it's a really big case I mean so first it's definitely way easier to change that stuff in drupal eight with like overwriting existing systems then it used to be in seven so if you really need that yeah maybe maybe look at the apis in eight so that will be definitely easier hey there I'm Kevin Kiva and we use drupal to translate about ten thousand plus loans every month yeah and it's been really awesome seeing all these improvements I'm really excited for these but what I am curious about we're kind of a decision point over actual translation tools for the translators themselves to improve their translations and this is something that I think drupal hasn't quite picked up on yet and often times our translators are jumping out of drupal pasting their text into the big external translation products doing their work there and then bring it back so do you guys think that it's the right decision to put effort into building translation memories and search translation suggestions into drupal or do you think that this is something that we should allow the third parties to continue to do that what they do best yeah you need and you can come to my talk at one if you're interested in how we're doing that as well cool so one thing one thing that definitely addresses your issue is that so transition management tool is a system it's actually a whole system with multiple modules that allows you what that connects when like drupal actually stops so a lot of issues like okay you can translate your site but you maybe have external translators or you have like workflows to review translations and stuff so transition management tool is built for seven and eight and supports specifically that so you create a job out of so you have different translations like many items terms you can put all them in a job and send them somewhere else and somewhere else is either a translator that is on your local site local drupal site or a service provider via an API so that's definitely one of the things that I will check out also there are people sitting here from translation providers like Lingotech right there so talk to them because they do really cool stuff about translation memory and I know they have a drupal 7 module I don't know about the 8th module yeah it's nodding okay so there will be also a drupal 8th module to handle that so you're covered but not by core itself thank you yeah keep that page up can we talk a little bit about the work that's on d8 for this module and like is working on it in here does anybody working on it in here? I'm working on it yeah so the process is that the core is let's say that the core is all migrated so drupal 8th translation management tools works it actually works better because of the whole entity system it's much easier the source and especially the translator plugins are not all yet done but the Microsoft Bing translator and I guess the Google automated translator they are there so most of the stuff actually works so if you're interested in that download it, try it out yeah I don't know about the Lingotech how is your drupal 8th module going? 10 lines of code, good that's all in it so we're working in progress but we'll be there perfect, cool hey Michael I have a question for you do you have any fun when you work on contributing to multilingual? if I have any fun on it we have a lot of fun yeah we do why you ask? because I want you all to know that it's not stressful at all and we do have a lot of fun and we're really supportive and we will help you wherever you are and make you feel really productive and be really productive and if for some reason your travel situation means that you can't come on Friday the whole entire community has got a completely different mindset now than they did several years ago and you can go to the 24 hour coder lounge sit down next to somebody you don't even know tell them you're new what you're interested in and they may not be able to help you but they will spot somebody else in the room and be like oh you should go talk to someone so I think they can help you Friday is the place to be but don't let that hold you back if you got to go home you got to go home we still have some other more relaxed opportunities in the 24 hour coder lounge yes so come on Friday definitely walk in and tell them you want to go to the best initiative and there will be somewhere assigned that calls D8MI or multilingual and we will all sitting there and working with you and we'll make Triple 8 awesome yes thank you Kathy so I'm sorry if I missed this point earlier but I'm still a little unclear about the integration between the interface translation and the content translation and with Triple 7 now it's a little bit of a pain to have to export all the translatable strings out with the POTX module and then to have people translate the content can you speak a little bit more about how Triple 8 will address this to be honest it's unfortunately still so as we saw there are three different modules there are still three different systems some kind so the content translation is completely separated from a UI point and also from exporting and importing than the others the interface translation has the new UI where you can directly translate and config translation as it used to be with IATN in Triple 7 directly shows you stuff in there so it's a bit combined with interface and config translation where it's its own thing but if you import and export you still have the PO files so that's not something that we really address that's something that I want to fix for 8.1, 8.2, 8.3, maybe 9 whatever to like make the UI unified because when we look at other CMSs what I saw there like in type of 3 you go there and say like create me a translation file and it outputs you an XML file which contains everything in there so you have your content and your config and your strings all in ones and you translate that and you throw it back and it's all there and the translation management tool handles you part of that but it's still a lot of different pieces so the process that we actually do is we first unify all these things that happened with Drupal in it and now we have a base that we can really work on to make the UI and like the whole process really really really great around that but we first need to fix the base so if you're interested and if you have ideas let them down, come to us talk to us because I guess we're interested in like knowing how we should continue in there as well but currently there's nothing really that fixes that so it's still like hard to find strings and so Hi Hi, I think you touched on this perhaps when you talked about path auto under the other category We currently use path translation on our site for so for example like a login URL we have login and then we have the other language we are not using more than one language on our sites right now but obviously we're going to have to move into that because we're international and I was wondering what kind of work you guys are doing right now in regards to paths because that's of interest to us and we've had some issues where we've targeted a path and right now it's English base and I was very intrigued by you talking about English no longer being a base Yes, so inside of core it's now the base it's not English anymore it's just language and you can translate that to English so if I understand your question correct so you have like different like paths for like slash user slash login in different languages and in 8 you can assign them languages so would that already fix your issue or what did you think like the English is the base Go and fix it, I mean one of the things we've done is we've targeted certain paths for SSL things like that so obviously that's in the past I guess with like actually assigning languages to paths or path aliases will fix a lot of issues to like have different ones and the question is if there is a module that actually redirects you to the right ones because sometimes you go with another path prefix then the path is itself but I guess that's definitely fixable as well so I hope you're fixed but you would definitely need to try it out more Sorry Good, awesome Yes Hello For those of you who haven't seen it yet there's also a duple 8 multilingual bof Gabor has said that he's going to try and come remotely at least it's going to be kind of late his time just like Schnitzel said he wasn't able to make it but so tomorrow one o'clock in the afternoon if you're interested have questions or just want to hang out and talk about duple 8 multilingual issues that's also a great chance especially if you're not able to come on Friday or over the weekend Cool, thank you, that's awesome Okay Yep 10B or 10C, yeah third floor It's on the schedule but check it out Good, hi We use multilingual pretty heavily but I'll preface this by saying that we're on a really customized D6 version and we're going to be skipping to 8 So if some of these questions are already solved I apologize First of all, do you know is there any initiative to have regular expressions searching in the interface strings that's the issue that we have right now? No, but you should be able to It's really easy at that Okay You mentioned that in the content translation there was a way to turn off translation for certain fields like for example if I didn't want to translate one particular field it would just not be available for translation Is that going to be available for the interface and config strings as well where you can turn off individual fields as being translatable So you mean that Sorry So on the right side you see all languages and I think the slide that I was remembering was one where it had a bunch of checkboxes for each field in the content type where you can turn, you can disable I don't know why you'd want to do this That's how it ends up then, being shown And you would like to have that for? For interface strings Oh For config I'm just wondering if that's possible I can't think of a particular So it's more of a permission question than actually a site building question Not really because we do all of our translation exported So if I could prevent export by saying for example maybe this is a terrible example but a views column header if it was not exportable that would be awesome There is no such system in core It's really easy now with 8 to hook into that stuff and basically change the controller that is responsible for exporting things So you could easily do some kind of like that each config entity has a checkbox not translatable or prevent translation and when you export that look at that checkbox and do whatever you would like to do you would know not of a module that can do that but from lines of code maybe it's a bit more than 10 but I shouldn't be a lot of code to write all that stuff And then briefly real quick you mentioned that I'm very sad to hear that the interface and config and all that is still PO files that's really sad It's not with TMGMT as XLIF you have services integrations into service providers so that also fixes you that because yes PO files I also hate them Okay, excellent, that's exactly what I wanted to hear Thank you Okay, I guess we have to last question or last saying and then we have to wrap up I just wanted to mention that the bot there's also a multilingual bot for Drupal 7 for those of you who are stuck in the dark ages actually a lot of sites are still much better, right where a lot of sites happen to live and so if you want to talk about how to get that multilingual Thursday at 1, there's also a session Okay, so Wednesday at 1 38 multilingual, Thursday Drupal 7 multilingual 10B and 10C Perfect, yeah, one question One quick question You mentioned about the migrate module being in the Drupal 8 code So it will help We have our content in D6 right now so it will help migrate everything from node level to the P level translation? Yes, yes, so the migrating core will not only have support for D7 to D8 it will have support from D6 to D8 So if you plan to upgrade your D site in the near future, you should maybe skip 7, wait probably a year or one and a half and then building an 8 That's what we are planning to, yeah Yeah, so it will be supported, yes Okay, thanks Yes, yeah, they're working on 6 first Okay, good, thank you very much Enjoy the conference