Adds Danish translation of website

[mex]

This adds a Danish translation of the website in the appropriate folder according to TRANSLATION.md.

Glossary is added here: https://github.com/iojs/iojs-da/wiki/Glossary

/cc @tjconcept, @Renetnielsen

[mikeal]

Let me know when the review comments and mere conflicts are resolved and we'll get this merged :)

[saebekassebil]

Hej @mex. Jeg synes det er super godt arbejde, og undskyld den lidt sporadiske feedback. Jeg får snart læst det hele igennem samlet.

[tjconcept]

I've just completed my review.

As stated earlier (in Danish) I am skeptical about translating the website. I am afraid it will do more harm than good. I so far have not been able to find Danish tech peers who prefer reading technical stuff in Danish (I have asked a total of eight so far, and done my best to be objective).
This "problem" is so well-recognized that a lot of Danish tech-companies internally use English as their written language regarding software. Danes are on average pretty comfortable with English.

The current translation, although a really thorough and well-done job (credits to @mex), is pretty direct making it cumbersome to read and you constantly find yourself doing the translation back to English to understand what tech-term is referred to.
We could improve the reading experience quite a bit by literally re-writing the chapters to make the language "more danish", but that might not be what io.js wants, and I would still imagine people preferring the original English version.

[therebelrobot]

@iojs/website how do you think we should proceed given @tjconcept's input? We could do a Danish-ish translation?

[mikeal]

Keep in mind that we aren't doing any language detection in the browser and defaulting to any non-english site. The only way to get to the Danish site would be to click a link to read the site in Danish :)

[Fishrock123]

Keep in mind that we aren't doing any language detection in the browser and defaulting to any non-english site. The only way to get to the Danish site would be to click a link to read the site in Danish :)

Yet, that is. We should probably do this in the future, and have some sort of language-switch thing.

[tjconcept]

Yet, that is. We should probably do this in the future, and have some sort of language-switch thing.

Please don't :( Debian pages do so, and it is terribly frustrating..

[snostorm]

@tjconcept the language switching will be more opt-in, some sort of visual hints on the page as to the other languages available (perhaps highlighting the probable choice based on your location/browser settings) but I don't want to ever have it force-redirect.

[snostorm]

Also, my 0.02€ on the tone/choice of words: I think the message/lesson is more important to get across versus a literal translation. As an anglophone living in France, I can pick up a lot of the technical details of a talk given in french because many things are still said in "international dev speak" (aka, the original English technical term.)

If it makes more sense to rewrite a page for it to make more sense contextually to a speaker in the target language, I'd say 👍

If it makes more sense to still use English-tech words your audience clearly knows/understands, I'd say 👍

Having the primary articles of the site still in non-English languages are helpful to those who might be younger (thus less practiced in second languages early/before their career) or to those coming from a less international/technology-driven team traditionally.

At the end of the day, it is up to the local group to decide on the scope of their translation efforts. Do they want 100% coverage or just key marketing/FAQ/etc. covered, knowing in their specific region, English is a very accessible language.

[bnb]

@snostorm I don't think it could have been said better. Should we ask members of iojs/iojs-da to get their word in on this?

[mex]

We also have a discussion going about this in Danish in iojs/iojs-da, but I personally totally agree with @snostorm. I would prefer to have a more loose translation while keeping "untranslatable" phrases in English.

This will of course be a more time consuming effort, but to me it's worth it.

[therebelrobot]

On the agenda for Mar 2nd Website WG meeting #240

[saebekassebil]

@mex, @tjconcept What's the status on this? Are we moving forward with the Danish translation (I could find some time to help out) or are we keeping the English version?

[mex]

I'm still up for using a translated version, but as discussed in the PR, it should probably be more loosely translated as to actually provide a benefit for Danish users compared to the English version.

So my point being that we need to spend the time to actually rewrite most of it.

[snostorm]

FYI at the WG meeting on Monday we basically agreed with my above summary which could be said, in short, "give the i18n groups lots of space to translate how they think is best". :)

[tjconcept]

@mex, @saebekassebil I have been playing around with a more freely translation, have a look: https://github.com/srcagency/iojs-website/commit/8301e0c68be85be0777a475caee52fd05f1c02d5

I think it is better that way, but I am still not completely satisfied (actually the English version feels a bit clunky too, so that might be more of a "information density" problem - I would like it simpler, more to the point), it might be good enough though. Sadly I do not have the time currently to do much of the translation.

[mex]

I think that translation looks good. It makes a lot of sense to translate it more freely.

By the way are you actually using VIM to write translations?

[tjconcept]

No, Sublime actually.

You're refering to the wrapping I suppose? I just think it is more readable that way (ALT + Q), but we'll of course have to align with the project as a whole. /cc @snostorm

[mex]

I would much prefer wrapping is done softly in individual editors, when we are dealing with prosa.

[snostorm]

Eventually we'll publish some sort of whitespace / etc. guidance for iojs/website, but at the end of the day, local rules/preferences might prevail for content-specific pages. I'm neutral right now, but we can open an issue to discuss this with the wider community?

[mex]

A convention for this would be nice to have nailed down, so I would say go for a general discussion on it.

[fhemberger]

@iojs/website What's the current status of this PR?

[mex]

Current state could probably be described as stale. It was decided that a Danish translation of the site would require a more thorough Danification (not really a word) of the text, but that requires a lot of time, which I don't currently have. I can't really give an estimate on when this would be ready.

[fhemberger]

Okay, in this case I'd like to close this issue for now. If there's enough interest to start an iojs-dk translation group, it could take over using your efforts so far and work on the internationalization of the website.

Any thoughts?

[tjconcept]

👍