git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Initial Japanese gitk translation

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 6, 2009, 01:40 UTC
Message-ID
<7vws9ymudz.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<FD6CAD0757FA434C91E904C1F202CBA1@DELL300>
"FORS Luis" <l-fors@cerca-jp.com> writes:
"FORS Luis" <l-fors@cerca-jp.com> writes:
Show 13 quoted lines
> My name is Luis Fors. I'm not a great Japanese speaker, and I have
> almost zero knowledge of tcl and getttext, but all of my coworkers are
> Japanese, and I couldn't just wait around for a translation to appear.
>
> This is my first time contributing, and I have no idea what I'm doing,
> so be please be gentle.
>
> This is a patch against gitk.git 5fdcbb13904e6...
>
> Feel free to bang this into whatever shape is necessary to include
> this in the next release.
>
> Thank you.

Judged by a native speaker (that is me), there are some funny translations we may want to fix up, but it should serve as a good basis for anybody to whip it into shape good enough and forward it to Paul to be merged.

Thanks.
> +#: gitk:113
> +msgid "Couldn't get list of unmerged files:"
> +msgstr "未マージファイルのリストをゲット出来ず:"

You are using です・ます style throughout the translation, so you would want to say:

    未マージファイルのリストを取得できません
or something like that.
Show 7 quoted lines
> +#: gitk:340
> +msgid "No files selected: --merge specified but no files are unmerged."
> +msgstr "ファイルが選択されていません:--mergeオプションが指定されたのに未マージファイルはありません。"
> +
> +#: gitk:343
> +msgid "No files selected: --merge specified but no unmerged files are within file limit."
> +msgstr "ファイルが選択されていません:--mergeオプションが指定されたのに選択されたファイル未マージファイルを含みません。No hay archivos seleccionados: se seleccionó la opción --merge pero los archivos especificados no necesitan fusión."
No habla Español, perdóname.
Show 7 quoted lines
> +#: gitk:1813
> +msgid "Reread references"
> +msgstr "照会情報再読込"
> +
> +#: gitk:1814
> +msgid "List references"
> +msgstr "照会情報出力"

I have never seen ref and reference translated as 照会 in the context of git.

There are some people working on translating the documentation; a good starting point would be:

    http://www8.atwiki.jp/git_jp/
and the glossary's translation is here.
    http://github.com/yasuaki/git-manual-jp/blob?path[]=Documentation&path[]=glossary.txt&raw=true

They translate "ref" as 参照 which may not be best but looks better than 照会. I wrote a magazine article in Japanese and I ended up calling them just リファレンス --- write pronunciation in kana which is a universal cop-out X-<.

> +msgid "Exact"
> +msgstr "完全な一致"
I'd drop な if I were translating this
Show 5 quoted lines
> +#: gitk:1970
> +#: gitk:3773
> +#: gitk:5518
> +msgid "IgnCase"
> +msgstr "大小文字を区別せず"

I'd say 区別しない instead of 区別せず as the rest is in です・ます style.

Show 5 quoted lines
> +msgid "Author"
> +msgstr "作者"
> +
> +msgid "Committer"
> +msgstr "コミット者"

I used 著者 for Author and 記録者 for Committer. The translated glossary I mentioned earlier seems to agree with me on Author (it cops out on committer by saying "コミットした人").

> +msgid "Diff this -> selected"
> +msgstr "これ→選択をdiff"
> +msgid "Diff selected -> this"
> +msgstr "選択→これをdiff"
Perhaps
    「これと選択したコミットの差分を見る」
    「選択したコミットとこれの差分を見る」

If you can affored to go a bit longer, I'd say このコミット instead of こ れ here, though.

> +#: gitk:2245
> +msgid "Blame parent commit"
> +msgstr "親コミットを責める"
This is a hard one ;-)  
Show 15 quoted lines
> +msgstr "<%s-Down>\tコミットのリストを一行下へスクロール"
> +
> +#: gitk:2532
> +#, tcl-format
> +msgid "<%s-PageUp>\tScroll commit list up one page"
> +msgstr "<%s-PageUp>\tコミットのリストを一ページ上へスクロール"
> +
> +#: gitk:2533
> +#, tcl-format
> +msgid "<%s-PageDown>\tScroll commit list down one page"
> +msgstr "<%s-PageDown>\tコミットのリストを一ページ下へスクロール"
> +
> +#: gitk:2534
> +msgid "<Shift-Up>\tFind backwards (upwards, later commits)"
> +msgstr "<Shift-Up>\t後進へ検索(うえの新しいリビジョンへ)"
逆方向検索 うえ should be 上
> +#: gitk:2535
> +msgid "<Shift-Down>\tFind forwards (downwards, earlier commits)"
> +msgstr "<Shift-Down>\t前進へ検索(下の古いリビジョンへ)"
前方向検索
Show 6 quoted lines
> +msgid "Local changes checked in to index but not committed"
> +msgstr "インデックスに入っている未コミット変更"
> +
> +#: gitk:4220
> +msgid "Local uncommitted changes, not checked in to index"
> +msgstr "インデックスの入っていない未コミット変更"
「に」入っていない。not「の」
> +msgid "Short SHA1 id %s is ambiguous"
> +msgstr "%sを含むSHA1が複数存在する"
Good job!!
> +#: gitk:7146
> +#, tcl-format
> +msgid "SHA1 id %s is not known"
> +msgstr "SHA1の%sは不明"
You probably do not want の here.
> +#: gitk:7430
> +msgid "Reverse"
> +msgstr "後進"
I am not sure about the context of this message but shouldn't it be 後退?
> +msgid "Tag \"%s\" already exists"
> +msgstr "タグ\"%s\"が既に存在する"
・・・は既に存在します
> +#: gitk:7708
> +msgid "Cherry-picking"
> +msgstr "リビジョンを任意に当てはまる(cherry-picking)"
当ては「め」る, perhaps?
Show 14 quoted lines
> +#: gitk:7755
> +msgid "Soft: Leave working tree and index untouched"
> +msgstr "軟らかい:ブランチもインデックスもそのまま"
> +
> +#: gitk:7758
> +msgid "Mixed: Leave working tree untouched, reset index"
> +msgstr "中庸:ブランチを触れずにインデックスをリセット"
> +#: gitk:7761
> +msgid ""
> +"Hard: Reset working tree and index\n"
> +"(discard ALL local changes)"
> +msgstr ""
> +"硬い:ブランチとインデックスをリセット\n"
> +"(ローカル変更が全て破壊される!)"

These are hard ones. I'd leave Soft/Mixed/Hard labels in English/alphabets if I were doing this, though.

> +msgid "The commits on branch %s aren't on any other branch.\nReally delete branch %s?"
> +msgstr "ブランチ%sが一意リビジョンを含む。\nそれでも削除しますか?"
ブランチ%sには他ブランチにマージされていないコミットがあります。それでも・・・
Show 7 quoted lines
> +#: gitk:9934
> +msgid ""
> +"Sorry, gitk cannot run with this version of Tcl/Tk.\n"
> +" Gitk requires at least Tcl/Tk 8.4."
> +msgstr ""
> +"gitkは現在のTcl/Tkバージョンでは実行できません。\n"
> +"Tcl/Tkバージョン8.4はgitkの最低条件です。"
Gitk には最低 Tcl/Tkバージョン8.4が必要です。
> +#: gitk:10098
> +#, tcl-format
> +msgid "Ambiguous argument '%s': both revision and filename"
> +msgstr "多義引数'%s':リビジョンでもファイル名でもあります"
引数'%s'は曖昧です:・・・
Previous: FORS LuisNext: Mike Hommey
Message 2 of 4 in “Initial Japanese gitk translation”
  1. Initial Japanese gitk translationFORS Luis, Apr 6, 2009
  2. Junio C HamanoApr 6, 2009
  3. Mike HommeyApr 6, 2009
  4. Felipe ContrerasApr 6, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.