Use of characters "é" or "ê"
cordial_camaraderie
german etc
Does the use of these extended characters increases the site download
time ??
Should we use this or not....
Please suggest us !!
Thanks
www.stellar-info.fr
Roy Schestowitz
If you vary your default charset, then the browser may have to use additional
services, which could lead to lag. The lag seems to be significantly long
for non-Latin languages such as Chinese or Arabic. For Latin languages, the
lag is not significant. Although it's a a no-no from the point-of-view of
Web standards, you could use Western (standard English) charset and embed
"é" or "ê" as images. Some Web sites handle the yet-loosely-supported Euro
symbol in this manner.
Hope it helps,
Roy
PS - I imagine it has a similar effect on search engines, including the
inclination to assign a page to a certain localised search. The language
attributes are probably more important though.
--
Roy S. Schestowitz | "Have you compiled your kernel today?"
http://Schestowitz.com | SuSE Linux ¦ PGP-Key: 0x74572E8E
8:15am up 14 days 0:52, 7 users, load average: 1.87, 1.18, 0.79
http://iuron.com - help build a non-profit search engine
tonnie
> __/ [ cordial_camaraderie ] on Wednesday 22 March 2006 08:17 \__
>
>
>>Normally these characters are used in other languages i.e French,
>>german etc
>>
>>Does the use of these extended characters increases the site download
>>time ??
>>
>>Should we use this or not....
>>
>>Please suggest us !!
>>
>>Thanks
>>www.stellar-info.fr
>
>
> If you vary your default charset, then the browser may have to use additional
> services, which could lead to lag. The lag seems to be significantly long
> for non-Latin languages such as Chinese or Arabic. For Latin languages, the
> lag is not significant. Although it's a a no-no from the point-of-view of
> Web standards, you could use Western (standard English) charset and embed
> symbol in this manner.
And what is wrong with using UTF-8, or iso-8859-15 and refer to the
characters as é and ê?
--
Webontwerp: http://vision2form.nl/webontwerp/
Korte handleiding zoekmachine optimalisatie / gevonden worden:
http://vision2form.nl/webontwerp/gevonden-worden.html
Lifestyle - wonen reizen en genieten : http://vision4living.com
Roy Schestowitz
> Roy Schestowitz wrote:
>> __/ [ cordial_camaraderie ] on Wednesday 22 March 2006 08:17 \__
>>
>>
>>>Normally these characters are used in other languages i.e French,
>>>german etc
>>>
>>>Does the use of these extended characters increases the site download
>>>time ??
>>>
>>>Should we use this or not....
>>>
>>>Please suggest us !!
>>>
>>>Thanks
>>>www.stellar-info.fr
>>
>>
>> If you vary your default charset, then the browser may have to use
>> additional services, which could lead to lag. The lag seems to be
>> significantly long for non-Latin languages such as Chinese or Arabic. For
>> Latin languages, the lag is not significant. Although it's a a no-no from
>> the point-of-view of Web standards, you could use Western (standard
>> English) charset and embed "é" or "ę" as images. Some Web sites handle the
>> yet-loosely-supported Euro symbol in this manner.
>
> And what is wrong with using UTF-8, or iso-8859-15 and refer to the
> characters as é and ê?
Oh, you're right. I can actually see them at the bottom of my 'pocket
reference':
http://www.ascii.cl/htmlcodes.htm
Some symbols remain excluded, but here's some fancy stuff you can achieve
with what's at hand: *smile*
http://www.unics.uni-hannover.de/nhtcapri/mathematics.html
Best wishes,
Roy
--
Roy S. Schestowitz | $> wget -r -erobots=off http://www.*
http://Schestowitz.com | SuSE Linux Ś PGP-Key: 0x74572E8E
8:35am up 14 days 1:12, 8 users, load average: 0.24, 0.46, 0.56
http://iuron.com - Open Source knowledge engine project
cordial_camaraderie
or "ê"
--
Logiciel de récupération de données - http://www.stellar-info.fr
tonnie
> Should I remove these characters with normal characters like e for "é"
No.
Use é for é and ê for ę
Big Bill
<cordial_c...@yahoo.com> wrote:
>Should I remove these characters with normal characters like e for "é"
>or "ę"
I think you should keep them if you can as it adds character to your
pages.
BB
--
http://www.here-be-posters.co.uk/art-prints-sitemap.htm
http://www.crystal-liaison.com/fairy-collection/index.html
kr...@crystal-liaison.com Gifty! Shiny! BB!
Harlan Messinger
> Should I remove these characters with normal characters like e for "é"
Those characters *are* normal characters, and normal browsers and fonts
support them. There's no reason whatsoever to remove them. The only
important thing is to make sure the web server is correctly reporting
the character encoding--generally ISO-8859-1 or UTF-8, OR to represent
these characters in the source in &aaaaa; or ✏ format.
Harlan Messinger
> cordial_camaraderie wrote:
>
>> Should I remove these characters with normal characters like e for "é"
>> or "ę"
>
>
> No.
>
> Use é for é and ê for ę
Not necessary if they are stored using an encoding that supports them
and the web server reports that encoding correctly.
John Bokma
> And what is wrong with using UTF-8, or iso-8859-15 and refer to the
> characters as é and ê?
If you use UTF-8/ISO-8859-15 you can just type the character as is (enter
it via the keyboard), no need for &younameit;
I can't think up of any overhead if you use ISO-8859-15
With UTF-8 your file, IIRC, might become a bit larger.
--
John Freelance Perl programmer: http://castleamber.com/
Installing and configuring Apache on Windows XP (virtual hosting):
http://johnbokma.com/windows/apache-virtual-hosts-xp.html
John Bokma
> cordial_camaraderie wrote:
>> Should I remove these characters with normal characters like e for "é"
>> or "ę"
>
> No.
>
> Use é for é and ê for ę
No
Just type them like é and ę and put
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
in your head section.
No need for images (silly!), or using a charset *and* typing them out like
&somefunnyshit;
If you doubt me, run it through the w3c validator.
tonnie
> tonnie <t.pr...@chello.nl> wrote:
>>Use é for é and ê for ê
>
> No
> No need for images (silly!), or using a charset *and* typing them out like
> &somefunnyshit;
> If you doubt me, run it through the w3c validator.
I did and you know what the $funnyshit; validated.
:-P
John Bokma
> John Bokma wrote:
>> tonnie <t.pr...@chello.nl> wrote:
>
>>>Use é for é and ê for ê
>>
>> No
>
>> No need for images (silly!), or using a charset *and* typing them out
>> like &somefunnyshit;
>
>> If you doubt me, run it through the w3c validator.
>
> I did and you know what the $funnyshit; validated.
Funny shit always does :-D
--
John Freelance Perl programmer: http://castleamber.com/
Firefox Fast Search:http://johnbokma.com/firefox/keymarks-explained.html
Borek
> John Bokma wrote:
>> tonnie <t.pr...@chello.nl> wrote:
>
>>> Use é for é and ê for ê
>> No
>
>> No need for images (silly!), or using a charset *and* typing them out
>> like &somefunnyshit;
>
>> If you doubt me, run it through the w3c validator.
>
> I did and you know what the $funnyshit; validated.
Try with &funnyshit;
Best,
Borek
--
http://www.chembuddy.com
http://www.ph-meter.info
Gerard
Would you really misspell words to decrease the download time of a
page? In that case I have a good tip. Just omit most of the vowels. It
works in Arabic and Hebrew ;-)
Harlan Messinger
> __/ [ cordial_camaraderie ] on Wednesday 22 March 2006 08:17 \__
>
>>Normally these characters are used in other languages i.e French,
>>german etc
>>
>>Does the use of these extended characters increases the site download
>>time ??
>
> services, which could lead to lag. The lag seems to be significantly long
> for non-Latin languages such as Chinese or Arabic. For Latin languages, the
> lag is not significant.
*What* lag? An accented character in ISO-8859-1 is one byte, exactly the
same as any unaccented ASCII character. It seems to me that under any of
the UTF encodings, the time required to expand the character
representations is trivial.
> Although it's a a no-no from the point-of-view of
> Web standards, you could use Western (standard English) charset and embed
> "é" or "ę" as images.
Why? You think image files are smaller than characters?
> Some Web sites handle the yet-loosely-supported Euro
> symbol in this manner.
I have a euro symbol entered directly into a file using UTF-8 encoding
and serve it as UTF-8. It is displayed as a euro symbol in Netscape 4.7,
and my copy of Lynx cleverly displays it as "EUR". Add existing support
by current versions of IE, Mozilla, Netscape, and Firefox, and I wonder
what you mean by "loosely supported".
Roy Schestowitz
I was thinking about Asian languages, which require loading of some extra
components and are slow(er) to render, over here at least. My arguments will
not hold for Latin typography like "é" or "ę", so apologies for my
spontaneous, poorly-generalised remarks.
Best wishes,
Roy
--
Roy S. Schestowitz | "Stand for nothing and you will fall for anything"
http://Schestowitz.com | SuSE Linux Ś PGP-Key: 0x74572E8E
6:05pm up 15 days 10:42, 8 users, load average: 0.48, 0.57, 0.64
tonnie
> __/ [ Harlan Messinger ] on Thursday 23 March 2006 16:29 \__
>>I have a euro symbol entered directly into a file using UTF-8 encoding
>>and serve it as UTF-8. It is displayed as a euro symbol in Netscape 4.7,
>>and my copy of Lynx cleverly displays it as "EUR". Add existing support
>>by current versions of IE, Mozilla, Netscape, and Firefox, and I wonder
>>what you mean by "loosely supported".
>
> I was thinking about Asian languages, which require loading of some extra
> components and are slow(er) to render, over here at least. My arguments will
> not hold for Latin typography like "é" or "ê", so apologies for my
> spontaneous, poorly-generalised remarks.
I also did think (just for a split second but i did) about older
browsers, and my "and" should have been a second or, but hey, we are
getting older and the net is changing fast. :-D
John Bokma
> *What* lag? An accented character in ISO-8859-1 is one byte, exactly
> the same as any unaccented ASCII character. It seems to me that under
> any of the UTF encodings, the time required to expand the character
> representations is trivial.
Some UTF encodings double the size of the file IIRC.
For the rest I agree :-D
--
John Freelance Perl programmer: http://castleamber.com/
Firefox Keywords: http://johnbokma.com/firefox/keymarks-explained.html