search

Warzone2100 / old-trac-import

Archived Import of (old) Warzone 2100 Trac
0 stars 0 forks source link

German translation update #4845

Closed wzdev-ci closed 5 years ago

wzdev-ci commented 5 years ago

resolution_fixed type_bug | by alfred007

The attached file includes translations for the new options in the main menu which has Forgon implemented at the beginning of this year. It also includes some suggestions for changes of old translations and some corrections of misspellings.

Issue migrated from trac:4845 at 2022-04-16 13:33:10 -0700

wzdev-ci commented 5 years ago

alfred007 uploaded file Änderungen.odt (23.0 KiB)

wzdev-ci commented 5 years ago

alfred007 commented

I made some additions to my attached file, so here is the current version. Ignore the old one.

wzdev-ci commented 5 years ago

alfred007 uploaded file Änderungen ergänzt.odt (23.6 KiB)

wzdev-ci commented 5 years ago

Kreuvf commented

Thank you.

This will take some time. Please remind me in a week.

wzdev-ci commented 5 years ago

alfred007 commented

I made a comparison between a commented po-file of Forgon and the current master version. In the added file "Weitere Änderungen" are some more suggestions. I think Kreuvf will need more time to check this.

wzdev-ci commented 5 years ago

alfred007 uploaded file Weitere Änderungen.odt (36.8 KiB)

wzdev-ci commented 5 years ago

Forgon changed blocking which not transferred by tractive

wzdev-ci commented 5 years ago

Forgon changed blockedby which not transferred by tractive

wzdev-ci commented 5 years ago

Forgon commented

Visit http://ix.io/1vm7 to view the latest state of my German PO file.

wzdev-ci commented 5 years ago

alfred007 commented

I noticed that the spoken translation often differs from the written.

Three examples from Alpha 10:

msgid "Initial research confirms it will be of great benefit to the Project." msgstr "Anfängliche Analysen bestätigen, dass sie für das Projekt von großem Vorteil sein werden." Suggestion from Forgon: Erste Forschungsergebnisse bestätigen, dass sie für das Projekt von großem Vorteil sein werden. Spoken: Die ersten Untersuchungen zeigen, dass diese sehr vorteilhaft für das Projekt sein wird.

msgid "Enemy forces are approaching from the east and north." msgstr "Feindliche Truppen rücken von Osten und Norden an." Spoken: Commander, wir orten Streitkräfte, die sich von Osten und Norden nähern

msgid "Hold the bases and repulse any attacks." msgstr "Halten Sie die Stellungen und schlagen Sie den Angriff zurück." Suggestion from Forgon: Halten Sie die Basen und schlagen Sie jeden Angriff zurück. Spoken: Halten Sie die Basis und wehren Sie alle Angriffe ab.

The question is: Should we adapt the written translation to the spoken or not?

If it's just a matter of work, I can do it.

wzdev-ci commented 5 years ago

Kreuvf commented

Replying to Warzone2100/old-trac-import#4845 (comment:5):

I noticed that the spoken translation often differs from the written.

As far as I know, it has always been like this, even in English.

The question is: Should we adapt the written translation to the spoken or not?

If it's just a matter of work, I can do it.

Nope, leave things as they are.

wzdev-ci commented 5 years ago

Kreuvf commented

So, if I am seeing this correctly, there are two files I have to check: Änderungen ergänzt.odt​ and Weitere Änderungen.odt​. Is that correct?

alfred007, how tech-savvy would you rate yourself? Would you be interested in learning another way to prepare your changes, one that makes it way easier for me/the WZP? ;)

wzdev-ci commented 5 years ago

Kreuvf changed status from new to assigned

wzdev-ci commented 5 years ago

Kreuvf changed owner from ` toKreuvf`

wzdev-ci commented 5 years ago

Kreuvf changed operating_system which not transferred by tractive

wzdev-ci commented 5 years ago

Kreuvf commented

Switching to German for commenting on comments in the ODT files:

„Radar Zoom“ ist dann „Minikartengröße“. Oder Dir fällt noch was griffigeres ein.

Grundsätzlich übersetze ich nur. "Zoom" halte ich mittlerweile für hinreichend verbreitet, dass der Begriff allgemein einsetzbar ist. Auch wenn es rein optisch aussieht wie eine Einstellung für die Minikartengröße, so behalte ich die Absicht der Entwickler das als Zoom der Minikarte zu betrachten bei: Minikartenzoom.

„Tracked“ mit „Schleichend“

Ich denke, dass das etwas komplizierter ist. "tracked" enthält "track" wie "Spur", sodass im Englischen klar ist, dass eine Spur nachgefahren wird. Das ist daher natürlich langsam, da das somit quasi animiert ist. "Schleichend" wiederum entählt ein Element der Unauffälligkeit und absichtlichen Langsamkeit. Beides ist im Original nicht gegeben. Nach langem Herumüberlegen bin ich auf "Sanft" gekommen.

„strongpoint“ hast Du ansonsten mit Aufhängung übersetzt. Stellung ist Deine Übersetzung für „emplacement“. Sollte hier somit auch als Aufhängung übersetzt werden.

Es handelt sich bei beiden Beispielen um emplacements. Daher müssen alle andere angepasst werden, denn "Aufhängung" steht für hardpoints.

Ich halte es für die Unterscheidung für sinnvoll, bei den beiden ersten Übersetzungen den Begriff „Radar“ mit in die Übersetzung zu nehmen.

Das bleibt so wie es ist. Spielerisch gibt es keinen Unterschied und, sofern ich das richtig sehe, werden auch nie "VTOL CB Radar Tower", "VTOL CB Radar Turret" und "VTOL CB Tower" gleichzeitig in einem Menü zu sehen sein.

"Turtle AI" betrachte ich als Eigenname, den ich unübersetzt lasse.

Für das, was ihr in "Weitere Änderungen.odt" habt, will ich das nicht so bearbeiten wie ich es aktuell mache. Bei der Größe ist ein anständiger Patch nötig.

New de.po does not contain the updates from "Weitere Änderungen.odt".

wzdev-ci commented 5 years ago

Kreuvf uploaded file update-de.po-20181209.patch (31.1 KiB)

Update de.po@5807d38b51120e8782609f3b28d348624647f306

wzdev-ci commented 5 years ago

alfred007 commented

Replying to Kreuvf

alfred007, how tech-savvy would you rate yourself? Would you be interested in learning another way to prepare your changes, one that makes it way easier for me/the WZP? ;

Sure, why not. Einen Versuch ist es wert. ;) Mit klaren Anweisungen bekomme ich (fast) alles hin.

wzdev-ci commented 5 years ago

Forgon commented

@Kreuvf

Visit http://ix.io/1w3d to view the latest state of my German PO file. It includes translations not only for the current master version, but also a few unpublished commits. Developed together with alfred007, it takes all his findings and suggestions into account and is thus the most advanced German translation so far. I hope you find it useful.

wzdev-ci commented 5 years ago

Kreuvf commented

First, please apply my updated de.po, so that we can close this issue. IMHO unpublished commits and your latest state do not belong in this issue. Is that okay with you?

Generally, I do not want to work with unpublished commits. If you want to add comments to PO files, these should go into every PO file. You probably know how to do that :)

When everything is in master, so that I can get it easily (via git = no manual downloading of unversioned files), please open a new ticket.

In parallel, I am sending alfred007 my suggestion to make his work easier for me to apply/check (via e-mail).

wzdev-ci commented 5 years ago

Forgon commented

Replying to Warzone2100/old-trac-import#4845 (comment:12):

First, please apply my updated de.po, so that we can close this issue. IMHO unpublished commits and your latest state do not belong in this issue. Is that okay with you?

Generally, I do not want to work with unpublished commits. If you want to add comments to PO files, these should go into every PO file. You probably know how to do that :)

When everything is in master, so that I can get it easily (via git = no manual downloading of unversioned files), please open a new ticket.

In parallel, I am sending alfred007 my suggestion to make his work easier for me to apply/check (via e-mail). I have applied the changes from your patch that I agreed with to my PO file, which has been sent to alfred007 for review. Once I have received his feedback, we will hopefully quickly settle remaining disagreements and finish this patch.

wzdev-ci commented 5 years ago

Kreuvf commented

Let me quickly explain how these things usually went:

  1. make -Cpo update-po (iirc) in the po directory, results committed.
  2. Local update of the po file.
  3. New ticket with patch or full po file.

Personally, I could work with that just fine as everything was either in git or in Trac and could be traced back easily. Nobody ever told me of any changes to this workflow.

Replying to Warzone2100/old-trac-import#4845 (comment:13):

[...] changes from your patch that I agreed with [...]

That is exactly the reason why I object to this intransparent workflow. If you do not mind, I have no problem putting stuff in a branch on GitHub and making a PR, so that everybody can comment on every single line before merging. From what you are writing I am under the impression that it will not be as easy for me to see exactly what changed, not even talking about discussing single points.

The de.po patch should apply cleanly to 5807d38b51120e8782609f3b28d348624647f306. Please just push that to master and I am open to anything that comes on top of these changes.

Also, please answer my [comment:12 question] (added emphasis):

First, please apply my updated de.po, so that we can close this issue. IMHO unpublished commits and your latest state do not belong in this issue. Is that okay with you?

wzdev-ci commented 5 years ago

alfred007 commented

To bring the complete discussion together in this ticket I will do the following: I implement all suggestions of Forgon and me into a new de.po file. Where Forgon and I disagree I will add a comment with an explanation why we disagree. This way we will have all suggestions of Forgon and me in one de.po file and we can discuss every single line here, if necessary. Because that takes a little bit more time it could be that I attach the changed file at the 30th of December instead of the 28th or 29th as originally announced.

wzdev-ci commented 5 years ago

Kreuvf commented

No need to hurry, I will not be able to work on this before next year anyway. Also, this does not change my objection to only adding in changes from my patch that Forgon agreed with. As I said before, that's not how I like to handle these things.

I prefer leveraging the powers of Git which would allow me to see exactly what has changed and who changed it. As long as only alfred007 and me worked on the file, everything was fine. With more than two people ~simultaneously working on the file, some sort of tracking is needed.

Still, I insist on applying the patch as is (or discussing) without mixing in anything else first. Everything after that must be based on the then-current de.po and I am open to discussing any new changes.

wzdev-ci commented 5 years ago

alfred007 commented

No problem. I can wait until your patch becomes the next master version. Even if it looks a little bit confusing and "suboptimal" at the moment, the ideas of Forgon are really helpful.

wzdev-ci commented 5 years ago

alfred007 commented

@Forgon Can you please push the patch from Kreuvf to master so that we can move on?

wzdev-ci commented 5 years ago

Steven Koenig kreuvf@... changed status from assigned to closed

wzdev-ci commented 5 years ago

Steven Koenig kreuvf@... changed resolution from ` tofixed`

wzdev-ci commented 5 years ago

Steven Koenig kreuvf@... commented

In https://github.com/Warzone2100/warzone2100/commit/d6baee2b23f29dd65b9178a1d2952484723b5f9c:

#CommitTicketReference repository="" revision="d6baee2b23f29dd65b9178a1d2952484723b5f9c"
Update German translation

Fixes #4845
wzdev-ci commented 5 years ago

Forgon changed status from closed to reopened

wzdev-ci commented 5 years ago

Forgon changed resolution from fixed to ``

wzdev-ci commented 5 years ago

Forgon commented

Replying to [comment:5 alfred007]:

I noticed that the spoken translation often differs from the written. [...] Should we adapt the written translation to the spoken or not?

If it's just a matter of work, I can do it.

No.

Spoken words and printed messages can differ for good reasons:

Adapting the German translation to German sequences is a further complication added to the requirements of understanding the English sequences, their context in the game and the meaning conveyed in their subtitles.

For example, in the German video "cam1/cam1dp1.ogg" this spoken text differs:

The German sequences, available at http://files.warzone2100.de/index.php in a compressed and uncompressed edition (username: warzone2100.de, password: ghostintheshell), are of such poor quality that they should not be installed.

The following tracks are untranslated despite containing English voices:

Audio quality is terrible. Voices appear to be robotic, despite campaign protagonists being human. The last update was in 2009, despite the spoken text containing many errors, some of which are categorized and listed below:

Grammar:

Pronunciation:

Vocabulary:

wzdev-ci commented 5 years ago

Forgon commented

Replying to [comment:18 alfred007]:

@Forgon Can you please push the patch from Kreuvf to master so that we can move on? Done.

wzdev-ci commented 5 years ago

Forgon commented

Replying to [comment:14 Kreuvf]:

Let me quickly explain how these things usually went:

  1. make -Cpo update-po (iirc) in the po directory, results committed.
  2. Local update of the po file.
  3. New ticket with patch or full po file.

Personally, I could work with that just fine as everything was either in git or in Trac and could be traced back easily. Nobody ever told me of any changes to this workflow.

Replying to [comment:13 Forgon]:

[...] changes from your patch that I agreed with [...]

That is exactly the reason why I object to this intransparent workflow. If you do not mind, I have no problem putting stuff in a branch on GitHub and making a PR, so that everybody can comment on every single line before merging. From what you are writing I am under the impression that it will not be as easy for me to see exactly what changed, not even talking about discussing single points.

The de.po patch should apply cleanly to 5807d38b51120e8782609f3b28d348624647f306. Please just push that to master and I am open to anything that comes on top of these changes.

Also, please answer my [comment:12 question] (added emphasis):

First, please apply my updated de.po, so that we can close this issue. IMHO unpublished commits and your latest state do not belong in this issue. Is that okay with you? I do not object to your workflow.

The current situation developed because I had improved translator comments in my local repository. While doing so, I checked the German PO file to find out what had been misunderstood by translators and thus needed to be explained, in the course of which I detected and corrected many errors in it. Knowing that alfred007 was working on a German translation, I was concerned about him missing out on these improvements and contacted him via PM. A productive exchange ensued. Alfred007 has found many mistakes in my PO file and prevented some of my bad ideas (like translating vehicle bodies) from needing to be discussed. I hardly explained any of my suggestions, so that I am grateful that he nonetheless worked with them.

Since your patch has been pushed to master and alfred007 is going to create a new patch that incorporates my ideas, we can follow your usual procedure now.

wzdev-ci commented 5 years ago

alfred007 commented

I finished my work with the de.po-file and attach it here for discussion. Reference is the de.po-file in master version d6baee2

wzdev-ci commented 5 years ago

alfred007 uploaded file de.po (436.4 KiB)

wzdev-ci commented 5 years ago

Forgon uploaded file de2.po (436.5 KiB)

updated version of German PO file from alfred007

wzdev-ci commented 5 years ago

Forgon commented

The PO file of afred007 contains both my extracted comments and translator comments, which are often mixed up. Any comments that begin with the string 'TRANSLATORS: ' should be removed before committing the file, but left in for the moment to help Kreuvf understand the changes made.

Further comments by alfred007 explain remaining disagreements, to be decided by Kreuvf.

My updated version of alfred007's PO file, named "de2.po", contains additional changes, which are listed and explained below:

msgid "Data from the Collective's base indicates the presence of the NEXUS intruder program."
< msgstr "Daten aus der Basis des Kollektivs deuten auf die Anwesenheit des NEXUS-Eindringlingsprogramm hin."
> msgstr "Daten aus der Basis des Kollektivs deuten auf die Anwesenheit des NEXUS-Eindringlingsprogramms hin."
msgid "TRANSPORT MISSION: Ambush NEXUS Forces"
< msgstr "TRANSPORTERMISSION: NEXUS Truppen aus dem Hinterhalt angreifen"
> msgstr "TRANSPORTERMISSION: NEXUS-Truppen aus dem Hinterhalt angreifen"
msgid "Kill Selected Unit(s)"
< msgstr "Gewählte Einheit(en) vernichten"
> msgstr "Ausgewählte Einheit(en) vernichten"

If "Turtle AI" is not translated, neither should "Hover AI":

msgid "Hover AI"
< msgstr "Hover KI"
> msgid "Hover AI"

Challenge names should be translated, and if "Two-faced" is not, neither should the others:

msgid "Two-faced"
< msgstr "Two-faced"
> msgstr "Doppelseitig"

In the campaign, Archangel Missiles and the campaign-specific Angel Missiles do currently not home in on their targets. Ticket #4850 contains a patch to change this behavior. If it is committed, in the following translations "Rakete" needs to be changed to "Lenkrakete":

# Missile nicht mit Lenkrakete übersetzt, weil die Waffe nicht zielsuchend ist
msgid "Angel Missile"
msgstr "Angel-Rakete"

# Missile nicht mit Lenkrakete übersetzt, weil die Waffe nicht zielsuchend ist
msgid "Angel Missile Battery"
msgstr "Angel-Raketenbatterie"

# Missile nicht mit Lenkrakete übersetzt, weil die Waffe nicht zielsuchend ist
msgid "Angel Missile Emplacement"
msgstr "Stellung mit Angel-Raketen"
wzdev-ci commented 5 years ago

alfred007 commented

I overlooked that the "Turtle AI" wasn't translated to "Turtle KI". Meaning that names don't get translated belonged only to the translation of "Turtle" to "Defensive". We should use the more common abbreviation "KI" for the German translation. So I suggest the translations "Hover KI" and "Turtle KI".

I agree with Forgon that we should translate all challenges or none. My fault. Basing on his Translators comment I suggest the translation "Von zwei Seiten" or "In der Zange" to describe that the player gets attacked from two sides even though my translation is not the literal one.

His additional changes are correct, I overlooked that.

wzdev-ci commented 5 years ago

Kreuvf commented

Replying to [comment:20 Forgon]:

Replying to [comment:5 alfred007]:

I noticed that the spoken translation often differs from the written. [...] Should we adapt the written translation to the spoken or not?

If it's just a matter of work, I can do it.

No.

I second that, do not adapt the texts.

My general policy is to keep things as close to the original Warzone 2100 as possible.

The German sequences, available at http://files.warzone2100.de/index.php in a compressed and uncompressed edition (username: warzone2100.de, password: ghostintheshell), are of such poor quality that they should not be installed.

IIRC, the German sequences were upscaled from the original German sequences I had on CD. Also IIRC: The problem with the German sequences and also the reason why you cannot just take the German audio track and mix it with the English sequences is that the German sequences sometimes use freeze-frames to have more video time for the (longer) German audio.

The following tracks are untranslated despite containing English voices:

  • "cam2/cam2int1.ogg"
  • "cam2/cam2int2.ogg"
  • "cam3/cam3int.ogg"

Do people encounter these during a playthrough? Maybe they are just left-overs.

Audio quality is terrible.

I wouldn't call that terrible ;) It was 1999, don't forget that. Also, the low audio quality might be an artifact introduced during conversion.

Voices appear to be robotic, despite campaign protagonists being human.

That's just how people will talk in 2100. ;)

The last update was in 2009, despite the spoken text containing many errors, some of which are categorized and listed below:

So, am I seeing this correctly? You are shifting things from de.po to de-audio in the de-sequences? IMHO that deserves to go in its own ticket.

Grammar:

  • in "cam1/map1cexp.ogg":

    • untranslated: "Verhöre von gefangenen Scavenger haben ergeben, dass das New Paradigm in diesem Sektor aktiv ist".

    "Scavenger" instead of "Scavengern"

  • in "cam1/sub1_1.ogg": untranslated: "Aufklärungsflüge durch den Transporter haben zahlreiche Ruinen aus der Zeit vor dem Kollaps entdeckt."

    "Aufklärungsflüge" is no proper noun, hence this sentence is wrong

Pronunciation:

  • in "cam1/c001.ogg":

    • msgid "Good luck and good hunting."

    msgstr "Viel Glück und Waidmannsheil."

    "Waidmannsheil" pronounced as "Waidmannheil"

    • msgid "Approaching Landing Zone. Team Alpha Briefing commences."

    msgstr "Wir nähern uns der Landezone. Missionsbesprechung für Team Alpha beginnt."

    "nähern" pronounced as "nähren"

  • in "cam1/cam1out2.ogg":

    • msgid "Let me meld with your machines and cyborgs."

    msgstr "Lasst mich mit Euren Maschinen und Cyborgs verschmelzen."

    "Cyborgs" pronounced "Cybörgs"

    • msgid "Open your systems to me and you will be strong."

    msgstr "Öffnet Eure Systeme für mich und Ihr werdet stark sein."

    "stark" propounced with a short vowel instead of long one

  • in "cam1/map1a_c.ogg":

    • msgid "The synaptic link allows for almost instantaneous transfer of thought from human operators to vehicle control and guidance systems. The synaptic link is fitted into the base of the skull circling the spinal column."

    msgstr "Die synaptische Verbindung erlaubt die beinahe verzögerungsfreie Übertragung von Gedanken eines menschlichen Bedieners an die Steuersysteme eines Fahrzeugs. Die synaptische Verbindung wird zwischen Schädelbasis und Wirbelsäule angebracht."

    "verzögerungsfreie" pronounced as "verzögerungsfrei"

    • msgid "The synaptic link allowed soldiers to be placed in power suits that they controlled as easily as their own bodies. Power suits allowed infantry to function effectively on the battlefields of the 21st Century."

    msgstr "Die synaptische Verbindung ermöglichte es Soldaten in Kraftanzüge zu stecken, die sie so einfach wie ihre eigenen Körper bewegen konnten. Kraftanzüge ermöglichten ein effektives Funktionieren der Infanterie auf den Schlachtfeldern des 21. Jahrhunderts."

    "Die synaptische Verbindung ermöglichte es Soldaten in Kraftanzüge zu stecken, die sie so einfach wie ihre eigenen Körper bewegen konnten. [...]"

    "Kraftanzüge" pronounced as "Kraftanzügen"

  • in "cam1/sub1_1.ogg" and "transport.ogg":

    • msgid "On landing, explore the ruins and recover any artifacts."

    msgstr "Erkunden Sie nach der Landung die Ruinen und bergen Sie jegliche Artefakte."

    "Erkunden Sie nach der Landung die Ruinen und bergen Sie alle Artefakte in der näheren Umgebung"

    "Artefakte" stressed on first syllable instead of third

  • in "cam1/sub13bet.ogg":

    • untranslated: "Unsere Erkundungsteams haben einige Artefakte bergen können."

    "Artefakte" stressed on first syllable instead of third

  • in "cam1/sub13gam.ogg":

    • untranslated: "Wir haben weder Artefakte gefunden noch ..."

    "Artefakte" stressed on first syllable instead of third

  • in "cam1/sub1_4b.ogg":

    • msgid "Destroy the base and recover any artifacts present."

    msgstr "Zerstören Sie die Basis und bergen Sie alle vorhandenen Artefakte."

    "Zerstören Sie die Basis des New Paradigm und bergen Sie alle vorhandenen Artefakte."

    "Artefakte" stressed on first syllable instead of third

  • in "cam1/sub1_5.ogg":

    • untranslated: "Dieses Artefakt muss unter allen Umständen geborgen werden."

    "Artefakt" stressed on first syllable instead of third

  • in "cam1/sub1_5pl.ogg":

    • msgid "Information discovered at the previous enemy base indicates that the New Paradigm recovered two synaptic link artifacts."

    msgstr "In der letzten feindlichen Basis entdeckte Informationen haben ergeben, dass das New Paradigm zwei Artefakte der synaptischen Verbindung geborgen hat."

    "Artefakte" stressed on first syllable instead of third

  • in "cam1/sub1_7b.ogg":

    • untranslated: "Das New Paradigm hat ein wichtiges Artefakt geborgen."

    "Artefakt" stressed on first syllable instead of third

  • in "cam2/cam2_5pl.ogg":

    • untranslated: "Commander, wir können jetzt VTOLs bauen."

    "VTOLs" pronounced as "V-T-O-Ls" instead of "V-tols"

  • in "cam2/cam2b.ogg":

    • untranslated: "Commander, wir orten Luft- und Bodenstreitkräfte die sich von Norden her nähern."

    "nähern" pronounced as "nähren"

  • in "cam2/cam2ca.ogg":

    • msgid "Analysis of flight paths indicate that The Collective's VTOLs originate from here."

    msgstr "Die Analyse der Flugbahnen zeigt, dass die VTOLs des Kollektivs von hier starten."

    "Die Analyse der Flugmuster legt nahe, dass die VTOLs in dieser Region starten"

    "VTOLs" pronounced as "V-T-O-Ls" instead of "V-tols"

    • msgid "Eradicate all Collective forces and recover all artifacts."

    msgstr "Vernichten Sie alle Truppen des Kollektivs und bergen Sie alle Artefakte."

    "Löschen Sie die Streitkräfte des Kollektivs aus und bergen Sie vorhandene Artefakte."

    "Artefakte" stressed on first syllable instead of third

  • in "cam2/cam2capl.ogg":

    • untranslated: "Es ist wichtig, dass Sie die VTOL-Technologie so schnell wie möglich bergen."

    "VTOL" pronounced as "V-T-O-L"

  • in "cam2/cam32a2.ogg":

    • msgid "Enemy strike VTOLs have got us pinned down. We've managed to hold off cyborgs and tanks, but we haven't been able to make any progress along the valley."

    msgstr "Feindliche VTOLs nageln uns am Boden fest. Wir konnten die Cyborgs und Panzer zurückschlagen, kommen aber entlang des Tals nicht vorwärts."

    "Feindliche VTOLs nageln uns am Boden fest. Wir konnten die Cyborgs und Panzer zurückschlagen, kommen aber im Tal nicht vorwärts."

    "VTOLs" pronounced as "V-T-O-Ls" instead of "V-tols"

  • in "cam3/cam32alp.ogg":

    • msgid "We are under heavy attack from cyborgs, laser tanks, and strike VTOLs."

    msgstr "Wir liegen unter heftigem Beschuss durch Cyborgs, Laserpanzer und VTOLs."

    "VTOLs" pronounced as "V-T-O-Ls" instead of "V-tols"

  • in "cam3/cam3_cn.ogg":

    • msgid "Commander, you're proving to be more resilient than I thought."

    msgstr "Commander, Sie erweisen sich als hartnäckiger als ich angenommen habe."

    "als" is not pronounced

Vocabulary:

  • in "cam1/cam1ascv.ogg" and "fastplay.ogg":

    • msgid "Scavenger raiders are approaching our base."

    msgstr "Scavenger-Überfalltrupps nähern sich unserer Basis."

    "Überfallkommandos der Scavengers nähern sich unserer Basis."

    "Scavengers" instead of "Scavenger"

    • msgid "Defend the base then destroy the Scavenger camps."

    msgstr "Verteidigen Sie die Basis, zerstören Sie dann die Scavenger-Lager."

    "Verteidigen Sie die Basis, zerstören Sie dann die Lager der Scavengers."

    "Scavengers" instead of "Scavenger"

  • in "cam1/cam1ccom.ogg":

    • untranslated: "Kommandoturm verfügbar"

    "Kommandoturm" instead of "Commanderturm"

    • msgid "Commander, we have recovered a command turret from the New Paradigm."

    msgstr "Commander, wir haben einen Commanderturm des New Paradigm erbeutet."

    "Commander, wir haben einen Kommandoturm des New Paradigm erbeutet."

    "Kommandoturm" instead of "Commanderturm"

  • in "cam1/sub1_1.ogg" and "transport.ogg":

    • msgid "Load an attack force into the transport."

    msgstr "Verladen Sie einen Angriffstrupp in den Transporter."

    "Laden Sie eine Angriffstruppe in den Transporter."

    "eine Angriffstruppe" instead of "einen Angriffstrupp"

  • in "cam1/sub1_2.ogg":

    • untranslated: "Aufklärungsberichte zeigen, dass die in dieser Region operierenden Scavengers technologisch fortgeschrittener sind als die bisherigen."

    "Scavengers" instead of "Scavenger"

  • in "cam1/sub1_3.ogg":

    • msgid "Take a scout force to investigate these signals."

    msgstr "Untersuchen Sie dieses Signal mit einem Spähtrupp."

    "Verwenden Sie einen Kundschaftertrupp, um die Herkunft dieser Signale zu erforschen."

    "Kundschaftertrupp" instead of "Spähtrupp"

  • in "cam2/cam2_2.ogg":

    • msgid "An enemy commander is collecting a shipment from NEXUS at this location."

    msgstr "Ein feindlicher Commander sammelt eine Lieferung von NEXUS an dieser Position ein."

    "Informationen aus der Basis des Kollektivs deuten darauf hin, dass ein feindlicher Gefechtsführer eine Lieferung an Nexus an dieser Stelle einsammelt".

    "Gefechtsführer" instead of "Commander"

  • in "cam2/cam2ca.ogg":

    • msgid "Analysis of flight paths indicate that The Collective's VTOLs originate from here."

    msgstr "Die Analyse der Flugbahnen zeigt, dass die VTOLs des Kollektivs von hier starten."

    "Die Analyse der Flugmuster legt nahe, dass die VTOLs in dieser Region starten"

    "Flugmuster" instead of "Flugbahnen"

  • in "cam3/cam3intp.ogg":

    • untranslated: "Sie müssen NEXUS besiegen, bevor er erneut seine Mächte einsetzen kann."

    "Mächte" instead of "Kräfte"

I cannot do anything about this, it's the original German audio. Please move this to a new ticket for further discussion.

wzdev-ci commented 5 years ago

Kreuvf commented

Replying to [comment:22 Forgon]:

I do not object to your workflow.

Thank you. <3

The current situation developed because I had improved translator comments in my local repository. While doing so, I checked the German PO file to find out what had been misunderstood by translators and thus needed to be explained, in the course of which I detected and corrected many errors in it.

So, it seems to me that this would probably be best put into every po file at generation time. This can be achieved by using translator comments.

Knowing that alfred007 was working on a German translation, I was concerned about him missing out on these improvements and contacted him via PM. A productive exchange ensued. Alfred007 has found many mistakes in my PO file and prevented some of my bad ideas (like translating vehicle bodies) from needing to be discussed. I hardly explained any of my suggestions, so that I am grateful that he nonetheless worked with them.

One question: Are you, Forgon, a native German speaker?

Since your patch has been pushed to master and alfred007 is going to create a new patch that incorporates my ideas, we can follow your usual procedure now.

Thank you very much, both of you. :)

wzdev-ci commented 5 years ago

Kreuvf commented

Replying to [comment:24 Forgon]:

My updated version of alfred007's PO file, named "de2.po", contains additional changes, which are listed and explained below:

msgid "Data from the Collective's base indicates the presence of the NEXUS intruder program."
< msgstr "Daten aus der Basis des Kollektivs deuten auf die Anwesenheit des NEXUS-Eindringlingsprogramm hin."
> msgstr "Daten aus der Basis des Kollektivs deuten auf die Anwesenheit des NEXUS-Eindringlingsprogramms hin."
msgid "TRANSPORT MISSION: Ambush NEXUS Forces"
< msgstr "TRANSPORTERMISSION: NEXUS Truppen aus dem Hinterhalt angreifen"
> msgstr "TRANSPORTERMISSION: NEXUS-Truppen aus dem Hinterhalt angreifen"
msgid "Kill Selected Unit(s)"
< msgstr "Gewählte Einheit(en) vernichten"
> msgstr "Ausgewählte Einheit(en) vernichten"

If "Turtle AI" is not translated, neither should "Hover AI":

msgid "Hover AI"
< msgstr "Hover KI"
> msgid "Hover AI"

Challenge names should be translated, and if "Two-faced" is not, neither should the others:

  • "Back to Basics"
  • "Hide Behind Me"
  • "No Place to Hide"
msgid "Two-faced"
< msgstr "Two-faced"
> msgstr "Doppelseitig"

In the campaign, Archangel Missiles and the campaign-specific Angel Missiles do currently not home in on their targets. Ticket #4850 contains a patch to change this behavior. If it is committed, in the following translations "Rakete" needs to be changed to "Lenkrakete":

# Missile nicht mit Lenkrakete übersetzt, weil die Waffe nicht zielsuchend ist
msgid "Angel Missile"
msgstr "Angel-Rakete"

# Missile nicht mit Lenkrakete übersetzt, weil die Waffe nicht zielsuchend ist
msgid "Angel Missile Battery"
msgstr "Angel-Raketenbatterie"

# Missile nicht mit Lenkrakete übersetzt, weil die Waffe nicht zielsuchend ist
msgid "Angel Missile Emplacement"
msgstr "Stellung mit Angel-Raketen"

Is this list exhaustive?

wzdev-ci commented 5 years ago

Forgon commented

Replying to [comment:26 Kreuvf]:

Replying to [comment:20 Forgon]:

Replying to [comment:5 alfred007]:

I noticed that the spoken translation often differs from the written. [...] Should we adapt the written translation to the spoken or not?

If it's just a matter of work, I can do it.

No.

I second that, do not adapt the texts.

My general policy is to keep things as close to the original Warzone 2100 as possible.

The German sequences, available at http://files.warzone2100.de/index.php in a compressed and uncompressed edition (username: warzone2100.de, password: ghostintheshell), are of such poor quality that they should not be installed.

IIRC, the German sequences were upscaled from the original German sequences I had on CD. Also IIRC: The problem with the German sequences and also the reason why you cannot just take the German audio track and mix it with the English sequences is that the German sequences sometimes use freeze-frames to have more video time for the (longer) German audio.

The following tracks are untranslated despite containing English voices:

  • "cam2/cam2int1.ogg"
  • "cam2/cam2int2.ogg"
  • "cam3/cam3int.ogg"

Do people encounter these during a playthrough? Maybe they are just left-overs.

Audio quality is terrible.

I wouldn't call that terrible ;) It was 1999, don't forget that. Also, the low audio quality might be an artifact introduced during conversion.

Voices appear to be robotic, despite campaign protagonists being human.

That's just how people will talk in 2100. ;)

The last update was in 2009, despite the spoken text containing many errors, some of which are categorized and listed below:

So, am I seeing this correctly? You are shifting things from de.po to de-audio in the de-sequences? IMHO that deserves to go in its own ticket.

[...] I cannot do anything about this, it's the original German audio. Please move this to a new ticket for further discussion. I have created ticket #4851 to discuss problems in German sequences, but will not fix any of them.

wzdev-ci commented 5 years ago

Forgon commented

Replying to [comment:28 Kreuvf]:

Replying to [comment:24 Forgon]:

My updated version of alfred007's PO file, named "de2.po", contains additional changes, which are listed and explained below: [...]

Is this list exhaustive? Yes.

wzdev-ci commented 5 years ago

alfred007 commented

Replying to [comment:29 Forgon]:

Replying to [comment:26 Kreuvf]:

Replying to [comment:20 Forgon]:

Replying to [comment:5 alfred007]:

I noticed that the spoken translation often differs from the written. [...] Should we adapt the written translation to the spoken or not?

If it's just a matter of work, I can do it.

No.

I second that, do not adapt the texts.

Neither I did, nor will I do.

wzdev-ci commented 5 years ago

Kreuvf commented

So, since Trac thinks my reply is spam, I cannot post it here. Great ticket system!

Here is the comment: https://pastebin.com/raw/HBPi5Rnx.

I'll attach three patches (to be applied consecutively):

  1. Accepted changes.
  2. Rejected/undecided changes and in-file comments. (Most comments should be made available to all translations by adding them at the appropriate place using gettext means.)
  3. FLAK -> Flak.
wzdev-ci commented 5 years ago

Kreuvf uploaded file de.po-4845-00-accepted.patch (107.1 KiB)

Accepted changes to de.po@b1d63b86fd6be7d904a291a48ef6a56a078e93b3

wzdev-ci commented 5 years ago

Kreuvf uploaded file de.po-4845-01-rejected.patch (94.3 KiB)

Rejected and undecided changes, comments for de.po@b1d63b86fd6be7d904a291a48ef6a56a078e93b3

wzdev-ci commented 5 years ago

Kreuvf uploaded file de.po-4845-02-FLAKFlak.patch (5.1 KiB)

FLAK -> Flak for de.po@b1d63b86fd6be7d904a291a48ef6a56a078e93b3

wzdev-ci commented 5 years ago

alfred007 commented

I think to move forward with our work we should now push the accepted changes and the "FLAKFlak" changes to master and then discuss the undecided changes. I suggest not to discuss more than three changes at the same time so that we don't get confused. I start the discussion with the following three undecided changes and include the comments of Kreuvf.

: data/base/messages/strings/cam2strings.txt:116

: data/base/messages/strings/cam2strings.txt:121

msgid "TRANSPORT MISSION: Satellite Uplink Site" msgstr "TRANSPORTERMISSION: [-Satellitenkontrollzentrum"-]{+Satelliten-Uplink-Station"+}

This is one of these translations that might be ~15 year old work of mine or original translations. I'd like to avoid "Uplink" in the translation, so how about "Satellitenkontrollanlage" or "Satellitenverbindungsanlage"?

I like "Satellitenverbindungsanlage"

{+# TRANSLATORS: The safe haven is a place of retreat for a new base (Kommentar von Forgon) -alfred007+}

: data/base/messages/strings/cam2strings.txt:131

: data/base/messages/strings/cam2strings.txt:136

msgid "TRANSPORT MISSION: Establish Safe Haven" msgstr "TRANSPORTERMISSION: [-Sicherheitszone-]{+Rückzugsbasis+} einrichten"

: data/base/messages/strings/cam2strings.txt:133

msgid "You are to establish a safe haven for evacuation of Beta Base." msgstr "Sie müssen eine [-Sicherheitszone-]{+Rückzugsbasis+} zur Evakuierung der Betabasis einrichten."

: data/base/messages/strings/cam2strings.txt:138

msgid "Once a safe haven is established, return to the LZ for further orders." msgstr "Sobald eine [-Sicherheitszone-]{+Rückzugsbasis+} eingerichtet ist, kehren Sie für weitere Instruktionen zur Landezone zurück."

Why not just "Sicheren Hafen einrichten"?

If you have a look at what the player is doing in the game he is neither establishing a "Rückzugsbasis" nor a "Sicheren Hafen". All he is doing is destroying the AA structures around his base. And this is for me more establishing a "Sicherheitszone". So I plead not to change the translation.

{+# Forgon will das "Blaster" unübersetzt lassen, ich bin für die übersetzte Variante -alfred007+}

: data/base/messages/strings/names.txt:287

: data/mp/messages/strings/names.txt:370

msgid "Bunker Blaster Cyborg" msgstr "Bunkersprenger"

There is no weapon "Bunker Blaster". I tried to name Cyborgs according to their use and this is >one of these names. I would like to keep this name. Actually, that seems like a remnant from >1.11? I wonder why these names are still in there o.O

As I wrote in my comment, I'm for the translated name.

@Forgon Is your German good enough that we can do this discussion in German?