How can I put a ´on a c?
Andreas Reikowski
é.
Who can help me?
Bonnie's Gang
Andreas Reikowski <andreas....@clickfish.com> wrote in message
news:98ao4c$8qb$1...@news1.transmedia.de...
> I need an html-order that makes my system putting an ´ on a c, like á
or
> é.
<font face="Verdana, Arial, Helvetica, sans-serif"
size="2">risqué</font>
Prosit
Bonnie's Gang
Instant Merchant Accounts
http://www.btobmerchantservices.com
Steven Van Hulle
the example you gave is correct for the é, but that's not what Andreas
asked.
BTW: comment from Allaire HomeSite's Validator: "In HTML 4.0, FONT is
depreciated. It may become obsolete in future versions, consider using style
sheets instead."
Andreas:
HomeSite has a function for picking diacritics, but the accented c isn't one
of them.
Steven
"Bonnie's Gang" <bon...@NOJUNKoptonline.net> wrote in message
news:CV5q6.117365$Vj5.18...@news02.optonline.net...
keTTle_drum
á is an a acute.
é is an e acute.
Email me if you need any more.
--
Join the HTMLGold's mailing list at http://groups.yahoo.com/group/htmlgold.
HTMLGold. It's not what you know. It's how it was taught!
Andreas Reikowski <andreas....@clickfish.com> wrote in message
news:98ao4c$8qb$1...@news1.transmedia.de...
Don McCahill
Andreas Reikowski wrote:
To this point there is no accented c character. Your best bet would be to create
a graphic and use it.
--
Don McCahill
Internet Graphic Design
Westervelt College
London, Canada
newshound
cC
"Steven Van Hulle" <stev...@pandora.be> wrote in message
news:5k8q6.8057$486.9...@afrodite.telenet-ops.be...
Vlatko Juric-Kokic
<stev...@pandora.be> wrote:
>Andreas:
>HomeSite has a function for picking diacritics, but the accented c isn't one
>of them.
Maybe Andreas should use iso-8859-2 META tag. Then he probably could
use æ in his page.
But the problem is who's going to see it. I don't think that people in
Germany have their browsers set for the Central European character
set. And if they fix that, they are not going to see the German
letters. Or other accented letters from Latin-1.
vlatko
--
vlatko.ju...@zg.hinet.hr
Bonnie's Gang
--
Prosit
Bonnie's Gang
Instant Merchant Accounts
http://www.btobmerchantservices.com
newshound <inquri...@xxxget-noticed.com remove the x's> wrote in message
news:taipllm...@corp.supernews.com...
Bonnie's Gang
newshound <inquri...@xxxget-noticed.com remove the x's> wrote in message
news:taipllm...@corp.supernews.com...
> Select the Baltic font. They are there
> cC
Baltic font won't work either. What you're reffering to is called
a "mikstinajums" it's used on the letters c, g, s, and some others,
but it looks more like a small letter "v" on top of the letter.
Yeah ... I'm Latvian :o)
--
Gypsy
Andreas Reikowski <andreas....@clickfish.com> wrote in message
news:98ao4c$8qb$1...@news1.transmedia.de...
Try here
http://www.htmlhelp.com/reference/html40/entities/
The Gypsy
Jukka Korpela
>I need an html-order that makes my system putting an ´ on a c, like á or
>é.
ć
Browser support is defective but getting better. I suppose that a
sufficiently new IE on Win gets it right. Netscape 4 needs some help,
see http://ppewww.ph.gla.ac.uk/%7eflavell/charset/quick.en.html#cons
Whether it would be best to use some surrogate, like a plain "c", or
perhaps "c" followed by "´" (acute accent as separate character),
depends on several factors.
Depending on the repertoire of characters needed as a whole, you might
also consider using a 8-bit character encoding that lets you enter c
with acute directly, as an octet (byte). I'm mainly thinking of
iso-8859-2, which is sufficient for a large number of European
languages, see http://czyborra.com/charsets/iso8859.html#ISO-8859-2
For some general considerations see
http://ppewww.ph.gla.ac.uk/%7eflavell/charset/checklist
--
Temporary incomplete copies of my Web site that was
at http://www.hut.fi/u/jkorpela/ (now removed by HUT):
http://mtl.uta.fi/jkorpela/
http://mirror.subotnik.net/jkorpela/
Jukka Korpela
>Maybe Andreas should use iso-8859-2 META tag. Then he probably could
>use æ in his page.
Oh no! The character reference æ unambiguously denotes the SMALL
LATIN LETTER AE (letters a and e combined into one character, used e.g.
in some Scandinavian languages and in some styles of writing Latin). Its
meaning does not depend on any meta tags, language used on the page,
phase of the moon, or anything. It's fixed by HTML specifications, ever
since HTML 2.0.
Some seriously broken browsers are known to get this wrong, but that's a
problem, not a solution. And browsers that behave correctly (in this
respect) are more common, so you'd get the wrong character (well, the
_right_ character in the technical sense: the one that the reference
actually denotes:-)) most of the time.
>But the problem is who's going to see it. I don't think that people in
>Germany have their browsers set for the Central European character
>set.
Actually, most of the popular browsers can handle iso-8859-2 just fine.
>And if they fix that, they are not going to see the German
>letters. Or other accented letters from Latin-1.
You've misunderstood the issue. The user is not expected to set the
"character set". It's a matter of communication between the server and
the browser: the server sends an HTTP header that specifies the
character encoding, and the browser takes it from there. The META tag
you are referring to is just an attempt to simulate that interaction.
And on some older browsers the user might actually need to manually
change the encoding - but it's switchable then: you can view a "normal"
(iso-8859-1) page, then an iso-8859-2 page, then change the encoding
(the way that the browser interprets the data) back to iso-8859-1 again.
The user would just do manually what browsers are expected to do
automatically.
This is a difficult topic, partly due to widespread problems in
implementations, but let's not make it more difficult by thinking that
changing the encoding manually in the browser would _fix_ it so that it
could be changed back. Mmm'kay?
Vlatko Juric-Kokic
<JukkaK...@hotmail.com> wrote:
>Vlatko Juric-Kokic <vlatko.ju...@zg.hinet.hr> wrote:
>
>>Maybe Andreas should use iso-8859-2 META tag. Then he probably could
>>use æ in his page.
>
>Oh no! The character reference æ unambiguously denotes the SMALL
>LATIN LETTER AE (letters a and e combined into one character, used e.g.
>in some Scandinavian languages and in some styles of writing Latin).
Please explain to me then why, when I switch the meta tag to 8859-1
just to confuse the browser, I see what you say, the Latin-1
characters like ae, superscript 1, etc? And with 8859-2 tag I see the
proper accented letters? With not a character changed?
>This is a difficult topic, partly due to widespread problems in
>implementations, but let's not make it more difficult by thinking that
>changing the encoding manually in the browser would _fix_ it so that it
>could be changed back. Mmm'kay?
Yeah, my bad.
vlatko
--
vlatko.ju...@zg.hinet.hr
Jukka Korpela
>>>Maybe Andreas should use iso-8859-2 META tag. Then he probably could
>>>use æ in his page.
>>
>>Oh no! The character reference æ unambiguously denotes the SMALL
>>LATIN LETTER AE (letters a and e combined into one character, used e.g.
>>in some Scandinavian languages and in some styles of writing Latin).
>
>Please explain to me then why, when I switch the meta tag to 8859-1
>just to confuse the browser, I see what you say, the Latin-1
>characters like ae, superscript 1, etc? And with 8859-2 tag I see the
>proper accented letters? With not a character changed?
If you really mean that this happens when the document contains æ,
then the simple answer is that you are using a faulty browser.
Are you absolutely sure you mean æ and not an octet (byte) with
value 230 decimal? They are quite distinct beasts. The meaning of the
latter depends on the encoding.
Vlatko Juric-Kokic
<JukkaK...@hotmail.com> wrote:
>>Please explain to me then why, when I switch the meta tag to 8859-1
>>just to confuse the browser, I see what you say, the Latin-1
>>characters like ae, superscript 1, etc? And with 8859-2 tag I see the
>>proper accented letters? With not a character changed?
>
>If you really mean that this happens when the document contains æ,
>then the simple answer is that you are using a faulty browser.
>
>Are you absolutely sure you mean æ and not an octet (byte) with
>value 230 decimal? They are quite distinct beasts. The meaning of the
>latter depends on the encoding.
Ah. I'm using the c acute character itself, not the numerical
reference. So, yes, it's 230 decimal. And that's what I was asking.
Sorry for the muddling.
Nevertheless, could you drop by at http://www.webart.hr/nrnm/ and tell
me what you see? Thanks in advance.
vlatko
--
vlatko.ju...@zg.hinet.hr
Jukka K. Korpela
news:p5hmatsccki0fv35j...@news.tel.hr...
> Ah. I'm using the c acute character itself, not the numerical
> reference. So, yes, it's 230 decimal. And that's what I was asking.
OK, fine. Using iso-8859-2 that way is quite OK, and probably the best
way to author pages in languages that make heavy use of such characters.
> Nevertheless, could you drop by at http://www.webart.hr/nrnm/ and tell
> me what you see?
I see c with acute in the signature, and c and s with hat (capek) in the
text elsewhere, just as it should be (I guess :-) ).
When writing an occasional name in a document otherwise in (say)
English, it's a tough decision. Many people prefer safety (e.g., just
use "c") to typographic correctness in such cases, since any method
(iso-8859-2, &#number; references, UTF-8, whatever) has some risk of
having a completely wrong character or no character at all displayed.
Vlatko Juric-Kokic
<jkor...@malibutelecom.com> wrote:
>"Vlatko Juric-Kokic" <vlatko.ju...@zg.hinet.hr> wrote in message
>news:p5hmatsccki0fv35j...@news.tel.hr...
>> Nevertheless, could you drop by at http://www.webart.hr/nrnm/ and tell
>> me what you see?
>
>I see c with acute in the signature, and c and s with hat (capek) in the
>text elsewhere, just as it should be (I guess :-) ).
Did you see the d with a crossbar on the stem? The one that looks like
the lowercase Icelandic eth?
I received an interesting mail from a guy in France today who decided
to try and help me, for which I'm grateful, just like I'm grateful to
you.
He said that he viewed the page with iCab Pre2.4 and IE 5 on Mac. iCab
didn't have the proper characters at all, while the IE showed s-caron
and c-caron as the letters with the diacritic marks after them. As I
understood, like this: sˇ. This is probably connected to what you
said:
>When writing an occasional name in a document otherwise in (say)
>English, it's a tough decision. Many people prefer safety (e.g., just
>use "c") to typographic correctness in such cases, since any method
>(iso-8859-2, &#number; references, UTF-8, whatever) has some risk of
>having a completely wrong character or no character at all displayed.
As far as I understand, the main problem is the fonts. While people
with Central and Eastern Europe international Windows certainly have
the appropriate fonts installed by default, others don't, so their
browsers won't display the characters anyway.
vlatko
--
vlatko.ju...@zg.hinet.hr