Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Multiple encodings in same page ???

Status
Not open for further replies.

Sleidia

Technical User
May 4, 2001
1,284
FR

Hello,

I'd like to know if there is a way to display different charsets within the same HTML document (French - English - Japanese). And what are the browsers who support such a feature?

Thanks ! ;)
 
Thanks Chris, but with iframes, it's not the same HTML document anymore. I don't want to use iframes mainly for SEO purpose.

Wasn't CSS supposed to allow such a feature anyway?

Thanks again for your input :)
 
I might have found the final answer here :


The character encoding (sometimes incorrectly referred to as the 'charset') determines how a user agent interprets the 1's and 0's as 'characters'. UTF-8 is one popular encoding which uses between 1 and 6 octets (8-bit numbers) to represent any given code point in the Unicode repertoir.
An HTML page has a given character encoding, and you don't want to change that in the middle of the document.
An HTML page is also written in a primary natural language, e.g. Japanese. This is declared via the 'lang' attribute in the <html> tag:
HTML Code:
<html lang="ja">
If you include words or phrases in another language in your page, you should mark these up using another 'lang' attribute, e.g.
HTML Code:
<span lang="sv">det här är svenska</span>
It used to be common to have specific character encodings for different parts of the world, e.g. Big5 in China, EUC in Japan, ISO 8859-1 in Europe. In order to get away from the problems with these incompatible encodings, we now have UTF-8 and UTF-16.
A page written mainly in a Western language, with some parts in an Oriental language, should probably use UTF-8. A page written mainly in an Oriental language might be more efficient to encode with UTF-16. UTF-8 would still work, but it might make the document larger (since most ideographs might require 3-4 octets, whereas UTF-16 uses 2 octets for any code point).
 
The biggest issue with iframes with regards to SEO is the orphaned page problem in the SERPs, which is handled simply by one line of javascript. All SEs have no problems crawling and indexing the page referenced in the src attribute of the <iframe> tag.

However Multilingual Documents straight from the horses mouth (so to speak)

No idea how the various UA handle this (if at all)

Chris.

Indifference will be the downfall of mankind, but who cares?
Woo Hoo! the cobblers kids get new shoes.
People Counting Systems

So long, and thanks for all the fish.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top