From d35c4933804a5761cd7f278422e7fd7439052bd7 Mon Sep 17 00:00:00 2001
From: Thijs Kinkhorst <thijs@kinkhorst.com>
Date: Tue, 15 Aug 2017 12:39:03 +0000
Subject: [PATCH] Remove references to discontinued translation portal.
---
docs/simplesamlphp-maintenance.md | 4 ----
docs/simplesamlphp-translation.md | 4 ----
modules/consent/dictionaries/consent.php | 9 ---------
3 files changed, 17 deletions(-)
diff --git a/docs/simplesamlphp-maintenance.md b/docs/simplesamlphp-maintenance.md
index 463b33c0e..cd78803e5 100644
--- a/docs/simplesamlphp-maintenance.md
+++ b/docs/simplesamlphp-maintenance.md
@@ -253,10 +253,6 @@ Please use the standardized two-character
You also can set the default language. You should ensure that the default language is complete, as it is used as a fallback when a text is not available in the language selected by the user.
-Translation of SimpleSAMLphp is done through the SimpleSAMLphp translation portal. To translate SimpleSAMLphp to a new language, please contact the authors at the mailing list, and the new language may be added to the translation portal.
-
- * [Visit the SimpleSAMLphp translation portal](https://translation.rnd.feide.no/?aid=simplesamlphp)
-
All strings that can be localized are found in the files `dictionaries/`. Add a new entry for each string, with your language code, like this:
'user_pass_header' => array(
diff --git a/docs/simplesamlphp-translation.md b/docs/simplesamlphp-translation.md
index da9766b03..b6cb10afc 100644
--- a/docs/simplesamlphp-translation.md
+++ b/docs/simplesamlphp-translation.md
@@ -27,8 +27,6 @@ When the template library is about to lookup the translation of a term, it will
* the definition file, for the English translation, and
* the translation file, for translation to other languages.
-When developing new functionalities it is common to start by just introducing the definition file, then upload the definition file to the SimpleSAMLphp translation portal, perform translation, and then download the translation files back in to the module.
-
SimpleSAMLphp will always fallback to the English translation using the definition file, both:
* when the term is not translated into the *current selected language*, and
@@ -74,8 +72,6 @@ To summarize the pattern of the definition file is as follows:
The translation file is similar to the definition file, but including translation to languages others than English.
-This file is recommended to never write manually, but instead use the SimpleSAMLphp translation portal, and then download generated translation files.
-
The structure of the file is identical to the definition files, except from the language index, which now is not `en`, but the actual langauge that is translated:
diff --git a/modules/consent/dictionaries/consent.php b/modules/consent/dictionaries/consent.php
index 34c63552d..cdf77fec0 100644
--- a/modules/consent/dictionaries/consent.php
+++ b/modules/consent/dictionaries/consent.php
@@ -1,14 +1,5 @@
<?php
-/*
- * DO NOT EDIT THIS FILE MANUALLY.
- * If you want to contribute to translation, you must instead use the
- * SimpleSAMLphp translation portal:
- * https://translation.rnd.feide.no/index.php?aid=simplesamlphp
- *
- * This file is automatically generated from the translation portal.
- */
-
$lang = array(
'yes' => array (
'no' => 'Ja, fortsett',
--
GitLab