Skip to content

Conversation

@RemiGC
Copy link
Contributor

@RemiGC RemiGC commented Jun 24, 2021

This PR add a way to read Linux traduction files that are encoded as UTF32 instead of Unicode Widestring like on Windows. This should fix #21 .

The way this is done for now is check for the filename on the construction of EdataManager and assign a most likely OSPlatform for the file. When a TradFileViewModel is built, it will read the OSPlatform value and send the string stype to the TradManager.

In addition, some files were split into a separate project and with a crossplatform target of net5.0 instead of net5.0-windows, allowing a test suite that can also be run under Linux.

Leaving in draft so I can get comment, while I still work on the UI and additional tests.
Linux and Windows dictionary, side-by-side:
image

For now, I show a textbox with the OSPlatform, either Linux, Windows or Generic. I plan to switch to an icon. Do you guys have any better idea to present this? Should I simply hide this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Characters corrupted - linux files

1 participant