From: Sean Brogan <sean.brogan@microsoft.com>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Edk2 uni file encoding
Date: Wed, 7 Nov 2018 23:00:24 +0000 [thread overview]
Message-ID: <DM5PR21MB018564B7B9AB81D0CAE334C9E1C40@DM5PR21MB0185.namprd21.prod.outlook.com> (raw)
Is there a definitive answer for the file encoding for all UNI files in edk2?
If not I would like to propose one. Incorrect encoding causes tool issues and is something we can easily check for and fix.
Proposal: All UNI files in edk2 should be
1. UTF-8
Or
1. Use a BOM and be UTF-16
https://en.wikipedia.org/wiki/Byte_order_mark
Results from searching edk2:
1 - UTF-16 LE BOM file: EdkCompatibilityPkg\Compatibility\FrameworkHiiOnUefiHiiThunk\Strings.uni
919 - Without BOM and decoded as UTF-8
Thoughts?
Future question: Can we make rule for all other standard file types (c, h, dec, dsc, fdf, inf,)?
Thanks
Sean
next reply other threads:[~2018-11-07 23:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 23:00 Sean Brogan [this message]
2018-11-08 6:00 ` Edk2 uni file encoding Gao, Liming
2018-11-08 7:10 ` Sean Brogan
2018-11-08 16:46 ` Kinney, Michael D
2018-11-08 16:55 ` Oram, Isaac W
2018-11-08 13:38 ` Laszlo Ersek
2018-11-08 16:42 ` Leif Lindholm
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DM5PR21MB018564B7B9AB81D0CAE334C9E1C40@DM5PR21MB0185.namprd21.prod.outlook.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox