From: "Zhu, Yonghong" <yonghong.zhu@intel.com>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Carsey, Jaben" <jaben.carsey@intel.com>,
"Shaw, Kevin W" <kevin.w.shaw@intel.com>,
"Zhu, Yonghong" <yonghong.zhu@intel.com>
Subject: Re: [edk2-UniSpecification PATCH] Allow .uni files on disk to be UTF-8 without a BOM
Date: Wed, 26 Apr 2017 02:10:01 +0000 [thread overview]
Message-ID: <B9726D6DCCFB8B4CA276A9169B02216D51E66548@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1493168839-11708-1-git-send-email-michael.d.kinney@intel.com>
Reviewed-by: Yonghong Zhu <yonghong.zhu@intel.com>
Best Regards,
Zhu Yonghong
-----Original Message-----
From: Kinney, Michael D
Sent: Wednesday, April 26, 2017 9:07 AM
To: edk2-devel@lists.01.org
Cc: Carsey, Jaben <jaben.carsey@intel.com>; Zhu, Yonghong <yonghong.zhu@intel.com>; Shaw, Kevin W <kevin.w.shaw@intel.com>
Subject: [edk2-UniSpecification PATCH] Allow .uni files on disk to be UTF-8 without a BOM
https://bugzilla.tianocore.org/show_bug.cgi?id=507
GitHub branch for review:
* https://github.com/mdkinney/edk2-UniSpecification/tree/Bugzilla_507_SupportUtf8Files
GitHub word diff view of the patches in this series:
* [1/1] https://github.com/mdkinney/edk2-UniSpecification/commit/68aedacc21e1ee606e97be4a7bcc158a4ad4c72d?w=1
Cc: Jaben Carsey <jaben.carsey@intel.com>
Cc: Yonghong Zhu <yonghong.zhu@intel.com>
Cc: Kevin W Shaw <kevin.w.shaw@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Michael Kinney <michael.d.kinney@intel.com>
Michael Kinney (1):
Allow .uni files on disk to be UTF-8 without a BOM
2_unicode_strings_file_format.md | 9 ++++++---
README.md | 27 ++++++++++++++-------------
2 files changed, 20 insertions(+), 16 deletions(-)
--
2.6.3.windows.1
prev parent reply other threads:[~2017-04-26 2:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 1:07 [edk2-UniSpecification PATCH] Allow .uni files on disk to be UTF-8 without a BOM Michael Kinney
2017-04-26 1:07 ` Michael Kinney
2017-04-26 16:15 ` Tim Lewis
2017-04-26 17:44 ` Carsey, Jaben
2017-04-26 17:53 ` Tim Lewis
2017-04-26 18:25 ` Kinney, Michael D
2017-04-26 18:11 ` Kinney, Michael D
2017-04-26 18:34 ` Tim Lewis
2017-04-26 18:46 ` Kinney, Michael D
2017-04-26 18:53 ` Tim Lewis
2017-04-26 22:47 ` Kinney, Michael D
2017-04-26 23:13 ` Tim Lewis
2017-04-27 0:02 ` Kinney, Michael D
2017-04-27 0:26 ` Tim Lewis
2017-04-28 16:47 ` Tim Lewis
2017-04-28 17:22 ` Kinney, Michael D
2017-04-26 2:10 ` Zhu, Yonghong [this message]
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=B9726D6DCCFB8B4CA276A9169B02216D51E66548@SHSMSX103.ccr.corp.intel.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