Translate content to Dutch #1750

tunetheweb · 2020-12-11T17:57:36Z

These are the core templates - without which we cannot release any translated chapters. They are in the language specific templates directory:

base.html - @noah-vdv
base_chapter.html- @noah-vdv
error.html- @noah-vdv

2024

2022

base.html -
contributors.html -
index.html -
table_of_contents.html -

2021

2020

base.html - @noah-vdv
contributors.html - @noah-vdv
index.html - @noah-vdv
table_of_contents.html - @noah-vdv

2019

base.html - @noah-vdv
contributors.html - @noah-vdv
index.html - @noah-vdv
table_of_contents.html - @noah-vdv

These are the chapters to be translated. They exist in the content directory:

2024

2022

2021

2020

2019

Additionally the following pages need translated too in the language specific templates directory:

2021/methodology.html -
2019/methodology.html - @noah-vdv
2020/methodology.html - @noah-vdv
accessibility_statement.html - @noah-vdv
accessibility_statement.html additional update - @VictorLeP Add Dutch accessibility statement translation extra piece #2596
base_ebook.htm - @noah-vdv

There is no need to translate the chapters HTML pages as they are generated off the markdown combined with the above templates.

Please include "Makes progress on #1750" in all pull requests so a link is created from the PR to this issue.

Common notes for writing consistency are here: https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Translators'-Guide. Feel free to edit that and/or add Dutch-specific extras by editing this comment.

Dutch specific extra advice:

strangernr7 · 2020-12-11T19:17:48Z

So the html files don't need to be translated right? Just the files under 2020, 2019 and additional files?

tunetheweb · 2020-12-11T19:31:09Z

The core html files DO need to be translated.

The chapter HTMLs not shown above (e.g. performance.html) do not need to be translated as they are generated from the markdown (e.g. performance.md). We used to store these generated chapter HTML files in git, but no longer do so probably can remove the statement related to that as probably more confusing than useful. Then again if you run the site locally (see instructions in src/README.md) then it will generate these files but they can be ignored from translation point of view.

That make sense, or have a just confused you more than helped? 😀

strangernr7 · 2020-12-11T19:32:34Z

alright, nah that helped thanks

rviscomi · 2020-12-15T00:43:56Z

@noah-vdv thanks for your help translating this content! I see the base templates have been checked off. Have those translations been submitted yet?

strangernr7 · 2020-12-15T06:10:23Z

@noah-vdv thanks for your help translating this content! I see the base templates have been checked off. Have those translations been submitted yet?

No problem.
I have checked them off indeed but realized that I might have translated bits that didn't need translating and totally forgot to check if some pieces needed the <lang="en"> tags. So I'll double-check those html files and get a PR out on Thursday hopefully.

tunetheweb · 2020-12-15T06:14:32Z

Feel free to open a draft PR for now and I can give feedback.

To @rviscomi ’s point we normally put your name beside something you’re working on (so others don’t work on it too) but only tick it off after PR is accepted to show its “done”. I’ve updated the first comment to that now.

tunetheweb · 2020-12-15T06:28:25Z

BTW since you've done the base templates we're ready to send this language live so (at the risk of making this PR even bigger!) can you add Dutch to server/language.py (lines 45-54) and also add nl to supported_languages in config/2019.json and config/2029.json?

strangernr7 · 2020-12-17T13:15:50Z

Should I translate content such as First Input Delay or keep it as is?

tunetheweb · 2020-12-17T13:24:56Z

Should I translate content such as First Input Delay or keep it as is?

I would say not as it's a technical term. Not quite code, but close enough. Maybe add the Dutch translation after first time it's used.

strangernr7 · 2021-01-15T18:07:54Z

What has changed in the 2020 base.html file for it to be translated?

tunetheweb · 2021-01-15T18:10:43Z

Oh. Looks like you already got the foreword. Most languages didn't. Will remove that one!

Did you see there were some changes to Markup chapter?

strangernr7 · 2021-01-15T18:15:47Z

Oh. Looks like you already got the foreword. Most languages didn't. Will remove that one!

Did you see there were some changes to Markup chapter?

Alright, yeah I'll get to those before I do the seo chapter

strangernr7 · 2021-01-21T13:43:25Z

I was going through the 2020 seo chapter and realized there's still 3 TODO's for authors at around line 500

strangernr7 · 2021-01-21T14:17:11Z

And in some other chapters as well so I'll just do those later

tunetheweb · 2021-01-21T14:23:47Z

I was going through the 2020 seo chapter and realized there's still 3 TODO's for authors at around line 500

Good spot. I've reviewed them and happy to just remove them. I count 4 though not three (though one is not marked as a TODO but a Note):

almanac.httparchive.org/src/content/en/2020/seo.md

Line 504 in 997997b

    
           {# TODO(authors): Why are the growth of bandwidth and ubiquity of smartphones contributors to image heaviness? #}

Seems pretty obvious to me so don't think it needs further comment. Maybe it was added since that comment was added.

almanac.httparchive.org/src/content/en/2020/seo.md

Line 517 in 997997b

    
           {# TODO(authors): Add your interpretation of these results. What do you hope readers get from it? #}

Yeah would have been nice to have some interpretation rather than just the stats, but not only chapter to do this, so let's leave for now and remove the TODO.

almanac.httparchive.org/src/content/en/2020/seo.md

Line 531 in 997997b

    
           {# TODO(authors, analysts): I don't think the interpretation of these stats was correct, so I edited out anything that I didn't think was accurate. Please double check my edit and feel free to expand on it. Note that this is incompatible with last year's stat because that was a Lighthouse audit checking that all images have alt attributes, while this data was calculated directly from the markup. There's something off if 40+% of pages have perfect alt coverage, but this chart has less than perfect coverage at the 75th percentile. Either coverage got much _worse_ this year or they're measuring different things. For example Lighthouse may be more lenient about which images should have alt attributes. Do you have those audit results based on 2020 data here for better comparison? #}

Rick edited this and I trust his understanding of Lighthouse so to me this is just a comment for Authors during review so TODO can be removed.

almanac.httparchive.org/src/content/en/2020/seo.md

Line 779 in 997997b

    
           {# NOTE(authors): I've made some ruthless edits to this section to remove everything related to synthetic measurement of CWV, including the entire Lighthouse discussion, which is orthogonal to the real-user aspect of CWV. Please push back if you disagree with any of these edits. #}

Same as above so TODO can be removed.

Would you mind removing them from English version too as part of this PR?

And in some other chapters as well so I'll just do those later

I'll try to review those similarly and submit a PR for them. I see Compression, JavaScript, Privacy (currently under re-review anyway), Resource-Hints (this TODO can be removed), Security (not edited yet anyway), and SEO (discussed above). Hold off translating them for now but SEO and Resource Hints can be done.

strangernr7 · 2021-03-14T22:04:58Z

Just a heads up: the 2020 ecommerce chapter has #jrharalson_bio: TODO above the Intro
And I'm pretty sure featured_stat_label_1: Mobile sizes identified as ecommerce sites should be Mobile sites

tunetheweb · 2021-03-15T11:16:58Z

Yeah we never got a bio from @jrharalson - Jason if you see this and wanna provide one then please do. It appears at the bottom of the chapter.

Agree on the featured stat correction.

strangernr7 · 2021-04-04T12:50:54Z

almanac.httparchive.org/src/content/en/2020/caching.md

Line 121 in 26509af

    
           *Caching entity*: The hardware or software that is doing the caching. Due to the focus of this chapter, we use "browser" as a synonym for "caching entity" unless otherwise specified.

Should Caching entity stay as is or be translated? As well as anywhere else in the chapter

tunetheweb · 2021-04-04T14:45:57Z

I would translate it. It's not a technical term as such. Same for Eviction and Revalidation further down that list. On the other hand, Time to Live (TTL) is a well-known technical term so I wouldn't translate that,

strangernr7 · 2021-04-04T20:01:50Z

almanac.httparchive.org/src/content/en/2020/caching.md

Line 200 in 26509af

    
           While we see a slight increase in the use of the `Cache-Control` header (1.8%), we also see a minimal decrease in the use of the older `Expires` header (0.2%). On Desktop we actually see a marginal increase of `Cache-Control` (1.3%), with a smaller increase on `Expiries` (0.8%) Effectively, more desktop sites look to be adding `Cache-Control` header without the `Expires` header.

Also, I noticed Expiries instead of Expires, that's a typo right?

tunetheweb · 2021-04-04T20:22:59Z

Yup! Good spot. If you could fix as part of your translation pull request that would be much appreciated!

rviscomi · 2021-04-14T03:14:55Z

Wow only 3 chapters to go! Thank you @noah-vdv for your amazing effort!!

tunetheweb · 2021-10-19T00:04:51Z

Hey @noah-vdv any chance we could persuade you back to finish off the final to chapters for 2020? Once we have those we can publish the ebook in Dutch! And we’ll even print a copy as a small token of our appreciation you for your efforts!

strangernr7 · 2021-10-19T10:10:38Z

Hey @noah-vdv any chance we could persuade you back to finish off the final to chapters for 2020?

Hey, wow time has flown! Didn't realise how long ago I had last worked on this. Anyways, yeah of course! However, I don't have as much spare time as before but I'll try my best to get it done, hopefully, by November.

Once we have those we can publish the ebook in Dutch! And we’ll even print a copy as a small token of our appreciation you for your efforts!

Awesome!! Looking forward to finishing it off! 👍

tunetheweb · 2021-11-17T20:14:09Z

We added a small note to our Accessibility Statement about colour contrast issues:

almanac.httparchive.org/src/templates/nl/accessibility_statement.html

Lines 69 to 71 in 14f8512

    
           {# TODO - Translate this <p> 
        
             In some chapters, we also include other content on the site, not created by ourselves, including YouTube videos, PDF links or links to other articles, which do not meet the strict criteria required of WCAG 2.1 level AAA. See note below on external content. 
        
           </p> #}

Would be great if someone could translate this (@noah-vdv ?). Very small and easy!

strangernr7 · 2021-11-26T17:00:47Z

"In sommige hoofdstukken nemen we ook andere inhoud op de site op, die niet door onszelf is gemaakt, waaronder YouTube-video's, pdf-links of links naar andere artikelen, die niet voldoen aan de strikte criteria die vereist zijn voor WCAG 2.1 level AAA. Zie onderstaande opmerking over externe inhoud."

Hey, wow time has flown! Didn't realise how long ago I had last worked on this. Anyways, yeah of course! However, I don't have as much spare time as before but I'll try my best to get it done, hopefully, by November.

Also, i hate to disappoint, but this is taking more time as I need to spend more time on my study than expected. I, unfortunately can't give you an eta yet.

tunetheweb · 2021-11-26T17:35:35Z

No probs. Thanks for that translation.

tunetheweb · 2021-11-27T08:13:23Z

Doh! Looks like I gave you the wrong bit of text to translate above :-( That was the next paragraph that was already translated. This was the paragraph I actually wanted translated:

We recognize that some of the color choices for our visualizations do not meet WCAG color contrast requirements. We make a conscious effort to use the more contrasting colors and labels to reduce the impact of this. We hope the detailed descriptions, as well as access to the underlying data itself can help with this issue. We aim to improve the accessibility of our visualization color schemes in future years.

VictorLeP · 2021-11-27T15:02:06Z

We erkennen dat sommige keuzes voor kleuren in onze visualisaties niet voldoen aan de kleurcontrastvereisten van de WCAG. We doen een bewuste inspanning om de meer contrasterende kleuren en opschriften te gebruiken om de impact hiervan te verminderen. We hopen dat de gedetailleerde beschrijvingen alsook toegang tot de onderliggende gegevens zelf kunnen helpen met dit probleem. We streven ernaar de toegankelijkheid van de kleurschema's in onze visualisaties de komende jaren te verbeteren.

tunetheweb · 2021-11-27T15:08:37Z

Bedankt @VictorLeP ! Zeer gewaardeerd.

VictorLeP · 2021-11-27T16:15:23Z

Will also take a stab at translating this year's Privacy chapter (since @noah-vdv is busy).

tunetheweb added the translation world wide web label Dec 11, 2020

tunetheweb added this to the 2020 Content Translation milestone Dec 11, 2020

tunetheweb assigned strangernr7 Dec 11, 2020

tunetheweb mentioned this issue Dec 11, 2020

Join the Translators team #923

Open

This was referenced Dec 15, 2020

Added Dutch base templates #1767

Merged

added 2019 accessibility chapter in dutch #1775

Closed

Translate 2019 Accessibility chapter to Dutch #1776

Merged

This was referenced Dec 17, 2020

translated 2020/performance to Dutch #1791

Merged

translated Javascript 2020 dutch #1803

Merged

tunetheweb added the good first issue Good for newcomers label Dec 19, 2020

This was referenced Dec 20, 2020

Translated 2020 Markup in Dutch #1814

Merged

Translated CMS 2020 to Dutch #1820

Merged

strangernr7 mentioned this issue Jan 15, 2021

translate 2020 Capabilities chapter to Dutch #1889

Merged

strangernr7 mentioned this issue Jan 19, 2021

Remove TODO's from nl 2020 markup #1905

Merged

This was referenced Mar 11, 2021

Translation of the 2020 mobile web chapter to Dutch #2064

Merged

Translation of the 2020 Media chapter to Dutch #2066

Merged

This was referenced Mar 20, 2021

Dutch 2020 Ecommerce chapter translation #2085

Merged

Update nl/ecommerce #2095

Merged

Translation of the 2020 Privacy chapter to Dutch #2101

Merged

strangernr7 mentioned this issue Apr 2, 2021

Translate the 2020 http2 chapter to Dutch #2112

Merged

strangernr7 mentioned this issue May 1, 2021

Translation of the 2020 Caching chapter to Dutch #2181

Merged

tunetheweb mentioned this issue Nov 27, 2021

Add Dutch accessibility statement translation extra piece #2596

Merged

VictorLeP mentioned this issue Nov 30, 2021

Privacy 2021: Dutch translation #2628

Merged

rviscomi modified the milestones: 2020 Content Translation, 2021 Content Translation Dec 2, 2021

VictorLeP mentioned this issue Feb 8, 2022

Fix typo in Dutch translation for Privacy 2021 #2809

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Translate content to Dutch #1750

Translate content to Dutch #1750

tunetheweb commented Dec 11, 2020 •

edited

Loading

strangernr7 commented Dec 11, 2020

tunetheweb commented Dec 11, 2020 •

edited

Loading

strangernr7 commented Dec 11, 2020

rviscomi commented Dec 15, 2020

strangernr7 commented Dec 15, 2020

tunetheweb commented Dec 15, 2020 •

edited

Loading

tunetheweb commented Dec 15, 2020

strangernr7 commented Dec 17, 2020

tunetheweb commented Dec 17, 2020

strangernr7 commented Jan 15, 2021

tunetheweb commented Jan 15, 2021

strangernr7 commented Jan 15, 2021

strangernr7 commented Jan 21, 2021

strangernr7 commented Jan 21, 2021

tunetheweb commented Jan 21, 2021 •

edited

Loading

strangernr7 commented Mar 14, 2021 •

edited

Loading

tunetheweb commented Mar 15, 2021

strangernr7 commented Apr 4, 2021 •

edited

Loading

tunetheweb commented Apr 4, 2021

strangernr7 commented Apr 4, 2021

tunetheweb commented Apr 4, 2021

rviscomi commented Apr 14, 2021

tunetheweb commented Oct 19, 2021

strangernr7 commented Oct 19, 2021

tunetheweb commented Nov 17, 2021 •

edited

Loading

strangernr7 commented Nov 26, 2021

tunetheweb commented Nov 26, 2021

tunetheweb commented Nov 27, 2021

VictorLeP commented Nov 27, 2021

tunetheweb commented Nov 27, 2021

VictorLeP commented Nov 27, 2021

Translate content to Dutch #1750

Translate content to Dutch #1750

Comments

tunetheweb commented Dec 11, 2020 • edited Loading

strangernr7 commented Dec 11, 2020

tunetheweb commented Dec 11, 2020 • edited Loading

strangernr7 commented Dec 11, 2020

rviscomi commented Dec 15, 2020

strangernr7 commented Dec 15, 2020

tunetheweb commented Dec 15, 2020 • edited Loading

tunetheweb commented Dec 15, 2020

strangernr7 commented Dec 17, 2020

tunetheweb commented Dec 17, 2020

strangernr7 commented Jan 15, 2021

tunetheweb commented Jan 15, 2021

strangernr7 commented Jan 15, 2021

strangernr7 commented Jan 21, 2021

strangernr7 commented Jan 21, 2021

tunetheweb commented Jan 21, 2021 • edited Loading

strangernr7 commented Mar 14, 2021 • edited Loading

tunetheweb commented Mar 15, 2021

strangernr7 commented Apr 4, 2021 • edited Loading

tunetheweb commented Apr 4, 2021

strangernr7 commented Apr 4, 2021

tunetheweb commented Apr 4, 2021

rviscomi commented Apr 14, 2021

tunetheweb commented Oct 19, 2021

strangernr7 commented Oct 19, 2021

tunetheweb commented Nov 17, 2021 • edited Loading

strangernr7 commented Nov 26, 2021

tunetheweb commented Nov 26, 2021

tunetheweb commented Nov 27, 2021

VictorLeP commented Nov 27, 2021

tunetheweb commented Nov 27, 2021

VictorLeP commented Nov 27, 2021

tunetheweb commented Dec 11, 2020 •

edited

Loading

tunetheweb commented Dec 11, 2020 •

edited

Loading

tunetheweb commented Dec 15, 2020 •

edited

Loading

tunetheweb commented Jan 21, 2021 •

edited

Loading

strangernr7 commented Mar 14, 2021 •

edited

Loading

strangernr7 commented Apr 4, 2021 •

edited

Loading

tunetheweb commented Nov 17, 2021 •

edited

Loading