Please pull git-l10n updates for git v1.7.12-146-g16d26

4 messages, 2 authors, 2016-06-15 · open the first message on its own page

Please pull git-l10n updates for git v1.7.12-146-g16d26

From: Jiang Xin <hidden>
Date: 2016-06-15 22:54:44

Hi Junio,

The following changes since commit 16d26b168b371b2f4f86b1adb61470c6b08b27b9:

  Latter half of the second batch for 1.8.0 (2012-08-29 15:00:30 -0700)

are available in the git repository at:

  git://github.com/git-l10n/git-po master

for you to fetch changes up to 9a4f34bb6d11ab47d532f7798ecc2b051f6d8893:

  l10n: Update Swedish translation (1166t0f0u) (2012-09-13 06:33:25 +0800)

----------------------------------------------------------------
Jiang Xin (3):
      l10n: Update git.pot (2 new, 4 removed messages)
      l10n: zh_CN.po: translate 2 new messages
      Merge git://github.com/vnwildman/git

Peter Krefting (1):
      l10n: Update Swedish translation (1166t0f0u)

Ralf Thielow (1):
      l10n: de.po: translate 2 new messages

Tran Ngoc Quan (2):
      l10n: vi.po & TEAMS: review Vietnamese translation
      l10n: vi.po: update to v1.7.12-146-g16d26

 po/TEAMS    |    3 +-
 po/de.po    |  712 ++++++++++++------------
 po/git.pot  |  684 +++++++++++------------
 po/sv.po    |  715 ++++++++++++------------
 po/vi.po    | 1767 +++++++++++++++++++++++++++++++----------------------------
 po/zh_CN.po |  712 ++++++++++++------------
 6 files changed, 2394 insertions(+), 2199 deletions(-)


-- 
Jiang Xin

Re: Please pull git-l10n updates for git v1.7.12-146-g16d26

From: Nguyen Thai Ngoc Duy <hidden>
Date: 2016-06-15 22:54:45

(Dropping translators as they probably are not interested in this)

I saw a gnu project does this (I don't remember what project). If we
update .po* files with --no-location, we can avoid a lot of diff
noises due to line number changes. A typical translator does not care
about these lines anyway. Those who do can easily search the string in
source files without them.

On Thu, Sep 13, 2012 at 5:41 AM, Jiang Xin [off-list ref] wrote:
 po/TEAMS    |    3 +-
 po/de.po    |  712 ++++++++++++------------
 po/git.pot  |  684 +++++++++++------------
 po/sv.po    |  715 ++++++++++++------------
 po/vi.po    | 1767 +++++++++++++++++++++++++++++++----------------------------
 po/zh_CN.po |  712 ++++++++++++------------
 6 files changed, 2394 insertions(+), 2199 deletions(-)
-- 
Duy

Re: Please pull git-l10n updates for git v1.7.12-146-g16d26

From: Jiang Xin <hidden>
Date: 2016-06-15 22:54:45

2012/9/14 Nguyen Thai Ngoc Duy [off-list ref]:
(Dropping translators as they probably are not interested in this)

I saw a gnu project does this (I don't remember what project). If we
update .po* files with --no-location, we can avoid a lot of diff
noises due to line number changes. A typical translator does not care
about these lines anyway. Those who do can easily search the string in
source files without them.
I believe some translators need these location infomation to find the
context. In order to squelch noise, users can:

1. Define a new diff driver, such as:

    $ git config --global diff.podiff.textconv "sed -e '/^#/ d'"

2. Add two lines in .git/info/attributes to use this driver for po/pot files:

    *.po diff=podiff
    *.pot diff=podiff

--
Jiang Xin

Re: Please pull git-l10n updates for git v1.7.12-146-g16d26

From: Nguyen Thai Ngoc Duy <hidden>
Date: 2016-06-15 22:54:45

On Sat, Sep 15, 2012 at 8:34 AM, Jiang Xin [off-list ref] wrote:
2012/9/14 Nguyen Thai Ngoc Duy [off-list ref]:
quoted
(Dropping translators as they probably are not interested in this)

I saw a gnu project does this (I don't remember what project). If we
update .po* files with --no-location, we can avoid a lot of diff
noises due to line number changes. A typical translator does not care
about these lines anyway. Those who do can easily search the string in
source files without them.
I believe some translators need these location infomation to find the
context.
Unless you are also a git developer, I doubt if sha1_file.c makes
sense to any translators. In my 8 years of being translator/programmer
to open source world, I rarely look at those lines (though I admit I
do). A slightly modified suggestion is just drop line number, not the
file name, but xgettext does not support that, unfortunately.
-- 
Duy
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help