This bug is the one that prompted me to ask for more guidance on localization strategies over the weekend at the conference. I've updated the branch to include the title and author, as discussed. However, this leads to an ugly mix of strings and display fields:
This bug is the one that prompted me to ask for more guidance on localization strategies over the weekend at the conference. I've updated the branch to include the title and author, as discussed. However, this leads to an ugly mix of strings and display fields:
<caption id="caption{ {index} }" *ngIf=" summary. copies. length" > >{{summary. copies. length} } Shelving Locations</span> >for</span> display- field [summary]="summary" field="title" [usePlaceholder ]="true" ></eg-bib- display- field> > - </span> display- field [summary]="summary" field="author" [usePlaceholder ]="true" ></eg-bib- display- field>
<span i18n="Shelving locations table heading"
<span i18n="Shelving locations table heading preposition"
<eg-bib-
<span i18n="Shelving locations table heading separator"
<eg-bib-
</caption>
That seems like it's going to cause problems for translators. I feel like there must be a better approach.