iobroker.waip-web 0.7.21 → 0.7.26
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.de.md +15 -11
- package/README.md +63 -8
- package/admin/i18n/de.json +5 -5
- package/admin/i18n/en.json +24 -24
- package/admin/i18n/es.json +5 -5
- package/admin/i18n/fr.json +5 -5
- package/admin/i18n/it.json +5 -5
- package/admin/i18n/nl.json +5 -5
- package/admin/i18n/pl.json +5 -5
- package/admin/i18n/pt.json +5 -5
- package/admin/i18n/ru.json +5 -5
- package/admin/i18n/uk.json +5 -5
- package/admin/i18n/zh-cn.json +5 -5
- package/admin/jsonConfig.json +18 -6
- package/io-package.json +178 -70
- package/main.js +20 -8
- package/package.json +1 -1
package/README.de.md
CHANGED
|
@@ -228,14 +228,18 @@ unter [Stichwort-Stammdaten](#stichwort-stammdaten)):
|
|
|
228
228
|
**Rettungsdienst-Dekodierung** (Admin-Checkbox, standardmäßig aus):
|
|
229
229
|
passt das Stichwort auf das Muster `R<Anzahl RTW>N<Anzahl NEF>[p][f][-NT]`
|
|
230
230
|
(z.B. `R1N0` → "Rettungswagen: 1, Notfalleinsatzfahrzeug: 0"), wird
|
|
231
|
-
automatisch eine Beschreibung erzeugt.
|
|
232
|
-
|
|
233
|
-
|
|
234
|
-
|
|
235
|
-
|
|
236
|
-
|
|
237
|
-
|
|
238
|
-
|
|
231
|
+
automatisch eine Beschreibung erzeugt. Zwei Schreibweisen des
|
|
232
|
+
`p`/`f`/`NT`-Teils werden erkannt: ohne Leerzeichen und mit Bindestrich
|
|
233
|
+
vor `NT` (z.B. `R1N1p`, `R1N0-NT`, siehe
|
|
234
|
+
[die dokumentierte Erklärung der Leitstelle Lausitz](https://www.leitstelle-lausitz.de/anpassung-der-einsatzstichworte-rettungsdienst/)
|
|
235
|
+
dazu) sowie mit Leerzeichen und ohne Bindestrich (z.B. `R1N1 p`,
|
|
236
|
+
`R1N0 nt`, wie von der IRLS Brandenburg verwendet) – dieses Schema
|
|
237
|
+
(in beiden Schreibweisen) wird von mehreren Leitstellen verwendet,
|
|
238
|
+
nicht nur diesen beiden – nur aktivieren, wenn eure Leitstelle eines
|
|
239
|
+
dieser Muster tatsächlich verwendet. Der Text für jeden Teil ist
|
|
240
|
+
selbst konfigurierbar (5 zusätzliche Textfelder erscheinen, sobald
|
|
241
|
+
die Checkbox aktiviert ist), da der Adapter mehrsprachig ist und
|
|
242
|
+
diese Bezeichnungen nicht automatisch übersetzt werden:
|
|
239
243
|
|
|
240
244
|
| Teil | Bedeutung | Default-Bezeichnung |
|
|
241
245
|
| --- | --- | --- |
|
|
@@ -243,7 +247,7 @@ automatisch übersetzt werden:
|
|
|
243
247
|
| `N<n>` | Anzahl Notfalleinsatzfahrzeuge | `Notfalleinsatzfahrzeug` |
|
|
244
248
|
| Suffix `p` | Polytrauma | `Polytrauma` |
|
|
245
249
|
| Suffix `f` | First Responder einbezogen | `First Responder` |
|
|
246
|
-
| Suffix `-NT` | Notfalltransport mit Notfallkrankenwagen | `Notfalltransport mit Notfallkrankenwagen` |
|
|
250
|
+
| Suffix `-NT`/` nt` | Notfalltransport mit Notfallkrankenwagen | `Notfalltransport mit Notfallkrankenwagen` |
|
|
247
251
|
|
|
248
252
|
### Stichwort-Stammdaten
|
|
249
253
|
|
|
@@ -253,8 +257,8 @@ hat: eine Liste von `{Stichwort-Muster, Beschreibung, Abgleich-Typ}`-Zeilen
|
|
|
253
257
|
– Abgleich-Typ ist `beginnt mit` oder `enthält`, der Vergleich ist
|
|
254
258
|
case-insensitiv, und passen mehrere Zeilen, gewinnt automatisch das
|
|
255
259
|
**spezifischste (längste) Muster** – die Zeilenreihenfolge hat keinen
|
|
256
|
-
Einfluss auf den Abgleich, die Tabelle kann also gefahrlos nach
|
|
257
|
-
sortiert werden (Klick auf die Spaltenüberschrift). Die Tabelle ist mit
|
|
260
|
+
Einfluss auf den Abgleich, die Tabelle kann also gefahrlos nach jeder
|
|
261
|
+
Spalte sortiert werden (Klick auf die Spaltenüberschrift). Die Tabelle ist mit
|
|
258
262
|
einer beispielhaften Feuerwehr-/Rettungsdienst-Stichwortliste
|
|
259
263
|
(`B:...`/`H:...`) als Startpunkt vorbefüllt – das ist **nicht** für
|
|
260
264
|
irgendeine bestimmte Leitstelle bestätigt, bei Bedarf anpassen oder
|
package/README.md
CHANGED
|
@@ -229,13 +229,17 @@ first of two sources checked, in order (see
|
|
|
229
229
|
**Rescue-service decoding** (admin checkbox, off by default): if the
|
|
230
230
|
keyword matches the pattern `R<RTW-count>N<NEF-count>[p][f][-NT]`
|
|
231
231
|
(e.g. `R1N0` → "Rettungswagen: 1, Notfalleinsatzfahrzeug: 0"), a
|
|
232
|
-
description is generated automatically.
|
|
233
|
-
|
|
232
|
+
description is generated automatically. Two spellings of the `p`/`f`/`NT`
|
|
233
|
+
part are recognized: without a space and with a hyphen before `NT`
|
|
234
|
+
(e.g. `R1N1p`, `R1N0-NT`, see
|
|
234
235
|
[Leitstelle Lausitz's documented explanation](https://www.leitstelle-lausitz.de/anpassung-der-einsatzstichworte-rettungsdienst/)
|
|
235
|
-
of it)
|
|
236
|
-
|
|
237
|
-
|
|
238
|
-
|
|
236
|
+
of it), and with a space and without a hyphen (e.g. `R1N1 p`, `R1N0 nt`,
|
|
237
|
+
as used by the IRLS Brandenburg) – this scheme (in either spelling) is
|
|
238
|
+
used by several German dispatch centers, not just these two – only
|
|
239
|
+
enable it if your dispatch center actually uses one of these patterns.
|
|
240
|
+
The text for each part is itself configurable (5 additional text
|
|
241
|
+
fields appear once the checkbox is enabled), since the adapter is
|
|
242
|
+
multi-language and these labels aren't translated automatically:
|
|
239
243
|
|
|
240
244
|
| Part | Meaning | Default label |
|
|
241
245
|
| --- | --- | --- |
|
|
@@ -243,7 +247,7 @@ is multi-language and these labels aren't translated automatically:
|
|
|
243
247
|
| `N<n>` | Number of emergency vehicles (Notfalleinsatzfahrzeug) | `Notfalleinsatzfahrzeug` |
|
|
244
248
|
| `p` suffix | Polytrauma | `Polytrauma` |
|
|
245
249
|
| `f` suffix | First responder included | `First Responder` |
|
|
246
|
-
| `-NT` suffix | Special ambulance transport | `Notfalltransport mit Notfallkrankenwagen` |
|
|
250
|
+
| `-NT`/` nt` suffix | Special ambulance transport | `Notfalltransport mit Notfallkrankenwagen` |
|
|
247
251
|
|
|
248
252
|
### Keyword descriptions
|
|
249
253
|
|
|
@@ -252,7 +256,7 @@ tab didn't match: a list of `{keyword pattern, description, match type}`
|
|
|
252
256
|
rows – match type is `starts with` or `contains`, comparison is
|
|
253
257
|
case-insensitive, and if several rows match, the **most specific
|
|
254
258
|
(longest) pattern wins automatically** – row order has no effect on
|
|
255
|
-
matching, so the table can be freely sorted by
|
|
259
|
+
matching, so the table can be freely sorted by any column (click the
|
|
256
260
|
column header) without changing behavior. The table is pre-filled
|
|
257
261
|
with an example fire/rescue keyword list (`B:...`/`H:...`) as a
|
|
258
262
|
starting point only – it is **not** confirmed to match any specific
|
|
@@ -404,6 +408,57 @@ example.
|
|
|
404
408
|
|
|
405
409
|
## Changelog
|
|
406
410
|
|
|
411
|
+
### 0.7.26 (2026-08-23)
|
|
412
|
+
|
|
413
|
+
- [Keyword descriptions](#keyword-descriptions) tab: `Description` and
|
|
414
|
+
`Match` columns are now sortable too (previously only `Keyword /
|
|
415
|
+
pattern`), and the table's help text was moved above the table
|
|
416
|
+
instead of below - with many rows it used to sit far out of view.
|
|
417
|
+
|
|
418
|
+
### 0.7.25 (2026-08-23)
|
|
419
|
+
|
|
420
|
+
- Updated the admin UI text for the [rescue-service decoder](#rescue-service-keywords)
|
|
421
|
+
to reflect the two supported keyword spellings added in 0.7.23
|
|
422
|
+
(Leitstelle Lausitz `R1N1p`/`R1N0-NT` and IRLS Brandenburg `R1N1 p`/
|
|
423
|
+
`R1N0 nt`) - the checkbox label/help and the NT suffix label/help
|
|
424
|
+
previously only mentioned the hyphenated no-space form.
|
|
425
|
+
|
|
426
|
+
### 0.7.24 (2026-08-23)
|
|
427
|
+
|
|
428
|
+
- Extended the default [keyword table](#keyword-descriptions) with two
|
|
429
|
+
more Brandenburg spelling variants: `B:Gebäude-Groß` and
|
|
430
|
+
`B:Gebäude-Klein` (hyphen instead of space, as used by some dispatch
|
|
431
|
+
centers) - same descriptions as the existing `B:Gebäude groß`/`B:Gebäude
|
|
432
|
+
klein` entries. Only affects the shipped example table for new
|
|
433
|
+
installs - existing configured tables are untouched.
|
|
434
|
+
|
|
435
|
+
### 0.7.23 (2026-08-23)
|
|
436
|
+
|
|
437
|
+
- Extended the default [keyword table](#keyword-descriptions) with the
|
|
438
|
+
29 `K`/`V`/`M`/`S` keywords (Krankentransport, Verlegung, MANV,
|
|
439
|
+
Sonderstichwörter) from the IRLS Brandenburg rescue-service catalog
|
|
440
|
+
(v2.7) - previously only the `R<ambulance>N<physician-vehicle>`
|
|
441
|
+
scheme and the Brand/THL (`B:`/`H:`) table were covered, so
|
|
442
|
+
`einsatz.beschreibung` stayed `null` for these.
|
|
443
|
+
- Fixed the [rescue-service keyword](#rescue-service-keywords) decoder
|
|
444
|
+
(`decodeRettungsdienstStichwort`): it only accepted the Leitstelle
|
|
445
|
+
Lausitz spelling without a space (`R1N1p`, `R1N0-NT`) and silently
|
|
446
|
+
returned `null` for the IRLS Brandenburg spelling with a space
|
|
447
|
+
(`R1N1 p`, `R1N0 nt`) - both are now recognized.
|
|
448
|
+
- Only affects the shipped example table and the decoder logic for
|
|
449
|
+
new installs/upgrades - existing configured tables are untouched.
|
|
450
|
+
|
|
451
|
+
### 0.7.22 (2026-08-23)
|
|
452
|
+
|
|
453
|
+
- Extended the default [keyword table](#keyword-descriptions) with
|
|
454
|
+
`H:Person-TMR` (technical human rescue) and corrected three entries
|
|
455
|
+
whose pattern didn't match the actual dispatch keyword:
|
|
456
|
+
`H:Flugunfall` → `H:Flugzeugunfall` (`klein`/`groß`), `H:Öl Wasser`
|
|
457
|
+
→ `H:Öl auf Wasser`, `H:Rettung aus Höhen/Tiefen` → `H:Rettung aus
|
|
458
|
+
Höhen und Tiefen` (source: Regionalleitstellen Brandenburg keyword
|
|
459
|
+
list, v7.1). Only affects the shipped example table for new
|
|
460
|
+
installs - existing configured tables are untouched.
|
|
461
|
+
|
|
407
462
|
### 0.7.21 (2026-08-23)
|
|
408
463
|
|
|
409
464
|
- Removed the keyword table's CSV export/import: a bug in ioBroker
|
package/admin/i18n/de.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"Alarm keyword descriptions": "Stichwort-Stammdaten",
|
|
3
|
-
"Automatically decode rescue-service keywords (R<RTW>N<NEF>[p][f][-NT])": "Rettungsdienst-Stichwörter automatisch dekodieren (R<RTW>N<NEF>[p][f][-NT])",
|
|
3
|
+
"Automatically decode rescue-service keywords (R<RTW>N<NEF>[p][f][-NT], with or without spaces)": "Rettungsdienst-Stichwörter automatisch dekodieren (R<RTW>N<NEF>[p][f][-NT], mit oder ohne Leerzeichen)",
|
|
4
4
|
"Base URL of the WAIP dispatch server (Socket.IO endpoint, namespace /waip is appended automatically)": "Basis-URL des WAIP-Leitstellenservers (Socket.IO-Endpunkt, Namespace /waip wird automatisch angehängt)",
|
|
5
5
|
"Connection": "Verbindung",
|
|
6
6
|
"Description": "Beschreibung",
|
|
@@ -9,18 +9,18 @@
|
|
|
9
9
|
"Keyword descriptions": "Stichwort-Stammdaten",
|
|
10
10
|
"Label for N (emergency vehicle count)": "Bezeichnung für N (Anzahl Notfalleinsatzfahrzeuge)",
|
|
11
11
|
"Label for R (ambulance count)": "Bezeichnung für R (Anzahl Rettungswagen)",
|
|
12
|
-
"Label for suffix -NT (special ambulance transport)": "Bezeichnung für Suffix -NT (Notfalltransport)",
|
|
12
|
+
"Label for suffix -NT / nt (special ambulance transport)": "Bezeichnung für Suffix -NT / nt (Notfalltransport mit Notfallkrankenwagen)",
|
|
13
13
|
"Label for suffix f (first responder)": "Bezeichnung für Suffix f (First Responder)",
|
|
14
14
|
"Label for suffix p (polytrauma)": "Bezeichnung für Suffix p (Polytrauma)",
|
|
15
15
|
"Loaded live from the configured server's /waip/ overview page - choose by Leitstelle, Kreis, Träger or Wache, or pick 'Alle Wachalarme' (ID 0) for every incident. If the server can't be reached, an ID can still be entered manually.": "Wird live von der /waip/-Übersichtsseite des konfigurierten Servers geladen - Auswahl nach Leitstelle, Kreis, Träger oder Wache, oder 'Alle Wachalarme' (ID 0) für jeden Einsatz. Ist der Server nicht erreichbar, kann die ID weiterhin manuell eingegeben werden.",
|
|
16
|
-
"Maps einsatz.stichwort to einsatz.beschreibung. If several rows match, the most specific (longest) pattern wins automatically - row order has no effect on matching, sort by
|
|
16
|
+
"Maps einsatz.stichwort to einsatz.beschreibung. If several rows match, the most specific (longest) pattern wins automatically - row order has no effect on matching, sort by any column freely. Pre-filled with an example fire/rescue keyword list as a starting point - it is not confirmed to match your own dispatch center's actual keywords, edit/replace as needed. To back up or transfer this table, use ioBroker's standard instance configuration export/import (JSON). After using that import, reload the Admin page before checking this table - the open config dialog doesn't refresh it from an external import automatically (a state-sync limitation of the Admin table component itself).": "Ordnet einsatz.stichwort eine Beschreibung für einsatz.beschreibung zu. Passen mehrere Zeilen, gewinnt automatisch das spezifischste (längste) Muster - die Zeilenreihenfolge hat keinen Einfluss auf den Abgleich, die Tabelle kann also frei nach jeder Spalte sortiert werden. Vorbefüllt mit einer beispielhaften Feuerwehr-/Rettungsdienst-Stichwortliste als Startpunkt - nicht bestätigt für eure eigene Leitstelle, bei Bedarf anpassen/ersetzen. Zum Sichern/Übertragen dieser Tabelle die Standard-Instanzkonfiguration von ioBroker exportieren/importieren (JSON). Nach einem solchen Import die Admin-Seite neu laden, bevor du diese Tabelle prüfst - der offene Konfigurationsdialog aktualisiert sie bei einem externen Import nicht automatisch (eine State-Sync-Einschränkung der Admin-Tabellenkomponente selbst).",
|
|
17
17
|
"Match": "Abgleich",
|
|
18
18
|
"Monitor ID": "Monitor-ID",
|
|
19
19
|
"Reconnect delay (s)": "Wiederverbindungs-Verzögerung (s)",
|
|
20
20
|
"Registration timeout (s)": "Registrierungs-Timeout (s)",
|
|
21
|
-
"Rescue-service keyword scheme
|
|
21
|
+
"Rescue-service keyword scheme R<RTW>N<NEF>, optionally followed by a p/f modifier and/or an NT suffix (e.g. \"R1N0\" = 1 ambulance, no emergency physician). Two spellings are recognized: without a space and with a hyphen before NT (Leitstelle Lausitz, e.g. \"R1N1p\", \"R1N0-NT\") and with a space and without a hyphen (Leitstelle Brandenburg/IRLS, e.g. \"R1N1 p\", \"R1N0 nt\") - only enable if your dispatch center actually uses one of these patterns. Takes priority over the table on the Keyword descriptions tab when a keyword matches.": "Rettungsdienst-Stichwortschema R<RTW>N<NEF>, optional gefolgt von einem p/f-Modifikator und/oder einem NT-Suffix (z.B. \"R1N0\" = 1 Rettungswagen, kein Notarzt). Zwei Schreibweisen werden erkannt: ohne Leerzeichen und mit Bindestrich vor NT (Leitstelle Lausitz, z.B. \"R1N1p\", \"R1N0-NT\") sowie mit Leerzeichen und ohne Bindestrich (Leitstelle Brandenburg/IRLS, z.B. \"R1N1 p\", \"R1N0 nt\") - nur aktivieren, wenn eure Leitstelle eines dieser Muster tatsächlich verwendet. Hat Vorrang vor der Tabelle im Tab Stichwort-Stammdaten, wenn ein Stichwort passt.",
|
|
22
22
|
"Rescue-service keywords": "Rettungsdienst-Stichwörter",
|
|
23
|
-
"Text appended when the keyword ends in \"-NT\".": "Text, der angehängt wird, wenn das Stichwort auf \"-NT\" endet.",
|
|
23
|
+
"Text appended when the keyword ends in \"-NT\" or \" nt\".": "Text, der angehängt wird, wenn das Stichwort auf \"-NT\" oder \" nt\" endet.",
|
|
24
24
|
"Text appended when the keyword ends in \"f\".": "Text, der angehängt wird, wenn das Stichwort auf \"f\" endet.",
|
|
25
25
|
"Text appended when the keyword ends in \"p\".": "Text, der angehängt wird, wenn das Stichwort auf \"p\" endet.",
|
|
26
26
|
"Text used in the generated description for the N<n> part, e.g. \"Notfalleinsatzfahrzeug: 0\".": "Text für den N<n>-Teil der erzeugten Beschreibung, z.B. \"Notfalleinsatzfahrzeug: 0\".",
|
package/admin/i18n/en.json
CHANGED
|
@@ -1,32 +1,32 @@
|
|
|
1
1
|
{
|
|
2
|
-
"
|
|
2
|
+
"Alarm keyword descriptions": "Alarm keyword descriptions",
|
|
3
|
+
"Automatically decode rescue-service keywords (R<RTW>N<NEF>[p][f][-NT], with or without spaces)": "Automatically decode rescue-service keywords (R<RTW>N<NEF>[p][f][-NT], with or without spaces)",
|
|
3
4
|
"Base URL of the WAIP dispatch server (Socket.IO endpoint, namespace /waip is appended automatically)": "Base URL of the WAIP dispatch server (Socket.IO endpoint, namespace /waip is appended automatically)",
|
|
4
|
-
"Monitor ID": "Monitor ID",
|
|
5
|
-
"Loaded live from the configured server's /waip/ overview page - choose by Leitstelle, Kreis, Träger or Wache, or pick 'Alle Wachalarme' (ID 0) for every incident. If the server can't be reached, an ID can still be entered manually.": "Loaded live from the configured server's /waip/ overview page - choose by Leitstelle, Kreis, Träger or Wache, or pick 'Alle Wachalarme' (ID 0) for every incident. If the server can't be reached, an ID can still be entered manually.",
|
|
6
|
-
"Registration timeout (s)": "Registration timeout (s)",
|
|
7
|
-
"How long to wait for the server to confirm the monitor registration before logging a warning; the connection itself keeps running either way.": "How long to wait for the server to confirm the monitor registration before logging a warning; the connection itself keeps running either way.",
|
|
8
|
-
"Reconnect delay (s)": "Reconnect delay (s)",
|
|
9
|
-
"Wait time before the adapter automatically reconnects after a lost connection or a connection error.": "Wait time before the adapter automatically reconnects after a lost connection or a connection error.",
|
|
10
|
-
"Automatically decode rescue-service keywords (R<RTW>N<NEF>[p][f][-NT])": "Automatically decode rescue-service keywords (R<RTW>N<NEF>[p][f][-NT])",
|
|
11
|
-
"Rescue-service keyword scheme (R<RTW>N<NEF>[p][f][-NT], e.g. \"R1N0\" = 1 ambulance, no emergency physician) used by several German dispatch centers (documented example: Leitstelle Lausitz) - only enable if your dispatch center actually uses this pattern. Takes priority over the table on the Keyword descriptions tab when a keyword matches.": "Rescue-service keyword scheme (R<RTW>N<NEF>[p][f][-NT], e.g. \"R1N0\" = 1 ambulance, no emergency physician) used by several German dispatch centers (documented example: Leitstelle Lausitz) - only enable if your dispatch center actually uses this pattern. Takes priority over the table on the Keyword descriptions tab when a keyword matches.",
|
|
12
5
|
"Connection": "Connection",
|
|
13
|
-
"
|
|
6
|
+
"Description": "Description",
|
|
7
|
+
"How long to wait for the server to confirm the monitor registration before logging a warning; the connection itself keeps running either way.": "How long to wait for the server to confirm the monitor registration before logging a warning; the connection itself keeps running either way.",
|
|
8
|
+
"Keyword / pattern": "Keyword / pattern",
|
|
14
9
|
"Keyword descriptions": "Keyword descriptions",
|
|
15
|
-
"Label for R (ambulance count)": "Label for R (ambulance count)",
|
|
16
|
-
"Text used in the generated description for the R<n> part, e.g. \"Rettungswagen: 1\".": "Text used in the generated description for the R<n> part, e.g. \"Rettungswagen: 1\".",
|
|
17
10
|
"Label for N (emergency vehicle count)": "Label for N (emergency vehicle count)",
|
|
18
|
-
"
|
|
19
|
-
"Label for suffix
|
|
20
|
-
"Text appended when the keyword ends in \"p\".": "Text appended when the keyword ends in \"p\".",
|
|
11
|
+
"Label for R (ambulance count)": "Label for R (ambulance count)",
|
|
12
|
+
"Label for suffix -NT / nt (special ambulance transport)": "Label for suffix -NT / nt (special ambulance transport)",
|
|
21
13
|
"Label for suffix f (first responder)": "Label for suffix f (first responder)",
|
|
22
|
-
"
|
|
23
|
-
"
|
|
24
|
-
"
|
|
25
|
-
"Alarm keyword descriptions": "Alarm keyword descriptions",
|
|
26
|
-
"Maps einsatz.stichwort to einsatz.beschreibung. If several rows match, the most specific (longest) pattern wins automatically - row order has no effect on matching, sort by keyword freely. Pre-filled with an example fire/rescue keyword list as a starting point - it is not confirmed to match your own dispatch center's actual keywords, edit/replace as needed. To back up or transfer this table, use ioBroker's standard instance configuration export/import (JSON). After using that import, reload the Admin page before checking this table - the open config dialog doesn't refresh it from an external import automatically (a state-sync limitation of the Admin table component itself).": "Maps einsatz.stichwort to einsatz.beschreibung. If several rows match, the most specific (longest) pattern wins automatically - row order has no effect on matching, sort by keyword freely. Pre-filled with an example fire/rescue keyword list as a starting point - it is not confirmed to match your own dispatch center's actual keywords, edit/replace as needed. To back up or transfer this table, use ioBroker's standard instance configuration export/import (JSON). After using that import, reload the Admin page before checking this table - the open config dialog doesn't refresh it from an external import automatically (a state-sync limitation of the Admin table component itself).",
|
|
27
|
-
"Keyword / pattern": "Keyword / pattern",
|
|
28
|
-
"Description": "Description",
|
|
14
|
+
"Label for suffix p (polytrauma)": "Label for suffix p (polytrauma)",
|
|
15
|
+
"Loaded live from the configured server's /waip/ overview page - choose by Leitstelle, Kreis, Träger or Wache, or pick 'Alle Wachalarme' (ID 0) for every incident. If the server can't be reached, an ID can still be entered manually.": "Loaded live from the configured server's /waip/ overview page - choose by Leitstelle, Kreis, Träger or Wache, or pick 'Alle Wachalarme' (ID 0) for every incident. If the server can't be reached, an ID can still be entered manually.",
|
|
16
|
+
"Maps einsatz.stichwort to einsatz.beschreibung. If several rows match, the most specific (longest) pattern wins automatically - row order has no effect on matching, sort by any column freely. Pre-filled with an example fire/rescue keyword list as a starting point - it is not confirmed to match your own dispatch center's actual keywords, edit/replace as needed. To back up or transfer this table, use ioBroker's standard instance configuration export/import (JSON). After using that import, reload the Admin page before checking this table - the open config dialog doesn't refresh it from an external import automatically (a state-sync limitation of the Admin table component itself).": "Maps einsatz.stichwort to einsatz.beschreibung. If several rows match, the most specific (longest) pattern wins automatically - row order has no effect on matching, sort by any column freely. Pre-filled with an example fire/rescue keyword list as a starting point - it is not confirmed to match your own dispatch center's actual keywords, edit/replace as needed. To back up or transfer this table, use ioBroker's standard instance configuration export/import (JSON). After using that import, reload the Admin page before checking this table - the open config dialog doesn't refresh it from an external import automatically (a state-sync limitation of the Admin table component itself).",
|
|
29
17
|
"Match": "Match",
|
|
30
|
-
"
|
|
31
|
-
"
|
|
18
|
+
"Monitor ID": "Monitor ID",
|
|
19
|
+
"Reconnect delay (s)": "Reconnect delay (s)",
|
|
20
|
+
"Registration timeout (s)": "Registration timeout (s)",
|
|
21
|
+
"Rescue-service keyword scheme R<RTW>N<NEF>, optionally followed by a p/f modifier and/or an NT suffix (e.g. \"R1N0\" = 1 ambulance, no emergency physician). Two spellings are recognized: without a space and with a hyphen before NT (Leitstelle Lausitz, e.g. \"R1N1p\", \"R1N0-NT\") and with a space and without a hyphen (Leitstelle Brandenburg/IRLS, e.g. \"R1N1 p\", \"R1N0 nt\") - only enable if your dispatch center actually uses one of these patterns. Takes priority over the table on the Keyword descriptions tab when a keyword matches.": "Rescue-service keyword scheme R<RTW>N<NEF>, optionally followed by a p/f modifier and/or an NT suffix (e.g. \"R1N0\" = 1 ambulance, no emergency physician). Two spellings are recognized: without a space and with a hyphen before NT (Leitstelle Lausitz, e.g. \"R1N1p\", \"R1N0-NT\") and with a space and without a hyphen (Leitstelle Brandenburg/IRLS, e.g. \"R1N1 p\", \"R1N0 nt\") - only enable if your dispatch center actually uses one of these patterns. Takes priority over the table on the Keyword descriptions tab when a keyword matches.",
|
|
22
|
+
"Rescue-service keywords": "Rescue-service keywords",
|
|
23
|
+
"Text appended when the keyword ends in \"-NT\" or \" nt\".": "Text appended when the keyword ends in \"-NT\" or \" nt\".",
|
|
24
|
+
"Text appended when the keyword ends in \"f\".": "Text appended when the keyword ends in \"f\".",
|
|
25
|
+
"Text appended when the keyword ends in \"p\".": "Text appended when the keyword ends in \"p\".",
|
|
26
|
+
"Text used in the generated description for the N<n> part, e.g. \"Notfalleinsatzfahrzeug: 0\".": "Text used in the generated description for the N<n> part, e.g. \"Notfalleinsatzfahrzeug: 0\".",
|
|
27
|
+
"Text used in the generated description for the R<n> part, e.g. \"Rettungswagen: 1\".": "Text used in the generated description for the R<n> part, e.g. \"Rettungswagen: 1\".",
|
|
28
|
+
"WAIP server URL": "WAIP server URL",
|
|
29
|
+
"Wait time before the adapter automatically reconnects after a lost connection or a connection error.": "Wait time before the adapter automatically reconnects after a lost connection or a connection error.",
|
|
30
|
+
"contains": "contains",
|
|
31
|
+
"starts with": "starts with"
|
|
32
32
|
}
|
package/admin/i18n/es.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"Alarm keyword descriptions": "Descripciones de palabras clave de alarma",
|
|
3
|
-
"Automatically decode rescue-service keywords (R<RTW>N<NEF>[p][f][-NT])": "Decodificar automáticamente palabras clave del servicio de rescate (R<RTW>N<NEF>[p][f][-NT])",
|
|
3
|
+
"Automatically decode rescue-service keywords (R<RTW>N<NEF>[p][f][-NT], with or without spaces)": "Decodificar automáticamente las palabras clave del servicio de rescate (R<RTW>N<NEF>[p][f][-NT], con o sin espacios)",
|
|
4
4
|
"Base URL of the WAIP dispatch server (Socket.IO endpoint, namespace /waip is appended automatically)": "URL base del servidor de envío WAIP (punto final Socket.IO, el espacio de nombres /waip se agrega automáticamente)",
|
|
5
5
|
"Connection": "Conexión",
|
|
6
6
|
"Description": "Descripción",
|
|
@@ -9,18 +9,18 @@
|
|
|
9
9
|
"Keyword descriptions": "Descripciones de palabras clave",
|
|
10
10
|
"Label for N (emergency vehicle count)": "Etiqueta para N (recuento de vehículos de emergencia)",
|
|
11
11
|
"Label for R (ambulance count)": "Etiqueta para R (recuento de ambulancias)",
|
|
12
|
-
"Label for suffix -NT (special ambulance transport)": "Etiqueta para el sufijo -NT (transporte especial en ambulancia)",
|
|
12
|
+
"Label for suffix -NT / nt (special ambulance transport)": "Etiqueta para el sufijo -NT / nt (transporte especial en ambulancia)",
|
|
13
13
|
"Label for suffix f (first responder)": "Etiqueta para el sufijo f (primer interviniente)",
|
|
14
14
|
"Label for suffix p (polytrauma)": "Etiqueta para el sufijo p (politraumatismo)",
|
|
15
15
|
"Loaded live from the configured server's /waip/ overview page - choose by Leitstelle, Kreis, Träger or Wache, or pick 'Alle Wachalarme' (ID 0) for every incident. If the server can't be reached, an ID can still be entered manually.": "Cargado en vivo desde la página de descripción general /waip/ del servidor configurado: elija Leitstelle, Kreis, Träger o Wache, o elija 'Alle Wachalarme' (ID 0) para cada incidente. Si no se puede acceder al servidor, aún se puede ingresar una identificación manualmente.",
|
|
16
|
-
"Maps einsatz.stichwort to einsatz.beschreibung. If several rows match, the most specific (longest) pattern wins automatically - row order has no effect on matching, sort by
|
|
16
|
+
"Maps einsatz.stichwort to einsatz.beschreibung. If several rows match, the most specific (longest) pattern wins automatically - row order has no effect on matching, sort by any column freely. Pre-filled with an example fire/rescue keyword list as a starting point - it is not confirmed to match your own dispatch center's actual keywords, edit/replace as needed. To back up or transfer this table, use ioBroker's standard instance configuration export/import (JSON). After using that import, reload the Admin page before checking this table - the open config dialog doesn't refresh it from an external import automatically (a state-sync limitation of the Admin table component itself).": "Asigna einsatz.stichwort a einsatz.beschreibung. Si varias filas coinciden, el patrón más específico (el más largo) gana automáticamente; el orden de las filas no tiene ningún efecto en la coincidencia, ordene libremente por cualquier columna. Precompletado con una lista de palabras clave de ejemplo de incendio/rescate como punto de partida; no se confirma que coincida con las palabras clave reales de su propio centro de despacho, edite/reemplace según sea necesario. Para hacer una copia de seguridad o transferir esta tabla, utilice la exportación/importación estándar de la configuración de instancia de ioBroker (JSON). Después de usar esa importación estándar, recargue la página de administración antes de comprobar esta tabla - el cuadro de diálogo de configuración abierto no la actualiza automáticamente desde una importación externa (una limitación de sincronización de estado del propio componente de tabla de administración).",
|
|
17
17
|
"Match": "Fósforo",
|
|
18
18
|
"Monitor ID": "Identificador del monitor",
|
|
19
19
|
"Reconnect delay (s)": "Retardo(s) de reconexión",
|
|
20
20
|
"Registration timeout (s)": "Tiempos de espera de registro",
|
|
21
|
-
"Rescue-service keyword scheme
|
|
21
|
+
"Rescue-service keyword scheme R<RTW>N<NEF>, optionally followed by a p/f modifier and/or an NT suffix (e.g. \"R1N0\" = 1 ambulance, no emergency physician). Two spellings are recognized: without a space and with a hyphen before NT (Leitstelle Lausitz, e.g. \"R1N1p\", \"R1N0-NT\") and with a space and without a hyphen (Leitstelle Brandenburg/IRLS, e.g. \"R1N1 p\", \"R1N0 nt\") - only enable if your dispatch center actually uses one of these patterns. Takes priority over the table on the Keyword descriptions tab when a keyword matches.": "Esquema de palabras clave del servicio de rescate R<RTW>N<NEF>, seguido opcionalmente de un modificador p/f y/o un sufijo NT (p. ej. \"R1N0\" = 1 ambulancia, sin médico de urgencias). Se reconocen dos escrituras: sin espacio y con guion antes de NT (Leitstelle Lausitz, p. ej. \"R1N1p\", \"R1N0-NT\") y con espacio y sin guion (Leitstelle Brandeburgo/IRLS, p. ej. \"R1N1 p\", \"R1N0 nt\") - actívelo solo si su central de despacho utiliza realmente uno de estos patrones. Tiene prioridad sobre la tabla de la pestaña Descripciones de palabras clave cuando una palabra clave coincide.",
|
|
22
22
|
"Rescue-service keywords": "Palabras clave del servicio de rescate",
|
|
23
|
-
"Text appended when the keyword ends in \"-NT\".": "Texto añadido cuando la palabra clave termina en \"-NT\".",
|
|
23
|
+
"Text appended when the keyword ends in \"-NT\" or \" nt\".": "Texto añadido cuando la palabra clave termina en \"-NT\" o \" nt\".",
|
|
24
24
|
"Text appended when the keyword ends in \"f\".": "Texto añadido cuando la palabra clave termina en \"f\".",
|
|
25
25
|
"Text appended when the keyword ends in \"p\".": "Texto añadido cuando la palabra clave termina en \"p\".",
|
|
26
26
|
"Text used in the generated description for the N<n> part, e.g. \"Notfalleinsatzfahrzeug: 0\".": "Texto utilizado en la descripción generada para la parte N<n>, p.e. \"Notfalleinsatzfahrzeug: 0\".",
|
package/admin/i18n/fr.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"Alarm keyword descriptions": "Descriptions des mots-clés d'alarme",
|
|
3
|
-
"Automatically decode rescue-service keywords (R<RTW>N<NEF>[p][f][-NT])": "Décoder automatiquement les mots-clés
|
|
3
|
+
"Automatically decode rescue-service keywords (R<RTW>N<NEF>[p][f][-NT], with or without spaces)": "Décoder automatiquement les mots-clés des services de secours (R<RTW>N<NEF>[p][f][-NT], avec ou sans espaces)",
|
|
4
4
|
"Base URL of the WAIP dispatch server (Socket.IO endpoint, namespace /waip is appended automatically)": "URL de base du serveur de répartition WAIP (point de terminaison Socket.IO, l'espace de noms /waip est ajouté automatiquement)",
|
|
5
5
|
"Connection": "Connexion",
|
|
6
6
|
"Description": "Description",
|
|
@@ -9,18 +9,18 @@
|
|
|
9
9
|
"Keyword descriptions": "Descriptions des mots-clés",
|
|
10
10
|
"Label for N (emergency vehicle count)": "Étiquette pour N (nombre de véhicules d'urgence)",
|
|
11
11
|
"Label for R (ambulance count)": "Étiquette pour R (nombre d'ambulances)",
|
|
12
|
-
"Label for suffix -NT (special ambulance transport)": "
|
|
12
|
+
"Label for suffix -NT / nt (special ambulance transport)": "Libellé pour le suffixe -NT / nt (transport spécial en ambulance)",
|
|
13
13
|
"Label for suffix f (first responder)": "Étiquette pour le suffixe f (premier intervenant)",
|
|
14
14
|
"Label for suffix p (polytrauma)": "Étiquette pour le suffixe p (polytraumatisme)",
|
|
15
15
|
"Loaded live from the configured server's /waip/ overview page - choose by Leitstelle, Kreis, Träger or Wache, or pick 'Alle Wachalarme' (ID 0) for every incident. If the server can't be reached, an ID can still be entered manually.": "Chargé en direct depuis la page de présentation /waip/ du serveur configuré - choisissez par Leitstelle, Kreis, Träger ou Wache, ou choisissez 'Alle Wachalarme' (ID 0) pour chaque incident. Si le serveur n'est pas accessible, un identifiant peut toujours être saisi manuellement.",
|
|
16
|
-
"Maps einsatz.stichwort to einsatz.beschreibung. If several rows match, the most specific (longest) pattern wins automatically - row order has no effect on matching, sort by
|
|
16
|
+
"Maps einsatz.stichwort to einsatz.beschreibung. If several rows match, the most specific (longest) pattern wins automatically - row order has no effect on matching, sort by any column freely. Pre-filled with an example fire/rescue keyword list as a starting point - it is not confirmed to match your own dispatch center's actual keywords, edit/replace as needed. To back up or transfer this table, use ioBroker's standard instance configuration export/import (JSON). After using that import, reload the Admin page before checking this table - the open config dialog doesn't refresh it from an external import automatically (a state-sync limitation of the Admin table component itself).": "Mappe einsatz.stichwort à einsatz.beschreibung. Si plusieurs lignes correspondent, le modèle le plus spécifique (le plus long) l'emporte automatiquement - l'ordre des lignes n'a aucun effet sur la correspondance, triez-la librement par n'importe quelle colonne. Pré-rempli avec un exemple de liste de mots-clés d'incendie/sauvetage comme point de départ - il n'est pas confirmé qu'il correspond aux mots-clés réels de votre propre centre de répartition, modifiez/remplacez si nécessaire. Pour sauvegarder ou transférer ce tableau, utilisez l'export/import standard de la configuration d'instance d'ioBroker (JSON). Après avoir utilisé cet import standard, rechargez la page Admin avant de vérifier ce tableau - la boîte de dialogue de configuration ouverte ne l'actualise pas automatiquement après un import externe (une limitation de synchronisation d'état du composant de tableau Admin lui-même).",
|
|
17
17
|
"Match": "Correspondre",
|
|
18
18
|
"Monitor ID": "ID du moniteur",
|
|
19
19
|
"Reconnect delay (s)": "Délai(s) de reconnexion",
|
|
20
20
|
"Registration timeout (s)": "Délai(s) d'enregistrement",
|
|
21
|
-
"Rescue-service keyword scheme
|
|
21
|
+
"Rescue-service keyword scheme R<RTW>N<NEF>, optionally followed by a p/f modifier and/or an NT suffix (e.g. \"R1N0\" = 1 ambulance, no emergency physician). Two spellings are recognized: without a space and with a hyphen before NT (Leitstelle Lausitz, e.g. \"R1N1p\", \"R1N0-NT\") and with a space and without a hyphen (Leitstelle Brandenburg/IRLS, e.g. \"R1N1 p\", \"R1N0 nt\") - only enable if your dispatch center actually uses one of these patterns. Takes priority over the table on the Keyword descriptions tab when a keyword matches.": "Schéma de mots-clés des services de secours R<RTW>N<NEF>, éventuellement suivi d'un modificateur p/f et/ou d'un suffixe NT (par ex. \"R1N0\" = 1 ambulance, pas de médecin urgentiste). Deux orthographes sont reconnues : sans espace et avec un tiret avant NT (Leitstelle Lausitz, par ex. \"R1N1p\", \"R1N0-NT\") et avec un espace et sans tiret (Leitstelle Brandebourg/IRLS, par ex. \"R1N1 p\", \"R1N0 nt\") - à activer uniquement si votre centre de répartition utilise effectivement l'un de ces modèles. Prioritaire sur la table de l'onglet Descriptions de mots-clés lorsqu'un mot-clé correspond.",
|
|
22
22
|
"Rescue-service keywords": "Mots-clés du service de secours",
|
|
23
|
-
"Text appended when the keyword ends in \"-NT\".": "Texte ajouté lorsque le mot
|
|
23
|
+
"Text appended when the keyword ends in \"-NT\" or \" nt\".": "Texte ajouté lorsque le mot-clé se termine par \"-NT\" ou \" nt\".",
|
|
24
24
|
"Text appended when the keyword ends in \"f\".": "Texte ajouté lorsque le mot clé se termine par \"f\".",
|
|
25
25
|
"Text appended when the keyword ends in \"p\".": "Texte ajouté lorsque le mot clé se termine par \"p\".",
|
|
26
26
|
"Text used in the generated description for the N<n> part, e.g. \"Notfalleinsatzfahrzeug: 0\".": "Texte utilisé dans la description générée pour la pièce N<n>, par ex. « Notfalleinsatzfahrzeug : 0 ».",
|
package/admin/i18n/it.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"Alarm keyword descriptions": "Descrizioni delle parole chiave degli allarmi",
|
|
3
|
-
"Automatically decode rescue-service keywords (R<RTW>N<NEF>[p][f][-NT])": "Decodifica automaticamente le parole chiave del servizio di soccorso (R<RTW>N<NEF>[p][f][-NT])",
|
|
3
|
+
"Automatically decode rescue-service keywords (R<RTW>N<NEF>[p][f][-NT], with or without spaces)": "Decodifica automaticamente le parole chiave del servizio di soccorso (R<RTW>N<NEF>[p][f][-NT], con o senza spazi)",
|
|
4
4
|
"Base URL of the WAIP dispatch server (Socket.IO endpoint, namespace /waip is appended automatically)": "URL di base del server di invio WAIP (endpoint Socket.IO, lo spazio dei nomi /waip viene aggiunto automaticamente)",
|
|
5
5
|
"Connection": "Connessione",
|
|
6
6
|
"Description": "Descrizione",
|
|
@@ -9,18 +9,18 @@
|
|
|
9
9
|
"Keyword descriptions": "Descrizioni delle parole chiave",
|
|
10
10
|
"Label for N (emergency vehicle count)": "Etichetta per N (numero di veicoli di emergenza)",
|
|
11
11
|
"Label for R (ambulance count)": "Etichetta per R (conteggio ambulanze)",
|
|
12
|
-
"Label for suffix -NT (special ambulance transport)": "Etichetta per il suffisso -NT (trasporto speciale in ambulanza)",
|
|
12
|
+
"Label for suffix -NT / nt (special ambulance transport)": "Etichetta per il suffisso -NT / nt (trasporto speciale in ambulanza)",
|
|
13
13
|
"Label for suffix f (first responder)": "Etichetta per il suffisso f (primo soccorritore)",
|
|
14
14
|
"Label for suffix p (polytrauma)": "Etichetta per il suffisso p (politrauma)",
|
|
15
15
|
"Loaded live from the configured server's /waip/ overview page - choose by Leitstelle, Kreis, Träger or Wache, or pick 'Alle Wachalarme' (ID 0) for every incident. If the server can't be reached, an ID can still be entered manually.": "Caricato in tempo reale dalla pagina di panoramica /waip/ del server configurato: scegli Leitstelle, Kreis, Träger o Wache oppure seleziona \"Alle Wachalarme\" (ID 0) per ogni incidente. Se il server non è raggiungibile, è comunque possibile inserire manualmente un ID.",
|
|
16
|
-
"Maps einsatz.stichwort to einsatz.beschreibung. If several rows match, the most specific (longest) pattern wins automatically - row order has no effect on matching, sort by
|
|
16
|
+
"Maps einsatz.stichwort to einsatz.beschreibung. If several rows match, the most specific (longest) pattern wins automatically - row order has no effect on matching, sort by any column freely. Pre-filled with an example fire/rescue keyword list as a starting point - it is not confirmed to match your own dispatch center's actual keywords, edit/replace as needed. To back up or transfer this table, use ioBroker's standard instance configuration export/import (JSON). After using that import, reload the Admin page before checking this table - the open config dialog doesn't refresh it from an external import automatically (a state-sync limitation of the Admin table component itself).": "Mappa einsatz.stichwort su einsatz.beschreibung. Se più righe corrispondono, il modello più specifico (più lungo) vince automaticamente: l'ordine delle righe non ha alcun effetto sulla corrispondenza, ordinala liberamente per qualsiasi colonna. Precompilato con un esempio di elenco di parole chiave per vigili del fuoco/soccorso come punto di partenza: non è confermato che corrisponda alle parole chiave effettive del tuo centro di spedizione, modifica/sostituisci secondo necessità. Per eseguire il backup o trasferire questa tabella, utilizza l'esportazione/importazione standard della configurazione dell'istanza di ioBroker (JSON). Dopo aver utilizzato quell'importazione standard, ricarica la pagina di amministrazione prima di controllare questa tabella - la finestra di configurazione aperta non la aggiorna automaticamente da un'importazione esterna (una limitazione di sincronizzazione dello stato del componente tabella di amministrazione stesso).",
|
|
17
17
|
"Match": "Incontro",
|
|
18
18
|
"Monitor ID": "Monitorare l'identità",
|
|
19
19
|
"Reconnect delay (s)": "Ritardo/i di riconnessione",
|
|
20
20
|
"Registration timeout (s)": "Timeout registrazione(s)",
|
|
21
|
-
"Rescue-service keyword scheme
|
|
21
|
+
"Rescue-service keyword scheme R<RTW>N<NEF>, optionally followed by a p/f modifier and/or an NT suffix (e.g. \"R1N0\" = 1 ambulance, no emergency physician). Two spellings are recognized: without a space and with a hyphen before NT (Leitstelle Lausitz, e.g. \"R1N1p\", \"R1N0-NT\") and with a space and without a hyphen (Leitstelle Brandenburg/IRLS, e.g. \"R1N1 p\", \"R1N0 nt\") - only enable if your dispatch center actually uses one of these patterns. Takes priority over the table on the Keyword descriptions tab when a keyword matches.": "Schema di parole chiave del servizio di soccorso R<RTW>N<NEF>, opzionalmente seguito da un modificatore p/f e/o un suffisso NT (ad es. \"R1N0\" = 1 ambulanza, nessun medico d'urgenza). Vengono riconosciute due grafie: senza spazio e con trattino prima di NT (Leitstelle Lausitz, ad es. \"R1N1p\", \"R1N0-NT\") e con spazio e senza trattino (Leitstelle Brandeburgo/IRLS, ad es. \"R1N1 p\", \"R1N0 nt\") - attivare solo se la propria centrale operativa utilizza effettivamente uno di questi modelli. Ha la priorità sulla tabella nella scheda Descrizioni delle parole chiave quando una parola chiave corrisponde.",
|
|
22
22
|
"Rescue-service keywords": "Parole chiave del servizio di soccorso",
|
|
23
|
-
"Text appended when the keyword ends in \"-NT\".": "Testo aggiunto quando la parola chiave termina con \"-NT\".",
|
|
23
|
+
"Text appended when the keyword ends in \"-NT\" or \" nt\".": "Testo aggiunto quando la parola chiave termina con \"-NT\" o \" nt\".",
|
|
24
24
|
"Text appended when the keyword ends in \"f\".": "Testo aggiunto quando la parola chiave termina con \"f\".",
|
|
25
25
|
"Text appended when the keyword ends in \"p\".": "Testo aggiunto quando la parola chiave termina con \"p\".",
|
|
26
26
|
"Text used in the generated description for the N<n> part, e.g. \"Notfalleinsatzfahrzeug: 0\".": "Testo utilizzato nella descrizione generata per la parte N<n>, ad es. \"Notfalleinsatzfahrzeug: 0\".",
|
package/admin/i18n/nl.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"Alarm keyword descriptions": "Beschrijvingen van alarmtrefwoorden",
|
|
3
|
-
"Automatically decode rescue-service keywords (R<RTW>N<NEF>[p][f][-NT])": "
|
|
3
|
+
"Automatically decode rescue-service keywords (R<RTW>N<NEF>[p][f][-NT], with or without spaces)": "Trefwoorden van de reddingsdienst automatisch decoderen (R<RTW>N<NEF>[p][f][-NT], met of zonder spaties)",
|
|
4
4
|
"Base URL of the WAIP dispatch server (Socket.IO endpoint, namespace /waip is appended automatically)": "Basis-URL van de WAIP-verzendingsserver (Socket.IO-eindpunt, naamruimte /waip wordt automatisch toegevoegd)",
|
|
5
5
|
"Connection": "Verbinding",
|
|
6
6
|
"Description": "Beschrijving",
|
|
@@ -9,18 +9,18 @@
|
|
|
9
9
|
"Keyword descriptions": "Trefwoordbeschrijvingen",
|
|
10
10
|
"Label for N (emergency vehicle count)": "Label voor N (aantal hulpvoertuigen)",
|
|
11
11
|
"Label for R (ambulance count)": "Label voor R (aantal ambulances)",
|
|
12
|
-
"Label for suffix -NT (special ambulance transport)": "
|
|
12
|
+
"Label for suffix -NT / nt (special ambulance transport)": "Label voor achtervoegsel -NT / nt (speciaal ambulancetransport)",
|
|
13
13
|
"Label for suffix f (first responder)": "Label voor achtervoegsel f (eerstehulpverlener)",
|
|
14
14
|
"Label for suffix p (polytrauma)": "Label voor achtervoegsel p (polytrauma)",
|
|
15
15
|
"Loaded live from the configured server's /waip/ overview page - choose by Leitstelle, Kreis, Träger or Wache, or pick 'Alle Wachalarme' (ID 0) for every incident. If the server can't be reached, an ID can still be entered manually.": "Live geladen vanaf de /waip/ overzichtspagina van de geconfigureerde server - kies voor Leitstelle, Kreis, Träger of Wache, of kies 'Alle Wachalarme' (ID 0) voor elk incident. Als de server niet bereikbaar is, kan er alsnog handmatig een ID worden ingevoerd.",
|
|
16
|
-
"Maps einsatz.stichwort to einsatz.beschreibung. If several rows match, the most specific (longest) pattern wins automatically - row order has no effect on matching, sort by
|
|
16
|
+
"Maps einsatz.stichwort to einsatz.beschreibung. If several rows match, the most specific (longest) pattern wins automatically - row order has no effect on matching, sort by any column freely. Pre-filled with an example fire/rescue keyword list as a starting point - it is not confirmed to match your own dispatch center's actual keywords, edit/replace as needed. To back up or transfer this table, use ioBroker's standard instance configuration export/import (JSON). After using that import, reload the Admin page before checking this table - the open config dialog doesn't refresh it from an external import automatically (a state-sync limitation of the Admin table component itself).": "Kaarten einsatz.stichwort naar einsatz.beschreibung. Als meerdere rijen overeenkomen, wint het meest specifieke (langste) patroon automatisch. De rijvolgorde heeft geen invloed op het matchen, sorteer vrij op elke kolom. Vooraf ingevuld met een voorbeeldlijst met trefwoorden voor brand/redding als uitgangspunt. Er is niet bevestigd dat deze overeenkomt met de daadwerkelijke trefwoorden van uw eigen meldkamer. Bewerk/vervang indien nodig. Gebruik voor het back-uppen of overzetten van deze tabel de standaard export/import van de ioBroker-instantieconfiguratie (JSON). Herlaad na het gebruik van die standaardimport de Admin-pagina voordat u deze tabel controleert - de geopende configuratiedialoog wordt niet automatisch bijgewerkt na een externe import (een status-synchronisatiebeperking van de Admin-tabelcomponent zelf).",
|
|
17
17
|
"Match": "Overeenkomst",
|
|
18
18
|
"Monitor ID": "Monitor-ID",
|
|
19
19
|
"Reconnect delay (s)": "Vertraging(en) opnieuw verbinden",
|
|
20
20
|
"Registration timeout (s)": "Time-out(s) voor registratie",
|
|
21
|
-
"Rescue-service keyword scheme
|
|
21
|
+
"Rescue-service keyword scheme R<RTW>N<NEF>, optionally followed by a p/f modifier and/or an NT suffix (e.g. \"R1N0\" = 1 ambulance, no emergency physician). Two spellings are recognized: without a space and with a hyphen before NT (Leitstelle Lausitz, e.g. \"R1N1p\", \"R1N0-NT\") and with a space and without a hyphen (Leitstelle Brandenburg/IRLS, e.g. \"R1N1 p\", \"R1N0 nt\") - only enable if your dispatch center actually uses one of these patterns. Takes priority over the table on the Keyword descriptions tab when a keyword matches.": "Trefwoordschema van de reddingsdienst R<RTW>N<NEF>, optioneel gevolgd door een p/f-modifier en/of een NT-achtervoegsel (bijv. \"R1N0\" = 1 ambulance, geen spoedarts). Twee schrijfwijzen worden herkend: zonder spatie en met een koppelteken vóór NT (meldkamer Lausitz, bijv. \"R1N1p\", \"R1N0-NT\") en met een spatie en zonder koppelteken (meldkamer Brandenburg/IRLS, bijv. \"R1N1 p\", \"R1N0 nt\") - alleen inschakelen als uw meldkamer daadwerkelijk een van deze patronen gebruikt. Heeft voorrang op de tabel op het tabblad Trefwoordbeschrijvingen wanneer een trefwoord overeenkomt.",
|
|
22
22
|
"Rescue-service keywords": "Reddingsdienst-trefwoorden",
|
|
23
|
-
"Text appended when the keyword ends in \"-NT\".": "Tekst toegevoegd wanneer het trefwoord eindigt op \"-NT\".",
|
|
23
|
+
"Text appended when the keyword ends in \"-NT\" or \" nt\".": "Tekst die wordt toegevoegd wanneer het trefwoord eindigt op \"-NT\" of \" nt\".",
|
|
24
24
|
"Text appended when the keyword ends in \"f\".": "Tekst toegevoegd wanneer het trefwoord eindigt op \"f\".",
|
|
25
25
|
"Text appended when the keyword ends in \"p\".": "Tekst toegevoegd wanneer het trefwoord eindigt op \"p\".",
|
|
26
26
|
"Text used in the generated description for the N<n> part, e.g. \"Notfalleinsatzfahrzeug: 0\".": "Tekst die wordt gebruikt in de gegenereerde beschrijving voor het N<n>-deel, b.v. \"Notfalleinsatzfahrzeug: 0\".",
|
package/admin/i18n/pl.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"Alarm keyword descriptions": "Opisy słów kluczowych alarmów",
|
|
3
|
-
"Automatically decode rescue-service keywords (R<RTW>N<NEF>[p][f][-NT])": "Automatycznie dekoduj słowa kluczowe
|
|
3
|
+
"Automatically decode rescue-service keywords (R<RTW>N<NEF>[p][f][-NT], with or without spaces)": "Automatycznie dekoduj słowa kluczowe pogotowia ratunkowego (R<RTW>N<NEF>[p][f][-NT], ze spacjami lub bez)",
|
|
4
4
|
"Base URL of the WAIP dispatch server (Socket.IO endpoint, namespace /waip is appended automatically)": "Podstawowy adres URL serwera wysyłkowego WAIP (punkt końcowy Socket.IO, przestrzeń nazw /waip jest dodawana automatycznie)",
|
|
5
5
|
"Connection": "Połączenie",
|
|
6
6
|
"Description": "Opis",
|
|
@@ -9,18 +9,18 @@
|
|
|
9
9
|
"Keyword descriptions": "Opisy słów kluczowych",
|
|
10
10
|
"Label for N (emergency vehicle count)": "Etykieta N (liczba pojazdów uprzywilejowanych)",
|
|
11
11
|
"Label for R (ambulance count)": "Etykieta dla R (liczba ambulansów)",
|
|
12
|
-
"Label for suffix -NT (special ambulance transport)": "Etykieta
|
|
12
|
+
"Label for suffix -NT / nt (special ambulance transport)": "Etykieta dla przyrostka -NT / nt (specjalny transport karetką)",
|
|
13
13
|
"Label for suffix f (first responder)": "Etykieta przyrostka f (pierwsza pomoc)",
|
|
14
14
|
"Label for suffix p (polytrauma)": "Etykieta przyrostka p (uraz wielonarządowy)",
|
|
15
15
|
"Loaded live from the configured server's /waip/ overview page - choose by Leitstelle, Kreis, Träger or Wache, or pick 'Alle Wachalarme' (ID 0) for every incident. If the server can't be reached, an ID can still be entered manually.": "Ładowane na żywo ze strony przeglądu /waip/ skonfigurowanego serwera - wybierz Leitstelle, Kreis, Träger lub Wache lub wybierz „Alle Wachalarme” (ID 0) dla każdego zdarzenia. Jeśli serwer jest nieosiągalny, identyfikator można wprowadzić ręcznie.",
|
|
16
|
-
"Maps einsatz.stichwort to einsatz.beschreibung. If several rows match, the most specific (longest) pattern wins automatically - row order has no effect on matching, sort by
|
|
16
|
+
"Maps einsatz.stichwort to einsatz.beschreibung. If several rows match, the most specific (longest) pattern wins automatically - row order has no effect on matching, sort by any column freely. Pre-filled with an example fire/rescue keyword list as a starting point - it is not confirmed to match your own dispatch center's actual keywords, edit/replace as needed. To back up or transfer this table, use ioBroker's standard instance configuration export/import (JSON). After using that import, reload the Admin page before checking this table - the open config dialog doesn't refresh it from an external import automatically (a state-sync limitation of the Admin table component itself).": "Mapuje einsatz.stichwort na einsatz.beschreibung. Jeśli pasuje kilka wierszy, automatycznie wygrywa najbardziej konkretny (najdłuższy) wzór - kolejność wierszy nie ma wpływu na dopasowanie, sortuj dowolnie według dowolnej kolumny. Wstępnie wypełniona przykładową listą słów kluczowych dotyczących straży pożarnej/ratownictwa jako punkt wyjścia — nie potwierdzono, że jest zgodna z rzeczywistymi słowami kluczowymi Twojego centrum dyspozytorskiego, edytuj/zamień w razie potrzeby. Aby wykonać kopię zapasową lub przenieść tę tabelę, użyj standardowego eksportu/importu konfiguracji instancji ioBroker (JSON). Po użyciu tego standardowego importu odśwież stronę administracyjną przed sprawdzeniem tej tabeli - otwarte okno konfiguracji nie odświeża się automatycznie po zewnętrznym imporcie (ograniczenie synchronizacji stanu samego komponentu tabeli administracyjnej).",
|
|
17
17
|
"Match": "Mecz",
|
|
18
18
|
"Monitor ID": "Identyfikator monitora",
|
|
19
19
|
"Reconnect delay (s)": "Opóźnienie ponownego podłączenia",
|
|
20
20
|
"Registration timeout (s)": "Limit czasu rejestracji (s)",
|
|
21
|
-
"Rescue-service keyword scheme
|
|
21
|
+
"Rescue-service keyword scheme R<RTW>N<NEF>, optionally followed by a p/f modifier and/or an NT suffix (e.g. \"R1N0\" = 1 ambulance, no emergency physician). Two spellings are recognized: without a space and with a hyphen before NT (Leitstelle Lausitz, e.g. \"R1N1p\", \"R1N0-NT\") and with a space and without a hyphen (Leitstelle Brandenburg/IRLS, e.g. \"R1N1 p\", \"R1N0 nt\") - only enable if your dispatch center actually uses one of these patterns. Takes priority over the table on the Keyword descriptions tab when a keyword matches.": "Schemat słów kluczowych pogotowia ratunkowego R<RTW>N<NEF>, opcjonalnie po którym następuje modyfikator p/f i/lub sufiks NT (np. \"R1N0\" = 1 karetka, brak lekarza ratunkowego). Rozpoznawane są dwa zapisy: bez spacji i z myślnikiem przed NT (centrala Lausitz, np. \"R1N1p\", \"R1N0-NT\") oraz ze spacją i bez myślnika (centrala Brandenburgia/IRLS, np. \"R1N1 p\", \"R1N0 nt\") - włączaj tylko wtedy, gdy twoja centrala dyspozytorska rzeczywiście używa jednego z tych wzorców. Ma pierwszeństwo przed tabelą na karcie Opisy słów kluczowych, gdy słowo kluczowe pasuje.",
|
|
22
22
|
"Rescue-service keywords": "Słowa kluczowe pogotowia ratunkowego",
|
|
23
|
-
"Text appended when the keyword ends in \"-NT\".": "Tekst
|
|
23
|
+
"Text appended when the keyword ends in \"-NT\" or \" nt\".": "Tekst dodawany, gdy słowo kluczowe kończy się na \"-NT\" lub \" nt\".",
|
|
24
24
|
"Text appended when the keyword ends in \"f\".": "Tekst dołączany, gdy słowo kluczowe kończy się na „f”.",
|
|
25
25
|
"Text appended when the keyword ends in \"p\".": "Tekst dołączany, gdy słowo kluczowe kończy się na „p”.",
|
|
26
26
|
"Text used in the generated description for the N<n> part, e.g. \"Notfalleinsatzfahrzeug: 0\".": "Tekst użyty w wygenerowanym opisie dla części N<n>, np. „Notfalleinsatzfahrzeug: 0”.",
|
package/admin/i18n/pt.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"Alarm keyword descriptions": "Descrições de palavras-chave de alarme",
|
|
3
|
-
"Automatically decode rescue-service keywords (R<RTW>N<NEF>[p][f][-NT])": "Decodificar automaticamente palavras-chave do serviço de resgate (R<RTW>N<NEF>[p][f][-NT])",
|
|
3
|
+
"Automatically decode rescue-service keywords (R<RTW>N<NEF>[p][f][-NT], with or without spaces)": "Decodificar automaticamente as palavras-chave do serviço de resgate (R<RTW>N<NEF>[p][f][-NT], com ou sem espaços)",
|
|
4
4
|
"Base URL of the WAIP dispatch server (Socket.IO endpoint, namespace /waip is appended automatically)": "URL base do servidor de despacho WAIP (endpoint Socket.IO, namespace /waip é anexado automaticamente)",
|
|
5
5
|
"Connection": "Conexão",
|
|
6
6
|
"Description": "Descrição",
|
|
@@ -9,18 +9,18 @@
|
|
|
9
9
|
"Keyword descriptions": "Descrições de palavras-chave",
|
|
10
10
|
"Label for N (emergency vehicle count)": "Etiqueta para N (contagem de veículos de emergência)",
|
|
11
11
|
"Label for R (ambulance count)": "Etiqueta para R (contagem de ambulâncias)",
|
|
12
|
-
"Label for suffix -NT (special ambulance transport)": "
|
|
12
|
+
"Label for suffix -NT / nt (special ambulance transport)": "Rótulo para o sufixo -NT / nt (transporte especial de ambulância)",
|
|
13
13
|
"Label for suffix f (first responder)": "Rótulo para sufixo f (socorrista)",
|
|
14
14
|
"Label for suffix p (polytrauma)": "Etiqueta para sufixo p (politrauma)",
|
|
15
15
|
"Loaded live from the configured server's /waip/ overview page - choose by Leitstelle, Kreis, Träger or Wache, or pick 'Alle Wachalarme' (ID 0) for every incident. If the server can't be reached, an ID can still be entered manually.": "Carregado ao vivo da página /waip/viewview do servidor configurado - escolha por Leitstelle, Kreis, Träger ou Wache, ou escolha 'Alle Wachalarme' (ID 0) para cada incidente. Se o servidor não puder ser acessado, um ID ainda poderá ser inserido manualmente.",
|
|
16
|
-
"Maps einsatz.stichwort to einsatz.beschreibung. If several rows match, the most specific (longest) pattern wins automatically - row order has no effect on matching, sort by
|
|
16
|
+
"Maps einsatz.stichwort to einsatz.beschreibung. If several rows match, the most specific (longest) pattern wins automatically - row order has no effect on matching, sort by any column freely. Pre-filled with an example fire/rescue keyword list as a starting point - it is not confirmed to match your own dispatch center's actual keywords, edit/replace as needed. To back up or transfer this table, use ioBroker's standard instance configuration export/import (JSON). After using that import, reload the Admin page before checking this table - the open config dialog doesn't refresh it from an external import automatically (a state-sync limitation of the Admin table component itself).": "Mapeia einsatz.stichwort para einsatz.beschreibung. Se várias linhas corresponderem, o padrão mais específico (mais longo) vencerá automaticamente - a ordem das linhas não tem efeito na correspondência, classifique livremente por qualquer coluna. Pré-preenchido com um exemplo de lista de palavras-chave de incêndio/resgate como ponto de partida - não está confirmado que corresponda às palavras-chave reais do seu próprio centro de despacho, edite/substitua conforme necessário. Para fazer backup ou transferir esta tabela, use a exportação/importação padrão da configuração da instância do ioBroker (JSON). Depois de usar essa importação padrão, recarregue a página de administração antes de verificar esta tabela - a caixa de diálogo de configuração aberta não a atualiza automaticamente a partir de uma importação externa (uma limitação de sincronização de estado do próprio componente de tabela de administração).",
|
|
17
17
|
"Match": "Corresponder",
|
|
18
18
|
"Monitor ID": "ID do monitor",
|
|
19
19
|
"Reconnect delay (s)": "Atraso(s) de reconexão",
|
|
20
20
|
"Registration timeout (s)": "Tempo limite de registro(s)",
|
|
21
|
-
"Rescue-service keyword scheme
|
|
21
|
+
"Rescue-service keyword scheme R<RTW>N<NEF>, optionally followed by a p/f modifier and/or an NT suffix (e.g. \"R1N0\" = 1 ambulance, no emergency physician). Two spellings are recognized: without a space and with a hyphen before NT (Leitstelle Lausitz, e.g. \"R1N1p\", \"R1N0-NT\") and with a space and without a hyphen (Leitstelle Brandenburg/IRLS, e.g. \"R1N1 p\", \"R1N0 nt\") - only enable if your dispatch center actually uses one of these patterns. Takes priority over the table on the Keyword descriptions tab when a keyword matches.": "Esquema de palavras-chave do serviço de resgate R<RTW>N<NEF>, opcionalmente seguido por um modificador p/f e/ou um sufixo NT (por exemplo, \"R1N0\" = 1 ambulância, sem médico de emergência). Duas grafias são reconhecidas: sem espaço e com hífen antes de NT (central de Lausitz, por exemplo, \"R1N1p\", \"R1N0-NT\") e com espaço e sem hífen (central de Brandemburgo/IRLS, por exemplo, \"R1N1 p\", \"R1N0 nt\") - ative apenas se a sua central de despacho realmente usar um desses padrões. Tem prioridade sobre a tabela na aba Descrições de palavras-chave quando uma palavra-chave corresponde.",
|
|
22
22
|
"Rescue-service keywords": "Palavras-chave do serviço de resgate",
|
|
23
|
-
"Text appended when the keyword ends in \"-NT\".": "Texto
|
|
23
|
+
"Text appended when the keyword ends in \"-NT\" or \" nt\".": "Texto adicionado quando a palavra-chave termina em \"-NT\" ou \" nt\".",
|
|
24
24
|
"Text appended when the keyword ends in \"f\".": "Texto acrescentado quando a palavra-chave termina em \"f\".",
|
|
25
25
|
"Text appended when the keyword ends in \"p\".": "Texto acrescentado quando a palavra-chave termina em “p”.",
|
|
26
26
|
"Text used in the generated description for the N<n> part, e.g. \"Notfalleinsatzfahrzeug: 0\".": "Texto usado na descrição gerada para a parte N<n>, por exemplo. \"Notfalleinsatzfahrzeug: 0\".",
|