Loading...
PREreview & CrowdIn: A demo (call held in English and Brazilian Portuguese)
Unknown Speaker
00:15Hello, account, hello.
Unknown Speaker
00:22All right, let me rearrange my windows as well. Yeah, I've
Unknown Speaker
00:27just been sorting out my tabs. Ready.
Speaker 1
00:29There you go. There you go. All right,
Speaker 1
00:58hey, all right, it's working now. Welcome back. Thank you for your patience. Mario, if you want to rename I'll then pick the right the right device to add as interpreter. You
Speaker 2
01:25Hey, welcome Rafael. All right, thank you. Good morning.
Unknown Speaker
01:30All Hello,
Speaker 3
01:37hello, hello. All right, interpreter, let
Speaker 2
01:42me just change my name. Let me just change my name here. Just give me a second. Should I just put Portuguese? Interpreter?
Unknown Speaker
01:54Yes, that's fine. I
Speaker 2
02:16I'm going to join with a second device. Now, just give me a second. Okay, I'm
Speaker 3
02:24sorry, my mic was open. I was talking to Rafa, and I will close. Okay, I guess I'm in both devices, and here we are.
Speaker 1
02:37Awesome. Should I I'll also add Mark.
Speaker 4
02:41I'm sorry, Mario, the second device. Can you name it something else, other than Portuguese interpreter, so that you're not enabled accidentally on that one?
Speaker 3
02:52Well, that's the my first device, the Portuguese interpreter. The second device is named as monitor. Mario, Costa,
Speaker 4
02:58I'm sorry. I meant to say, all right, got it, got it. Okay.
Speaker 3
03:02And there's also Raphael with Portuguese instruments. So that might be a little confusing, because this mine is the one with its own Rafael is in low case, minus the one port in. That's the device who won't be speaking. That's the device I'm speaking right now, and the other one, mon Mario is just a listening device. Thank you. Got it, no problems.
Speaker 1
03:25And then I'll add Portuguese underscore interpreter Rafael as well. Okay, that should do it.
Speaker 4
03:38Yay. And we see interpretation. And if we can test the channels, maybe starting with English in an alphabetical order, can we go with you first Mario in the English Channel?
Speaker 4
03:59Oh, oh, yes,
Speaker 4
04:09no, not really. And you sound really good. Do you want to test your monitor? Mario, that will be the one from where you would make the announcement. You
Speaker 4
04:40you? Well, I can make the announcement in English. Rafael, do you have a microphone on your second device?
Unknown Speaker
05:11And oh,
Unknown Speaker
05:17see if you can hear me on the second device.
Speaker 4
05:19Can you hear me? Yes, but there's an echo, sure, yes, let me turn it off.
Speaker 2
05:27What about now? Yes, perfect. Okay,
Speaker 4
05:33alrighty and okay and Rafael, can we test your two channels now? Starting with English, all right, uh huh,
Unknown Speaker
05:52awesome.
Unknown Speaker
05:58All righty, so that's tested,
Speaker 1
06:20all right. Thank you all so much for joining and supporting the call today. For folks I haven't met yet, I'm Chad. I'm the head of product at PREreview in Virginia in the States. So East Coast say, hey Chris.
Speaker 5
06:35Yeah, hi everyone. My name is Chris. I'm Head of Technology at PREreview, so I'm based just outside Cambridge in the UK. I think
Speaker 5
06:47we might have some other previews joining potentially. Was Danny planning on joining? Yeah,
Speaker 1
06:51I think so we I gotta rename myself. We had that champions program call earlier today, so Daniela and or Vanessa might show up,
Speaker 4
07:11and you've met me all. It's a pleasure to be here this morning, supporting elusiana. Would you like to introduce yourself too?
Speaker 6
07:23Yes, hi. I'm Luciana, and I've been working helping with the translation of the website. It's a pleasure to be here and learn from all The insights we'll get here. You
Speaker 1
07:58I forgot about five or so folks registered who are not interpreting and not staff, so hopefully, at the top of the hour, they will show up and we'll get started, and I'll share the notes and say one or two words before we get started, just to remind folks that we're going to record and we have our transcription tool on so we can share those records of this call later on. Since it is a demo call for anyone else who might be interested in joining the project on CrowdIn and then, you know, three minutes past, four minutes past, we'll go ahead and kick off the call for anyone who needs it. I'll be repeating this message in the chat frequently, but there are our notes today. Should be just about everything we need.
Speaker 1
08:55Hey, welcome, let's see, and we'll go through. I'll just do a quick hello and welcome, and then the language inclusion invitation. I'll share our code of conduct, notes, goals of the call, and invite folks to add to the document hopes, hopes and aspirations, what they would like to get out of this call. Chris will then do the demo. We'll have time to do some Q and A, we'll get close to wrapping up by just giving folks some time to go into CrowdIn to try it out and ask any other questions that come up. And then we'll close and ask for feedback that'll be that you
Speaker 1
09:45can you hear my dog or no? Yeah, great. Well, hopefully the delivery person will be finished in the next moment or two. Here,
Unknown Speaker
09:55maybe we get to see your dog too.
Speaker 1
10:00If you see like motion over there, that's blurry, that's that's her usual spot.
Speaker 4
10:05I love seeing pet cameos in zoom meetings. Oh, she, she likes
Unknown Speaker
10:11to let me know whenever anything's happening.
Speaker 2
10:13No, Amy, just have a question. Marie and I were talking about the introduction. Can you brief us again. How do you want to go about the introduction? And we have to go from the second device, right?
Speaker 4
10:27Yes, thank you for asking so where it says consecutive, which is through the instructions, and where it says pause briefly to see if anyone is having issues. Until then, it's consecutive. And the second device,
Speaker 2
10:48that's my question. So somebody will introduce in English. Yes, I'll
Speaker 4
10:55do the English part. And then where, there's where the yellow highlight is to begin simultaneous. Whichever one of you is going to start the first shift in simultaneous can start doing simultaneous then, okay, got it. Thank you. Thank you for asking. But
Speaker 2
11:14then the other person, as soon as you finish the introduction in English, we do consecutive into Portuguese so everyone can hear is that right or no? Yes, just on the Portuguese channel. Yes.
Speaker 4
11:25Um, no. The The first part is not from the channel. It's on them, on the manager, on the main channel. And then that is to get everyone who's not on a channel and doesn't know how to get on a channel, to get them on a channel, and from that point forward, I continue in English alone while one of you does the interpretation simultaneously into Portuguese. Got it Okay? Thank you. Awesome. Thank you.
Speaker 1
11:58And as we're two past the hour, it doesn't seem like any of our other registrants are yet. Here, we'll give it till five past the hour, and then, you know, probably an important output from today is this, this record or this demo that we can share in both languages. So if none of our registrants have showed up, we'll start at five past and we'll kind of just move through the call at a nice leisurely rate to make sure everything can be interpreted clearly. But we'll probably skip the activities for the participants and go from or maybe I'll do just like a little placeholder, like, you know, here's a great time to think about, you know, your own aspirations, your own goals. What would you like to get from the localization and translation of prereview.org into Brazilian Portuguese, and then we'll go to the demo, and then, rather than have time to practice or Q and A, I'll fold those things into the closing and invite people to visit the different places and to try out the work there. So we'll give it about two more minutes, but then we'll proceed as best we can, so that we produce an artifact from the call we can share for folks who might be curious in coming to this from from Portuguese, rather than English. Is that? All
Speaker 4
13:12right? That sounds like a plan. And would you like us to skip the intro then, since there are no folks to connect
Unknown Speaker
13:18to, someone just joined. So there we go.
Speaker 1
13:29All right, here we are. Hello and welcome, Bruno. We're gonna get started in a moment. I'm gonna put into the chat the notes for today, which you are welcome to add to beginning with the roll call at the top, this will be a highly customized call for you as our participant, our registrant. Right now, others may join. Shortly. We're going to give it another moment, and then we'll start. So quick reminder, we're going to record the call today and use the AI tool to produce a transcript so we can share those things afterwards with folks who might want to review the call and who couldn't make it today, but want to get started with helping us to localize and translate prereview.org on their own time. If you have any questions, let us know in the chat, or feel welcome to come off of mute and ask them aloud, and we'll get started in just a minute.
Speaker 1
14:32If I can find my monitor here amongst the two two screens. I did it. Yay. Hello and welcome. First prereviewer, I imagine that's Daniela, welcome.
Speaker 1
14:53All right, we are here at five past we'll go ahead and get started. I'm going to start up the recording, and then we'll move through the agenda the first way we talked about it, and to make sure to capture any feedback from Bruna as we go, here we go. Hey, hello, and welcome everyone to this demo call meant to help the PREreview community help us localize our website into Brazilian Portuguese, and we'll have another call tomorrow focused on Latin American, Spanish, all its varieties. Really appreciate you spending this time with us, helping us out, you know, and holding in mind and working towards that better vision of PREreview, scholarly communication, the world that we share in the chat I am going to put our notes for today. If you'd like to add yourself to the Roll call, please feel welcome to though it is optional. And with that, I want to pass things over to our interpretation team for a welcome and some reminders and help with our language inclusion piece in translation today, Noemi,
Speaker 4
16:06thank you so much. Chad, hi. I'm Noemi, and I'm here with Mario and Rafael, who will be our Portuguese interpreters today.
Speaker 2
16:21Hola, Bucha, no me happy. Communication, and
Speaker 4
16:31today we will communicate in Portuguese and English using Zoom's interpretation feature was it
Speaker 2
16:38not communicate? Was in Portuguese inspiring glass was in a question. Interpreter, song to zoom.
Speaker 4
16:45And we ask everyone to please choose a language channel, even if you're bilingual, and if you'd like to share in both languages, please just remember to change channels when you change languages.
Speaker 2
16:58Epgm, school, sales. Interpreter, some do zoom. German
Speaker 4
17:11now to connect to a language channel, if you connect it on a computer, you will see a globe icon that says interpretation, and it's located at the bottom of your screen. And if it's not at the bottom of your screen, it may have moved to the More menu.
Speaker 2
17:30Don't put a civil says, connect it down canal. Do German necessary civilization figure that tail is traditional. Oh, see, no. It's not a passion video. You So,
Speaker 4
17:49once you find it, please select the language that you prefer my
Speaker 2
17:53best says In contrary Association our geometry versus prefilled.
Speaker 4
17:58And if you connected on a mobile device, a tablet, an iPad or a smartphone, click on More or the ellipsis, then language interpretation, select English or Portuguese, and then press the blue button labeled done to enable interpretation. It
Speaker 2
18:21was assessing tablet on my page was much funny, a soccer in mice on duty as it senses in Segi, the interpretation. Drama. I was a solution. Who Portuguese, always by audio Codex. Drama, equally kind of bottom azuki just conclude.
Speaker 4
18:38Is there anyone who didn't find a language channel and their device, please let us know
Speaker 2
18:45they are going to know in control esta from somebody German.
Speaker 4
18:53All right, we are now going to test the simultaneous channels and let me know when you're ready Rafael or Mario to move on to inter simultaneous interpretation in
Speaker 2
19:09terms of star agora. Who can out, interpret us on in Don you have i Omar kind of pursue very thick sister function and Portuguese. I
Speaker 4
19:22please. All right, so simultaneous interpretation now, and let's make sure that you can hear on your preferred channel. If you can hear me directly, I'm speaking English right now. And if you can hear Rafael or Mario, very good. And Rafael or Mario, whoever is interpreting right now, do you want to come into the English language and say
Speaker 4
19:56hi? All right, so now we have a few reminders that support language justice in bilingual or multilingual settings. Some languages use more words than English. Portuguese uses in Spanish too, by the way, use more than 30% words than English. Because of this, if someone speaks too fast in English, the interpretation will go very fast or be incomplete, and that leads to inequity in the message. We encourage everyone to speak slowly, particularly if we're speaking English and a good way to slow down naturally is simply breathing regularly, which is also good for our health. If anyone forgets, we will do this to remind you. We invite everyone who's present here to also do it if they feel the speaker and or the interpreter are going very fast, why does this matter? Because language justice is a collective effort. If you have them handy, we invite you to please put on Wired headsets, earphones or headphones, and if you don't have that, perhaps an external mic, so that we can hear you clearly, and that matters, so that we can capture the message fully and interpret accurately into the other channel. But also for interpreters mental health, it's very exhausting when the audio is not clearly and interpreters try to make out what is being said throughout the day. We also invite you to take process and wait a few seconds between speakers to allow for interpretation, and please announce your name and the language in which you will be sharing, so that folks listening to interpretation know when someone else is speaking. Thank you so much. And enjoy today's session. Back to you, Chad,
Speaker 1
22:16thank you, Noemi. We're now towards the bottom of page two of our notes, and I'd like to share a quick reminder of our code of conduct by participating on this call together today, we agree to create a harassment free experience for all, and specifically, we're here to welcome one another And our diverse viewpoints to offer and receive constructive feedback respectfully and graciously, to demonstrate empathy and support of one another and for the good of our community and to act professionally throughout we will not dismiss disrupt harm harass or troll anybody. We won't pay anyone any unwanted attention, sexual or otherwise. We won't share anyone's personal information or contributions without consent, and we won't act unprofessionally or insist on providing destructive or harmful feedback. If you'd like to learn more about our code of conduct, you can through the link at the top of page three, if there are any incidents you need to report, you can reach us at report@prereview.org, or through the anonymous form also linked near the top of page three, with that reminder done, we'll share the goals of today's call and gather a little bit of feedback from our participants before the demo itself. So today, primarily, we want to learn how to get involved with prereviews, localization and translation campaign, beginning with Brazilian, Portuguese, Latin American, Spanish. To do that, we want to learn how to use the crowd in platform to suggest localizations and translations of text on prereview.org and we want to understand the timeline for this work in Brazilian, Portuguese and Latin American Spanish, as well as to get an idea of when we at PREreview might begin the discovery process To start working on localization and translation for other languages in the near future. That's, that's, that's the big idea for today's call. And one of the first things we'd like to do is invite our participants to say hello, if you would like a listen and Bruna, but we're at the bottom of page three, top of page four. And we would love to know from you a little bit about maybe what brought you to the call today. What do you hope to learn today, or what do you hope to contribute to or get from this localization and translation project? What are your hopes for this work? We'd love to know. If anyone adds anything you want to affirm you can add a plus one. If you have a kind and clarifying question, you can, of course, ask it. And if you ever have resources to suggest or share with people, you can do that as well. And there's space for you in the document at the top of page four, to share your hopes for today's call and for this work with us. You could also come off of mute on the call itself and share aloud if you would prefer, or you can type into the chat on the call, and we'll move those notes over to the document. But Adelson Bruno, if you would like to say hello and share, you know a hope, or you know a goal you have for your time with us here today, we would love to know it. Please go ahead and respond now. If
Speaker 7
26:11you'd like, Yeah, hello, can you send me? Yes, yeah, I'm thriving now, so I hope that everybody will be able to listen to me properly. Yes, so my name is Bruna. I am apostle, Brazilian, and I lived for for 25 years. It's my native language, and I heard about this action in another meeting, and I just wanted to know more about it and see if I can help with my expertise in my own language, but also translate translated to English. That is another language that I needed to learn as a scientist,
Unknown Speaker
26:58understood. Thank you very much for that. Adelson, would you like to share anything?
Speaker 1
27:14You're on mute in case you're sharing, but you can certainly share later or interrupt us at any time. If you'd like to come off mute and and to share anything now, though.
Speaker 1
27:31All right, please do come back and let us know if you'd like to share anything in either language allowed on the call, in the chat around the document. But that was fantastic to know, and we are indeed here to make sure everyone understands how they can get involved if they would like to, and how to help with this phase of our localization and translation work. And to get into some of the specifics of that, how to help, where to go, to help, how to begin. I'll turn things over to my colleague, Chris.
Speaker 5
28:04Thanks, Chad. Hi everyone. My name is Chris Wilkinson. I'm head of technology for PREreview. I'm based just outside Cambridge in the UK, and I'm going to be giving a demo today around the translation work we've been doing at PREreview. And as Chad mentioned, our usage of CrowdIn as a place where you can help. So I'm just going to start by sharing my screen. Just bear with me one moment while I pick the right one. Okay, so hopefully you can see a browser window now, if Chad just give me a thumbs up, there we go. Great. So we run as well as the main PREreview site, we run what we call a sandbox, which is a place where we can experiment with new features. We can try things out with the community. So this is visible to everyone. One of the things we've done recently is to add translations to the site which are enabled on our sandbox. So this is you can go to this right now and see yourselves, but I'm going to quickly show you it here. It's exactly like the normal site, except you can't publish things for real. So it gives you 
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.
+5
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 
+2
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 +2
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 +3
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, 
+7
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 
+1
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. Speaker 5
38:08Okay, 
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
+1
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 +3
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 
+1
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 +1
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 +1
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 +2
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 Speaker 5
48:00so 
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.
+2
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 +1
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 +2
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. Speaker 5
51:46A 
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,
+3
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 
+3
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 
+3
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, 
Speaker 1
56:55absolutely. Thank you, Chris, that was a lot of fun to see kind of come to life there before our monitors, we've got probably about, I don't know, 10 minutes or so before we should start closing the call. So I'd like to invite all of our participants, Adelson and Bruna Saeed, to and anybody else on the call from staff, any of the interpretation, even if you have questions that we can answer for you. Now, you could come off mute and ask them aloud. You could add them to the chat and we'll put them in our document. Oh, it looks like where are we in our docket looks like we're on page five for Q and A. Or you can just type right into the document yourself. I would also encourage you, I think we'll combine the next sections, which are Q and A and some practice time. So if you'd like to log into CrowdIn, if you'd like to find the preview, PREreview project and click around a bit, explore a bit of what Chris just showed you, in case that prompts a question. Right now, we're all here together. It's a great time to do that. So please in the chat or document, or if you want to come off mute with a question, please ask questions you have now. And if you'd like to go to the site to CrowdIn or to translate.prereview.org and begin playing around and seeing if that gives you some questions. You could do that now too. We'll take the next seven, eight minutes for Q and A here. So please let us know what questions you have. And Chris, there are a few here to start with, if you want to go over them in the doc. Well, other folks are formulating their
Speaker 5
58:41questions. All right, so yeah, I see there are a few in the chat. First one being, if multiple people are suggesting edits at the same time, does anything bad happen? I imagine no, because all the suggestions, all the suggestions that need approval, that's correct. So it's perfectly fine for there to be multiple suggestions for the same string, but only one can be approved, and the approval can be changed. For example, if things are not put into stone, they can be changed. Sometimes Mistakes happen, they can always be changed further down the line. But yeah, there's no reason not to have multiple suggestions, and as we kind of discover what the most appropriate wording is for a particular translation. And there's another question about mentioning connecting with Slack. So this was, I believe, on the crowd in Account menu, on the Notifications tab, there is something about slack at the top of that. This is separate. This is you are able to connect your own slack account to crowd in so you can be notified through slack. If you don't maybe want to be notified through email or something. One area we haven't explored yet is connecting our community, Slack, instance, to CrowdIn, so it might prove useful for us to announce when there's a new string being added on Slack. If our translators are keeping an eye on that channel, maybe we can do that as well, but that's not something we've tested out yet.
Speaker 1
01:00:27Okay, super helpful. I have a question. Yes, thank you.
Speaker 8
01:00:34I choose from Brazil. I am speaking in or to give okay thing as a premier, very so doctor to sell a story. No crowding. Ella as a premier person to give a Fauci 40, yeah. Okay, consistency.
Speaker 5
01:01:10So the ones that are done by AI will have the PREreview User Account next to it, and this little icon with stars in if you hover over that little, little icon with stars in it, will give you context to say this was using AI to generate it. It's up to a human whether to approve that directly or to change it or to reject it entirely. That can happen. Sometimes some of these AI translations were done while we were beginning the project, and we didn't necessarily provide it to the right context. So there are some quite wild mistakes in what it was able to produce. It's getting better as we go along, but we always require someone real to look at it to make sure it's a real Yeah, it makes sense and also adheres to our policies such as language inclusion and things. Yeah, you should always look for the little star icon against the username to see it will signify when one came through, AI, Great. Glad to hear
Speaker 1
01:02:29Thank you. Very glad to hear that you are in crowd and already checking that out. Yeah, other questions from anyone else on the call? Yeah,
Speaker 1
01:02:54Chris Well, as Chris mentioned, there are many ways to get in contact with us as questions come up, and anytime you have a question related to this work or other parts of prereview.org Please do just let us know. I think we'll go on now towards the closing of the call and an opportunity for you to share some feedback with us at the bottom of Page Six, the top of page seven. Bucha, again. Thank you so much for joining today, for the great questions, for sharing your hopes for this work. It's really it's really exciting to be collaborating with all of you on this as it's shared at the bottom of page six. You can find us online, on blue sky Mastodon and LinkedIn as well as you know, at help@prereview.org, lots of ways to continue staying engaged with us and this project, we have a newsletter you can subscribe to as well that is linked near the top of page six to get news about new projects like this and ongoing work, and we mentioned slack a few times. We do have our own community, Slack. If you're not on there yet, you can find a link to that at the top of page six. If you fill out that form, you will then get an email invitation from us, leading to slack. And with that, I think we'll probably come to a close. We've got about six minutes left here in the hour. Thank you. Vanessa, our head of community, shared that slack link in the chat. And going from the middle of page seven on to page eight, there is a space for you to offer feedback in English or Portuguese, either is fantastic. Would love to know a couple of things. First, if you wanted to leave your name and perhaps let me edit this. Though this was incorrect. I had a typo here. Sorry. We'll say if you would like to help us with future translation work, there we go. You can add your name here and a preferred email address, and we will get back to you. You can also let us know what worked well for you on this call, you can let us know what didn't work well for you on this call. You can let us know if anything surprised you, and you can let us know if there's anything you would change, and if you would take the next few minutes to provide feedback for those questions, that would be fantastic. We have our call in English and Spanish tomorrow, and what we love to do is take feedback right when we get it, and to try to use it as quickly as possible to make the next thing better. So anything you can share with us today will help out our potential friends tomorrow on that call and all of us moving ahead in this localization and translation project. So big. Final. Thank you. This has been super exciting. Keep bringing those questions, keep bringing those suggestions to CrowdIn and we're just very happy to be here, engaged in this work with you, and you know, future efforts to continue improving prereview.org and Chris or anyone else on staff for translation team, any final thoughts to share or participants, anything you'd like to share before we say goodbye.
Speaker 5
01:06:30No, just reiterate what you said. We Yeah. If you've joined any of our calls previously similar calls, we always take this feedback really, yeah. It really to heart, and it definitely helps us direct us and how we should be changing things and making things better. So yeah, and if things come to mind afterwards, please feel free, just to let us know they don't necessarily have to go in these notes, but we do always, yeah, try and do the best thing we can based on what people in suggesting to us. So thanks, everyone.
Speaker 1
01:07:11Awesome. Would anyone else like to share anything before we go?
Speaker 1
01:07:21All right. Well, we will find each other soon, on on all the channels and in crowded Thank you, everyone. Be well.
Unknown Speaker
01:07:30Thanks everyone.
Unknown Speaker
01:07:38We'll hang out for a moment and stop the recording. Thank you Adelson,
Speaker 1
01:07:51thank you Bruna, thank you Saeed, thank you wonderful language team. You
Unknown Speaker
01:08:04all right.
Speaker 1
01:08:06Well, thanks for being here. Say, all right. Well, team, if, unless there's anything pressing, we'll go ahead maybe and jump off. Folks from PREreview, we'd mentioned this on our earlier call today. Would we like to start the next the next meeting, five minutes past the hour, 15 minutes past the hour? What do you think? Yeah, that sounded like a 15 minute. Yeah, yeah. All right, I've got a hard stop at the top of the next hour. But Shall we start at 15 past is that right? Daniela, they're not here, so we'll get some looks like. All right.
Unknown Speaker
01:08:45Thank you all.
Unknown Speaker
01:08:46Thank you. Thank you.