Re: xkcd: LTR

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
other OSes.

In all cases, I also suggest that you could tag only the parts that are
written in Deseret with the xml:lang="en-Dsrt", so that you can have a CSS
selector to match these Deseret fonts. For the rest, just use your choice
of "Lucida, Arial, sans-serif" in less selective CSS selectors (that don't
care about the language tags). The template design of these pages are
simple enough that you can do it with just a few modifications.

2012/11/27 Philippe Verdy <verdy_p_at_wanadoo.fr>

> 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 difficult to read as it is
> not hinted at all (so its rendering on screen is extremely poor, we
> probably don't want to print each page of this XKCD series, when the main
> interest is the image which is perfectly readable).
> Could you ask to someone in this list to help you hinting this font a
> minimum (even basic autohinting would be much better).
>
>
> 2012/11/27 Philippe Verdy <verdy_p_at_wanadoo.fr>
>
>> 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.html&ucn_lang=fr&ucn_task=conformance#
>>
>> May be this could help IE and Firefox that can't figure out the language
>> used to properly detect the encoding if they still don't trust the XML
>> declaration in this case, to avoid them to use an encoding "guesser". It is
>> anyay curious because this site is valid as XHTML 1.1 (not as HTML5 which
>> uses a very different and simplified prolog, which is not matched here, so
>> the "legacy" rules should apply to detect XHTML here, then legacy HTML4 if
>> XHTML is no longer recognized by IE and Firefox). Because XHTML is properly
>> tagged, the XML requirements should apply and the XML declaration in the
>> prolog should be used without needing to guess the encoding from the rest
>> of the content (starting by a meta element in the HTML head element).
>>
>>
>> 2012/11/27 John H. Jenkins <jenkins_at_apple.com>
>>
>> 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 <verdy_p_at_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 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 "Unicoded" HTML pages containing Deseret letters.
>>>
>>>
>>> 2012/11/26 John H. Jenkins <jenkins_at_apple.com>
>>>
>>>> Or, if one prefers:
>>>>
>>>> http://www.%e4%ba%95%e4%bd%9c%e6%81%86.net/XKCD/1137.html<http://www.xn--elqus623b.net/XKCD/1137.html>
>>>>
>>>> On 2012年11月21日, at 上午10:22, Deborah Goldsmith <goldsmit_at_apple.com>
>>>> wrote:
>>>>
>>>>
>>>> http://xkcd.com/1137/
>>>>
>>>> Finally, an xkcd for Unicoders. :-)
>>>>
>>>> Debbie
>>>>
>>>>
>>>>
>>>
>>>
>>
>
Received on Mon Nov 26 2012 - 19:49:43 CST