bzr - en to unknown language translation catalogue (30 entries)

en: kind changed
        File kind has been changed (e.g. from file to directory).
target: type changed
        File type has been changed (e.g. from file to directory).

en: To see ignored files use 'bzr ignored'.  For details on the
    changes to file texts, use 'bzr diff'.
target: To see ignored files, use 'bzr ignored'.  For details on the
    changes to file texts, use 'bzr diff'.

en: Since a lightweight checkout is little more than a working tree
    this will refuse to run against one.
target: Since a lightweight checkout is little more than a working tree,
    this will refuse to run against one.

en: Don't recursively add the contents of directories.
target: Do not recursively add the contents of directories.

en: invalid kind %r specified
target: invalid type %r specified

en: can not move root of branch
target: cannot move root of branch

en: List entries of a particular kind: file, directory, symlink.
target: List entries of a particular type: file, directory, symlink.

en: invalid kind specified
target: invalid type specified

en: Unrecognized bug %s. Commit refused.
target: Unrecognised bug %s. Commit refused.

en: Path "%(path)s" is not unicode normalized
target: Path "%(path)s" is not unicode normalised

en: Cannot operate on "%(filename)s" of unsupported kind "%(kind)s"
target: Cannot operate on "%(filename)s" of unsupported type "%(kind)s"

en: Root class for inventory serialization errors
target: Root class for inventory serialisation errors

en: Unsupported entry kind %(kind)s
target: Unsupported entry type %(kind)s

en: Kind change from %(from_kind)s to %(to_kind)s for %(path)s not supported by format %(format)r
target: Type change from %(from_kind)s to %(to_kind)s for %(path)s not supported by format %(format)r

en: %s cannot canonicalize CHKs.
target: %s cannot canonicalise CHKs.

en:   bzr status         summarize changes in working copy
      bzr diff           show detailed diffs
target:   bzr status         summarise changes in working copy
      bzr diff           show detailed diffs

en: Checkouts are source trees that are connected to a branch, so that when
    you commit in the source tree, the commit goes into that branch.  They
    allow you to use a simpler, more centralized workflow, ignoring some of
    Bazaar's decentralized features until you want them. Using checkouts
    with shared repositories is very similar to working with SVN or CVS, but
    doesn't have the same restrictions.  And using checkouts still allows
    others working on the project to use whatever workflow they like.
target: Checkouts are source trees that are connected to a branch, so that when
    you commit in the source tree, the commit goes into that branch.  They
    allow you to use a simpler, more centralised workflow, ignoring some of
    Bazaar's decentralised features until you want them.
    Using checkouts with shared repositories is very similar to working with 
    SVN or CVS, but doesn't have the same restrictions.  
    And using checkouts still allows others working on the project to use 
    whatever workflow they like.

en:   N File created
      D File deleted
      K File kind changed
      M File modified
target:   N File created
      D File deleted
      K File type changed
      M File modified

en: The intent is to make this file as small as possible to minimize maintenance.
target: The intent is to make this file as small as possible to minimise maintenance.

en: The ``password_encoding`` and ``verify_certificates`` fields are recognized but
    ignored in the actual implementation.
target: The ``password_encoding`` and ``verify_certificates`` fields are recognised but
    ignored in the actual implementation.

en: Bazaar tries to avoid conflicts ; its aim is to ask you to resolve the
    conflict if and only if there's an actual conceptual conflict in the source
    tree.  Because Bazaar doesn't understand the real meaning of the files being
    versioned, it can, when faced with ambiguities, fall short in either direction
    trying to resolve the conflict itself. Many kinds of changes can be combined
    programmatically, but sometimes only a human can determine the right thing to
    do.
target: Bazaar tries to avoid conflicts; its aim is to ask you to resolve the
    conflict if and only if there's an actual conceptual conflict in the source
    tree.  Because Bazaar doesn't understand the real meaning of the files being
    versioned, it can, when faced with ambiguities, fall short in either direction
    trying to resolve the conflict itself. Many kinds of changes can be combined
    programmatically, but sometimes only a human can determine the right thing to
    do.

en: Various actions are available depending on the kind of conflict, for some of
    these actions, Bazaar can provide some help. In the end you should at least
    inform Bazaar that you're done with the conflict with::
target: Various actions are available depending on the kind of conflict; for some of
    these actions, Bazaar can provide some help. In the end you should at least
    inform Bazaar that you're done with the conflict with::

en: ``bzr resolve`` recognizes the following actions:
target: ``bzr resolve`` recognises the following actions:

en: To resolve that kind of conflict, you just have to decide what name should be
    retained for the file involved.
target: To resolve that kind of conflict, you just have to decide which name should be
    retained for the file involved.

en: In this situation, Bazaar will cancel the move, and leave ``white`` in
    ``black``.  To resolve that kind of conflict, you just have to decide what
    name should be retained for the directories involved.
target: In this situation, Bazaar will cancel the move, and leave ``white`` in
    ``black``.  To resolve that kind of conflict, you just have to decide which
    name should be retained for the directories involved.

en: To resolve that kind of conflict, you have to decide what name should be
    retained for the file, directory or symlink involved.
target: To resolve that kind of conflict, you have to decidewhich name should be
    retained for the file, directory or symlink involved.

en: To generalize, there are two content formats supported by Bazaar:
target: To generalise, there are two content formats supported by Bazaar:

en: This situation commonly arises when using a centralized workflow with local
    commits.  If someone else has committed new work to the mainline since your
    last pull and you have local commits that have not yet been pushed to the
    mainline, then your local branch and the mainline have diverged.
target: This situation commonly arises when using a centralised workflow with local
    commits.  If someone else has committed new work to the mainline since your
    last pull and you have local commits that have not yet been pushed to the
    mainline, then your local branch and the mainline have diverged.

en: Called after new branch initialization completes. post_branch_init is
    called with a bzrlib.branch.BranchInitHookParams. Note that init,
    branch and checkout (both heavyweight and lightweight) will all
    trigger this hook.
target: Called after new branch initialisation completes. post_branch_init is
    called with a bzrlib.branch.BranchInitHookParams. Note that init,
    branch and checkout (both heavyweight and lightweight) will all
    trigger this hook.

en: Invoked after a repository has been initialized. post_repo_init is
    called with a bzrlib.controldir.RepoInitHookParams.
target: Invoked after a repository has been initialised. post_repo_init is
    called with a bzrlib.controldir.RepoInitHookParams.
