From a7b37ce247e44d6a75f65da0e3846f301ff1705f Mon Sep 17 00:00:00 2001 From: dhvenema Date: Wed, 29 Mar 2017 12:29:19 +0200 Subject: [PATCH] l10n Dutch translations (closes #1170) --- js/core/issues-notes.js | 278 ++++++++++++++++++++-------------------- 1 file changed, 139 insertions(+), 139 deletions(-) diff --git a/js/core/issues-notes.js b/js/core/issues-notes.js index 59a6683e0f..828f9f911d 100644 --- a/js/core/issues-notes.js +++ b/js/core/issues-notes.js @@ -1,139 +1,139 @@ -// Module core/issues-notes -// Manages issues and notes, including marking them up, numbering, inserting the title, -// and injecting the style sheet. -// These are elements with classes "issue" or "note". -// When an issue or note is found, it is reported using the "issue" or "note" event. This can -// be used by a containing shell to extract all of these. -// Issues are automatically numbered by default, but you can assign them specific numbers (or, -// despite the name, any arbitrary identifier) using the data-number attribute. Note that as -// soon as you use one data-number on any issue all the other issues stop being automatically -// numbered to avoid involuntary clashes. -// If the configuration has issueBase set to a non-empty string, and issues are -// manually numbered, a link to the issue is created using issueBase and the issue number -"use strict"; -define([ - "core/pubsubhub", - "deps/text!core/css/issues-notes.css", - "github", - ], - function(pubsubhub, css, github) { - return { - run: function(conf, doc, cb) { - function handleIssues($ins, ghIssues, issueBase) { - $(doc).find("head link").first().before($("