Originally reported by: Marcel Bollmann (Bitbucket: mbollmann, GitHub: mbollmann)
Traditionally, the GUI requires that at least a POS tagset is associated with each text, while every other tagset type is optional.
I don't see any reason to keep this restriction, since the tagset handling on the GUI side is completely modularized now. However, opening a text without an associated POS tagset still results in a crash, so apparently some parts of the code still rely on this assumption. Can we fix this?
Originally reported by: Marcel Bollmann (Bitbucket: mbollmann, GitHub: mbollmann)
Traditionally, the GUI requires that at least a POS tagset is associated with each text, while every other tagset type is optional.
I don't see any reason to keep this restriction, since the tagset handling on the GUI side is completely modularized now. However, opening a text without an associated POS tagset still results in a crash, so apparently some parts of the code still rely on this assumption. Can we fix this?