lem-entry-readings.component.html 1.1 KB

12345678910111213141516171819202122232425
  1. <span class="lem-entry-reading">
  2. <!--
  3. It's necessary to handle both readings with and without nested apps, because nested apps inside app-entry-detail have different behaviour,
  4. so we can't use apparatus-entry-component to render them.
  5. -->
  6. <evt-reading *ngIf="data.nestedLemsIDs.length === 0" [data]="data.lemma"></evt-reading>
  7. <ng-container *ngIf="data.nestedLemsIDs.length > 0">
  8. <ng-container *ngTemplateOutlet="template context: { rdgHasCounter: rdgHasCounter }"></ng-container>
  9. </ng-container>
  10. <ng-container *ngIf="data.lemma.content.length > 0">
  11. <span *ngFor="let witID of data.lemma.witIDs"> {{ witID }}</span>
  12. </ng-container>
  13. <span>] </span>
  14. </span>
  15. <span class="lem-entry-reading" *ngFor="let el of significantRdg">
  16. <evt-reading *ngIf="el.content.length !== 0" [data]="el"></evt-reading>
  17. <span class="font-italic" *ngIf="el.content.length === 0">omit.</span>
  18. <!-- TODO: handle lacunastart and lacunaend -->
  19. <ng-container *ngFor="let witID of el.witIDs">
  20. <span *ngFor="let wit of getWits$(witID) | async" class="font-italic"> {{ wit }} </span>
  21. </ng-container>
  22. </span>