Adds Danish translation of website #153

mex · 2015-02-10T04:12:07Z

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

content/da/es6.md


-io.js is built against modern versions of [V8](https://code.google.com/p/v8/). By keeping up-to-date with the latest releases of this engine we ensure new features from the [JavaScript ECMA-262 specification](http://www.ecma-international.org/publications/standards/Ecma-262.htm) are brought to io.js developers in a timely manner, as well as continued performance and stability improvements.
+io.js er bygget op mod en moderne version af [V8](https://code.google.com/p/v8/). Ved at holde det opdateret med de seneste udgivelser af denne motor, sikrer vi at nye funktioner fra [JavaScript ECMA-262-specifikationen](http://www.ecma-international.org/publications/standards/Ecma-262.htm) bliver rettidigt tilgængelige for io.js-udviklere, hvilket også gælder forbedringer til ydeevne og stabilitet.


mikeal · 2015-02-12T22:07:07Z

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

content/da/es6.md


-On joyent/[email protected] (V8 3.26), the `--harmony` runtime flag enabled all **completed**, **staged** and **in progress** ES6 features together, in bulk (with the exception of nonstandard/non-harmonious semantics for `typeof` which were hidden under `--harmony-typeof`). This meant that some really buggy or even broken features like [proxies](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Proxy) were just as readily available for developers as [generators](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*), which had very little or even no known-issues. As such, it was best practice to either enable only certain features by using specific runtime harmony feature flags (e.g. `--harmony-generators`), or simply enable all of them and then use a restricted subset.
+I joyent/[email protected] (V8 3.26), slår `--harmony`-runtime-flaget alle **færdige**, **staged** og **igangværende** ES6-funktioner til sammen på samme tid (med undtagelse af ikke-standard/ikke-harmonerende semantikker for `typeof`, som blev skjult under `--harmony-typeof`). Dette betød at nogle meget fejlfyldte eller ikke-virkende funktioner som [proxy'er](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Proxy) var lige så tilgængelige for udviklere som [generatorer](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*), der havde meget få eller endda ingen kendte problemer. Derfor var det den bedste praksis kun at slå bestemte funktioner til ved at bruge specifikke runtime-flag (fx `--harmony-generators`), eller ved simpelthen at slå dem alle til og derefter bruge et begrænset udsnit.


saebekassebil · 2015-02-13T10:22:13Z

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.

content/da/es6.md

-*   All **shipping** features, the ones that V8 has considered stable, like [generators](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*), [templates](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/template_strings), [new string methods](https://developer.mozilla.org/en-US/docs/Web/JavaScript/New_in_JavaScript/ECMAScript_6_support_in_Mozilla#Additions_to_the_String_object) and many others are turned **on by default on io.js** and do **NOT** require any kind of runtime flag.
-*   Then there are **staged** features which are almost-completed features that haven't been completely tested or updated to the latest spec yet and therefore are not considered stable by the V8 team (e.g. there might be some edge cases left to discover). This is probably the equivalent of the state of [generators](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*) on 3.26. These are the "use at your own risk" type of features that now require a runtime flag: `--es_staging` (or its synonym, `--harmony`).
-*   Finally, all **in progress** features can be activated individually by their respective harmony flag (e.g. `--harmony_arrow_functions`), although this is highly discouraged unless for testing purposes.
+*   Alle **færdige** funktioner, dem som V8 betragter som stabile, som [generatorer](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*), [skabeloner](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/template_strings), [ny streng-methods](https://developer.mozilla.org/en-US/docs/Web/JavaScript/New_in_JavaScript/ECMAScript_6_support_in_Mozilla#Additions_to_the_String_object) og mange andre er slået **til som standard i io.js** og kræver **IKKE** nogen form for runtime-flag.


tjconcept · 2015-02-13T12:01:01Z

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 · 2015-02-13T16:35:47Z

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

mikeal · 2015-02-13T17:03:30Z

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 · 2015-02-13T17:06:26Z

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 · 2015-02-13T17:14:30Z

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 · 2015-02-27T13:51:26Z

@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 · 2015-02-27T14:15:39Z

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 · 2015-02-27T15:36:34Z

@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 · 2015-02-27T15:46:34Z

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 · 2015-03-02T18:43:36Z

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

saebekassebil · 2015-03-03T22:38:39Z

@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 · 2015-03-03T23:01:20Z

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 · 2015-03-03T23:44:54Z

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 · 2015-03-04T00:24:27Z

@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 · 2015-03-04T13:09:42Z

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 · 2015-03-04T13:30:58Z

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 · 2015-03-04T13:40:35Z

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

snostorm · 2015-03-04T15:53:04Z

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 · 2015-03-04T15:55:41Z

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

fhemberger · 2015-04-23T06:49:42Z

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

mex · 2015-04-23T17:08:15Z

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 · 2015-04-24T05:15:46Z

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 · 2015-04-24T08:11:52Z

👍

Added Danish translation of website

0f302b1

mex mentioned this pull request Feb 10, 2015

Adds Danish translations of website #129

Closed

Fishrock123 added content i18n and removed i18n labels Feb 10, 2015

therebelrobot added the needs i18n review label Feb 10, 2015

saebekassebil reviewed Feb 12, 2015
View reviewed changes

saebekassebil reviewed Feb 13, 2015
View reviewed changes

tjconcept reviewed Feb 13, 2015
View reviewed changes

snostorm mentioned this pull request Feb 27, 2015

Remove/flag stale i18n articles #246

Closed

snostorm mentioned this pull request Mar 2, 2015

Website WG Meeting 4.0 - March 2, 2015 #240

Closed

5 tasks

therebelrobot added the wg-agenda label Mar 2, 2015

fhemberger closed this Apr 28, 2015

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Adds Danish translation of website #153

Adds Danish translation of website #153

mex commented Feb 10, 2015

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

mikeal commented Feb 12, 2015

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

saebekassebil commented Feb 13, 2015

This comment was marked as off-topic.

tjconcept commented Feb 13, 2015

therebelrobot commented Feb 13, 2015

mikeal commented Feb 13, 2015

Fishrock123 commented Feb 13, 2015

tjconcept commented Feb 13, 2015

snostorm commented Feb 27, 2015

snostorm commented Feb 27, 2015

bnb commented Feb 27, 2015

mex commented Feb 27, 2015

therebelrobot commented Mar 2, 2015

saebekassebil commented Mar 3, 2015

mex commented Mar 3, 2015

snostorm commented Mar 3, 2015

tjconcept commented Mar 4, 2015

mex commented Mar 4, 2015

tjconcept commented Mar 4, 2015

mex commented Mar 4, 2015

snostorm commented Mar 4, 2015

mex commented Mar 4, 2015

fhemberger commented Apr 23, 2015

mex commented Apr 23, 2015

fhemberger commented Apr 24, 2015

tjconcept commented Apr 24, 2015


		io.js is built against modern versions of [V8](https://code.google.com/p/v8/). By keeping up-to-date with the latest releases of this engine we ensure new features from the [JavaScript ECMA-262 specification](http://www.ecma-international.org/publications/standards/Ecma-262.htm) are brought to io.js developers in a timely manner, as well as continued performance and stability improvements.
		io.js er bygget op mod en moderne version af [V8](https://code.google.com/p/v8/). Ved at holde det opdateret med de seneste udgivelser af denne motor, sikrer vi at nye funktioner fra [JavaScript ECMA-262-specifikationen](http://www.ecma-international.org/publications/standards/Ecma-262.htm) bliver rettidigt tilgængelige for io.js-udviklere, hvilket også gælder forbedringer til ydeevne og stabilitet.


		On joyent/[email protected] (V8 3.26), the `--harmony` runtime flag enabled all completed, staged and in progress ES6 features together, in bulk (with the exception of nonstandard/non-harmonious semantics for `typeof` which were hidden under `--harmony-typeof`). This meant that some really buggy or even broken features like [proxies](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Proxy) were just as readily available for developers as [generators](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*), which had very little or even no known-issues. As such, it was best practice to either enable only certain features by using specific runtime harmony feature flags (e.g. `--harmony-generators`), or simply enable all of them and then use a restricted subset.
		I joyent/[email protected] (V8 3.26), slår `--harmony`-runtime-flaget alle færdige, staged og igangværende ES6-funktioner til sammen på samme tid (med undtagelse af ikke-standard/ikke-harmonerende semantikker for `typeof`, som blev skjult under `--harmony-typeof`). Dette betød at nogle meget fejlfyldte eller ikke-virkende funktioner som [proxy'er](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Proxy) var lige så tilgængelige for udviklere som [generatorer](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*), der havde meget få eller endda ingen kendte problemer. Derfor var det den bedste praksis kun at slå bestemte funktioner til ved at bruge specifikke runtime-flag (fx `--harmony-generators`), eller ved simpelthen at slå dem alle til og derefter bruge et begrænset udsnit.

Adds Danish translation of website #153

Adds Danish translation of website #153

Conversation

mex commented Feb 10, 2015

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

mikeal commented Feb 12, 2015

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

saebekassebil commented Feb 13, 2015

This comment was marked as off-topic.

tjconcept commented Feb 13, 2015

therebelrobot commented Feb 13, 2015

mikeal commented Feb 13, 2015

Fishrock123 commented Feb 13, 2015

tjconcept commented Feb 13, 2015

snostorm commented Feb 27, 2015

snostorm commented Feb 27, 2015

bnb commented Feb 27, 2015

mex commented Feb 27, 2015

therebelrobot commented Mar 2, 2015

saebekassebil commented Mar 3, 2015

mex commented Mar 3, 2015

snostorm commented Mar 3, 2015

tjconcept commented Mar 4, 2015

mex commented Mar 4, 2015

tjconcept commented Mar 4, 2015

mex commented Mar 4, 2015

snostorm commented Mar 4, 2015

mex commented Mar 4, 2015

fhemberger commented Apr 23, 2015

mex commented Apr 23, 2015

fhemberger commented Apr 24, 2015

tjconcept commented Apr 24, 2015