-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Grammatical properties in presentation xml #554
Comments
Bug indeed. Thanks for investigating. |
Additional issues:
=== jetty
[%metadata]
language:: eng
preferred:[pier]
[%metadata]
language:: fra
deck structure supported by vertical and possibly inclined piles extending into the sea, frequently in a
direction normal to the coastline Presentation xml contains only 'eng' (due two terms in the one element?): <term id="term-jetty">
<name>4.9</name>
<preferred language="eng">jetty; pier</preferred>
<definition>
<p id="_">deck structure supported by vertical and possibly inclined piles extending into the sea, frequently in a
direction normal to the coastline</p>
</definition>
</term>
=== disturbance
[%metadata]
pronunciation:: dıˈstɜ:bəns
any event or series of events that disrupt ecosystem, community, or population structure and alters the
physical environment no info for pronunciation in the metanorma xml: <term id="term-disturbance">
<name>4.10</name>
<preferred>disturbance</preferred>
<definition>
<p id="_">any event or series of events that disrupt ecosystem, community, or population structure and alters the
physical environment</p>
</definition>
</term> |
Let's not call it a bug, let's call it a different convention to what ISO 10241-1 A.1.3.2.4 recommends. Fixing. |
Oversight in model: we will also need to add sg/pl to model. (And dual: we need grammatical number as a category.) |
There is another issue: the grammatical information in presentation XML needs to be not boldfaced. @Intelligent2013 I will explicitly introduce boldfaced rendering of terms, so that it excludes grammatical information; you will likewise need to ensure that preferred, admitted, deprecated are not by default boldface. |
And grammatical information is delimited from designation by comma. |
The Presentation XML is conflating preferred terms for rendering; it must not if they are in different languages. |
Adding language, script, country code, pronunciation to designation rendering in Presentation XML. |
And only merging preferred terms if they don't have grammar information, have identical geographic info or language, and don't have pronunciations. |
Source: #550
The document: https://github.com/metanorma/iso-19135/tree/master/sources/iso-19135-1-2021
03-terms.adoc:
The presentation xml contains
n
at the end of preferred:Should I process
n
as indication fornoun
or is it a bug?Semantic xml is ok:
The text was updated successfully, but these errors were encountered: