Ask
We drafted a Korean version of our English UI; a native Korean reader should say which strings sound translated
Goal and context
Pumasi ships in English today. We drafted a Korean version of the interface, string by string, and the drafts were written by people who are fluent in Korean but think about the product in English first. We suspect some of them read like translations: grammatically fine, but not what a Korean product would actually say. We cannot judge this ourselves any more because we have read them too many times. Below are twenty-two drafts, each paired with the English string it came from, grouped by where the English appears in the product today. The product is a marketplace where a person requests one piece of AI-assisted help (an "Offer") for a fixed price in internal Credits, or posts an "Open Request" that another member answers once. The audience is developers who use coding agents. The register we want is plain, direct, slightly warm, never salesy. English product terms (Offer, Request, Result, Credits, Claim, Member) stay in English on purpose; please do not translate those, but do say if the Korean around them makes them awkward. Offer list page 1. EN "Find expertise that runs as an Agent. Ask once, get a complete Result." / KO 한 번 요청하고, 완결된 Result를 받으세요. 2. EN "No Offer fits?" / KO 적합한 Offer가 없나요? 3. EN "No Offers available right now" / KO 현재 이용 가능한 Offer가 없습니다 4. EN "One answer" / KO 한 번만 답변 5. EN "About 2 min" / KO 약 2분 6. EN "Request for 500 Credits" / KO 500 Credits로 요청하기 Open Request form 7. EN "Share what you need and the Result you want. Another Member answers once with their own Agent." / KO 필요한 도움과 원하는 Result를 공개하세요. 다른 Member가 자신의 Agent로 한 번 답변합니다. 8. EN "Goal and context" / KO 목표와 맥락 9. EN "Result you want" / KO 원하는 Result 10. EN "Public reference notes (optional)" / KO 공개 가능한 참고 맥락 (선택) 11. EN "Comma-separated · up to 5" / KO 쉼표로 구분 · 최대 5개 12. EN "Everything above is visible to other Members and to Codex." / KO 위 내용은 다른 Member와 Codex에게 공개됩니다. 13. EN "I haven't included account details, secrets, or anything I'm not allowed to share." / KO 계정 정보, 비밀, 공유 권한이 없는 내용을 넣지 않았습니다. 14. EN "Use 500 Credits to publish this Request." / KO 500 Credits를 사용해 이 Request를 공개합니다. 15. EN "Publish for 500 Credits" / KO 500 Credits로 공개 Errors and status 16. EN "Check what you're about to publish." / KO 공개할 Request 내용을 다시 확인해 주세요. 17. EN "Check what you're asking for and confirm the 500 Credits." / KO 요청할 내용과 500 Credits 사용을 다시 확인해 주세요. 18. EN "The Agent has already picked up this Request. Wait for the Result." / KO Agent가 이미 이 Request를 맡았습니다. Result를 기다려 주세요. 19. EN "Request canceled. Your 500 Credits are back." / KO Request를 거두어 500 Credits를 돌려드렸습니다. 20. EN "A Result has already been sent." / KO 이 Request는 이미 끝났습니다. 21. EN "Check your Result. It needs to be one complete answer." / KO 한 번의 완성된 Result를 확인해 주세요. 22. EN "This Offer can't take Requests right now." / KO 이 Offer는 지금 요청할 수 없습니다. Things we are unsure about and would like an opinion on: whether 거두다 (19) is a natural verb for "take back / withdraw" a request, or whether 취소 or 철회 would be expected; whether 한 번만 답변 (4) reads as a limitation or as a feature; whether 완결된 (1) is a word a product would use; and whether the polite endings are consistent enough across the set. We are asking a Korean speaker to answer in Korean. This request is in English because the person posting it thinks in English; the review itself should be in whatever language is most natural for you, and Korean is preferred for the rewrites.
Result you want
Answer in Korean (English is fine for any framing you want to add). For each numbered string: - **Verdict:** natural / slightly translated / clearly translated / wrong register. - **Why,** in one sentence, only when the verdict is not "natural". - **Rewrite,** at most one, keeping the English product terms and the meaning. Leave it out if the original is fine. Then a short closing section: - **Patterns.** Two or three things that recur across the set (a particle habit, an ending, a word choice), so we can fix the pattern rather than the instances. - **The four questions we asked** (거두다, 한 번만 답변, 완결된, endings), answered directly. Please do not propose new strings we did not list, and do not change the English terms into Korean.
Reference notes
The English strings are live in `pumasi` (Next.js app, English-only interface). The Korean drafts are not shipped and exist only in this review. Nothing here is a translation memory: every draft was written fresh from the English, so a rewrite that departs from the English wording is fine as long as it says the same thing to the same reader. ---
Details
- Response
- One answer
- Credits
- 500
The Request is public. Only the Member who asked and the Member who answers see the Result.