diff --git a/nodac/de/basis.json b/nodac/de/basis.json index 27f7c583..ddcf8c11 100644 --- a/nodac/de/basis.json +++ b/nodac/de/basis.json @@ -153,6 +153,7 @@ "open_update_log": "\u00d6ffnet ein einfaches Log der Bearbeitungen des derzeitigen Eintrags und zeigt die jeweiligen Bearbeitenden an.", "versioning": "Versionierung", "versioning_explica": "\u00d6ffnet ein Overlay, dass die gesamte aufgezeichnete Versionsgeschichte des gegebenen Eintrags anzeigt.", - "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." + "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" } } \ No newline at end of file diff --git a/nodac/en/basis.json b/nodac/en/basis.json index 6f3c142e..a19d9ad4 100644 --- a/nodac/en/basis.json +++ b/nodac/en/basis.json @@ -153,6 +153,7 @@ "open_update_log": "Opens a simple log of what updates happened to the current entry and by whom.", "versioning": "Versioning", "versioning_explica": "Opens a full versioning overlay displaying all tracked changes to the current entry over time.", - "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." + "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" } } \ No newline at end of file diff --git a/nodac/hu/basis.json b/nodac/hu/basis.json index 2e5d95c4..d02f2e56 100644 --- a/nodac/hu/basis.json +++ b/nodac/hu/basis.json @@ -153,6 +153,7 @@ "open_update_log": "Opens a simple log of what updates happened to the current entry and by whom.", "versioning": "Versioning", "versioning_explica": "Opens a full versioning overlay displaying all tracked changes to the current entry over time.", - "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." + "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" } } \ No newline at end of file diff --git a/nodac/id/basis.json b/nodac/id/basis.json index 1f0a430f..9327cf81 100644 --- a/nodac/id/basis.json +++ b/nodac/id/basis.json @@ -153,6 +153,7 @@ "open_update_log": "Opens a simple log of what updates happened to the current entry and by whom.", "versioning": "Versioning", "versioning_explica": "Opens a full versioning overlay displaying all tracked changes to the current entry over time.", - "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." + "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" } } \ No newline at end of file diff --git a/nodac/ro/basis.json b/nodac/ro/basis.json index 6f3c142e..a19d9ad4 100644 --- a/nodac/ro/basis.json +++ b/nodac/ro/basis.json @@ -153,6 +153,7 @@ "open_update_log": "Opens a simple log of what updates happened to the current entry and by whom.", "versioning": "Versioning", "versioning_explica": "Opens a full versioning overlay displaying all tracked changes to the current entry over time.", - "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." + "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" } } \ No newline at end of file diff --git a/nodac/ru/basis.json b/nodac/ru/basis.json index 0934c02c..3e5120d9 100644 --- a/nodac/ru/basis.json +++ b/nodac/ru/basis.json @@ -153,6 +153,7 @@ "open_update_log": "Opens a simple log of what updates happened to the current entry and by whom.", "versioning": "Versioning", "versioning_explica": "Opens a full versioning overlay displaying all tracked changes to the current entry over time.", - "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." + "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" } } \ No newline at end of file diff --git a/nodac/uk/basis.json b/nodac/uk/basis.json index 7cd67380..3b3d3b9a 100644 --- a/nodac/uk/basis.json +++ b/nodac/uk/basis.json @@ -153,6 +153,7 @@ "open_update_log": "Opens a simple log of what updates happened to the current entry and by whom.", "versioning": "Versioning", "versioning_explica": "Opens a full versioning overlay displaying all tracked changes to the current entry over time.", - "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." + "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" } } \ No newline at end of file