C-Scene Submissions Guidlines

Please adhere to the following guidelines for article submissions:

Policies

   * Once submitted, all articles become property of C-Scene. We reserve
     the right to publish, re-publish, and edit all articles. We will not
     make major edits without your consent, and you can keep your copyright
     otherwise.
   * We assume that articles submitted to us are ready for publication, and
     reserve the right to publish them in any issue.

General Formatting

   * Please include your real name, IRC nickname (if applicable), and email
     address with your submission. If this is your first submission, please
     include a short bio that lists your interests and experience, along
     with relevant contact data.
   * Please make up a title for your article.
   * While we try to correct spelling and grammar, you should spell-check
     and proofread your writing before submitting it.
   * Articles should be either in plaintext ASCII format or fully-formatted
     HTML (ie, your code is <PRE> formatted and all special characters like
     & are replaced with the proper HTML codes). If you are not confident
     in your ability to format your article so that everyone (including
     users of text-based browsers like Lynx) can read it, please send it in
     formatted ASCII and let us do the work. If your article is not
     properly formatted, we will have to send it back to you with
     suggestions on how to format it, because we don't have the time to do
     it for you. We suggest you run your article through a validation tool
     such as weblint.
   * If your article is in HTML format, please make sure that you use only
     valid HTML3 extensions. Do not use Netscape or Internet Explorer
     extensions unless you are sure that browsers which do not support
     these extensions can ignore them without making your article
     unreadable. This means no JavaScript, no frames, no ActiveX controls,
     etc. You can use font coloring, but remember that Lynx and other text
     browsers will not display it, so don't rely on it.
   * If you do your own complete HTML formatting, then images are
     acceptable. Graphics are often necessary to get your point across.
     Unfortunately, Lynx does not display graphics (does someone want to
     write a JPEG to ASCII-art translator?), so keep in mind that users of
     Lynx will not be able to see your pictures. Try to include ALT text in
     your IMG tags so they will at least know what they're missing.
   * While multiple-file submissions are accepted, please try to keep them
     to a minimum. Web space isn't cheap.

Source Code

   * We try to check the source code for obvious errors, but you should
     make sure all your code compiles cleanly and does not rely on any
     undefined behavior (unless you state it specifically).
   * Unless specifically stated, all source code should be fully ISO/ANSI
     compliant. We welcome API and platform specific code, but don't assume
     that the readers are able to guess your platform if you don't tell
     them.
   * Format your source code consistently and cleanly, unless you are
     purposely writing obfuscated code.
