🇩🇪German Translators - Post your questions for other German Translators here

If you have a question for other German translators, please post your question here.

If you have a question for Discogs staff that isn't answered in this Translation Help Doc, please post it here.

If your question is about a specific string in Transifex, and needs to be answered by Discogs staff, please post a comment within Transifex. Here is an explanation of how to ask a question about a string from within Transifex.

Thanks for being part of the Discogs Community Translation Team!

Just one question: It is an obligatory aspect of German language to differentiate between formal and informal address ("sie" and "du", respectively), a feature that is not used in modern English anymore ("you" vs. "thou").
In German, both the formal and the informal address have become pretty much common in any field of business as well as customer communication - while more traditional companies seem to stick to the formal address, others (like IKEA, facebook) use the informal "du" form.
How are we supposed to handle this in the process of translating to German? I have seen examples of both forms among the translated strings on transifex

Lars

Hi no_noise_reduction,

Great question! I haven't added specifics about this in our this Translation Help Doc, but perhaps I should add further guidance there.

We have discussed this in the past with another translator when we were accepting translations via GitHub. After completing some research, we decided that we would use "sie".

I just added a section in the Translation Help Document about what to do if you notice an incorrect translation.

Thanks for bringing this issue to my attention! Please let us know if there is anything else I can assist with.

You wish this issue of correct addressing was a German-related one of its own! :-)
Consequently though, it will also come up with most of the Romance language versions of the site in no time.
Spanish uses "usted" as formal address, French uses "vous" and Italian uses 3rd person singular plus "Lei" with capital L (may often be omitted). In French, addressing the with "tu" on a site of worldwide renown like Discogs would be considered plainly RUDE! (same thing on auction sites) Obviously, this is not a site that offers something like e. g. games for younger people...
Furthermore, in Japanese, the even expects to be addressed with the -san suffix when an alias name is used.

Thanks for the , pianoman74! You're right, I'm sure this question will continue to come up, so it would probably be best to address this in the Translation Help Document. I'll update that document ASAP.

Here is the update to the Translation Help Document.

Weetzie
so it would probably be best to address this in the Translation Help Document.

Or otherwise, could you please consider creating a generic discussion thread in this group which addresses issues across languages?
Since this addressing issue is not exclusive to German language, so...

pianoman74
could you please consider creating a generic discussion thread in this group which addresses issues across languages?

Sure! Is this what you were thinking: http://www.discogs.sie.com/groups/topic/394990

Exactly! Thanks for agreeing to do it.

After completing my first translation strings for the project, I came to realize that Discogs uses a lot of English 'technical' which in my opinion should be left unaltered in the process of translation.
These are like 'key release', 'master release', or 'release ID', which would obviously become less comprehensible if they were translated to German directly ('Schlüssel-Veröffentlichung', 'Hauptveröffentlichung' or 'Veröffentlichungs-ID').
Other have German equivalents but these have become or are gradually becoming obsolete: 'label', 'tracklist', 'limited edition', 'sleeve', or 'cover' ('Verlag', 'Titelliste', 'Limitierte Auflage', 'Hülle'). This means they will not only be understood by every German native speaker without being translated but in many cases sound even more natural to them.

I suggest that, at this early stage, we should agree on a list of that are to remain English in order to provide fluent and consistent translation strings.

L.F.

List of that I think should not be translated:
master release (Master Release)
key release (Key Release)
release ID (Release ID)
label (Label)
cover (Cover)

that could be translated but don't really have to since they have already entered or are in the process of entering recent German:
tracklist (Tracklist/Trackliste)
limited edition (Limited Edition -> Limitierte Auflage)
sleeve (Sleeve ->Cover, Germ. 'Hülle')
changelog (Changelog)
to post (->posten)
tag/tags (Tag/Tags)
community (Community)
link (Link->'Verknüpfung')

that I feel need to be discussed:
abbreviations like ANV could be explained/translated in the glossary
marketplace
review (Rezension, Besprechung?)
media (Tonträger, Medium?)

Feel free to add anything to this list!

no_noise_reduction
master release (Master Release)
key release (Key Release)
release ID (Release ID)
label (Label)
cover (Cover)

agreed, however I personally would "Germanify" (yes, that apparently is an actual word in the English language :-D) them in order to avoid the so called "Deppenapostroph": , e.g. "Key-Release", "Release-ID" etc.

tracklist (Tracklist/Trackliste)
I'd tend to use "Trackliste", as I feel that's the most common variant out there (it's even present in the Duden)[/quote]

limited edition (Limited Edition -> Limitierte Auflage)
hard to decide, but I think I'd go with "Limitierte Auflage". That term has been around for ages, while I feel like "Limited Edition" has only recently "introduced" to the general masses in .

sleeve (Sleeve ->Cover, Germ. 'Hülle')
+1 for "Cover". My experience shows, that when people say "Hülle" they often refer to the packaging (e.g. the jewel case).
"Cover" is used for the

changelog (Changelog)
Changelog is a rather technical term – I doubt most "common s" know what it means. I think "Liste der Änderungen" might be a better compromise.

to post (->posten)
tag/tags (Tag/Tags)
community (Community)
link (Link->'Verknüpfung')

I think we can use the English words for these.

On another note: not that I would have any problem with writing in English, but wouldn't it be easier to continue this topic in German?

Hallo pano9000,

Deinen Ausführungen stimme ich zu. Danke für Deine Mühen : ). Auf gute Zusammenarbeit!

Lars

Ein paar weitere Worte, die man einheitlich übersetzen sollte:

Logged in
"angemeldet" oder "eingeloggt"?

Bsp.: You have to be loggin in to do xyz.
Sie müssen angemeldet/eingeloggt sein, um xyz zu tun.
Ich persönlich würde zu "angemeldet" tendieren.

(im Sinne von " ")
"" oder "Konto"?
Würde hier für "Konto" stimmen.

Nach langer Zeit mal wieder an einer Übersetzung arbeiten, fühlt sich gut an :-D
(Hatte davor bei einigen Open-Source-Programmen mitgeholfen)

Gruß,

pano

Ich stimme Dir voll zu! "Angemeldet" und Konto finde ich besser als "eingeloggt" und "".

Im Augenblick benutze ich die Wörter "Einträge" und "Beiträge" synonym für "submissions". Hat da jemand eine Präferenz?

no_noise_reduction
review (Rezension, Besprechung?)

"Rezension".

Erst einmal sind das alles Kommentare.
Dann kann man ein Kästchen anklicken, in dem stehen sollte "Mein Kommentar ist eine Rezension" (orig. my comment is a review)
"Besprechung" klingt so nach Büro-Jargon ;-)

Key Release
Wirklich knifflig. ("Schlüssel-Veröffentlichung" *schock*). Nein, aber man könnte es als "Standard-Release" bezeichnen. Ist zwar auch noch englisch, aber wirkt nicht mehr so fremd..."Standard" im Sinne, dass es standardmäßig (IT-Newspeak: "defaultmäßig") angezeigt wird und - z. B. für das früheste VÖ-Datum - maßgebend ist.
Bei Menschen würde man "stellvertretend" sagen. Wird nämlich statt des ganzen MR stellvertretend für alle im MR befindlichen Releases angezeigt.

Richtig, aber ein "review" ist ja nicht das selbe wie ein Kommentar. Was das Wort "Besprechungen" angeht, gebe ich dir recht - allerdings klingt auch das etwas endere "Rezension" noch etwas holprig. Das Wort "review" ist nach meinem Erachten im Deutschen noch nicht so richtig angekommen, eins zu eins übernehmen kann man also auch nicht.

Dann nimm Rezension. Quasi jeder kennt Amazon, und da heißt das seit knapp 20 Jahren so. Für "holprig" halte ich es überhaupt nicht (YMMV).

okay, dann bleibts bei Rezension. Das mit dem "Standard-Release" ist eine gute Idee, obwohl ich denke, dass eine gewisse Menge an Anglizismen den Discogs-Nutzern nicht weh tun wird. Ich denke, dass wir "Standard-Release" übernehmen könnten.

Gibt es eine Meinung zur Übersetzung von "order page"?

Ja, sobald ich einen Link habe. Muss die Seite sehen für die richtige Übersetzung.

Wegen "Key-Release":

Wie wär's mit "Haupt-Release" als Alternative zu "Standard-Release"?

"Standard-Release" liest sich so, als wäre es das Gegenteil von "Limited Edition".
Könnte dann vielleicht zu Verwirrungen führen.

In dem Punkt hast Du recht - allerdings klingt "Haupt-Release" als deutsch-englisches Mischkompositum auch irgendwie sperrig. Ich denke, dass es eine ideale Lösung vielleicht garnicht gibt. Vielleicht sollten wir abstimmen?
Key-Release
Standard-Release
Haupt-Release

Hi no_noise_reduction,

It's great to see all of this discussion and collaboration! Please let me know if I can help in any way.

Once you have decided on specific translations for certain Discogs-specific words, post a list here (you can always continue to add later). I can then add the translations to the German glossary, so all German translators see a reminder to translate the word in a consistent way. I can also make a note on certain words to leave them untranslated, if it's decided that certain words or acronyms should be left in English.

Here is an explanation of the Transifex Glossary feature.

So, for example, if you provide a list like this:

Limited Edition = Limitierte Auflage
Tag = Tags (leave untranslated / use English)
Tracklist = Trackliste

I can add the English and German translations to the German Transifex Glossary.

"Guidelines":

Sollten wir das als "Richtlinien" übersetzen?

Habe ich erstmal so gemacht. Hast Du einen anderen Vorschlag?

nein, "Richtlinien" t mMn gut, wollte mich nur rückversichern :-)

alles klar ;-)

Community ----> Gemeinschaft / Gemeinde
Order Page ----> Bestellseite
Guidelines ------> Richtlinien (stimme ich auch zu)
Tracklist -------> Trackliste (kann man eigentlich auch so stehen lassen) vielleicht Liederliste ?
Limited Edition ---> Limitierte Auflage (kann ich auch nur zustimmen)
Tag ----------------> Anhänger

Ne r3uZ. "Community" ist heutzutage schon im Jugend-Jargon angekommen, siehe TV "wir haben da auf Facebook eine Community gegründet" / "klinkt euch doch mal bei unserer Community ein".
'Gemeinde' klingt nach Pfarrer in der Kirche (Liebe Gemeinde, LOL). Und 'Gemeinschaft' zu formell.
Da würde ich 'Community' lassen.

Tracklist--->Trackliste (mit e am Ende, das Wort ist schon in Gebrauch unter DJs ("Hast du 'ne Trackliste davon?") - Weetzie schlägt das gleiche vor, hab ich gesehen)

Tag--->Schlagwort (?)
(in IT-Foren gibt's das oft, z. B. linux startup kernel panic, dass man durch solche Tags (Schlagworte) thematisch gleiche Threads und Problemberichte findet)

Something general: It could be helpful to create somthing like dummy s and dummy releases for translators in order to check string contexts. s that can not do anything "real" on Discogs but help us accessing areas that we could not get to using our own s.
I don't know whether something like this could be implemented easily but I thought I should at least make a suggestion.

no_noise_reduction
It could be helpful to create somthing like dummy s and dummy releases for translators in order to check string contexts.

That's a great idea! I'm not sure it would be possible for non-staff to access our testing environment, but I'll run the idea past our development team to see if it's feasible.

Can anyone help me with a quick translation question?

How can I best translate the following into German:

"Complete Your Record Collection
Get Started"

Does "So legen Sie los" work for "Get Started"?

Thanks in advance for any help!

Well, actually I would go for "Legen Sie los" only. "So legen Sie los" is an idiomatic translation which I felt sounds better in the given context (under " In"/translated back it would be something like "This is how you get started").
The entire string translates:
"Vervollständigen Sie Ihre Schallplattensammlung
Legen Sie los"

Thanks so much no_noise_reduction! We are starting to work on expanding our audience in , so you might see your translations on http://www.visions.de/ !

On visions.de they seem to use the less formal "du" form instead of "sie". you might want to consider that.

no_noise_reduction
On visions.de they seem to use the less formal "du" form instead of "sie". you might want to consider that.

Hmmm, that's a good point! What would the less formal translation be?

"Vervollständigen Du Ihre Schallplattensammlung
Legen Du los"

I'm thinking this isn't quite right, is it?

"Vervollständige Deine Plattensammlung
Lege direkt los"

Note that the "Du" pronoun is inherent in the verb "Lege" already. I added "direkt" because "Lege los" alone sounds a bit odd to my ears. "Lege direkt los" is a more casual translation for "Get started now". I think this should suit the inviting character of the source phrase.

Nice, thanks for the quick response! I'll send both translations along to our Marketing Manager, along with your explanation that the less formal version may be more appropriate. Thanks, no_noise_reduction! :)

Alternate translations: Leg gleich los!
or even: Fang jetzt gleich damit an!

BTW, should you favor the "Leg[e] direkt los", omit the -e from the 'Leg'. "Mach hin", "fang an", "komm her", "lass los" - there were old days when these imperative forms were considered "too informal", but today hardly anybody would say "Bitte fange an". Modern German now does tolerate this particular kind of elisions (this is the technical term from linguistics that describes this phenomenon).

I agree, pianoman74.

Besides, I don't feel too well with the "direkt", as it reminds me a bit too much of "Rheinisch" respectively Cologne dialect ("Kölsch") and their "treck" (at once, as the next action). "Fang treck ahn!", "Ich hann treck protestiert","hä hätt treck Jeld jewollt" :)

"...gleich..." sounds more Standard German to me.

So let's agree on "Leg' gleich los". :-)

Yes! That'll be perfectly fine. (even though you might omit the apostrophe, DUDEN too has been allowing this now for quite some time)

Thanks guys, I really appreciate your help! :)

Thanks, even though I am more much playing the role of a consultant than actually working on translations - sorry 'bout that. That's because I come from the programming world: I am much better in transforming old, non-working code to something real stunning than concocting something entirely from scratch (w/o knowing whether I'm on the right track). I need a kinda basis. :)

Hello German translators! We recently had to update some of our policies to make sure we were in-line with the updated Value-Added Tax (VAT) laws. I didn't think it was appropriate to ask our community to translated these policies, since I know that many community are frustrated with this change (believe me, we find the whole process frustrating and incredibly costly too) so we hired contractors to translate these help documents.

However, I've received reports that the German translations aren't entirely correct:

"VAT" translated into the German can mean "Mehrwertsteuer" or "Umsatzsteuer".
It seems you should use "Umsatzsteueridentifikationsnummer" instead of "Mehrwertsteueridentifikationsnummer", as the latter does not exist.
In the German tax system sellers pay "Umsatzsteuer" to the tax office and ask its aeqiuvalent "Mehrwertsteuer" from the customers."

I just wanted to check in with you guys before I make any updates. Does anyone have recommendations for how to improve these three documents?

http://www.discogs.sie.com/help/doc/Discogs-and-VAT?locale=de
http://www.discogs.sie.com/help/doc/vat-validation?locale=de
http://www.discogs.sie.com/help/doc/vat-identification-number?locale=de

Thanks for your !

I will look into the matter myself during the next 24 hours, but it appears that what you are describing makes sense. I think I used wikipedia and dict.cc to translate the string appropriately - I'm sorry should I have been the one who caused this confusion.

No worries, I'm honestly not sure what is best! Here is the current translation on the Seller Settings page:

Umsatzsteuer-Identifikationsnummer (UST-IdNr.)
Verkäufer aus der Europäischen Union sollten Ihre Umsatzsteuer-Identifikationsnummer hier eingeben. Lesen Sie mehr über die Mehrwehrtsteuerverpflichtung bei Discogs.

Whatever we decide is best, I'll try to update the help documents so that the language we use is consistent across the site.

Small typo: 'Ihre' must be written as 'ihre'. EU sellers are supposed to enter their own USt.-ID-Nr. not that of the reader (which need not necessarily be identical to the seller).
Or even better (= addressing the reader in a more direct way, current version reads a little too "ively" for my taste)

Wenn Sie ein Verkäufer aus der Europäischen Union sind, sollten Sie Ihre Umsatzsteuer-Identifikationsnummer hier eingeben.

saying: If YOU happen to be an EU seller, please do the following...
NOW the "Ihre" with capital I *IS* correct, as you're addressing the person directly. (formal "your" in plural, like French "votre", 2nd person). The "ihre" would have to be translated as "their" (French "leur", 3rd person)

You are absolutely right, I already corrected the string in question.

Thanks for the , pianoman74!
And thanks, no_noise_reduction, for making that update!

I've had our German-speaking staff review the three German translations of the VAT help documents, so hopefully they are also looking better!

Hi German translators! We've been syncing with Transifex every Thursday, but we will be syncing three times this week in an attempt to get as many translations live as possible. There are some new strings for an Discogs Labs beta test you'll be hearing more about soon, as well as some last minute VAT updates. If you have time, check out the new and untranslated strings, and chip in a few translations: https://www.transifex.com/discogs-1/discogs-i18n/dashboard/

You might want to take advantage of the Transifex Translation Memory, as I noticed that many of the new strings are actually 100% matches with past translations.

As always, let me know if you have any questions! Thanks for all of your help!

I think "Order #" has to be changed to "Bestellung #" instead of "Bestell #" but it is already reviewed.

I just fixed that. Thank you.

Hi CrateConductor,

Thanks for all of your help with German translations! I have a quick question I'm hoping to get on...

We've recently received two questions from German sellers about their invoice. The confusion is with the difference between 'Current Invoice Items' and 'Unpaid Invoice'. The German translation of the former might imply that these items are on the current/unpaid Invoice, when in reality 'Current Invoice Items' are items that we aren't yet billing for, but will be included on the next issued invoice.

Honestly I think even in English the billing / invoicing page is a little confusing, so I'm not surprised that it's confusing in German. But I'm just wondering if you can think of a way to improve either translation so it's clear that the 'Unpaid Invoice' is an invoice that is ready to be paid, and the 'Current Invoice Items' is just a list of sales that will be included on a future invoice.

If it helps, here are the two strings in Transifex:

'Current Invoice Items'
https://www.transifex.com/discogs-1/discogs-i18n/translate/#de/$/50451128?tags=current

'Unpaid Invoice'
https://www.transifex.com/discogs-1/discogs-i18n/translate/#de/$/50453023?tags=unpaid

Thanks again for all that you do to help make Discogs more accessible to German music-lovers!

I think I understand now, what exactly the strings are refering to. I changed the translations accordingly. I would like to ask the other translators to have a look at my solutions and give me a short .

What do you think about "Artikel der nächsten Rechnung" so it could be a little bit clearer?

[quote=mruetten][/quote]

yes, this is about what I decided for. should be clearer now.

Awesome, thanks CrateConductor!

Hi all, you'll notice that there are a lot of new untranslated strings that were just added to Transifex. Styles and Genres are finally translatable! Feel free to discuss here or in one of the general Database forums if you get stuck on how to translate a style, or if a style should even be translated.
Thanks for all of your help!

After having had a first look on the new strings I'm positive most styles and genres won't have to be translated anyway. A few of them will need consideration. Should not be too much work :-)

Great, thanks, no_noise_reduction

Guten Morgen! As some of you may have noticed, we recently rolled out the ability to change a name! We took a crack at writing a help document in German. Do you all have suggestions for us on where we can improve it? (see https://www.discogs.sie.com/help/doc/change-name?locale=de for proper formatting).

Sie können Ihre Benutzername ändern in Ihre Kontoeinstellungen.

Sie können Ihre Benutzername ingesamt 3 Male ändern. Folgen Sie diese Schritten um dies zu tun:

Stellen Sie sicher dass sie eingeloggt sind in Ihr Konto. Gehe nach die Einstellungen-Seite.
Scrollen Sie nach unten, unter ‘wort ändern’.
Setzen Sie Ihre neue Benutzername ein in die ‘Neue Benutzername’-Section. Bitte beachten Sie dass eine Benutzername mindestens 3 und höchstens 20 Zeichen. Benutzernamen müssen nicht jetzt oder irgendwann schon benutzt sein. Deswegen ist es auch nicht möglich Ihre Benutzername zurück zu ändern. Erlaubte Zeichen enthalten Buchstaben, Nummern, Unterstreichen (_), Bindestrichen (-) und Punkten (.).
Sie müssen Ihre wort eingeben um die Änderung zu bestätigen.
Sie bekommen eine Bestätigunsmail wenn Ihre Benutzername geändert ist.

Und das war es! Alle Einstellungen und Kontodaten werden gleich bleiben, und alle URLs mit Ihre Benutzername werden normal funktionieren.

Bitte beachten Sie das wenn Sie Ihre Benutzername geändert haben, Ihre alte Benutzername nicht mehr verwendbar ist. Nicht für Sie, nicht für andere (zukünftige) Benutzer. Bitte stellen Sie sicher, dass Sie bereit sind Ihre alte Identität zu löschen - es gibt keinen Weg zurück.

The text by itself should be easily understandable for any German speaker. There are, however, a couple of flaws regarding case, number and word order, which are always a bit tricky for non-native German speakers. This is the revised text:

Sie können Ihren Benutzernamen in den Kontoeinstellungen ändern.

Sie haben die Möglichkeit, Ihren Benutzernamen insgesamt dreimal zu ändern. Gehen Sie dazu wie folgt vor:

Stellen Sie sicher, dass Sie in Ihr Konto eingeloggt sind. Rufen Sie die Einstellungen-Seite auf und scrollen Sie nach unten bis zum Punkt "wort ändern".
Tragen Sie unter "Neuer Benutzername" den von Ihnen gewünschten neuen Nutzernamen ein. Bitte beachten Sie, dass ein Benutzername aus mindestens drei und höchstens zwanzig Buchstaben bestehen muss. Neue Benutzernamen dürfen nicht vergeben oder in der Vergangenheit vergeben gewesen sein; aus diesem Grunde ist es auch nicht möglich, Änderungen an Benutzernamen rückgängig zu machen. Erlaubte Zeichen sind Buchstaben, Nummern, Unterstriche (_), Bindestriche (-) und Punkte (.).
Sie müssen Ihr wort eingeben, um die Änderung zu bestätigen.
Wenn Ihr Benutzername geändert wurde, erhalten Sie eine Bestätigungsmail.

Das war es! Alle weiteren Einstellungen und Kontodaten bleiben erhalten und alle URLs mit Ihrem Benutzernamen werden normal funktionieren.

Bitte beachten Sie: Wenn Sie Ihren Benutzernamen geändert haben, ist Ihr alter Nutzername nicht mehr verwendbar - weder für Sie noch für andere (zukünftige) Benutzer. Bitte überlegen Sie sich gut, ob Sie Ihren alten Nutzernamen löschen möchten, denn dieser Schritt ist nicht rückgängig zu machen.

Super! Vielen Dank, no_noise_reduction! I've applied the edits. Thanks again!

Hi, I'm new here and just started looking at some of the untranslated strings. Two questions:

1) I've used the double-quote (") for Anführungszeichen, because that's how it seems to be done so far. But even though I'm personally not the greatest fan of the German-style „Anführungszeichen“, shouldn't those be used? Is there a reason not to?

2) I don't know which text-replacement is used. But I always like translations like "2 Bestellungen" but "Eine Bestellung", which would mean using the {} placeholder only in the plural version. Does that break things?

Sorry if those questions have been answered before and I've been too blind…

Hello cdrx,

You are right about the quotation marks. We'd have to use the ALT+0132 combination for any of the respective strings and be careful not to mess up any of the HTML code. But I think it can be done. I will look into it later today :-)

Regarding the {} placeholders:Good point. Yes, this would make transifex at least display a warning. Since {} is a placeholder for a digital value inherent in the Discogs system I am not sure whether it can easily be replaced by a linguistic numeral.

By the way, I have had a first look into your translations - excellent job so far!

Lars

Hi Lars,

thanks for the kind ! :)
I actually had fun doing this and Transifex provides a rather nice interface. So I'll happily help when there's more to translate.

Chris

Thanks Chris and Lars for your excellent work on translations!

cdrx
I don't know which text-replacement is used. But I always like translations like "2 Bestellungen" but "Eine Bestellung", which would mean using the {} placeholder only in the plural version. Does that break things?

I'm not totally sure, but I'm happy to check with one of our developers if you either mark that string as an issue in Transifex or post a link here.

I have had a first go on most of the style related strings on transifex and I was a bit surprised to find so many that either I could not translate or that would become ambiguous after translation. I compiled a little list of genres/styles that I would like to have the experts have a look at. Thanks in advance for everybody's opinion!

Here we go:
Abstract: Abstrakte Musik (?)
Acid Rock: Acid Rock (?)
Acoustic: Akustische Musik (?) - eigentlich ist ja jede Musik akustisch
Afro-cuban Jazz: Afrokubanischer Jazz (?)
Bass Music: Bass Music (?)
Ballroom:
Bayou Funk: Bayou Funk (?)
Beatdown: Beatdown (?)
Broken Beat: Broken Beat(?), BRUK (?)
Celtic: Celtic Music(?)
Children's: Kinder(?), Kindermusik(?)
Comedy: Comedy (?), Humor (?)
Conscious: Conscious Rap (?, Quelle: wikipedia) - gibt es diesen Stil nur als Unterart des Hip-Hop?
Contemporary: Zeitgenössische Musik (?) - laut Discogs-Beschreibung ein Bereich der klassischen Musik seit etwa 1975
Contemporary Jazz: Zeitgenössischer Jazz (?)
Cubano: Kubanische Musik (?)
Cut-up/DJ: Cut-up/DJ (???), Mashup (?)
Deep Techno:
DJ Battle Tool: DJ Battle Tool (???)
Dialogue: Dialog (?), Gespräch (?)
Donk:
Doomcore:
Educational: Pädagogik (?), Bildung für Kinder (?) - hierzu bitte die Stilbeschreibung auf Discogs beachten
Folk, World & Country: Folk, World & Country (?), Folk, Weltmusik & Country (?)
Gangsta - wo liegt der Unterschied zu "Thug Rap"?
Ghetto - ?
Harsh Noise Wall - Harsh Noise (?)
J-Core - ?
Juke - Juke House (?)
Leftfield - ?
Light Music - Leichte Musik ??
Luk Krung - Luk Krung?
Medieval: Mittelalter (?), Mittelaltermusik (?), Mittelalterliche Musik
Mizrahi - Mizrachim-Musik ???
Modern Classical: Neue Musik (?)Mouth Music: Vokalmusik (?)
Neo Trance - Neo-Trance (?)
Neo-Romantic - wer kennt sich da aus?
Népzene - Népzene, Ungarische Volksmusik (?)
Nordic Music - Nordische Musik, Nordeuropäische Musik (?)
Pacific - Pazifische Musik (?)
Philipine Classical -
Pipe & Drum - ?
Progressive Breaks - ?
Public Service Announcements - ?

...to be continued.

Hey guys. I just checked the glossary and wanted to translate a few things. Some easy ones I just translated without consulting you guys. I hope thats not a big problem.

Now to the issues at hand:

1) "Barcode": The official translation is "Strichcode" but in everyday life we use the english term just as often. Now in the next row someone translated "Barcodes and Other Identifiers" to "Barcodes und andere Identifizierungsmerkmale". Translations should be consistent which now makes me ask the question if we should stick to "Barcode" or use the german term "Strichcode".

2) "Policy": I guess you are referring to your business policies, right? Then this should be translated to "Firmenpolitik" oder "Geschäftspolitik". What do you guys think?

3) "History": Should simply be translated to "Geschichte" oder "Historie" or am I missing something?

4) "Item": Are you referring to the items being traded here and can be added to the shopping cart? Then the proper translation would be "Artikel", right?

Where did you translate the glossary? Transifex? reference.discogs.sie.com?

Regarding the use of "Barcode" rather than "Strichcode": I don't think it makes much of a difference whether we use German "Strichcode" or the (perfectly acceptable) anglicism "Barcode". We could change it but what would be the benefit from that?

"Policy" is not always referring to business policy here. Discogs involves all sorts of different policies, such as cancellation policies, shipping policies, an "Offensive Marketplace Item and Inventory" policy, and so on. If we would limit "policy" to business policy the term wouldn't be applicable in other contexts anymore.

"History" is mainly referring to the history of sales or release histories here. You wouldn't say "Verkaufsgeschichte" in German, would you? We went for "Verlauf" because there is not really a "historicity" to sales and release page logs; it's more about the course something took.

4) I agree. But don't we use "Artikel" already?

Apart from that: Welcome to the team :-)

I translated on https://www.transifex.com/discogs-1/discogs-i18n/glossary/de/?page=2

Regarding "Barcode": Makes totally sense.

Regarding "Policy": Yes there are all kinds of policies. I'm asking specifically about the term "Policy" in the glossary at the link I provided above. There are no specifications, it's just "Policy". So what is it referring to?

Regarding "History": Oh ok in that context "Verlauf" is of course the best option.

Regarding "Item": I guess you did in the "en" ressource on transifex but there was no translation in the glossary on transifex.

Hm ok then should I even bother translating the stuff in the glossary?

Thank you very much! Happy to be here :)

SirVize
Hm ok then should I even bother translating the stuff in the glossary?

Of course you should! Regarding "policy": I agree, there is no context given. I guess that, since there are other specific policies in the glossary "this" policy should be treated as policy in the widest possible sense.

Hey no_noise_reduction!

I have a quick question regarding the context of a string on transifex. I noticed in translation mode there is a column with "More Info" giving under "Occurences" what seems to be part of a link to the document containing the full text in which the string occurs. Is there a way to access the document using this part of the link? It would make finding the correct context quite easy for each individual translator and string. I didn't find any information in the transifex help about this or am I missing something?

SirVize
Is there a way to access the document using this part of the link?

Hey SirVize! Sorry I missed this question from so long ago. No, there is no easy way to reference those occurrences besides viewing the private Discogs code repository. But if you ever need context, just make the string as an issue and ask for context. Staff will get back to you ASAP with either written context or screenshots.

Does anyone who speaks German have any thoughts on the translation for "Custom Range" that shows up on a Seller's page?

For example, look at the filters under Price (Preisspanne) and Year (Jahr) on this page: https://www.discogs.sie.com/de/seller/OctoVinyl/profile

Both are translated as Eigene Preisspanne since there is only one string for "Custom Range". Is there a German word we could use that is more general that could work for both Price and Year?

"Bereich anen" (~ customise range) might work, or "Eigener Wertebereich" (~ custom value range). The second version in particular is rather technical, but both should be understandable.

Awesome, thanks so much, cdrx!
I'm going to go with "Bereich anen" as that seems the best fit. I've just made the update in Transifex, so this change will be live on the website the next time we sync. Thanks again!

As a Russian translator (sorry for wrong thread) I have a question to the Germans, how do you manage with different grammar cases (as far as I know in German there are enough of them). In Russian it affects word endings so sometimes adding one letter to the end of the word in order to observe grammar leads to getting the auto mark that the translation of the term from the dictionary is omitted. Thanks for the reply.

nickist420
how do you manage with different grammar cases (as far as I know in German there are enough of them).

Interesting question! I am working as both a translator and reviewer for the German localization of Discogs and you are right, German language has a pretty complex inflectional system (as I assume Russian language has) that in some cases requires to alter certain keywords.
Translations have to be comprehensible and, at the same time, adhere to a uniform level of language and style. In many cases we are required to stick to the exact English wording (e.g. "Discogs Payments") anyway. Stylistically, it is a very bad idea to apply German inflection to English wordings, so in most cases I adopt the original wording one on one.
Being a reviewer, I can tell you that translations that cause a "glossary translation missing warning" (I understand this is what you mean by "auto mark") can be ignored in cases where otherwise the understandability, grammar or style of a translation would suffer. I quite constantly (have to) approve to translations that come with this warning.

nickist420
In Russian it affects word endings so sometimes adding one letter to the end of the word in order to observe grammar leads to getting the auto mark that the translation of the term from the dictionary is omitted.

Yeah, I definitely agree with what no_noise_reduction says. Don't worry too much about those warnings. (You are still able to save the translation after you receive the warning, correct?)

The Glossary should help guide translations and make sure translators are trying to be consistent. But providing a translation that makes sense for the specific phrase or string matters most.

Also, the Russian Glossary translations can certainly be debated and changed if needed. :) https://www.transifex.com/discogs-1/discogs-i18n/glossary/ru/

Thanks for your replies!

I have a problem with the translation of strings related to Australian "GSt". Since these strings will probably be of no concern for any german speaking , wouldn't it be better to leave these strings untranslated (or even hide them) and concentrate on important parts of the webside (e.g. Database Guidelines - Datenbank-Richtlinien).
"Discogs Shipping" (Versenden mit Discogs) in the Help section is for me the prototype of a senseless effort of translation, because you can only use it as US seller.

Hi 1wax,

Good point! Our development team tries to make sure all new features are translatable, but yes, that means some of the text you see pulled into Transifex might not be relevant for German speakers.

You can certainly skip those translations if they aren't relevant to German s.

The Database Team is working on translating the Database Guidelines into Spanish right now, and they hope to work on more languages after they see how that goes.

I think they've started with the Database Guidelines Glossary in German: https://www.transifex.com/discogs-1/zendesk-help-center-4/translate/#de/HTML-articles-360004017694/163139790?q=translated%3Ano

Äh, soll man Button mit Schaltfläche übersetzen oder als Wort erhalten?
Und wie würdet ihr mit amp in "This is part of our Sales & Transactions Policy" verfahren?
Should button be translate or not?
And what would you do with amp in "This is part of our Sales & Transactions Policy"?

Und Grundlegend: Die Fehlermeldung "Glossary translation for term 'xxx' missing from translation", muß ich die irgendwie bestätigen und wo finde ich denn dieses Glossar?

Hallo Rosiefisch!

Wir haben "Button" bisher immer als Schaltfäche übersetzt. Ich denke, es wäre nicht sinnvoll, jetzt damit zu beginnen, das Wort "Button" zu verwenden.

"&" ist HTML und steht für "&" - das kannst Du unverändert im String belassen.

Diese Fehlermeldung, die Du da beschreibst, kannst Du weitestgehend ignorieren.
Das Glossar ist noch nicht vollständig übersetzt, d.h. Du müsstest die englischen Begriffe übernehmen, um die Fehlermeldung zu vermeiden. Wichtig ist am Ende aber vor allem, dass die Übersetzung im Deutschen gut verständlich ist.

no_noise_reduction
wäre nicht sinnvol

Deswegen meine Frage. Vielen Dank für die Antwort.

Hello German Translation Team!

I'm going to make some improvements for our Community Translation Team in the coming months, and I would love to hear your in this survey:
Discogs Community Translation Team Survey

The survey is only a few questions long and should only take a few minutes to complete. I'll use the to help guide improvements to the translator onboarding process. The survey is anonymous, so feel free to along any and all . Thank you!!! :)

Hey team! I have a basic question about the cratediggers.com project. I just wanted to know whether we should translate "you" in the 3rd person plural (Sie) or the 2nd person singular (Du)? Maybe Weetzie could chip in here too? Using the 3rd person plural in german makes for a more formal and respectable address and puts a bit of a distance between people. You use it for talking to people you don't know, superiors of you etc. The 2nd person singular in german is used for a more direct and informal form of address. It's like talking to a friend. I wonder what kind of marketing cratediggers.com has and whether or not it's targeted at younger audiences and aims for a personal approach. If that's the case I would use the 2nd person singular. At Discogs.com it looks like the 3rd person plural is the standard. Any suggestions/thoughts?

Hey SirVize, many thanks for chiming in. The decision to use 3rd pers. pl. instead of 2nd pers. sing. for the main site was made years ago in consultation with Discogs staff/management. I that we were looking at how different bigger German domains (Ikea, among others) solved it. I think that ultimately the decision to use the plural forms was made pretty much intuitively. Personally, I still think it was the right decision because with many German websites that use the 2nd pers. sing. form I get the feeling communication is too chummy, too matey, too "I know whats best for you, buddy" (if you get what I mean). This is only my opinion, though.

I guess it's up to Discogs staff/management to decide how to proceed with the Crate Diggers website. Localization there is still in a very early stage, so it would be possible to opt for the 2nd pers. sing, at this point.

Hi SirVize, thanks for bringing this up.
And thanks no_noise_reduction for your response.

SirVize
I wonder what kind of marketing cratediggers.com has and whether or not it's targeted at younger audiences and aims for a personal approach.

You're right, our Crate Diggers audience skews a little younger than our Discogs audience, but there is a pretty major overlap. Many of the sellers that sell at Crate Diggers are also selling on Discogs.

My initial thought is that it would be nice to have brand consistency between Crate Diggers and Discogs. We should have a similar "voice" across both sites. So with that in mind, it seems like we should stick with the 3rd person plural.

However, I'm not fluent in German. I certainly don't understand all of the nuances, so feel free to disagree with me and we can continue to discuss. SirVize, do you feel strongly that 2nd person singular would be better for Crate Diggers?

Thanks for the quick responses no_noise_reduction! If the majority of the audience were teens, then yes I would feel strongly for 2nd person singular and go all in with kind of a "mtv"-approach. But if there is a major overlap anyways and I view Discogs as more of a mature, reputable and in some ways classy (if that's the right word) platform, I think it would be better to go with brand consistency too and carry over the 3rd person plural.

Great, let's carry over 3rd person plural to Crate Diggers then. Thanks so much for your and involvement in translations!

Yeah, we are definitely not targeting teens with Crate Diggers. Most Crate Diggers events we host in the US are age 21+ (although that age varies based on the venue and the country's alcohol consumption laws.)

Hey no_noise_reduction!
Bezüglich Events/Veranstaltungen: Ich hab gemerkt, wir haben beide bei "previous events" und " events" "Events" benutzt. Bei "Events" alleine hab ich mich vorher dummerweise für Veranstaltungen entschieden. Sollen wir da auch einfach "Events" draus machen, damits einheitlicher ist? Es würde auch schon allein von der Buchstabenanzahl besser zu den anderen Menüpunkten en. Oder wärs besser es so zu lassen? Oder gar alle "Events" strikt als "Veranstaltungen" übersetzen?

Ich würde sagen, dass hier zum Tragen kommt, was wir vorher schon erörtert haben. Anglizismen wie "Event" versteht inzwischen fast jeder, trotzdem hat das Ganze ja doch eher einen jugendlichen Unterton. Wenn wir "Events" auf der gesamten Seite als Events übersetzen, dann würde das zu viel werden, auf der Startseite, die ja eher etwas auffordend-werbend rüber kommt, t es meiner Meinung nach ganz gut. Ich finde, wir sollten überwiegend Veranstaltung(en) verwenden, und hin und wieder mal Event einstreuen, damit es insgesamt lockerer wird.

Hey all, just a quick update:

There are many places on the website where we "recycle" translations for certain words or phrases. For example, we don't ask you to translate "Forum" for each place it's used on the website - we simply use the same translation across the website. However, occasionally that doesn't work. There are several English homonyms (words that have the same spelling, but different meaning) that we also incorrectly reuse the same translation for across the website.

One example, which has been an issue for a long time, is "Credits". On Discogs, "Credits" might relate to Artist "Credits" or Marketplace "Credits". Obviously, in most languages, two different translations are needed. But until recently we were using the same translation for both. But, as of today, we have a better way of separating out these strings! Wahooo!

• Here is the string that relates to Marketplace Billing "Credits".

• Here is the string that relates to Artist "Credits".

Will someone please check those two strings to make sure they are translated correctly? The Transifex "Translation Memory" filled in a translation for the new string already, but I'm not certain it's correct.

And please let me know if you run across other strings that are incorrectly using the same translation in multiple places. Thanks all!

We now have different strings for homonyms? The 21st century is full of surprises.. :P Just kidding, wahooo indeed! I suggested another translation for the Marketplace Billing "Credits", namely "Gutschriften". I think this makes the most sense if I go by the given definition "Credits: An amount of money added to an ." Translating it to "Credits" would In my estimate only make more sense if these were meant to be specific "Discogs Credits" as a type of discogs-specific currency but the way I see it it's simply the amount or payment of a refund or cancelled order paid automatically by/through the Discogs system credited to the s .