On 30 Aug 2008 at 10:26, Robert Hanson wrote:
> <span> </span>
>
> might. If that is in the GT expression, then the translator will see that
> and, presumably, know to
> use this mechanism. It isn't great, because it is nonstandard, but it seems
> the only alternative.
Don't know yet what to vote here.
> Somehow, though, the page title has to be put in correctly, and I don't see
> that as being
> appropriately done using this mechanism. The user is typing it. Do we really
> expect novice users
> to know the &....; codes? Or to know to enter those in the entry box?
No
> I still don't understand why specifying UTF-8 on the web page does not work.
> I'd like more
> evidence that &...; codes really are necessary.
Since this only fails on some systems (not mine), it's difficult to say.
> Let's still find out if there is a UTF-8 solution. Are there any examples of
> web pages using UTF-8
> encoding that work?
Plenty. But I think that the issue is that the page is being written from Java.
If you do the
page in your editor, and choose UTF8 coding, things work. At least if the
server doesn't
screw it up, as I suspect.
> OK, here's another simple possibility. We simply change those character codes
> entered by the
> translator or user that are going to HTML by converting them to the hex value:
>
> á
Can that really be done? There are dozens of characters if you consider all
languages
already there.
I assume that you mean that Jmol Java code can read a character's (Uni- or
UTF8-) code
and "translate" it into the &#xnnnn; form? Painful to have to do so, if even
possible! But
that looks like a perfect solution for the translators.
> Two pages to check:
>
> http://www.alanwood.net/demos/ent4_frame.html
Nice page, I didn't know it. I always use
http://htmlhelp.com/reference/html40/entities/
Hey, there may be a clue there! It says
"XML does not support character entity references by default, but Dave Pawson
has a page
on Special Characters that includes instructions for modifying the DOCTYPE
declaration in
XML DTDs and XSLT scripts."
And the tenplates ARE XHTML!
It seems to say that entities proper (like á) are not accepted, but
numeric codes
(&#nnnn) are. So, not an issue.
But my browsers show the pages correctly and they are coded with entities. So
forget that.
And anyawy, I guess that, if provided automatically as Bob is suggesteing, we'd
better and
easier go for the numeric codes than for the entities.
> question is whether the &#nnnn; method works for you.
As far as I know, &#nnnn; and &#xnnnn; work the same as á etc
--only there are
more characters available in the first ones.
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Jmol-developers mailing list
Jmol-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jmol-developers
