{"action":"created","issue":{"url":"https://api.github.com/repos/samaaron/sonic-pi/issues/391","labels_url":"https://api.github.com/repos/samaaron/sonic-pi/issues/391/labels{/name}","comments_url":"https://api.github.com/repos/samaaron/sonic-pi/issues/391/comments","events_url":"https://api.github.com/repos/samaaron/sonic-pi/issues/391/events","html_url":"https://github.com/samaaron/sonic-pi/issues/391","id":63298822,"number":391,"title":"i18n de - German tutorial translation - proofreading chp. 7-11","user":{"login":"mbutz","id":3934249,"avatar_url":"https://avatars.githubusercontent.com/u/3934249?v=3","gravatar_id":"","url":"https://api.github.com/users/mbutz","html_url":"https://github.com/mbutz","followers_url":"https://api.github.com/users/mbutz/followers","following_url":"https://api.github.com/users/mbutz/following{/other_user}","gists_url":"https://api.github.com/users/mbutz/gists{/gist_id}","starred_url":"https://api.github.com/users/mbutz/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mbutz/subscriptions","organizations_url":"https://api.github.com/users/mbutz/orgs","repos_url":"https://api.github.com/users/mbutz/repos","events_url":"https://api.github.com/users/mbutz/events{/privacy}","received_events_url":"https://api.github.com/users/mbutz/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":20,"created_at":"2015-03-20T20:11:40Z","updated_at":"2015-04-11T10:19:48Z","closed_at":null,"body":"Hi Sam, hi to the other translaters,\r\n\r\nI proof-read chapter 7 - 11. Of course I can not proof-read my own translation (1-6)\r\n\r\nAs we did not agree upon a specific procedure (see: https://github.com/samaaron/sonic-pi/issues/343#issuecomment-78045930 onwards) I noted some necessary/possible changes in the text; example:\r\n\r\n```\r\nEine Möglichkeit ist es, alle Noten in einer Liste zu spielen: `[52, 55, 59]`. \r\nUnsere freundliche Funktione [Funktion][@mbutz] `play` ist schlau \r\ngenug[,][@mbutz] um zu wissen, wie man eine Liste von Noten abspielt. \r\nVersuche es einmal:\r\n```\r\n\r\nPlease let me know whether there is a better way how we should carry on. The corrections/propositions for changes I pushed to my repository: https://github.com/mbutz/sonic-pi/.\r\n\r\n@samaaron: Do you want me to issue a pull request? (Don't know whether this is a good idea because now the tutorial is in an interim state; @wwerner and @st01c have to accept or dicard my changes and remove my notes).\r\n\r\nI also have some general remarks and/or more extended comments which I am posting here; also here, let me know if there is a better way to communicate about this:\r\n\r\n# Proof-Reading of Tutorial Chapter 7-11 by @mbutz\r\n\r\n## 06-FX.md\r\n\r\nGeneral remarks: \r\n\r\n+ English expressions in parenthesis, e.g. \"möchtest du deine Bassmelodien verzerren ('distortion') oder schwabbeln lassen ('wobble').\"\r\n+ English: \"This is called FX chaining.\" German: \"Man nennt diese Vorgehensweise 'Effektverkettung.'\" We need a general guideline whether to stress new expressions or not (like in the english text)\r\n+ \"Du, Dein\" etc. or \"du, dein\"? IMHO the capitalized versions do look oldfashioned and is not necessary according to Duden. Actually the \"Du\", as I understand it, is meant for personal conversations like in letters. Here it is a generic \"du\" which adresses all readers of the tutorial.\r\n\r\n## 06.2-FX-in-Practice.md\r\n\r\nGeneral remarks:\r\n\r\nAgain the question pops up: What to translate and what to leave in English; here e.g.: \"run-local\" and \"run\"\r\n\r\nMy general rule of thumb: Not to translate any terms which also appear in the code such as \"synth\" and some more. Furthermore: expressions which do not have an equivalent in German, such as \"live coding\". In all other cases, i.e. if there is a decent translation (decent = meaning: it is a common term used in colloquial German or comparable German technical documentations, such as envelope = Hüllkurve), I vote for a translation. My argument for this rule: we do not want to teach English but make the program usable for those, who do not read English fluently. (If people want to know the English term the better it is, but this has no priority for me; on the other hand it is crucial, that users do not get confused, if they find a term which is frequently used within the code but translated into German; that's the threshold for me where they will have to understand and use the English term).\r\n\r\n+ \"Synthie\" or \"Synth\" (I would argue: it is used in the code so no translation)\r\n\r\n## 06.1-Adding-FX.md\r\n\r\n+ \"nutzen wir die \"goalpost\"-Parameter (deut. Torpfosten)\"; I propose to be less true to the original text but more clear concerning the actual meaning: \"senkrechte Striche\", see http://de.wikipedia.org/wiki/Senkrechter_Strich\r\n+ I propose to apply the German language rule to bind terms which belong together with a hyphen, e.g. not \"do/end Block\" but \"do/end-Block\"\r\n\r\n## 07.1-Controlling-Running-Synths.md\r\n## 07.2-Controlling-FX.md\r\n## 07.3-Sliding-Parameters.md\r\n## 07-Control.md\r\n\r\n+ \"Sounds\" or \"Klänge\"?\r\n+ Who is speaking? See: \"Glück gehabt - in diesem Kapitel werden wir Dir genau das zeigen.\" I used to translate either \"I ...\" if Aaron speaks of himselft or \"it (the chapter) shows ...\"; we should be univocal throughout the tutorial.\r\n\r\n## 08.1-Lists.md\r\n\r\n+ Log [Protokoll]; occurs also elsewhere. See: `app/gui/qt/lang/sonic-pi_de.ts`\r\n\r\n## 08.2-Chords.md\r\n\r\n`time`: often I'd rather prefer to translate this as `Zeitdauer` or `Dauer` rather than `Zeit`, because that's what's actually meant.\r\n\r\nA `Kreis von Zeiten` ist not really a clear description of `circle of times`; I do not have a simple translation at hand, but I think is is rather something like `zirkulär verwendete (Zeit)Dauern` (which is clumsy but more precise and does not bear the danger of sounding metaphorical).\r\n\r\n## 08.3-Scales.md\r\n\r\n`Lang-Knopf`: 1. will this be called `lang` in the translated GUI (this questions also applied to the tutorial navigation in general e.g. `chord` and `scale`)? 2. I chose `Button` because I feel that `Knopf` sounds akward. Otherwise my own proposition is to use german expressions if available. What should we do?\r\n\r\n## 08.4-Rings.md\r\n\r\n## 08-Data-Structures.md\r\n\r\n## 09.1-Live-Coding-Fundamentals.md\r\n\r\n`named thread`: I don't think there is such a word like `benamt` in German; I'd rather say `benannt` (you could say `namentlich` which might even be more precise but sounds a bit akward in my ears)\r\n\r\n`Wir haben keine neue Ebene bekommen, da wir einen benannten Thread verwendet haben, was nur einen Thread pro Name zulässt.`: The last subordinate clause sounds a bit clumsy in my ears. I propose to rephrase `; jedem Namen kann nur ein Thread zugeordnet werden.` That's the other way round but because we have a one-to-one correspondence of thread and name it seems to be okay.\r\n\r\n## 09.2-Live-Loops.md\r\n\r\n`Live Loop`: Should we go for `Live-Loop` (see also next chapter and chapter 06.1-Adding-FX.md about using the hyphen)\r\n\r\n## 09.3-Multiple-Live-Loops.md\r\n## 09-Live-Coding.md\r\n\r\nSometimes seemingly simple english phrases become quite long and conplicated in German: `Einer der interessantesten Aspekte von Sonic Pi ist, das [dass][@mbutz] es dir die Möglichkeit gibt, Code live zu schreiben und zu verändern um Musik zu machen, so als würdest Du beispielsweise mit einer Gitarre auftreten.` I would rephrase somehow like that to make it more simple and : `Einer der interessantesten Aspekte von Sonic Pi ist es, das es dir die Möglichkeit gibt, Code live zu schreiben; beim Spielen veränderst du deine Musik so, als würdest Du beispielsweise mit einer Gitarre auftreten.`\r\n\r\n## 10.1-Using-Shortcuts.md\r\n\r\nProposition: German names resp. naotations printed the keys for keys\r\n\r\nControl = Strg/Ctrl (Mac)\r\nMeta = Alt/Cmd (Mac)\r\nShift = Umschalttaste\r\n\r\n## 10.2-Shortcut-Cheatsheet.md\r\n## 10.3-Sharing.md\r\n\r\n`[GitHub](https://github.com) ist eine Seite um Code zu teilen und damit zu arbeiten. GitHub wird von professionellen Entwicklern und auch Künstlern verwendet, um Code zu teilen und zusammenzuarbeiten.`: One of these sentences is redundant. I would skip the first one, keep the second and link GitHub.\r\n\r\n## 10.4-Performing.md\r\n## 10-Essential-Knowledge.md\r\n## 11-Conclusions.md\r\n\r\n`Hoffentlich hast Du etwas dabei gelernt.` In German - at least for me - one could easily read this in a moralistic way. My proposition: `Hoffentlich hat es dir etwas gebracht` or `Hoffentlich konntest du dabei etwas lernen.`\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/samaaron/sonic-pi/issues/comments/91821506","html_url":"https://github.com/samaaron/sonic-pi/issues/391#issuecomment-91821506","issue_url":"https://api.github.com/repos/samaaron/sonic-pi/issues/391","id":91821506,"user":{"login":"mbutz","id":3934249,"avatar_url":"https://avatars.githubusercontent.com/u/3934249?v=3","gravatar_id":"","url":"https://api.github.com/users/mbutz","html_url":"https://github.com/mbutz","followers_url":"https://api.github.com/users/mbutz/followers","following_url":"https://api.github.com/users/mbutz/following{/other_user}","gists_url":"https://api.github.com/users/mbutz/gists{/gist_id}","starred_url":"https://api.github.com/users/mbutz/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mbutz/subscriptions","organizations_url":"https://api.github.com/users/mbutz/orgs","repos_url":"https://api.github.com/users/mbutz/repos","events_url":"https://api.github.com/users/mbutz/events{/privacy}","received_events_url":"https://api.github.com/users/mbutz/received_events","type":"User","site_admin":false},"created_at":"2015-04-11T10:19:48Z","updated_at":"2015-04-11T10:19:48Z","body":"@hzulla - If @samaaron accepts the pull request you will get some changes I did as a result of my proof-reading. I do hope I did not mess up any of your changes while resolving my conflicts. Especially I did take care about the line breaks where I rephased things. I understood that lines should not have more than 72 characters. Is that right? Please give me an idea, why this is necessary. I thought the help window of Sonic Pi would take care of and make automatic line breaks. Nevertheless I will make proper line breaks in the future."}}