Units
Translation components API.
See the Weblate's Web API documentation for detailed description of the API.
GET /api/translations/yast-cluster/master/ca/units/?format=api&page=8
{ "count": 147, "next": null, "previous": "https://l10n.opensuse.org/api/translations/yast-cluster/master/ca/units/?format=api&page=7", "results": [ { "translation": "https://l10n.opensuse.org/api/translations/yast-cluster/master/ca/?format=api", "source": [ "<p><b><big>Model</big></b><br>Specifies the model to be used. This parameter is required. corosync-qdevice is modular and is able to support multiple different models. The model basically defines what type of arbitrator is used. Currently only 'net' is supported.</p>\n<p><b><big>Host</big></b><br>Specifies the IP address or host name of the qnetd server to be used. This parameter is required.</p>\n<p><b><big>Port</big></b><br>Specifies TCP port of qnetd server. Default is 5403.</p>\n<p><b><big>TLS</big></b><br>Can be one of 'on', 'off' or 'required' and specifies if tls should be used. 'on' means a connection with TLS is attempted first, but if the server doesn't advertise TLS support then non-TLS will be used. 'off' is used then TLS is not required and it's then not even tried. This mode is the only one which doesn't need a properly initialized NSS database. 'required' means TLS is required and if the server doesn't support TLS, qdevice will exit with error message. 'on' need manually change, refer to corosync-qdevice's man page for more details. Default is 'off' in yast.</p>\n<p><b><big>Algorithm</big></b><br>Decision algorithm. Can be one of the 'ffsplit' or 'lms'. (Actually there are also 'test' and '2nodelms', both of which are mainly for developers and shouldn't be used for production clusters, so yast will convert to 'ffsplit' automatically). For a description of what each algorithm means and how the algorithms differ see their individual sections. Default value is ffsplit.</p>\n<p><b><big>Tie breaker</big></b><br>Can be one of 'lowest', 'highest' or 'valid_node_id' (number) values. It's used as a fallback if qdevice has to decide between two or more equal partitions. 'lowest' means the partition with the lowest node id is chosen. 'highest' means the partition with highest node id is chosen. And 'valid_node_id' means that the partition containing the node with the given node id is chosen. Default is 'lowest'.</p>\n<p><b><big>Qdevice Heuristics</big></b><br>Subsection of Qdevice. Heuristics are set of commands executed locally on startup, cluster membership change, successful connect to corosync-qnetd and optionally also at regular times. Commands are executed in parallel. When *all* commands finish successfully (their return error code is zero) on time, heuristics have passed, otherwise they have failed. The heuristics result is sent to corosync-qnetd and there it's used in calculations to determine which partition should be quorate.</p>\n<p><b><big>Heuristics Mode</big></b><br>Can be one of on, sync or off and specifies mode of operation of heuristics. Default is off, which means heuristics are disabled. When sync is set, heuristics are executed only during startup, membership change and when connection to corosync-qnetd is established. When heuristics should be running also on regular basis, this option should be set to on value.</p>\n<p><b><big>Heuristics Timeout</big></b><br>Specifies maximum time in milliseconds. How long corosync-qdevice waits till the heuristics commands finish. If some command doesn't finish before the timeout, it's killed and heuristics fail. This timeout is used for heuristics executed at regular times. Default value is half of the quorum.device.timeout, so 5000.</p>\n<p><b><big>Heuristics Sync_timeout</big></b><br>Similar to quorum.device.heuristics.timeout but used during membership changes. Default value is half of the quorum.device.sync_timeout, so 15000.</p>\n<p><b><big>Heuristics Interval</big></b><br>Specifies interval between two regular heuristics execution. Default value is 3 * quorum.device.timeout, so 30000.</p>\n<p><b><big>Heuristics exec_NAME</big></b><br>Defines executables. *NAME* can be arbitrary valid cmap key name string and it has no special meaning. The value of this variable must contain a command to execute. The value is parsed (split) into arguments similarly as Bourne shell would do. Quoting is possible by using backslash and double quotes. <br>For example, Name(exec_check_master), Value(/etc/corosync/qdevice/check_master.sh)</p>\n" ], "previous_source": "", "target": [ "<p><b><big>Model</big></b><br>Especifica el model per usar. Aquest paràmetre és necessari. El corosync-qdevice és modular i admet múltiples models diferents. El model bàsicament defineix quin tipus d'àrbitre s'usa. Ara només s'admet \"net\".</p>\n<p><b><big>Amfitrió</big></b><br>Especifica l'adreça IP o el nom d'amfitrió del servidor qnetd per usar. Aquest paràmetre és necessari.</p>\n<p><b><big>Port</big></b><br>Especifica el port TCP del servidor qnetd. Per defecte és 5403.</p>\n<p><b><big>TLS</big></b><br>Pot ser \"on\", \"off\" o \"required\" (requerit, necessari) i especifica si s'ha d'usar TLS. \"On\" significa que primer s'intenta una connexió amb TLS, però si el servidor no indica que admeti TLS es farà servir no TLS. \"Off' s'usa quan TLS no és necessari i llavors ni tan sols s'intenta usar. Aquest mode és l'únic que no necessita una base de dades NSS adequadament iniciada. \"Required\" significa que TLS és necessari i que, si el servidor no admet TLS, qdevice sortirà amb un missatge d'error. \"On\" necessita un canvi manual, vegeu la pàgina del manual de corosync-qdevice per a més detalls. Per defecte és \"off\" al Yast.</p>\n<p><b><big>Algorisme</big></b><br>Algorisme de decisió. Pot ser \"ffsplit\" o \"lms\". (Actualment també hi ha \"test\" i \"2nodelms\", però aquets dos són principalment per a desenvolupadors i no s'haurien d'usar en clústers de producció; per tant, el Yast passarà a \"ffsplit\" automàticament). Per a la descripció del que significa cada algorisme i quina diferència tenen vegeu-ne les seccions individuals. El valor per defecte és \"ffsplit\".</p>\n<p><b><big>Desempat</big></b><br>(Tie breaker) Pot ser \"lowest\" (el més baix), \"highest\" (el més elevat) o \"valid_node_id\" (número). S'usa com a alternativa si qdevice ha de decidir entre dues o més particions iguals. \"El més baix\" significa que es tria la partició amb l'identificador de node més baix. \"El més elevat\" significa que es tria la partició amb l'identificador de node més alt. I \"valid_node_id\" significa que es tria la partició que contingui el node amb l'identificador de node proporcionat. Per defecte és el més baix.</p>\n<p><b><big>Heurística de Qdevice</big></b><br>Subsecció de Qdevice. L'heurística és un conjunt d'ordres executades localment durant l'arrencada, el canvi de pertinença de clúster, la connexió correcta a corosync-qnetd i opcionalment també en moments regulars. Les ordres s'executen en paral·lel. Quan *totes* les ordres acaben correctament (retornen un codi d'error que és zero) a temps, l'heurística ha passat, si no, han fallat. El resultat de l'heurística s'envia a corosync-qnetd i allà s'usa en càlculs per determinar quina partició hauria de ser de quòrum.</p>\n<p><b><big>Mode de l'heurística</big></b><br>Pot ser activat, sincronització o desactivat i n'especifica el mode d'operació. Per defecte és desactivat, que significa que l'heurística està inhabilitada. Quan s'estableix la sincronització, l'heurística només s'executa durant l'arrencada, el canvi de pertinença i quan s'estableix la connexió amb corosync-qnetd. Quan l'heurística hagi d'executar-se regularment, aquesta opció hauria d'establir-se al valor d'activat.</p>\n<p><b><big>Temps d'espera de l'heurística</big></b><br>N'especifica el temps mínim en mil·lisegons, quant espera corosync-qdevice fins que les ordres de l'heurística acabin. Si alguna ordre no acaba abans del temps d'espera, es mata i l'heurística falla. Aquest temps d'espera s'usa per a l'heurística executada en moments regulars. El valor per defecte és la meitat del que indica quorum.device.timeout, per tant, 5000.</p>\n<p><b><big>Temps d'espera de la sincronització de l'heurística</big></b><br>Similar a quorum.device.heuristics.timeout però usat durant els canvis de pertinença. El valor per defecte és la meitat del que indica quorum.device.sync_timeout, per tant, 15000.</p>\n<p><b><big>Interval de l'heurística</big></b><br>Especifica l'interval entre dues execucions regulars de l'heurística. El valor per defecte és 3 * quorum.device.timeout, per tant, 30000.</p>\n<p><b><big>Nom d'execució de l'heurística</big></b><br>Defineix executables. El *NOM* pot ser la cadena de nom de clau de cmap vàlida arbitrària i no té significat especial. El valor d'aquesta variable ha de contenir una ordre per executar. El valor és analitzat (dividit) en arguments similarment com ho faria l'intèrpret d'ordres Bourne. La citació és possible usant la barra obliqua inversa i cometes dobles. <br>Per exemple: Name(exec_check_master), Value(/etc/corosync/qdevice/check_master.sh)</p>\n" ], "id_hash": -7026888997277326667, "content_hash": -7026888997277326667, "location": "src/include/cluster/helps.rb:47", "context": "", "note": "", "flags": "", "state": 20, "fuzzy": false, "translated": true, "approved": false, "position": 118, "has_suggestion": false, "has_comment": false, "has_failing_check": false, "num_words": 556, "source_unit": "https://l10n.opensuse.org/api/units/12678798/?format=api", "priority": 100, "id": 11445772, "web_url": "https://l10n.opensuse.org/translate/yast-cluster/master/ca/?checksum=1e7b79afe12f22b5", "url": "https://l10n.opensuse.org/api/units/11445772/?format=api", "explanation": "", "extra_flags": "" }, { "translation": "https://l10n.opensuse.org/api/translations/yast-cluster/master/ca/?format=api", "source": [ "Crypto Hash:" ], "previous_source": "", "target": [ "Resum criptogràfic:" ], "id_hash": -3169754400151625420, "content_hash": -3169754400151625420, "location": "src/include/cluster/dialogs.rb:1114", "context": "", "note": "", "flags": "", "state": 20, "fuzzy": false, "translated": true, "approved": false, "position": 73, "has_suggestion": false, "has_comment": false, "has_failing_check": false, "num_words": 2, "source_unit": "https://l10n.opensuse.org/api/units/12593345/?format=api", "priority": 100, "id": 12022499, "web_url": "https://l10n.opensuse.org/translate/yast-cluster/master/ca/?checksum=5402c52ac9bb2134", "url": "https://l10n.opensuse.org/api/units/12022499/?format=api", "explanation": "", "extra_flags": "" }, { "translation": "https://l10n.opensuse.org/api/translations/yast-cluster/master/ca/?format=api", "source": [ "Crypto Cipher:" ], "previous_source": "", "target": [ "Xifratge criptogràfic:" ], "id_hash": -277941717471186054, "content_hash": -277941717471186054, "location": "src/include/cluster/dialogs.rb:1119", "context": "", "note": "", "flags": "", "state": 20, "fuzzy": false, "translated": true, "approved": false, "position": 74, "has_suggestion": false, "has_comment": false, "has_failing_check": false, "num_words": 2, "source_unit": "https://l10n.opensuse.org/api/units/12593352/?format=api", "priority": 100, "id": 12022500, "web_url": "https://l10n.opensuse.org/translate/yast-cluster/master/ca/?checksum=7c248d7b05de337a", "url": "https://l10n.opensuse.org/api/units/12022500/?format=api", "explanation": "", "extra_flags": "" }, { "translation": "https://l10n.opensuse.org/api/translations/yast-cluster/master/ca/?format=api", "source": [ "The Member Address has to be fulfilled" ], "previous_source": "", "target": [ "S'ha de proporcionar l'adreça del membre." ], "id_hash": 3150308139115623838, "content_hash": 3150308139115623838, "location": "src/include/cluster/dialogs.rb:224", "context": "", "note": "", "flags": "", "state": 20, "fuzzy": false, "translated": true, "approved": false, "position": 19, "has_suggestion": false, "has_comment": false, "has_failing_check": false, "num_words": 7, "source_unit": "https://l10n.opensuse.org/api/units/12682250/?format=api", "priority": 100, "id": 12028248, "web_url": "https://l10n.opensuse.org/translate/yast-cluster/master/ca/?checksum=abb8248fbd02359e", "url": "https://l10n.opensuse.org/api/units/12028248/?format=api", "explanation": "", "extra_flags": "" }, { "translation": "https://l10n.opensuse.org/api/translations/yast-cluster/master/ca/?format=api", "source": [ "The Expected Votes has to be fulfilled when multicast transport is configured" ], "previous_source": "", "target": [ "Els vots esperats s'han satisfer quan hi ha configurat el transport de multidifusió." ], "id_hash": -4595801077360999264, "content_hash": -4595801077360999264, "location": "src/include/cluster/dialogs.rb:230", "context": "", "note": "BNC#880242, expected_votes must have value when \"udp\"", "flags": "", "state": 20, "fuzzy": false, "translated": true, "approved": false, "position": 20, "has_suggestion": false, "has_comment": false, "has_failing_check": false, "num_words": 12, "source_unit": "https://l10n.opensuse.org/api/units/12683675/?format=api", "priority": 100, "id": 12028249, "web_url": "https://l10n.opensuse.org/translate/yast-cluster/master/ca/?checksum=40386f450d8a44a0", "url": "https://l10n.opensuse.org/api/units/12028249/?format=api", "explanation": "", "extra_flags": "" }, { "translation": "https://l10n.opensuse.org/api/translations/yast-cluster/master/ca/?format=api", "source": [ "Need to press \"Generate Auth Key File\"" ], "previous_source": "", "target": [ "Cal prémer \"Genera un fitxer de clau d'autenticació\"" ], "id_hash": 5626607367904250576, "content_hash": 5626607367904250576, "location": "src/include/cluster/dialogs.rb:753", "context": "", "note": "Notice, current could be \"nil\" if the list is empty.", "flags": "", "state": 20, "fuzzy": false, "translated": true, "approved": false, "position": 46, "has_suggestion": false, "has_comment": false, "has_failing_check": false, "num_words": 7, "source_unit": "https://l10n.opensuse.org/api/units/14119359/?format=api", "priority": 100, "id": 14119368, "web_url": "https://l10n.opensuse.org/translate/yast-cluster/master/ca/?checksum=ce15b9970e874ad0", "url": "https://l10n.opensuse.org/api/units/14119368/?format=api", "explanation": "", "extra_flags": "" }, { "translation": "https://l10n.opensuse.org/api/translations/yast-cluster/master/ca/?format=api", "source": [ "<p><b><big>IP Version</big></b><br>Specifies version of IP to use for communication. Value can be one of ipv4 or ipv6. Default (if unspecified) is ipv4.<br></p>\n<p><b><big>Bind Network Address</big></b><br>This specifies the address which the corosync executive should bind. This address should always end in zero. If the totem traffic should be routed over 192.168.5.92, set bindnetaddr to 192.168.5.0.<br>This may also be an IPV6 address, in which case IPV6 networking will be used. In this case, the full address must be specified and there is no automatic selection of the network interface within a specific subnet as with IPv4. If IPv6 networking is used, the nodeid field must be specified.<br></p>\n<p><b><big>Multicast Address</big></b><br>This is the multicast address used by corosync executive. The default should work for most networks, but the network administrator should be queried about a multicast address to use. Avoid 224.x.x.x because this is a \"config\" multicast address.<br>This may also be an IPV6 multicast address, in which case IPV6 networking will be used. If IPv6 networking is used, the nodeid field must be specified.</p>\n<p><b><big>Port</big></b><br>This specifies the UDP port number. It is possible to use the same multicast address on a network with the corosync services configured for different UDP ports.<br></p>\n<p><b><big>Member Address</big></b><br>This list specifies all the nodes in the cluster by IP address. This could be configurable when using udpu(Unicast). <br></p>\n<p><b><big>Node ID</big></b><br>This configuration option is optional when using IPv4 and required when using IPv6. This is a 32 bit value specifying the node identifier delivered to the cluster membership service. If this is not specified with IPv4, the node id will be determined from the 32 bit IP address the system to which the system is bound with ring identifier of 0. The node identifier value of zero is reserved and should not be used.<br></p>\n<p><b><big>rrp_mode</big></b><br>This specifies the mode of redundant ring, which may be none, active, or passive. Active replication offers slightly lower latency from transmit to delivery in faulty network environments but with less performance. Passive replication may nearly double the speed of the totem protocol if the protocol doesn't become cpu bound. The final option is none, in which case only one network interface will be used to operate the totem protocol. If only one interface directive is specified, none is automatically chosen. If multiple interface directives are specified, only active or passive may be chosen.<br></p>\n<p><b><big>Cluster Name</big></b><br>This specifies the name of cluster and it's used for automatic generating of multicast address. Default is hacluster. For a geo cluster, each cluster must have a unique name.<br></p>\n<p><b><big>Expected votes</big></b><br>Expect vote number for voting quorum. Will be automatically calculated when the nodelist {} section is present in corosync.conf (the list will be generated when using unicast transport) or can be specified in the quorum {} section (Expect votes should use the total node numble of the cluster). If Expected votes presents in unicast transport, the value will override the one automatically calculated. For safety, the Expected votes will be disabled once nodelist not empty, it's good for ignore the inappropriate Expected votes set.<br></p>\n<p><b><big>Auto Generate Node ID</big></b><br>Nodeid is required when using IPv6. Auto node ID enabled will generate nodeid automatically.<br></p>\n" ], "previous_source": "<p><b><big>IP Version</big></b><br>Specifies version of IP to use for communication. Value can be one of ipv4 or ipv6. Default (if unspecified) is ipv4.<br></p>\n<p><b><big>Bind Network Address</big></b><br>This specifies the address which the openais executive should bind. This address should always end in zero. If the totem traffic should be routed over 192.168.5.92, set bindnetaddr to 192.168.5.0.<br>This may also be an IPV6 address, in which case IPV6 networking will be used. In this case, the full address must be specified and there is no automatic selection of the network interface within a specific subnet as with IPv4. If IPv6 networking is used, the nodeid field must be specified.<br></p>\n<p><b><big>Multicast Address</big></b><br>This is the multicast address used by openais executive. The default should work for most networks, but the network administrator should be queried about a multicast address to use. Avoid 224.x.x.x because this is a \"config\" multicast address.<br>This may also be an IPV6 multicast address, in which case IPV6 networking will be used. If IPv6 networking is used, the nodeid field must be specified.</p>\n<p><b><big>Port</big></b><br>This specifies the UDP port number. It is possible to use the same multicast address on a network with the openais services configured for different UDP ports.<br></p>\n<p><b><big>Member Address</big></b><br>This list specifies all the nodes in the cluster by IP address. This could be configurable when using udpu(Unicast). <br></p>\n<p><b><big>Node ID</big></b><br>This configuration option is optional when using IPv4 and required when using IPv6. This is a 32 bit value specifying the node identifier delivered to the cluster membership service. If this is not specified with IPv4, the node id will be determined from the 32 bit IP address the system to which the system is bound with ring identifier of 0. The node identifier value of zero is reserved and should not be used.<br></p>\n<p><b><big>rrp_mode</big></b><br>This specifies the mode of redundant ring, which may be none, active, or passive. Active replication offers slightly lower latency from transmit to delivery in faulty network environments but with less performance. Passive replication may nearly double the speed of the totem protocol if the protocol doesn't become cpu bound. The final option is none, in which case only one network interface will be used to operate the totem protocol. If only one interface directive is specified, none is automatically chosen. If multiple interface directives are specified, only active or passive may be chosen.<br></p>\n<p><b><big>Cluster Name</big></b><br>This specifies the name of cluster and it's used for automatic generating of multicast address. Default is hacluster. For a geo cluster, each cluster must have a unique name.<br></p>\n<p><b><big>Expected votes</big></b><br>Expect vote number for voting quorum. Will be automatically calculated when the nodelist {} section is present in corosync.conf (the list will be generated when using unicast transport) or can be specified in the quorum {} section (Expect votes should use the total node numble of the cluster). If Expected votes presents in unicast transport, the value will override the one automatically calculated. For safety, the Expected votes will be disabled once nodelist not empty, it's good for ignore the inappropriate Expected votes set.<br></p>\n<p><b><big>Auto Generate Node ID</big></b><br>Nodeid is required when using IPv6. Auto node ID enabled will generate nodeid automatically.<br></p>\n", "target": [ "<p><b><big>Versió d'IP</big></b><br>Especifica la versió d'IP a usar per a la comunicació. El valor pot ser d'ipv4 o ipv6. Per defecte (si no s'especifica) és ipv4.<br></p>\n<p><b><big>Adreça de vinculació de xarxa</big></b><br>Això especifica l'adreça a la qual la directiva corosync s'hauria de vincular. Aquesta adreça hauria d'acabar sempre amb zero. Si el trànsit tòtem s'hauria d'encaminar per 192.168.5.92, establiu bindnetaddr a 192.168.5.0.<br>Això també pot ser una adreça IPV6, en aquest cas s'usarà el treball en xarxa IPV6. En aquest cas, cal especificar l'adreça completa i no hi ha selecció automàtica d'interfície de xarxa dins d'una subxarxa específica com amb IPv4. Si s'usa treball en xarxa IPv6, el camp ID de node s'ha d'especificar.<br></p>\n<p><b><big>Adreça de multidifusió</big></b><br>Aquesta és l'adreça de multidifusió usada per la directiva corosync. La configuració per defecte hauria de funcionar a la majoria de xarxes, però l'administrador de xarxes hauria de ser consultat sobre quina adreça de multidifusió fer servir. Eviteu 224.x.x.x perquè és una adreça de multidifusió de \"config\".<br>Això també pot ser una adreça de multidifusió IPV6, cas en què s'usarà el treball de xarxa IPV6. Si s'usa IPv6 networking, cal especificar el camp ID de node.</p>\n<p><b><big>Port</big></b><br>Això especifica el número de port UDP. És possible usar la mateixa adreça de multidifusió en una xarxa amb els serveis corosync configurats per a diferents ports UDP.<br></p>\n<p><b><big>Adreça membre</big></b><br>Aquesta llista especifica tots els nodes del clúster per l'adreça IP. Això podria ser configurable quan s'usa udpu(Unicast). <br></p>\n<p><b><big>ID de node</big></b><br>Aquesta opció de configuració és opcional quan s'usa IPv4 i necessària quan s'usa IPv6. Això és un valor de 32 bits que especifica l'identificador de node lliurat al servei de pertinença del clúster. Si no s'especifica amb IPv4, l'id del node es determinarà des de l'adreça IP de 32 bits del sistema al qual el sistema està lligat amb un identificador d'anell de 0. El valor d'identificador de node de zero està reservat i no s'hauria d'usar.<br></p>\n<p><b><big>rrp_mode</big></b><br>Això especifica el mode d'anell redundant, que pot ser cap, actiu o passiu. La replicació activa ofereix una latència una mica més baixa des de la transmissió fins al lliurament en entorns de xarxes defectuosos però amb menys rendiment. La replicació passiva pot arribar a doblar la velocitat del protocol tòtem si el protocol no esdevé lligat a la cpu. L'opció final és cap, en què només s'usarà una interfície de xarxa per operar el protocol tòtem. Si només s'especifica una directiva d'interfície, es tria automàticalment \"cap\". Si se n'especifiquen múltiples, només es pot triar entre actiu o passiu.<br></p>\n<p><b><big>Nom del clúster</big></b><br>Especifica el nom del clúster i s'usa per a la generació automàtica d'adreces de multidifusió. Per defecte és \"hacluster\". Per a un geoclúster, cada clúster ha de tenir un nom únic.<br></p>\n<p><b><big>Vots esperats</big></b><br>Nombre de vots esperats per tenir quòrum. Es calcularà automàticalment quan la secció nodelist {} sigui present a corosync.conf (la llista es generarà quan s'usi transport unicast) o es pot especificar a la secció quorum {} (L'\"expect votes\" hauria d'usar el nombre total de nodes del clúster). Si els vots esperats són presents al transport unicast, el valor passarà per alt del que s'ha calculat automàticament. Per seguretat, els vots esperats s'inhabilitaran un cop la llista de nodes no sigui buida; és bo per ignorar el conjunt de vots esperats no apropiats.<br></p>\n<p><b><big>Autogenera ID de node</big></b><br>L'id de node és necessari quan s'usa IPv6. L'habilitació d'ID de node automàtic generarà un \"nodeid\" automàticament.<br></p>\n" ], "id_hash": 3081110394975739161, "content_hash": 3081110394975739161, "location": "src/include/cluster/helps.rb:35", "context": "", "note": "All helps are here", "flags": "", "state": 20, "fuzzy": false, "translated": true, "approved": false, "position": 117, "has_suggestion": false, "has_comment": false, "has_failing_check": false, "num_words": 519, "source_unit": "https://l10n.opensuse.org/api/units/14448657/?format=api", "priority": 100, "id": 14448666, "web_url": "https://l10n.opensuse.org/translate/yast-cluster/master/ca/?checksum=aac24d946e4add19", "url": "https://l10n.opensuse.org/api/units/14448666/?format=api", "explanation": "", "extra_flags": "" } ] }