The internal format for strings is always UTF-16, it is not tied to the page encoding.
Let’s recall the kinds of quotes.
Strings can be enclosed within either single quotes, double quotes or backticks:
let single = 'single-quoted'; let double = "double-quoted"; let backticks = `backticks`;
Single and double quotes are essentially the same. Backticks, however, allow us to embed any expression into the string, by wrapping it in
Another advantage of using backticks is that they allow a string to span multiple lines:
Looks natural, right? But single or double quotes do not work this way.
If we use them and try to use multiple lines, there’ll be an error:
Single and double quotes come from ancient times of language creation when the need for multiline strings was not taken into account. Backticks appeared much later and thus are more versatile.
Backticks also allow us to specify a “template function” before the first backtick. The syntax is:
func`string`. The function
func is called automatically, receives the string and embedded expressions and can process them. This is called “tagged templates”. This feature makes it easier to implement custom templating, but is rarely used in practice. You can read more about it in the manual.
It is still possible to create multiline strings with single and double quotes by using a so-called “newline character”, written as
\n, which denotes a line break:
For example, these two lines are equal, just written differently:
There are other, less common “special” characters.
Here’s the full list:
||Carriage return: not used alone. Windows text files use a combination of two characters
||Backspace, Form Feed, Vertical Tab – kept for compatibility, not used nowadays.|
||Unicode character with the given hexadecimal unicode
||A unicode symbol with the hex code
||A unicode symbol with the given UTF-32 encoding. Some rare characters are encoded with two unicode symbols, taking 4 bytes. This way we can insert long codes.|
Examples with unicode:
All special characters start with a backslash character
\. It is also called an “escape character”.
We might also use it if we wanted to insert a quote into the string.
As you can see, we have to prepend the inner quote by the backslash
\', because otherwise it would indicate the string end.
Of course, only the quotes that are the same as the enclosing ones need to be escaped. So, as a more elegant solution, we could switch to double quotes or backticks instead:
Note that the backslash
\. You can clearly see that in
alert from the examples above.
But what if we need to show an actual backslash
\ within the string?
That’s possible, but we need to double it like
length property has the string length:
\n is a single “special” character, so the length is indeed
lengthis a property
People with a background in some other languages sometimes mistype by calling
str.length() instead of just
str.length. That doesn’t work.
Please note that
str.length is a numeric property, not a function. There is no need to add parenthesis after it.
To get a character at position
pos, use square brackets
[pos] or call the method str.charAt(pos). The first character starts from the zero position:
The square brackets are a modern way of getting a character, while
charAt exists mostly for historical reasons.
The only difference between them is that if no character is found,
charAt returns an empty string:
We can also iterate over characters using
Let’s try it to show that it doesn’t work:
The usual workaround is to create a whole new string and assign it to
str instead of the old one.
In the following sections we’ll see more examples of this.
Or, if we want a single character lowercased:
alert( 'Interface'.toLowerCase() ); // 'i'
There are multiple ways to look for a substring within a string.
The first method is str.indexOf(substr, pos).
It looks for the
str, starting from the given position
pos, and returns the position where the match was found or
-1 if nothing can be found.
The optional second parameter allows us to search starting from the given position.
For instance, the first occurrence of
"id" is at position
1. To look for the next occurrence, let’s start the search from position
If we’re interested in all occurrences, we can run
indexOf in a loop. Every new call is made with the position after the previous match:
The same algorithm can be layed out shorter:
There is also a similar method str.lastIndexOf(substr, position) that searches from the end of a string to its beginning.
It would list the occurrences in the reverse order.
There is a slight inconvenience with
indexOf in the
if test. We can’t put it in the
if like this:
alert in the example above doesn’t show because
0 (meaning that it found the match at the starting position). Right, but
0 to be
So, we should actually check for
-1, like this:
One of the old tricks used here is the bitwise NOT
~ operator. It converts the number to a 32-bit integer (removes the decimal part if exists) and then reverses all bits in its binary representation.
In practice, that means a simple thing: for 32-bit integers
As we can see,
~n is zero only if
n == -1 (that’s for any 32-bit signed integer
So, the test
if ( ~str.indexOf("...") ) is truthy only if the result of
indexOf is not
-1. In other words, when there is a match.
People use it to shorten
It is usually not recommended to use language features in a non-obvious way, but this particular trick is widely used in old code, so we should understand it.
if (~str.indexOf(...)) reads as “if found”.
To be precise though, as big numbers are truncated to 32 bits by
~ operator, there exist other numbers that give
0, the smallest is
~4294967295=0. That makes such check correct only if a string is not that long.
.includes method (see below).
The more modern method str.includes(substr, pos) returns
true/false depending on whether
It’s the right choice if we need to test for the match, but don’t need its position:
The optional second argument of
str.includes is the position to start searching from:
str.slice(start [, end])
Returns the part of the string from
startto (but not including)
If there is no second argument, then
slicegoes till the end of the string:
Negative values for
start/endare also possible. They mean the position is counted from the string end:
str.substring(start [, end])
Returns the part of the string between
This is almost the same as
slice, but it allows
startto be greater than
Negative arguments are (unlike slice) not supported, they are treated as
str.substr(start [, length])
Returns the part of the string from
start, with the given
In contrast with the previous methods, this one allows us to specify the
lengthinstead of the ending position:
The first argument may be negative, to count from the end:
Let’s recap these methods to avoid any confusion:
||negative values mean
All of them can do the job. Formally,
Of the other two variants,
slice is a little bit more flexible, it allows negative arguments and shorter to write. So, it’s enough to remember solely
slice of these three methods.
As we know from the chapter Comparisons, strings are compared character-by-character in alphabetical order.
Although, there are some oddities.
A lowercase letter is always greater than the uppercase:
Letters with diacritical marks are “out of order”:
This may lead to strange results if we sort these country names. Usually people would expect
Zealandto come after
Österreichin the list.
All strings are encoded using UTF-16. That is: each character has a corresponding numeric code. There are special methods that allow to get the character for the code and back.
Returns the code for the character at position
Creates a character by its numeric
We can also add unicode characters by their codes using
\ufollowed by the hex code:
Now let’s see the characters with codes
65..220 (the latin alphabet and a little bit extra) by making a string of them:
See? Capital characters go first, then a few special ones, then lowercase characters, and
Ö near the end of the output.
Now it becomes obvious why
a > Z.
The characters are compared by their numeric code. The greater code means that the character is greater. The code for
a (97) is greater than the code for
- All lowercase letters go after uppercase letters because their codes are greater.
- Some letters like
Östand apart from the main alphabet. Here, it’s code is greater than anything from
The “right” algorithm to do string comparisons is more complex than it may seem, because alphabets are different for different languages.
So, the browser needs to know the language to compare.
It provides a special method to compare strings in different languages, following their rules.
The call str.localeCompare(str2) returns an integer indicating whether
str is less, equal or greater than
str2 according to the language rules:
- Returns a negative number if
stris less than
- Returns a positive number if
stris greater than
0if they are equivalent.
This method actually has two additional arguments specified in the documentation, which allows it to specify the language (by default taken from the environment, letter order depends on the language) and setup additional rules like case sensitivity or should
"á" be treated as the same etc.
The section goes deeper into string internals. This knowledge will be useful for you if you plan to deal with emoji, rare mathematical or hieroglyphic characters or other rare symbols.
You can skip the section if you don’t plan to support them.
All frequently used characters have 2-byte codes. Letters in most european languages, numbers, and even most hieroglyphs, have a 2-byte representation.
But 2 bytes only allow 65536 combinations and that’s not enough for every possible symbol. So rare symbols are encoded with a pair of 2-byte characters called “a surrogate pair”.
The length of such symbols is
We actually have a single symbol in each of the strings above, but the
length shows a length of
str.codePointAt are few rare methods that deal with surrogate pairs right. They recently appeared in the language. Before them, there were only String.fromCharCode and str.charCodeAt. These methods are actually the same as
fromCodePoint/codePointAt, but don’t work with surrogate pairs.
Getting a symbol can be tricky, because surrogate pairs are treated as two characters:
Note that pieces of the surrogate pair have no meaning without each other. So the alerts in the example above actually display garbage.
Technically, surrogate pairs are also detectable by their codes: if a character has the code in the interval of
0xd800..0xdbff, then it is the first part of the surrogate pair. The next character (second part) must have the code in interval
0xdc00..0xdfff. These intervals are reserved exclusively for surrogate pairs by the standard.
In the case above:
You will find more ways to deal with surrogate pairs later in the chapter Iterables. There are probably special libraries for that too, but nothing famous enough to suggest here.
In many languages there are symbols that are composed of the base character with a mark above/under it.
For instance, the letter
a can be the base character for:
àáâäãåā. Most common “composite” character have their own code in the UTF-16 table. But not all of them, because there are too many possible combinations.
To support arbitrary compositions, UTF-16 allows us to use several unicode characters: the base character followed by one or many “mark” characters that “decorate” it.
For instance, if we have
S followed by the special “dot above” character (code
\u0307), it is shown as Ṡ.
If we need an additional mark above the letter (or below it) – no problem, just add the necessary mark character.
For instance, if we append a character “dot below” (code
\u0323), then we’ll have “S with dots above and below”:
This provides great flexibility, but also an interesting problem: two characters may visually look the same, but be represented with different unicode compositions.
To solve this, there exists a “unicode normalization” algorithm that brings each string to the single “normal” form.
It is implemented by str.normalize().
It’s funny that in our situation
normalize() actually brings together a sequence of 3 characters to one:
\u1e68 (S with two dots).
In reality, this is not always the case. The reason being that the symbol
Ṩ is “common enough”, so UTF-16 creators included it in the main table and gave it the code.
If you want to learn more about normalization rules and variants – they are described in the appendix of the Unicode standard: Unicode Normalization Forms, but for most practical purposes the information from this section is enough.
- There are 3 types of quotes. Backticks allow a string to span multiple lines and embed expressions
- We can use special characters like
\nand insert letters by their unicode using
- To get a character, use:
- To get a substring, use:
- To lowercase/uppercase a string, use:
- To look for a substring, use:
includes/startsWith/endsWithfor simple checks.
- To compare strings according to the language, use:
localeCompare, otherwise they are compared by character codes.
There are several other helpful methods in strings:
str.trim()– removes (“trims”) spaces from the beginning and end of the string.
str.repeat(n)– repeats the string
- …and more to be found in the manual.
Strings also have methods for doing search/replace with regular expressions. But that’s big topic, so it’s explained in a separate tutorial section Regular expressions.