Re: Google funny

Paul Blay hu kiteb:

Hmm, maybe I should try again in English. ;-)

A ruby markup such as
ruby><rb>$BGQ4~(B</rb><rp>(</rp><rt>$B%O%$%-(B</rt><rp>)</rp></ruby
is 'honoured' by Internet Explorer, but not by Netscape* so in IE you
get furigana.

On browsers that dont support ruby it declines 'gracefully' to $BGQ4~(B($B%O(B
$B%$%-(B)
(e.g. to word + reading). However if you prefer to see $BGQ4~(B instead
of
$BGQ4~(B($B%O%$%-(B)
for browsers that dont support ruby then a <span
style='display:none'> would hide the reading.

Given that I know of no browser that supports <ruby> but doesn't
support <span style='display:none'> it would be a very stupid thing
to do.

function ShowKanji() {
document.rb.style.display='inline';
document.rp.style.display='none';
document.rt.style.display='none';
}
function ShowFurigana() {
document.rb.style.display='none';
document.rp.style.display='none';
document.rt.style.display='inline';
}

Would these do what i think they would do? Couple those functions with
an appropriate user interface, and you could show the kanji or hiragana
easily.


--
--
Fabian
Visit my website often and for long periods!
http://www.lajzar.co.uk

"Fabian" wrote ...

Paul Blay hu kiteb:

Hmm, maybe I should try again in English. ;-)

A ruby markup such as
ruby><rb>$BGQ4~(B</rb><rp>(</rp><rt>$B%O%$%-(B</rt><rp>)</rp></ruby
is 'honoured' by Internet Explorer, but not by Netscape so in IE you
get furigana.

On browsers that dont support ruby it declines 'gracefully' to $BGQ4~(B($B%O(B
$B%$%-(B) (e.g. to word + reading). However if you prefer to see $BGQ4~(B
instead of $BGQ4~(B($B%O%$%-(B) for browsers that dont support ruby then a
span style='display:none'> would hide the reading.

Given that I know of no browser that supports <ruby> but doesn't
support <span style='display:none'> it would be a very stupid thing
to do.

function ShowKanji() {
document.rb.style.display='inline';
document.rp.style.display='none';
document.rt.style.display='none';
}
function ShowFurigana() {
document.rb.style.display='none';
document.rp.style.display='none';
document.rt.style.display='inline';
}

Would these do what i think they would do?

I compliment you on your bravery in cross-posting to c.l.j ;-)
So here I go risking showing off my ignorance as well.

Assuming that the browser supports the ruby tag then the first
does (but you don't need* the
document.rp.style.display='none';
). However I'm not sure the second does, I'd have to try it and
see. Possibly you'd end up with small furigana text hovering
above the space where the kanji isn't displayed.

I've no idea how it would work on hypothetical browsers that
support javascript and styles but dont support ruby.

Couple those functions with
an appropriate user interface, and you could show the kanji or
hiragana easily.

I'm not sure there's that much call for it.

* Because what's in the <rp> tags is not to be displayed by design.

Paul Blay hu kiteb:

"Fabian" wrote ...
Paul Blay hu kiteb:

Hmm, maybe I should try again in English. ;-)

A ruby markup such as
ruby><rb>$BGQ4~(B</rb><rp>(</rp><rt>$B%O%$%-(B</rt><rp>)</rp></ruby
is 'honoured' by Internet Explorer, but not by Netscape so in IE you
get furigana.


function ShowKanji() {
document.rb.style.display='inline';
document.rp.style.display='none';
document.rt.style.display='none';
}
function ShowFurigana() {
document.rb.style.display='none';
document.rp.style.display='none';
document.rt.style.display='inline';
}

Would these do what i think they would do?

I compliment you on your bravery in cross-posting to c.l.j ;-)
So here I go risking showing off my ignorance as well.

Just tested it; it doesn't work. I realise my mistake. That format is
for manipulating tags whose ID attribute has been set, and not for
manipulating tags directly. Anyone know the correct way to manipulate
the style for an entire tag?

I've no idea how it would work on hypothetical browsers that
support javascript and styles but dont support ruby.

Assuming the browser has a document object model that allows
manipulation of arbitrary html tags, but doesnt recognise RUBY, the
principle is still sound. manipulating the RP tag is necessary in this
case to avoid having plain hiragana display inside parenthesis.


--
--
Fabian
Visit my website often and for long periods!
http://www.lajzar.co.uk

"Fabian" wrote ...

Just tested it; it doesn't work. I realise my mistake. That format is
for manipulating tags whose ID attribute has been set, and not for
manipulating tags directly. Anyone know the correct way to manipulate
the style for an entire tag?

Lots of people, but obviously I've forgotten.

I've no idea how it would work on hypothetical browsers that
support javascript and styles but dont support ruby.

Assuming the browser has a document object model that allows
manipulation of arbitrary html tags,

But are there such browsers? Back when I was actually doing this
stuff I stuck to using tags that existed for the browsers I was
testing with.

but doesnt recognise RUBY, the
principle is still sound. manipulating the RP tag is necessary in this
case to avoid having plain hiragana display inside parenthesis.

Paul Blay wrote:

"Fabian" wrote ...
Just tested it; it doesn't work. I realise my mistake. That format is
for manipulating tags whose ID attribute has been set, and not for
manipulating tags directly. Anyone know the correct way to manipulate
the style for an entire tag?

With the DOM of a UA you do not manipulate tags but elements represented
by objects.

Lots of people, but obviously I've forgotten.

In the case Ruby markup (inside XHTML) allows for using the W3C-DOM, you
can access elements by their tag name:

document.getElementsByTagName("...")

returns an array of objects where the respective elements have `...' as tag
name. You need to check if such an object has a `style' property, and if it
has, you can access it.


HTH

PointedEars, F'up2 cljs