I'm sorry if this info is already in the Unicode website or book, but
I searched and couldn't find it in a hurry.
When extending beyond the BMP and the maximum range of 16-bit
codepoints, why was it chosen to go upto 10 and not any more or
less? Wouldn't F have been the next logical stop
On Mon, Nov 26, 2012 at 11:47 AM, Shriramana Sharma samj...@gmail.com wrote:
I'm sorry if this info is already in the Unicode website or book, but
I searched and couldn't find it in a hurry.
When extending beyond the BMP and the maximum range of 16-bit
codepoints, why was it chosen to go upto
Or, if one prefers:
http://www.井作恆.net/XKCD/1137.html
On 2012年11月21日, at 上午10:22, Deborah Goldsmith golds...@apple.com wrote:
http://xkcd.com/1137/
Finally, an xkcd for Unicoders. :-)
Debbie
Pierpaolo Bernardi olopierpa at gmail dot com replied to Shriramana
Sharma samjnaa at gmail dot com:
When extending beyond the BMP and the maximum range of 16-bit
codepoints, why was it chosen to go upto 10 and not any more or
less?
I think this is because upto 10 is the maximum
Somewhat ironically, both Firefox and Internet Explorer, on my machine at
least, detect this page is encoded with ISO-8859-1 and cp-1252 respectively,
instead of UTF-8. It seems they both ignore the XML prolog which is the only
place where the encoding is stated.
From:
I wonder why this IDN link appears to me using sinograms in its domain
name, instead of Deseret letters. The link works, but my browser cannot
display it and its displays the Punycoded name instead without decoding it.
This is strange because I do have Deseret fonts installed and I can
view
Not a bug of your machine or browser; this is a problem of the webserver in
its metadata.
The transport layer indicates to the client another encoding in HTTP
headers, and it prevails to what the document encodes.
In this case, the webserver should be able to transform the source document
to match
Actually, I think the omission here is the word canonical. In other words,
Section 16.4 should probably read:
The base character in a variation sequence is never a combining character or a
*canonical* decomposable character.
Note that with this addition, StandardizedVariants.txt poses no
I agree with that analysis.
Mark https://plus.google.com/114199149796022210033
*
*
*— Il meglio è l’inimico del bene —*
**
On Mon, Nov 26, 2012 at 1:53 PM, Whistler, Ken ken.whist...@sap.com wrote:
Actually, I think the omission here is the word canonical. In other
words, Section 16.4
That's because the domain does, in fact, use sinograms and not Deseret. (It's
my Chinese name.)
On 2012年11月26日, at 下午1:54, Philippe Verdy verd...@wanadoo.fr wrote:
I wonder why this IDN link appears to me using sinograms in its domain name,
instead of Deseret letters. The link works, but my
In this instance the web server is not returning an encoding (“Content-Type:
text/html”), which is why I was curious to see that neither web browser picked
up the UTF-8 hint in the XML prolog.
Chrome does detect UTF-8 for that page.
From: ver...@gmail.com [mailto:ver...@gmail.com] On Behalf Of
I've compiled cross-browser data on the question of how to cp1252 decodes
the byte 0x81.
http://bukzor.github.com/encodings/cp1252.html
In summary, all browsers agree that it decodes to U+81. Opera initially
thought it was undefined, but changed their mind in version 12 (the current
version).
Hello everyone,
Just a quick heads-up... We received a report of a problem in a RAID
disk and have arranged to have it swapped out this evening, Pacific
time. That will be sometime after 6pm today November 26 (0200 GMT Nov
27, 1100 Tokyo time), for up to an hour. It should be back online
Also I really don't like the Deseret font:
{font-family: CMU; src: url(CMUSerif-Roman.ttf) format(truetype);}
that you have inserted in your stylesheet (da.css) which is used to display
the whole text content of the page, including the English Latin text at the
bottom part. This downloaded font is
Did you try add the xml:lang=en-Dsrt pseudo-attribute to the html
element, as suggested by the W3C Unicorn validator ?
http://validator.w3.org/unicorn/check?ucn_uri=www.xn--elqus623b.net%2FXKCD%2F1138.htmlucn_lang=frucn_task=conformance#
May be this could help IE and Firefox that can't figure
Anyway, you could at least use Segoe UI before your CMU font, even if Segoe
UI works only in Windows, but it has a decent support for Deseret. May be
there's a good font also on your Mac that ships with some recent version of
Mac OS, which you could list too. Leaving your CMU after them, only for
Opera is most frequently used now in embedded devices, and it is most often
not updatable there in their firmware (difficult to convince appliance
manufacturers like those that build HDTV sets to update their firmware for
their embedding of Opera, they promote their support of the web, but the
web
17 matches
Mail list logo
