 Sharon having multiple languages on their website for the commission for the conservation of Antarctic marine living resources. Yes. Excellent. All right. Welcome, Dane. Thank you. So I'll just give a quick introduction about myself before I go into it. So I have been a developer in Drupal before. I now am more in the project management side of things. Working at Camelow, which is based just down the road here in Hobart. And so, yeah, we're going through working with a multi-language infrastructure. So about Camelow. Camelow, as you've just heard, is the commission for the conservation of Antarctic marine living resources. It was established in Canberra in 1982 by International Treaty, which is why we are actually based here in Australia. Hobart being the optimal place because it's where Antarctic things happen. The objective for the commission is obviously to protect the Antarctic marine life, but allowing to provide the rational use so that we can still actually fish and use the resources. As of this year, we're actually at 26 members. We've gone up by one. The Netherlands actually joined us this year. They used to be one of the signing countries, so that number has gone down to 10. And the 26 members are the ones who make the decisions at our yearly meetings. As I mentioned, our headquarters is actually located here in Hobart, literally up the road on Macquarie Street, near the Ibis for anyone who's staying in that area. And we operate in four languages. And this comes from the fact that we're part of the Antarctic treaty system. And their languages are English, French, Russian and Spanish. And so therefore, we also have to support English, French, Russian and Spanish. We actually currently have multiple websites in operation. And we're looking in the future of having even more websites in operation. But we'll get to that later. Just a quick information about the actual area that we look after. So here's the map of our convention area. It's roughly 10% of the Earth's oceans that we actually look after. And so therefore, all the information we're presenting is about this ocean area. And as you can see on the map, it's also divided into areas and sub-areas. And we have to provide all the information for those areas. If you'd like to explore more about the areas, we do have a GIS site, which you can actually go to. You can play around with it. You can put different things on the map, like the EZs in the area, and see where the NPAs are located as well. That site isn't in Drupal, I should add. These are the main websites which we have. So the top four are our Drupal sites. We have a couple of other Drupal sites, but they're quite minor. And we have a couple of other websites which are not Drupal. The main sites that I'll be talking about today will be the main website, which is camela.org, and our meeting server, which is meetings.camela.org. Those websites have full multilingual functionality, whereas sites like groups is done in English only because of the quick, the speed that people have to be able to communicate in it. So we support that one in English. And our ECDS, which I'll give a quick information about right now, is our catch documentation scheme. This is a scheme which is for the specifically the species of toothfish. And this actual server has partial translation. But what this server actually does is it allows us to keep track of all toothfish all around the world when they're caught, and also where they're exported to, and the process of actually getting from ocean to the actual table. And so this system actually allows us to know exactly how many toothfish are being caught. I'm not going to go into full depth about the modules, but this is just a brief list of the modules that are used to do translation on the websites. So obviously we have the localization update to improve the localization. We have the multilingual internationalization, multilingual entity translation, and we have numerous other extensions for these, as well as numerous custom built modules. So I'm not going to go into full detail on these, but this is what we use to actually achieve our goals. The key goal for translation for our websites is that we should be able to have everything available in those four official languages. So about our main website, the current design of the main website was built in 2012 by the local development agency here, 80 options. And they're still the organization that we use to develop the website. It was built in Drupal 7. It contains a lot of functionality. I'm not going to go into details of all the functionality, or we'd be here till next week. But we do have currently in it over 40,000 nodes, and that is growing on a daily basis. Most of these nodes also have revisions. And when we're dealing with translation, that means we have to keep translating all of those revisions. Now, Camilla has internally, we have our own translation team. We have two of each of the three languages that are not English. And they do all the translation of all the content that is on the site. And so what we're going to be going into next is how we work through doing that translation. This is an example of a translator page on the website. So I've just done the about Camilla page. As you can see, so top left is English, top right is French, bottom left is Russian, and bottom right is Spanish. And so as you can see, we have a complete translation of all of those. The menus is completely translated. The links, the quick links and related pages are completely translated. And this means that anyone who's on this site can travel around the website in their language and see all the content of the language. We don't just have translations on the content as well. Because one of the key things about this website is being the organization we are with the 26 members. Those 26 members actually all have users who are actually registered on this site. And we'll get into that a little bit more later. But it means that we're not just translating the front end of the page that the public can see, but we're also translating functional back end items as well. To achieve this, we have a translation workflow that we work through to make sure that everything gets translated. It starts obviously when a page is created. This is just a standard page, the page about the convention area. As you can see, we have a standard title, a standard body. This then gets copied into a HTML file and saved into a directory where the translators can actually find the file so they can put it into their translation software, which helps to look for consistent phrases or consistent words to assist with their translating. Lovely tool that they can have. But one of the key things that they do as a translator is that they are actually checking everything to make sure that the English and the language that they translate it to is accurate and has the same meaning. The next step of the translation workflow is we have to actually then set up the content to actually be available for the translation. So for the example here, you can see that currently the information for Northern Warrior page has not been set up to be translated to French, Russian, and Spanish. So what we would do is we would actually then add the translation for that language. And when we add that translation, we set its workflow. So it will have in there a workflow status. We send that to assign to translator. That then allows it so that the translators can actually see that piece of work. So, yeah. And this is then what the translators see. And so I took this image this morning so that we would get a clear picture of what's currently in the translator's backlog for the website. So the translators aren't just translating the website. So that's why we've got two of each. Right now they're actually translating all the report text from the meeting we had. But this view here gives them an idea of all the things that they're translating for the website. And as you can see in this view, what we have is we have, so the Russian and the Spanish. So for example with the conservation measures for 2019-20 season, this is a circular that's going to go out to the members only to tell them the current status of the conservation measures for the next season that's about to happen. If I look at this list right now, I can see because the French isn't on the list, the French has been translated. The English as part of our workflow is put in there so that when we go to this list and all we see is the English one on here, we know that that has been completed with translation. There is an example on here where we don't have the English showing and that's where we've got the schedule of conservation measures in force 2019-20. That's because the English is actually already published. It got published before the other languages and the other languages are being translated. So we have two slightly different approaches that happen for things. Circular says one document has another, but this view allows the translators to see specifically their translations. We also obviously have when you're looking at a specific content type, the status of the specific translation. So looking again at that translate view that we looked at before, this shows that we have the English one published and this is the one I was talking about before that the English wasn't showing in the list. So the English is already published. You can see that the French has been translated but not published. What actually happens when the translators have finished translating it is they actually put it into a pending approval status. So it's still not published at that point and that allows for another check to make sure that the actual translation is correct. So I'm expecting that that French one will probably go live at some stage during today. As I mentioned before, it's not just content that we have translated. I'm not sure how easy this is to see on the screen, but if you look at it, you'll be able to see that on the left we have the English and on the right I have, I think it's the Spanish, might be the French. I can't remember which one I grabbed. So basically what we have is an example where we have a majority of the back-end content translated and this specific form here is actually part of our meeting document request. So for those who are members of the site, they can download the Antarctic Peninsula under a 1.5 degree global warming scenario document automatically, but for anyone who's not a member of the commission, we have attached to the document so you can see the list of documents this form and it's available in the four languages up until a point. So there are a few things which haven't actually been translated on this form and it even passes down to user creation and that comes because of the fact that the members actually create, so each member nation has allocated what we call party administrators and those party administrators, they actually create the accounts for their members that they wish to be able to have access to the site and so this form I have on the left the English and I have on the right the Russian and that means that you can see that what we have is the vast majority of that user creation form is translated into Russian so that the Russian party admins can create a user in their own language. So that was really the main website. Another one of our key servers is our meeting server. Now this server I have been corrected slightly on when it was when it was built. I believe the original meeting server itself meeting functionality was built in 2016. The current design was built in about 2018 for the site. It's also in Drupal 7 at the moment and it's used for multiple different meetings during the year. So in the meetings during the year it's mostly used as an English only server but it does have the translations in there for field names and those sorts of things for non-English speakers to be able to still get some translation but during the two week commission and scientific committee meetings this website has everything translated into four languages within reason obviously because things are changing very quickly we can't always get everything translated because of the small translation team but the key thing about it is all documents will be in all languages all final report texts for adoption will be in all languages and that's done on the fly during the meeting. Now this server I'll go to this page here so this is what the meeting server looks like which is from the pictures which you've seen before is vastly different to the main website at the moment. You can see we have the translations down on the right for people and this is a very simple setup of the meeting server at the moment. This is an example of the kind of translation which is happening on the the meeting server so these are what we call report text. I can't show you more than what's on the screen there because these are actually confidential documents so what I'm showing you here is the absolute maximum that I can show you of how this works but what happens is during the meetings we have what we're called raptors and they draft documents that has all the notes all the minutes of the meeting and that document of the minutes of the meeting during the meeting itself will be uploaded to the meeting server through different versions to actually in English because the raptors will be doing it in English initially and then when that document has been signed off by the chair of the meeting it then goes to our translators who translate it and upload the translated version of that document to the meeting server and this is the final result we get before we go into adopting the meeting. Now I should also point out that this meeting is is so important with language that we actually also have live interpretation at the meeting and that means that when you're listening on everyone listens to with with headphones and or earphones if they want to wear earphones instead they can they will actually hear everything in their language but the people who speak French Spanish and Russian can speak their own language and it will get translated to English or vice versa the English will get translated to them or the Spanish will get translated to English and then to French and Russian and just a large combination of languages happening during these meetings and this server helps to support all that. So this is an example of the report text uploading or uploading of a new version of report text so as you can see this is for agenda item three of the report and what it has as you can see is it actually has four versions in it at this point in time and they're all visible to anyone who has access to the meeting server this as you can see we have translation for the vast majority of the form obviously you can see status the status title name the version number are not but the vast majority of the rest of this form is actually translated and as I said earlier on one of the key goals of of us is to have as much of the sites actually translated to these four languages we possibly can so there's and there's always room for us to do improvement on these these items and I've also attached the so that first page was English and French and this is the Russian and the Spanish versions of the of the same form so you can see the same thing everything for all the languages is translated with the exception of a few of the titles at the moment so what does the future look like for this infrastructure basically we're always looking to constantly improve the translation and and eliminate any oddities that that are happening for examples as we saw on some of those forms some of the things that are not translated we're currently in the very early stages of a two-year project that will upgrade all our sites the Drupal 8 working with 80 options on delivering that as well as separating out the functional parts of the sites into actual separate sites that's mainly for our main website which has a large amount of functionality in it not all of it is actually related to the other parts of the website we're also looking to have a new design for the entire web infrastructure developed by 2021 um and as I mentioned we're in the early stages at the moment and the first phase of this delivery is we're delivering a new purpose built authentication server in Drupal 8 and I know that there'll be people who potentially wonder why are we building an authentication system in Drupal 8 well one of the key things is that the translation there's not a lot of authentication tools out there which can actually operate in the four languages the way we need it to operate and so therefore we're actually got 80 options building us a authentication um in Drupal 8 and I've wrapped up pretty early but does anyone have any questions I'm just wondering how much if any you rely on automatic translation systems that's actually a very good question um we obviously with some of the functionality with some of the titles of the forms and fields and things like that there is some automated translation um the philosophy that I I'm going to go be going forward with most of it is to limit the automated translation in terms of using other people's translations the idea is we will use automated translation in terms of being able to have words and phrases but it needs to be our own dictionary because and this is one of the key things which the translators have actually told me in the last couple of months is they're not happy with some of the the translations that have happened through the localization for example they the problem is is that some of those translations don't have the context of where that item actually is and so therefore the translation is technically correct but it's not right for that context um and so there will be a bit of a balance of automating that stuff so that we don't have to get the translators to translate everything but also allowing the translators to make those calls on what words should actually be used um so does that answer your question you mentioned using various custom built modules this is with the translation um you want to know what kind of um customizations you did there and what why and why you needed it and what purpose um that's that's a harder one for me to answer because obviously I haven't been involved but maybe um Tony from 80 options would be able to help out with that one so from memory because the the site was sort of launched when Drupal 7 was pretty new and at that time the entity translation module didn't exist yet so the very first instance was all node based translations so when you add a translation you're adding an extra node and then Drupal 7 matured the entity translation module came on and then you could have translations within the same the same node um so there's some custom work that had to be done to make sure that the translators had a common workflow um despite there being those two approaches because of how Drupal 7 sort of developed over the the lifecycle of the site yeah so it was mostly around trying to make the process easy for the translators so they would have a sort of an easy to-do list these are the pages that needed translations updated anyone else yes I'd like to hear about the process of migrating to Drupal 8 so are you like updating only the core and that's it or are you migrating all the content in a new newly created site yeah um that's probably a very good question actually so we as um the commission we have to keep everything that we have so for us to go to Drupal 8 all the data which is currently in the websites is going to have to be migrated to the Drupal 8 version and I'm not um I guess I should say what's the right words for it I'm I feel sorry for 80 options because they're going to have to deal with that migration um and um but we're also going to have to deal with making sure that that migration goes and everything is actually over onto the new system um one of the things which we do have as well um which I can possibly show is we because of that requirement we actually do have our previous site still available online um you just have to know where it is to find it um and that means that we have kept all our information from our previous sites as well um which will probably be probably be what happens with this site as well it'll probably still exist in some form um it'll just be shuffled off to the side somewhere so that if if we ever find that something's missing we can go back to it and get it into the into the new site but yeah the main aim would be to get a hundred percent over if we can the the process of migrating the translation of translated content um isn't that um problematic I don't think in most cases except that the the early iteration of the site was using that node based translation um and because it's developed so that we still have some translations that are in different nodes and the rest are in entities that that'll be one complication with the migration process that will have to overcome but um but for any other site that that you might have that you're going through the same process if you were lucky enough to jump on Drupal 7 when entity translation was the norm um then I don't think the migration to Drupal dates translation method would be um too problematic last chance no all right well let's thank Dain