Hi,

The "#langdef" value used in various EDK-II *.uni files define
the language name in various ways, seemingly inconsistent.

Most use either:
    #langdef   en-US "english"
or:
    #langdef   en-US "English"

A few use:
    #langdef   en-US "en-US"

UefiShellInstall1CommandsLib.uni uses:
    #langdef   en-US "en-english"

UefiShellLevel1CommandsLib.uni uses:
    #langdef   en-US "en-USlish"

At least these last 2 usages should probably be fixed, perhaps others. 

Also, perhaps related, but it seems confusing that the code uses one (or
multiple formats) and the end user is asked to use another convention.
Besides the "English"/"en-US" formats that #langdef uses, however, the
end user docs (the shell commands that support the -L XXX switch)
presumes "Eng" format. FYI, there is a Eng/us-EN style lang code patch
on github.

Thanks,
Lee

------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
edk2-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/edk2-devel

Reply via email to