[pacman-dev] [PATCH] Fix typo in german translation
This patch fixes a typo in the german translation of pacman. Because the german word for package is "Paket" not "Packet". Signed-off-by: Jan-Marten Brüggemann <brueggemann@b1-systems.de> --- src/pacman/po/de.po | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/pacman/po/de.po b/src/pacman/po/de.po index e9c9460..45f594e 100644 --- a/src/pacman/po/de.po +++ b/src/pacman/po/de.po @@ -1354,7 +1354,7 @@ msgstr "Konnte den Vorgang nicht vorbereiten (%s)\n" #: src/pacman/remove.c:125 src/pacman/sync.c:724 #, c-format msgid "%s: removing %s breaks dependency '%s'\n" -msgstr "%s: das Entfernen von %s löscht ein benötigtes Packet von '%s'\n" +msgstr "%s: das Entfernen von %s löscht ein benötigtes Paket von '%s'\n" #: src/pacman/remove.c:144 #, c-format @@ -1494,7 +1494,7 @@ msgstr "%s: benötigt %s\n" #, c-format msgid "%s: installing %s (%s) breaks dependency '%s'\n" msgstr "" -"%s: das Installieren von %s (%s) löscht ein benötigtes Packet von '%s'\n" +"%s: das Installieren von %s (%s) löscht ein benötigtes Paket von '%s'\n" #: src/pacman/sync.c:744 #, c-format -- 2.9.0
Am 26.06.2016 12:22, schrieb Jan-Marten Brüggemann:
This patch fixes a typo in the german translation of pacman. Because the german word for package is "Paket" not "Packet".
Signed-off-by: Jan-Marten Brüggemann <brueggemann@b1-systems.de> --- src/pacman/po/de.po | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/pacman/po/de.po b/src/pacman/po/de.po index e9c9460..45f594e 100644 --- a/src/pacman/po/de.po +++ b/src/pacman/po/de.po @@ -1354,7 +1354,7 @@ msgstr "Konnte den Vorgang nicht vorbereiten (%s)\n" #: src/pacman/remove.c:125 src/pacman/sync.c:724 #, c-format msgid "%s: removing %s breaks dependency '%s'\n" -msgstr "%s: das Entfernen von %s löscht ein benötigtes Packet von '%s'\n" +msgstr "%s: das Entfernen von %s löscht ein benötigtes Paket von '%s'\n"
#: src/pacman/remove.c:144 #, c-format @@ -1494,7 +1494,7 @@ msgstr "%s: benötigt %s\n" #, c-format msgid "%s: installing %s (%s) breaks dependency '%s'\n" msgstr "" -"%s: das Installieren von %s (%s) löscht ein benötigtes Packet von '%s'\n" +"%s: das Installieren von %s (%s) löscht ein benötigtes Paket von '%s'\n"
#: src/pacman/sync.c:744 #, c-format
This seems to be already fixed in Transifex. There was a third instance of this "Packet/Paket" error, which I have fixed too. Please note that translation problems should be discussed with the l10n-group at Transifex, not at this list. As an aside, I should also note that outscourcing translations to Transifex was one of the worst decisions ever made on this list. Transifex lacks a decent VCS, which means that I cannot easily see changes done by my collaborators. Things were way much easier when just used git. And we can get a seperate git-repo anywhere for free.
On 27/06/16 02:32, Matthias Gorissen wrote:
As an aside, I should also note that outscourcing translations to Transifex was one of the worst decisions ever made on this list. Transifex lacks a decent VCS, which means that I cannot easily see changes done by my collaborators. Things were way much easier when just used git. And we can get a seperate git-repo anywhere for free.
You can use the transifex client to pull the changes then commit it to a local repo. A simple script could be run each day. I know its far from an ideal solution, and you still to go to transifex to look at the change history... This has simplified things a lot from the handling of translation files at the pacman end. A
On 27/06, Allan McRae wrote:
On 27/06/16 02:32, Matthias Gorissen wrote:
As an aside, I should also note that outscourcing translations to Transifex was one of the worst decisions ever made on this list. Transifex lacks a decent VCS, which means that I cannot easily see changes done by my collaborators. Things were way much easier when just used git. And we can get a seperate git-repo anywhere for free.
You can use the transifex client to pull the changes then commit it to a local repo. A simple script could be run each day. I know its far from an ideal solution, and you still to go to transifex to look at the change history...
This has simplified things a lot from the handling of translation files at the pacman end.
There's not really anything that prevents the translation teams from doing their work in Git and then importing that into transifex either. -- Sincerely, Johannes Löthberg PGP Key ID: 0x50FB9B273A9D0BB5 https://theos.kyriasis.com/~kyrias/
Am 27.06.2016 07:37, schrieb Allan McRae:
On 27/06/16 02:32, Matthias Gorissen wrote:
As an aside, I should also note that outscourcing translations to Transifex was one of the worst decisions ever made on this list. Transifex lacks a decent VCS, which means that I cannot easily see changes done by my collaborators. Things were way much easier when just used git. And we can get a seperate git-repo anywhere for free.
You can use the transifex client to pull the changes then commit it to a local repo. A simple script could be run each day. I know its far from an ideal solution, and you still to go to transifex to look at the change history...
This has simplified things a lot from the handling of translation files at the pacman end.
A Since you have seemed to grasped the basic message ("Matt hates Transifex!"), I don't want to make any fuzz about it. Devs make decisions, translators try to deliver in time.
A local repo (which I would own as leader of just one local-language community) is an awkward work-around, and somewhat against the principles of decentralization and collaborative work inspired by git. The crucial point here is that devs work continuasly, while translators get active only once or twice a year. So we will stick with the solution most comfortable at the dev-side.
participants (4)
-
Allan McRae
-
Jan-Marten Brüggemann
-
Johannes Löthberg
-
Matthias Gorissen