Now I could probably fix the line breaks and use machine translation coupled with an online context dictionary and glossing with a basic awareness of Korean as a head-final topic-comment language, but that frankly sounds like a pain. I can at least say right now that Google Translate keeps rendering 농인 as farmer (農人) rather than Deaf person (聾人)
Main
I tried converting PDF -> html and then using Firefox Translate but it turned out super weird:
IDK what the PDF -> html program did to keep the pagenation of the PDF. The generated HTML is a mess. possibly if a different tool was used for that conversion the translation would make more sense. Something that created a simpler output. And maybe making sure the local system is set up for Korea language.
Even better would be finding a non-PDF version of the document: ideally HTML but a doc or other format would be easier to convert to HTML.
Firefox translate can translate the PDF directly in-browser but only by selecting the text and right-click. You can do it a bit at a time, not the whole document. It translates the first paragraph of the above image as
I am not sure if that makes sense because I don’t know what is expected in an academic article about hand signs. But give it a shot.
I don’t understand Korean but DeepL has the best Korean>English translations of any service I’ve used and will translate pdfs if you make an account. I’ve had good luck using it to translate technical literature. It’s actually able to handle line breaks in Korean/Chinese/Japanese texts in a way that other services struggle with. It’s worth a shot.
If I have a chance this weekend I’ll see if I can’t mash out a translation that scans okay.