Kaho Naa Pyaar Hai
File:KahoNaaPyaarHai.jpg Theatrical release poster
Directed by	Rakesh Roshan
Produced by	Rakesh Roshan
Screenplay by	Ravi Kapoor Honey Irani
Story by	Rakesh Roshan
Starring	Hrithik Roshan Ameesha Patel
Music by	Rajesh Roshan
Cinematography	Kabir Lal
Editing by	Sanjay Verma
Distributed by	Filmkraft Productions (I) Pvt. Ltd.
Release date(s)	January 14, 2000
Running time	173 mins
Country	India
Language	Hindi
Budget	18 crore (US$3.59 million)
Box office	61.5 crore (US$12.27 million)[1]

Kaho Naa... Pyaar Hai (Hindi: कहो ना प्यार है - translation: Say...you Love me) is a 2000 Bollywood film directed by Rakesh Roshan. The film marks the debut of his son Hrithik Roshan and also the debut of Ameesha Patel. Hrithik plays a double role in the film, and became an overnight superstar in India.

Kaho Naa... Pyaar Hai was the biggest Bollywood commercial success of 2000 and won many awards, including eight Filmfare Awards. Rakesh Roshan collected his first ever Filmfare award, which he won as producer and as director. Hrithik Roshan became the only actor to win both, the Filmfare Award for Best Debut along with the Filmfare Award for Best Actor for the same film. He was praised by both the young and old for his acting and dancing abilities.^[2] Following on the success of Kaho Naa... Pyaar Hai, the father and son team would go on to make several more hits including Koi... Mil Gaya and Krrish.^[3]

Plot[link]

Rohit(Hrithik Roshan) and his kid brother Amit are orphans living with a Christian couple(Farida Jalal) and (Satish Shah). Rohit is an aspiring singer who works in a car showroom run by Malik(Dalip Tahil). One day he meets Sonia Saxena(Ameesha Patel), daughter of Mr.Saxena(Anupam Kher) when he goes to deliver a car to her home as her birthday present. Unknown to everybody, Saxena and Malik are running a drug cartel with help of two police officers(Mohnish Behl) and Ashish Vidyarthi). Saxena is called as "Sir Ji"(Sir) by the trio.

They see each other later that night when Sonia and her friends are having a party on the beach. After Rohit sings for her, Atul, Sonia's friend, invites him on a cruise to perform. With a turn of unpredictable events, Rohit & Sonia fall for each other. This is objected to by Saxena, who demands Malik to sack him. However, later he softens up a bit and challenges Rohit to do something big so that he can win back his love. Determined to prove himself, Rohit and his friends attempt to procure a record deal for him. Rohit eventually becomes famous, and prepares to put on a huge concert.

On the evening of the show, Rohit goes to pick-up his younger brother Amit from school to take him up to show. He witnesses the corrupt policemen and Malik shooting down the Commissioner(Ram Mohan) who has found out about their drug dealings. The policemen discover Rohit's presence and shoot at him. Rohit is chased by the policemen and falls into a river when his bike slips on a bridge. Rohit, who didn't know how to swim, drowns. Sonia learns about this, but everyone including her thinks that he died in an accident.

Sonia goes into depression so her father sends her to New Zealand to her cousin Neeta(Tanaaz Currim) to get over Rohit. When she reaches there she meets Raj Chopra(also Hrithik Roshan) in a club. He looks exactly like Rohit and is also a good singer. Raj falls for Sonia, but she cannot get over her feelings and his face only reminds her of Rohit. On learning her story, Raj decides to follow her back to India. But on reaching India, one of the corrupt officers spots them and opens fire on Raj. When both Raj & Sonia escape the firing, Raj realizes that somebody is mistaking him for Rohit. With this revelation, he and Sonia realize the truth.

Raj is sheltered by Rohit's well wishers. Then, he unexpectedly learns that Amit witnessed Rohit's murder. Raj decides to set the trap for nabbing the killers, posing as Rohit. Only Sonia & Rohit's acquaintances know the truth. The villains panick on learning that "Rohit" is alive. Malik and the officers turn up incognito at the concert where Raj is performing. Here, Saxena learns the truth from Sonia. He warns Malik. But when Raj tells details about the day that only Rohit would have known, Malik assumes that Saxena is playing some double game.

Malik kidnaps Sonia. Rohit succeeds in killing the officers and rescuing Sonia, but she is taken aback by the fact that Malik is a villain. Just when Malik is about to tell the truth about Saxena as well, Saxena shoots him, feigning anger. Here, Amit tells Raj that the villains were talking to someone named Sirji over the phone. Raj finds Sirji's number in Malik's cell and makes a call. When Saxena's phone goes off, he understands everything. On being confronted, Saxena confesses up everything in front of Sonia and Raj.

After everything is settled, Sonia and Raj go back to New Zealand, taking Amit with them.

Cast[link]

• Hrithik Roshan as Rohit / Raj Chopra
• Ameesha Patel as Sonia Saxena
• Anupam Kher as Mr. Saxena / Sirjee
• Dalip Tahil as Shakti Malik
• Mohnish Behl as Inspector Kadam
• Ashish Vidyarthi as Inspector Shinde
• Satish Shah as Anthony Uncle (Rohit's landlord)
• Farida Jalal as Lily Aunty (Rohit's landlady)
• Asha Patel as Mrs. Chopra (Raj's mother)
• Tanaaz Currim as Neeta
• Vrajesh Hirjee as Tony (Rohit's Friend)
• Abhishek Sharma as Amit
• Johnny Lever as Inspector Parab
• Kamya Punjabi as Girl on Cruise ship

Production[link]

The role of Sonia was first cast with Kareena Kapoor who walked out of the picture a few days after shooting had started. She was then replaced with newcomer Ameesha Patel who became a star overnight when the film became a blockbuster.^[4]

The ship scenes were filmed aboard the Star Flyer.^[5] The island scenes were filmed in Krabi, Thailand in the area near James Bond Island.^[6]

Reception[link]

Critical Reception[link]

Kaho Naa... Pyaar Hai received mixed reviews from critics, although the performance of Hrithik Roshan was well praised and the music received positive reviews.^[7] Many critics noted the storyline was clichéd. Planet Bollywood's Alok Kumar said "I'm telling you all to go see KNPH, a movie with which I had low expectations, The film ended up being very entertaining".^[8] Ajay Chaturvedi of Apunkachoice.com said "The film suffers from a bad script". But he praised the performance and dancing of Hritik Roshan saying "The highlight of the film is Hritik Roshan who has good screen presence, He has acted quite well considering that this is his debut film and he is a brilliant dancer". He also praised the music saying "it is a big plus with "Na Tum Jano Na Hum" and "Ek Pal Ka Jeena" being the pick of the lot".^[9]

Box office[link]

The movie initially had a slow start but picked up due to positive word of mouth to an overwhelming response and by the end of its run at the box office it had grossed Rs 61 crores and was declared a blockbuster. It was also the highest grossing Bollywood film of 2000.^[10] When adjusted for inflation it is the 11th highest grossing Bollywood film of all time,^[11] and the sixth highest grossing film from the 2000s.^[12]

Soundtrack[link]

The film's music was composed by Rajesh Roshan. Lyrics were by Ibrahim Ashq, Saawan Kumar Tak and Vijay Akela. The album became the best selling Bollywood soundtrack of the year.^[13]

Awards[link]

Filmfare Awards[link]

The film was nominated for many Filmfare Awards.^[14] It ultimately won eight of them.^[15]

• Best Movie - Rakesh Roshan
• Best Director - Rakesh Roshan
• Best Actor - Hrithik Roshan
• Best Debut - Hrithik Roshan
• Best Choreography - Farah Khan
• Best Music Director - Rajesh Roshan
• Best Male Playback - Lucky Ali for "Na Tum Jaano"
• Best Screenplay - Ravi Kapoor and Honey Irani
• Nominated for Best Male Playback - Lucky Ali for "Ek Pal Ka Jeena"
• Nominated for Best Lyricist - Ibrahim Ashq for "Na Tum Jaano"

References[link]

External links[link]

• Kaho Naa... Pyaar Hai at the Internet Movie Database

v t e Bollywood (Hindi cinema) Directors · Actors · Playback singers · Music Directors · Songs · Bibliography Hindi films A–Z—Highest-grossing Films by year: 1930s · 1940 · 1941 · 1942 · 1943 · 1944 · 1945 · 1946 · 1947 · 1948 · 1949 · 1950 · 1951 · 1952 · 1953 · 1954 · 1955 · 1956 · 1957 · 1958 · 1959 · 1960 · 1961 · 1962 · 1963 · 1964 · 1965 · 1966 · 1967 · 1968 · 1969 · 1970 · 1971 · 1972 · 1973 · 1974 · 1975 · 1976 · 1977 · 1978 · 1979 · 1980 · 1981 · 1982 · 1983 · 1984 · 1985 · 1986 · 1987 · 1988 · 1989 · 1990 · 1991 · 1992 · 1993 · 1994 · 1995 · 1996 · 1997 · 1998 · 1999 · 2000 · 2001 · 2002 · 2003 · 2004 · 2005 · 2006 · 2007 · 2008 · 2009 · 2010 · 2011 · 2012

Look up Kaho in Wiktionary, the free dictionary.

Kaho may refer to:

Places[link]

• Kaho, Burkina Faso, a village in southern Burkina Faso
• Kaho District, Fukuoka (嘉穂郡), a district in Fukuoka, Japan
• Kaho, Fukuoka (嘉穂町), a town located in Kaho District
• 4284 Kaho, a main-belt asteroid

Japanese given name[link]

Kaho can be a feminine Japanese name written in different kanji characters and having different meanings:

• 花歩, "flower, walk/progress"
• 花穂, "flower, ear (of grain)"
• 果歩, "fruit, walk/progress"
• 香穂, "incense, ear (of grain)"
• 夏帆, "summer, sail"
• 夏穂, "summer, ear (of grain)"
• 嘉穂, "praise, ear (of grain)"
• 加保, "add, protect"
• 歌歩, "song, walk/progress"

The name can also be written in hiragana or katakana.

People[link]

• Kaho (夏帆), a Japanese actress and fashion model
• Kaho Kōda (夏穂), a Japanese voice actress
• Kaho Minami (果歩), a Japanese actress
• Kaho Miyasaka (香帆), a Japanese manga artist
• Kaho Shimada (歌穂), a Japanese singer and musical theater actress

Fictional characters[link]

• Kaho Mizuki (歌帆), a character in the anime and manga series Cardcaptor Sakura
• Kaho Serizawa (香穂), the heroine of the Japanese visual novel Hourglass of Summer

See also[link]

• Kaho Naa... Pyaar Hai, a 2000 Bollywood blockbuster movie
• Kahoʻolawe, the smallest of the eight main volcanic islands in the Hawaiian Islands

This disambiguation page lists articles associated with the same title. If an internal link led you here, you may wish to change the link to point directly to the intended article.

NAA can refer to:

• 1-naphthaleneacetic acid - synthetic auxin (organic compound and plant hormone)
• N-Acetylaspartate, a neurochemical often imaged in magnetic resonance spectroscopy
• NAA, a radio station in Cutler, Maine, operated by the United States Navy
• Naa Govindasamy
• Narita International Airport Corporation
• Narrabri Airport in IATA code NAA
• National Academy of Arbitrators
• National Academy of Arts of Bulgaria
• National Aeronautic Association
• National Airworthiness Authority
• National Anthropological Archives
• National Archives of Australia
• National Assessment Agency
• National Association of Actors, a Mexican television and motion picture performers union.
• National Auctioneers Association
• National Aviation Academy
• National Aviation Authority
• Neutron activation analysis
• Newspaper Association of America, a trade association
• Nigerian Accounting Association
• No abstract available bias
• North American Airlines
• North American Arms, an arms company
• North American Aviation

This disambiguation page lists articles associated with the same title. If an internal link led you here, you may wish to change the link to point directly to the intended article.

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.

HAI may stand for:

• List of IOC country codes for Haiti
• Hellenic Aerospace Industry
• Helicopter Association International
• Hot air intake, a system in carburated engines to prevent carburator's throat from freezing by taking warm air to inlet air from exhaust manifold.
• Hospital-acquired infection
• Human Awareness Institute, an organization offering workshops on intimate relationships and sexuality
• Humanist Association of Ireland
• International Air Transport Association airport code for Three Rivers Municipal Airport
• Home Automation, Inc., a global home automation technology developer and manufacturer

Hai may refer to:

• Hai (Brodivskyi Raion), a village in Ukraine, Lviv Oblast
• Hai (Cantonese profanity)
• Hai, a 2002 film by Telugu director E. V. V. Satyanarayana
• Hai (midget submarine), a German midget submarine from World War II
• Hai (keelboat), a sloop-rigged one-design yacht class
• Hai (symbol) or chai, letters of the Hebrew alphabet
• Hai District, Tanzania
• Hai Gaon (939 - 1038), a rabbi of the 10th and 11th centuries
• Hai River, China
• A word for "is" or "to live" in Hebrew. Written as "חַי". See Chai (symbol)

See also[link]

• HI (disambiguation)
• Hainan
• Ai (disambiguation)

This disambiguation page lists articles associated with the same title. If an internal link led you here, you may wish to change the link to point directly to the intended article.