You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi Ethan,
I don't know if this is a numishare issue or something I forget to do, but some translations are not working properly in the coins page. For example
<physDesc>
<axis>11</axis>
<measurementsSet>
<diameter>12</diameter>
<thickness>13</thickness>
<weightunits="g">14</weight>
</measurementsSet>
<conservationState>
<completeness>intero</completeness>
<wearxlink:type="simple"xlink:href="http://nomisma.org/id/extremely_worn">Extremely
worn</wear>
</conservationState>
<countermark>
<symbol>testo di prova</symbol>
<descriptionxml:lang="it">descrizione in italiano</description>
<descriptionxml:lang="en">description in English</description>
</countermark>
<testmark>
<symbol>testo di prova</symbol>
<descriptionxml:lang="it">descrizione in italiano</description>
<descriptionxml:lang="en">description in English</description>
</testmark>
</physDesc>
With this kind of XML the UI shows a double description field both in Italian and in English (regarding the selected language). I noticed that this happens for many of the fields that should be in theory translatable. Some of them instead works properly, for example the description of the type of a coin side:
<obverse>
<type>
<descriptionxml:lang="it">Working Italian description</description>
<descriptionxml:lang="en">Working English description</description>
</type>
<symbol>Testo di prova</symbol>
<persnamexlink:type="simple"xlink:role="deity"xlink:href="http://nomisma.org/id/zeus_velchanos">Zeus Velchanos</persname>
<persnamexlink:type="simple"xlink:role="artist"xlink:href="http://nomisma.org/id/k_basileus_cyzicus">K... Basileus</persname>
<persnamexlink:type="simple"xlink:role="engraver"xlink:href="http://nomisma.org/id/p_carisius">P. Carisius</persname>
<persnamexlink:type="simple"xlink:role="portrait"xlink:href="http://nomisma.org/id/c_marius_c_f_tro">C. Marius C F Tro</persname>
</obverse>
But if I add only a general description without the type tag I still get a double voice in the UI:
<obverse>
<descriptionxml:lang="it">Working Italian description</description>
<descriptionxml:lang="en">Working English description</description>
<symbol>Testo di prova</symbol>
<persnamexlink:type="simple"xlink:role="deity"xlink:href="http://nomisma.org/id/zeus_velchanos">Zeus Velchanos</persname>
<persnamexlink:type="simple"xlink:role="artist"xlink:href="http://nomisma.org/id/k_basileus_cyzicus">K... Basileus</persname>
<persnamexlink:type="simple"xlink:role="engraver"xlink:href="http://nomisma.org/id/p_carisius">P. Carisius</persname>
<persnamexlink:type="simple"xlink:role="portrait"xlink:href="http://nomisma.org/id/c_marius_c_f_tro">C. Marius C F Tro</persname>
</obverse>
I have to manually change XML files in the eXist db because if I add the additional contextual fields, that you recently include, numishare UI doesn't allow me to save the coin properly (I guess because UI still lacks of the new fields).
This is not a big problem, but I thought that there might be issues with indices or something like this.
Thanks!
The text was updated successfully, but these errors were encountered:
Hi Ethan,
I don't know if this is a numishare issue or something I forget to do, but some translations are not working properly in the coins page. For example
With this kind of XML the UI shows a double description field both in Italian and in English (regarding the selected language). I noticed that this happens for many of the fields that should be in theory translatable. Some of them instead works properly, for example the description of the type of a coin side:
But if I add only a general description without the type tag I still get a double voice in the UI:
I have to manually change XML files in the eXist db because if I add the additional contextual fields, that you recently include, numishare UI doesn't allow me to save the coin properly (I guess because UI still lacks of the new fields).
This is not a big problem, but I thought that there might be issues with indices or something like this.
Thanks!
The text was updated successfully, but these errors were encountered: