Open
Conversation
- Add NA prefix to current languages - Bring "generic" definition over from OOT3DR - Deprecate MakeColored in favor of generic Text "#"
- Add EUR versions of English, French, and Spanish - Support assiging values to EUR strings - Update functions to support EUR strings
To be uncommented once all Text objects are updated to match
- Add EU languages to iterative funtions - Fix error in planned languages
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The American and European versions of French and Spanish have some different item names and such, so it's probably a good idea to start preparing for them having separate Custom Messages.
And just in case, European English is also accounted for.