User Study for Improving Tools for Bible Translation

Joel Mathew, Ulf Hermjakob
2/1/2023
cs.CLcs.HC

No confident code implementation found for this paper.

Abstract

Technology has increasingly become an integral part of the Bible translation process. Over time, both the translation process and relevant technology have evolved greatly. More recently, the field of Natural Language Processing (NLP) has made great progress in solving some problems previously thought impenetrable. Through this study we endeavor to better understand and communicate about a segment of the current landscape of the Bible translation process as it relates to technology and identify pertinent issues. We conduct several interviews with individuals working in different levels of the Bible translation process from multiple organizations to identify gaps and bottlenecks where technology (including recent advances in AI) could potentially play a pivotal role in reducing translation time and improving overall quality.

View on arXivView PDF

Code Implementations

No confident code match yet

We couldn't find an author-owned or strongly-evidenced community implementation for this paper. Any repos shown below are weak matches — verify before relying on them.

No code implementations found yet.

Know of an implementation? Let us know in the comments below!

Similar Papers

Beyond Accuracy: Community Perspectives on Machine Translation

84% match2026

Prediction of Translation Techniques for the Translation Process

84% match2024

How to Design Translation Prompts for ChatGPT: An Empirical Study

83% match2023

Artificial intelligence contribution to translation industry: looking back and forward

82% match2024

Towards Making the Most of ChatGPT for Machine Translation

82% match1 repo742023

Machine Translation in the Wild: User Reaction to Xiaohongshu's Built-In Translation Feature

82% match2026

Cite this paper

@article{mathew2023user,
  title  = {User Study for Improving Tools for Bible Translation},
  author = {Joel Mathew and Ulf Hermjakob},
  year   = {2023},
  eprint = {2302.00778},
  archivePrefix = {arXiv},
  url    = {http://arxiv.org/abs/2302.00778v1}
}

Add a badge to your README

Shows whether official code is linked for this paper.

Code of Paper badge
[![Code of Paper](https://codeofpaper.com/badge/2302.00778.svg)](https://codeofpaper.com/paper/2302.00778)

Discussion