Skip to content
Snippets Groups Projects
Commit be37674a authored by Lennard Strohmeyer's avatar Lennard Strohmeyer :penguin:
Browse files

#62 translated all strings to German

parent e4d4cfc0
Branches
No related tags found
No related merge requests found
<div class="provider">
<h1>Provider Schemas</h1>
<h1 i18n="Provider Schemas | Provider Schemas header @@providerSchemas">Provider Schemas</h1>
<nz-tabset>
<nz-tab *ngFor="let provider of providers" [nzTitle]="provider.name">
......
<div class="data-removal">
<h1 i18n="Data Removal | Header text data removal page @@headerDataRemovalPage">
Löschaufträge
Deletion requests
</h1>
<p i18n="Data Removal Description | Description data removal @@dataRemovalDescription">
Mithilfe von Löschaufträgen lassen sich im LRS (Learning Record Store) gespeicherte Daten
entfernen. Polaris gibt hierzu die Löschaufträge an den LRS weiter, welcher anschließend für
die Ausführung verantwortlich ist. Konzeptionbedingt kann es hierbei zu einer zeitlichen
Verzögerung kommen, da der LRS etwa Daten vornehmlich bei Nacht löscht.
Data stored in the LRS (Learning Record Store) can be removed with the help of delete requests. Polaris forwards the deletion requests to the LRS, which is then responsible for executing them. Depending on the concept, there may be a time delay, as the LRS primarily deletes data at night, for example.
</p>
<button
nz-button
(click)="requestDataRemoval()"
i18n="Button Remove LRS data | Button text @@dataRemovalButtonText">
Alle Daten entfernen
Remove all data
</button>
<nz-table #removalTable [nzData]="jobs">
......
......@@ -42,6 +42,7 @@
routerLink="/provider"
*ngIf="loggedIn?.isProvider"
[nzMatchRouter]="true"
i18n="Provider | Header Entry @@providerHeader"
>
Provider
</li>
......
This diff is collapsed.
......@@ -278,6 +278,9 @@
<context context-type="linenumber">104</context>
</context-group>
</trans-unit>
<trans-unit id="providerHeader" datatype="html">
<source>Provider</source>
</trans-unit>
<trans-unit id="pauseDataRecordingHeader" datatype="html">
<source>Continue Data Recording</source>
<context-group purpose="location">
......@@ -457,6 +460,9 @@
<note priority="1" from="description"> Provider schema information </note>
<note priority="1" from="meaning">Superseded By </note>
</trans-unit>
<trans-unit id="providerSchemas" datatype="html">
<source>Provider Schemas</source>
</trans-unit>
<trans-unit id="toggleDefinition" datatype="html">
<source>Toggle Definition</source>
<context-group purpose="location">
......@@ -885,7 +891,7 @@
</context-group>
</trans-unit>
<trans-unit id="headerDataRemovalPage" datatype="html">
<source> Löschaufträge </source>
<source> Deletion requests </source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/data-removal/data-removal.component.html</context>
<context context-type="linenumber">2,4</context>
......@@ -894,7 +900,7 @@
<note priority="1" from="meaning">Data Removal </note>
</trans-unit>
<trans-unit id="dataRemovalDescription" datatype="html">
<source> Mithilfe von Löschaufträgen lassen sich im LRS (Learing Record Store) gespeicherte Daten entfernen. Polaris gibt hierzu die Löschaufträge an den LRS weiter, welcher anschließend für die Ausführung verantwortlich ist. Konzeptionbedingt kann es hierbei zu einer zeitlichen Verzögerung kommen, da der LRS etwa Daten vornehmlich bei Nacht löscht. </source>
<source> Data stored in the LRS (Learning Record Store) can be removed with the help of delete requests. Polaris forwards the deletion requests to the LRS, which is then responsible for executing them. Depending on the concept, there may be a time delay, as the LRS primarily deletes data at night, for example. </source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/data-removal/data-removal.component.html</context>
<context context-type="linenumber">6,11</context>
......@@ -903,7 +909,7 @@
<note priority="1" from="meaning">Data Removal Description </note>
</trans-unit>
<trans-unit id="dataRemovalButtonText" datatype="html">
<source> Alle Daten entfernen </source>
<source> Remove all data </source>
<context-group purpose="location">
<context context-type="sourcefile">src/app/data-removal/data-removal.component.html</context>
<context context-type="linenumber">17,19</context>
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment