- Can started to work on the Turkish translation.

- Carrey continued proofreading the English translation.
- Mariam continued translating to Arabic.

backend/de/check.json

@@ -3,7 +3,7 @@
         "to_short": "Das eingegebene Schlagwort war zu kurz",
         "you_entered": "Ihre Eingabe lautete",
         "already_known_as": "Dieser Begriff ist bereits bekannt als",
-        "unknown": "Dieser Begriff ist unbekannt",
+        "unknown": "Dieser Begriff ist als <a class=\"textRed\">Schlagwort<\/a> unbekannt",
         "proposals": "Vielleicht meinten Sie einen der folgenden Begriffe",
         "persons_to_events": "Personen\/Institutionen sollten immer \u00fcber Ereignisse verkn\u00fcpft werden! Wenn die Person beispielsweise \"abgebildet wurde\" oder \"hergestellt hat\", dann geben Sie bitte unbedingt ein Ereignis ein",
         "place_to_events": "Orte sollten immer \u00fcber Ereignisse verkn\u00fcpft werden! Wenn der Ort beispielsweise \"Herstellungsort\" oder \"Nutzungsort\" ist, dann geben Sie bitte unbedingt ein Ereignis ein",

backend/en/overview.json

@@ -14,10 +14,11 @@
         "places": "Place names",
         "literature": "Literature",
         "links": "Links",
-        "tags": "Key word",
+        "tags": "Keywords",
         "access_to": "Access to",
         "additions": "Additions",
         "edits": "Edits",
-        "objects_visible": "Objects (Visible)"
+        "objects_visible": "Objects (Visible)",
+        "18": ""
     }
 }

backend/en/quality.json

@@ -25,7 +25,7 @@
         "no_tag": "No keyword (or general asignment) provided. (Ideal: 3-9)",
         "one_tag": "Only one keyword (or general asignment) provided. (Ideal: 3-9)",
         "two_tags": "Two keywords (or general asignments) provided. (Ideal: 3-9)",
-        "tree_nine__tags": "Key Words (or general asignments) provided. (Ideal: 3-9)",
+        "tree_nine__tags": "Keywords (or general asignments) provided. (Ideal: 3-9)",
         "too_many__tags": "10 or more keywords (or general asignments) provided. (Ideal: 3-9)",
         "literature_asigned": "Literature assigned to the object",
         "online_resources_asigned": "Online resources assigned to the object",

backend/tr/action.json

@@ -1,20 +1,20 @@
 {
     "action": {
-        "museum_choose": "Ein Museum zum Bearbeiten ausw\u00e4hlen ...",
+        "museum_choose": "D\u00fczenlemek i\u00e7in bir m\u00fcze se\u00e7 ...",
-        "museum_change": "Ein Museum bearbeiten ...",
+        "museum_change": "Bir m\u00fcze d\u00fczenle ...",
-        "museum_input": "Ein Museum erfassen ...",
+        "museum_input": "Bir m\u00fcze kay\u0131tla ...",
-        "collection_choose": "Eine Sammlung zum Bearbeiten ausw\u00e4hlen ...",
+        "collection_choose": "D\u00fczenlemek i\u00e7in bir koleksiyon se\u00e7 ...",
-        "collection_change": "Eine Sammlung bearbeiten ...",
+        "collection_change": "Koleksiyonu d\u00fczenle ...",
-        "collection_input": "Eine Sammlung erfassen ...",
+        "collection_input": "Koleksiyonu kay\u0131tla ...",
-        "object_choose": "Ein Objekt zum Bearbeiten ausw\u00e4hlen ...",
+        "object_choose": "D\u00fczenlemek i\u00e7in bir obje se\u00e7 ...",
-        "object_change": "Ein Objekt bearbeiten ...",
+        "object_change": "Bir objeyi d\u00fczenle ...",
-        "object_input": "Ein Objekt erfassen ...",
+        "object_input": "Bir objeyi kay\u0131tla ...",
-        "event_choose": "Ein Ereignis zum Bearbeiten ausw\u00e4hlen ...",
+        "event_choose": "D\u00fczenlemek i\u00e7in bir etkinlik se\u00e7 ...",
-        "event_change": "Ein Ereignis bearbeiten ...",
+        "event_change": "Etkinli\u011fi d\u00fczenle ...",
-        "event_input": "Ein Ereignis erfassen ...",
+        "event_input": "Bir etkinlik kay\u0131tla ...",
-        "time_choose": "Einen Zeiteintrag zum Bearbeiten ausw\u00e4hlen ...",
+        "time_choose": "D\u00fczenlemek i\u00e7in bir zaman birimi se\u00e7 ...",
-        "time_change": "Einen Zeiteintrag bearbeiten ...",
+        "time_change": "Bir zaman birimi d\u00fczenle ...",
-        "time_input": "Einen Zeiteintrag erfassen ...",
+        "time_input": "Bir zaman birimi kay\u0131tla ...",
         "actor_choose": "Einen Akteur zum Bearbeiten ausw\u00e4hlen ...",
         "actor_change": "Einen Akteur bearbeiten ...",
         "actor_input": "Einen Akteur erfassen ...",

backend/tr/appointments.json

@@ -1,36 +1,36 @@
 {
     "tlAppointments": {
-        "appointment": "Veranstaltung",
+        "appointment": "Etkinlik",
-        "title": "Titel",
+        "title": "\u00dcnvan",
-        "name_explica": "Name der Veranstaltung",
+        "name_explica": "Etkinligin Ismi",
-        "start_time": "Beginn",
+        "start_time": "Ba\u0219lang\u0131\u00e7",
-        "start_time_explica": "Der Zeitpunkt des Beginns der Veranstaltung.",
+        "start_time_explica": "Ba\u0219lang\u0131\u00e7 zaman\u0131.",
-        "end_time": "Ende",
+        "end_time": "biti\u015f zaman\u0131",
-        "end_time_explica": "Das Ende der Veranstaltung.",
+        "end_time_explica": "Etnkinli\u011fin biti\u015f zaman\u0131",
-        "appointment_belongs": "Institution",
+        "appointment_belongs": "Kurum",
-        "appointment_added": "Eine Veranstaltung wurde hinzugef\u00fcgt.",
+        "appointment_added": "Bir etkinlik eklendi.",
-        "description": "Beschreibung",
+        "description": "a\u00e7\u0131klama",
-        "description_explica": "Beschreibung der Veranstaltung.",
+        "description_explica": "Etkinlik a\u00e7\u0131klamas\u0131.",
-        "there_are_no_appointments": "Es gibt hier noch keine Veranstaltungen \/ Termine.",
+        "there_are_no_appointments": "Bu tarihde etkinlik kay\u0131tl\u0131 de\u011fil.",
-        "appointments_list": "Liste Veranstaltungen",
+        "appointments_list": "Etkinlik listesi",
-        "appointment_no_name": "Die Veranstaltung hat keinen Namen",
+        "appointment_no_name": "Etkinlikde isim eksik",
-        "appointments_edit": "Eine Veranstaltung bearbeiten",
+        "appointments_edit": "Etkinli\u011fi d\u00fczenle",
-        "image_uploaded": "Die Abbildung wurde heraufgeladen",
+        "image_uploaded": "Resim y\u00fcklendi",
-        "appointment_deleted": "Der Termin wurde gel\u00f6scht",
+        "appointment_deleted": "Randevu silindi",
-        "image_deleted": "Die Abbildung wurde gel\u00f6scht",
+        "image_deleted": "Resim silindi",
-        "appointment_edited": "Der Termin wurde bearbeitet",
+        "appointment_edited": "Randevu d\u00fczenlendi",
-        "make_public": "Ver\u00f6ffentlichen",
+        "make_public": "Yayinlamak",
-        "make_hidden": "\"Nicht \u00f6ffentlich\" schalten",
+        "make_hidden": "Gizle",
-        "upload_image": "Abbildung heraufladen",
+        "upload_image": "Resim y\u00fckle",
-        "delete_image": "Abbildung l\u00f6schen",
+        "delete_image": "Resimi sil",
-        "start_time_hour": "Stunde",
+        "start_time_hour": "Saat",
-        "start_time_min": "Minute",
+        "start_time_min": "Dakika",
-        "images": "Abbildungen",
+        "images": "Resimler",
-        "url": "URL",
+        "url": "url",
-        "url_explica": "URL einer anderen Webseite, die diese Veranstaltung repr\u00e4sentiert. Muss eine valide URL sein; also mit http:\/\/ oder https:\/\/ beginnen.",
+        "url_explica": "ba\u0219ka bir internetsayfas\u0131n\u0131n url'si, bu etkinligi temsil etmek i\u00e7in, ge\u00e7erli bir url\u2018ye sahip olmasi gerekiyor. B\u00f6ylece http:\/\/ veya https:\/\/ le ba\u015flamas\u0131 gerekiyor.",
-        "allAppointments": "Alle Termine \/ Veranstaltungen",
+        "allAppointments": "B\u00fct\u00fcn randevular \/ etkinlikler",
-        "new_appointment": "Neue Veranstaltung",
+        "new_appointment": "Yeni etkinlik",
-        "base_data": "Basisdaten zur Veranstaltung",
+        "base_data": "Etkinli\u011fe ayit temel veriler",
-        "no_appointments_text": "Es wurde noch kein Termin f\u00fcr Ihr Museum erfasst (entsprechend k\u00f6nnen wir keine auflisten). Sie k\u00f6nnen:"
+        "no_appointments_text": "Sizin m\u00fczenize ayit randevu kay\u0131t\u0131 bulunmamaktad\u0131r (bu y\u00fczden size g\u00f6remiyorsunuz)."
     }
 }

backend/tr/basis.json

@@ -1,108 +1,108 @@
 {
     "basis": {
-        "museum": "Museum",
+        "museum": "m\u00fcze",
-        "museum_choose": "Ein Museum ausw\u00e4hlen",
+        "museum_choose": "Bir m\u00fcze se\u00e7",
-        "museum_change": "Eintrag f\u00fcr Museum \u00e4ndern",
+        "museum_change": "M\u00fcze kay\u0131d\u0131 de\u011fi\u015ftir",
-        "museum_input": "Ein Museum erfassen",
+        "museum_input": "Bir m\u00fcze kay\u0131tla",
-        "collection": "Sammlung",
+        "collection": "koleksiyon",
-        "collection_choose": "Eine Sammlung ausw\u00e4hlen",
+        "collection_choose": "Bir koleksiyon se\u00e7",
-        "collection_change": "Sammlung bearbeiten",
+        "collection_change": "Koleksiyonu d\u00fczenle",
-        "collection_input": "Eine Sammlung erfassen",
+        "collection_input": "Bir koleksiyon kay\u0131tla",
-        "object": "Objekt",
+        "object": "obje",
-        "object_choose": "Ein Objekt ausw\u00e4hlen",
+        "object_choose": "Bir obje se\u00e7",
-        "object_input": "Ein Objekt erfassen",
+        "object_input": "Bir obje kay\u0131tla",
-        "users": "Benutzer",
+        "users": "kullan\u0131c\u0131",
-        "users_choose": "Einen Benutzer ausw\u00e4hlen",
+        "users_choose": "Bir kullan\u0131c\u0131 se\u00e7",
-        "users_input": "Benutzer hinzuf\u00fcgen",
+        "users_input": "kullan\u0131c\u0131 ekle",
-        "basis": "Basis",
+        "basis": "temel",
-        "resource": "Ansicht",
+        "resource": "g\u00f6r\u00fc\u015f",
-        "addendum": "Zusatz",
+        "addendum": "eklem",
-        "administration": "Verwaltung",
+        "administration": "y\u00f6netim",
-        "abode": "Verbleib",
+        "abode": "kalan",
-        "rights": "Rechte",
+        "rights": "haklar",
-        "remarks": "Notizen",
+        "remarks": "notlar",
-        "goes_to": "Geht zu",
+        "goes_to": "gider",
-        "send": "Abschicken",
+        "send": "g\u00f6nder",
-        "again": "Noch einmal",
+        "again": "tekrar",
-        "show": "zeigen",
+        "show": "g\u00f6ster",
-        "search": "Suchen",
+        "search": "ara",
-        "disconnect": "Verkn\u00fcpfung l\u00f6sen",
+        "disconnect": "ay\u0131r",
-        "place": "Ort",
+        "place": "yer",
-        "actor": "Person\/Institution",
+        "actor": "\u015fah\u0131s",
-        "actor_short": "Akteur",
+        "actor_short": "ki\u015fi",
-        "time": "Zeit",
+        "time": "zaman",
-        "tag": "Schlagwort",
+        "tag": "terim",
-        "event": "Ereignis",
+        "event": "etkinlik",
-        "pi_relation": "Person\/Institution-Bezug",
+        "pi_relation": "\u015fah\u0131s ile ilgili ",
-        "place_relation": "Ortsbezug",
+        "place_relation": "yer ile ilgili",
-        "time_related": "Zeitbezug",
+        "time_related": "zaman ile ilgili ",
-        "did_you_mean": "Meinten Sie",
+        "did_you_mean": "demek istedi\u011fin",
-        "choosing_by_clicking": "Auswahl durch Anklicken",
+        "choosing_by_clicking": "t\u0131klayarak se\u00e7erek",
-        "already_known": "Ist schon bekannt",
+        "already_known": "zaten bilinen",
-        "back": "zur\u00fcck",
+        "back": "geri",
-        "found": "Gefunden",
+        "found": "bulunan",
-        "or": "Oder",
+        "or": "veya",
-        "literature": "Literatur",
+        "literature": "literat\u00fcr",
-        "weblink": "Weblink",
+        "weblink": "ba\u011flant\u0131s\u0131",
-        "document": "Dokument",
+        "document": "belge",
-        "single_object": "Einzelobjekt",
+        "single_object": "tek obje",
-        "objectgroup": "Objektgruppe",
+        "objectgroup": "obje gurubu",
-        "objectgroup_choose": "Eine Objektgruppe ausw\u00e4hlen",
+        "objectgroup_choose": "bir obje gurubu se\u00e7",
-        "objectgroup_change": "Eintrag f\u00fcr Objektgruppe \u00e4ndern",
+        "objectgroup_change": "obje gurubu kay\u0131t\u0131 d\u00fczenle",
-        "objectgroup_input": "Eine Objektgruppe erfassen",
+        "objectgroup_input": "obje gurubu kay\u0131tla",
-        "literature_choose": "Einen Literatureintrag ausw\u00e4hlen",
+        "literature_choose": "literat\u00fcr kay\u0131t\u0131 se\u00e7",
-        "literature_change": "Einen Literatureintrag \u00e4ndern",
+        "literature_change": "literat\u00fcr kay\u0131t\u0131 d\u00fczenle",
-        "literature_input": "Einen Literatureintrag erfassen",
+        "literature_input": "Bir literat\u00fcr kay\u0131tla",
-        "objects": "Objekte",
+        "objects": "Objeler",
-        "overview": "\u00dcberblick",
+        "overview": "genel g\u00f6r\u00fcn\u00fcm",
-        "notfound": "Sorry, nichts gefunden",
+        "notfound": "\u00fczg\u00fcn\u00fcm, bir \u015fey bulunamad\u0131",
-        "oak": "Objekte auf Karte zeigen",
+        "oak": "objeyi haritada g\u00f6ster",
-        "record_history": "Datensatz",
+        "record_history": "veri kayd\u0131",
-        "loans": "Leihverkehr",
+        "loans": "krediler",
-        "exhibitions": "Ausstellung",
+        "exhibitions": "sergiler",
-        "restoration": "Konservierung",
+        "restoration": "restorasyon",
-        "provenanceresearch": "Provenienz",
+        "provenanceresearch": "kaynak",
-        "account_settings": "Kontoeinstellungen",
+        "account_settings": "hesap ayarlar\u0131",
-        "edit": "Bearbeiten",
+        "edit": "duzende",
-        "contacts": "Kontakte",
+        "contacts": "rehber listesi",
-        "contacts_input": "Einen Kontakt erfassen",
+        "contacts_input": "bir ki\u015fiyi kay\u0131tla",
-        "contacts_edit": "Kontakt bearbeiten",
+        "contacts_edit": "ki\u015fiyi d\u00fczenle",
-        "loans_input": "Einen Leihvorgang erfassen",
+        "loans_input": "Bir kredi i\u015flemi girin",
-        "loans_edit": "Leihvorgang bearbeiten",
+        "loans_edit": "Kredi i\u015flemi d\u00fczenle",
-        "delete": "L\u00f6schen",
+        "delete": "sil",
-        "exhibitions_input": "Eine Ausstellung erfassen",
+        "exhibitions_input": "bir sergi kay\u0131tla",
-        "loans_choose": "Einen Leihvorgang ausw\u00e4hlen",
+        "loans_choose": "Bir kredi i\u015flemi se\u00e7",
-        "contacts_choose": "Einen Kontakt ausw\u00e4hlen",
+        "contacts_choose": "Bir ki\u015fi se\u00e7",
-        "exhibitions_choose": "Eine Ausstellung ausw\u00e4hlen",
+        "exhibitions_choose": "Bir sergi se\u00e7",
         "impressum": "Impressum",
-        "privacy_policy": "Datenschutzerkl\u00e4rung",
+        "privacy_policy": "Gizlilik Politikas\u0131",
-        "appointments_input": "Einen Termin hinzuf\u00fcgen",
+        "appointments_input": "Bir randevu ekle",
-        "appointments": "Termine",
+        "appointments": "randevular",
-        "appointments_choose": "Einen Termin ausw\u00e4hlen",
+        "appointments_choose": "Bir randevu se\u00e7",
-        "link_no_url": "Der eingegebene Link ist keine valide URL.",
+        "link_no_url": "girilen link ge\u00e7erli de\u011fil ",
-        "yes": "Ja",
+        "yes": "evet",
-        "no": "Nein",
+        "no": "hayir",
-        "more": "Mehr",
+        "more": "daha fazla",
-        "amount_all": "Gesamt",
+        "amount_all": "b\u00fct\u00fcn",
-        "icon": "Icon",
+        "icon": "ikon",
-        "actions": "Aktionen",
+        "actions": "aksiyon",
-        "add": "Hinzuf\u00fcgen",
+        "add": "ekle",
-        "lists": "Listen",
+        "lists": "listeler",
-        "settings": "Einstellungen",
+        "settings": "ayarlar",
-        "public_page": "\u00d6ffentliche Seite",
+        "public_page": "kamu sitesi",
-        "toggles": "Schalter",
+        "toggles": "\u015falter",
-        "own_rule_create": "Hausregel erstellen",
+        "own_rule_create": "kendi kural\u0131n\u0131 olu\u015ftur",
-        "own_rule_delete": "Hausregel entfernen",
+        "own_rule_delete": "kendi kural\u0131n\u0131 sil",
-        "own_rule_edit": "Hausregel bearbeiten",
+        "own_rule_edit": "kendi kural\u0131n\u0131 d\u00fczenle",
-        "less": "Weniger",
+        "less": "daha az",
-        "grid": "Grid",
+        "grid": "system",
-        "sort": "Sortieren",
+        "sort": "ay\u0131rmak",
-        "quilt": "Flexibles Grid",
+        "quilt": "esnek system",
-        "options": "Optionen",
+        "options": "se\u00e7enekleri",
-        "newspapers_mailing_lists": "Newsletters and mailing lists",
+        "newspapers_mailing_lists": "b\u00fclten aboneli\u011fi ve E-posta listeleri",
-        "room": "Raum",
+        "room": "oda",
-        "image": "Bild",
+        "image": "resim",
-        "menu_items": "Menu Items",
+        "menu_items": "men\u00fc \u00f6\u011feleri",
-        "backgrounds": "Hintergr\u00fcnde"
+        "backgrounds": "arka plan g\u00f6r\u00fcnt\u00fcleri"
     }
 }

frontend/ar/navigation.json

@@ -1,10 +1,10 @@
 {
     "nav": {
         "home": "\u0627\u0644\u0635\u0641\u062d\u0629 \u0627\u0644\u0631\u0626\u064a\u0633\u064a\u0629",
-        "museum": "\u0627\u0644\u0645\u062a\u062d\u0641",
+        "museum": "\u0627\u0644\u0645\u062a\u0627\u062d\u0641",
-        "collection": "\u0627\u0644\u0645\u062c\u0645\u0648\u0639\u0629",
+        "collection": "\u0627\u0644\u0645\u062c\u0645\u0648\u0639\u0627\u062a ",
-        "object": "\u0627\u0644\u0642\u0637\u0639\u0629",
+        "object": "\u0627\u0644\u0642\u0637\u0639",
-        "topics": "\u0645\u0648\u0627\u0636\u064a\u0639",
+        "topics": "\u0627\u0644\u0645\u0648\u0627\u0636\u064a\u0639",
         "contact": "\u0627\u0644\u062a\u0648\u0627\u0635\u0644",
         "API": "API ",
         "API_link": " \u0631\u0627\u0628\u0637 API ",
@@ -14,8 +14,8 @@
         "settings": "\u0627\u0644\u0627\u0639\u062f\u0627\u062f\u0627\u062a",
         "sitemap": "\u062e\u0631\u064a\u0637\u0629 \u0627\u0644\u0645\u0648\u0642\u0639",
         "more": "\u0627\u0644\u0645\u0632\u064a\u062f",
-        "articles": "\u0645\u0642\u0627\u0644\u0627\u062a",
+        "articles": "\u0627\u0644\u0645\u0642\u0627\u0644\u0627\u062a",
-        "events": "\u0641\u0639\u0651\u0627\u0644\u064a\u0627\u062a",
+        "events": "\u0627\u0644\u0641\u0639\u0651\u0627\u0644\u064a\u0627\u062a",
         "select_language": "\u0627\u062e\u062a\u064a\u0627\u0631 \u0627\u0644\u0644\u063a\u0629",
         "join_us": "\u0627\u0646\u0636\u0645 \u0627\u0644\u064a\u0646\u0627"
     }

frontend/en/basis.json

@@ -42,7 +42,7 @@
         "privacy_policy": "Privacy policy",
         "for_example": "For example",
         "exhibitions": "Exhibitions",
-        "tag_cloud": "Key word cloud",
+        "tag_cloud": "Tag cloud",
         "sitemap": "Sitemap",
         "page": "Page",
         "image_search": "Image search",

frontend/en/objects.json

@@ -6,7 +6,7 @@
         "here": "here",
         "to_refined_search": "To use the advanced search engine, click here",
         "to_image_wall": "The image wall is meant for exploration. You will see randomly chosen images of objects if you click",
-        "last": "Those that just want to explore without knowing anything specific about whatever they might be searching for, might want to use the key word cloud to the right. The objects on this site have been tagged, and from these tags the tag cloud is generated in a random order. Maybe a bit messy - but an interesting tool for exploring",
+        "last": "Those that just want to explore without knowing anything specific about whatever they might be searching for, might want to use the tag cloud to the right. The objects on this site have been tagged, and from these tags the tag cloud is generated in a random order. Maybe a bit messy - but an interesting tool for exploring",
         "advanced_search_intro": "Here you can do an advanced search for objects based on their relationship to a given person\/institution, a place, or time. If you enter a term into the search bar, a list of possible terms from our database will be shown. Choose one by clicking on it. Entering information into more than one field lets you close in the search more. You can also define the kind of object or the kind of relationship between, for example, an object and an event etc., you are looking for.",
         "actor": "Person\/Institution",
         "place": "Place",

mdorg/de/calendar.json

@@ -5,6 +5,7 @@
         "calendarPageDescription": "Auf dieser Seite k\u00f6nnen Sie aktuelle Veranstaltungen rund um museum-digital finden, z.B. Schulungen.",
         "calendarPageKeywords": "museum-digital, Kalender, Veranstaltungen, Seminare",
         "calendar_title": "Kalender",
-        "calendar_introduction": "Auf dieser Seite k\u00f6nnen Sie aktuelle Veranstaltungen rund um museum-digital finden, z.B. Schulungen."
+        "calendar_introduction": "Auf dieser Seite k\u00f6nnen Sie aktuelle Veranstaltungen rund um museum-digital finden, z.B. Schulungen.",
+        "attendees": "Teilnehmende"
     }
 }

mdorg/en/calendar.json

@@ -5,6 +5,7 @@
         "calendarPageDescription": "On this page you can find current events concerning museum-digital, e.g. seminars.",
         "calendarPageKeywords": "museum-digital, Calendar, Events, Seminars",
         "calendar_title": "Calendar",
-        "calendar_introduction": "On this page you can find current events concerning museum-digital, e.g. seminars."
+        "calendar_introduction": "On this page you can find current events concerning museum-digital, e.g. seminars.",
+        "attendees": "Attendees"
     }
 }

mdorg/en/mission.json

@@ -2,8 +2,8 @@
     "tlMission": {
         "pageTitle": "Mission and Vision :: museum-digital",
         "pageDescription": "museum-digital is a project for the digitization of museum data. Here we declare our mission.",
-        "pageKeywords": "museum-digital, museums, digitization, mission statement, aims",
+        "pageKeywords": "Museum-digital, Museums, Digitization, Mission Statement, Aims",
         "missions_title": "Mission",
-        "missions_introduction": "Museums and their objects should be online! museum-digital's aim is to create simple to use tools and an appropriate environment for this. Museums that use a different software for inventorization can use museum-digital for publishing their data. For all other museums that may not yet have a dedicated inventorization tool museum-digital offers appropriate tools.<\/p>\r\n\r\n<p>museum-digital is a community: all participating museums can join the conversation on what the project should focus on, and how the software is to be developed further. By and by, infrastructure is set up to facilitate and develop the conversation about the digital and museums.<\/p>\r\n\r\n<p>An important principle of museum-digital is to respect existing structures."
+        "missions_introduction": "Museums and their objects should be online! Museum-digital's aim is to create simple to use tools and an appropriate environment for this. Museums that use a different software for inventory can use museum-digital for publishing their data. For all other museums that may not yet have a dedicated inventory tool museum-digital offers appropriate tools.<\/p>\r\n\r\n<p>Museum-digital is a community: all participating museums can join the conversation on what the project should focus on, and how the software is to be developed further. By and by, infrastructure is set up to facilitate and develop the conversation about the digital and museums.<\/p>\r\n\r\n<p>An important principle of museum-digital is to respect existing structures."
     }
 }

mdorg/en/navigation.json

@@ -10,7 +10,7 @@
         "software_themator": "Themator",
         "software_term_nodac": "md:term & nodac",
         "portals": "Portals",
-        "terminology_work": "Terminological work",
+        "terminology_work": "Terminology work",
         "dashboard": "Dashboard",
         "participate": "Participate",
         "mission": "Mission",
@@ -19,7 +19,7 @@
         "third_party": "Third Party Tools",
         "publications": "Publications",
         "api_based": "Third Party Tools",
-        "impressum": "Impressum",
+        "impressum": "Copyright",
         "contact": "Contact",
         "privacy": "Privacy",
         "people": "People",

mdorg/en/participate.json

@@ -1,16 +1,16 @@
 {
     "tlParticipate": {
-        "pageTitle": "Becoming a Part of museum-digital! :: museum-digital",
+        "pageTitle": "Become a part of museum-digital! :: museum-digital",
-        "pageDescription": "museum-digital is a community project. Of course, we always welcome volunteers, who're ready to help out!",
+        "pageDescription": "Museum-digital is a community project. Of course, we always welcome volunteers who are ready to help out!",
-        "pageKeywords": "participation, community, peers, volunteering",
+        "pageKeywords": "Participation, Volunteering, Community",
-        "participate_title": "Becoming a Part of museum-digital",
+        "participate_title": "Becoming a part of museum-digital",
         "participate_introduction": "Helping museum-digital is possible in a multitude of ways. Direct participation is mainly reserved for museums, but anybody can help greatly by providing meaningful information and comments.",
-        "individuals": "... as an Individual",
+        "individuals": "You can visit a single museum",
-        "individuals_title": "... as an Individual",
+        "individuals_title": "...alone or with a group",
-        "individuals_text": "You can help museums greatly by providing information and working with the museums. At the bottom of almost all object pages, there is a link \"Do you know more ...?\". By clicking on this line, you can directly provide e-mail feedback on the given object to the museum concerned. You may however also offer helping out the museum in your area of expertise.",
+        "individuals_text": "You can help museums greatly by providing information and working with the museums. At the bottom of almost all object pages, there is a link \"Do you know more ...?\". By clicking on this line, you can directly provide e-mail feedback on the given object to the related museum. You may however also offer help to a museum in your area of expertise.",
         "local_museum_title": "Helping Out at Your Local Museum",
         "local_museum_text": "Many, if not most, museums welcome little more than a helping hand. ",
         "institutions_title": "... as an Institution",
-        "institutions_text": "If your institution wants to join museum-digital, you only need a short description, a photo, and the usual contact information of the museum. The museum will then be entered into the appropriate instance of museum-digital and a user account for the museum will be set up. Our tools have shown to be sufficiently intuitive for half an hour of an introduction (via phone) to be sufficient for publishing an object.<\/p>\r\n\r\n<p>Regional museum associations often offer day-long seminars in which working with museum-digital is discussed in more detail. These events usually feature hands-on exercises. It may be fruitful to consult your regional museum association or the administrator of your regional instance of museum-digital."
+        "institutions_text": "If your institution wants to join museum-digital, you only need a short description, a photo, and the usual contact information of the museum. The museum will then be entered into the appropriate instance of museum-digital and a user account for the museum will be set up. Our tools have shown to be sufficiently intuitive for half an hour of an introduction (via phone) to be sufficient for publishing an object.<\/p>\r\n\r\n<p>Regional museum associations often offer day-long seminars in which working with museum-digital is discussed in more detail. These events usually feature hands-on exercises. It may be fruitful to consult your regional museum association or the administrator of your region of museum-digital."
     }
 }

mdorg/en/people.json

@@ -10,9 +10,9 @@
         "affiliation": "Affiliation",
         "blog_posts_by": "Blog Posts by %s",
         "overviewTitle": "Team :: museum-digital",
-        "overviewDescription": "museum-digital is people. Here you can some people from our core team.",
+        "overviewDescription": "Museum-digital is people. Here you can learn about some people from our core team.",
-        "overviewKeywords": "museum-digital, team, people",
+        "overviewKeywords": "Museum-digital, Team, People",
         "overviewListTitle": "Team",
-        "overviewListSummary": "museum-digital is - in effect - people. Here you can find a list of some of our core team members in random order."
+        "overviewListSummary": "Museum-digital is - in effect - people. Here you can find a list of some of our core team members in random order."
     }
 }

mdorg/en/portals.json

@@ -1,16 +1,16 @@
 {
     "tlPortals": {
         "pageTitle": "Portals :: museum-digital",
-        "pageDescription": "museum-digital is represented on different, regional portals. Here, there is a list of them.",
+        "pageDescription": "Museum-digital is represented on different, regional portals. Here is a list of them.",
-        "pageKeywords": "museum-digital, portals, museum objects, access",
+        "pageKeywords": "Museum-digital, Portals, Museum Objects, Access",
-        "portals_title": "The Different Portals of museum-digital",
+        "portals_title": "The different portals of museum-digital",
-        "portals_introduction": "museum-digital is composed of different portals. Most of them are regionally structured.",
+        "portals_introduction": "Museum-digital is composed of different portals. Most of them are regionally structured.",
         "international_portals": "International Portals",
         "german_portals": "Regional portals in Germany",
         "themator_title": "Themator: Topical Portals",
         "themator_introduction": "The themator is a tool we developed to enable museums and like-minded people to create digital exhibitions and - more generally - to easily engage in digital storytelling. As the themator is largely monolingual, we have set up different instances of it.",
-        "md_term_title": "md:term: The Controlled Vocabularies of museum-digital Made Accessible",
+        "md_term_title": "md:term: The controlled vocabularies of museum-digital made accessible",
-        "md_term_introduction": "About 2010, we started to use controlled vocabularies to facilitate the common tagging and interlinking of digitized objects. For a long time, these vocabularies were not accessible for any outside viewers. Since they may be a useful resource to some, we since developed md:term as a public and hopefully easily accessible portal for our (and some other) controlled vocabularies.",
+        "md_term_introduction": "Around 2010, we started to use controlled vocabularies to facilitate the common tagging and interlinking of digitized objects. For a long time, these vocabularies were not accessible for any outside viewers. Since they may be a useful resource to some, we have since developed md:term as a public and hopefully easily accessible portal for our (and some other) controlled vocabularies.",
         "Germany": "Germany",
         "Hungary": "Hungary",
         "Brazil": "Brazil",

mdorg/en/resources.json

@@ -1,8 +1,8 @@
 {
     "tlResources": {
         "pageTitle": "Resources :: museum-digital",
-        "pageDescription": "Here you can find resources on museum-digital specifically and those relevant to the digitization in museums in general.",
+        "pageDescription": "Here you can find specific resources on museum-digital and those relevant to the digitization in museums in general.",
-        "pageKeywords": "museums, resources, materials",
+        "pageKeywords": "Museums, Resources, Materials",
         "resources_title": "Resources",
         "resources_introduction": "Relevant resources can be found here.",
         "general": "General"

mdorg/en/resources_documents.json

@@ -1,9 +1,9 @@
 {
     "tlDocuments": {
         "pageTitle": "museum-digital :: Resources",
-        "pageDescription": "A selection of helpful documents for about museum work in general and digital museum work in specific can be found here.",
+        "pageDescription": "A selection of helpful documents about museum work in general and specific digital museum work can be found here.",
-        "pageKeywords": "documents, museums, museums work, digitization, inventorization",
+        "pageKeywords": "Documents, Museums, Museum Works, Digitization, Inventory",
         "title": "Documents",
-        "introduction": "A selection of helpful documents for about museum work in general and digital museum work in specific can be found here."
+        "introduction": "A selection of helpful documents about museum work in general and specific digital museum work can be found here."
     }
 }

mdorg/en/resources_links.json

@@ -2,7 +2,7 @@
     "tlLinks": {
         "pageTitle": "museum-digital :: Links",
         "pageDescription": "A selection of relevant links about museum digitization can be found here.",
-        "pageKeywords": "Links, museums, digitization in museums, museum portals",
+        "pageKeywords": "Links, Museums, Digitization in Museums, Museum Portals",
         "title": "Links",
         "introduction": "Here you can find a list of interesting links.",
         "museum_portals": "Other Museum (Object) Portals",

mdorg/en/software.json

@@ -2,9 +2,9 @@
     "tlSoftware": {
         "pageTitle": "Software :: museum-digital",
         "pageDescription": "At museum-digital, we have developed a set of software solutions to aid different parts of museum (digitization) work.",
-        "pageKeywords": "software, museums, museum objects, museum software, museum-digital",
+        "pageKeywords": "Software, Museums, Museum Objects, Museum Software, museum-digital",
         "software_title": "Software",
-        "software_introduction": "At museum-digital, we have developed a set of software solutions to facilitate an easy and inclusive process of digitizations in museums. Originally, museum-digital was founded to publish object information online. We thus began by developing a <a href=\"\/software\/frontend\">public interface for viewing object information<\/a>.\r\n<\/p>\r\n<p>\r\nSince the original method of data input - the museums entered their data into their local database, sent it to the programmers, the programmers entered it to museum-digital - did not scale well, we then developed a simple online input interface, <a href=\"\/software\/musdb\">musdb<\/a>. Some museums, that did not yet have a dedicated database for inventorization data, but knew musdb well, began to ask additional inventorization functionalities. And thus the approach of musdb changes: instead of being an input interface to a publication platform, it turned into an inventorization tool with the option to publish.\r\n<\/p>\r\n<p>\r\nSoon after, requests for options to more thoroughly present digital narratives and stories became more frequent. While museum objects may be interesting by themselves, it is also a central task of museums to contextualize them. As a reaction to these requests, we created the <a href=\"\/software\/themator\">Themator<\/a> as an independent tool for writing and publishing stories online.\r\n<\/p>\r\n<p>\r\nEarly on, when developing the main frontend and musdb, we decided to use controlled vocabularies for all databases of a given language. Internally, we use our \"norm data control tool\" <a href=\"\/software\/term_nodac\">nodac<\/a> for curating these. Since the vocabularies have grown considerably since, and have become a useful resource on their own by now, we have also developed a searchable frontend for these, <a href=\"\/software\/term_nodac\">md:term<\/a>.",
+        "software_introduction": "At museum-digital, we have developed a set of software solutions to facilitate an easy and inclusive process of digitization in museums. Originally, museum-digital was founded to publish object information online. We thus began by developing a <a href=\"\/software\/frontend\">public interface for viewing object information<\/a>.\r\n<\/p>\r\n<p>\r\nSince the original method of data input - the museums entered their data into their local database, sent it to the programmers, the programmers entered it to museum-digital - did not scale well, we then developed a simple online input interface, <a href=\"\/software\/musdb\">musdb<\/a>. Some museums, that did not yet have a dedicated database for inventorized data, but knew musdb well, began to ask additional inventory functionalities. And thus the approach of musdb changed: instead of being an input interface to a publication platform, it turned into an inventory tool with the option to publish.\r\n<\/p>\r\n<p>\r\nSoon after, requests for options to more thoroughly present digital narratives and stories became more frequent. While museum objects may be interesting by themselves, it is also a central task of museums to contextualize them. As a reaction to these requests, we created the <a href=\"\/software\/themator\">Themator<\/a> as an independent tool for writing and publishing stories online.\r\n<\/p>\r\n<p>\r\nEarly on, when developing the main frontend and musdb, we decided to use controlled vocabularies for all databases of a given language. Internally, we use our \"norm data control tool\" <a href=\"\/software\/term_nodac\">nodac<\/a> for curating these. Since the vocabularies have grown considerably since, and have become a useful resource on their own by now, we have also developed a searchable frontend for these, <a href=\"\/software\/term_nodac\">md:term<\/a>.",
         "frontend_portal": "Frontend\/Portals",
         "musdb": "musdb",
         "themator": "Themator",

mdorg/en/software_frontend.json

@@ -2,12 +2,12 @@
     "tlFrontend": {
         "pageTitle": "The Main Frontend\/Portal Software :: museum-digital",
         "pageDescription": "Most of the work museum-digital does focuses on bringing museums online. We do so mainly using our main frontend\/portal software.",
-        "pageKeywords": "software, museums, museum objects, museum software, exhibitions, web portal",
+        "pageKeywords": "Software, Museums, Museum Objects, Museum Software, Exhibitions, Web Portal",
         "frontend_title": "The Main Frontend of museum-digital",
         "frontend_introduction": "museum-digital was founded to publish museum object information online. That's not possible without the right software.<\/p>\r\n<p>The \"frontend\" is thus the first application, that was developed at museum-digital. With it, museums can join together to present themselves and their objects online.<\/p>\r\n<p>To offer a comprehensive glimpse at the museums and their objects, a variety of additional information has been made presentable since. On the one hand, museums can now add information on their collections, object groups, exhibitions, and events. On the other, a number of options for linking and visualizing information have been added.",
         "technical_title": "Technical Information",
         "design_principles_title": "Focus - Design Principles",
-        "design_principles_text": "\"The \"frontend\" of museum-digital is primarily designed to always offer a clear focus on whichever information is central to a given page or section. This provides for an easy of understanding. A lot of additional options exist for power users - from visualizations to a command line menu embedded into the website. These are however \"hidden\" in sidebars or only accessible through keyboard shortcuts, so that they don't irritate first-time users.",
+        "design_principles_text": "\"The \"frontend\" of museum-digital is primarily designed to always offer a clear focus on whichever information is central to a given page or section. This allows for easy understanding. A lot of additional options exist for power users - from visualizations to a command line menu embedded into the website. These are however \"hidden\" in sidebars or only accessible through keyboard shortcuts, so that they don't irritate first-time users.",
         "api_title": "API(s)",
         "api_text": "Publishing and making things accessible doesn't only mean making it possible to view something. It also means enabling people to use data to realize their own ideas. Accordingly, all information that is published using the \"frontend\" of museum-digital is also accessible in a machine-readable way via our <abbr title=\"JavaScript Object Notation\">JSON<\/abbr> API.<\/p><p>As much as possible, the \"frontend\" provides information in open standards as well: object information can be accessed in <a href=\"http:\/\/network.icom.museum\/cidoc\/working-groups\/lido\/what-is-lido\/\">LIDO<\/a>, information about museums can be downloaded as electronic business cards (<a href=\"https:\/\/de.wikipedia.org\/wiki\/VCard\">vCard<\/a>), and calendar information such as exhibitions can be integrated with calendar tools using the <a href=\"https:\/\/de.wikipedia.org\/wiki\/ICalendar\">iCalendar<\/a> standard.",
         "development_title": "Development",
@@ -28,8 +28,8 @@
         "screenshot_oak": "Using the \"objects on map\" pages, users can find interesting objects based on their geographical background.",
         "screenshot_object_page_alt": "An object page.",
         "screenshot_object_page": "An object page in the frontend of museum-digital.",
-        "screenshot_multilinguality_alt": "Multilinguality in the museum-digital frontend.",
+        "screenshot_multilinguality_alt": "Multilingualism in the museum-digital frontend.",
-        "screenshot_multilinguality": "museum-digital is multilingual, and so can be the displayed entries. The navigation language and the record language can be switched independent of each other.",
+        "screenshot_multilinguality": "museum-digital is multilingual, and so, too, can be the displayed entries. The navigation language and the record language can be switched independent of each other.",
         "screenshot_exhibition_tiles_alt": "Exhibition overview page in the museum-digital frontend",
         "screenshot_exhibition_tiles": "The exhibition overview page in tiles mode.",
         "screenshot_calendar_alt": "Calendars are available for exhibitions and events.",

mdorg/en/software_musdb.json

@@ -1,24 +1,24 @@
 {
     "tlMusdb": {
         "pageTitle": "musdb :: museum-digital",
-        "pageDescription": "musdb is museum-digital's tool for indexing and inventorization. It has in many ways developed into a more general museum-management tool.",
+        "pageDescription": "musdb is museum-digital's tool for indexing and creating inventories. It has in many ways developed into a more general museum-management tool.",
-        "pageKeywords": "musdb, museum-management, inventorization, software",
+        "pageKeywords": "musdb, Museum Management, Inventory, Software",
         "musdb_title": "musdb",
-        "musdb_introduction": "musdb is museum-digital's tool for indexing and inventorization. Originally developed for recording objects to be published only, it has since developed into a full-featured inventorization and museum management solution.<\/p>\r\n<p>Central to the development of musdb are:<\/p>\r\n<ul>\r\n<li>musdb is developed based on requests by and communications with the museums using it<\/li>\r\n<li>musdb is being with collaboration in mind: New features and fixes are available to all museums<\/li>\r\n<li>using musdb means working collaboratively: the controlled vocabularies, that are used for linking people, times, places, and tags, are used together by all museums of a given language<\/li>\r\n<li>working with musdb should be as easy and intuitive as possible<\/li>\r\n<li>Tips and warnings are given to not just enter data, but to create high quality data<\/li>\r\n<\/ul>",
+        "musdb_introduction": "Musdb is museum-digital's tool for indexing and creating inventories. Originally developed for recording objects to be published only, it has since developed into a full-featured inventory and museum management solution.<\/p>\r\n<p>Central to the development of musdb are:<\/p>\r\n<ul>\r\n<li>musdb is developed based on requests by and communication with the museums using it<\/li>\r\n<li>musdb is made with collaboration in mind: New features and fixes are available to all museums<\/li>\r\n<li>using musdb means working collaboratively: the controlled vocabularies, that are used for linking people, times, places, and tags, are used together by all museums of a given language<\/li>\r\n<li>working with musdb should be as easy and intuitive as possible<\/li>\r\n<li>Tips and warnings are given to not just enter data, but to create high quality data<\/li>\r\n<\/ul>",
         "technical_title": "Technical Information",
         "design_principles_title": "Design Principles",
-        "design_principles_text": "musdb should be easy and intuitive to use. It should be fun to use. One the one hand, this means that the design should give a clear focus to the main subject of a given page. To reach this aim, options exist to toggle many features on or off. Optional features (like generating QR codes for object pages or a table of contents to directly jump to the wanted section of a page) are available in a toolbox on the left border of the window.<\/p>\r\n\r\n<p>But <i>easy<\/i> and <i>intuitive<\/i> also means that power users can work efficiently in whatever way suits them best. musdb offers a variety of helpers for this. A selection of these are:<\/p>\r\n\r\n<ul>\r\n<li>Clicking into a field, users can see how many characters have been entered, how many are required, and how many are allowed at max.<\/li>\r\n<li>PuQi: the \"Publication Quality Index\" shows, how object information can be enhanced<\/li>\r\n<li>Plausi: using the controlled vocabularies, musdb can warn about implausible entries (e.g. a painter cannot have painted a painting before she was born)<\/li>\r\n<li>Text blocks provide for a quick entry of similar contents<\/li>\r\n<\/ul>",
+        "design_principles_text": "Musdb should be easy and intuitive to use. It should be fun to use. On the one hand, this means that the design should give a clear focus to the main subject of a given page. To reach this aim, options exist to toggle many features on or off. Optional features (like generating QR codes for object pages or a table of contents to directly jump to the wanted section of a page) are available in a toolbox on the left border of the window.<\/p>\r\n\r\n<p>But <i>easy<\/i> and <i>intuitive<\/i> also means that power users can work efficiently in whatever way suits them best. Musdb offers a variety of aids for this. A selection of these are:<\/p>\r\n\r\n<ul>\r\n<li>Clicking into a field, users can see how many characters have been entered, how many are required, and how many are allowed at max.<\/li>\r\n<li>PuQi: the \"Publication Quality Index\" shows, how object information can be enhanced<\/li>\r\n<li>Plausi: using the controlled vocabularies, musdb can warn about implausible entries (e.g. a painter cannot have painted a painting before she was born)<\/li>\r\n<li>Text blocks provide for a quick entry of similar contents<\/li>\r\n<\/ul>",
         "development_title": "Development",
-        "development_text": "musdb is based on PHP7 and MySQL. A number of PHP and JavaScript libraries are used, a list of which can be found <a href=\"https:\/\/handbook.museum-digital.info\/?lan=de&q=Weiteres\/Dependencies#2\">in the handbook<\/a>.",
+        "development_text": "Musdb is based on PHP7 and MySQL. A number of PHP and JavaScript libraries are used, a list of which can be found <a href=\"https:\/\/handbook.museum-digital.info\/?lan=de&q=Weiteres\/Dependencies#2\">in the handbook<\/a>.",
         "screenshots": "Screenshots",
         "resources": "Resources",
         "in_handbook": "Documentation for musdb",
-        "videos_and_screencasts": "Videos and Screencasts on YouTube",
+        "videos_and_screencasts": "Videos on YouTube",
         "in_blog": "News About the Development of musdb",
-        "screenshot_dashboard_alt": "Dashboard \/ default startpage of musdb.",
+        "screenshot_dashboard_alt": "Dashboard\/Default startpage of musdb.",
         "screenshot_dashboard": "The default start page is a customizable dashboard. Other start pages can be selected by the user.",
         "screenshot_batch_editing_alt": "Batch editing in musdb.",
-        "screenshot_batch_editing": "musdb features batch editing functionalities for e.g. batch publishing or tagging.",
+        "screenshot_batch_editing": "Musdb features batch editing functionalities for batch publishing or tagging.",
         "screenshot_xml_export_alt": "XML export",
         "screenshot_xml_export": "Users can export their data in our own md:xml (a simple notation featuring all available fields) and <a href='http:\/\/lido-schema.org'>LIDO<\/a>.",
         "screenshot_backgrounds_alt": "Background research tool.",
@@ -26,20 +26,20 @@
         "screenshot_find_an_export_alt": "Find an expert: Connecting users.",
         "screenshot_find_an_export": "Using the \"Find an Export\" button, users can find other users who have done much work on a given topic. Still, every user can decide if they want to let others find them through this tool or not.",
         "screenshot_multilingual_alt": "Multilingual usage of musdb.",
-        "screenshot_multilingual": "musdb is multilingual and it can handle multilingual inputs.",
+        "screenshot_multilingual": "Musdb is multilingual and it can handle multilingual inputs.",
         "screenshot_navigation_alt": "Navigation of musdb.",
-        "screenshot_navigation": "The navigation gives a rough overview over different sections of musdb: museums, collections, objects, object groups, exhibitions, etc.",
+        "screenshot_navigation": "The navigation gives a rough overview over different sections of musdb: Museums, Collections, Objects, Object Groups, Exhibitions, etc.",
         "screenshot_object_overview_alt": "Object overview page.",
         "screenshot_object_overview": "An object overview page in image mode. The sidebar on the right offers search and filter-based exporting and batch editing functionalities. A simple list view is also available.",
-        "screenshot_object_page_alt": "Object page.",
+        "screenshot_object_page_alt": "Object page",
         "screenshot_object_page": "The main section of an object page. At the top, most basic information on the object can be entered. At the bottom, the tabbed menu for managing detailed information on the object can be seen.",
         "screenshot_record_history_alt": "Record history of an object.",
         "screenshot_record_history": "Edits to an object are logged. If the user who previously edited the object set up their user profile, new users who see the logs can get to know others from the museum through the logs.",
-        "screenshot_provenance_research_alt": "Provenance research tab.",
+        "screenshot_provenance_research_alt": "Provenance research tab",
         "screenshot_provenance_research": "Using the provenance research tab, detailed reports on a predefined set of critical issues can be recorded.",
-        "screenshot_restoration_alt": "Restoration tab on a musdb object page.",
+        "screenshot_restoration_alt": "Restoration tab on a musdb object page",
         "screenshot_restoration": "The restoration tab of an object page offers options for color-coded and easily accessible notes towards the top of the section, detailed ones on the bottom.",
-        "screenshot_user_management_alt": "User management and user rights section.",
+        "screenshot_user_management_alt": "User management and user rights section",
         "screenshot_user_management": "Museum directors and regional administrators set detailed permissions for what users can edit or view."
     }
 }

mdorg/en/software_term_nodac.json

@@ -2,8 +2,8 @@
     "tlTermNodac": {
         "pageTitle": "Nodac & md:term :: museum-digital",
         "pageDescription": "At museum-digital we build two tools for managing and displaying controlled vocabularies: md:term and nodac.",
-        "pageKeywords": "software, controlled vocabularies, subject headings",
+        "pageKeywords": "Software, Controlled Vocabularies, Subject Headings",
         "term_nodac_title": "Our Tools for Managing Controlled Vocabularies: nodac and md:term",
-        "term_nodac_introduction": "nodac is the name of our tool for correcting, enriching, and hierarchializing controlled vocabularies at museum-digital. Nodac is multilingual and can be used for controlling vocabularies in different languages. Using nodac, external vocabularies can be managed as well: for example the Hornbostel-Sachs-Systematik for Musikinstrumente or the Hessische Systematik. The primary use of the tool remains, however, the curation of the museum-digital's own controlled vocabularies. It is the dedicated place for in-depth enrichment of terms from the domains of \"actors\" (people and institutions), geographic places, times, and tags. These are controlled centrally for a given language by the <i>norm data editors<\/i>. Each participating museum can however submit requests for changes.<\/p>\r\n\r\n<p>While it is the dedicated aim of museum-digital to make entering and linking - for example - a tag as easy as possible for the museums, further edits like providing a definition of the term and linking it with other controlled vocabularies are taken over by the <i>norm data editors<\/i>. It thus becomes a background task, that does however remain central to the success of the whole endeavor. It is only because we keep curated controlled vocabularies, that we can generate correct timelines or place objects on maps in any meaningful way.<\/p>\r\n\r\n<p>md:term is the public equivalent of nodac. It provides for public, structured access to our own vocabularies and a number of external ones. Besides making the vocabularies browse-able, it offers <a href=\"https:\/\/en.wikipedia.org\/wiki\/Simple_Knowledge_Organization_System\"><abbr title=\"Simple Knowledge Organization System\">SKOS<\/abbr><\/a> and <abbr title=\"JavaScript Object Notation\">JSON<\/abbr> interfaces. In this way, it provides access for other developers and projects to creatively use and incorporate our controlled vocabularies."
+        "term_nodac_introduction": "nodac is the name of our tool for correcting, enriching, and stratifying controlled vocabularies at museum-digital. Nodac is multilingual and can be used for controlling vocabularies in different languages. Using nodac, external vocabularies can be managed as well: for example the Hornbostel-Sachs-Systematik for musical instruments or the Hessische Systematik. The primary use of the tool remains, however, the curation of the museum-digital's own controlled vocabularies. It is the dedicated place for in-depth enrichment of terms from the domains of \"actors\" (people and institutions), geographic places, times, and tags. These are controlled centrally for a given language by the <i>norm data editors<\/i>. Each participating museum can however submit requests for changes.<\/p>\r\n\r\n<p>While it is the dedicated aim of museum-digital to make entering and linking - for example - a tag as easy as possible for the museums, further edits like providing a definition of the term and linking it with other controlled vocabularies are taken over by the <i>norm data editors<\/i>. It thus becomes a background task, that does however remain central to the success of the whole endeavor. It is only because we keep curated controlled vocabularies, that we can generate correct timelines or place objects on maps in any meaningful way.<\/p>\r\n\r\n<p>md:term is the public equivalent of nodac. It provides for public, structured access to our own vocabularies and a number of external ones. Besides making the vocabularies browse-able, it offers <a href=\"https:\/\/en.wikipedia.org\/wiki\/Simple_Knowledge_Organization_System\"><abbr title=\"Simple Knowledge Organization System\">SKOS<\/abbr><\/a> and <abbr title=\"JavaScript Object Notation\">JSON<\/abbr> interfaces. In this way, it provides access for other developers and projects to creatively use and incorporate our controlled vocabularies."
     }
 }

mdorg/en/software_themator.json

@@ -2,7 +2,7 @@
     "tlThemator": {
         "pageTitle": "Themator :: museum-digital",
         "pageDescription": "The Themator is museum-digital's solution for digital story-telling.",
-        "pageKeywords": "software, story-telling, topics, stories, narrative, exhibitions",
+        "pageKeywords": "Software, Story Telling, Topics, Stories, Narrative, Exhibitions",
         "themator_title": "The Themator - A Tool for Online Storytelling and Digital Exhibitions",
         "screenshots": "Screenshots",
         "themator_introduction": "The Themator is museum-digital's solution for digital story-telling.<\/p><p>After setting up the <a href=\"\/software\/frontend\">main frontend<\/a> for museum-digital, questions for how to embed the thus published objects in online narratives soon arose. To answer this demand, the development of the Themator began.<\/p><p>The Themator is structured around topics, which can be super- or subordinate to other topics and which can be associated with objects (both those entered only in the Themator and those published in any of the <a href=\"\/about\/portals\">main portals of museum-digital<\/a>), literature entries, and more. This focus on <em>topics<\/em> provides for a broad range of possible uses in the field of digital storytelling, especially where it relates to museum objects. On the one hand, the Themator can be used for creating digital exhibitions. On the other, it has been used to create learning materials (e.g. <a href=\"https:\/\/hu.museum-digital.org\/themator\/ausgabe\/showthema.php?m_tid=1&tid=1&ver=standalone\">for teaching in German minority schools in Hungary<\/a>). This, combined with the need to be able to embed objects from the different instances in the same topic, led us to design the Themator as a tool completely independent from the main instances.",

mdorg/en/software_third_party.json

@@ -2,7 +2,7 @@
     "tlThirdParty": {
         "pageTitle": "Third Party Tools :: museum-digital",
         "pageDescription": "Based on the APIs of museum-digital, a number of third party tools have been written. Here you can find some of them.",
-        "pageKeywords": "software, museum software, API, digitization in museums",
+        "pageKeywords": "Software, Museum Software, API, Digitization in Museums",
         "title": "Third Party Tools",
         "introduction": "Using the different APIs of museum-digital, a number of additional tools have been written. These are in principle independent of museum-digital, but since they interact with or are based on museum-digital in some way, we collect brief introductions to those we know of here.",
         "resources": "Resources",

mdorg/en/terminology.json

@@ -1,10 +1,10 @@
 {
     "tlTerminology": {
-        "pageTitle": "Terminological Work at museum-digital :: museum-digital",
+        "pageTitle": "Terminology Work at museum-digital :: museum-digital",
         "pageDescription": "At museum-digital we use controlled vocabularies, to enrich the users' experience. Here we describe, how they are handled.",
-        "pageKeywords": "Terminology, museums, controlled vocabularies, tagging",
+        "pageKeywords": "Terminology, Museums, Controlled Vocabularies, Tagging",
         "terminology_title": "Controlled Vocabularies at museum-digital",
-        "terminology_role_of_terminology": "Controlled vocabularies are a central issue to museum-digital. Sorted into four catalogs (persons and institutions, geographical places, times, and tags), terms are enriched with definitions and links to external controlled vocabularies and services (Wikipedia, GND, ULAN, RKD, MBL, LAGIS, geonames, TGN, AAT, LCSH, ...). At the same time, they are categorized hierarchically. This provides for the possibility to return objects linked to subordinate terms to searches for a given superordinate term. A search for \"vehicle\" thus returns any object linked to \"car\" as well.",
+        "terminology_role_of_terminology": "Controlled vocabularies are a central issue to museum-digital. Sorted into four catagories (Persons and Institutions, Geographical Places, Times, and Keywords), terms are enriched with definitions and links to external controlled vocabularies and services (Wikipedia, GND, ULAN, RKD, MBL, LAGIS, geonames, TGN, AAT, LCSH, ...). At the same time, they are categorized hierarchically. This provides for the possibility to return objects linked to subordinate terms to searches for a given superordinate term. A search for \"vehicle\" thus returns any object linked to \"car\" as well.",
         "terminology_how_we_do_it": "How are the Vocabularies Controlled?",
         "terminology_how_we_do_it_text": "<p>The curation of controlled vocabularies at museum-digital takes place in a centralized manner. All museums of all instances of a given primary language work together to create a common database of controlled terms. Since curating controlled vocabularies is time consuming, we try to reduce the participating museums' workload in this regard as much as possible. Besides, a centralized curation of controlled vocabularies leads to more uniform results.<\/p><p>To ease the curation, we have developed a tool, <a href=\"\/software\/term_nodac\">\"nodac\"<\/a>, which automatizes much of the enrichment work and offers a simple interface for positioning terms hierarchically. With this tool, norm data editors, can also use batch editing functionalities for enhancing the controlled vocabularies.<\/p><p>The curation of controlled vocabularies is thus a joint effort of the participating museums, direct volunteering, and support by a number of state governments, led by a small team of \"norm data editors\".<\/p>"
     }

mdorg/hu/calendar.json

@@ -5,6 +5,7 @@
         "calendarPageDescription": "On this page you can find current events concerning museum-digital, e.g. seminars.",
         "calendarPageKeywords": "museum-digital, calendar, events, seminars",
         "calendar_title": "Calendar",
-        "calendar_introduction": "On this page you can find current events concerning museum-digital, e.g. seminars."
+        "calendar_introduction": "On this page you can find current events concerning museum-digital, e.g. seminars.",
+        "attendees": "Attendees"
     }
 }

nodac/en/basis.json

@@ -17,11 +17,11 @@
         "which_vocabulary": "Please choose the source (controlled vocabulary) ...",
         "enlarge_vocabulary_list": "Please enlarge the list of vocabularies",
         "delete_vocabulary": "Delete controlled vocabulary or source",
-        "delete_vocabulary_check": "You are about deleting controlled vocabulary or source",
+        "delete_vocabulary_check": "You are about to delete controlled vocabulary\/a source",
         "change_vocabulary": "Change controlled vocabulary or source",
         "general_source": "General web resource, i.e. no controlled vocabulary or thesaurus",
         "last_change": "Last changed",
-        "better_not_delete": "No, that was not meant seriously (back)",
+        "better_not_delete": "No, that was not what I meant to do (go back)",
         "better_to_delete": "Of course, I mean what I say. Delete it",
         "sortorder": "Sort order",
         "sequence": "Sequence",
@@ -35,8 +35,8 @@
         "numberinvoc": "ID in vocabulary",
         "linktovoc": "Link into vocabulary",
         "found": "Found:",
-        "wikilink": "Link to wikipedia (New window)",
+        "wikilink": "Link to Wikipedia (New window)",
-        "googlelink": "Google-search (New window)",
+        "googlelink": "Google search (New window)",
         "syngroup": "Synonyms",
         "syngroup_build": "Build group of synonyms",
         "syngroup_add": "Add a synonym",
@@ -52,16 +52,16 @@
         "status_red": "Turns status into UNCHECKED",
         "status_question": "Turns status into TO BE CHECKED",
         "status": "Status",
-        "change_status_to": "change to",
+        "change_status_to": "Change to",
         "unknown": "is unknown",
-        "create_new_entry": "create new entry",
+        "create_new_entry": "Create new entry",
         "or_go_back": "or: Go back",
         "select_with_click": "Select by clicking",
         "noda_source": "Source",
-        "noda_number": "Nr. in source",
+        "noda_number": "No. in source",
         "noda_link": "Link",
         "egal": "Any",
-        "in": "in",
+        "in": "In",
         "containing": "Containing",
         "syncronized_values": "Syncronized values",
         "back_no_change": "Back without changes",

nodac/en/languser.json

@@ -1,7 +1,7 @@
 {
     "languser": {
         "active": "The language of your choice is actually",
-        "choice": "If you like to change the interface language, please take your choice",
+        "choice": "If you like to change the interface language, please choose another one",
         "user_add": "Add new user",
         "userlist": "List of all users",
         "order_by": "Order by",

nodac/en/persinst.json

@@ -1,10 +1,10 @@
 {
     "persinst": {
         "langbezeichnung": "Name (detailed)",
-        "langbezeichnung_explica": "Please always fill in<br><br>Write name of person as: [Given name][ ][Surname][ (][Year of Birth][-][Year of Death][)]<br>Example (person):<br>Achenbach Andreas (1815-1910)<br><br>If years are unknown, just write the name in regular way<br>Example: \"Andreas Achenbach\"<br><br>Names of institution in complete form<br>Example: Brauerei Landsberg GmbH<br><br>If an institution has the name of a person as its name, simply add \"(Company)\"<br>Example: \"A. Lehmann (Company)",
+        "langbezeichnung_explica": "Please always fill in<br><br>Write name of person as: [First name][ ][Surname][ (][Year of Birth][-][Year of Death][)]<br>Example (person):<br>Achenbach Andreas (1815-1910)<br><br>If years are unknown, just write the name in regular way<br>Example: \"Andreas Achenbach\"<br><br>Names of institution in complete form<br>Example: Brauerei Landsberg GmbH<br><br>If an institution has the name of a person as its name, simply add \"(Company)\"<br>Example: \"A. Lehmann (Company)",
         "kurzbezeichnung": "Name (short)",
-        "kurzbezeichnung_explica": "Please always fill in<br><br>Write name of person as: [Surname][,][Given name]<br>Example: Achenbach, Andreas<br><br>Names of institutions in short form<br>Example: Brauerei Landsberg GmbH<br><br>If an institution has the name of a person as its name, simply add \"(Company)\"<br>Example: \"A. Lehmann (Company)",
+        "kurzbezeichnung_explica": "Please always fill in<br><br>Write name of person as: [Surname][,][First name]<br>Example: Achenbach, Andreas<br><br>Names of institutions in short form<br>Example: Brauerei Landsberg GmbH<br><br>If an institution has the name of a person as its name, simply add \"(Company)\"<br>Example: \"A. Lehmann (Company)",
-        "english_name": "... in english",
+        "english_name": "... in English",
         "english_name_explica": "Only fill in if known and different from the original name",
         "birthyear": "Year of birth",
         "birthyear_explica": "Only fill in if known<br><br>A four digit number<br>Example: 1815",
@@ -20,8 +20,8 @@
         "delete_persinst_check": "You are going to delete an entry for a person or institution",
         "attention1": "<b>Attention:<\/b> If you change the year of birth or year of death field for a person-entry you have to change the detailed name too!",
         "name_detailed_contains": "Name contains ...",
-        "unite_titel": "Unite persons etc.",
+        "unite_titel": "Bring people togeter",
-        "unite_with": "unite with",
+        "unite_with": "Unite with",
         "unite_really": "Relly unite?",
         "unite_instruction": "Please click the entity that should be kept.",
         "unite_better_not": "No, better not unite",
@@ -31,9 +31,9 @@
         "please_select": "Please choose a person or institution",
         "new_persinst": "New person or institution",
         "add_superordinates": "Superordinate (Companies etc.)",
-        "add_subordinates": "Subordinate (Firmen etc.)",
+        "add_subordinates": "Subordinate (Companies etc.)",
         "build_group_synonym": "Build group of synonyms for actual term",
         "nominalbezeichnung": "Nominal",
-        "nominalbezeichnung_explica": "The common form the name is used - i.e. without dates for birth and death"
+        "nominalbezeichnung_explica": "The common form of the name is used - i.e. without dates for birth and death"
     }
 }

nodac/en/places.json

@@ -3,12 +3,12 @@
         "name_contains": "Name contains ...",
         "placename": "Placename",
         "unite_names": "Unite locations with",
-        "unite_with": "unite with",
+        "unite_with": "Unite with",
         "unite_leave_mode": "Leave mode \"unification\"",
         "unite_first": "Unite two entries. Please choose first entry.",
         "unite_second": "Unite two entries. Please choose second entry.",
         "in_hierarchy": "The place is part of the hierarchy",
-        "not_in_hierarchy": "The place is NOT a part of the hierarchy",
+        "not_in_hierarchy": "The place is NOT part of the hierarchy",
         "placename_explica": "Please always fill in<br><br>It is a good habit to use the actual name:<br>Example 1: Groningen <br>Example 2: Halle (Saale)<br>Example 3: Soho (London)<br>Beispiel 4: Smaland - in this case use as placetype: \"Region\"\"<br><br>If not avoidable ... you might also use \"Italy\"",
         "placetype": "Place type",
         "placetype_explica": "If the place (or building) is <br><b>not<\/b> an actual place of living (village, city, ...) and <br><b>not<\/b> an actual existing political entity (county, federal state, ...) <br>- than please chose a suitable placetype.<br><br>For actually existing villages, cities, counties ... (and in cases of doubt) please leave empty<br><br>If the place (or building) is not existing anymore than please chose \"historical\"<br><br><b style=\"font-weight:normal;color:#006600;\">Only fill in if suitable<\/b>",
@@ -19,7 +19,7 @@
         "coordinatesNS": "Coordinates, North-South",
         "coordinatesNS_explica": "Please always fill in<br><br>Use \".\" (dot) as decimal separator and use numbers only (- is allowed, of course)<br><br>Example \"Berlin\": 52.518333",
         "coordinatesWE": "Coordinates, West-East",
-        "coordinatesWE_explica": "Bitte immer ausf\u00fcllen<br><br>Please always fill in<br><br>Use \".\" (dot) as decimal separator and use numbers only (- is allowed, of course)<br><br>Example \"Berlin\": 13.408333",
+        "coordinatesWE_explica": "<br><br>Please always fill in<br><br>Use \".\" (dot) as decimal separator and use numbers only (- is allowed, of course)<br><br>Example \"Berlin\": 13.408333",
         "zoom": "Zoom",
         "zoom_explica": "Determines the zoom used on maps. Allowed values: 1-17. Often a good value for a place is: 9, for a country: 7",
         "delete_placename": "Delete the placename",
@@ -30,7 +30,7 @@
         "is_not_the_place": "... this is not the place looked for. Create a new entry",
         "similar_placenames": "There are similar placenames",
         "placename_not_listed": "The placename is not in the list (create a new entry)",
-        "delete_ort_check": "You are about deleting a place",
+        "delete_ort_check": "You are about to delete a place",
         "please_select": "Please select a geographical entity",
         "new_place": "New geographical entity",
         "no_placename": "Please specify a name for the place",

nodac/en/tags.json

@@ -1,18 +1,18 @@
 {
     "tags": {
         "keyword": "Keyword",
-        "keyword_explica": "Any keyword is allowed here. Names of places, persones or timespans do belong to their own vocabularies",
+        "keyword_explica": "Any keyword is allowed here. Names of places, people, or timespans do belong to their own vocabularies",
-        "in_english": "auf englisch",
+        "in_english": "in English",
-        "in_english_explica": "Please provide an english translation. Use the plural form if possible",
+        "in_english_explica": "Please provide an English translation. Use the plural form if possible",
         "remarks": "Remarks",
         "remarks_explica": "Short definition of the keyword. If possible with name of the source",
         "tag_contains": "Keyword contains",
         "alphabet": "Alphabet",
-        "unite_names": "Unify keywords",
+        "unite_names": "Unite keywords",
-        "unite_with": "unify with",
+        "unite_with": "Unite with",
         "unite_leave_mode": "Leave mode \"unification\"",
-        "unite_first": "Unify two tags. Please select the first",
+        "unite_first": "Unite two tags. Please select the first",
-        "unite_second": "Unify two tags. Please select the second",
+        "unite_second": "Unite two tags. Please select the second",
         "add_superordinates": "Broader term",
         "add_subordinates": "Narrower term",
         "add_related": "Related term",
@@ -20,7 +20,7 @@
         "insert_tag": "Please give a keyword",
         "please_select": "Please select a keyword",
         "new_tag": "New tag",
-        "delete_tags_check": "You are about deleting a keyword",
+        "delete_tags_check": "You are about to delete a keyword",
         "broader_generic": "broader generic",
         "broader_partitive": "broader partitive",
         "broader_instantiate": "broader instantiate",

nodac/en/tempi.json

@@ -1,15 +1,15 @@
 {
     "tempi": {
         "timename": "Time name",
-        "counting_time_start": "Counting-time starts with",
+        "counting_time_start": "Counting time starts with",
         "name_contains": "Time name contains",
         "unite_names": "Unite two time names",
-        "unite_with": "unite with",
+        "unite_with": "Unite with",
         "unite_leave_mode": "Leave mode \"unification\"",
         "time_begin": "Begin (Year)",
         "time_end": "End (Year)",
-        "counting_time": "Counting-time",
+        "counting_time": "Counting time",
-        "counting_time_info": "Counting-time - Info",
+        "counting_time_info": "Counting time - Info",
         "annotation": "Remarks",
         "time_tool": "Time tool",
         "time_disassemble": "(Disassemble time)",
@@ -17,29 +17,30 @@
         "time_month": "Month",
         "time_day": "Day",
         "timename_explica": "Please always fill in<br><br>You are free to choose any name<br>Example 1: 16.02.1913 <br>Example 2: 1st half 12. century<br>Example 3: 1655-1699<br><br>(The \"time name\" is a public denomination)",
-        "time_begin_explica": "Please always fill in<br><br>Use 4-digit-values only<br>Example 1: 1913<br>Example 2: -1800<br><br>If the time is B.C. please place a \"-\" (minus) in front<br><br>With time concept like \"Before 1830\", when the beginning is not known, please put a question mark here",
+        "time_begin_explica": "Please always fill in<br><br>Use 4-digit-values only<br>Example 1: 1913<br>Example 2: -1800<br><br>If the time is B.C. please place a \"-\" (minus) in front<br><br>With time concept like \"Before 1830\", when the beginning is not known, please put a question mark here.",
-        "time_end_explica": "Please always fill in<br><br>Use 4-digit-values only<br>Example 1: 1913<br>Example 2: -1800<br><br>If the time is B.C. please place a \"-\" (minus) in front<br><br>With time concept like \"After 1830\", when the end is not known, please put a question mark here",
+        "time_end_explica": "Please always fill in<br><br>Use 4-digit-values only<br>Example 1: 1913<br>Example 2: -1800<br><br>If the time is B.C. please place a \"-\" (minus) in front<br><br>With time concept like \"After 1830\", when the end is not known, please put a question mark here.",
         "counting_time_explica": "Important for internal processing",
         "annotation_explica": "Only fill in if needed<br><br>Keep it short!",
         "please_select": "Please select a time name",
         "new_time": "Create new time name",
         "delete_time": "Delete the time-entry",
-        "delete_time_check": "You are about deleting a time-entry",
+        "delete_time_check": "You are about to delete a time-entry",
         "no_time": "Please give a name for this time",
         "no_time_hint": "Something like \"1784\" or \"12. Januar 1785\" or \"Early mediaval times\"",
         "no_about": "Please use exact names (not starting or ending with \"about\")",
         "no_about_hint": "Uncertainty might be expressed in the event module for objects",
         "no_begin": "Please name a starting point",
         "no_begin_hint": "If the time is a year (e.g. \"1784\"), simply repeat (e.g. \"1784\"). If the begin was before christ, please put \"-\" in front (e.g. \"-1200\"). For time entries like \"until 1902\", where the exact begin is unclear, please put \"?\" here",
-        "no_end": "Please name an ending point",
+        "no_end": "Please enter an end time",
         "no_end_hint": "If the time is a year (e.g. \"1784\"), simply repeat (e.g. \"1784\"). If the end was before christ, please put \"-\" in front (e.g. \"-1200\"). For time entries like \"after 1902\", where the exact end is unclear, please put \"?\" here",
         "no_begin_numeric": "As starting points only years (numeric) are allowed",
         "no_begin_end_numeric_hint": "Please give a year (numeric) - if needed with \"-\" in front",
         "no_end_numeric": "As ending points only years (numeric) are allowed",
-        "no_counting_time": "A (internal) counting-time has to be given always! Minimum: A year (in four digits)",
+        "no_counting_time": "A (internal) counting-time has to always be given! Minimum: A year (in four digits)",
         "no_counting_time_hint": "Eg. \"1784\". With timespans larger than one year please calculate the year in the middle (e.g. Time is \"1870-1880\" -> Counting time is \"1875\". Month and day have to be digits, e.g. month -> \"04\", day -> \"12\" - both might be left empty",
         "wrong_month": "Please give month in the correct way",
         "wrong_day": "Please give day in the correct way",
-        "end_before_start": "Your time starts after it ended"
+        "end_before_start": "Your time starts after it ended",
+        "40": ""
     }
 }

nodac/en/wiki.json

@@ -5,8 +5,8 @@
         "dont_take_description_or_link": "Neither take description nor link",
         "back": "Back",
         "no_dbpedia": "Search in dbpedia was not successful",
-        "no_wikipedia": "Search in wikipedia was not successful",
+        "no_wikipedia": "Search in Wikipedia was not successful",
-        "only_take_exact": "[If the title of the wikipedia-page shown on the right does not  exactly match this term, please do NOT take the link]",
+        "only_take_exact": "[If the title of the Wikipedia page shown on the right does not  exactly match this term, please do NOT take the link]",
         "overwrite_all": "Overwrite all",
         "so_far": "Known so far",
         "new_values": "New values",

themator/en/backend.json

@@ -18,8 +18,8 @@
         "object_select": "Select an object for editing ...",
         "object_edit": "Edit an object ...",
         "object_add": "Add an object ...",
-        "ufo_edit": "Edit an U-F-O ...",
+        "ufo_edit": "Edit a U-F-O ...",
-        "ufo_add": "Add an U-F-O ...",
+        "ufo_add": "Add a U-F-O ...",
         "event_select": "Select an event for editing ...",
         "event_edit": "Edit an event ...",
         "event_add": "Add an event ...",
@@ -32,24 +32,24 @@
         "place_select": "Select a place for editing ...",
         "place_edit": "Edit a place ...",
         "place_add": "Add a place ...",
-        "tag_select": "Select a tag for editing ...",
+        "tag_select": "Select a keyword for editing ...",
-        "tag_edit": "Edit a tag ...",
+        "tag_edit": "Edit a keyword...",
-        "tag_add": "Add a tag ...",
+        "tag_add": "Add a keyword...",
         "literature_select": "Select a literature entry for editing ...",
         "literature_edit": "Edit a literature entry ...",
         "literature_add": "Add a literature entry ...",
         "link_select": "Select a hyperlink for editing ...",
         "link_edit": "Edit hyperlink",
-        "link_add": "Add hyperlink!",
+        "link_add": "Add hyperlink",
         "image_edit": "Select an image for editing ...",
         "document_attach": "Attach a document ...",
-        "tag_select_simple": "Please select a tag ...",
+        "tag_select_simple": "Please select a keyword...",
         "settings_edit": "Edit settings ...",
         "user_select": "Select a user for editing ...",
         "topic_edit": "Edit a <b style=\"color:#3333aa;\">topic<\/b>",
         "subtopic_edit": "Add a <b style=\"color:#3333aa;\">lower level topic<\/b>",
         "document_edit": "Edit document",
-        "source_add": "Add link with a source!",
+        "source_add": "Add link with a source",
         "object_add_complicated": "Add an <b style=\"color:#3333aa;\">object<\/b>",
         "object_edit_complicated": "Edit an <b style=\"color:#3333aa;\">object entry<\/b>",
         "user_role_change_alt": "Changes the relation between a user and a topic",
@@ -58,7 +58,7 @@
         "field": "Field",
         "definitelyconfirm": "Yes!!",
         "explanation_short_title": "<b>Field \"Short Title\"<\/b><br><br>This field is mandatory!<br><br>The short title is used for listing the entry in the navigation<br><br>Example 1: \"Archaology of the Lords of Anhalt\"<br>Example 2: \"Excavations\"",
-        "explanation_long_title": "<b>Field: \"Long Title\"<\/b><br><br>This field is mandatory!<br><br>Der \"Langtitel\" ist der eigentliche Titel des Themas. Bestenfalls nicht mehr als 150 Zeichen.<br><br>Example: \"Arch\u00e4ologie der anhaltischen F\u00fcrsten vom 15. Jahrhundert bis in unsere Tage",
+        "explanation_long_title": "<b>Field: \"Long Title\"<\/b><br><br>This field is mandatory!<br><br>The \"long title\" is the actual title of the topic. At best, it is not more than 150 characters.<br><br>Example: \"Archeology of the Anhalt princes from the 15th century to modern day",
         "explanation_abstract": "<b>Field: \"Abstract\"<\/b><br><br>This field is mandatory!<br><br>Ideally a sentence, that summarizes the topic's contents.",
         "explanation_text": "<b>Field: \"Image Text\"<\/b><br><br>This field is mandatory!<br><br>Unrestricted length of text. Ideally, the text fills about one screen. If possible, write sentences and avoid lists.<br><br>You can - but are not required to - upload an image for the topic. The image will appear on the left of the text.",
         "explanation_text_image": "<b>Field: \"Image Text\"<\/b><br><br>Please only fill this out, if you have uploaded an image for the topic. This text appears upon hovering over the image. Useful for information on copyright and origin.",
@@ -113,7 +113,7 @@
         "user_rights_topics": "Rights for topics",
         "user_institution_nr": "Institution No.",
         "select_by_clicking": "Select by clicking",
-        "here": "here",
+        "here": "Here",
         "higher_level_topic_not_listed": "If the higher level topic is not listed here, then please click",
         "lower_level_topic_not_listed": "If the lower level topic is not listed here, then please click",
         "requirements_caps": "CONDITIONS",
@@ -123,13 +123,13 @@
         "requirements_filesize": "4. The file size should not exceed 4 megabyte. Ideally, the file size should be between 500kb and 900kb.",
         "select_image_to_upload": "Please select the image file you want to upload. It will be automatically resized.",
         "select_large_image_to_upload": "Please selecct the large image file you want to upload. Smaller versions willl be automatically created.",
-        "pdf_select_from_list": "* Here you can upload documents (PDF files only) for a topic - or link documents that have already been uploaded.<br \/>\nIf the document is not listed, then please click",
+        "pdf_select_from_list": "* Here you can upload documents (PDF files only) for a topic - or link documents that have already been uploaded.<br \/>\r\nIf the document is not listed, then please click",
         "requirements_pdf_filename": "1. The file name of the PDF file to be uploaded needs to conform to the following general rules: No special characters. No dots (except the one before the file extension). No spaces.",
         "requirements_pdf_filesize": "2. The file size of the PDF cannot exceed 4 megabyte. ",
         "select_pdf_for_upload": "Please select the PDF file to be uploaded.",
         "explanation_document_kind": "<b>Field: \"Type of Document\"<\/b><br><br>Mandatory<br><br><br>Example 1: \"pdf\"",
         "explanation_document_text": "<b>Field: \"Display Text\"<\/b><br><br>Mandatory<br><br>The text you entered will be displayed when linking the document.",
-        "explanation_document_location": "<b>Field: \"Storage location (link)\"<\/b><br><br>Mandatory",
+        "explanation_document_location": "<b>Field: \"Storage location (link)\"<\/b><br><br>Mandatory<br><br>At best, a sentence summarizing the content of the topic",
         "explanation_document_note": "<b>Field: \"Note\"<\/b><br><br>Not required. Additional information for the document.",
         "type_of_document": "Type of Document",
         "document_display_text": "Display text",
@@ -153,7 +153,7 @@
         "object_alternative_description": "Alternative Object Description",
         "image": "Image",
         "image_text": "Image Text",
-        "image_link": "Target with Clicking on Image",
+        "image_link": "Target for clicking on image",
         "linking_image_mandatory": "For saving, you need to link an image (on the left)",
         "image_change": "Exchange presentation",
         "image_upload": "Upload image",
@@ -162,8 +162,8 @@
         "assigned_to": "Assigned to",
         "preview_in": "Preview in",
         "source_titel": "Title of the Source",
-        "source_list_not_listed": "* Here you can add sources (= references to literature, that is not yet online) or link already known references.<br \/>\nShould the source not be in the list, please click",
+        "source_list_not_listed": "* Here you can add sources (= references to literature, that is not yet online) or link already known references.<br \/>\r\nShould the source not be in the list, please click",
-        "mandatory_title_source": "Sie m\u00fcssen einen Titel f\u00fcr die Quelle angeben!",
+        "mandatory_title_source": "You need to add a title for the souce!",
         "linkdisplayname": "Link Display Name",
         "link": "Link"
     }

themator/en/general.json

@@ -6,6 +6,6 @@
         "expand_all": "Expand all",
         "reduce": "Reduce",
         "objektsfor": "Objects for",
-        "objektsfor_description": "Objektansichten zu Objekten aus diesem und Unterthemen, die dem gegebenen Ort entsprechen."
+        "objektsfor_description": "Object views of objects from this and subtopics that correspond to the given location."
     }
 }

themator/en/startpage.json

@@ -7,6 +7,6 @@
         "english": "English",
         "for_example": "For Example ...",
         "all_topics": "All Topics",
-        "about": "Topics, stories, exhibitions at museum-digital."
+        "about": "Topics, Stories, and Exhibitions at museum-digital."
     }
 }

themator/en/topic_object.json

@@ -2,10 +2,10 @@
     "topic": {
         "material_technique": "Material \/Technique",
         "measurements": "Measurements",
-        "when": "when",
+        "when": "When",
-        "where": "where",
+        "where": "Where",
-        "who": "who",
+        "who": "Who",
         "object_from": "Object from",
-        "original_entry": "original entry"
+        "original_entry": "Original entry"
     }
 }