I have noticed that a large number of escape sequences are defined in the
current .uni build specification, but they are defined in a manner which makes
future extensibility difficult. Escape sequences (in order to be effective)
must always be (a) fixed length, (b) delimited or (c) never extended. Consider
the case of \hy (hyphen) in the current specification (or \r, for that matter).
Today, I might create a .UNI file with the string "\hybrid" which would be
encoded as <hyphen>brid. If, tomorrow, the UEFI specification decides to denote
special usage for "hybridae" (just for example), we could not add an escape
code \hyb, because previous existing code which used "\hybrid" would now
generate a different string (<hybridae>rid instead of <hyphen>brid.)
Since (a) these codes are not currently implemented (except \r, \n, \t, \uxxxx,
\wide, \narrow and \nbr) and (b) it is likely that support for the UEFI font
characters must be in the work, I suggest that these be reconsidered. Instead,
I suggest that the \!zzzz! for be used for these special characters. These
delimited forms are much more robust for this usage.
Tim
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
edk2-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/edk2-devel
