Above all, make sure that programming terms and the pattern name itself are translated in a way that is common to Korean programmers. This is very crucial. I tried to use a friendly casual voice in the book, avoiding academic jargon and complexities. It would be nice if the translated variant retains the same spirit for easy reading and understanding.
I would like to point this right of the bet: keep things consistent.
-
If you translated the pattern name as A, do not refer to it as to B.
-
If you translated a role in the structure section as X, don't refer to it as Y later in the text. 90% of these links are established between things defined in the Structure and sections that go after it: "Applicability" & "How to Implement".