This belongs to CheckGlossaryTester panel. The idea will be ported to ContentEditionPanel in LocalizeThat.

This involves changing JTextArea to a JTextPane (in ContentEditionPanel it already is a JTextPane), and using styles to add an image after each failed word with a tooltip that displays the possible suggestions.

Aside from the technical definition of two Glossary Entries being equal (same Id, equals() returning true and so), from the perspective of a translator, a given Glossary Entry would be equivalent to another if they belong to the same Glossary and they have the same term and pos (PartOfSpech) values. Currently, GlsEntryGuiManager does not implement validations to prevent that two GlsEntry instances end being equivalent given that criteria. Something similar happens to translations (GlsTranslation).

GlsEntryGuiManager should implement that validations (see GlsEntry.isEquivalent() and GlsTranslation.isEquivalent()).

LocalizeThat! dialogs are placed in net.localizethat.gui.dialogs, so let's create that package in GlossaryManager and move CSVImport into it.

LocalizeThat! has now L10n and a L10n Manager that does not use Beans Binding, has nice icons and includes some validations on saving. It is better to import it into GlossaryManager.

Glossary Manager currently implements an Import from CSV feature that may be used to transfer data from spreadsheet-maintained glossaries. However, as this is currently a testbed project for learning techniques, a corresponding export feature has not been added, since it offers less room for learning.

Some in the future, the export feature will be added.

LocalizeThat! tabpanel classes implement AbstractTabPanel, which forces concrete tabpanels to implement onTabPanelAdded and onTabPanelRemoved.