The requirements and instructions for the production of the camera-ready copy will be provided by Conference Publishing Solutions shortly.
In the following, they are summarized briefly. Help on formatting papers can additionally be found at the
help page of Conference Publishing Solutions.
Make sure your paper:
does not exceed the page limit specified in the acceptance-notification e-mail,
is in PDF format,
is in letter page size,
does not have page numbers,
has all fonts embedded in the PDF file,
uses only scalable font types (like Type 1, TrueType) --- bit-mapped font types (like Type 3) are not acceptable,
has all figures embedded in vector graphics
(if not possible, use a high-resolution bitmap format of at least 300 dpi;
do not use JPG, but a lossless format like PNG or GIF),
has all text in figures and tables large enough and readable when printed,
has a caption for every figure or table,
has the title and all headings properly capitalized,
has no orphans and widows, and
does not use footnote references in the abstract.
The use of color in regular body text (e.g., in order to emphasize words, URLs, or citations)
is discouraged due to reduced readability and greyscale printing.
The use of color is allowed in figures, tables, listings, and in non-body text,
such as source code, XML snippets, etc.
Conference Specific Requirements
The format of your paper must strictly adhere to the following single-column IEEE conference-proceedings format:
The conference committee believes that the papers in the CSEE&T proceedings should not only reflect an appropriate academic standard but that they should also be aesthetically pleasing and reflect a consistent high standard of presentation. In producing your final paper we therefore request that you use the information and checklist on this page in achieving this.
The Abstract (where required) can be read in isolation from the paper and includes sufficient information to enable an eventual reader to determine the relevance of the paper to their work/interests. The introductory section of the paper should clearly place the paper in context, "set the scene", and make the reader aware of what he/she will find in the rest of the paper. Please remember that the Abstract and Introduction perform different roles and should not depend upon each other.
The paper is clearly structured with a reasonable balance between the sections. Sections should be numbered 1., 2., 3., etc. with subsections in the hierarchy numbered, for example 2.1., 2.2., etc. Please ensure that there are no single children subsections (i.e., there should not be a 2.1. unless there is at least a 2.2.). Please ensure that only the sections within the body of your paper are numbered – you should not number for example: Abstract, Acknowledgements, References. You may also wish to consider the cohesion and coupling of the sections within your paper.
There is a clear conclusion to the paper that does not simply reiterate what has been said earlier. Informative conclusions should draw together the themes that have been explored in the body of the paper and/or effectively point to areas for future work.
Each reference is complete and accurate. Please do check that an eventual reader can actually access your references. Please remember that since the Abstract is intended to be read in isolation from the paper, it should not depend on the reference list.
Before submitting your paper as camera-ready, please check off the following items
(this is not a complete list and does not replace the IEEE style guide,
but serves as a list of frequently noticed issues):
Title: every important word must start capitalized; a word that follows a colon is always capitalized.
Headings: number ends with a dot, heading starts capitalized.
Orphans and widows should be eliminated (cf. the help section for hints).
Tables and figures (also headings, program code, and formulas) must not run into
the margins outside the text area.
Figures must be either embedded as vector graphics, or as high-resolution bitmap (300 dpi).
The font of text in the figures should be large enough and readable when printed.