museum-digital/translation-json
34
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Approval in nodac

Browse Source
This commit is contained in:
Joshua Ramon Enslin 2024-09-22 21:17:09 +00:00 committed by md translation bot
parent 82a2182598
commit 665e5f4fa6
7 changed files with 14 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
nodac/de/basis.json
View File

@ -154,6 +154,7 @@
"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.",
"list_search": "Liste \/ Suche"
"list_search": "Liste \/ Suche",
"visualize_selection": "Auswahl visualisieren"
}
}

3
nodac/en/basis.json
View File

@ -154,6 +154,7 @@
"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.",
"list_search": "List \/ search"
"list_search": "List \/ search",
"visualize_selection": "Visualize selection"
}
}

3
nodac/hu/basis.json
View File

@ -154,6 +154,7 @@
"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.",
"list_search": "List \/ search"
"list_search": "List \/ search",
"visualize_selection": "Visualize selection"
}
}

3
nodac/id/basis.json
View File

@ -154,6 +154,7 @@
"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.",
"list_search": "List \/ search"
"list_search": "List \/ search",
"visualize_selection": "Visualize selection"
}
}

3
nodac/ro/basis.json
View File

@ -154,6 +154,7 @@
"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.",
"list_search": "List \/ search"
"list_search": "List \/ search",
"visualize_selection": "Visualize selection"
}
}

3
nodac/ru/basis.json
View File

@ -154,6 +154,7 @@
"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.",
"list_search": "List \/ search"
"list_search": "List \/ search",
"visualize_selection": "Visualize selection"
}
}

3
nodac/uk/basis.json
View File

@ -154,6 +154,7 @@
"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.",
"list_search": "List \/ search"
"list_search": "List \/ search",
"visualize_selection": "Visualize selection"
}
}