Skip to content

fix. template files should use UTF8 encoding other than UTF8 BOM#236

Merged
albertli-msft merged 1 commit intomainfrom
dev/albertli/fix-template-encoding
Feb 17, 2023
Merged

fix. template files should use UTF8 encoding other than UTF8 BOM#236
albertli-msft merged 1 commit intomainfrom
dev/albertli/fix-template-encoding

Conversation

@albertli-msft
Copy link
Copy Markdown
Contributor

@albertli-msft albertli-msft commented Feb 17, 2023

Template files should be encoded in UTF8 other than UTF8 w/ BOM.

UTF8-BOM would prefix a zero width no-break space, 0xEF 0xBB 0xBF, at the beginning of the file for editors to more reliably to tell whether the file is encoded in UTF8 or not.
https://www.compart.com/en/unicode/U+FEFF

And it would cause problem when we need to directly handle the whole file over to the parser. Either we have to trim white spaces manually or we have to tell whether file is encoded of BOM.

So, I suggested encode all files in UTF8 by default for simplicity.

@albertli-msft albertli-msft merged commit 821ee97 into main Feb 17, 2023
@albertli-msft albertli-msft deleted the dev/albertli/fix-template-encoding branch February 17, 2023 16:25
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.

2 participants