po: Fix the 'All key' Korean translation.

[Francois Gouget]

---

We have two 'Yes|No|All' messages:
  msgid " (Yes|No|All)"
  msgstr "(예|아니오|모두)"

  msgid "Overwrite %1? (Yes|No|All)\n"
  msgstr "%1를 덮어쓰겠습니까? (예|아니오|모두)\n"

And logically the 'Yes' and 'No' keys instruct the user to type the 
corresponding Korean strings:

msgctxt "Yes key"
msgid "Y"
msgstr "예"

msgctxt "No key"
msgid "N"
msgstr "아니오"

Actually the translation for 'N' looks like more than one character but 
I suspect the code can deal with it anyway. I further suspect it will 
only check the first (Unicode) character of the string typed by the user 
but that should be enough to distinguish all three answers. So hopefully 
all is well till now.

However the 'All' key translation told the code to expect an 'A' which 
is not what the user is told to type.

   msgctxt "All key"
   msgid "A"
   msgstr "A"

So I modified that translation by following the 'Yes' and 'No' ones.

See also this discussion for an alternative way to deal with these 
prompts and avoid requiring that the user type non-Ascii characters:
 * Should we translate the prompt
   http://www.winehq.org/pipermail/wine-devel/2013-July/100454.html


 po/ko.po |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-po-Fix-the-All-key-Korean-translation.bin
Type: application/octet-stream
Size: 2367 bytes
Desc: 
URL: <http://www.winehq.org/pipermail/wine-patches/attachments/20130712/4f263dd3/attachment.bin>