Hi Tim,
I agree with your assessment. I would like to follow up by asking if anyone
would object to removing the alternate control characters and just redefine the
UNI file format to use just the “#” symbol as the ‘control character’ and
stating that “//” is used to indicate a comment that terminates with the end of
the line (no comment blocks permitted)?
If there is no objection by September 21, I will post an errata and we will
modify the existing EDK II VfrCompiler code to only use the hash “#” character
symbol for the keyword identifier (AKA control character). The errata would
also remove the “/=#” line from the examples.
Cheers,
Larry
From: Tim Lewis [mailto:[email protected]]
Sent: Wednesday, August 29, 2012 2:26 PM
To: Carsey, Jaben
Cc: [email protected]
Subject: Re: [edk2] Proposed Syntax for .idf (Image Definition File) format.
Jaben –
You are correct. I find that incredibly distracting, so was hoping to avoid it
with .idf. It seems like an anachronism. None of the .uni files in the EDK2
tree use the ‘/’ control character.
Tim
From: Carsey, Jaben
[mailto:[email protected]]<mailto:[mailto:[email protected]]>
Sent: Wednesday, August 29, 2012 2:22 PM
To: Tim Lewis
Cc: Ifan Llwyd;
[email protected]<mailto:[email protected]>;
Carsey, Jaben
Subject: RE: [edk2] Proposed Syntax for .idf (Image Definition File) format.
Tim,
I think that the actual control character of UNI files is a single forward
slash ‘/’, and that most of the files have a line like this “/=#” to change the
character to #.
-Jaben
From: Tim Lewis [mailto:]
Sent: Wednesday, August 29, 2012 2:16 PM
To: [email protected]<mailto:[email protected]>;
Ifan Llwyd
Subject: Re: [edk2] Proposed Syntax for .idf (Image Definition File) format.
Samer –
The HII database has a specific separate record type for JPEG files. It is
possible that #image could support jpeg also and would convert it into the HII
bitmap record type. But we need some tag to explicitly state that it will
create a JPEG record.
Tim
From: El-Haj-Mahmoud, Samer
[mailto:[email protected]]<mailto:[mailto:[email protected]]>
Sent: Wednesday, August 29, 2012 11:07 AM
To: Ifan Llwyd;
[email protected]<mailto:[email protected]>
Subject: Re: [edk2] Proposed Syntax for .idf (Image Definition File) format.
Tim,
Thank you for proposing this. It would be nice to add something similar to
build HII Font packages and Keyboard Layout packages as well.
In UNI files, a “//” is used for comments, while “#” is used for tag
definitions, such as “#string”, “#language”, and “#langdef”
Also, any reason the #jpeg construct is different from #image, since #image can
be a BMP, GIF, or PNG files? Why not just use #image for JPG files as well?
Thanks,
--Samer
From: Ifan Llwyd
[mailto:[email protected]]<mailto:[mailto:[email protected]]>
Sent: Wednesday, August 29, 2012 12:14 PM
To: [email protected]<mailto:[email protected]>
Subject: Re: [edk2] Proposed Syntax for .idf (Image Definition File) format.
Hi Tim.
This may be naive, as I am not at all familiar with HII, nor .idf.
However given that "Comments are introduced with the ‘#’ character " then the
keywords "#image", etc seem an unfortunate choice. Have I missed something?
From: Tim Lewis <[email protected]<mailto:[email protected]>>
To: "[email protected]<mailto:[email protected]>"
<[email protected]<mailto:[email protected]>>
Sent: Wednesday, 29 August 2012, 8:53
Subject: [edk2] Proposed Syntax for .idf (Image Definition File) format.
...
Comments are introduced with the ‘#’ character and are terminated by the end
of the line. The following table summarizes the commands in the image
definition file:
Command
Description
#image [#id integer] identifier “file-name”
Generate a bitmap image from the file specified by file-name.
#jpeg [#id integer] identifier|integer “file-name”
Generate a JPEG image from the file specified by file-name. >
#include “file-name”
Include another .idf file.
...
------------------------------------------------------------------------------
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
