9 messages in org.freebsd.freebsd-wwwRe: SGML->HTML: entities translation ...| From | Sent On | Attachments |
|---|---|---|
| Andrey A. Chernov | Mar 4, 2000 2:42 am | |
| Andrey A. Chernov | Mar 5, 2000 9:36 am | |
| Chris Costello | Mar 5, 2000 2:07 pm | |
| Andrey A. Chernov | Mar 5, 2000 2:16 pm | |
| Chris Costello | Mar 5, 2000 3:45 pm | |
| Nik Clayton | Mar 5, 2000 6:14 pm | |
| Andrey A. Chernov | Mar 6, 2000 2:14 am | |
| Alexey Zelkin | Mar 7, 2000 2:44 pm | |
| Andrey A. Chernov | Mar 8, 2000 12:24 am |
| Subject: | Re: SGML->HTML: entities translation is broken for non-Latin1 charsets | |
|---|---|---|
| From: | Andrey A. Chernov (ac...@nagual.pp.ru) | |
| Date: | Mar 5, 2000 2:16:50 pm | |
| List: | org.freebsd.freebsd-www | |
On Sun, Mar 05, 2000 at 04:08:00PM -0600, Chris Costello wrote:
On Saturday, March 04, 2000, Andrey A. Chernov wrote:
Right way is to not translate &...; entities from sgml source at all and leave them in place. Browser always know better substitution for them.
No, you'd have to have a list of some sort of the HTML standard entities and use them when translating to HTML from SGML. There are other SGML entities that begin with &...; such as &rel.current; which can't be preserved into HTML. Then there's the issue of other various formats like TeX and RTF. Will we handle those the same too? Or will this just be an HTML issue?
Yes, I agree to have a list of HTML standard entities which will be not converted in sgml->html procedure. Other formats must use its own symbolic names or hardcoded values not from latin1 but from native tables in this case. But for HTML better variant is to keep all symbolic HTML entities untouched. If adding all of them will be hard, we need to add at least all entities above ASCII and not latin1 letters (like and © are).
-- Andrey A. Chernov <ac...@nagual.pp.ru> http://nagual.pp.ru/~ache/
To Unsubscribe: send mail to majo...@FreeBSD.org with "unsubscribe freebsd-www" in the body of the message