Because you need to type:

The following is the output:

[nissanka@c83-250-108-126 ~]$ cat "$v8"
cat: The Holy Family's flight to Egypt : No such file or directory
[nissanka@c83-250-108-126 ~]$

Remember file names are case sensitve, and the file must be in your cwd. This is what happened when I did it:

I didn't write the file name; I just copied and pasted. I know very well about the case sensitivity aspects in Linux.

What shall I write for the words 'File Contents''?

It is a big file. I read it on an online newspaper and saved it. I have no problems to open it using the web browser.

[nissanka@c83-250-108-126 ~]$ pwd
/home/nissanka
[nissanka@c83-250-108-126 ~]$

Forget the first line, with the echo, that just created a file with the name same as yours with just any arbitary text content to show you how it works.

Something went wrong, cat reckons the file doesn't exist so you either spelt it wrong or that file is not in your home directory. When defining the variable you made sure there was no leading or trailing white space?

You said You tried So I guess you *don't* really have a file called "The Holy Family's flight to Egypt".

Or you do, and it exists in some other directory.

Who cares?

The point is:
1. A Linux file name can contain spaces (maybe unwise, but you can do it)
2. A Linux shell variable can also contain spaces (it's very common)
3. When Linux *EXPANDS* the shell variable, everything delimited by a space is BROKEN INTO A SEPARATE WORD
... But ...
4. You can KEEP your shell-variable-with-spaces as a SINGLE word ... by using quotes (").

That's the beginning and end of all I was trying to say.

Because "cat $v8" is expanded to "cat The Holy Family's flight to Egypt". the command cat will try to open several files named "The", and "Holy" ....
The correct way to avoid such mistake is protect the cat's argument with a double quote: