Fix idl encoding support - #286
Open
tr1cks wants to merge 1 commit into
Open
Conversation
…on to specify encoding of IDL files, in parsing always was used OS specific encoding. That worked fine only for IDL in ASCII (without national language comments) or if you was lucky enough, that OS encoding matches IDL encoding.
tr1cks
force-pushed
the
fix-idl-encoding-support
branch
from
March 15, 2017 14:18
7d068c4 to
62e18fa
Compare
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.
Fixed bug with IDL encoding support. Before this moment we haven't option to specify encoding of IDL files, in parsing always was used OS specific encoding. That worked fine only for IDL in ASCII (without national language comments) or if you was lucky enough, that OS encoding matches IDL encoding.
This change has backward compatibility.