Loading...
Loading...




access to everything. But we've turned on our new local our language picker. So we've been working hard with the team to translate the site into Brazilian Portuguese and Latin American Spanish. And you can right now see how it works. So in our sandbox, if I choose Portuguese, we see the entirety of the peer review site translated through our usage of crowd in. So, yeah, so what is crowd in? Where does it come from? So crowd in is a platform. There's a commercial platform for translation of things like websites, of apps, all types of pieces of software. It is commercial, but they do support non profit open source projects by providing their services for free, which includes PREreview. So there are lots of public projects available on CrowdIn, where some of the more famous ones, for example, like the game Minecraft or kit lab piece of software. These are kind of quite well known things, and there's lots of private projects as well that we don't have access to. But these are all available publicly. You can choose to join and help out. One of those now is PREreview. So PREreview is available as a public 
project on CrowdIn, which we can go and have a look at. So if I follow this link, this will take me through to the dashboard for the PREreview project on CrowdIn. We can see a bit of information around the project, around the people involved, there's some guy and the languages that we're choosing to translate into now, as Chad mentioned, we're starting with Brazilian Portuguese and Latin American Spanish. So we can see these two projects, and this provides us a place where we can go and have a look at the translations. We can make suggestions. We can put comments, various things. This is available publicly to everyone. You can see the state of our translations. So if I expand this Brazilian Portuguese section, we can see that there's a handful. So there's a lot of words in total that need to be translated, so nearly 9000 we've still got a few left to translate and a few left to approve. So what you saw on our sandbox site was the product of all the translations that have been approved. So we have a two step process where people can suggest translations, and then we choose to 
approve one, and that gets taken forward to appear on the site. We can go into, if I go into the language, we can see here is the language is actually split up over a whole bunch of individual files that represent sections of the website, for example, things like the site header, the about us page, or one that's maybe interesting for us is the home page. So if I go and click on Home page, this will take me through to the place where I can translate it. However, CrowdIn does need you to have an account at this point. So to be able to go in to make any suggestions, they need to know who you are. There's a whole bunch of options for how to create an account with CrowdIn using existing services like Google or Facebook, signing up with a username and password, or even a passwordless option. So I'm going to use this right now just to set up a quick test account for me. So I've never signed into CrowdIn with this email address before. If I do this, it will send me an email with a link that I can open, so there's no need to set up a password if you choose, and in the background, I just have an email where I will grab a link and come back and I'm going to paste what that link was in the email, which will complete the process of signing up for CrowdIn so they know my email address, because I just typed that in. But also I need to set up a username, so I'm just going to make one up. So this is the only account details required by CrowdIn, and I'll say I agree to their terms and conditions 

and things. So I am now in the crowd in editor for the PREreview project in Brazilian Portuguese, as this is the first time this user has joined crowd in it provides a few pieces of health information, help, information that I'm just going to close, but feel free to look at those when you if You decided to try and try the project yourself. So this is as I selected the homepage. So these are the pieces of text that appear on our homepage. The default view here is to have this two column approach. So on the left hand side, what's labeled as source string. So these are the pieces of text, and in our source language, which we are saying, is American, English. So these are the Up till now, the pieces of text that have been visible on the site. On the right hand column is our translation as is. So this might be an approved translation. It might not be or it may not exist at all in some cases, but here you can see, these are approved translations within Brazilian Portuguese. If I zoom out slightly, I was expecting to see another third column, 





one second. Here we go. And behind the scenes, there is also more information about this particular one. So I've selected our slogan that appears on the homepage. So open preprint reviews for all researchers with our fancy underlining of the word all there is this option to show this right panel. If I click on that, it will provide a whole bunch more information around the translation. What I'm going to do is actually collapse the ones we're not too interested in for now. So there's a few different sections here. There are so for a source string. There can be multiple translations available. One of those can be marked as approved. So right here we see there are three potential translations that have been added into CrowdIn. One of those has been marked approved. So that is the one that will appear on the site. You may notice there is a little kind of stars icon around this one. So if I hover over that, it does declare that this translation was made using AI. So it's an automated process. So we are experimenting with CrowdIn integration with OpenAI to try and automatically translate text. This will only
ever create suggested translations. They'll never be approved automatically. We will always require someone to look at them and make sure they're okay or not. In some cases, they don't have enough context or understanding to be able to translate effectively. But we're finding in a lot of cases, this can help speed up the process. This is a experiment, though, that we will definitely be evaluating to see how it's gone. Okay, there are the other kind of sections in this. Sorry, just one second. If I close that, if I did want to change this text, say, for example, I've spotted maybe a typo or something, or I think there's a better phrasing or something. If I were to go and change this say, I'll just add a word to the end of this sentence, if I were to click save, that would create it as a new suggested translation, so that would be one that is then a notification they sent out asking whether this thing should be approved or not. So it's quite straightforward and easy for people to be able to change these but we do require them a manual step of someone approving these translations. I'm not going to do that for real thing, because I'm fortunately not a Portuguese speaker.
so there's a few other sections in here which I did collapse this first one at the top is called context. So sometimes it's not obvious what a particular in what context a particular phrase or sentence or even just a word, potentially it should be taken in. So it's trying to provide context here which will appear here. So there's a few technical details at the top which you can mostly ignore, but we're also trying to provide like, a description of the sentence and guidance for how to translate it. We are trying to add these as we go. We could definitely do a better job. We're trying to get through them. It's there's a lot to add, but we've tried to do it from the more important ones. This is an example of one where it has been added. So there's a description here that says how it's going to be used and kind of what the meaning is, which should give enough context for this person translating. There's also the UI isn't great. I'm crowd in for this. There is a little slightly blurry image here, which is actually a screenshot that's been attached of our 

site where the section is highlighted. So in this red box here, there is the text. You can see where this exactly appears in the page. And there's a Zoom icon at the bottom where it goes to real size, which is quite large. If you want to kind of see where this text is used on this particular page. We only have a handful of these screenshots so far, but they are available for some strings the other sections we have here these other suggestions. So part of CrowdIn, the kind of public projects in CrowdIn, is they can come together and share translations between the different projects. So in some cases, a string we're translating is the same as some other project, and they can kind of share those translations if they're already pre existing. So we have an opportunity to see other suggestions from other CrowdIn users. And occasionally there is sorry, and at the bottom there is the other languages tab, where we can also see how the string has been translated into other languages. So our other language here is Latin American Spanish, where we can also see the current accepted translation for that. So
if we were to, hopefully, in the future, we'll be able to have a list of languages that we translate into. It might be useful to see how they're doing it. If you have a familiarity between the two, there's a few other parts on the right hand side, which will be interesting. So there's a few icons here with a few menu things. I'm just going to have a look at a couple of those. The kind of chat icon, the speech bubble is a comments section. So this is where if there's a bit of something needs a bit more clarity, or someone's got a question about something, you can ask this, and you can flag it for other people to look at, either ourselves or other translators. So this is in kind of normal chat box with a tagging system to contact other users. But also there is a little check box here about issues. So if you click on that, you get the option to categorize what your comment is. Say, if I want to add something new, there's four categories here. So a general question, which, yeah, something that, ideally you'd use one of the more granular groups, but if it doesn't match one of those, then yeah, feel free to leave this general question. But the other ones are more interesting, and that's maybe signifying that there is an accepted translation. But it's not quite right. Maybe someone made a mistake or something a lack of contextual information. So this is does exist in some strings. We're trying to resolve this, but maybe some cases, there's not enough information to be able to translate a string. We need more. And also occasionally a mistake in the source string. Maybe we've made a typo or
something in our English that happens too. So you can use this as a way to communicate with us and flag it on a particular string. Some of the facilities that CrowdIn also provide a glossary. So that allows us to produce a whole bunch of terms that are common across the strings and sometimes give meaning. Maybe the translators, people translating it aren't necessarily familiar with these words, if they don't have a science background or research background, but sometimes we also need to agree on how we're translating particular word. So in this case, because I've selected this string that contains the word preprint, we have preprint in our glossary. It's kind of important to PREreview, and we also have details of how we're choosing to translate it. So we have our source term that is our English US, noun preprint, and how we're choosing to translate it into Brazilian Portuguese, as well as providing a bit more detail around it. This exists for a bunch of things in our list of translations. CrowdIn does highlight these so in our source text, it will do a little dashed underline and allow us to hover over and we can quickly see what that word means. In case it's something you're not too familiar with, an example of those might be the words prereviewer. So this is telling us that this word, prereviewer, gets translated. I'm not going to pronounce it into this word in Portuguese, but also provides the details about it. So we're looking to expand our glossary with more terms, just to make sure we have standardization and providing more clarity to translators. So yeah, okay, there are the CrowdIn editor is fairly complex. There's lots of things you can do. There are various filtering options, where, if you want to see cases that have not been approved, maybe or things have not been translated, things that have quality check issues, ones that have comments. There's all kinds of various filters, but it also has various ways of being able to display the translations which maybe match how you would like to interact with them. So this button here called the editor view, if you click on it, you get a few options. So currently this is called the side by side view, so displaying both the source and the translation next to each other. Another one
you may be interested in will be the comfortable view. So this is, if I click this, get it to reload and look slightly different again. This is the first time this user is doing this. It's providing me with some details. I'm going to skip those over for now. So this looks a little different, but it provides the same functionality, just in a reordered way. So down the left hand side, here are our source strings to translate, and the little preview of the current translation provides the same information so our context possible translations, the other suggestions and the other languages down at the bottom, but it does also provide the text box here for you to be able to edit your translation, so I can choose to suggest anyone if I were to Click Save, which I'm very much not going to do, that would create a new translation suggestion. So it's the same functionality, it's just organized a little bit differently, and depending on how you choose to interact with CrowdIn that might be useful. There are some other options. I won't go through those in these demo just to avoid them overload, because it 
is quite complex, but yeah, there's definitely lots of options for us. So what I'm going to do now is, if I open the menu through this icon here, I can choose to go back to the project dashboard. So this was the page we were on earlier, where we can see so this is the PREreview project on CrowdIn. As I'm logged in, I get some extra options that we didn't have previously. So a menu down the left, they kind of account bar and things, but also is a Join button. So this allows you to officially join prereview.org translation project. Anyone you can choose to participate without joining the project. But what it does allow you to do is to sign up for notifications. So if you'd like to find out when we add a new string or some other change has been made, you can choose to be you can opt in to be notified. So the default notification setting is mentions only. So if someone were to write a comment directed to you, you'd be notified, but you wouldn't find out about other things. So a useful thing to do would be to turn on the global notifications. So this will turn on all notifications for you in the PREreview project, and there are options to limit what that is. But for now, we'll just turn on to global 
if we add a new string, which will happen as we develop new features, or we reword things, you would start to receive an email notification that a new string has been added, that there's something to do. So that would allow you to keep track of the project and help out. As I mentioned, we have a settings menu up here. So inside here, there's a few kind of normal things about appearance and the ability to log out as well when you're done. But there is a settings menu which contains a few tabs I won't go through, apart from two. So the first one that you're sent on to is a profile. You can choose to add, for example, your real name or an avatar, whether it's the real picture of you or something else. You kind of got the normal account options. You might have some information about yourself, what pronouns you use. You can also choose which language you would like to see crowd in in. So crowd in is itself an open source project on CrowdIn, so you can choose to have it translate into any of these languages. You can also declare what
your preferred languages are. So for example, if you are a native Brazil, you might choose to tick like Brazilian Portuguese. I can translate stuff into Brazilian Portuguese, and that helps us know who in the community can speak what languages, in case we ever have questions and things, we can use this as a way to communicate with you. And I mentioned notifications earlier. So there is also a notifications tab where there's a bunch of options around how to receive notifications, but the most interesting thing is this global notification setting. So because we set the preview.org project to be under Global notifications, these will allow you to choose what what messages you receive and how? So by default, things are ticked. So you will receive, for example, new strings have been added. So if we add a new string, if we're adding a new feature or changing a piece of text, you would receive an email about that. If you don't want to, you can untick it. Some of these other ones you won't have access to as translators. They're more of administration things around the project, but they may be useful to look at. Maybe, in 
case you do get notified, something that maybe you're not too interested in, you can always turn things off here. Okay, so that's a bit of a whistle stop tour of CrowdIn. But we also have another piece of work we've been doing, which is another feature CrowdIn provides, which is what they call the in context editor. So we run another copy of our sandbox. That's our sandbox, if I change that to translate.preview.org This is already available to you. This is a special copy of our sandbox that has CrowdIn integration built in. So like with the crowd in editor, you only have to be logged in. I'm already logged in with this account. So it's not prompting me to log in, but he's asking me to choose language. So these are our target translation languages I can choose. Might as well choose Brazilian Portuguese. So click select and just let it load for a second. 

second more. Hey, live demos. Let me refresh that page occasionally. This does seem to happen with it. There we go. So this is a copy of our sandbox using CrowdIn in context editor that allows you to point and click around this site and change things. So I don't know about the video quality, will you, but there are boxes around all the pieces of text. They signify areas that can be translated, and when I hover over them, I get a little icon on the left hand side. If I click on that, it pops up a little thing that looks familiar as CrowdIn that shows this string that needs to be translated provides access to the context that we saw earlier in context in the crowd, in editor, a place to be able to suggest translations. So maybe I want to change the wording, existing translations and the same things as well. And there's also the option to get that right hand menu up so I can interact with comments, and I can make a comment here, so you can access all the things you can do in the regular crowd, in editor, but in place, which 

is quite powerful. The other thing this does is, if I were to make a change, I would see it appear here. So this, the difference between this and choosing Portuguese on our main sandbox site is that I can actually see the changes I'm suggesting reflected here, so I can see how they look in context, which is another way to interact and suggest translations and maybe tweak things. Has a sandbox site this has access to everything. It just doesn't publish prereviews For real, but you can log in with your kid. You can go through the whole process as you would when publishing something for real. There are some strings that you can't access through the site. For example, we have emails that get sent out. There's no user interface in this where we you can access it. So some things will need to be accessed through the CrowdIn editor that said they do provide a few more features. So there is a little menu bar down the bottom here that provide a few options. So starting rest right to left, this right one will allow us to turn off those little boxes of color. This one 

next to it the kind of eye icon that allows you to quickly flip between your translation language and the source language. So if you want to compare it back to English, you can quickly flick between them. I'll put it back to Portuguese, and then there's a menu icon here. So when I mentioned there isn't a user interface for being able to access things like email messages, email strings, it's not entirely true, because this source strings menu actually allows you to access any string in the project. It's not as clear to use as the regular crowd in editor, but it does allow you to find them. You can find through all the pages of all the strings. There is a way of doing it. There is also another menu here, so we're kind of an options menu which has a couple of interesting things. So if you'd like to log out, that's where the Logout link is. If you happen to be multilingual and would like to flick between the languages, easiest, you can do that here. So I can reload this in Spanish. There we go. And so the in context editor has now been reloaded in Spanish. Okay, so that's, yeah, most of the features that of CrowdIn that we're using, we're there's a lot to this. It's internationalization is complex. We're learning a lot as we go through this process, we've already learned a huge amount, and I'm sure we'll learn more as we roll this out to the wider community. But we're really excited to roll this out and to get this appearing as soon as we can. And we're always open to any feedback questions or help. We have a variety of contact methods, which will be in the notes document. But we do have our PREreview Help Slack channel on our community slack instance, as well as the helper preview.org email address. Yeah, we're always available to try and yeah, if you ever run into a problem with CrowdIn or got questions about it, yeah, we're more than happy to get in touch with you. All right. So I think that's the demo. I'm going to stop sharing my screen now so I can get back to the next document, and I believe we have time now for any questions and answers. Chad,