Translation of Web Pages

sylver wrote:



is key. As unpleasant as my remark may sound, I believe that someone starting an HTML localisation job should know basic HTML.

A web page with frames is in fact made of several separate web pages. The page with frames itself merely gives a link to the actual pages and say where they should appear on the display. There is no real text on the page with frames (with the possible exception of a "no frames" tag). To better understand that concept, right click on the file you saved, choose "open with" and select "notepad".

The code will appear, and as you can see, the text is nowhere to be seen. CatCraddle can't translate what *does not* exist. You are simply using the wrong file.

Now, to get the pages you need, there are 2 ways:

1. The professional way. Get your client to send the files you need to translate. That's the only way that accomodates for all types of Web sites.

2. Cope solution: go to the web page. Right click on the part of the page where the text is displayed. Go to "properties". A pop up window will appear, and in the middle, it gives you the url of the page. Select it with the mouse and copy it (Ctrl+C). Close the property window. paste the url in the address bar of the browser and go. The actual page will be displayed alone, and at that point you can save it and translate it with Catcraddle or any other way. Repeat the procedure for every separate page from the frame page.

These informations should be enough for you to get some results, but please understand that you are not doing your client a favor when you undertake HTML translations without knowing at least some HTML. As good as Catscraddle (or any other program) may be, it is no substitute for understanding what you are doing. I don't mean you should stop offering web site translation, but you should definetly burn the midnight oil and learn some more on the subject.