Current behavior:
It is not possible to upload an image directly to a TB entry in order to have a visual reference of the term from the Editor.
Workaround:
It is possible to add URLs leading to images to the URL field in the TB entry, however, this requires users to open external pages.
Requested behavior:
Add an image field to the in order to allow the upload of pictures to TB entries. The uploaded picture could be displayed at the bottom of the CAT pane whenever the TB match is selected.
Use case:
In cases of confidential content, using URLs is not possible for security reasons, as those could be easily shared with unauthorized external users. Having a visual reference inside the Editor would improve and speed linguists' performance, and also overcome the mentioned security issues.
3 comments
Hi. Please note that if you choose to implement this, it should be also supported in the TBX import/export.
TBX standard allows for embedding base64 encoded data in back matter of the TBX file. See snippet below.
In practice, preferred approach is to reference external files using <xref> element and implementing preview feature directly within editor environment. Access management for the referenced data can be achieved through other means.
Jano
<body>
<termEntry>
...
<descrip type="figure" target="fid-cricketbat">cricket bat</descrip>
...
</termEntry>
</body>
<back>
<refObjectList type="binaryData">
<refObject id="fid-cricketbat">
<item type="codePage">base64</item>
<item type="format">jpg</item>
<item type="data">
/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAgGBgcGBQgHBwcJCQgKDBQNDAsLDBkSEw8UHRofHh0a...
</item>
</refObject>
</refObjectList>
</back>
A worthy entry on the "Reasons why you shouldn't use Memsource" list, which is obviously a very short list, but a list nonetheless.
Images/Graphics in a termbase are sometimes vital for understanding complex technical concepts. We have been using lots of graphics in our previous terminology application and find it very difficult having to do without.
Please sign in to leave a comment.