GeoFrotz: Fixed output of german umlauts #481
Open
+10
−14
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 4 commits
February 29, 2024 23:31
…D or get_geos_low_word, which causes random values for the extension-header lenght. This causes, that frotz is looking for an unicode table, which isn't really there.
…nted as there transcription.
…cause German umlauts were not displayed correctly. Now their transcription will be displayed.
…ad to random values, which has several negative effects on text-output especially for accented characters. the features of the header-extension are not implemented in the geos-port of frotz (e.g. Mouse-Click-Positions, Unicode, ...)
|
Bariossimo enters SDK world... FANTASTICO! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using German story files, the umlauts were previously displayed as question marks or were otherwise unreadable. A bug when reading a header extension led to the use of a Unicode table that did not really exist in the story file. This is now bypassed. Furthermore, non-Latin1 characters are now converted to ASCII. For German umlauts e.g. ä = ae, Ö = Oe, ...