Make header more Unicode (possibly buggy) #5
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
|
Sorry for the late reply. I was on a business trip and didn't notice this PR. Will test it the weekend! |
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.
I like em dashes and curly quotes so I decided to make this one-line change instead of opening an Issue first. I will not be the least bit offended if you don't merge it in.
One caveat: I don't quite have everything set up on my computer to actually run TLGS in development with this change, so I can't test it myself. For example, I'm not sure if I should have stuck an
Lbefore the string or if that would break something (I'm not sure if people usestd::wstringor if that just died out and people usestd::stringwith UTF-8 in it).