Approval in nodac

nodac/de/basis.json

@@ -156,6 +156,8 @@
         "ambiguous_names_explica": "Sonderseite f\u00fcr die Verwaltung \"zweideutiger Begriffe\". \"Frankfurt\" mag etwa \"Frankfurt am Main\" oder \"Frankfurt an der Oder\" bedeuten. Beide Begriffe sind valide, weshalb eine Autokorrektur in die eine oder andere Richtung nicht sinnvoll einzurichten ist. So ist nicht zu verhindern, dass zweideutige Begriffe regelm\u00e4\u00dfig in die kontrollierten Vokabulare gelangen. Umso wichtiger ist, sie schnell zu bereinigen und zu spezifizieren. Entsprechend bestehen Suchfunktionen f\u00fcr das finden als \"zweideutig\" markierter Begriffe.",
         "list_search": "Liste \/ Suche",
         "visualize_selection": "Auswahl visualisieren",
-        "store_search_explica": "Gespeicherte Suchabfragen werden als Kacheln auf dem Dashboard angezeigt. Dort ist neben einem Link eine \u00dcbersicht der neuesten passenden Begriffe zu sehen."
+        "store_search_explica": "Gespeicherte Suchabfragen werden als Kacheln auf dem Dashboard angezeigt. Dort ist neben einem Link eine \u00dcbersicht der neuesten passenden Begriffe zu sehen.",
+        "print_generate_report": "Drucken \/ Report generieren",
+        "print_generate_report_explica": "Generiert eine Druckansicht mit Visualisierungen und allen Treffern. Dies kann insbesondere im Kontext von Projekten n\u00fctzlich sein. So l\u00e4sst sich der urspr\u00fcngliche Zustand speichern und sp\u00e4ter mit dem derzeitigen Arbeitsstand vergleichen."
     }
 }

nodac/en/basis.json

@@ -156,6 +156,8 @@
         "ambiguous_names_explica": "Special page to allow the management of ambiguous names for entries. E.g. \"Frankfurt\" may refer to \"Frankfurt am Main\" and \"Frankfurt an der Oder\", which are both valid terms in their own right. Hence, no autocorrection can be established and the ambiguous term needs to be regularly cleaned from the vocabularies. This lists helps identifying newly added entries named using such ambiguous terms so as to clean \/ remove them again.",
         "list_search": "List \/ search",
         "visualize_selection": "Visualize selection",
-        "store_search_explica": "Stored searches are displayed on the dashboard. They are linked along with a list of the newest results so you can immediately see changes."
+        "store_search_explica": "Stored searches are displayed on the dashboard. They are linked along with a list of the newest results so you can immediately see changes.",
+        "print_generate_report": "Print \/ generate report",
+        "print_generate_report_explica": "Generates a print view featuring visualizations and all matched entries. This can be useful in the context of projects to pinpoint the original situation at the start of a task and compare it against the current status to see progress."
     }
 }

nodac/hu/basis.json

@@ -156,6 +156,8 @@
         "ambiguous_names_explica": "Special page to allow the management of ambiguous names for entries. E.g. \"Frankfurt\" may refer to \"Frankfurt am Main\" and \"Frankfurt an der Oder\", which are both valid terms in their own right. Hence, no autocorrection can be established and the ambiguous term needs to be regularly cleaned from the vocabularies. This lists helps identifying newly added entries named using such ambiguous terms so as to clean \/ remove them again.",
         "list_search": "List \/ search",
         "visualize_selection": "Visualize selection",
-        "store_search_explica": "Stored searches are displayed on the dashboard. They are linked along with a list of the newest results so you can immediately see changes."
+        "store_search_explica": "Stored searches are displayed on the dashboard. They are linked along with a list of the newest results so you can immediately see changes.",
+        "print_generate_report": "Print \/ generate report",
+        "print_generate_report_explica": "Generates a print view featuring visualizations and all matched entries. This can be useful in the context of projects to pinpoint the original situation at the start of a task and compare it against the current status to see progress."
     }
 }

nodac/id/basis.json

@@ -156,6 +156,8 @@
         "ambiguous_names_explica": "Special page to allow the management of ambiguous names for entries. E.g. \"Frankfurt\" may refer to \"Frankfurt am Main\" and \"Frankfurt an der Oder\", which are both valid terms in their own right. Hence, no autocorrection can be established and the ambiguous term needs to be regularly cleaned from the vocabularies. This lists helps identifying newly added entries named using such ambiguous terms so as to clean \/ remove them again.",
         "list_search": "List \/ search",
         "visualize_selection": "Visualize selection",
-        "store_search_explica": "Stored searches are displayed on the dashboard. They are linked along with a list of the newest results so you can immediately see changes."
+        "store_search_explica": "Stored searches are displayed on the dashboard. They are linked along with a list of the newest results so you can immediately see changes.",
+        "print_generate_report": "Print \/ generate report",
+        "print_generate_report_explica": "Generates a print view featuring visualizations and all matched entries. This can be useful in the context of projects to pinpoint the original situation at the start of a task and compare it against the current status to see progress."
     }
 }

nodac/ro/basis.json

@@ -156,6 +156,8 @@
         "ambiguous_names_explica": "Special page to allow the management of ambiguous names for entries. E.g. \"Frankfurt\" may refer to \"Frankfurt am Main\" and \"Frankfurt an der Oder\", which are both valid terms in their own right. Hence, no autocorrection can be established and the ambiguous term needs to be regularly cleaned from the vocabularies. This lists helps identifying newly added entries named using such ambiguous terms so as to clean \/ remove them again.",
         "list_search": "List \/ search",
         "visualize_selection": "Visualize selection",
-        "store_search_explica": "Stored searches are displayed on the dashboard. They are linked along with a list of the newest results so you can immediately see changes."
+        "store_search_explica": "Stored searches are displayed on the dashboard. They are linked along with a list of the newest results so you can immediately see changes.",
+        "print_generate_report": "Print \/ generate report",
+        "print_generate_report_explica": "Generates a print view featuring visualizations and all matched entries. This can be useful in the context of projects to pinpoint the original situation at the start of a task and compare it against the current status to see progress."
     }
 }

nodac/ru/basis.json

@@ -156,6 +156,8 @@
         "ambiguous_names_explica": "Special page to allow the management of ambiguous names for entries. E.g. \"Frankfurt\" may refer to \"Frankfurt am Main\" and \"Frankfurt an der Oder\", which are both valid terms in their own right. Hence, no autocorrection can be established and the ambiguous term needs to be regularly cleaned from the vocabularies. This lists helps identifying newly added entries named using such ambiguous terms so as to clean \/ remove them again.",
         "list_search": "List \/ search",
         "visualize_selection": "Visualize selection",
-        "store_search_explica": "Stored searches are displayed on the dashboard. They are linked along with a list of the newest results so you can immediately see changes."
+        "store_search_explica": "Stored searches are displayed on the dashboard. They are linked along with a list of the newest results so you can immediately see changes.",
+        "print_generate_report": "Print \/ generate report",
+        "print_generate_report_explica": "Generates a print view featuring visualizations and all matched entries. This can be useful in the context of projects to pinpoint the original situation at the start of a task and compare it against the current status to see progress."
     }
 }

nodac/uk/basis.json

@@ -156,6 +156,8 @@
         "ambiguous_names_explica": "Special page to allow the management of ambiguous names for entries. E.g. \"Frankfurt\" may refer to \"Frankfurt am Main\" and \"Frankfurt an der Oder\", which are both valid terms in their own right. Hence, no autocorrection can be established and the ambiguous term needs to be regularly cleaned from the vocabularies. This lists helps identifying newly added entries named using such ambiguous terms so as to clean \/ remove them again.",
         "list_search": "List \/ search",
         "visualize_selection": "Visualize selection",
-        "store_search_explica": "Stored searches are displayed on the dashboard. They are linked along with a list of the newest results so you can immediately see changes."
+        "store_search_explica": "Stored searches are displayed on the dashboard. They are linked along with a list of the newest results so you can immediately see changes.",
+        "print_generate_report": "Print \/ generate report",
+        "print_generate_report_explica": "Generates a print view featuring visualizations and all matched entries. This can be useful in the context of projects to pinpoint the original situation at the start of a task and compare it against the current status to see progress."
     }
 }