Maintenance: Translations update from translations.zammad.org

Special thanks to the amazing translation team. You rock! 💪 Co-authored-by: Weblate <[email protected]> Co-authored-by: Ralf Schmid <[email protected]> Co-authored-by: morealedgar <[email protected]>
zammad · Oct 16, 2023 · bef0ecc · bef0ecc
1 parent 42b41d0
commit bef0ecc
Show file tree

Hide file tree

Showing 21 changed files with 890 additions and 480 deletions.
diff --git a/locale/cs/LC_MESSAGES/admin-docs.po b/locale/cs/LC_MESSAGES/admin-docs.po
@@ -7,7 +7,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Zammad\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2023-09-25 14:43+0100\n"
+"POT-Creation-Date: 2023-10-13 14:31+0200\n"
 "PO-Revision-Date: 2023-09-23 01:13+0000\n"
 "Last-Translator: Tomáš Kovařík <[email protected]>\n"
 "Language-Team: Czech <https://translations.zammad.org/projects/"
@@ -21554,57 +21554,57 @@ msgstr ""
 msgid ""
 "You have an empty field which you referenced and it appears as ``-``? That's "
 "currently working as designed - you might want to ensure that these fields "
-"always have a value (in text fields `` `` is a value!)."
+"always have a value."
 msgstr ""
 
-#: ../system/variables.rst:21
+#: ../system/variables.rst:20
 msgid "Variable Categories"
 msgstr ""
 
-#: ../system/variables.rst:32
+#: ../system/variables.rst:31
 msgid "Wait, what about custom objects?"
 msgstr ""
 
-#: ../system/variables.rst:34
+#: ../system/variables.rst:33
 msgid ""
 "Good point! Of course, we can't predict what objects you might create, but "
 "we can give you a hint on how to put the puzzle together to get your custom "
 "values."
 msgstr ""
 
-#: ../system/variables.rst:37
+#: ../system/variables.rst:36
 msgid ""
 "For this, we'll talk about the inner part of the variable (so everything "
 "within ``#{}``), please put the outer part around to have a valid variable. "
 "The first part of the variable name consist of the object type. Currently "
 "these are:"
 msgstr ""
 
-#: ../system/variables.rst:42
+#: ../system/variables.rst:41
 msgid "Ticket (``ticket``)"
 msgstr ""
 
-#: ../system/variables.rst:43
+#: ../system/variables.rst:42
 msgid "User (``user``)"
 msgstr ""
 
-#: ../system/variables.rst:44
+#: ../system/variables.rst:43
 msgid "Organization (``organization``)"
 msgstr ""
 
-#: ../system/variables.rst:45
+#: ../system/variables.rst:44
 msgid "Group (``group``)"
 msgstr ""
 
-#: ../system/variables.rst:47
+#: ../system/variables.rst:46
 msgid ""
 "The second part is the name of the object. This is the name you define "
 "during object creation and can be found within the object menu at any time. "
 "The first and second part of a variable is divided by a point, e.g.: "
 "``ticket.number`` which will in total be ``#{ticket.number}``."
 msgstr ""
 
-#: ../system/variables.rst:52
+#: ../system/variables.rst:51
 msgid ""
 "Now, in some situations it's possible that you'll need to use a third part. "
 "The best example for such a situation would be a ``select`` or ``tree-"

diff --git a/locale/da/LC_MESSAGES/admin-docs.po b/locale/da/LC_MESSAGES/admin-docs.po
@@ -7,7 +7,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Zammad\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2023-09-25 14:43+0100\n"
+"POT-Creation-Date: 2023-10-13 14:31+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: Automatically generated\n"
 "Language-Team: none\n"
@@ -21524,57 +21524,57 @@ msgstr ""
 msgid ""
 "You have an empty field which you referenced and it appears as ``-``? That's "
 "currently working as designed - you might want to ensure that these fields "
-"always have a value (in text fields `` `` is a value!)."
+"always have a value."
 msgstr ""
 
-#: ../system/variables.rst:21
+#: ../system/variables.rst:20
 msgid "Variable Categories"
 msgstr ""
 
-#: ../system/variables.rst:32
+#: ../system/variables.rst:31
 msgid "Wait, what about custom objects?"
 msgstr ""
 
-#: ../system/variables.rst:34
+#: ../system/variables.rst:33
 msgid ""
 "Good point! Of course, we can't predict what objects you might create, but "
 "we can give you a hint on how to put the puzzle together to get your custom "
 "values."
 msgstr ""
 
-#: ../system/variables.rst:37
+#: ../system/variables.rst:36
 msgid ""
 "For this, we'll talk about the inner part of the variable (so everything "
 "within ``#{}``), please put the outer part around to have a valid variable. "
 "The first part of the variable name consist of the object type. Currently "
 "these are:"
 msgstr ""
 
-#: ../system/variables.rst:42
+#: ../system/variables.rst:41
 msgid "Ticket (``ticket``)"
 msgstr ""
 
-#: ../system/variables.rst:43
+#: ../system/variables.rst:42
 msgid "User (``user``)"
 msgstr ""
 
-#: ../system/variables.rst:44
+#: ../system/variables.rst:43
 msgid "Organization (``organization``)"
 msgstr ""
 
-#: ../system/variables.rst:45
+#: ../system/variables.rst:44
 msgid "Group (``group``)"
 msgstr ""
 
-#: ../system/variables.rst:47
+#: ../system/variables.rst:46
 msgid ""
 "The second part is the name of the object. This is the name you define "
 "during object creation and can be found within the object menu at any time. "
 "The first and second part of a variable is divided by a point, e.g.: "
 "``ticket.number`` which will in total be ``#{ticket.number}``."
 msgstr ""
 
-#: ../system/variables.rst:52
+#: ../system/variables.rst:51
 msgid ""
 "Now, in some situations it's possible that you'll need to use a third part. "
 "The best example for such a situation would be a ``select`` or ``tree-"