ISO basic Latin alphabet
Aa	Bb	Cc	Dd
Ee	Ff	Gg	Hh
Ii	Jj	Kk	Ll
Mm	Nn	Oo	Pp
Qq	Rr	Ss	Tt
Uu	Vv	Ww	Xx
Yy	Zz

K (named kay /ˈkeɪ/)^[1] is the eleventh letter of the ISO basic Latin alphabet.

History and usage[link]

In English, the letter K usually represents the voiceless velar plosive; this sound is also transcribed by /k/ in the International Phonetic Alphabet and X-SAMPA.

Egyptian hieroglyph D	Proto-Semitic K	Phoenician kaph	Etruscan K	Greek Kappa

The letter K comes from the Greek letter Κ (kappa), which was taken from the Semitic kap, the symbol for an open hand.^[2] This, in turn, was likely adapted by Semites who had lived in Egypt from the hieroglyph for "hand" representing D in the Egyptian word for hand, d-r-t. The Semites evidently assigned it the sound value /k/ instead, because their word for hand started with that sound.^[3] In modern-day English slang, the word "k" is used as a substitute for the abbreviation "O.K.", or "Okay." In International Morse code it is used to mean "over".^[4]

In the earliest Latin inscriptions, the letters C, K and Q were all used to represent the sounds /k/ and /g/ (which were not differentiated in writing). Of these, Q was used to represent /k/ or /g/ before a rounded vowel, K before /a/, and C elsewhere. Later, the use of C (and its variant G) replaced most usages of K and Q. K survived only in a few fossilized forms such as Kalendae, "the calends".^[5]

When Greek words were taken into Latin, the Kappa was changed to C, with a few exceptions such as the praenomen Kaeso.^[2] Some words from other alphabets were also transliterated into C. Hence, the Romance languages have K only in words from other language groups. The Celtic languages also chose C over K, and this influence carried over into Old English. Today, English is the only Germanic language to productively use hard C in addition to K (though Dutch use it in learned words of Latin origin and follows the same "hard / soft" distinction in such words as does French and English – but not in native words).

Some English linguists prefer to reverse the Latin transliteration process for proper names in Greek, spelling Hecate as "Hekate", for example. And the writing down of languages that do not have their own alphabet with the Latin one has resulted in a standardization of the letter for this sound, as in Kwakiutl.

In the International Phonetic Alphabet, [k] is the symbol for the voiceless velar plosive.

Several other alphabets use characters with sharp angles to indicate the sound /k/ or syllables that start with a /k/, for example: Arabic ك, Hebrew כ or ק, Korean ㄱ. This kind of phonetic-visual association was studied by Wolfgang Köhler. However, there are also many examples of rounded letters for /k/, like క in Telugu, ก and ค in Thai, Ք in Armenian, ክ in Geez, and C in Latin.

Related letters and other similar characters[link]

• Ƙ ƙ : Latin letter K with hook
• Κ κ/ϰ : Greek letter Kappa
• К к : Cyrillic letter Ka

Computing codes[link]

¹ and all encodings based on ASCII, including the DOS, Windows, ISO-8859 and Macintosh families of encodings.

Other representations[link]

NATO phonetic	Morse code
Kilo	–·–

Signal flag	Flag semaphore	Braille

See also[link]

• "K" replacing "C" in Satiric misspelling

Notes[link]

External links[link]

• Media related to K at Wikimedia Commons
• The Wiktionary entry for K
• The Wiktionary entry for k

This article contains instructions, advice, or how-to content. The purpose of Wikipedia is to present facts, not to train. Please help improve this article either by rewriting the how-to content or by moving it to Wikiversity or Wikibooks. (July 2011)

Text file created with gedit and viewed with a hex editor
Besides the text objects there are only EOL markers
with the hexadecimal value 0A.

In computing, a newline,^[1] also known as a line break or end-of-line (EOL) marker, is a special character or sequence of characters signifying the end of a line of text. The name comes from the fact that the next character after the newline will appear on a new line—that is, on the next line below the text immediately preceding the newline. The actual codes representing a newline vary across operating systems, which can be a problem when exchanging text files between systems with different newline representations.

There is also some confusion whether newlines terminate or separate lines. If a newline is considered a separator, there will be no newline after the last line of a file. The general convention on most systems is to add a newline even after the last line, i.e. to treat newline as a line terminator. Some programs have problems processing the last line of a file if it is not newline terminated. Conversely, programs that expect newline to be used as a separator will interpret a final newline as starting a new (empty) line.

In text intended primarily to be read by humans using software which implements the word wrap feature, a newline character typically only needs to be stored if a line break is required independent of whether the next word would fit on the same line, such as between paragraphs and in vertical lists. See hard return and soft return.

Representations[link]

Software applications and operating systems usually represent a newline with one or two control characters:

• Systems based on ASCII or a compatible character set use either LF (Line feed, '\n', 0x0A, 10 in decimal) or CR (Carriage return, '\r', 0x0D, 13 in decimal) individually, or CR followed by LF (CR+LF, '\r\n', 0x0D0A). These characters are based on printer commands: The line feed indicated that one line of paper should feed out of the printer thus instructed the printer to advance the paper one line, and a carriage return indicated that the printer carriage should return to the beginning of the current line. Some rare systems, such as QNX before version 4, used the ASCII RS (record separator, 0x1E, 30 in decimal) character as the newline character.
  • LF:    Multics, Unix and Unix-like systems (GNU/Linux, Mac OS X, FreeBSD, AIX, Xenix, etc.), BeOS, Amiga, RISC OS and others.
  • CR+LF: Microsoft Windows, DEC TOPS-10, RT-11 and most other early non-Unix and non-IBM OSes, CP/M, MP/M, DOS (MS-DOS, PC-DOS, etc.), Atari TOS, OS/2, Symbian OS, Palm OS
  • LF+CR: Acorn BBC and RISC OS spooled text output.
  • CR:    Commodore 8-bit machines, Acorn BBC, TRS-80, Apple II family, Mac OS up to version 9 and OS-9
  • RS:    QNX pre-POSIX implementation.
• EBCDIC systems—mainly IBM mainframe systems, including z/OS (OS/390) and i5/OS (OS/400)—use NEL (Next Line, 0x15) as the newline character. Note that EBCDIC also has control characters called CR and LF, but the numerical value of LF (0x25) differs from the one used by ASCII (0x0A). Additionally, there are some EBCDIC variants that also use NEL but assign a different numeric code to the character.
• Operating systems for the CDC 6000 series defined a newline as two or more zero-valued six-bit characters at the end of a 60-bit word. Some configurations also defined a zero-valued character as a colon character, with the result that multiple colons could be interpreted as a newline depending on position.
• ZX80 and ZX81, home computers from Sinclair Research Ltd used a specific non-ASCII character set with code NEWLINE (0x76, 118 decimal) as the newline character.
• OpenVMS uses a record-based file system, which stores text files as one record per line. In most file formats, no line terminators are actually stored, but the Record Management Services facility can transparently add a terminator to each line when it is retrieved by an application. The records themselves could contain the same line terminator characters, which could either be considered a feature or a nuisance depending on the application.
• Fixed line length was used by some early mainframe operating systems. In such a system, an implicit end-of-line was assumed every 80 characters, for example. No newline character was stored. If a file was imported from the outside world, lines shorter than the line length had to be padded with spaces, while lines longer than the line length had to be truncated. This mimicked the use of punched cards, on which each line was stored on a separate card, usually with 80 columns on each card. Many of these systems added an carriage control character to the start of the next record, this could indicate if the next record was a continuation of the line started by the previous record, or a new line, or should overprint the previous line (similar to a CR). Often this was a normal printing character such as '#' that thus could not be used as the first character in a line. Some early line printers interpreted these characters directly in the records sent to them.

Most textual Internet protocols (including HTTP, SMTP, FTP, IRC and many others) mandate the use of ASCII CR+LF (0x0D 0x0A) on the protocol level, but recommend that tolerant applications recognize lone LF as well. In practice, there are many applications that erroneously use the C newline character '\n' instead (see section Newline in programming languages below). This leads to problems when trying to communicate with systems adhering to a stricter interpretation of the standards; one such system is the qmail MTA that actively refuses to accept messages from systems that send bare LF instead of the required CR+LF.^[2]

FTP has a feature to transform newlines between CR+LF and LF only when transferring text files. This must not be used on binary files. Usually binary files and text files are recognised by checking their filename extension.

Unicode[link]

The Unicode standard defines a large number of characters that conforming applications should recognize as line terminators:^[3]

 LF:    Line Feed, U+000A
 VT:    Vertical Tab, U+000B
 FF:    Form Feed, U+000C
 CR:    Carriage Return, U+000D
 CR+LF: CR (U+000D) followed by LF (U+000A)
 NEL:   Next Line, U+0085
 LS:    Line Separator, U+2028
 PS:    Paragraph Separator, U+2029

This may seem overly complicated compared to an approach such as converting all line terminators to a single character, for example LF. However, Unicode was designed to preserve all information when converting a text file from any existing encoding to Unicode and back. Therefore, Unicode should contain characters included in existing encodings. NEL is included in ISO-8859-1^{[citation needed]} and EBCDIC (0x15). The approach taken in the Unicode standard allows round-trip transformation to be information-preserving while still enabling applications to recognize all possible types of line terminators.

Recognizing and using the newline codes greater than 0x7F is not often done. They are multiple bytes in UTF-8 and the code for NEL has been used as the ellipsis ('…') character in Windows-1252. For instance:

• YAML^[4] no longer recognizes them as special in order to be compatible with JSON.
• ECMAScript^[5] accepts LS and PS as line breaks, but considers U+0085 (NEL) white space, not a line break.
• Microsoft Windows 2000 does not treat any of NEL, LS or PS as line-break in the default text editor Notepad
• In Linux, a popular editor "gedit" treats LS and PS as newlines but does not for NEL.

History[link]

ASCII was developed simultaneously by the ISO and the ASA, the predecessor organization to ANSI. During the period of 1963–1968, the ISO draft standards supported the use of either CR+LF or LF alone as a newline, while the ASA drafts supported only CR+LF.

The sequence CR+LF was in common use on many early computer systems that had adopted Teletype machines, typically a Teletype Model 33 ASR, as a console device, because this sequence was required to position those printers at the start of a new line. On these systems, text was often routinely composed to be compatible with these printers, since the concept of device drivers hiding such hardware details from the application was not yet well developed; applications had to talk directly to the Teletype machine and follow its conventions.

Most minicomputer systems from DEC used this convention. CP/M used it as well, to print on the same terminals that minicomputers used. From there MS-DOS (1981) adopted CP/M's CR+LF in order to be compatible, and this convention was inherited by Microsoft's later Windows operating system.

The separation of the two functions concealed the fact that the print head could not return from the far right to the beginning of the next line in one-character time. That is why the sequence was always sent with the CR first. In fact, it was often necessary to send extra characters (extraneous CRs or NULs, which are ignored) to give the print head time to move to the left margin. Even many early video displays required multiple character times to scroll the display.

The Multics operating system began development in 1964 and used LF alone as its newline. Multics used a device driver to translate this character to whatever sequence a printer needed (including extra padding characters), and the single byte was much more convenient for programming. The seemingly more obvious choice of CR was not used, as a plain CR provided the useful function of overprinting one line with another, and thus it was useful to not translate it. Unix followed the Multics practice, and later systems followed Unix.

In programming languages[link]

To facilitate the creation of portable programs, programming languages provide some abstractions to deal with the different types of newline sequences used in different environments.

The C programming language provides the escape sequences '\n' (newline) and '\r' (carriage return). However, these are not required to be equivalent to the ASCII LF and CR control characters. The C standard only guarantees two things:

1. Each of these escape sequences maps to a unique implementation-defined number that can be stored in a single char value.
2. When writing a file in text mode, '\n' is transparently translated to the native newline sequence used by the system, which may be longer than one character. When reading in text mode, the native newline sequence is translated back to '\n'. In binary mode, no translation is performed, and the internal representation produced by '\n' is output directly.

On Unix platforms, where C originated, the native newline sequence is ASCII LF (0x0A), so '\n' was simply defined to be that value. With the internal and external representation being identical, the translation performed in text mode is a no-op, and text mode and binary mode behave the same. This has caused many programmers who developed their software on Unix systems simply to ignore the distinction completely, resulting in code that is not portable to different platforms.

The C library function fgets() is best avoided in binary mode because any file not written with the UNIX newline convention will be misread. Also, in text mode, any file not written with the system's native newline sequence (such as a file created on a UNIX system, then copied to a Windows system) will be misread as well.

Another common problem is the use of '\n' when communicating using an Internet protocol that mandates the use of ASCII CR+LF for ending lines. Writing '\n' to a text mode stream works correctly on Windows systems, but produces only LF on Unix, and something completely different on more exotic systems. Using "\r\n" in binary mode is slightly better.

Many languages, such as C++, Perl,^[6] and Haskell provide the same interpretation of '\n' as C.

Java, PHP,^[7] and Python^[8] provide the '\r\n' sequence (for ASCII CR+LF). In contrast to C, these are guaranteed to represent the values U+000A and U+000D, respectively.

The Java I/O libraries do not transparently translate these into platform-dependent newline sequences on input or output. Instead, they provide functions for writing a full line that automatically add the native newline sequence, and functions for reading lines that accept any of CR, LF, or CR+LF as a line terminator (see BufferedReader.readLine()). The System.getProperty() method can be used to retrieve the underlying line separator.

Example:

  String eol = System.getProperty( "line.separator" );
  String lineColor = "Color: Red" + eol;

Python permits "Universal Newline Support" when opening a file for reading, when importing modules, and when executing a file.^[9]

Some languages have created special variables, constants, and subroutines to facilitate newlines during program execution.

Common problems[link]

The different newline conventions often cause text files that have been transferred between systems of different types to be displayed incorrectly. For example, files originating on Unix or Apple Macintosh systems may appear as a single long line on some Windows programs. Conversely, when viewing a file originating from a Windows computer on a Unix system, the extra CR may be displayed as ^M at the end of each line or as a second line break.

The problem can be hard to spot if some programs handle the foreign newlines properly while others do not. For example, a compiler may fail with obscure syntax errors even though the source file looks correct when displayed on the console or in an editor. On a Unix system, the command cat -v myfile.txt will send the file to stdout (normally the terminal) and make the ^M visible, which can be useful for debugging. Modern text editors generally recognize all flavours of CR / LF newlines and allow the user to convert between the different standards. Web browsers are usually also capable of displaying text files and websites which use different types of newlines.

The File Transfer Protocol can automatically convert newlines in files being transferred between systems with different newline representations when the transfer is done in "ASCII mode". However, transferring binary files in this mode usually has disastrous results: Any occurrence of the newline byte sequence—which does not have line terminator semantics in this context, but is just part of a normal sequence of bytes—will be translated to whatever newline representation the other system uses, effectively corrupting the file. FTP clients often employ some heuristics (for example, inspection of filename extensions) to automatically select either binary or ASCII mode, but in the end it is up to the user to make sure his or her files are transferred in the correct mode. If there is any doubt as to the correct mode, binary mode should be used, as then no files will be altered by FTP, though they may display incorrectly.

Conversion utilities[link]

This article contains instructions, advice, or how-to content. The purpose of Wikipedia is to present facts, not to train. Please help improve this article either by rewriting the how-to content or by moving it to Wikiversity or Wikibooks. (June 2010)

Text editors are often used for converting a text file between different newline formats; most modern editors can read and write files using at least the different ASCII CR/LF conventions. The standard Windows editor Notepad is not one of them (although Wordpad and the MS-DOS Editor are).

Editors are often unsuitable for converting larger files. For larger files (on Windows NT/2000/XP) the following command is often used:

TYPE unix_file | FIND "" /V > dos_file

On many Unix systems, the dos2unix (sometimes named fromdos or d2u) and unix2dos (sometimes named todos or u2d) utilities are used to translate between ASCII CR+LF (DOS/Windows) and LF (Unix) newlines. Different versions of these commands vary slightly in their syntax. However, the tr command is available on virtually every Unix-like system and is used to perform arbitrary replacement operations on single characters. A DOS/Windows text file can be converted to Unix format by simply removing all ASCII CR characters with

tr -d '\r' < inputfile > outputfile

or, if the text has only CR newlines, by converting all CR newlines to LF with

tr '\r' '\n' < inputfile > outputfile

The same tasks are sometimes performed with awk, sed, Tr_(Unix) or in Perl if the platform has a Perl interpreter:

awk '{sub("$","\r\n"); printf("%s",$0);}' inputfile > outputfile  # UNIX to DOS  (adding CRs on Linux and BSD based OS that haven't GNU extensions)
awk '{gsub("\r",""); print;}' inputfile > outputfile              # DOS to UNIX  (removing CRs on Linux and BSD based OS that haven't GNU extensions)
sed -e 's/$/\r/' inputfile > outputfile              # UNIX to DOS  (adding CRs on Linux based OS that use GNU extensions)
sed -e 's/\r$//' inputfile > outputfile              # DOS  to UNIX (removing CRs on Linux based OS that use GNU extensions)
cat inputfile | tr -d "\r" > outputfile              # DOS  to UNIX (removing CRs using tr(1). Not Unicode compliant.)
perl -pe 's/\r?\n|\r/\r\n/g' inputfile > outputfile  # Convert to DOS
perl -pe 's/\r?\n|\r/\n/g'   inputfile > outputfile  # Convert to UNIX
perl -pe 's/\r?\n|\r/\r/g'   inputfile > outputfile  # Convert to old Mac

To identify what type of line breaks a text file contains, the file command can be used. Moreover, the editor Vim can be convenient to make a file compatible with the Windows notepad text editor. For example:

[prompt] > file myfile.txt
myfile.txt: ASCII English text
[prompt] > vim myfile.txt
  within vim :set fileformat=dos
             :wq
[prompt] > file myfile.txt
myfile.txt: ASCII English text, with CRLF line terminators

The following grep commands echo the filename (in this case myfile.txt) to the command line if the file is of the specified style:

grep -PL $'\r\n' myfile.txt # show UNIX style file (LF terminated)
grep -Pl $'\r\n' myfile.txt # show DOS style file (CRLF terminated)

For Debian-based systems, these commands are used:

egrep -L $'\r\n' myfile.txt # show UNIX style file (LF terminated)
egrep -l $'\r\n' myfile.txt # show DOS style file (CRLF terminated)

The above grep commands work under Unix systems or in Cygwin under Windows. Note that these commands make some assumptions about the kinds of files that exist on the system (specifically it's assuming only UNIX and DOS-style files—no Mac OS 9-style files).

This technique is often combined with find to list files recursively. For instance, the following command checks all "regular files" (e.g. it will exclude directories, symbolic links, etc.) to find all UNIX-style files in a directory tree, starting from the current directory (.), and saves the results in file unix_files.txt, overwriting it if the file already exists:

find . -type f -exec grep -PL '\r\n' {} \; > unix_files.txt

This example will find C files and convert them to LF style line endings:

find -name '*.[ch]' -exec fromdos {} \;

The file command also detects the type of EOL used:

file myfile.txt
> myfile.txt: ASCII text, with CRLF line terminators

Other tools permit the user to visualise the EOL characters:

od -a myfile.txt
cat -e myfile.txt
hexdump -c myfile.txt

dos2unix, unix2dos, mac2unix, unix2mac, mac2dos, dos2mac can perform conversions. The flip^[10] command is often used.

See also[link]

• ASA carriage control characters
• C0 and C1 control codes
• Page break
• Line starve

References[link]

External links[link]

• The Unicode reference, see paragraph 5.8 in Chapter 5 of the Unicode 4.0 standard (PDF)
• "The End-of-Line Story"
• The [NEL] Newline Character
• The End of Line Puzzle
• Tofrodos - software for Unix that converts to and from DOS newlines
• ToFroWin: a Windows shell extension that is able to convert multiple files from DOS to UNIX (and vice-versa) line endings right from the context menu.
• "Understanding Newlines" on O'Reilly-Net - an article by Xavier Noria.

Shane Dawson
Dawson at the Streamy Awards in 2010
Born	Shane Lee Yaw (1988-07-19) July 19, 1988 (age 23) Long Beach, California, U.S.
Occupation	YouTube video maker (actor, comedian)
Years active	2008–present
Known for	Sketch comedy, vlogging
Website
www.shanedawsontv.com

Shane Dawson (born Shane Yaw; July 19, 1988)^[1][2][3] is an American YouTube actor, comedian, and musician. Dawson is known for making comedy videos featuring many recurring characters (such as Shananay, Ned the Nerd, S. Deezy, Mom, and Aunt Hilda), impersonations (such as Paris Hilton, Miley Cyrus and Sarah Palin), and spoofs of popular music videos and television shows. As of September 2011 his main YouTube channel is the fifth most subscribed channel of all time, behind Ray William Johnson, Nigahiga, Smosh, and Machinima.com.^[4][5][6] Dawson has since expanded on YouTube by adding his second channel (twelfth most subscribed)^[4] where he posts video blogs and the series "Ask Shane", which moved to his main channel February 26, 2011.^[7]

Dawson's career began when he and several friends would turn in videos instead of homework in high school. Dawson's first videos on YouTube were old assignments that he turned in during high school.^[8][9]

In November 2009, Dawson was featured on Attack of the Show!^[10] In 2010, Forbes magazine named him their 25th most famous web celebrity.^[3]

Dawson's debut mainstream single (third overall), SUPERLUV! was released on March 31, 2012.^[11]

Personal life[link]

Dawson grew up in Long Beach, California, where he attended Lakewood High School.^[12] Dawson has revealed in a video, that as a teenager he was over-weight and would get bullied a lot, as well as being beaten by his alcoholic father, who then abandoned the family. He has since lost 150 pounds. Shane has three dogs, Miley, Charlie, and Chocolate as well as two cats, Muffins and Snoop. They often appear in his videos. He used to work in Jenny Craig, Inc. along with his mother and brother, but was fired after he uploaded a video of himself pole dancing in the building he worked in. His mother, brother and about 6 other coworkers who appeared in the video also got fired after the company saw the video.^[13] In a video he said he is a virgin, and plans to stay one until he is married as he believes strongly in sex after marriage.^[14] Shane Dawson revealed in a video that he and an unknown female broke up from their relationship, which lasted about a year.^[15] He decided to not release the female's identity in order to preserve her from getting negative criticism. In March 2012, Dawson stated that he was in a relationship with fellow YouTuber, Lisa Schwartz.^[16]

Dawson currently resides in Sherman Oaks, California.^[17]

YouTube channels[link]

Dawson posts new videos on his main channel, ShaneDawsonTV, every Saturday and video blogs on his second channel, ShaneDawsonTV2, throughout the week.^[18] Every Monday, posted on his second channel, he also has an "Ask Shane" webseries where he answers questions from his viewers. This series is similar to a previous web series, "Viewer Orgy Party", which currently only airs approximately once a month. His third YouTube channel, Shane, is where he posts unedited videos directly from his iPhone. He began using this channel in May, 2010. Starting in 2012 Shane had announced he would be making daily blogs (video blog) on his iPhone channel. He has also begun a new series called "Shane and Friends" on his main channel which he does once every month. This series includes him giving advice and talking as basically all his characters. Shane often collaborates with other YouTubers or appears in their videos, such as BrittaniLouiseTaylor, TheFineBros, JoeNationTV, and ijustine.

In August 2010, he announced that he was going to write a television pilot and post it on his main channel, featuring himself and his characters from previous videos, about him in high school.

Television projects[link]

On August 11, 2010, Dawson announced that he was in the making of a 30-minute pilot which he will call SD High. Previously, the funding he needed for the pilot was provided by digital media group Take180 after he helped them out with acting in their own videos.^[19] The pilot is based on two previous videos which Dawson uploaded to his main channel in Summer 2010. In his previous videos, the story centers around a teenage boy in school, and his interactions with the other characters. The pilot was due to be released towards the end of September 2010 on his main YouTube Channel, however Dawson later announced that he had been contacted by a television studio to produce the pilot for their TV channel(s).^[20] According to Dawson, there is some uncertainty involving the pilot, however it may be a TV show in the future.^[21] On March 26, 2011, Dawson uploaded a video to YouTube explaining to his audience that he's working with Happy Madison Productions, Sony Pictures, and some other YouTubers including TheFineBros and BrittaniLouiseTaylor to create the television show.^[22] The video contains an explanation from Dawson about what he's working on, and a 'mock trailer', made up of clips from previous episodes on his YouTube channel, for the show.

In January 2012, Dawson stated in a video that he was now working on a new television show, which would be semi-based on his life working at a Weight Loss center. He stated that he would be pitching the show soon, and that he was "really excited" for it, and stated the show was "kind of like Arrested Development, but - not."^[23] Recently, Shane, on May 16, 2012, announced in his daily vlog that he was working on a professional horror-comedy movie. "I want to write something like a teen comedy but like scary and fun," said Dawson in the vlog, Day 96.

Music projects[link]

In 2012, Dawson revealed in his Vlogs that he was working on a music project. In March 2012, Dawson revealed that his debut mainstream single, SUPERLUV! would be released that month. The song was released on March 31, 2012 on iTunes, with an accompanying music video debuting on his YouTube channel on the same day. The song managed to chart at 87 in Ireland, 16 on the UK Indie Chart and reached the 28th spot on the US iTunes Pop Chart.

On May 8, 2012, Dawson revealed in a video that he has begun working on his next original song, which is tentatively titled The Vacation Song. He previewed about 10 seconds of the "rough edit" of the song, and stated that he was going to change the mood of the song, saying, "Right now, it's a little too happy, because it's a break up song. I want it to be more like Kelly Clarkson's Since You've Been Gone." He stated that the song would "hopefully" be released by the beginning of June 2012.^[24]

Major productions[link]

• Hot Teens Gone Wild on Degrassi! Part 1 - November 21, 2009 (11-minute long special)
• Hot Teens Go Wild on Degrassi! Part 2 - March 6, 2010 (12-minute long special)
• SD High: School Dance Disaster - July 3, 2010 (SD High Episode 1) (8-minute long special)
• SD High: High School Drama - July 31, 2010 (SD High Episode 2) (9-minute long special)
• Haunted House Party - October 30, 2010 (Interactive Halloween special)
• Shane Dawson's Love Story - December 18, 2010 (10-minute long Christmas special)
• SD High: Teens Gone Wild - March 26, 2011 (SD High Episode 3) (7-minute long special)
• Final Destination: The Game - July 2, 2011 (Interactive special based on the Final Destination film series )
• Friends 4Ever - October 29, 2011 (22-minute long Halloween short film)
• How Shananay Stole Christmas - December 17, 2011 (15-minute long Christmas special)

Dawson will play a character named Binder in the upcoming feature-length horror film, Smiley (directed by YouTuber Michael Gallagher and produced by Level 10 Films) which has finished filming and is currently in post-production. It will be released in theaters and DVD in 2012.^[25]

Discography[link]

Singles[link]

Note: These are only songs Shane has released officially to iTunes as singles. He has also released a set of ringtones on iTunes, also available to download as tracks, and he releases all his parodies free on a media sharing website.

Awards and nominations[link]

Dawson has been nominated for various awards.^[26] On August 9, 2010, Dawson won the award for Choice Web Star at the 2010 Teen Choice Awards. Although the category was not featured at the awards show, Dawson stated in a video that he posted to YouTube the next day that "It was just great to be nominated and at the show itself". The nominees for that category included fellow YouTubers Justine Ezarik, Charles Trippy, Lucas Cruikshank, best known for his Fred character, and singer Greyson Chance. Dawson was nominated for Choice Web Star in the 2011 Teen Choice Awards, but lost to Rebecca Black.

References[link]

External links[link]

• Shane Dawson at the Internet Movie Database
• Official Website
• ShaneDawsonTV, Shane Dawson's YouTube channel