What is PHP?

PHP stands for PHP: HyperText Preprocessor, it is a server-side scripting language, and as the name goes, it is to create dynamic and interactive Websites for your visitors. Maybe you currently make your Websites in HTML? HTML alone cannot create dynamic Web pages, HTML is clearly defined as a static language, as it is always static and mainly is used for structuring (or styling, in some cases) a document (or a Web page, if you like).

What do we mean by server-side scripting?

You may already know, but HTML is a client-side language, so the browser translates the HTML code into "bytecode" that the computer can understand, and so the computer translates bytecode into what we can clearly understand, text, for example. Server-side scripting is a little different, a little bit more added to the story. As with PHP, server-side scripting languages have an interpreter inside a machine, that translates the code (in our case, PHP code) to HTML code (that the browser can understand), and then the same process will take place with the browser translating the HTML code to bytecode, and so forth. With server-side scripting languages, you don't need anything adding to your browser or computer, as the interpreter inside the machine that hosts the particular Website does most of the work.

What's the fuss with server-side scripting languages, then?

The thing that makes server-side scripting a must nowadays is because it can generate dynamic Web pages, but what do we mean by dynamic Web pages? Well, imagine you wanted to start a forum, and you used HTML. Okay, you used a form to submit the data and it is sent to your e-mail address, and you have to edit the static Web page every time you want a new post added. That, to me, would be the most annoying job of creating a Website. However, with PHP (or any other server-side scripting language, for that matter), can be completely automated, and you'd not have to edit your file even once! The thing that PHP does, is sends the form data to a different page, saves it in "pre-defined" variables (things that store a value), and using something called a "while loop" that continually loops all the posts saved in the Web page - and that's it! PHP stores the posts in a MySQL database (something that holds data, if you like, like member accounts, etc) and uses that as long-term memory.

But if we're talking about server-side scripting languages, what makes PHP different from the rest? Well, simply put, PHP is probably the best thing that has come into the server-side scripting genre. If you have heard about other scripting languages like Perl or ASP/ASP.NET, you'll come to find that they are extremely hard to learn from. Put it this way, the majority of Web developers that use ASP.NET, for example, are those who have come from a different programming background, like have known VBScript, or other languages that's in relation to ASP.NET, the same with Perl. The difference between PHP and the rest, is PHP is incredibly easy to learn, especially for the newbies towards this industry, and PHP has took several steps to ensure an easy introduction to those newbies to the world of programming. Let's do an example, lets see which is the easiest to understand, out of PHP, VBScript and Perl, by doing a simple "Hello World" program, that outputs text to a Web page:

PHP:

echo "This is some text that'll be shown in a Web page...";

VBScript/ASP.NET:

Response.Write("This is some text that'll be shown in a Web page...");

Perl:

#!/usr/bin/perl

print "content-type: text/html nn";

print "This is some text that'll be shown in a Web page...";

Okay, now I am not going to say things like "well, obviously PHP is the easiest to understand" - as obviously, we all have different preferences, but what I can say is, that they all do the same thing. Which seems the most logical to you? In my opinion, the two most logical ones for me is PHP and VBScript/(ASP.NET).

Now it's up to you which one you want to go ahead with, experiment which one is best for you, after all, we all have dfferent tastes.

Good luck!

Below are a few resources to get started with PHP:

# - w3schools.com

# - php.net

# - mysql.com

Making your web site easy for international visitors to understand is what website internationalization is all about. There are times when differences in vocabulary may crop up. This can even happen across different industries in the same country.

One of the ways you can help your readers is to start a Glossary.

In your glossary you can list industry specific words and all words you use commonly where others may not have the exact same understanding. If you explain a process in your communication, think of including verbs in your glossary.

The key to making your glossary work for you is to strive for accuracy, clarity, and ease of understanding.

Accuracy

In some cases a lack of accuracy can have devastating effects.

• In health issues.
• In reference to using machinery.

Clarity

A glossary's aim is to give a clear meaning to the words you use. Keep your explanations as clear as possible. If they only lead to further misunderstandings or do not answer the readers questions, you would be better off without one.

Ease Of Understanding

Keep your glossary very easy read and people will enjoy reading it. Pay attention to the general appearance of the glossary as a whole as well as the individual explanations.

An Added Value

After ready through a well done glossary, the reader may well come away feeling appreciative of the easy to read informative experience. It is a wonderful touch of thoughtfulness to your international visitors.

Non-native English speakers will greatly appreciate its value.

Prepares For Translation

A glossary is highly recommended in certain industries where specific vocabulary requires expert translations.

In some instances some people feel they can take a dictionary out and provide translations of key vocabulary in languages other than their mother-tongue. This can lead to further misunderstandings. A glossary well done is far better than taking on translation skills when you do not have them.

However, your glossary will be of significant value to a professional translator once you decide to offer multilingual services.

Glossaries are also appreciated in non-technical areas too. Cultural habits differ. People can use vocabulary differently. Glossaries provide insight into how you communicate and provide a base for cross-cultural dialogue.

Let's begin with a little history. Many years ago, when the web was up and coming and you needed to be on it, I paid someone to build a site for me. Afterwards, I could say, "Yeah, I have a site, go to -" and then I would name my site a feel a hit of pride. I'd also get satisfaction when my webmaster (if you could call him that; I don't know that I would in retrospect, but that's another story) occasionally forwarded me an email of an interested visitor. My satisfaction was short-lived, as you might imagine. I soon began to understand the power of the web and found the sad reality that my "webmaster" was getting all my emails from my website visitors to be annoying. I had him change this so that the emails came to me. He charged me a one-time fee for getting him to do this.

Okay, so these days it is not quite that bad, is it? Your webmaster or whoever is doing the "web thing" for you isn't charging you for every little service? Excuse me. I'll reserve my rant for another article, or possibly a blog entry.

So anyway, I fired my webmaster. I built my own webpage. I did this - of all things - with Microsoft Publisher. Yeah, well, it worked - in that I was able to build a site and, with some effort, get it on the web. I won't go into why you shouldn't try this, kids, at home. I was at home when I tried it, sure. But I don't suggest building a site with Publisher. It can be done, but don't do it.

One thing that happens - talk about annoying: The site crams all against the left side of the page. There's nothing you can do to change that. You might as well type out onto the web page "Look, Ma, I can create a website using Publisher." Don't do it.

Well, I knew at the time I shouldn't be messing around with Publisher. It's great for putting together a book or something for print. It's not good for websites. I had just been so excited because I had created a downloadable book for lulu.com. Publisher was great for laying out a book. I had so much momentum...

I put the Publisher site up, and thought I had done a pretty good job, considering that everything was crammed up to the left of the screen. I had yet to become a blogger, and I had yet to realize the importance of tagging and so on. All that important "extra" stuff. I'm joking. Writing tags is not extra. It's essential. So is the blog - on the website.

Then I bought FrontPage and a book and... That's all she wrote. I learned FrontPage and I haven't tried anything else out since. Why not? So far I don't need to use the fantastic Dreamweaver that everyone talks about. Oh, I can't do Flash on FrontPage? Uh - yes you can. Easily.

I continue to believe that content is all-important. Not bells. Not whistles. Content. I don't care what kind of a site you are putting up. Well, okay, I wouldn't necessarily use FrontPage for every circumstance. But for you and me, the individual or small company that wants to be up and shining on the web, FrontPage is the clear answer. At least it was for me. As I say, I haven't looked back since.

One needn't learn the bells and whistles. One certainly needn't incorporate dhtml or whatever that code is that will make letters pop and fly about. Old browsers can't see it, and new browsers - mine, at least - don't want to see it.

I have affiliated with companies. That is, I've tried to turn a dollar by putting them up on my site, a link or banner or what have you. Let me say that what I don't like are the banners that flicker and blink and all that junk. If I want the Las Vegas experience, I'll go there.

Just give me content. FrontPage can handle that and handle it well. You want to be able to upload Flash, for sure. FrontPage can do it. You want to be able to get as much information on your website with as few bytes as possible. FrontPage can do this as well as any program. So, I'm happy. Are you happy - yet?