W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > May to August 1996

Re: Remapping charsets

From: Keld J|rn Simonsen <keld@dkuug.dk>
Date: Sat, 13 Jul 1996 13:51:27 +0200
Message-Id: <199607131151.NAA24135@dkuug.dk>
To: mirsad.todorovac@fer.hr, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/1118
Mirsad Todorovac writes:

> In few last messages regarding charsets, I was to notice that many troubles
> could be handled via some character remapping mechanism.
> How this should work is as follows:
> -	let's suppose that browser cannot accept document charset, then
> 	document should be translated into charset which is supported
> 	by browser, but lest likely to loose some characters
> 	(Example: with CP-1250 and iso-8859-2 there are only some
> 		  swapped blocks of chars, says Dave, so then there should
> 		  never be a loss in conversion, but we don't need to have
> 		  both, duplicate versions of documents -- one for UN*X
> 		  machines, and one for Wind*ws CEE [and still more for
> 		  other platforms ...]
> 	)
> - conversion mechanism is simple transliteration, different codes are
>   being assigned for the same characters

RFC1345 actually provides specifications for doing such simple
transliteration, with fallbacks.

keld simonsen
Received on Saturday, 13 July 1996 04:59:07 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:40:17 UTC