Subscribe
Share
Share
Embed
A podcast from the ETEN Innovation Lab exploring acceleration in Bible translation. Tune in for experimentation, updates, and conversations about new methods and technologies advancing Scripture accessibility.
Isabella Scarinzi 0:06
welcome back to the Bible translation innovation podcast, a show brought to you by the E 10 innovation lab. So before I begin today, I want to make a quick shout out to the open Bible technology community hackathon, which is happening this spring, from April 27 through May 1. So the hackathon is a five day, global and hybrid event that's going to bring together developers and translation teams. The goal is to collaborate on new ideas and open Bible technology that can work across platforms instead of in isolation. There are confirmed in person sites in Florida, in Bogota, in France and in India, and there are also options for full online participation if you want to work with teams across different time zones on real solutions that can serve our movement. So if you want to join a team, if you want to host a site or contribute, you can register at the link below that we're going to leave in the show notes with that. Today, we are joined by clappy and Joel. As usual, clappy is transitioning to an innovation advisor role that he will be serving teams beyond just the E 10 Innovation Lab. We are happy and excited that he's going to continue recording these podcast episodes with us. So we're looking forward to recording today and in the future as well. But today, our topic of discussion is going to be iterative publishing in Bible translation and why it's sometimes misunderstood. Iterative publishing is the process of releasing completed portions of Scripture as they are ready, which we will talk about the concept of ready as well. But publishing what is ready instead of waiting for an entire New Testament or full Bible to be finished before publication. So because scripture is extensive, and as we all know, translation projects can spend many, many years. This approach recognizes a practical reality. It's all about communities benefiting from access to God's word sooner rather than later, without compromising quality. My first question of the day is, what does iterative publishing mean to you, and why do we want it? So I'll hand it over to Joel and claffey.
Klappy 2:27
Thanks, Isabella, you gave a great definition for iterative publishing as we look at it. You know, there's sometimes this false dichotomy of, you know, it's one thing versus another in we're talking about the trade offs later, but with Iterative publishing, we have to look at the fundamental pieces involved in Bible translation. And it's such a complex topic with you know, if you really map out all the different things that happen in Bible translation at one tech conference, it there was over like 100 different steps to Bible translation. It was just overly complicated. So a part of simplifying the understanding of Bible translation, you know, if you look at everything coming down to drafting, checking and publishing, it's way over simplified. But at the same time, I think those foundational things are still present in iterative publishing. So with Iterative publishing, we're not doing away with the checking before we publish, and I think we'll get into some of the misconceptions later, but
we can still whether we're publishing a full Bible waiting till everything is drafted, all at, you know, in one long process, and then coming back and then checking behind and checking the entire Bible from beginning to end before we publish.
Iterative publishing does the same thing, but in smaller chunks, right? And we can talk about how that changes and later in the episode, but that's my oversimplification. Sometimes we have to break things down into simple things, and then just kind of restate things from first principles thinking to help understand the tensions and the constraints that we have. So we're not doing away with anything that was good from the previous process, as we introduce new methods, new processes to help us in
your original question, what is it and why would we want it? Okay, so that's more about what it is. Why do we want it? You know, a part of it is just, how do we get God's Word into people's hands
sooner, right? Like, if it's a 1020, 30 year process, like it has been traditionally, part of iterative publishing was also helping to pave a way for, well, if it is such a long process, in some of the older or established methods.
Theology for Bible translation, it takes a lifetime to create Scripture how? How can we get scripture portions to save this generation right into people's hands and make a difference in the impact of their cultures now? And
as we've done that, it's actually helped unlock more and more, I think, innovations overall in the Bible translation processes and accelerations that have compounded over time. So now we're no longer looking at this 2030, 4050, year Bible translation process, but I think it's helped bring innovation along so that we can get a much shorter timeframe for the entire process. However, during that we're still able to get God's Word in people's hands as each book is done. Yeah, accelerating pace really is the baseline commissioning that the lab has been given by e 10, and we think about that at every stage of the translation process, including publishing, which is why we're talking about this topic today. So Kapi, you kind of touched on that a little bit, but
Isabella Scarinzi 6:09
what are some of the pushbacks or concerns that we typically hear with Iterative publishing?
Joel Matthews 6:16
Yeah, this is
something that I feel we should not not speak lightly of because it is important to understand what the risks are here and and to make reasonable choices understand the trade offs. One thing I'll preface what I'm about to say is that I think the reality is all scripture is iteratively published, including the very highly resourced Bible translations in English, the ESV and the NIV also have have created revisions and publish them. Now, the extent of their revisions may be small or different, but even still, they they have been going back to the text and found areas to improve or clarify and change, and we're talking about highly resourced you know extremely well curated resources that have taken many years to complete. So when we come to the minority language Bible translation context, we're talking about a local church which has been given enough resources, tools and technology training to be able to do Bible translation within their context, at least that's the working assumption I'm going to keep for now, though, that that is not the only model that Bible translation happens. That is the C C B T, or the cbbtt church based Bible translation model. However, a lot of the emerging ways of doing Bible translation include this model. And for a local church, this is, you know, they, they are not. They don't have all the luxuries of access to Scripture and and resources, even in languages of their wider communication as say, English as so for a team like theirs, the we have to be realistic about what available resources they have and outputs that they can produce in reasonable amount of time. Now, one thing to also say is, nobody wants poor quality scripture, especially the local church. You can ask anybody on the field, and they will always say they want high quality scripture. There's not a thought that we can compromise on quality to move forward. And I think that's a fear that maybe a more Western minded philosophy can feel that when we are going to a smaller community from the west to help a community, local community, somewhere remote. It might seem like we are giving them permission to be compromising on quality, but that is actually a false assumption, if you understand if, especially if the local church there is taking ownership of this process, and they feel the need to have a high quality even more than their facilitators. So the danger there is, of course, when you think about Iterative publishing, if you do this recklessly, you might end up with some content in people's hands. Who are you? Not prepared to receive that which has errors in it. And I think the worst of it, I mean, if you project that out, it could end up saying that you'll teach heresy or propagate non theological teachings in the community, and especially when you think about a nascent community that is still understanding or new to the faith that can be pretty dangerous. I don't think anybody wants that. Anybody is trying to push that. What we want to be careful is that we are taking enough steps to make sure that does not happen at the same time, we can push, push the ball too far and say, No, this is this need to have. You can only publish the text after it's spent years and years of checking, and some consultant has looked at it. I think you know, even from the lab, we believe that's not necessarily true that even if you did that, you will not have any errors either. So there is some better medium we can find. And that's kind of the struggle that we all are, in some sense, talking about this today.
Klappy 11:18
Yeah, we have, we have personal experience, you know, engaging with these communities that are doing the translation work with the churches. Really, no, like you said, nobody wants poor quality scripture, right? Like, if anybody is invested in having high quality scripture, it's the churches themselves. And I'll never forget when I first moved from the business world into the Bible translation, space full time, my second international trip was actually to a safe house. And with that visit in safe house, you have people in the Muslim background context, in their culture, their holy book that they're aware of never changed, right? It was written in Arabic, and it's still in Arabic, so there weren't iterative iterations, right? There's no translation of it in Arabic that needs to be improved over time. So they have this static text. So in their mind, the bar is, we need a perfect translation, and it can't change. And so when we were working with them and explaining about Iterative publishing, you know, and ideas of iterative checking and iterative releases like it, they had a hard time wrapping their their mind around it. So when we talk about some of these pushbacks, you know, some of it actually comes from the field in there they're grappling with, and I'll just summarize it in what they said has never left me like verbatim they said, Tell Tell me, brother. How do we know when our Scripture is good enough to give to the Lord? And so that's always stuck with me, that in their heart it's not about is this good enough quality for people to use it for them? When is this good enough to present to the Lord like tell us, guide us, show us when this is good enough to give to God. And so that's their heart and it's, it's something that we have to trust the churches that are, that are doing the work and engaging with them as we explore the bright processes for for them and over time, you know, they, they've, they're still working through that issue. You know, it's it's not a one and done, and it's not a one size fits all, and it's not all cultures will see this issue the same, or all regions will, or all churches will, right? This is something that we work together with, with the region, with the churches and in those regions, on on how to navigate this issue.
Joel Matthews 14:21
Agreed, that's really cool story. Thank you for sharing that.
Isabella Scarinzi 14:24
Chapi, so we talked a little bit about quality. I'm wondering, how do we practically determine when it's ready to be published? What does ready mean?
Joel Matthews 14:39
Yeah, that's a hard one. So I think there are in the Bible translation community some best practices that have been agreed upon, and they have to do with the process, and they have to do with doing certain types of checking. And. And how you would do it, and they've been largely accepted and practiced successfully on the field. But I don't think we have any automated, fully automated techniques to measure a quality of output. We have automation for parts of it, and we continue to improve on that. There are tools even that the lab is working with that we are looking at measuring and improving quality estimation in different modalities, text and audio. But at the end of the day, it's a human, it's, it's a human. It's a community that needs to put a stamp on it and say, Okay, this is, this is good. We have done these sort of steps, and looks good to us, sounds good to us. We have checked all of these things and spend the time. Now there is an aspect where a consultant can also do that, and they can put a stamp on it and say it's good enough. And that's commonly practiced too. I think we, I believe the local church can be equipped to do that also, given even just what clappy shared their investment and their heart to see a high quality scripture available for their own community and their church. So it's a very fuzzy concept, I think, in intrigue as it relates to intritive Publishing, it's a matter of knowing when is it ready enough to put out to the community. And in my mind, I think those the idea of quality and community checking. Community checking is an extremely important part of quality improvement for the translation and iterative publishing is a means to do that. It's you know, you can do quality community checking in a much more controlled environment where you have very select group of folks who get, receive the text or the audio, listen, read or listen to it and give feedback, but I believe the best way to actually get real feedback would be to put it into use on a Sunday morning and have people listen to it, interact with it. Now, the danger there again, is okay, would they learn something that is not biblical? Is this theologically true? Because the text is not accurate? I think I want to camp on that for a minute here, because I think it's important. In when I think about the cbbt way of doing things, the church itself is part of the translation. They are not outsiders to the system that that is just on the receiving end. They are invested in it. They want to support, and they want to help. And So involving them in this process is they're not unwittingly accepting the Scripture as the final because they know what the process is. They know that this is in progress. They know where what the work has been done so far, and what's next. And along with having the guardrails of the more biblically trained pastor or elder and other believers, I think it's much more of a safe setting to actually put out scripture like this to the community and get feedback. So I feel you can go through a few stages of checking, not all the way through, while keeping the community completely aware of the process of where you are at and what's ahead, and put this out in that in that safety of that information. And this is also where digital publishing is really awesome, where you know you're not as opposed to print, where you have a version that's a snapshot in time of the of the state of the content for text, but in digital, if they're looking at a version, it can just update on the fly as things are fixed, and they don't need to keep worrying about which version is, this is the latest or not and but, yeah, there is a way to do that for text. Also, it's a little more manual.
Klappy 19:55
Yeah, there's so many assumptions that we have, like when the system for hundreds of. Years has been all about this, completing the translation, checking the translation, printing the translation, like you talking about print. I mean that print assumption has actually baked in a lot of our process, right? And so by the very nature of this being a digital world where we can the cost, let me, let me rephrase that, the cost of distributing Bible translations comes down to pennies when or less. When it's digital, however, when it's print. You know, there's the foundational like printing on a printing press. You know the the traditional way, when you have to print 10,000 Bibles, or whatever that number is, to get the gold? Did you know The Gilded edges and the leather bound feel like? If that's the goal, I can see why we can't do iterative publishing, because you're not going to print the book of Luke with of Luke with gilded edges in leather bound right? And then now you have Mark, okay, do you have two Bibles now? Or, you know, can you somehow, like, do you have it to where you can add in that book? So, so that mental model that everything has been based upon locked us into all of our tools, right? All of our tools have been built from the beginning with that in mind. So foundationally, there's a cost there in Joey you mentioned at the very beginning, even in English and the best case scenario where we have more resources about the Bible than any other language available. We still have to iterate. We still have new releases, like in I applaud the ESV when, when they, when they first said, Hey, this is the last edition we'll ever print. I kind of scratched my head. I'm like, Oh no, the English language changes. You know, from time to time, surely there'll be some point where there's going to need to be a change, and they have the humility to admit, okay, we need to make another release right in. They should be celebrated for acknowledging that then. And so there's, there's other translations that you know have stagnated and and there, there are major gaps between those releases, but without getting into that. So now imagine, because of the cost of printing has been the limiting factor. What if we have print on demand? What if we have digital Bibles actually as the primary release mechanism. We're not negating that. Once the Bible is fully done, then we'll print that leather bound the book that's worthy of being, you know, praised as you know, scripture, right? We're not negating that. That doesn't need to be to happen. But along the way, we're unlocking the ability for this to be tested in pulpits. It's it's tested in the churches by the people who are going to use it eventually. Why not use it now and give the feedback of, yeah, technically, that's accurate, but it just doesn't feel as natural, and then that process can actually help refine and give us feedback that wouldn't happen if we waited till it got printed and handed out.
Joel Matthews 23:30
Agreed, yeah, that's that's the exciting part, that technology changes the paradigm here for us, where we don't, where we have an opportunity to rethink the process here, and this is equally true for the oral Bible translation community too, where you know you don't, you don't need to wait until the end for having A full Bible recording. It's actually even better to to have iterative publishing for chunks of the Bible and let the community listen to it and provide feedback. In fact, that actually improves the quality of the translation more than any other simulated or any other smaller scale checking steps that we could do because it's actually in use and people are responding to it and giving us feedback. Yeah, I think this is it's a matter of us who are. I mean, as I think about myself, even growing up with so much text around me, we can kind of lock ourselves into, you know, once you have something printed, it's it's in your bookshelf, and stays there, or you look at it and it's always in that state, it doesn't change. And that's what's different, is now people are actually consuming scripture much more through their phones. And. Reading it on there or listening to it. It has become more and more easier to do that, even for people in smaller communities, because most of them have smartphones, if they don't have computers, and they look at their phones often, and lot of the ways that they might consume it is through bite sized devotionals of certain verses that they are pastor shared for their community, or something like that. And so all of that actually is highly valuable, and any feedback on that text. In fact, there is a whole approach of doing Bible translation through discipleship, making moments where they start with creating discipleship, making material which has scripture text embedded in them, and you do translations as part of creating that material. And it's it's a smaller set than the whole of the Bible, but it has a lot of important, common or popular scripture verses in it, and that becomes the foundation for you to then see as the first iteration of what's available. And then you iterate from there to expand scope, add more books, and there are existing approaches and organizations that are doing Bible translation that way. Yeah.
Klappy 26:21
It's interesting how each group that gets involved thinks differently and has a different set of assumptions, and so, like when it was the missionary, they're spending their life's work around building this translation, right? So the missionaries come and so that that long process makes sense, but once you start getting into the church, owning it and driving the process, they actually have more people that are able to be involved. And so we're actually able to unlock the iterative workflows, but taking it one step further to discipleship, making movements, and then starting with the actual use of the scripture in context of their of their materials, you know that that's a whole new set of constraints that we have to explore, and potentially even new tools and workflows to support that. And then, okay, so now we have all these verses. How do we pull them together, and what are the implications of that? Right? And, you know, just, just looking at orality and oral Bible translation as I've spent the last couple of years, diving in headfirst to oral Bible translation tools like the sets of assumptions for orality, change the workflows as well, and so, so, seeing the natural tendencies of Okay, now that we're working and operating this way, it makes way more sense for iterative publishing in orality, like couldn't even imagine another model at the moment, like the tools from the ground up, just assume iterative publishing. And so it's kind of exciting to see, because oral Bible translation. OBT is fairly new in the grand scheme of things. And so they're actually starting from the premise, and not really even questioning. Is iterative, publishing an option, and they're able to engage in okay? Now, how do we rethink the quality assurance and it impacts everything. Everything about Bible translation is impacted by this shift, and there's no way we would have time to touch on 10% of the issues in a podcast episode. So all the things that you may be thinking in your mind, what if or what about, and you know those things that are on the tip of your brain of like wanting to hear us debate or discuss today, we're not going to be able to get to them.
Isabella Scarinzi 28:49
So there hasn't been a single episode of this podcast where we haven't talked about AI, and I don't want to break this streak. Now, is there any way have we ideated on how AI is supporting publishing.
Klappy 29:07
Man, yeah, in many, many ways, right? You know, most of the time we think about AI historically is most useful in the drafting phase. But what we've noticed ever since, people are really getting good at taking advantage of tools such as chat, GPT and other AI assistants. Really, they're great at research and helping us understand, granted with the proper guardrails, if they're if they're locked in to only look at certain resources, and they know how to cite and they can be audited and trustworthy the only quote from trusted resources, then they can be excellent at, you know, not to overcomplicate his exegesis, but understanding Scripture as translators are translating, so that actually helps with the iterative publishing process. Us, because now you don't have to study a whole bunch of resources you can use just in time. Ai, understanding tool. You know, tools help you understand your passage you're working on. So if you have a question, you can get an answer much more quickly. And it's not just during the drafting phase or with human drafting, AI drafting, or just, no matter where the draft came from, the checking process. So now, while you're checking, you have instant access through these tools, such as, you know, BT servant and faith bridge. And there's all these AI assistants out there that are being trusted by the Bible translation community to use as research assistants throughout the process. And there's other ways that we're exploring as well to help with better understanding the process and flow. But I'll let Joel talk about other ways that he's seen AI being explored for this.
Joel Matthews 31:01
Yeah, those are great examples. Clappy to add. Maybe a few other dimensions is, you know, when you get down to the mechanics of it, publishing involves formatting, when you talk about text and making it look pretty on a screen. And that actually is not a glamorous work. It's tedious. It's laborious. And actually it's very important, because it breaks a reading flow, or it makes it so it's important to get it right. And thankfully, some of the newer models are really good at maintaining or fixing or adding such formatting for us. Now that doesn't take away the need for some more procedural programs that can can verify what the AI say llms have done, but it does make getting to the point of publishing a scripture to a screen or to print even much more easier, and that is a way that that it has been is being used, especially when you talk about in the Bible space, there is a format called Unified scripture format markers, which is usfm, and is a common format for saving or storing scripture content and for ultimately publishing it by converting usfm into other publishable formats. I think another thought I had about AI helping is also, you know, in the past, you would have to think of which apps or which websites finally you're going to put your content out into, and you have to probably work with that app developer or the website creator, because that's where, and I don't think that goes away today, but what AI has enabled is, if you want to create just a bespoke app with your own way of navigating scripture, whether it be a text audio or both, you can get AI to quickly put create a mobile app for you that is only custom made for your content. And the economics of creating an app has kind of changed so drastically that you can see it as iterative, also that you can throw away that app after the first stage of iteration, and then you create another app after because now you want to have more content or have want to show it differently, and it's kind of become iterative all around even on the client or the application side of things, because of AI. And I think that's a big impact that it has.
Klappy 34:02
So I'm gonna say something that I hope it ages, like milk, right? Like, I hope it, I hope by the end of 2026, this is no longer an issue. But you know, Joe, you're right. Like, first off, you talked about printing. Printing is hard. Printing has always been hard. Like, I remember when I was a kid we got our first printer, like getting something from the computer to the printer was like a weeks long job right in frustratingly enough, like I have two printers at my house in I have more problems with my printers. When I did all the research to make sure these were the most reliable, least problematic, highest customer satisfaction printers, I still have print issues. I don't understand how print is still so problematic in 2026 in the. The other thing you said, Joel, that I'll tie these things together here in March 2026, most ais that I did I use, we can finally have an idea and create a proof of concept, almost ready to send to the field within a week of, you know, quick iterations of that app that quickly in it's harder to format using the same AI system to format something that looks good to print. It's mind boggling. How is printing to a page harder or feels like for me, maybe, maybe I don't know how to whisper print speak to chat GPT, but it has the ugliest templates, like I worked so hard with chat GPT, and it can't Now, granted, I move over to Claude, and right now, as of today, going to Claude and I say, Hey, can you make this printable And look pretty. It actually has better, decent print, print, printable, whatever. You know, it looks good. But if I really want something to look fancy, I basically have to say, hey, go make a web app that's printable. And somehow that looks better. But it still doesn't look print quality, right? It just looks like a hack. You know, it's not just not perfected. So I hope by the end of this year, AI is going to help us get the last mile of Bible translation for iterative publishing well oiled, because it's still an arduous task, right there. There are great tools in our space that have helped us kind of bridge this usfm to to, you know, our publishing, you know, Joel, you know, we were talking about some of the, some of those apps before we recorded this episode. You know, scripture, app builder, PTX, print. You know, there's some tools out there that help us get through this last mile. But big picture, like we are still using like latex and other arduous tools and programming languages to get things to the printer that I just don't understand. Why can't we make things look like a Bible in an HTML page and then just click print on that, that the tools just aren't there yet without AI, let alone AI, navigating and making that up for us. That's just a gap that I'm hoping 2026 solves for the iterative publishing problem.
Joel Matthews 37:36
Yeah, I think some of the tooling out there that exists, which is not so much AI as it is making it a little bit easier for humans to get a printable version through normal software. I think PTX print has a has done a great job in trying to make it more option oriented, where a community member might be able to import a usfm into the application and say they want two column or one column, or they want footnotes looking like this, under at the bottom of the page, etc, I don't, I think it's a lot more accessible than you know, going to say InDesign to be able to properly do this as a more professional, printable Bible. There is, there are other tools that we are looking into, and some of them are more experimental, trying to use other frameworks to make this easily formatted for the web, because that is a big gap I feel is still left, is how do we get something that's in the translator's editor, And it probably might even look good on the editor. But how do we get this into a website or a mobile app screen that is still readable for the for the community, without having to learn HTML or or JavaScript or a CSS like those? Those sort of things are distracting and not productive for the translation team to look at and and there is, there are, there are paths to do this. I'm just saying, like you mentioned, clapping, it's not well oiled. We need to kind of work through some of the kinks. And with AI, it is promising, and we can, we can get there sooner, as I feel the future is, I don't think print will go away. In fact, they said that even with digital publishing in the past and it came to be that printed books became all the more popular. I don't think the print goes away, but I do think. Think when you talk about especially iterative publishing, it's highly valuable to have this in digital medium, even for a little Bible translation, that's the only way you can so we need to find good tooling that bridges the gap from the editor to a consumption app, and ideally, we also want ways to capture feedback. So this is not, you know, in intro to publishing, I don't think anybody is saying it's done, and the reader also, would all would also understand that. And as they read, they want to add some comments. And when you zoom out, it looks like a large scale community check actually, which is exactly the benefit of it. You put it out early, you get more feedback, and you improve it. That's the ideal case. So I think having ways to capture comments and feedback alongside what you're putting out and then aggregating that's gold information, goal data, for the translators to take a second pass or fix things, which is usually hard to gather otherwise.
Klappy 41:11
There's another topic like it's almost like this thing that people learn, have to learn the hard way. Everybody who gets involved in adapting their existing tools they've been working on. And I'll just, I know a lot of our audience is involved in actually creating Bible translation tools, right? Like that's what we talk about. So naturally, you know, it's our peers that are checking this out and listening to us, so I really appreciate that, and then I'm happy to know that they continue to listen to us and not just listen to one episode and not anymore. But I feel like you know, as I work together with everybody, there's something that we all learn the hard way, and that is iterative. Publishing means everything is a living document, right? The implications of iterative publishing means all the assumptions we had about publishing is different now, because it's not just a one stop shop of, okay, it's published now, it never changes. You wouldn't you wouldn't imagine like, it's hard to believe how many assumptions that impacts, like that one assumption impacts everything in the pipeline. Like, every API no longer can cache. Like, the caching strategies have to change. Like, the storage mechanisms have to change, like, because things could be modified and edited, that release cycle has to be thought about. You know, when there's a new release, it's not just that you're adding a book. You know, people have to realize that sometimes the previously released books have now had their own iterative cycle. Now that the Gospels are done, okay, let's do another pass on the other gospels and make sure there's consistency. The same thing with like as more and more Bible books of the Bible get get completed. There's a new, iterative past that happens. And so that thing, that one thing of this, this being a living document, is just something we can't quite wrap our head around the implications for the way we code our tools, until we live it. And then we realize, oh, man, that doesn't work. Or why is this not working? You know, why is this out of date? And so, you know, just my encouragement, I know, I know you talked about the open Bible technology community hackathon coming up. As we engage with that, I think that would be fun and exciting for for everybody to realize, if you're new into the space, hopefully you don't have to learn the hard way. Just keep in mind, these documents can change, so don't bake into your tools that you're creating and trying to help out in the Bible translation world. Just understand and realize that there will be iterative cycles to the Bible translation process. So if you're building tools for churches who receive these translations, and not even building tools just for Bible translators, but for the recipients, you know, the communities, the churches, we have to think that we have to appreciate that it's not just one release, you know, next month, next week, or maybe it's not till next year, like depending on, you know, the community and the release patterns, but there will be updates that happen more often than what you realize.
Isabella Scarinzi 44:32
Yeah, that's great. Thank you. Clappy. So publishing is challenging, especially when we think about vibrant translation acceleration and wanting to see communities access God's Word in a language they understand best best at a faster pace. So to our listeners, they heard potential solutions this past hour, but this is definitely an ideating kind of conversation that we're having, and we want. To invite you in, if you are attending the hackathon that's happening in the spring, maybe that's an area that you might explore. Just grab a team, think about some potential solutions and what role you can play as well. So thank you so much for listening, and we will see you at our next episode.
Klappy 45:19
Thank you. Thank you, Isabella
Theophany Media Media 45:21
the Bible translation innovation podcast is brought to you by the Eaton Innovation Lab. This episode is edited and produced by Jake dobrins With Theophany media. Your hosts were Joel Matthew and Christopher Clapp with facilitation by Isabella scarenzi. Please subscribe on your favorite podcast platform, and we'll be with you again next month. You.