Open RieksJ opened 8 months ago
I can see various options:
The basic problem seems to be that if an MRG entry is imported from an external scope (be it as part of a completely imported MRG or as an MRG entry that was selected from an MRG imported from an external scope), their TermRefs are to be interpreted as they would have been in their originating scope. Problems this may pose include:
We need to find out if there are more such discrepancies, and then think about whether this is an issue to address, and if so, how to do that.
Analogous to #27, we might make maps of interpreters and converters (naming the interpreters and converters, as if we have additional 'predefined' ones). The idea could be that we might think of how to employ this, e.g., by stuffing them into the MRG, such that in other contexts, this can be used to interpret and convert termrefs found in MRG entries (e.g. by specifying 'defaults' for them in the MRG), or as values in glossaryTermRefInterpreter
and glossaryTermRefConverter
fields of MRG entries.
we must PROPERLY DEFINE if/how this might work
Let's do it as follows:
[showtext](termType:term@scopetag:vsntag)
. Also, it has a field that specifies the converter that generates a termref according to this, its (default) termref interpreter. Failute to do so expects that this will be the (predefined) converter for the default termref.While working on the code regarding the conversion of termrefs included within mrg entries imported from an external scope, I came to realise that a good amount of work still has to be done in order to achieve the desirable result. The following observations are related to this, and give an update about the status of this issue.
interpreter
is provided within the SAF, the default interpreter has to be retrieved (which is currently only stored within the interpreter of the TRRT).A workaround could consist of the following:
-tid <tid>
(or --terminology <tid>
), where <tid>
is a terminology identifier. This may even be a good idea on its own...<tid>
as its default scope, similar to the point above. The idea is that the MRG associated with the <tid>
would contain the default interpreter for the TermRefs used therein.
When the HRGT generates a HRG from an MRGRef which specifies (a particular version of) some MRG, that may have been generated in the current scope, or imported from some external scope, it is very likely that the HRG entries that are generated will include TermRefs, and the idea is that such TermRefs should be resolvable from the MRG for which the HRG was created (even though this is may not be true in all cases).
Let's think a bit about this before taking actions to resolve this