Closed iTReprise closed 1 week ago
So, the name of the lexicon has an umlaut in it, is that right? On Ubuntu it results in an error message for me but it doesn't crash eAPDD. Would it be possible to send the files epadd.log and epadd.warnings.log from the epadd-settings folder? Thanks.
Yes, with an umlaut.
I was unclear - you are right. ePADD doesn't crash per se, it just shows the error page but is still alive and well. Do you still need logs?
Yes, that would be helpful.
Sorry, no I actually don't need the logs.
Thanks for reporting this. We have fixed the issue for the next ePADD 11 release. You can try it out: SharePoint Link. You should have access to the file. Please let me know if it says you don't have access permission.
You might need to clear your browser cache.
It won't work for the existing lexicon, you have to create it again.
Fixed in v11.0.1
Describe the bug Creating a lexicon with a special character (I tested ü & ä) creates a seemingly working lexicon but removes my abilty to interact with it as epadd chrashes when clicking on it. This prevents me from renaming it or adding/removing entries.
Steps to Reproduce Steps to reproduce the behavior:
Screenshots Broken encoding in lexicon list:![grafik](https://github.com/ePADD/epadd/assets/29485072/aae02f79-a1e8-4a59-807d-983b25d950f3)
Desktop: