Re: inconsistency between the UNI spec and the Build tool

Re: inconsistency between the UNI spec and the Build tool

[Gao, Liming]

Felix:
  Thanks for your report. We will fix it in BaseTools to align to UNI spec. 

Thanks
Liming
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> Felix Poludov
> Sent: Wednesday, July 27, 2016 9:50 PM
> To: Kinney, Michael D <michael.d.kinney@intel.com>; edk2-
> devel@lists.01.org
> Subject: Re: [edk2] inconsistency between the UNI spec and the Build tool
> 
> No, STR_Xyz or str_x triggers the same error.
> 
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> Kinney, Michael D
> Sent: Tuesday, July 26, 2016 7:04 PM
> To: Felix Poludov; edk2-devel@lists.01.org; Kinney, Michael D
> Subject: Re: [edk2] inconsistency between the UNI spec and the Build tool
> 
> Felix,
> 
> Does STR_Xyz work?  I am wondering if the build tools are trying to enforce
> Camel case between the '_'.
> 
> Mike
> 
> > -----Original Message-----
> > From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> Felix Poludov
> > Sent: Tuesday, July 26, 2016 3:00 PM
> > To: edk2-devel@lists.01.org
> > Subject: [edk2] inconsistency between the UNI spec and the Build tool
> >
> > According to UNI specification string token identifier can use upper case
> and lower
> > case letters:
> > From section 2.1:
> > <Token> ::= <CtrlChar> "string" <MS> <Identifier>
> > <Identifier> ::= <Letter> [{<Letter>} {<Digit>} {<UN>}]*
> > <Letter> ::= {(\u0041-\u005A)} ; Characters A - Z
> >                     {(\u0061-\u007A)} ; Characters a - z
> >
> > However, when I'm trying to use lower case characters in string token
> identifier,
> > I'm getting a build error.
> >
> > Here is a test UNI statement I use:
> > #string STR_x                        #language eng "Test"
> >
> > Here is the build error I'm getting:
> > build...
> > : error 3000: The string token name STR_x defined in UNI file x.uni contains
> the
> > invalid lower case character.
> >
> > Is it an implementation bug or the specification inaccuracy?
> >
> > Thanks
> > Felix
> >
> > Please consider the environment before printing this email.
> >
> > The information contained in this message may be confidential and
> proprietary to
> > American Megatrends, Inc.  This communication is intended to be read only
> by the
> > individual or entity to whom it is addressed or by their designee. If the
> reader of
> > this message is not the intended recipient, you are on notice that any
> distribution of
> > this message, in any form, is strictly prohibited.  Please promptly notify the
> sender
> > by reply e-mail or by telephone at 770-246-8600, and then delete or
> destroy all copies
> > of the transmission.
> > _______________________________________________
> > edk2-devel mailing list
> > edk2-devel@lists.01.org
> > https://lists.01.org/mailman/listinfo/edk2-devel
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
> 
> Please consider the environment before printing this email.
> 
> The information contained in this message may be confidential and
> proprietary to American Megatrends, Inc.  This communication is intended to
> be read only by the individual or entity to whom it is addressed or by their
> designee. If the reader of this message is not the intended recipient, you are
> on notice that any distribution of this message, in any form, is strictly
> prohibited.  Please promptly notify the sender by reply e-mail or by
> telephone at 770-246-8600, and then delete or destroy all copies of the
> transmission.
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel