Re: [po]updated korean resource(2012-1-28)

2012-01-29 Thread Frédéric Delanoy
2012/1/28 Hwang YunSong(황윤성) 

>
> fuzzy sections tranlated
>
>  <http://www.dreamwiz.com/> http://www.dreamwiz.com/
>
> <http://mall.shinsegae.com/display/display/planshop.do?disp_ctg_id=10049845&clickarea=dreamwiz_etc>
>
>
You should send your patch in plain text format (as all mails to wine-devel
/ wine-patches).
Also, you shouldn't specify a date in the patch subject line (Change
PO-Revision-Date in the po file instead for instance)
so "[po]updated korean resource(2012-1-28)" should be sthg like "po: Update
Korean translation" to conform to naming conventions (see
http://wiki.winehq.org/SubmittingPatches).

Frédéric



Re: [po]updated korean resource(2012-1-22)

2012-01-23 Thread Francois Gouget
Hi,

Thanks a lot for the translation update.

> -#, fuzzy
>  msgid "&Width:"
>  msgstr "너비(&W) :"
[...]
> -#, fuzzy
>  msgid "&Height:"
>  msgstr "높이(&H) :"
[...]

How come these (there is a whole series) have a space before the colon? 
That does not seem to be the case in other translations with a trailing 
colon (and may be why these ended up as fuzzy).


-- 
Francois Gouget   http://fgouget.free.fr/
   Cahn's Axiom: When all else fails, read the instructions.


Re: [po]updated korean resource(2011-09-30)

2011-10-01 Thread Francois Gouget
On Fri, 30 Sep 2011, Hwang YunSong(황윤성) wrote:
[...]
>  #: winecfg.rc:88
> -#, fuzzy
>  msgid "(None)"
> -msgstr "없음"
> +msgstr "(없음)"

I think you're missing a closing parenthesis here.


-- 
Francois Gouget   http://fgouget.free.fr/
question = ( to ) ? be : ! be;
  -- Wm. Shakespeare


Re: [po]updated korean resource(2011-09-19)

2011-09-19 Thread Francois Gouget

 msgstr ""
+"Wine is free software; you can redistribute it and/or modify it under the "
+"terms of the GNU Lesser General Public License as published by the Free "
+"Software Foundation; either version 2.1 of the License, or (at your option) "
+"any later version.\n"
+"\n"
+"Wine is distributed in the hope that it will be useful, but WITHOUT ANY "
+"WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS "
+"FOR A PARTICULAR PURPOSE.  See the GNU Lesser General Public License for "
+"more details.\n"
+"\n"
+"You should have received a copy of the GNU Lesser General Public License "
+"along with Wine; if not, write to the Free Software Foundation, Inc., 51 "
+"Franklin St, Fifth Floor, Boston, MA 02110-1301, USA."

This is not a translation so I don't think it should be put in the PO 
file[1]. Copying the English string is not needed by Wine and it will 
only make it less likely that a proper translation is provided later.


[1] Also Korean is not an RTL language so the 'Hebrew' exception does 
not apply.

-- 
Francois Gouget   http://fgouget.free.fr/
   La terre est une bêta...


Re: [po]updated korean resource(2011-09-16)

2011-09-17 Thread Francois Gouget

>  #: attrib.rc:47
> -#, fuzzy
>  msgid ""
>  "ATTRIB - Displays or changes file attributes.\n"
>  "\n"

The reason why this one was fuzzy is that the indentation changed. 
However the translation's indentation has not be updated (which might 
possibly be ok for Korean), and it also seems to be pretty inconsistent 
(e.g. between the +/- lines and the R/A/etc ones. Also the '[drive:]' 
should probably really be indented.

 #: cmd.rc:288
-#, fuzzy
 msgid ""
 "CMD built-in commands are:\n"
 "ASSOC\t\tShow or modify file extension associations\n"

The translation is missing the XCOPY line (it's hard to spot in the 
middle of all these lines).


Maybe I should add translator comments when I mark a translation as 
fuzzy. This way the real translator would not have to puzzle over what 
caused the string to be marked as fuzzy. I have not been doing it 
because I worry they may be tricky to remove with some PO editors (but 
maybe my fears are unfounded).


-- 
Francois Gouget   http://fgouget.free.fr/
 Linux, WinNT, MS-DOS - also known as the Good, the Bad and the Ugly.




Re: 78278: Subject: [po]updated korean resource

2011-09-01 Thread buildbot
The Buildbot has detected a failed build on builder runtests while building 
Wine.
Full details are available at: 
http://buildbot.kegel.com/builders/runtests/builds/223
BUILD FAILED: failed git


For more info about this message, see http://wiki.winehq.org/BuildBot





Re: [po]updated korean resource

2011-08-28 Thread Henri Verbeet
On 28 August 2011 23:51, Dan Kegel  wrote:
> Maybe it's in how I fetched the patch?
> $ wget http://source.winehq.org/patches/data/78034
> $ sha1sum 78034
> b363a8529306e5e8fef896f79cdf0580fa20e298  78034
>
That's a different patch, superseded by this one. I suppose that could
have been indicated with something slightly more verbose than
"updated", but nevertheless.




Re: [po]updated korean resource

2011-08-28 Thread Dan Kegel
On Sun, Aug 28, 2011 at 2:33 PM, Henri Verbeet  wrote:
> Works fine for me. Also, don't use patch to apply git patches.

Strange:

$ git apply korean.patch
error: patch failed: po/ko.po:8715
error: po/ko.po: patch does not apply

Maybe it's in how I fetched the patch?
$ wget http://source.winehq.org/patches/data/78034
$ sha1sum 78034
b363a8529306e5e8fef896f79cdf0580fa20e298  78034

But even if I do
$ wget 
'http://www.winehq.org/pipermail/wine-patches/attachments/20110825/aa6694e4/attachment-0001.obj'
$ git apply attachment-0001.obj
it still fails similarly.

What is the right sha1sum for the patch?




Re: [po]updated korean resource

2011-08-28 Thread Henri Verbeet
2011/8/28 Dan Kegel :
> Patch failed to apply here:
> patching file po//ko.po
> Hunk #1 succeeded at 775 (offset -4 lines).
> Hunk #2 succeeded at 783 (offset -4 lines).
> Hunk #3 succeeded at 798 (offset -4 lines).
> Hunk #4 FAILED at 8714.
> Hunk #5 FAILED at 8809.
> Hunk #6 succeeded at 8812 (offset -23 lines).
> Hunk #7 FAILED at 8968.
> Hunk #8 succeeded at 10220 (offset -25 lines).
> 3 out of 8 hunks FAILED -- saving rejects to file po//ko.po.rej
>
Works fine for me. Also, don't use patch to apply git patches.




re: [po]updated korean resource

2011-08-28 Thread Dan Kegel
Patch failed to apply here:
patching file po//ko.po
Hunk #1 succeeded at 775 (offset -4 lines).
Hunk #2 succeeded at 783 (offset -4 lines).
Hunk #3 succeeded at 798 (offset -4 lines).
Hunk #4 FAILED at 8714.
Hunk #5 FAILED at 8809.
Hunk #6 succeeded at 8812 (offset -23 lines).
Hunk #7 FAILED at 8968.
Hunk #8 succeeded at 10220 (offset -25 lines).
3 out of 8 hunks FAILED -- saving rejects to file po//ko.po.rej

Also, please send plain text email next time (but still with the patch
as an attachment).